Insula Activation and What it May Tell Us About Food Motivation in Anorexia Nervosa: A Systematic Literature Review

• Anorexia nervosa (AN) is a severe psychiatric disorder characterized by recurrent refusal of caloric intake, resulting in emaciation. • Identifying whether neural networks that process food-related stimuli are affected in AN is important for understanding the biological basis of this illness, particularly severe food restriction. • The insular cortex is a key area that has been implicated; this brain region is associated with interoceptive awareness and gustation

Calibration of a resistance thermometer down to 0.04 degrees K

Method for calibrating germanium-resistance thermometers in cryostats between 0.4 degrees K and 4 degrees K involves extrapolating the specific heat of a simple metal to low temperatures. This method is used when a magnetic thermometer is not available

Second CLIPS Conference Proceedings, volume 1

Topics covered at the 2nd CLIPS Conference held at the Johnson Space Center, September 23-25, 1991 are given. Topics include rule groupings, fault detection using expert systems, decision making using expert systems, knowledge representation, computer aided design and debugging expert systems

COMPASS: An Ada based scheduler

COMPASS is a generic scheduling system developed by McDonnell Douglas and funded by the Software Technology Branch of NASA Johnson Space Center. The motivation behind COMPASS is to illustrate scheduling technology and provide a basis from which custom scheduling systems can be built. COMPASS was written in Ada to promote readability and to conform to DOD standards. COMPASS has some unique characteristics that distinguishes it from commercial products. This paper discusses these characteristics and uses them to illustrate some differences between scheduling tools

Knowledge-based system V and V in the Space Station Freedom program

Knowledge Based Systems (KBS's) are expected to be heavily used in the Space Station Freedom Program (SSFP). Although SSFP Verification and Validation (V&V) requirements are based on the latest state-of-the-practice in software engineering technology, they may be insufficient for Knowledge Based Systems (KBS's); it is widely stated that there are differences in both approach and execution between KBS V&V and conventional software V&V. In order to better understand this issue, we have surveyed and/or interviewed developers from sixty expert system projects in order to understand the differences and difficulties in KBS V&V. We have used this survey results to analyze the SSFP V&V requirements for conventional software in order to determine which specific requirements are inappropriate for KBS V&V and why they are inappropriate. Further work will result in a set of recommendations that can be used either as guidelines for applying conventional software V&V requirements to KBS's or as modifications to extend the existing SSFP conventional software V&V requirements to include KBS requirements. The results of this work are significant to many projects, in addition to SSFP, which will involve KBS's

COMPASS: A general purpose computer aided scheduling tool

COMPASS is a generic scheduling system developed by McDonnell Douglas under the direction of the Software Technology Branch at JSC. COMPASS is intended to illustrate the latest advances in scheduling technology and provide a basis from which custom scheduling systems can be built. COMPASS was written in Ada to promote readability and to conform to potential NASA Space Station Freedom standards. COMPASS has some unique characteristics that distinguishes it from commercial products. These characteristics are discussed and used to illustrate some differences between scheduling tools

Approaches to the verification of rule-based expert systems

Expert systems are a highly useful spinoff of artificial intelligence research. One major stumbling block to extended use of expert systems is the lack of well-defined verification and validation (V and V) methodologies. Since expert systems are computer programs, the definitions of verification and validation from conventional software are applicable. The primary difficulty with expert systems is the use of development methodologies which do not support effective V and V. If proper techniques are used to document requirements, V and V of rule-based expert systems is possible, and may be easier than with conventional code. For NASA applications, the flight technique panels used in previous programs should provide an excellent way to verify the rules used in expert systems. There are, however, some inherent differences in expert systems that will affect V and V considerations

Verification issues for rule-based expert systems

Verification and validation of expert systems is very important for the future success of this technology. Software will never be used in non-trivial applications unless the program developers can assure both users and managers that the software is reliable and generally free from error. Therefore, verification and validation of expert systems must be done. The primary hindrance to effective verification and validation is the use of methodologies which do not produce testable requirements. An extension of the flight technique panels used in previous NASA programs should provide both documented requirements and very high levels of verification for expert systems

An expert system development methodology which supports verification and validation

Expert systems have demonstrated commercial viability in a wide range of applications, but still face some obstacles to widespread use. A major stumbling block is the lack of well defined verification and validation (V and V) techniques. The primary difficulty with expert system V and V is the use of development methodologies which do not support V and V. As with conventional code, the key to effective V and V is the development methodology. An expert system development methodology is described which is based upon a panel review approach, that allows input from all parties concerned with the expert system

The Blackstar: Persona, Narrative, and Late Style in the Mourning of David Bowie on Reddit

This article considers how David Bowie’s last persona, The Blackstar, framed his death through the narratives of mourning it provoked on the social media site Reddit. The official narrative of death, through the media, and the unofficial narrative of death, through the fan, can contradict each other, with fans usually bringing their own lived experiences to the mourning process. David Bowie is a performer of personas. While Bowie died in 2016, his personas have continued to live on, informing his legacy, his work, and his death reception. Through the concepts of persona, narrative, authenticity, late style, and mourning, this article finds that Bowie’s Blackstar persona actively constructs fan’s interaction with Bowie’s death. Instead of separate and contradicting narratives, this article finds that users on Reddit underpin and extend the official narrative of his death, using Bowie’s persona as a way to construct and establish their own mourning. As such, Bowie’s last persona is further entrenched as one of authentic mourning, of a genius constructing his own passing. With these narratives, fans construct their own personas, informing how they too would like to die: artistically and with grace