text:
Culture, Medicine, and Psychiatry
An International Journal of Cross-Cultural Health Research
Submission Categories
AAA 2017 Session Highlight: Jonathan Metzl, "Negroes With Guns: Mental Illness, Gun Violence, and the Racial Politics of Firearms"
Posted by sonyapetrakovitz
This week on the blog we are highlighting an oral presentation given at this year's annual American Anthropological Association conference in Washington D.C. by Jonathan Metzl entitled Negroes With Guns: Mental Illness, Gun Violence, and the Racial Politics of Firearms. The session was named "Critical Inquiries: Violence, Trauma, and the Right to Health" on Thursday, November 30, 2017. Metzl combined historiographical and ethnographic analysis to explore the connections between gun violence, mental illness, and shifting anxieties about race in the United States. Metzl discussed how decisions about which crimes American culture diagnoses as "crazy," and which crimes it deems as "sane," are driven as much by the politics and anxieties of particular cultural moments as by the innate neurobiologies of particular assailants. The presentation concluded by describing how racialized questions of whether "the insane" should be allowed to bear arms become the only publicly permissible way to talk about questions of gun control while other narratives, such as the mass psychology of needing so many guns in the first place or the anxieties created by being surrounded by them, remain silenced.
Metzl began his presentation by stating that after the recent and tragic Las Vegas mass shooting, he gave 58 interviews in only two days on "the insane politics of mass shootings." The two main questions that get asked after each mass shooting are: "Is mental illness the cause of mass shootings?" and, "Will treating mental illness stop gun crime?" Both conservative and liberal media analyses include these types of questions, whether or not they ultimately claim mental illness as the answer (for example: NPR's On Point, Politico, and Fox News).
Yet Metzl asked, why do these mental illness questions follow after mass shootings? "Aren't these questions starting to be ridiculous?" Metzl asked, after referring to a study published in the journal Aggression and Violent Behavior which found some mass murderers and serial killers have something in common: autism and head injury. Yet this study was criticized for fueling judgments about an entire section of society and further contributing to the mental illness-gun violence debate.
In some ways, linking mass shootings and mental illness makes sense. Mass shootings are beyond the realm of "sanity" and understanding. Metzl stated that constructing a binary of sane vs. insane, good vs. evil, may be a means of processing grief and uncertainty. Further, many of the mass shooting perpetrators in the last decades have displayed some kind of mental illness symptomatology before their crimes. Mother Jones published an investigation of US mass shootings from 1982-2017 including information on the shooter's race, gender, prior signs of mental health issues, mental health details, and whether or not the weapons were obtained legally. But this information cannot lead to a causal argument.
These types of questions have ideological and political roots, and focusing exclusively on issues of mental health force other concerns out of the debate. At a National Rifle Association (NRA) press conference in December 2012, chief executive Wayne LaPierre suggested having "an active national database for the mentally ill" would help prevent gun violence. In 2013, Ann Coulter wrote a Sound Off on Fox Nation entitled "Guns Don't Kill People, The Mentally Ill Do." After the 2015 Planned Parenthood shooting in Colorado Springs, Paul Ryan called for a need to look at fixing our nation's mental illness health system, not it's gun legislation. Most recently, following news of the mass shooting of parishioners at a Sunday service at a small Baptist church in Texas, Trump proclaimed mental health was the overarching issue, not gun control, even before complete details of the shooter were known.
Following this overview of political ideologies shaping the mental illness conversation, Metzl then asks, "What can reasonably minded people do to push back?"
Metzl then presented five talking points about important ways to push back against the mental-illness-and-mass-shooting account while still remaining respectful of mental illness, treatments, and medications. These talking points discuss why this association is problematic.
1. "It's sample bias – and dangerously so…": Mass shootings come to stand for all shootings. But mass shootings are not the only time we need to talk about gun violence, Metzl stated. When we talk about mass shootings, we are not talking about policy implications for everyday gun death. Every day gun violence, gun proliferation, the ability to buy guns through loop holes should all be part of the national conversation. Worryingly, Metzl states, the situation is about to get much worse. Today (Wednesday, December 6, 2017) the House will vote on a "concealed carry reciprocity" bill, creating a national blanket right to carry a concealed weapon across state lines. For Metzl, the point overall is that the mental illness narrative distracts from daily gun violence and the political negotiations behind gun regulations.
2. "It's stigmatizing and misrepresentative…": Fewer crimes involve people with mental illness. People with sanity are much more dangerous, Metzl stated. People diagnosed with a mental illness are less likely to shot other people, therefore we should really be restricting guns from the sane. Further, Metzl stated that statistically there is no predictive value in using a mental illness diagnosis for gun crime. Individuals with mental illness are more likely to be shot by police than to do the shooting themselves.
3. "It constructs false psychiatric expertise…": Psychiatrists are being told they should be able to predict which of their patients may commit violent act. Yet the pool of people they see are not a high risk population. Metzl stated the public culture of fear may lead psychiatrists to feel culpable for the actions of their patients, over-report their concerns, and complicates the doctor-patient confidentiality bond. In the weeks before the Aurora, Colorado movie theater shooting, shooter James Holmes was seeing a psychiatrist specializing in schizophrenia. In June 2012 The Brian Lehrer Show discussed how psychiatrists determine red flags with their patients and when behavior is concerning enough to warrant further action with Columbia University Director of Law, Ethics, and Psychiatry Paul Appelbaum.
4. "It detracts from awareness of true predictive factors for everyday gun violence…": The mental illness narrative also detracts from other risk factors for everyday gun violence and mass shootings. Substance use or abuse, past history of violence, lack of gun training, social networks, and access to firearms are all important predictive factors for gun violence.
5. "It's racist…": Last but certainly not least, the construction of a mentally ill, dangerous, white, male, gun-owning "loner" is a political choice. The intentional presentation of the individual-isolated-from-society is not supposed to be representative of white culture. Yet in the 1960s, the FBI openly blamed "crazy" black "culture" for the rise of public black activist groups. In debates leading up to the Gun Control Act of 1968, the U.S. Government and mainstream US culture proclaimed links between African American political protest, guns, and mental illness in ways that intensified fears about black activist groups. For example, FBI profilers diagnosed Malcolm X with "pre-psychotic paranoid schizophrenia" and with membership in the "Muslim Cult of Islam" while highlighting his militancy and his "plots" to overthrow the government. The FBI also hung "Armed and Dangerous" posters throughout the southern states warning citizens about Robert Williams, the controversial head of the Monroe, North Carolina chapter of the NAACP author of a manifesto, Negroes With Guns, that advocated gun rights for African Americans. According to the posters, "Williams allegedly has possession of a large quantity of firearms, including a .45 caliber pistol… He has previously been diagnosed as schizophrenic and has advocated and threatened violence."
These historical narratives were linked to black culture, not black individuals. Issues of race and insanity produced black male bodies coded as insane. This association fostered fears that helped mobilize significant public and political sentiment for gun control. Yet there are very different politics of the present day. Metzl states were are in a time when white shooters with mental illness beget reaffirmations of gun rights and groups that advocate anti-government platforms and support broadening of gun rights, such as the Tea Party, take seats in Congress rather than being subjected to police scrutiny. For much of our country's history, guns marked whiteness.
Metzl concluded his presentation with a discussion of a helplessness narrative. There is a kind of inaction about calling mass shootings and gun violence part of mental illness. Since we can not do anything about whether or not individuals have mental illness, it allows us to ignore the other issues and risk factors. This further constructs a kind of persons, not a composition of something larger and more systemic. The learned helplessness surrounding gun crime in the US makes hard rhetorical work to not look at whiteness and mass culture as part of the problem.
Jonathan Metzl, MD, PhD is the Frederick B. Rentschler II Professor of Sociology and Medicine, Health, and Society, Director for the Center for Medicine, Health, and Society, and Professor of Psychiatry at Vanderbilt University. He is also the Research Director of the Safe Tennessee Project, a non-partisan, volunteer-based organization that is concerned with gun-related injuries and fatalities in the United States and in the state of Tennessee. His areas of expertise include mental illness and gun violence with a particular focus on gender and race.
Learn more about Jonathan Metzl at his website, available here.
Posted in Commentary, Conferences, Current Events, Medical Anthropology, News
Tagged aaa, anthropology, brain, conference, Culture, ethnography, gun control, gun violence, health, history, Humanities, mass shootings, medical anthropology, mental health, mental illness, NRA, policy, psychiatry, psychological anthropology, psychology, racism, schizophrenia, society, united states
Book Review: "A Surgeon in the Village"
This week we are highlighting a book review written by Veronica Tomasic originally published in MedHum Daily Dose, a blog for the intersections of medicine and humanities, available here. The book is entitled A Surgeon in the Village: An American Doctor Teaches Brain Surgery in Africa (2017) by Tony Bartelme, published by Beacon Press.
A Surgeon in the Village: An American Doctor Teaches Brain Surgery in Africa (Beacon Press, 2017) is the story of American neurosurgeon Dr. Dilan Ellegala's efforts to provide medical aid in Tanzania. It was written by Tony Bartelme, an American reporter for Charleston, South Carolina's Post and Courier; Bartelme is a three time Pulitzer prize finalist, including for the series that formed the basis for this book. The Post and Courier's executive editor relayed a story to Bartelme about a "crazy brain surgeon who opened a guy's head with a wire saw in Africa"; Bartelme's interest was piqued and thus began the story that he narrates here (269).
A Surgeon in the Village is a bildungsroman of sorts. It describes the beginning of Ellegala's career as a neurosurgeon and his personal journey toward finding meaning in his work. It is also about his ideas for how foreign medical aid should be delivered, and the growth of an organization, Madaktari Africa (Madaktari means doctors in Swahili), that he formed as a result of his ideas.
We first meet Ellegala when he has just completed his neurosurgery training in the US. He is burned out after years of grueling residency and fellowship programs. He travels to Tanzania for six months, volunteering to perform brain surgery at a small, remote hospital. Ellegala is determined to spend as much time as possible vacationing while there. But his plan changes after he starts to attend daily morning meetings where the visiting foreign students and MDs, and local medical personnel gather to discuss their cases. Ellegala observes that the foreign students sit in a privileged position at the front of the room, while the local personnel — such as assistant medical officers (or "AMOs," who have paramedic plus a few years' level of training) — stand at the back of the room. This disturbs his sense of propriety — in the US, medical students typically stand or sit behind attendings and residents. He insists that the students and local personnel trade places, a shift that becomes a central organizing metaphor for the book. The change symbolizes the degree of responsibility Ellegala believes the local staff should have for the care they provide, and the respect he feels they should be shown by foreign visitors.
Galvanized, Ellegala starts to rethink traditional models for providing aid in Tanzania, a country with limited resources to train and keep its own MDs. Rather than encourage foreign MDs to travel to a hospital, perform surgeries for a brief period of time and then leave, Ellegala realizes that it makes more sense to train local AMOs to perform neurosurgical procedures. If they can take over, he reasons, a hospital will transition from being dependent on outside help to being self-sustaining. Ellegala notices an AMO who has a surgeon's confidence about him, Emmanuel Mayyega, and he trains him to diagnose and perform operations for a number of conditions, such as intracranial tumors, head trauma, and hydrocephalus. Eventually, Mayyega trains others. And thus began the "train forward" movement in Tanzania.
Bartelme weaves through his account the challenges Ellegala faces in his career as he devotes time, money, and considerable energy to Madaktari Africa. He also describes some of the ethical issues that are raised by the "train forward" practice. For example, should we accept that people will die in countries where there are not enough traditionally-trained MD surgeons to perform surgeries? Or should surgeries in these countries be performed by people with limited training and supervision because they can save lives? And what about the liability exposure for people trained under such circumstances? One area where the book could have been strengthened would have been to devote a chapter to the history of aid organizations and their varied philosophies. While mention of organizations such as Smile Train, or Paul Farmer's Partners in Health, among others, are interspersed throughout the book, it was never clear to me whether Ellegala was the first person to conceptualize "train forward," or whether such a practice had already been established in other countries.
Altogether, A Surgeon in the Village is a warmly engaging account of one doctor's efforts to make a difference in a part of the world that has limited medical resources, and the personal rewards his efforts afforded him. It would be useful for medical providers and students to read, as well as anyone interested in how best to provide aid to other countries.
Veronica Tomasic (PhD, JD) practices community law in the New Haven, CT, area. She is a scholar of literature, painting, psychoanalytic theory, and end-of-life issues.
For more information about the book, visit the Beacon Press website, here.
Posted in Book Release, Guest Blog, Medical Anthropology, Medical Humanities
Tagged Africa, anthropology, biomedicine, book review, brain, Culture, health, Humanities, medhum, medical anthropology, medical humanities, medicine, treatment, united states
University of Washington Today: Q and A with Janelle Taylor
Yesterday we highlighted Janelle S. Taylor's article from the latest edition of Culture, Medicine, and Psychiatry entitled Engaging with Dementia: Moral Experiments in Art and Friendship, available here. In this post, we follow up with a link to a recent Question & Answer session with Taylor by Kim Eckart, posted on the University of Washington Today website. Included with the Q & A interview is a video with Taylor entitled "How friendships evolve when one person has dementia." In the video, Taylor discusses her research and the implications of the moral challenges taken on by people who have friends with dementia. Visit the UW Today post here.
Posted in Article Highlight, Commentary, Interview, Issues, Medical Anthropology, Medical Humanities
Tagged anthropology, brain, care, caregiving, dementia, ethnography, health, illness, Interview, link, medical anthropology, medical humanities, psychological anthropology, society, technology, treatment, united states, video
Article Highlight: Vol. 41, Issue 2, "Engaging with Dementia: Moral Experiments in Art and Friendship"
This week, we are featuring an Article Highlight written by Monica Windholtz, an Integrated Graduate Studies student in the Anthropology and Bioethics departments at Case Western Reserve University. Monica highlights Janelle S. Taylor's article from the latest edition of Culture, Medicine, and Psychiatry (Vol. 41, Iss. 2), entitled Engaging with Dementia: Moral Experiments in Art and Friendship. The article examines activities and social circumstances used to involve people with dementia in the world. Taylor depicts the steps involved in creating 'moral experiments' that plant patients with dementia in life. Through interviews with caregivers of people with dementia, Taylor explores the role of art and community in engaging those with dementia.
In this article, Taylor analyzes the experiences of individuals with dementia as relayed through the narratives of their caregivers. The article begins with the concept of media portrayals of dementia. Dementia is typically not represented well in the media, with stories devoid of "either subtlety or compassion" (285). In 2014, Julianne Moore received critical acclaim and an Academy Award for her role as the titular character in the film Still Alice, based on a book. The book and movie both chronicle the decline of Alice Howland, a brilliant scientist, as she suffers from early-onset Alzheimer's Disease. While her husband and two oldest children are unable to confront the changes in Alice and focus only on treatment, her daughter Lydia attempts to understand her mother and engage with Alice's new world. The article highlights Lydia's artistic interactions with her mother to introduce the concept of the positive impacts of art and relationships to those with dementia.
While there is currently no effective cure for dementia, caregivers attempt to guide those with dementia to live full lives. The arts have especially served as a way to engage people with dementia, using programs in "storytelling, poetry, painting, dance, theater, [and songwriting]" (287). These programs engage and enrich the lives of individuals suffering with dementia. Artistic forms of expression help to imbue the lives of dementia patients with meaning. In Seattle, such programs to connect with dementia patients have been increasing.
Taylor labels these programs as "moral experiments," following the work of Cheryl Mattingly where experiments are created by people trying to do the right thing (289). By attempting to enrich the lives of those with dementia, artistic programs are exploring new ways to bring meaning to their daily experiences.
Through an analysis of her interviews, Taylor recounts the experiences of those who have served as caregivers for family members or friends with dementia. In one case, a woman named Janet offered to help engage her friend's husband, who was suffering with dementia. Their interactions formed a strong friendship between Janet and the husband, enabling him to still feel a sense of community, even as a patient with dementia.
Taylor found that caregivers and friends of those with dementia often see themselves as modeling or teaching proper behaviors to the rest of society, which may exhibit apprehension or discomfort when engaging with dementia patients. Since these anxious attitudes are common, caregivers may have interventions with their social groups or instruct others in how to interact with the individual with dementia. According to Taylor, people should attempt to interact with dementia patients, as they still understand the social environment, even if the context is not clear. Thus it is important for communities and social groups to still recognize the person with dementia in social settings.
Another striking example of people coming together was with the caregivers of Jacqueline, an immigrant woman in Seattle. Jacqueline had relied on the care and help of her mother in the home for many years, but soon after her mother's death Jacqueline developed dementia. Those that knew Jacqueline were drawn into greater involvement in her life because of her dementia, and helped with the tasks her mother had otherwise taken care of. The group even created a calendar to organize their efforts to aid her.
The Still Alice novel uses the motif of a butterfly to reflect the theme of transformation while still being the same being. As discussed by Taylor, one caregiver of a dementia patient referred to the group that sought to improve the patient's life as their 'cocoon.' The article reflects on the prominent transformations that patients with dementia undergo, and how cocoons and butterflies can both serve as symbols for the moral communities that protect and engage the patients.
In conclusion, Taylor reflects how Still Alice shows that it is not only science and medicine that can improve the lives of those with dementia. Engaging dementia patients through art and the community can help to improve their lives. Finally, there is further room for anthropologists and other researchers to understand and document these other forms of support and improvement.
Posted in Article Highlight, Guest Blog, Issues, Medical Anthropology, Medical Humanities
Tagged anthropology, art therapy, brain, care, caregiving, community, dementia, ethnography, health, Humanities, illness, medical anthropology, medical humanities, medicine, psychological anthropology, science, society, technology, treatment, united states
Article Highlight: Vol. 41, Issue 1, "Innocent or Intentional?: Interpreting Oppositional Defiant Disorder in a Preschool Mental Health Clinic"
To begin article highlights from our latest edition of Culture, Medicine, and Psychiatry (Vol. 41, Iss. 1), this week we are featuring Christine El Ouardani's Innocent or Intentional?: Interpreting Oppositional Defiant Disorder in a Preschool Mental Health Clinic. This article examines contradictions clinicians face when attempting to identify and interpret "intentionality" in young children with oppositional defiant disorder (ODD). El Ouardani argues that conceptualizing intentionality as a developmental, interpersonal process may help to make sense of the multiple discourses and practices clinicians use to try to reconcile the contradictions inherent in diagnosing ODD.
El Ouardani begins by introducing "Carla," a three-year-old who arrived for evaluation and clinical diagnostic determination at the Preschool Behavior Disorder Clinic (PBDC). At first Carla appears as any typical preschooler, energetic and affectionate, but the care team quickly learns she would frequently have violent outbursts and tantrums, lashing out at her family members, other children, or even nearby animals. This type of aggressive, disruptive behavior represents the main reason for the referral of preschoolers to mental health clinics. Early intervention into and treatment of such behaviors is thus of great interest to researchers and clinicians in the field of child mental health care in hopes of helping the young children adapt and cope with life more effectively and prevent the development of later, more destructive behaviors.
El Ouardani discusses that many of the children seen in the PBDC were given a diagnosis of oppositional defiant disorder (ODD), defined in the Diagnostic and Statistical Manual IV (DSM-IV) as "a recurrent pattern of negativistic, defiant, disobedient, and hostile behavior toward authority figures that persists for at least 6 months" that impairs a child's social and/or academic functioning. Yet with very young, preschool-aged children, the diagnosis is controversial. Many children displaying aggressive behavior come from chaotic or otherwise problematic social environments in which this kind of behavior is a reasonable reaction. El Ouardani states that clinicians "must reconcile their characterization of disruptive behavior as a matter of 'self,' with the social environments that seem to be producing this kind of behavior." El Ouardani also draws attention to the values and assumptions of current treatment models and diagnostic procedures. These modules are often based on white, middle-class norms of a "proper" family, moral assumptions of how parents should discipline their children, and the assumed role of a child in social institutions. Many patients at the PBDC did not fall into those characterizations; the reality of their lives are much different.
Moving to a discussion of agency and intentionality, El Ouardani then examines the biomedical, disease model of mental illness, which attempts to remove the blame for the illness from the individual. "Ideologically, then, those afflicted with mental disorders bear no responsibility for the behaviors that directly result from their disorders," El Ouardani writes, since the biological processes of mental illness are taken out of the patient's control. Thus, ODD as a category defined by "intentional" defiance conflicts with the disease model of mental illness. "A central concern of psychiatric therapeutics is to motivate and use the intentionality of a patient to regain control over the self." Yet the idea that preschool-aged children are fully capable of acting with this type of intention, and possess the capacity to do so, is disputed. Therefore clinicians diagnosing a young child with ODD are forced to face the disparities between what is out of the child's control, and what is the "will" of the child.
While discussing the diagnostic criteria for ODD as described in the DSM-IV, El Ouardani emphasizes the criteria for an ODD diagnosis requires the child to be aware of his or her own behavior and is purposely trying to upset or defy the person with whom they are interacting. From this criteria, ODD-labeled children are manipulative and spiteful, qualities that require a degree of intentional malice and deception. These characteristics are not thought to be present in other kinds of childhood mental disorders, such as depression, anxiety, neurodevelopmental disorders, and attention-deficit hyperactivity disorder (ADHD). Clinicians also attribute ODD children with controlling their behavior to influence "weaker" adults, depicting these children as culpable and intentional in their attempts to "confuse and subvert the efforts of their caretakers who are trying to control their behavior."
El Ouardani discuses that determining intentionality is a complex process, especially because of a child's limited verbal capacity for expressing internal states. "In order to identify intentional defiance and diagnose ODD, clinicians had to delineate authentic displays of emotion from those that are inauthentic and manipulative." El Ouardani explains that nuanced, intersubjective exchanges between the children and the clinicians are not captured within the DSM-IV diagnosis. Clinicians often feel frustrated when they perceive a child is trying to manipulate them. This can be compared to clinicians stating "that they feel bad for children with depressive symptoms. They theorized that disruptive behavior in depressed children is a way to cope with internal pain." This difference means the clinicians feel less personally attacked by children without the ODD diagnosis, becoming less frustrated. Further, by diagnosing a child with multiple disorders the clinicians can discursively split the child's "self" into different intentional and non-intentional parts. However, this leads to ODD being categorized as a feature of the individual's character, who that child is as an individual, rather than as a biological disease.
Explanations for why a particular child's behavior were not always attended to within the PBDC. "Clinicians tended to rely upon the widely accepted idea that behavior and psychopathology is a result of interactions between biological temperament and the social environment. According to this model of developmental psychopathology, innate temperament interacts with problematic interpersonal relationships and chaotic household environments, causing the child to react to these negative circumstances with disruptive behavior." Yet this strategy still leaves ambiguities over etiology and treatment.
El Ouardani concludes her article with a discussion of the treatment modality. Clinicians regularly spend the majority of the treatment focused on teaching caretakers how to more effectively discipline and relate to the children. The clinicians primarily focus on a lack of consistency in discipline and structure in both interactions and routines, thus, if the caretakers correctly implement strategic routines, the child will then change their behavior over time. "However, clinicians also informally acknowledged these techniques, which took time and energy that many of the caretakers coming from stressful, low-income, single-caretaker families did not necessarily have."
Dr. Christine El Ouardani is an Assistant Professor in the Department of Human Development at California State University, Long Beach. She is a cultural, medical, and psychological anthropologist who focuses on the anthropology of childhood and lifecourse in Morocco and in North America. El Ouardani's current book project, Discipline and Development: Negotiating Childhood, Authority, and Violence in Rural Morocco, examines the everyday lives of children and youth in a Moroccan village as they move through their families, classrooms, and medical clinics. She analyzes disciplinary interactions between children and caretakers in their extended families and local schools that were often both violent and playful, demonstrating how local conceptions of authority, care, pain, and violence are constructed and enacted in everyday life at different points throughout childhood, and in different institutions. El Ouardani shows how examining the nuances of child socialization practices over time and children's roles in family and community life provides a sharp lens through which to consider larger-scale political, economic, and social change, in this case, contested norms of authority and violence in Moroccan families. For more information, visit her information page on the Department of Human Development, California State Universtity, Long Beach, available here.
Posted in Issues, Medical Anthropology, Medical Humanities
Tagged agency, anthropology, biomedical, biomedicine, brain, care, children, clinic, clinical practice, Culture, diagnosis, ethnography, health, Humanities, illness, intentionality, manipulation, medical anthropology, medical humanities, mental health, mental illness, ODD, Oppositional Defiant Disorder, preschool, psychiatry, psychological anthropology, psychology, treatment, united states
Interview: Jonathan Sadowsky and "Electroconvulsive Therapy in America"
This week on the blog we're highlighting an interview with Dr. Jonathan Sadowsky about his new book Electroconvulsive Therapy in America: The Anatomy of a Medical Controversy, released November 2016 by Routledge. The book (available here) follows the American history of one of the most controversial procedures in medicine, electroconvulsive therapy (ECT), and seeks to provide an explanation of why it has been so controversial, juxtaposing evidence from clinical science, personal memoir, and popular culture. ECT is widely demonized or idealized. Some detractors consider its very use to be a human rights violation, while some promoters depict it as a miracle, as the "penicillin of psychiatry." Sadowsky contextualizes the controversies about ECT, instead of simply engaging in them, making the history of ECT more richly revealing of wider changes in culture and medicine. He shows that the application of electricity to the brain to treat illness is not only a physiological event, but also one embedded in culturally patterned beliefs about the human body, the meaning of sickness, and medical authority.
Dr. Sadowsky is the Theodore J. Castele Professor of Medical History at Case Western Reserve University in Cleveland, OH, the Associate Director of Medical Humanities and Social Medicine, the Medical Humanities and Social Medicine Initiative co-founder, the Associate Director of Medicine, Society, and Culture in the Bioethics department of the Case Western Reserve University School of Medicine, and on the Editorial Board here at Culture, Medicine, and Psychiatry. Sadowsky's research concentrates largely on the history of medicine and psychiatry in Africa and the United States. His previous publications include Imperial Bedlam: Institutions of Madness in Colonial Southwest Nigeria (1999), available here from the University of California Press.
From all of us at CMP, we hope you enjoy our new interview category!
For someone who is thinking about reading your book or about to start, is there anything you would like them to know beforehand?
I would urge everyone to understand that not everybody's experience of a medical therapy is the same. People should be careful not to generalize from experiences they've had, or that loved ones have had, and assume everyone has had the same experience. People who've had bad experiences with ECT have criticized me for to wanting to pay attention to the voices of people who've had good experiences, and people who've have good experiences have wanted to say "oh sure that might have been true in the 1950s but everything's fine now." ECT has a complicated story. I have met people who have told me that this treatment saved their lives and that it did so with either none or only the most mild of adverse effects. Those people are very concerned to make sure that the therapy gets represented in positive light because there are so many negative depictions. At the same time I've heard from and spoken to people who say they've lost 20 points off their IQ after having this treatment, or who had huge gaps in memory, or that they know somebody who had killed themselves after an ECT treatment. And what I find a little bit puzzling still after all these years of working on this book, is the way people are so unwilling to see that other people might have had a different experience than their own. But it's my feeling as a social and cultural historian that it's my responsibility to take into account all voices. So that's the main thing that I want people to know and think about, that experiences of this treatment do vary and people shouldn't be too quick to generalize from their own experience.
How did you become interested in ECT?
I was already several years into my career as a historian of medicine, and in particular psychiatry, and had no knowledge of the treatment other than the images that many of us have from movies like One Flew Over the Cuckoo's Nest. Images that it was a highly frightening and abusive treatment. I was a well-trained student of medicine and psychiatry and I didn't know anything more than that. And then I began to hear stories, both from patients and from clinicians, about it being a valuable treatment and that was just so intriguing to me. So I began to look at some of the clinical literature and it was represented in almost completely the opposite way, as this safe, effective, humane treatment that's been unfairly stigmatized. I felt like these were two completely distinct realities. It wasn't so much that I wanted to reconcile them, but I just wanted to understand how views of this treatment became so bifurcated. And that became the central goal of the project: to understand why it became a controversy and have such strongly held opinions on either side.
What did you find most exciting to research and write about?
I worked on this project for a long time and one of the things that sustained me was that there are so many different angles to it. I was interested in learning about how it was used to treat homosexuals in 1950s, to see what the reaction of the psychoanalytic community was, and how it figured as a symbol for all that was worst in psychiatry in the antipsychiatry moment. And then there were all the debates going back to the inception of the treatment, ongoing continual debates about the extent of memory loss. Is it a serious problem? Is it a rare problem? These debates are still raging. All of this I found so intriguing. The history of ECT is also replete with ironies. Such as the irony that it was developed initially as a treatment for schizophrenia based on a hypothesis that schizophrenia has an inverse relationship with epilepsy. That hypothesis is no longer even believed in, and schizophrenia is not the main indication anymore, and yet it's effective. That's so weird and so seemly random! Another irony is that this treatment which become an icon for frightening medical treatment, and became almost like people's haunting nightmare of how medicine could abuse you if you came into its clutches, was initially developed as a way to try to create a safer, less frightening treatment than chemical convulsive therapy. So it's these layers of irony that I just found so interesting and kept me intrigued in the book.
Did you come across anything unexpected?
Yes, I did come across things that were unexpected. I found the gender politics to be very elusive. I found very little evidence for the idea that women were given ECT for simply protesting against their social role as housewives, which was promoted in another book on ECT. But it does appear likely that over the course of the treatment's history more women have gotten it than men, and there is likely a gender politics to this. Minimally it may mean simply that more women are getting diagnosed with depression, and that's the main indication. And we know that. The diagnosis of depression has predominated among women. There is a darker possibility, which is that women's cognitive abilities haven't been as valued, and so doctors have been more willing to use a treatment that might damage cognitive abilities on women than they were on men. I didn't see any proof for that. But I think there were suggestive circumstances that might indicate that that played a role. In many realms of medicine, and this has been really well documented by historians, anthropologists, and sociologists of medicine, women's complaints about medical treatments are more quickly dismissed than men's complaints. So it's quite possible that some of the complaints about memory loss, which have persisted throughout the history of this treatment, have been taken less seriously because they were so often voiced by women. I'm not arguing that women had more memory loss than men, but if they predominated in the treatment, and there were complaints about memory loss, it is plausible to suggest that perhaps there has been too much dismissal. I didn't have evidence such as clearly sexist language in clinical reports that would strengthen a speculation like that, but one thing I do argue in the book is that the history of ECT is filled with doctors dismissing patient complaints of adverse effects. There are a number of ECT providers now, however, who are trying to be very sensitive to these complaints about memory and cognitive deficits following the treatment, but there still exists in clinical manuals the claim that serious memory problems are extremely rare, and that rarity really hasn't been proven. So it remains a problem. The history of ECT treatment has shown a tendency to dismiss patient complaints about adverse effects, and this has not served anyone well. If anything, the tendency to dismiss complaints has worsened the stigma attached to the treatment. It's understandable that some clinicians might feel some defensiveness for a treatment they feel is helpful and safe, but the dismissal of complaints of adverse effects has led to embittered patients and worsened the stigma. In a recent piece in The Conversation (available here), I argued that if we wanted to spell the stigma attached to ECT, it's going to take more than attesting to its therapeutic efficacy. It's going to mean we have to reconcile with its full costs.
Why was it important for you to try and remain neutral and not argue for or against ECT?
I'm not trying to presume objectivity. Everyone has a point of view. But I thought I could tell a more interesting story by taking a step back and making the controversy itself my study rather than becoming a disputant in the controversy. There's some precedent for this. Didier Fassin, an anthropologist, did a book on AIDS in South Africa, When Bodies Remember (available here), in which he did the same thing; he tried to look at the structure of the controversy. He was trying to understand the medical controversy over HIV as an anthropologist, even though he did actually side more with one than the other. But I do argue in the book there are good reasons to attest to efficacy of ECT and it is a valuable part of psychiatry's repertoire, that it has a place in medicine. But I also argue that there were good grounds for people to contest it and have fear of the treatment. I really try to resist the view, which is very common in clinical literature on ECT, that opposition to ECT is irrational. There are rational reasons for the resistance rooted in some of its historical uses, some of which were abusive, and rooted in the experiences of adverse effects. At the end of the book I lay it all out and I say exactly what I think about ECT after trying to look at it from a step back. I think it's an invaluable part of psychiatry and could be very useful for many people. But I don't think it should be used as a first or second resort; other things should be tried first because there are risks. I'm glad it's there if I should ever need it, but I hope I never need it.
Would ECT be perceived differently if it didn't treat the brain but some other organ?
Probably. In our society now, more than any other organ your brain is you. It is the seed of the self in our self-conception. I would go beyond that. The side effects do occur, without making any kind of representation about how common these problems are, but at least some people do experience permanent memory losses. I used a lot of patient memoirs in the chapter on memory as my source material. And as one of the memoirists wrote: We are our pasts. You lose your memory it's like you lose a part of yourself. I think in some ways people feel they lose a part of themselves if they lose their memories more than even if they were to lose a limb. Losing a limb is very traumatic, I don't mean to minimize that. But in a way, you lose your leg and you say "I lost my leg." It's something that belongs to you, but it isn't you in the same way that maybe you feel your memories are you. Memories are not just something that you have, they're something that you are.
I think ECT is a treatment for the very ill and as a society we do generally accept that treatments for the very ill sometimes involve radical interventions. Chemotherapy for cancers for example. Most of us are glad we have it, and there isn't a large anti-chemotherapy movement. My leading theory for why ECT treatment occasions this kind of resistance is because of depression's uncertain status as illness. No one disagrees that cancer is an illness. When you have cancer you accept that you need surgery or radiation or chemotherapy. These are things that you normally wouldn't do to your body if you were healthy and you didn't need them. Cancer is clearly different from normal. But depression has this ambiguous status for two reasons. It is an ambiguous word in the English language because it refers both to an illness which can be extremely severe, yet it also refers to a mood that's normal and that everybody at some point in their lives gets a little bit depressed. We might have disagreements about how long it has to go on and how severe it has to be to be considered an illness. But it becomes something different when we call it an illness. Secondly why I think depression's status is a bit uncertain, is that there continue to be people who reject medical models for what we call mental illness altogether. Some might believe what people need is talk therapy and they shouldn't have drugs or shock therapies or anything like that. Some might believe that they don't need any treatment at all; they might want to de-medicalize the entire thing. For example, for something to qualify as disease, there has to be some kind of lesion, or something physical that can be identified. Since we don't have the means to do that with depression, it should be removed from the medical realm. I argue against this view. The idea that there has to be some kind of visual marker is arbitrary. I do think what we consider an illness is a social decision. But if you look at it historically and anthropologically, the idea that things we call madness are medical problems is pretty widespread. And in some ways having to have something be visually identifiable is buying into a lot of biomedical hegemony. I just don't see why that should be the criteria for illness. Ultimately it's a philosophical question. Most people in our society do accept that severe depression actually constitutes an illness category, but I think these kinds of ambiguities leave people unsure whether this is something worthy of very strong medicine. ECT is strong medicine. It's a big decision to undergo ECT and it's the right decision for some people. It's a decision that shouldn't be made lightly and shouldn't be treated like a trip to the dentist.
Is there anything else you want to add?
I was really gratified by the number of anthropologists who read and used my first book on insanity in Nigeria, Imperial Bedlam (available here), and I would be thrilled if anthropologists gave this book the same attention. And I'd also like to add that Routledge says there will probably be a paperback within the next year and a half.
Posted in Book Release, Interview, Medical Anthropology, Medical History, Medical Humanities
Tagged Africa, anthropology, biomedicine, brain, care, controversy, Culture, drugs, ECT, electricity, electroconvulsive therapy, gender, health, history, history of medicine, Humanities, illness, media, medical, medical anthropology, medical humanities, medicine, mental health, mental illness, psychiatry, psychological anthropology, psychology, schizophrenia, science, society, technology, treatment, united states
Issue Highlight: Vol 39 Issue 3, Maya Mental Disorders in Belize
Posted by jknopes
With each new issue of Culture, Medicine & Psychiatry, we feature a series of blog posts that highlight the latest publications in our journal. This September's issue includes articles that address psychiatric conditions and the experiences of people with mental illness across numerous cultures. Readers may access the full issue at Springer here: http://link.springer.com/journal/11013/39/3/page/1. In today's issue highlight, we will examine a study on indigenous nosologies of mental illness amongst the Maya of Belize.
Narrative Structures of Maya Mental Disorders
Andrew R. Hatala, James B. Waldram, and Tomas Caal – Pages 449-486
http://link.springer.com/article/10.1007/s11013-015-9436-9
To understand the compatibility of divergent medical traditions, it is first essential to describe how medical systems classify and interpret disorders in particular ways. With this aim in mind, the authors of this ethnographic study sought to develop an picture of indigenous mental illness nosology amongst the Q'eqchi' Maya of southern Belize. They also asked how this knowledge may alternatively coexist, or compete, with biomedical concepts of suffering.
In order to learn about this indigenous medical epistemology, the authors worked with the Maya Healers' Association, a professional, self-regulated group of twelve healers who maintain a garden of medicinal plants for research and who strive to reinvigorate traditional medical practice in Belize. Across ninety-four interviews with healers, the authors uncovered four illness categories that the participants used to describe the roots of mental illnesses: "thinking too much," fright, the day of birth, and spirit "attacks."
These descriptions are sometimes cross-compatible with DSM-V nosologies, as the researchers discovered that "thinking too much" was also listed as a symptom in biomedical models of mental illness. However, unlike the DSM-V, Maya healers tended to characterize overthinking as a "genre" of illness experience rather than as a discrete symptom. Maya healers also characterize mental illnesses as existing within the heart, the mind, and the spirit: thereby expanding the implications of mental illness beyond brain physiology, the proximate explanation employed by biomedical psychiatry.
The authors conclude that it is essential to understand the similarities in the two nosologies to facilitate collaboration between indigenous and biomedical healers, but add that both groups must also be aware of the differences in classificatory schemes that they use to interpret mental illness. In this way, people with mental disorders in Belize may best receive care that accounts for all of the ways they might seek care and understand their illness across the boundaries of medical systems.
Posted in Issue Preview, Issues, Medical Anthropology
Tagged anthropology, beliz, brain, care, cultural, Culture, disease, healing, health, illness, indigenous, local, maya, medical, medicine, mental health, mental illness, mind, nosology, psychiatry, spiritual, suffering, traditional
Winter 2017 Blog Hiatus
Message from the AAA 2017 Annual Meeting
SPA Interview with Dr. Greg Downey and Dr. Daniel Lende
Article Highlight: Expert Knowledge Influences Decision-Making for Couples Receiving Positive Prenatal Chromosomal Microarray Testing Results
Article Highlight
Issue Preview
Medical Anthropology
Follow CMP on Twitter
Anthropologyworks
BMJ Medical Humanities
Somatosphere


This downloadable printable was created for elementary school students at Elementary (A1) level. It was designed for developing your students' Speaking skills. It focuses on the vocabulary topic of Dates and Weather.
mariyat is from/lives in Russia and has been a member of iSLCollective since 2012-02-24 20:31:17. mariyat last logged in on 2019-03-11 15:08:19, and has shared 2 resources on iSLCollective so far.


Philip Trammell Shutze built Pleasant Hill in 1937, and it took the love of one couple to ensure his vision was painstakingly preserved.
When building all exterior decks, the pool and the grand tented pavilion—projects the homeowners took on after purchase—the exact limestone quarry Shutze specified was used, as well as the design from his original blueprints. Dupree Lynch custom-designed the porcelain tiles on the pool and the identical swan motif on the home's weather vane.
The home's original weather vane at the top of the house was recovered and restored before being placed back in its spot on the apex of the home. Dupree Lynch and husband Helvie recreated the original landscape plans with indigenous plants that were first planted by architect William C. Pauley in 1946.
All the Murano glass chandeliers in the estate—four total—were commissioned and custom made by Ca' Rezzonico in Venice, Italy, and an Italian consultant was hired to manage the shipping and reassembling of each one in the home. Oversize artwork sits on custom-made Lucite easels to easily rearrange the foyer for entertaining.
The kitchen is the only room in the house that has been remodeled, mostly to open it up. However, the room's original footprint was not changed, and all the millwork detail Shutze specified for the cabinets and flooring was done to match his exact specifications. A chef-designed La Cornue range was commissioned; Carrara marble was brought in; as well as new faucets, an island and sinks. An elliptical staircase (off camera) was also recreated in the kitchen for symmetry to the foyer.
The sofas in the living room were custom-made by Studio LA and covered in oversize mohair from Jerry Pair with trim from Ainsworth-Noah. Almost all the artwork in the home is European and was acquired at auctions abroad. The handpulled plasterwork throughout the house is quite extraordinary.
The bar on the third floor is actually from cruise ship SS Normandie. The original linoleum was replaced with custom 4-inch walnut planks made with extruded brass to echo the feeling of an actual ship's deck.
Benches with orange mohair fabric from Travis & Company and a gold leaf Giacometti-inspired base from Ainsworth-Noah help bring out the warmth from the ceiling.
The loggia overlooking the back of the home's rolling greens and manicured lawns, which completely obscure the street. The aluminum furniture from Kreiss includes custom slipcovers that Dupree Lynch designed.
The dining room, complete with Shutze's original handpulled plasterwork, also houses a working wood-burning fireplace.
This is our home. It is full of love, laughter and beauty. Every piece of artwork, sculpture and furniture was chosen by me and my husband, Dr. William W. Helvie; therefore, every piece inside has a beautiful memory or experience attached to it.
My husband and I are the fourth owners of the home, and upon our purchase of the property in 1997, the third owner gave us only three photographs and a business card: They were pictures of the original swan weather vane that was designed and placed on the top of the roof, and the name and number of where he dropped it off years ago. We contacted the company and were very fortunate to retrieve the weather vane—we discovered it weighed 2,000 pounds and was made of cast iron. It took us hiring two French master water gold-leafing gilders to prepare it for its new finish. It was completely restored with gold leafing and the empire green enamel that echoed the Prince of Wales feathers architectural detail on the rest of the house. It required a massive crane to lift and place it in the original location on the house. This was the beginning of a long journey of discovering the house's hidden secrets and, most importantly, how to impeccably restore and maintain her in the style to which she was accustomed.
Piggle told us that Shutze wanted "the home to be open to the light" and for "everyone to enter through the front door." This explains why the windows are double or triple the size of a typical Regency house and there is a grand entrance with the elliptical staircase. Piggle and her family desired the symmetry of the classic Regency-style home, but they also wanted a more modern style added to the architecture, which clarifies the art deco influence seen on the second and third floors.
My husband and I did not fully understand the extent of the restoration project and repair required when we first started—though we did know a house like this deserved only the highest level of skilled craftsmanship from all over the world. We took it on with a passion and did the necessary research on how to accurately restore the house and grounds. To begin, we visited the Atlanta History Center to investigate the history of the house before commencing projects—some that would take 20 years to complete.
Miraculously, the home had been kept as it was originally for almost 100 years. The only room that has been completely renovated is the kitchen. It was a typical 1930s kitchen when we bought the house. Carefully, we took every design element from Shutze's original millwork for the kitchen cabinetry to mirror exactly his specifications in the dining-room panel details.
We were fortunate to have Shutze's original blueprints with all the specifications detailed. The pool and tented pool pavilion are now located exactly where he originally envisioned them being placed (he was unable to complete them). Design firm Bill Ingram Architect and I carried out that project for him. We used Shutze's preferred limestone quarry for the cutting of all exterior decks in the building of the pool and surrounding decks. Piggle's grandchildren also gave us the original landscape plans designed by architect William C. Pauley in January 1946. Shutze believed in using only indigenous plants on his gardens and projects, including boxwoods, magnolias, camellias, hollies, cherry trees and dogwoods, which we abided by in our own plans.We decided to triple-plant the bushes and trees, using layer upon layer of green texture to create a totally private-park-like setting. You can't see the house from the road, so once you approach our gated entrance, you know you have arrived at a special place. This was very intentional on our part: My husband and I wanted you to feel like you could be anywhere in the world when you enter the estate grounds.
The house is painted in varying shades of white, conveying a neutral palette, which is perfect because it allows the artwork to shine on the large walls with high ceilings. There is also a natural flow to the house, which allows for entertaining throughout the main level, the south-facing loggia; and on the third floor, which has exterior decks for dinner parties and dancing. We also love to host dinner parties alfresco in the tented pool pavilion. The third floor features the SS Normandie influence with its art deco aspect—the architect's vision comes through in the Normandie cruise ship bar.
My husband and I both feel like it has been a real honor to be given the temporary guardianship of this magnificent house and gardens over the last two decades and to restore her into an even more beautiful home.


text:
More than 500 Scots killed by drug misuse last year
Wednesday August 18 2010, 12.23am, The Times
Fergus Ewing announced a two-year national programme for Naloxone, an opiate antidote that temporarily reverses the effects of an overdose
EUAN ANDERSON\UNIVERSAL NEWS AND SPORT (SCOTLAND)
Misuse of drugs claimed the lives of more than 500 people in Scotland last year, official figures show.
Although the number of drug- related deaths in 2009 fell for the first time in four years, from 574 in 2008 to 545, it was still the second-highest annual number to be recorded.
One expert described the figure as "a shattering toll" for a country the size of Scotland.
Professor Neil McKeganey, head of the Centre for Drug Misuse Research at the University of Glasgow, also called for a change in the Scottish government's anti-drugs strategy, claiming that the emphasis on the heroin substitute methadone was not working.
The number of deaths last year was 29 fewer than in 2008, but it was 90 more than in

redpajama_set_name: RedPajamaCommonCrawl


you will notice is the high back cushion, perfect for head support. The back cushion has a split, so the lower part of the back cushion gently cradles the lower back & provides lower lumbar support.
The Cumbria is compact, just 97cm deep for the sofa's & 94cm deep for the arm- chair. The arms of the Cumbria are slim & elegant, as are the legs; whether you choose the stylish Kensington legs with castors, or the Ainsley or Dylan legs, in either a dark or light wood finish.
If your check-list for a sofa contains these criterion, then Cumbria may be the model for you. Many find this a design that provides for a more contemporary sofa with the comfort qualities of some of our more traditional designs.
The Cumbria comes as a Large Sofa, Small Sofa, Love Seat & an Armchair & with a matching footstool or perhaps an Ottolong to finish the look.
Cumbria Sofa Side - Modena 13921 Sand.


electric kettle water design in now production ibis cordless bistro bodum 17 ounce mini double wall with.
redo fireplace redone hearth redoing a remodel el brick remodeling 8 ideas updating best how to surround mantel.
old work metal electrical box round boxes vs new.
a stacked stone fireplace in modern living room environment with flame rock tile white.
next 2 stroke gas scooter engine 4 cu c model.
stainless steel electric kettle china copper and toaster set.
cleaning stone fireplace surround deep cleaned hearth how to clean surr.
bay electric fireplace reviews real flame home design inspirations hampton 50 in wa.
mounting a over fireplace hiding wires for wall mounted great how pictures of tv mou.
faucets web site faucet parts home ideas for small living room who makes pegasus lowes.


Jukebox Poker is easy to operate and easy for your guests to play. They don't even need to know how to play poker! User friendly software that easily allows in house staff the ability to host Jukebox Poker events without hiring a company to do it for you. All you supply is a sound system and computer. Music is legal and licensed through the Audio Video Licensing Agency (AVLA). Over 40 different games with more games available at no additional cost as they are released. BONUS: Comes with a complete Digi-Beats Music Library of over 25,000 songs and counting! Initial purchase subscription is valid for 90 days, then monthly/annual subscription fees apply as described below.
This Item is an ongoing subscription for the Jukebox Poker item as listed above. Subscribers have the choice of subscribing in the following 2 ways: 1) Pre-Paid Annual Subscription (Get 2 Months Free!) 2) Monthly, Quarterly or Semi-annual Subscription(s). Once you have renewed your subscription, your new unlock file will be sent to you by email within 72 hours of your purchase.


