216,321 research outputs found
A Follow-up Study of Doctor of Education Students at Drake University
No full textix, 208 leaves. Advisor: Hilda L. WilliamsProblem: Because decision-makers must choose between many competing alternatives, astute administrators will use findings from periodic
evaluations to help make suitable decisions regarding the policy and direction of an institution. This thesis is an evaluation, from the students' perspective, of the doctor of education degree offered by Drake University's School of Education.
The study has two purposes: (1) to define the demographic characteristics of the doctoral population to enable Drake to better serve the needs of the doctoral population; and (2) to ascertain from the students' perspective if Drake has realized the goals for the program.
Procedure: The population of this study are those students who were admitted to and enrolled in the doctoral core for an Ed.D. degree at Drake
University from the years 1986 to 1988. Twenty-seven students were interviewed using a combination mail survey/telephone interview
methodology.
Findings: The findings indicate the doctoral students were generally satisfied with the program. Most of the dissatisfaction was found in the major specific and class specific areas. It was found that progress toward the doctoral degree ceases at the dissertation stage. It was found that structure of the program is influencial when choosing a school to attend. It was found that Drake graduates are an integral part of the community as they participate in leadership activities. It is found that research endeavors of the students is lower than desired. It is found that students did not exhibit significant lifestyle changes after completing the doctoral
core. It is found that the students tolerate the comprehensive exam process but did not view it as valuable and suggested many nontraditional
approaches they felt would be of greater value.
Conclusions: This study contributes to a limited body of research on outcomes of doctoral education. Further, the methodology used may have contributed to the investigation's ability to obtain richer, and more detailed information in that a mail survey/phone interview combined methodology was used
X-Ray Machine Tests and X-Ray Experiments for Undergraduate Physics Laboratories
No full text111 leaves. Advisor: Dr. Harry DowningThe Problem. In the spring of 1977, the Drake University Physics Department acquired an X-ray machine. There was a need to convert this device
to an educational tool so it could be used on an undergraduate level.
Procedure. First, the machine was tested to find its range limits. Secondly, numerous experiments were designed to use the X-ray machine.
Findings. The X-ray machine has a wide range of uses and can be used on an undergraduate level for many laboratories. Dosimeters and film are both very useful tools in the detection of radiation; however, considering each experiment designed, one method of detection proved more useful than the other for that given experiment.
Conclusions. The Drake University X-ray machine be extremely helpful for undergraduate students in the life sciences. The machine will provide many new experiments not available before and will supplement both physics and life science courses within the Drake University curriculum.
Recommendations. Recommendations are that the Drake University X-ray machine be used in the future for undergraduate physics laboratories for the life sciences. Also, it is recommended that the laboratories designed be used by junior-senior physics level students as introductory experiments
to X-rays and X-ray related phenomena
Painting by Will N. Drake of the old Plaza Church, ca.1905
No full textPhotograph of a painting by Will N. Drake of the old Plaza Church, ca.1905. The painting depicts a street scene in front of the Plaza Church: In the foreground a cart vendor in dark clothing is pictured. Closer to the church itself are several horse-drawn carriages, drawn both by dark and light horses. Between both the vendor and the carriages, towards the center of the image, a woman with a basket holds the hand of a child to her left. They are followed by what appears to be a dog. Short palms line the side of the church
A Study of the Feasibility of Reorganization of the Collins-Maxwell School Districts
No full text72 leaves. Advisor: Dr.a Charles RowleyThe problem. Since the 1968 study by Drake University, the Department of School Administration, College of Education, and the 1970 survey by Richard Dexter, no action
has been taken to reorganize any of the five school districts in East Story County which includes the Collins and Maxwell School Districts. The purpose of this study was to
determine the feasibility of a Collins-Maxwell reorganization.
Procedure. A questionnaire was mailed to the board members of the Collins and Maxwell School Districts and an interview was held with their respective superintendents.
Findings. Enrollments are decreasing in the Collins and Maxwell School Districts according to projected enrollments. The curriculums of both districts stress academics and do not offer enough units of credits in order to provide students with a comprehensive education. A majority of the board members indicated that they thought reorganization is
needed and that it would benefit the students' possibility of a better education.
Conclusions. Enrollments in the Collins and Maxwell School Districts will continue to decrease. A reorganization of the Collins and Maxwell Schools would create a substantial
increase in the amount of units of credits the
students could be offered, therefore providing a comprehensive education.
Recommendations. Each district must face the reality of declining enrollment and the effect it will have on its educational program. Reorganization should be considered as
a means to improve educational programs and not to cut costs. The Collins and Maxwell School Districts should reorganize in the very near future with consideration given to the
possibility of including a third district
Smile More: A Subcultural Analysis of the Anchor/Consultant Relationship in Local Television News Operations
No full textiii, 209 leaves. Advisor: Michael CheneyThe problem: Few television stations in the United States remain untouched by the influence of news consultants. To become a news anchor for a local television station, a journalist is likely to
receive specialized training from these consultants. The author will analyze the relationship between anchors and consultants
within the framework of an occupational subculture to better understand that relationship,
Procedure: The author uses qualitative research to explore the situation described; specifically, a series of structured interviews with randomly chosen American television news anchors and several representative consultants. Contents of the interviews are analyzed within an occupational subculture paradigm.
Findings: As subcultural outsiders, station consultants can cause irritation and anxiety for news anchors, but the skills they teach are valued by the modern television industry. Some anchors
may be willing to compromise traditional news culture values to survive in their careers, but this compromise may be offset by new perceptions of their social responsibility.
Conclusion: While the skills taught by a consultant may be valued within the television news subculture, his or her role as an outsider
can contribute negatively to the subculture. The hypothesis drawn from qualitative analysis is as follows: If journalistic norms constitute a strong subculture, then those who receive coaching from within the subculture will report a more positive
experience than those who are coached by consultants.
Recommendations: Quantitative research can now be pursued to test the preceding hypothesis
Problems and Implications of Outlawing Aggressive War : An Examination of the Charter Resulting from the London Conference, August 8, 1945
No full text85 leaves. Advisor: C. Walter ClarkThe problem. The International Military Tribunal
which tried Nazi Germany's leaders after the Second World War was predicated on the Allied nations' signing of the London Charter, which provided the law and procedures for the
Nuremberg war-crime trials. The Charter is something of a landmark, both as a substantive code outlawing crimes against the international community and as an instrument establishing
a procedure for prosecution and trial of such crimes before an international court. The focus of this paper will be on the category in the charter that deals with crimes against peace, which consist of conspiring to wage, initiating, or waging a war of aggression.
Procedure. Examination of relevant documents and
written analyses, which are available in the Drake Cowles and Law School libraries.
Conclusions. At the London Conference aggressive
warfare was declared to be an international crime. Whether the conferees were codifying a principle generally accepted internationally or creating ex post facto legislation remains
a question of substantive process.
The principle of outlawing aggressive warfare was incorporated into the charter of the United Nations. It appears doubtful that the United Nations can enforce this principle based on the considerations that the United Nations has been awarded weak coercive powers; the superpowers
are regionally aligned and have established the
practice of "collective self-defense" within their respective regions; any consensual definition of a nation-state is
lacking, especially with regard to emerging nations; and, the nation-states or aspiring nation-states have the universally confirmed right to engage in wars of self-determination.
Overtime if world organization becomes functionally oriented, this may provide the key to reordering the nationstate system and, as a consequence rather than a declared goal, end aggressive warfare
ropensci/drake: drake transformed
No full textVersion 7.0.0
Breaking changes
<ul>
<li>The enhancements that increase cache access speed also invalidate targets in old projects. Workflows built with drake <= 6.2.1 will need to run from scratch again.</li>
<li>In <code>drake</code> plans, the <code>command</code> and <code>trigger</code> columns are now lists of language objects instead of character vectors. <code>make()</code> and friends still work if you have character columns, but the default output of <code>drake_plan()</code> has changed to this new format.</li>
<li>All parallel backends (<code>parallelism</code> argument of <code>make()</code>) except "clustermq" and "future" are removed. A new "loop" backend covers local serial execution.</li>
<li>A large amount of deprecated functionality is now defunct, including several functions (<code>built()</code>, <code>find_project()</code>, <code>imported()</code>, and <code>parallel_stages()</code>; <a href="https://github.com/ropensci/drake/issues/564">full list here</a>) and the single-quoted file API.</li>
<li>Set the default value of <code>lock_envir</code> to <code>TRUE</code> in <code>make()</code> and <code>drake_config()</code>. So <code>make()</code> will automatically quit in error if the act of building a target tries to change upstream dependencies.</li>
<li><code>make()</code> no longer returns a value. Users will need to call <code>drake_config()</code> separately to get the old return value of <code>make()</code>.</li>
<li>Require the <code>jobs</code> argument to be of length 1 (<code>make()</code> and <code>drake_config()</code>). To parallelize the imports and other preprocessing steps, use <code>jobs_preprocess</code>, also of length 1.</li>
<li>Get rid of the "kernels" <code>storr</code> namespace. As a result, <code>drake</code> is faster, but users will no longer be able to load imported functions using <code>loadd()</code> or <code>readd()</code>.</li>
<li>In <code>target()</code>, users must now explicitly name all the arguments except <code>command</code>, e.g. <code>target(f(x), trigger = trigger(condition = TRUE))</code> instead of <code>target(f(x), trigger(condition = TRUE))</code>.</li>
<li>Fail right away in <code>bind_plans()</code> when the result has duplicated target names. This makes <code>drake</code>'s API more predictable and helps users catch malformed workflows earlier.</li>
<li><code>loadd()</code> only loads targets listed in the plan. It no longer loads imports or file hashes.</li>
<li>The return values of <code>progress()</code>, <code>deps_code()</code>, <code>deps_target()</code>, and <code>predict_workers()</code> are now data frames.</li>
<li>Change the default value of <code>hover</code> to <code>FALSE</code> in visualization functions. Improves speed.</li>
</ul>
Bug fixes
<ul>
<li>Allow <code>bind_plans()</code> to work with lists of plans (<code>bind_plans(list(plan1, plan2))</code> was returning <code>NULL</code> in <code>drake</code> 6.2.0 and 6.2.1).</li>
<li>Ensure that <code>get_cache(path = "non/default/path", search = FALSE)</code> looks for the cache in <code>"non/default/path"</code> instead of <code>getwd()</code>.</li>
<li>Remove strict dependencies on package <code>tibble</code>.</li>
<li>Pass the correct data structure to <code>ensure_loaded()</code> in <code>meta.R</code> and <code>triggers.R</code> when ensuring the dependencies of the <code>condition</code> and <code>change</code> triggers are loaded.</li>
<li>Require a <code>config</code> argument to <code>drake_build()</code> and <code>loadd(deps = TRUE)</code>.</li>
</ul>
New features
<ul>
<li>Introduce a new experimental domain-specific language for generating large plans (#233). Details <a>here</a>.</li>
<li>Implement a <code>lock_envir</code> argument to safeguard reproducibility. See <a href="https://github.com/ropensci/drake/issues/615#issuecomment-447585359">this thread</a> for a demonstration of the problem solved by <code>make(lock_envir = TRUE)</code>. More discussion: #619, #620.</li>
<li>The new <code>from_plan()</code> function allows the users to reference custom plan columns from within commands. Changes to values in these columns columns do not invalidate targets.</li>
<li>Add a menu prompt (<a href="https://github.com/ropensci/drake/pull/762">https://github.com/ropensci/drake/pull/762</a>) to safeguard against <code>make()</code> pitfalls in interactive mode (<a href="https://github.com/ropensci/drake/issues/761">https://github.com/ropensci/drake/issues/761</a>). Appears once per session. Disable with <code>options(drake_make_menu = FALSE)</code>.</li>
<li>Add new API functions <code>r_make()</code>, <code>r_outdated()</code>, etc. to run <code>drake</code> functions more reproducibly in a clean session. See the help file of <code>r_make()</code> for details.</li>
<li><code>progress()</code> gains a <code>progress</code> argument for filtering results. For example, <code>progress(progress = "failed")</code> will report targets that failed.</li>
</ul>
Enhancements
<ul>
<li><strong>Large speed boost</strong>: move away from <code>storr</code>'s key mangling in favor of <code>drake</code>'s own encoding of file paths and namespaced functions for <code>storr</code> keys.</li>
<li>Exclude symbols <code>.</code>, <code>..</code>, and <code>.gitignore</code> from being target names (consequence of the above).</li>
<li>Use only one hash algorithm per <code>drake</code> cache, which the user can set with the <code>hash_algorithm</code> argument of <code>new_cache()</code>, <code>storr::storr_rds()</code>, and various other cache functions. Thus, the concepts of a "short hash algorithm" and "long hash algorithm" are deprecated, and the functions <code>long_hash()</code>, <code>short_hash()</code>, <code>default_long_hash_algo()</code>, <code>default_short_hash_algo()</code>, and <code>available_hash_algos()</code> are deprecated. Caches are still back-compatible with <code>drake</code> > 5.4.0 and <= 6.2.1.</li>
<li>Allow the <code>magrittr</code> dot symbol to appear in some commands sometimes.</li>
<li>Deprecate the <code>fetch_cache</code> argument in all functions.</li>
<li>Remove packages <code>DBI</code> and <code>RSQLite</code> from "Suggests".</li>
<li>Define a special <code>configeval <- new.env(parent = configenvir)</code> for storing built targets and evaluating commands in the plan. Now, <code>make()</code> no longer modifies the user's environment. This move is a long-overdue step toward purity.</li>
<li>Remove dependency on the <code>codetools</code> package.</li>
<li>Deprecate and remove the <code>session</code> argument of <code>make()</code> and <code>drake_config()</code>. Details: <a href="https://github.com/ropensci/drake/issues/623#issue-391894088">https://github.com/ropensci/drake/issues/623#issue-391894088</a>.</li>
<li>Deprecate the <code>graph</code> and <code>layout</code> arguments to <code>make()</code> and <code>drake_config()</code>. The change simplifies the internals, and memoization allows us to do this.</li>
<li>Warn the user if running <code>make()</code> in a subdirectory of the <code>drake</code> project root (determined by the location of the <code>.drake</code> folder in relation to the working directory).</li>
<li>In the code analysis, explicitly prohibit targets from being dependencies of imported functions.</li>
<li>Increase options for the <code>verbose</code> argument, including the option to print execution and total build times.</li>
<li>Separate the building of targets from the processing of imports. Imports are processed with rudimentary staged parallelism (<code>mclapply()</code> or <code>parLapply()</code>, depending on the operating system).</li>
<li>Ignore the imports when it comes to build times. Functions <code>build_times()</code>, <code>predict_runtime()</code>, etc. focus on only the targets.</li>
<li>Deprecate many API functions, including <code>plan_analyses()</code>, <code>plan_summaries()</code>, <code>analysis_wildcard()</code>, <code>cache_namespaces()</code>, <code>cache_path()</code>, <code>check_plan()</code>, <code>dataset_wildcard()</code>, <code>drake_meta()</code>, <code>drake_palette()</code>, <code>drake_tip()</code>, <code>recover_cache()</code>, <code>cleaned_namespaces()</code>, <code>target_namespaces()</code>, <code>read_drake_config()</code>, <code>read_drake_graph()</code>, and <code>read_drake_plan()</code>.</li>
<li>Deprecate <code>target()</code> as a user-side function. From now on, it should only be called from within <code>drake_plan()</code>.</li>
<li><code>drake_envir()</code> now throws an error, not a warning, if called in the incorrect context. Should be called only inside commands in the user's <code>drake</code> plan.</li>
<li>Replace <code>*expr*()</code> <code>rlang</code> functions with their <code>*quo*()</code> counterparts. We still keep <code>rlang::expr()</code> in the few places where we know the expressions need to be evaluated in <code>config$eval</code>.</li>
<li>The <code>prework</code> argument to <code>make()</code> and <code>drake_config()</code> can now be an expression (language object) or list of expressions. Character vectors are still acceptable.</li>
<li>At the end of <code>make()</code>, print messages about triggers etc. only if <code>verbose >= 2L</code>.</li>
<li>Deprecate and rename <code>in_progress()</code> to <code>running()</code>.</li>
<li>Deprecate and rename <code>knitr_deps()</code> to <code>deps_knitr()</code>.</li>
<li>Deprecate and rename <code>dependency_profile()</code> to <code>deps_profile()</code>.</li>
<li>Deprecate and rename <code>predict_load_balancing()</code> to <code>predict_workers()</code>.</li>
<li>Deprecate <code>this_cache()</code> and defer to <code>get_cache()</code> and <code>storr::storr_rds()</code> for simplicity.</li>
<li>Change the default value of <code>hover</code> to <code>FALSE</code> in visualization functions. Improves speed. Also a breaking change.</li>
<li>Deprecate <code>drake_cache_log_file()</code>. We recommend using <code>make()</code> with the <code>cache_log_file</code> argument to create the cache log. This way ensures that the log is always up to date with <code>make()</code> results.</li>
</ul>
Using Video Reporting as a Communications Modality for Federal Evaluation Reports
No full textvi, 90 leaves. Advisor: Howard TraxlerThe Problem. The problem studied was how the recipient of a training grant such as the Drake Rehabilitation Placement Specialist Program can best report its goals, activities, and achievements to a sponsoring federal agency. Traditionally, final reports have been made in writing. The study focused on whether a video reporting system could effectively convey both cognitive and affective information.
Procedure. A video reporting system was designed to serve the purposes of government reports. A video report about the Drake Placement Program using this design was produced. A second version combining the video report with a written summary was developed. The effectiveness of these experimental models was compared with that of the written report prepared by the program administrators. The participants in the study were thirty rehabilitation specialists from five rehabilitation state agencies involved in the assessment and funding of government grants. From this sample, three groups of ten were randomly selected. Group I viewed the video tape, Group II read the written report, and Group III viewed the video tape and read a summary report. A test was designed to determine the level of a viewer’s cognitive understanding of the program. A second instrument was designed to identify viewer attitudes toward the program. Subjects were pre-tested, presented one reporting model and given post-tests on cognitive understandings and attitudinal concepts.
Findings. Two analyses of variance were conducted. The first compared the mean changes of the three groups on the cognitive test. The null hypothesis, that there are no differences in comprehension of the project when presented in written form only, in video form only, or in a combination of video presentation and written summary, was accepted.
The second hypothesis, that there are no differences in a reviewer’s attitude toward a project when the report is presented in written form only, in video format only, or in a combination of video report and written summary, was rejected at the .05 level. A further comparison of scores, using the t-test, between the attitudinal test for the written and the video/summary revealed no significant difference. A comparison of the attitudinal test for the written and video only was significant at the .05 level in favor of the video presentation using the t-test.
The grant evaluators participating in the study were asked to make a professional judgment regarding the continuance or discontinuance of the program presented. In 40% of the cases those reading the written report recommended that the program be discontinued. Those reading the summary and seeing the video report responded negatively in 10% of the cases. None of those seeing only the video report voted to discontinue the program.
Conclusions. The cognitive material of a report can be communicated equally well in video format, in written format, or in a combination of the two. However, the study’s findings suggest that a video report will be more effective that a written report in changing attitudes or opinions.
The feasibility of a video reporting format hinges on the availability of production funds, access to video equipment and technical assistance. Advances in television technology together with a growing consumer market have established a trend toward lower cost and simplified operation. Government applications are increasing as a result.
The findings indicate that a video report can influence an evaluator’s opinion of a program. It was the consensus among the rehabilitation grant reviewers participating in the study that the video presentation provided a more affective understanding of a program than the traditional reporting system. However, they identified the need to include more hard date and critical assessments
ropensci/drake: First release under rOpenSci
No full text<p>TL;DR: this is the first release in which <code>drake</code> is part of rOpenSci. Relative to 4.4.0, this release has major changes to cache internals, user-level function names, and documentation.</p>
<ul>
<li>Transfer <code>drake</code> to rOpenSci: <a href="https://github.com/ropensci/drake">https://github.com/ropensci/drake</a></li>
<li>Several functions now require an explicit <code>config</code> argument, which you can get from
<code>drake_config()</code> or <code>make()</code>. Examples:<ul>
<li>outdated()</li>
<li>missed()</li>
<li>rate_limiting_times()</li>
<li>predict_runtime()</li>
<li>vis_drake_graph()</li>
<li>dataframes_graph()</li>
</ul>
</li>
<li>Always process all the imports before building any targets. This is part of the solution to #168: if imports and targets are processed together, the full power of parallelism is taken away from the targets. Also, the way parallelism happens is now consistent for all parallel backends.</li>
<li>Major speed improvement: dispense with internal inventories and rely on <code>cache$exists()</code> instead.</li>
<li>Let the user define a trigger for each target to customize when <code>make()</code> decides to build targets.</li>
<li>Document triggers and other debugging/testing tools in the new <a href="https://github.com/ropensci/drake/blob/master/vignettes/debug.Rmd">debug vignette</a>.</li>
<li>Restructure the internals of the <code>storr</code> cache in a way that is not back-compatible with projects from versions 4.4.0 and earlier. The main change is to make more intelligent use of <code>storr</code> namespaces, improving efficiency (both time and storage) and opening up possibilities for new features. If you attempt to run drake >= 5.0.0 on a project from drake <= 4.0.0, drake will stop you before any damage to the cache is done, and you will be instructed how to migrate your project to the new drake.</li>
<li>Use <code>formatR::tidy_source()</code> instead of <code>parse()</code> in <code>tidy_command()</code> (originally <code>tidy()</code> in <code>R/dependencies.R</code>). Previously, <code>drake</code> was having problems with an edge case: as a command, the literal string <code>"A"</code> was interpreted as the symbol <code>A</code> after tidying. With <code>tidy_source()</code>, literal quoted strings stay literal quoted strings in commands. This may put some targets out of date in old projects, yet another loss of back compatibility in version 5.0.0.</li>
<li>Speed up clean() by refactoring the cache inventory and using light parallelism.</li>
<li>Implement <code>rescue_cache()</code>, exposed to the user and used in <code>clean()</code>. This function removes dangling orphaned files in the cache so that a broken cache can be cleaned and used in the usual ways once more.</li>
<li>Change the default <code>cpu</code> and <code>elapsed</code> arguments of <code>make()</code> to <code>NULL</code>. This solves an elusive bug in how drake imposes timeouts.</li>
<li>Allow users to set target-level timeouts (overall, cpu, and elapsed) with columns in the workflow plan data frame.</li>
<li>Document timeouts and retries in the new <a href="https://github.com/ropensci/drake/blob/master/vignettes/debug.Rmd">debug vignette</a>.</li>
<li>Add a new <code>graph</code> argument to functions <code>make()</code>, <code>outdated()</code>, and <code>missed()</code>.</li>
<li>Export a new <code>prune_graph()</code> function for igraph objects.</li>
<li>Delete long-deprecated functions <code>prune()</code> and <code>status()</code>.</li>
<li>Deprecate and rename functions:<ul>
<li><code>analyses()</code> => <code>plan_analyses()</code></li>
<li><code>as_file()</code> => <code>as_drake_filename()</code></li>
<li><code>backend()</code> => <code>future::plan()</code></li>
<li><code>build_graph()</code> => <code>build_drake_graph()</code></li>
<li><code>check()</code> => <code>check_plan()</code></li>
<li><code>config()</code> => <code>drake_config()</code></li>
<li><code>evaluate()</code> => <code>evaluate_plan()</code></li>
<li><code>example_drake()</code> => <code>drake_example()</code></li>
<li><code>examples_drake()</code> => <code>drake_examples()</code></li>
<li><code>expand()</code> => <code>expand_plan()</code></li>
<li><code>gather()</code> => <code>gather_plan()</code></li>
<li><code>plan()</code>, <code>workflow()</code>, <code>workplan()</code> => <code>drake_plan()</code></li>
<li><code>plot_graph()</code> => <code>vis_drake_graph()</code></li>
<li><code>read_config()</code> => <code>read_drake_config()</code></li>
<li><code>read_graph()</code> => <code>read_drake_graph()</code></li>
<li><code>read_plan()</code> => <code>read_drake_plan()</code></li>
<li><code>render_graph()</code> => <code>render_drake_graph()</code></li>
<li><code>session()</code> => <code>drake_session()</code></li>
<li><code>summaries()</code> => <code>plan_summaries()</code></li>
</ul>
</li>
<li>Disallow <code>output</code> and <code>code</code> as names in the workflow plan data frame. Use <code>target</code> and <code>command</code> instead. This naming switch has been formally deprecated for several months prior.</li>
<li>Deprecate the ..analysis.. and ..dataset.. wildcards in favor of analysis<strong> and dataset</strong>, respectively. The new wildcards are stylistically better an pass linting checks.</li>
<li>Add new functions <code>drake_quotes()</code>, <code>drake_unquote()</code>, and <code>drake_strings()</code> to remove the silly dependence on the <code>eply</code> package.</li>
<li>Add a <code>skip_safety_checks</code> flag to <code>make()</code> and <code>drake_config()</code>. Increases speed.</li>
<li>In <code>sanitize_plan()</code>, remove rows with blank targets "".</li>
<li>Add a <code>purge</code> argument to <code>clean()</code> to optionally remove all target-level information.</li>
<li>Add a <code>namespace</code> argument to <code>cached()</code> so users can inspect individual <code>storr</code> namespaces.</li>
<li>Change <code>verbose</code> to numeric: 0 = print nothing, 1 = print progress on imports only, 2 = print everything.</li>
<li>Add a new <code>next_stage()</code> function to report the targets to be made in the next parallelizable stage.</li>
<li>Add a new <code>session_info</code> argument to <code>make()</code>. Apparently, <code>sessionInfo()</code> is a bottleneck for small <code>make()</code>s, so there is now an option to suppress it. This is mostly for the sake of speeding up unit tests.</li>
<li>Add a new <code>log_progress</code> argument to <code>make()</code> to suppress progress logging. This increases storage efficiency and speeds some projects up a tiny bit.</li>
<li>Add an optional <code>namespace</code> argument to <code>loadd()</code> and <code>readd()</code>. You can now load and read from non-default <code>storr</code> namespaces.</li>
<li>Add <code>drake_cache_log()</code>, <code>drake_cache_log_file()</code>, and <code>make(..., cache_log_file = TRUE)</code> as options to track changes to targets/imports in the drake cache.</li>
<li>Detect knitr code chunk dependencies in response to commands with <code>rmarkdown::render()</code>, not just <code>knit()</code>.</li>
<li>Add a new general best practices vignette to clear up misconceptions about how to use <code>drake</code> properly.</li>
</ul>
The Realism of George Moore
No full text102 leaves. Advisor: Dr. Bruce MartinThe problem. The realist novels of George Moore are extremely unlike one another in content and technique. While scholars have studied in detail the French influences in Moore's writing,
the question of whether Moore was something more than an imitator of French fiction and whether he contributed something new to the English realist tradition has not been studied.
Procedure. The multifarious literary currents in England during the Nineties were examined. Then George Moore's realist novels were studied with respect to their links with the naturalism
of Zola. Finally, the novels of Moore were compared to those of Dickens, Eliot, and Hardy with regard to elements of realism. One typical novel of each author was examined in detail,
and references were made to other novels of the three writers.
Findings. It was found that Moore brought to the English novel a distinctly new creation in realism. His borrowing from French naturalism was selective and superficial. Moore created a realist novel that was highly objective in tone and technique, concentrating on the cerebral reality of the individual, who for the first time in English fiction, was not a representative
of a distinct and strong social environment.
Conclusion. While Moore's novels will probably never be ranked beside those of Dickens, Eliot, and Hardy as the great novels of the English language, Moore will be regarded as one who not
only sought and found inspiration outside of the English tradition but also contributed something new and different to the tradition of the realist novel
- …
