Myosides seriehispidus Roelofs : an Asian weevil new to the United States (Coleoptera, Curculionidae)

Myosides seriehispidus Roelofs, a small cryptic broadnosed weevil from Japan, is reported as established in the eastern U.S. since at least 1973. This nocturnal weevil has been collected most often from leaflitter using berleses. The genus and species are redescribed and placement in Kissinger's key to genera of North American weevils is indicated. Dorsal and lateral habitus photographs of this species are included

Interdisciplinary Legal Scholarship in Search of a Paradigm

A “mature” science, according to Thomas Kuhn, can afford to be uncritical. It has finally answered to its practitioners\u27 satisfaction the fundamental, foundational questions of their field. It finally rests (“for a time,” at least) on an established scientific achievement that epitomizes the accomplished, collective wisdom of an age and defines the terms, conditions, directions, and limits of further refining research. With this “paradigm” in place, researchers are spared the incessant and distracting reexamination of first principles, the extravagant costs of intellectual retooling; they can proceed with confidence, effectiveness, and efficiency to do what they do best: articulating and specifying the received paradigm in more depth and detail, extending and applying it to new areas of interest. Because a paradigm “provides rules that tell the practitioner of a mature specialty what both the world and his science are like,” the practitioner “can concentrate with assurance upon the esoteric problems that these rules and existing knowledge define for him.” Postmodern legal theory appropriates and assimilates Kuhn\u27s insights in ways and to an extent that have not, I think, yet been fully recognized. In describing the development of legal scholarship in Kuhnian terms, I am thus merely elaborating assumptions integral to contemporary intellectual discourse. In particular, interdisciplinary legal scholarship regularly proceeds on the assumption that it possesses a stable, accepted, and uncontroversial paradigm for further research-in other words, that it constitutes a “mature science.” But beneath the institutional trappings of interdisciplinary legal scholarship I detect not a scholarly tradition that has finally resolved to general acclaim all its basic, foundational, methodological problems, but rather one that has never really confronted them. As a result, the attempt to apply the supposed paradigm of interdisciplinary legal scholarship to its subject matter reveals significant “anomalies” in the application. In what follows I shall first analyze and discuss these anomalies and then consider in some detail a specific example of contemporary interdisciplinary legal scholarship

Visualizing Fantasy Fiction: Design of a Class in Digital Scholarship and Visualization, including Research, Organization and Digital Visualization, that Does Not Require Programming or IT support

This paper outlines a course to integrate digital visualizations into undergraduate research. These visualizations will include mapping and timelines of events, and the ability to hyperlink the events, characters, and story lines in a fantasy fiction story such as Lord of the Rings or A Game of Thrones. The digital scholarship will involve the methodology for collecting, organizing, and representing the data for the visualizations. The topic for the visualizations in this paper is fantasy fiction; however the methods to develop these visualizations will be applicable to many academic disciplines, including the humanities and social sciences. The paper outlines the justification for this class, the appropriate audience for this class, and the tools needed. Types of projects and homework assignments to implement the visualizations are suggested. It concludes with a syllabus outlining a typical schedule for this class

Programming Safety Tips: Why You Should Use Immutable Objects or How to create programs with bugs that can never be found or fixed.

Program safety deals with how to make programs as error free as possible. The hardest errors in a program for a programmer to find are often errors in using memory. There are two reasons for this. The first is that errors in accessing memory almost never show problems in the proximate area of the program where the error is made. The error has no apparent impact when it is made, but often causes catastrophic results to occur much later in the program, in areas of the program unrelated to memory error that caused it. The second reason memory errors are so difficult to find is that the working of memory is often poorly understood by most novice, and many professional, programmers. This makes it difficult for many programmers to even understand why an action causes the error. This article will show an example of a program error that can easily occur when memory access is poorly understood. This leads to program errors that are very easy to fix when they are found, but extremely difficult to find. The article will then explain how many memory errors can be easily avoided by following the very simple rule, “Make all object immutable unless there is a good reason to make them mutable”, and why immutable objects are an essential tool in good, safe programming practice

Banking Crises Yesterday and Today

Provides an overview of the history of banking crises, as distinguished from financial crises, and the role of microeconomic and regulatory policy, both as causes of and as responses to the crises. Examines how politics can limit improved regulation

Digital Scholarship: Applying Digital Tools to Undergraduate Student Research Papers, A Proposal for a Freshman Seminar. Part I: Definition of Student Research Methodology

There are many digital tools that can be used for research and presentation in nearly every college discipline, including the social sciences and humanities. These tools hold the promise to radically change both the process and products of research. But in their application these tools have failed miserably to live up to their promise. This paper is based on the hypothesis that one reason these tools do reach their potential is that there is no systemic way to include them in research process, resulting in the tools being seen as ways to improve the final research product. This results in the tools becoming just an added on kludge, and leading researchers to the conclude that they are hard to use, full of bugs and other problems, and that they do not bring a lot of value to the research. This paper is an attempt to address this problem of including digital tools in a research process. It is part of a series of papers proposing a systematic methodology for including digital tools in a research process. This paper is the first, and outlines a methodology for the research process that allows the application of digital tools to a small area, undergraduate student research papers. It will outline a development process that will systematize the steps in the research process. These steps will then be used to classify the digital tools, and show how they can be applied to the research process. The final product of this paper will be a process methodology for creating student research papers to be used in a class to be run as a freshman seminar. The students will be taught this research methodology, and be led through the development of a research paper using the steps defined in this methodology. The steps in the process being enhanced using appropriate digital tools applicable to each step in the methodology. The ability of the students to do research using the research methodology and digital tools will be measured by the degree of success the students have in completing a humanities/social science research product as part of the class. The students will be followed in a longitudinal study by asking them to complete a short survey at the end of each year of their undergraduate education

Implementing a One Address CPU in Logisim

Most computer users have an incorrect, but useful, cognitive metaphor for computers in which the user says (or types or clicks) something and a mystical, almost intelligent or magical, behavior happens. It is not a stretch to describe computer users as believing computers follow the laws of magic, where some magic incantation is entered, and the computer responds with an expected, but magical, behavior. This magic computer does not actually exist. In reality computer are machines, and every action a computer performs reduces to a set of mechanical operations. In fact the first complete definition of a working computer was a mechanical machine designed by Charles Babbage in 1834, and would have run on steam power. Probably the biggest success of Computer Science (CS) in the 20th century was the development of abstractions that hide the mechanical nature of computers. The fact that average people use computers without ever considering that they are mechanistic is a triumph of CS designers. This purpose of this monograph is to break the abstract understanding of a computer, and to explain a computer’s behavior in completely in mechanistic terms. It will deal specifically with the Central Processing Unit (CPU) of the computer, as this is where the magic happens. All other parts of a computer can be seen as just providing information for the CPU to operate on. This monograph will deal with a specific type of CPU, a one-address CPU, and will explain this CPU using only standard gates, specifically AND, OR, NOT, NAND and XOR gates, and 4 basic Integrated Circuits (ICs), the Decoder, Multiplexer, Adder, and Flip Flop. All of these gates and components can be described as mechanical transformations of input data to output data, and the overall CPU can then be seen as a mechanical device.https://cupola.gettysburg.edu/oer/1002/thumbnail.jp