(Nanowerk News) Researchers at Chalmers University of Technology have discovered that large area graphene is able to preserve electron spin over an extended period, and communicate it over greater distances than had previously been known. This has opened the door for the development of spintronics, with an aim to manufacturing faster and more energy-efficient memory and processors in computers. The findings will be published in the journal Nature Communications ("Long Distance Spin Communication in CVD Graphene").
"We believe that these results will attract a lot of attention in the research community and put graphene on the map for applications in spintronic components," says Saroj Dash, who leads the research group at Chalmers University of Technology.
"In future spin-based components, it is expected that the electrons must be able to travel several tens of micrometers with their spins kept aligned. Metals, such as aluminium or copper, do not have the capacity to handle this. Graphene appears to be the only possible material at the moment," says Saroj Dash.
"Our measurements show that the spin signal is preserved in graphene channels that are up to 16 micrometers long. The duration over which the spins stay aligned has been measured to be over a nanosecond," says Chalmers researcher Venkata Kamalakar who is the article's first author.
"This is promising because it suggests that the spin parameters can be further improved as we develop the method of manufacturing.
"Graphene is a good conductor and has no band gaps. But in spintronics there is no need for band gaps to switch between on and off, one and zero. This is controlled instead by the electron's up or down spin orientations," Saroj Dash explains.
Spin is a quantum mechanical property of elementary particles, which among other things gives rise to the phenomenon of magnetism. The spin can be directed either up or down. For the electrons in a normal electric current, the spin is randomly distributed, and the stream carries no spin signal. But with the help of magnets, electrons that are fed into a conductor can be polarised, which means they all have their spin directed up or down. You could liken the electrons to a series of small compass needles, all pointing towards north or south. The challenge is to maintain this state long enough and over sufficiently long distances.


