1,721,044 research outputs found
Going Beyond Counting First Authors in Author Co-citation Analysis
The present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation
counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings
are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that
only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into
account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed
Recommended from our members
A comparison of the theoretical and practical components of the US and German higher-education systems; what we can learn from the German approach to better prepare our students for ever-changing technologies
The curriculum of technical degrees at higher education institutions in the United States needs to continuously adapt to ever changing technologies. One way to accomplish this is to adopt a more dynamic approach that separates the practical and theoretical components of the university education, and where the student concentrates on each part. An example is the German system, where the students learn about the theory through classes at the university and learn the practical application of the theory through industrial internships. I propose that universities concentrate on theory in the classroom while requiring each student participate in several semester-long internships in the industry to gain appreciation of the practical application of the theory. This, coupled with more industry involvement curriculum ensures that students will not learn out-dated material, and will make the US more competitive in the world market
Variations on the Author
“Variations on the Author” discusses two of Eduardo Coutinho’s recent films (Um Dia na Vida, from 2010, and Últimas Conversas, posthumously released in 2015) and their contribution to the general question of documentary authorship. The director’s filmography is characterized by a consistent yet self-effacing form of authorial self-inscription: Coutinho often features as an interviewer that rather than express opinions propels discourses; an interviewer that is good at listening. This mode of self-inscription characterizes him as an author who is not expressive but who is nonetheless markedly present on the screen. In Um Dia na Vida, however, Coutinho is completely absent form the image, while Últimas Conversas, on the contrary, includes a confessional prologue that moves the director from the margins to the center of his films. This article examines the ways in which these works stand out in the filmography of a director who offers new insights into the notion of cinematic authorship
Appropriate Similarity Measures for Author Cocitation Analysis
We provide a number of new insights into the methodological discussion about author cocitation analysis. We first argue that the use of the Pearson correlation for measuring the similarity between authors’ cocitation profiles is not very satisfactory. We then discuss what kind of similarity measures may be used as an alternative to the Pearson correlation. We consider three similarity measures in particular. One is the well-known cosine. The other two similarity measures have not been used before in the bibliometric literature. Finally, we show by means of an example that our findings have a high practical relevance.information science;Pearson correlation;cosine;similarity measure;author cocitation analysis
Recommended from our members
A tool for evaluating programming style
Programming style is a highly individualistic and important part of programming. Yet, there is no general agreement on the definition of programming style nor even the qualities that make up programming style. Existing automated programming style analyzer programs either produce a battery of numbers, leaving the weight and/or importance of each to the user, or output a score between zero and one hundred based on subjective program characteristics. No attempt is made to give non-technical feedback to the user.
This project report defines programming style principles used in a prototype automated programming style analyzer. This automated tool provides meaningful descriptive non-technical comments about programming style deficiencies in the user's Pascal source program.
Although The Prototype Automated Program Style Analyzer for Pascal, called "Style", was designed for MacPascal and LightSpeed Pascal. the concepts and techniques are extendible to other programming languages and programming environments
Recommended from our members
An investigation of the on-line debugging process of expert and novice student programmers
Debugging, the process of locating and correcting errors in a computer program, is a common programming task that is not well understood. Of the several debugging studies reported in the literature, most compared the performance differences between expert and novice programmers by measuring their debug time and the number of errors found and corrected; a few provided information about their debugging process. This dissertation investigates the on-line debugging process of expert and novice student programmers by means of protocol analysis. This dissertation describes three debugging experimentations that were conducted to understand the debugging process and were used as the basis for a cognitive model of subjects' on-line debugging behavior. In the three experiments subjects debugged a defective Pascal program seeded with several errors on a Apple Macintosh computer. Some of the major results obtained through this research work are summarized below: Experts employed a comprehension approach in which they first attempted to understand the program and then used this knowledge for finding the bugs. Intermediates and novices employed an isolation approach in which they immediately attempted to identify candidate bug locations by searching the output for clues, recalling similar bugs, and testing program states. Experts corrected multiple errors before verifying the corrections while novices corrected and verified single errors. Novices corrected the semantic errors first and then the logic errors while experts corrected both semantic and logic errors at the same time. Experts were more efficient in correcting all of the errors, modified fewer statements, and did not introduce more errors. Novices did not correct all of the errors, made very extensive modifications and introduced many new errors. Program understanding played a key role in locating and correcting logic errors. Experts' superiority in locating and correcting errors was due to their better (a) overall understanding of the program, (b) ability to identify program segment containing the error, and (c) ability to select a correct error hypothesis
Recommended from our members
Comparison of several sorting algorithms designed for nearly sorted lists
Quickersort, Straight Insertion Sort, Mehlhorn's AVL-tree Sorting Algorithm and Cook's new sorting algorithm are compared on nearly and nedium sorted lists. The ratio of the minimum number of list elements that must be removed so that the remaining portion of the list is in order to the size of the list is our measure. Tests on randomly generated lists of various combinations of list length and small and medium sortedness ratios indicate that Straight Insertion Sort is best for small or very nearly sorted lists, Cook's new sorting algorithm is best for nearly sorted lists and Quickersort is best otherwise. We also modify the AVL-tree Sorting Algorithm and it performs better than Quickersort on medium sorted lists
Recommended from our members
Critique : a prototype style critic for FORTRAN
Programming style is important for program understanding in programming tasks such as maintenance. testing, and debugging. The goal of programming style is to improve the readability of the source program without adversely affecting its performance.
Critique is a FORTRAN source program style critic which analyzes the source program and outputs meaningful, non-technical messages about its style. Unlike most other automatic style analyzer/graders, Critique does not assign a style score to a program or output counts of various program characteristics. Critique is designed to point out deficiencies and to offer the user suggestions about improving the style of the program.
Critique is written in C and runs under UNIX. It uses the programming tools Lex and Sed
Recommended from our members
The cloze procedure : a proposal for a measure of program comprehension
- …