Hot towel warmer cabinets maintain an average temperature of 176°F. Towels heat up quickly and units can be placed on most countertops, carts, or below treatment tables. Double walled metal door with rust-proof aluminum interior and silicon door seal. 3-tiered wire metal rack and condensation drip tray included. Capacity: 144pcs.


text:
Researchers learn how the cancer-causing stomach bacterium Helicobacter maintains its shape
NSF-funded scientists reporting in the journal eLife have revealed that they are closer to understanding a risk factor for stomach cancer: how the bacterium Helicobacter pylori maintains its shape.
About half the world's population is chronically infected with H. pylori, a bacterium whose helical, or corkscrew, shape allows it to burrow into the mucus lining of the stomach.
Researchers at the Fred Hutchinson Cancer Research Center home in on stomach cancer risk.
Image credit: Robert Hood / Fred Hutch News Service
"Shape is important to the survival of bacteria," said Jong-on Hahm, a program director in NSF's Division of Graduate Education.
Scientists have long wondered how H. pylori becomes helical. Investigators at the Fred Hutchinson Cancer Research Center in Seattle, Washington, used fluorescence microscopy to discover how the shape develops.
"We're really excited about the fact that we're starting to understand the molecular biophysical mechanism by which H. pylori maintains its helical shape," said Nina Salama, the bacteriologist who led the study. Her group demonstrated that H. pylori's corkscrew shape is essential for its ability to infect the stomach.
A molecular understanding of how different bacteria species acquire their characteristic shapes could provide insights needed to develop better-targeted antibiotics.
More information about the research may be found on the Fred Hutchinson website.
Source: NSF


text:
package com.paypal.risk.hadoopjt.entity

import org.json.{JSONArray, JSONObject}
import org.slf4j.LoggerFactory
import scala.language.implicitConversions
import scala.collection.mutable.ListBuffer

import com.paypal.risk.hadoopjt.JobTracker
import com.paypal.risk.hadoopjt.util._
import EntityTraits._

/**
 * @author Danick
 */
object HadoopV2Crawler extends JobTracker {

  val logger = LoggerFactory.getLogger(getClass())

  implicit def IntToString(data: Int): String = data.toString()

  implicit def LongToString(data: Long): String = data.toString()

  implicit def DoubleToString(data: Double): String = data.toString()

  var urlLoader: String => String = NetUtils.httpGet

  case class ClusterMetrics(val appsSubmitted: String,
                            val appsCompleted: String,
                            val appsPending: String,
                            val appsRunning: String,
                            val appsFailed: String,
                            val appsKilled: String,
                            val reservedMB: String,
                            val availableMB: String,
                            val allocatedMB: String,
                            val containersAllocated: String,
                            val containersReserved: String,
                            val containersPending: String,
                            val totalMB: String,
                            val totalNodes: String,
                            val lostNodes: String,
                            val unhealthyNodes: String,
                            val decommissionedNodes: String,
                            val rebootedNodes: String,
                            val activeNodes: String) extends ListableObject {
    override def toList = List(this.appsSubmitted, this.appsCompleted,
      this.appsPending, this.appsRunning, this.appsFailed,
      this.appsKilled, this.reservedMB, this.availableMB,
      this.allocatedMB, this.containersAllocated,
      this.containersReserved, this.containersPending,
      this.totalMB, this.totalNodes, this.lostNodes,
      this.unhealthyNodes, this.decommissionedNodes,
      this.rebootedNodes, this.activeNodes)
  }

  object ClusterMetrics extends SchemaObject {
    override def getSchema = List("appsSubmitted", "appsCompleted",
      "appsPending", "appsRunning", "appsFailed", "appsKilled", "reservedMB",
      "availableMB", "allocatedMB", "containersAllocated", "containersReserved",
      "containersPending", "totalMB", "totalNodes", "lostNodes", "unhealthyNodes",
      "decommissionedNodes", "rebootedNodes", "activeNodes")
  }

  override def getClusterInfo() = {
    val clusterMetricsStr = loadRestfulAPI(Constants.JT_HTTP_BASE_URL + "/ws/v1/cluster/metrics")
    val clusterMetrics = new JSONObject(clusterMetricsStr).getJSONObject("clusterMetrics");
    List(new ClusterMetrics(clusterMetrics.getInt("appsSubmitted"),
      clusterMetrics.getInt("appsCompleted"), clusterMetrics.getInt("appsPending"),
      clusterMetrics.getInt("appsRunning"), clusterMetrics.getInt("appsFailed"),
      clusterMetrics.getInt("appsKilled"), clusterMetrics.getLong("reservedMB"),
      clusterMetrics.getLong("availableMB"), clusterMetrics.getLong("allocatedMB"),
      clusterMetrics.getLong("containersAllocated"), clusterMetrics.getLong("containersReserved"),
      clusterMetrics.getLong("containersPending"), clusterMetrics.getInt("totalMB"),
      clusterMetrics.getInt("totalNodes"), clusterMetrics.getInt("lostNodes"),
      clusterMetrics.getInt("unhealthyNodes"), clusterMetrics.getInt("decommissionedNodes"),
      clusterMetrics.getInt("rebootedNodes"), clusterMetrics.getInt("activeNodes")))
  }

  //TODO enhance the data
  case class SchedulerQueue(val queueName: String,
                            val capacity: String,
                            val maxCapacity: String,
                            val usedCapacity: String,
                            val numApplications: String,
                            val maxApplicationsPerUser: String,
                            val numContainers: String) extends ListableObject {
    override def toList: List[String] = List(this.queueName, this.numApplications, this.capacity, this.maxCapacity, this.usedCapacity, this.maxApplicationsPerUser, this.numContainers)
  }

  object SchedulerQueue extends SchemaObject {
    override def getSchema: List[String] = List("Name", "NumApps", "Capacity",
      "MaxCapacity", "CurrentCapacity", "MaxAppsPerUser", "#RunningContainers")
  }

  override def getQueuesInfo() = {
    val schedulerJson = loadRestfulAPI(Constants.JT_HTTP_BASE_URL + "/ws/v1/cluster/scheduler")
    val rootQueues: JSONArray = new JSONObject(schedulerJson).
      getJSONObject("scheduler").
      getJSONObject("schedulerInfo")
      .getJSONObject("queues").getJSONArray("queue");

    parseQueueArrayInfo(rootQueues, "")
  }

  def parseQueueArrayInfo(queue: JSONArray, prefix: String): ListBuffer[SchedulerQueue] = {
    val listBuffer = ListBuffer[SchedulerQueue]()
    for (i <- 0 until queue.length()) {
      listBuffer ++= parseQueueInfo(queue.getJSONObject(i), prefix)
    }
    listBuffer
  }

  def parseQueueInfo(queue: JSONObject, prefix: String) = {
    val listBuffer = ListBuffer[SchedulerQueue]()
    var maxApplicationsPerUser: String = ""
    var numContainers: String = ""
    if (!queue.has("queues")) {
      maxApplicationsPerUser = queue.getInt("maxApplicationsPerUser")
      numContainers = queue.getInt("numContainers")
    }
    val queueInfo = new SchedulerQueue(prefix + queue.getString("queueName"), queue.getDouble("capacity"),
      queue.getDouble("maxCapacity"), queue.getDouble("usedCapacity"), queue.getInt("numApplications"), maxApplicationsPerUser, numContainers)
    listBuffer.append(queueInfo)
    if (queue.has("queues")) {
      listBuffer ++= parseQueueArrayInfo(queue.getJSONObject("queues").getJSONArray("queue"), prefix + "  ")
    }
    listBuffer
  }

  case class Application(val id: String,
                         val user: String,
                         val name: String,
                         val applicationType: String,
                         val queue: String,
                         val progress: String,
                         val elapsedTime: String,
                         val allocatedMB: String,
                         val allocatedVCores: String,
                         val runningContainers: String,
                         val trackingUI: String,
                         val trackingUrl: String,
                         val diagnostics:String) extends ListableObject {
    override def toList: List[String] = List(this.id, this.applicationType, this.user,
      this.queue, this.name, this.progress, this.elapsedTime, this.allocatedMB, this.allocatedVCores, this.runningContainers)
  }

  object Application extends SchemaObject {
    override def getSchema: List[String] = List("application_Id", "Type",
      "User", "Queue", "Name", "Prgrs", "TimeUsd", "Mem(MB)", "VCr", "Cntnr")
  }

  case class MapReduceJobInfo(val mapProgress: String,
                              val mapsTotal: String,
                              val mapsPending: String,
                              val mapsRunning: String,
                              val mapsCompleted: String,
                              val failedMapAttempts: String,
                              val killedMapAttempts: String,
                              val reduceProgress: String,
                              val reducesTotal: String,
                              val reducesPending: String,
                              val reducesRunning: String,
                              val reducesCompleted: String,
                              val failedReduceAttempts: String,
                              val killedReduceAttempts: String) {
    def getSchema = {
      List("Kind", "% Complete", "Num Tasks", "Pending",
        "Running", "Complete", "Failed", "Killed")
    }

    def getSchemaData = {
      val result = new ListBuffer[Seq[String]]
      result.append(List("map", mapProgress + "%", mapsTotal, mapsPending, mapsRunning, mapsCompleted, failedMapAttempts, killedMapAttempts))
      result.append(List("reduce", reduceProgress + "%", reducesTotal, reducesPending, reducesRunning, reducesCompleted, failedReduceAttempts, killedReduceAttempts))
      result
    }
  }

  class MapReduceJob(id: String,
                     user: String,
                     name: String,
                     applicationType: String,
                     queue: String,
                     progress: String,
                     elapsedTime: String,
                     allocatedMB: String,
                     allocatedVCores: String,
                     runningContainers: String,
                     trackingUI: String,
                     trackingUrl: String,
                     diagnostics:String) extends Application(id, user, name, applicationType, queue, progress, elapsedTime,
    allocatedMB, allocatedVCores, runningContainers, trackingUI, trackingUrl,diagnostics) {
    var detailed: MapReduceJobInfo = null

    def getDetailedData = {
      detailed
    }

    def setDetailedData(jobInfo: MapReduceJobInfo) {
      detailed = jobInfo
    }
  }

  /**
   *
   * @param id task id
   * @param state NEW, SCHEDULED, RUNNING, SUCCEEDED, FAILED, KILL_WAIT, KILLED
   * @param _type MAP or REDUCE
   * @param successfulAttempt The the id of the last successful attempt
   * @param progress The progress of the task as a percent
   * @param startTime The time in which the task started (in ms since epoch)
   * @param finishTime The time in which the task finished (in ms since epoch)
   * @param elapsedTime The elapsed time since the application started (in ms)
   */
  case class MapReduceJobTask(val id: String,
                              val state: String,
                              val _type: String,
                              val successfulAttempt: String,
                              val progress: String,
                              val startTime: Long,
                              val finishTime: Long,
                              val elapsedTime: Long)

  def getMapReduceJobTasks(mrJob: MapReduceJob, tasktype: String, tasksate: String) = {
    require(mrJob != null)
    require(tasktype != null)
    require(tasksate != null)

    val mrJobId = "job_" + mrJob.id.replace("application_", "")
    val trackingUI = mrJob.trackingUI

    var taskUrl = mrJob.trackingUrl
    if (!taskUrl.endsWith("/"))
      taskUrl = taskUrl + "/"

    if (trackingUI.equals("History")) {
      taskUrl = Constants.JT_YARN_MR_HISTORY_ADDRESS + "/ws/v1/history/mapreduce/jobs/" + mrJobId + "/tasks"
    } else {
      taskUrl = taskUrl + "ws/v1/mapreduce/jobs/" + mrJobId + "/tasks"
    }

    logger.debug("Request for job tasks from " + taskUrl)

    val tasksString = loadRestfulAPI(taskUrl)
    logger.debug("Response " + tasksString)
    val tasksJsonObj: JSONObject = new JSONObject(tasksString)
    val listBuffer = ListBuffer[MapReduceJobTask]()
    if (tasksJsonObj.get("tasks") != JSONObject.NULL) {
      val tasks = tasksJsonObj.getJSONObject("tasks").getJSONArray("task")
      for (i <- 0 until tasks.length()) {
        val taskObj = tasks.getJSONObject(i)
        val mrJobTask = new MapReduceJobTask(taskObj.getString("id"), taskObj.getString("state"),
          taskObj.getString("type"), taskObj.getString("successfulAttempt"), taskObj.getDouble("progress"),
          taskObj.getLong("startTime"), taskObj.getLong("finishTime"), taskObj.getLong("elapsedTime"))

        if (mrJobTask._type.equalsIgnoreCase(tasktype)) {
          tasksate match {
            case "running" =>
              if (mrJobTask.state.equalsIgnoreCase("RUNNING"))
                listBuffer.append(mrJobTask)
            case "completed" =>
              if (mrJobTask.state.equalsIgnoreCase("SUCCEEDED"))
                listBuffer.append(mrJobTask)
            case "killed" =>
              if (mrJobTask.state.equalsIgnoreCase("KILLED"))
                listBuffer.append(mrJobTask)
            case "failed" =>
              if (mrJobTask.state.equalsIgnoreCase("FAILED"))
                listBuffer.append(mrJobTask)
            case _ =>
          }
        }
      }
    }
    listBuffer
  }

  /**
   *
   * @param id task id
   * @param state The state of the task attempt - valid values are: NEW, UNASSIGNED, ASSIGNED, RUNNING, COMMIT_PENDING, SUCCESS_CONTAINER_CLEANUP, SUCCEEDED, FAIL_CONTAINER_CLEANUP, FAIL_TASK_CLEANUP, FAILED, KILL_CONTAINER_CLEANUP, KILL_TASK_CLEANUP, KILLED
   * @param _type type of the task
   * @param assignedContainerId The container id this attempt is assigned to
   * @param nodeHttpAddress The http address of the node this task attempt ran on
   * @param diagnostics The diagnostics message
   * @param progress The progress of the task attempt as a percent
   * @param startTime The time in which the task attempt started (in ms since epoch)
   * @param finishTime The time in which the task attempt finished (in ms since epoch)
   * @param elapsedTime The elapsed time since the task attempt started (in ms)
   */
  case class MapReduceTaskAttempt(val id: String,
                                  val state: String,
                                  val _type: String,
                                  val assignedContainerId: String,
                                  val nodeHttpAddress: String,
                                  val diagnostics: String,
                                  val progress: String,
                                  val startTime: String,
                                  val finishTime: String,
                                  val elapsedTime: String)

  def getMapReduceTaskAttempts(mrJob: MapReduceJob, mrJobTask: MapReduceJobTask, attemptstatus: String) = {
    require(mrJob != null)
    require(mrJobTask != null)
    require(attemptstatus != null)

    val mrJobId = "job_" + mrJob.id.replace("application_", "")
    val trackingUI = mrJob.trackingUI

    var taskUrl = mrJob.trackingUrl
    if (!taskUrl.endsWith("/"))
      taskUrl = taskUrl + "/"

    if (trackingUI.equals("History")) {
      taskUrl = Constants.JT_YARN_MR_HISTORY_ADDRESS + "/ws/v1/history/mapreduce/jobs/" + mrJobId + "/tasks"
    } else {
      taskUrl = taskUrl + "ws/v1/mapreduce/jobs/" + mrJobId + "/tasks"
    }
    taskUrl = taskUrl + "/" + mrJobTask.id + "/attempts"

    logger.debug("Request for map-reduce job tasks attempt from " + taskUrl)

    val taskAttemptsString = loadRestfulAPI(taskUrl)
    val fixedAttemptString = taskAttemptsString.replace("\"type\":\"REDUCE\"","\"_type\":\"REDUCE\"")
    .replace("\"type\":\"MAP\"","\"_type\":\"MAP\"")
    logger.debug("Response " + fixedAttemptString)
    val taskAttemptsJsonObj: JSONObject = new JSONObject(fixedAttemptString)
    val listBuffer = ListBuffer[MapReduceTaskAttempt]()
    if (taskAttemptsJsonObj.get("taskAttempts") != JSONObject.NULL) {
      val taskAttempts = taskAttemptsJsonObj.getJSONObject("taskAttempts").getJSONArray("taskAttempt")
      for (i <- 0 until taskAttempts.length()) {
        val taskAttemptsObj = taskAttempts.getJSONObject(i)
        val mrJobTaskAttempt = new MapReduceTaskAttempt(taskAttemptsObj.getString("id"), taskAttemptsObj.getString("state"),
          taskAttemptsObj.getString("_type"), taskAttemptsObj.getString("assignedContainerId"), taskAttemptsObj.getString("nodeHttpAddress"),
          taskAttemptsObj.getString("diagnostics"), taskAttemptsObj.getDouble("progress"),
          taskAttemptsObj.getLong("startTime"), taskAttemptsObj.getLong("finishTime"), taskAttemptsObj.getLong("elapsedTime"))

        //use case match to handle one-multi mapping
        attemptstatus match {
          case "running" =>
            if (mrJobTaskAttempt.state.equalsIgnoreCase("running"))
              listBuffer.append(mrJobTaskAttempt)
          case "failed" =>
            if (mrJobTaskAttempt.state.equalsIgnoreCase("failed"))
              listBuffer.append(mrJobTaskAttempt)
          case "killed" =>
            if (mrJobTaskAttempt.state.equalsIgnoreCase("killed"))
              listBuffer.append(mrJobTaskAttempt)
          case "succeeded" =>
            if (mrJobTaskAttempt.state.equalsIgnoreCase("succeeded"))
              listBuffer.append(mrJobTaskAttempt)
          case _ =>
        }
      }
    }
    listBuffer
  }

  def fullFillMapReduce(mrJob: MapReduceJob) {
    var trackingUrl = mrJob.trackingUrl
    val trackingUI = mrJob.trackingUI
    if ("ApplicationMaster".equals(trackingUI)) {
      if (!trackingUrl.endsWith("/")) {
        trackingUrl = trackingUrl + "/"
      }
      trackingUrl = trackingUrl + "ws/v1/mapreduce/jobs/"
    } else {
      trackingUrl = Constants.JT_YARN_MR_HISTORY_ADDRESS + "/ws/v1/history/mapreduce/jobs/"
    }
    try {
      val jobUrl = trackingUrl + "job_" + mrJob.id;
      val jobString = loadRestfulAPI(jobUrl)
      val jobJsonObj: JSONObject = new JSONObject(jobString)
      if (jobJsonObj.get("job") != JSONObject.NULL) {
        val job = jobJsonObj.getJSONObject("job")
        if ("ApplicationMaster".equals(trackingUI)) {
          mrJob.setDetailedData(new MapReduceJobInfo(job.getDouble("mapProgress"),
            job.getInt("mapsTotal"), job.getInt("mapsPending"), job.getInt("mapsRunning"), job.getInt("mapsCompleted"),
            job.getInt("failedMapAttempts"), job.getInt("killedMapAttempts"),
            job.getDouble("reduceProgress"), job.getInt("reducesTotal"), job.getInt("reducesPending"),
            job.getInt("reducesRunning"), job.getInt("reducesCompleted"), job.getInt("failedReduceAttempts"), job.getInt("killedReduceAttempts")))
        } else {
          mrJob.setDetailedData(new MapReduceJobInfo(100.00,
            job.getInt("mapsTotal"), 0, 0, job.getInt("mapsCompleted"),
            job.getInt("failedMapAttempts"), job.getInt("killedMapAttempts"),
            100.00, job.getInt("reducesTotal"), 0,
            0, job.getInt("reducesCompleted"), job.getInt("failedReduceAttempts"), job.getInt("killedReduceAttempts")))
        }

      }
    } catch {
      case e: Exception =>
        System.err.println("Unable to get MR job information for job_" + mrJob.id + "  from " + trackingUrl)
    }

  }

  def getApplications(appId: String, user: String, queue: String = null, name: String = null) = {
    val listBuffer = ListBuffer[Application]()
    if (appId != null) {
      val app = getApplication(appId)
      if (app != null)
        listBuffer.append(app)
      listBuffer
    } else {
      var appUrl = Constants.JT_HTTP_BASE_URL + "/ws/v1/cluster/apps?states=running"
      if (user != null)
        appUrl += "&user=" + user
      if (queue != null)
        appUrl += "&queue=" + queue

      try {
        val appsString = loadRestfulAPI(appUrl)
        val appsJsonObj: JSONObject = new JSONObject(appsString)
        if (appsJsonObj.get("apps") != JSONObject.NULL) {
          val apps = appsJsonObj.getJSONObject("apps").getJSONArray("app")
          for (i <- 0 until apps.length()) {
            val appObj = apps.getJSONObject(i)
            if ("MAPREDUCE".equalsIgnoreCase(appObj.getString("applicationType"))) {
              listBuffer.append(new MapReduceJob(appObj.getString("id").replace("application_", ""),
                appObj.getString("user"), appObj.getString("name"),
                appObj.getString("applicationType"), appObj.getString("queue"),
                appObj.getLong("progress") + "%", TimeUtils.readableTime(appObj.getLong("elapsedTime")),
                appObj.getLong("allocatedMB"), appObj.getInt("allocatedVCores"),
                appObj.getInt("runningContainers"), appObj.getString("trackingUI"), appObj.getString("trackingUrl"),appObj.getString("diagnostics")))
            } else {
              listBuffer.append(new Application(appObj.getString("id").replace("application_", ""),
                appObj.getString("user"), appObj.getString("name"),
                appObj.getString("applicationType"), appObj.getString("queue"),
                appObj.getLong("progress") + "%", TimeUtils.readableTime(appObj.getLong("elapsedTime")),
                appObj.getLong("allocatedMB"), appObj.getInt("allocatedVCores"),
                appObj.getInt("runningContainers"), appObj.getString("trackingUI"), appObj.getString("trackingUrl"),appObj.getString("diagnostics")))
            }

          }
        }
      } catch {
        case e: Exception => System.err.println("Invalid parameters, please check!")
      }

      if (name == null)
        listBuffer
      else
        listBuffer.filter(p => p.name.toLowerCase().contains(name.toLowerCase()))
    }
  }

  def getApplication(appId: String) = {
    require(appId != null)
    val normAppId = normalizeId(appId)
    var appUrl = Constants.JT_HTTP_BASE_URL + "/ws/v1/cluster/apps/" + normAppId
    var result: Application = null
    try {
      val appsString = loadRestfulAPI(appUrl)
      val appsJsonObj: JSONObject = new JSONObject(appsString)
      if (appsJsonObj.get("app") != JSONObject.NULL) {
        val appObj = appsJsonObj.getJSONObject("app")
        if ("MAPREDUCE".equalsIgnoreCase(appObj.getString("applicationType"))) {
          result = new MapReduceJob(appObj.getString("id").replace("application_", ""),
            appObj.getString("user"), appObj.getString("name"),
            appObj.getString("applicationType"), appObj.getString("queue"),
            appObj.getLong("progress") + "%", TimeUtils.readableTime(appObj.getLong("elapsedTime")),
            appObj.getLong("allocatedMB"), appObj.getInt("allocatedVCores"),
            appObj.getInt("runningContainers"), appObj.getString("trackingUI"), appObj.getString("trackingUrl"),appObj.getString("diagnostics"))
        } else {
          result = new Application(appObj.getString("id").replace("application_", ""),
            appObj.getString("user"), appObj.getString("name"),
            appObj.getString("applicationType"), appObj.getString("queue"),
            appObj.getLong("progress") + "%", TimeUtils.readableTime(appObj.getLong("elapsedTime")),
            appObj.getLong("allocatedMB"), appObj.getInt("allocatedVCores"),
            appObj.getInt("runningContainers"), appObj.getString("trackingUI"), appObj.getString("trackingUrl"),appObj.getString("diagnostics"))
        }
      }
    } catch {
      case e: Exception => logger.debug("Unable to find Application with id: " + normAppId, e)
    }
    if (result == null)
      System.err.println("Unable to find Application with id: " + normAppId)
    result
  }

  def loadRestfulAPI(url: String) = {
    urlLoader(url)
  }

  def normalizeId(id: String) = {
    require(id != null)
    if (!id.startsWith("application_")) {
      if (!id.startsWith("job_"))
        "application_" + id
      else
        id.replace("job_", "application_")
    } else {
      id
    }
  }
}

redpajama_set_name: RedPajamaGithub


The CKNJ understands the importance of education in building a strong and vibrant community, and their Bursary sub-committee helps young people to achieve their academic goals and further themselves in their chosen career paths.
The committee annually helps students studying KwaZulu-Natal with tertiary education by providing bursaries and loans, generously funded by bequests and trusts within the community. The CKNJ is proud to continue to play a part in building tomorrow's team of leaders.
For more information, contact the CKNJ office on 031 335 4452.


text:
Q: Reverse engineer: How do I remove the black plastic that hides the ics? I am hacking a circuit and it has this black plastic thing (see picture below) that hides part of the circuit.

How can I remove them to see what is inside?
What they are for? I think they are for chips that have no packaging, is this right?
What the real name of this?
Thanks for your help.

A: This is known as Chip-On-Board (COB) technology, the black material is epoxy resin, it is the same as the black material on ICs. Note than the bonding wires encased in the resin are very thin and fragile. COB technology is sometimes used to prevent reverse engineering.
This YouTube video demonstrates a process for removing the resin packaging on ICs using a hotplate, nitric acid, acetone, and a rotary tool.
This video YouTube video demonstrates a simpler (but more destructive) method for removing the resin from a COB, using just a heat-gun and a hobby knife. This method destroys the bonding wires.
And here's a related question, with more information about COBs: What kind of components are black blobs on a PCB?

A: Red fuming nitric acid is supposedly the stuff to use. It's very nasty.

redpajama_set_name: RedPajamaStackExchange


Discover nice offers on eBay for Wicker Chair in Chairs. Store with confidence. Store for indoor wicker chair cushions on-line at Goal. Free transport on purchases over $35 and save 5% every single day together with your Goal REDcard. Store for wicker white chair on-line at Goal. Free transport on purchases over $35 and save 5% every single day together with your Goal REDcard. Wicker Paradise sells out of doors wicker furnishings units, together with brown wicker patio furnishings and a beautiful out of doors wicker daybed. For the most effective Outdoor Wicker Furnishings, take a look at the vary at United Home Furnishings. We inventory Luxurious Outdoor Wicker Furnishings to swimsuit any dwelling. Wicker is a form of furnishings woven from any one in all quite a lot of cane-like supplies, together with rattan, willow, reed and bamboo. As such, it's not an precise materials .
Premium high quality Indoor Rattan and Wicker furnishings units at discounted costs. Discover the most effective indoor sunroom and patio furnishings at assured low costs. High quality aluminum framed wicker furnishings and rattan furnishings. Take pleasure in unique designs and nice values. White wicker furnishings and Patio Furnishings obtainable! Wicker paradise has high quality wicker furnishings for indoor or out of doors use. Outdoor wicker furnishings is resilient and exquisite. Select trendy wicker furnishings, or browse That includes an intricate woven design for energy and sturdiness, this simplistic wicker chair is completed in a pure colourway with sturdy gentle washed legs .


text:
package org.infinispan.tutorial.simple.remote.counter;

import org.infinispan.client.hotrod.RemoteCacheManager;
import org.infinispan.client.hotrod.RemoteCounterManagerFactory;
import org.infinispan.counter.api.CounterConfiguration;
import org.infinispan.counter.api.CounterManager;
import org.infinispan.counter.api.CounterType;
import org.infinispan.counter.api.StrongCounter;
import org.infinispan.counter.api.WeakCounter;
import org.infinispan.tutorial.simple.connect.Infinispan;

/**
 * Remote Counter simple tutorial.
 * <p>
 * Remote counters are available as of Infinispan version 9.2.
 *
 * Infinispan Server includes a default property realm that requires
 * authentication. Create some credentials before you run this tutorial.
 *
 * @author Pedro Ruivo
 */
public class InfinispanRemoteCounter {

   public static void main(String[] args) throws Exception {
      // Connect to the server
      RemoteCacheManager cacheManager = Infinispan.connect();

      // Retrieve the CounterManager from the CacheManager. Each CacheManager has it own CounterManager
      CounterManager counterManager = RemoteCounterManagerFactory.asCounterManager(cacheManager);

      // Create 3 counters.
      // The first counter is bounded to 10 (upper-bound).
      counterManager.defineCounter("counter-1", CounterConfiguration.builder(CounterType.BOUNDED_STRONG)
            .upperBound(10)
            .initialValue(1)
            .build());

      // The second counter is unbounded
      counterManager.defineCounter("counter-2", CounterConfiguration.builder(CounterType.UNBOUNDED_STRONG)
            .initialValue(2)
            .build());
      // And finally, the third counter is a weak counter.
      counterManager.defineCounter("counter-3", CounterConfiguration.builder(CounterType.WEAK)
            .initialValue(3)
            .build());

      // StrongCounter provides the higher consistency. Its value is known during the increment/decrement and it may be bounded.
      // Bounded counters are aimed for uses cases where a limit is needed.
      StrongCounter counter1 = counterManager.getStrongCounter("counter-1");
      // All methods returns a CompletableFuture. So you can do other work while the counter value is being computed.
      counter1.getValue().thenAccept(value -> System.out.println("Counter-1 initial value is " + value)).get();

      // Try to add more than the upper-bound
      counter1.addAndGet(10).handle((value, throwable) -> {
         // Value is null since the counter is bounded and we can add 10 to it.
         System.out.println("Counter-1 Exception is " + throwable.getMessage());
         return 0;
      }).get();

      // Check the counter value. It should be the upper-bound (10)
      counter1.getValue().thenAccept(value -> System.out.println("Counter-1 value is " + value)).get();

      //Decrement the value. Should be 9.
      counter1.decrementAndGet().handle((value, throwable) -> {
         // No exception this time.
         System.out.println("Counter-1 new value is " + value);
         return value;
      }).get();

      // Similar to counter-1, counter-2 is a strong counter but it is unbounded. It will never throw the CounterOutOfBoundsException
      StrongCounter counter2 = counterManager.getStrongCounter("counter-2");

      // All counters allow a listener to be registered.
      // The handle can be used to remove the listener
      counter2.addListener(event -> System.out
            .println("Counter-2 event: oldValue=" + event.getOldValue() + " newValue=" + event.getNewValue()));

      // Adding MAX_VALUE won't throws an exception. But the all the increments won't have any effect since we can store
      //any value larger the MAX_VALUE
      counter2.addAndGet(Long.MAX_VALUE).thenAccept(aLong -> System.out.println("Counter-2 value is " + aLong)).get();

      // Conditional operations are allowed in strong counters
      counter2.compareAndSet(Long.MAX_VALUE, 0)
            .thenAccept(aBoolean -> System.out.println("Counter-2 CAS result is " + aBoolean)).get();
      counter2.getValue().thenAccept(value -> System.out.println("Counter-2 value is " + value)).get();

      // Reset the counter to its initial value (2)
      counter2.reset().get();
      counter2.getValue().thenAccept(value -> System.out.println("Counter-2 initial value is " + value)).get();

      // Retrieve counter-3
      WeakCounter counter3 = counterManager.getWeakCounter("counter-3");
      // Weak counter doesn't have its value available during updates. This makes the increment faster than the StrongCounter
      // Its value is computed lazily and stored locally.
      // Its main use case is for uses-case where faster increments are needed.
      counter3.add(5).thenAccept(aVoid -> System.out.println("Adding 5 to counter-3 completed!")).get();

      // Check the counter value.
      System.out.println("Counter-3 value is " + counter3.getValue());

      // Stop the cache manager and release all resources
      cacheManager.stop();
   }

}


text:
layout: page
title: 'Programming languages'
date:   2014-10-26 12:00:00
---

* [Elm-lang](http://elm-lang.org/)
* [Elm by Example](http://elm-by-example.org)
* [Phoenix with Elm](http://www.cultivatehq.com/posts/phoenix-elm-1/),
  [Part 2](http://www.cultivatehq.com/posts/phoenix-elm-2/)

* [Getting started with Elm](http://pragmaticstudio.com/blog/2014/12/19/getting-started-with-elm)
* [Learning FP the hard way: Experiences on the Elm language](https://gist.github.com/ohanhi/0d3d83cf3f0d7bbea9db)


You are visiting the placeholder page for Rachel Carter. This page is here because someone used our placeholder utility to look for Rachel Carter. We created this page automatically in hopes Rachel Carter would find it. If you are not Rachel Carter, but are an alumni of Marble Falls High School, register on this site for free now.


Ready to Declare your Major or Minor?
Students are able to declare their major or minor in the department. Each department has specific instructions on how to declare. Click here to find out the instructions for your intended major or minor department!
Click on the links below to view departmental websites. Major and minor requirements can be found on the University Bulletin.