Spelling suggestions: "subject:"beholder"" "subject:"householder""
1 |
Jole: a library for dynamic job-level parallel workloadsPatterson, Jordan 11 1900 (has links)
Problems in scientific computing often consist of a workload of jobs with dependencies between them. Batch schedulers are job-oriented, and are not well-suited to executing these workloads with complex dependencies.
We introduce Jole, a Python library created to run these workloads. Jole has three contributions that allow flexibility not possible with a batch scheduler. First, dynamic job execution allows control and monitoring of jobs as they are running. Second, dynamic workload specification allows the creation of workloads that can adjust their execution while running. Lastly, dynamic infrastructure aggregation allows workloads to take advantage of additional resources as they become available.
We evaluate Jole using GAFolder, a protein structure prediction tool. We show that our contributions can be used to create GAFolder workloads that use less cluster resources, iterate on global protein structures, and take advantage of additional cluster resources to search more thoroughly.
|
2 |
Jole: a library for dynamic job-level parallel workloadsPatterson, Jordan Unknown Date
No description available.
|
3 |
Insert Title Here : Investigating the communication of placeholders and placeholder-characters in code examples in the programming trade.Parker, Sven January 2017 (has links)
To improve the communication between programming instructors and learners; placeholders, placeholder-characters and placeholder characteristics are investigated via two focus groups. One focus group with instructors, the other with learners. The combined and analyzed results show that placeholder-characters can confuse more than they help, more often for programming beginners. The semantics of a placeholder is the most crucial part of understanding its purpose and strengthens its characteristics. A placeholder using a different letter case from the surrounding code is easier to differentiate and find in a block of code. / Summary The study’s purpose is: To find out if digital characters could improve the communication between programming instructors and learners by standardizing the implication “placeholder” or “replace this”. What characteristics could be used to communicate placeholders? To answer the purpose, it has been broken down into two research questions. What opinions do programming instructors and learners have about using placeholder-characters to improve the communication between them? What characteristics could a placeholder have to better communicate its purpose? To answer the research questions, two focus groups were held. One with instructors and one with learners. They are then asked to discuss placeholders, placeholder- characters and their characteristics. Later transcribed, categorized and analyzed into findings that are discussed and concluded upon. The participants mostly believed that placeholder-characters can confuse more than they are able to help, more often the case for beginners. That the placeholder’s semantics of the label is crucial for understanding the purpose of it. Using a different letter-casing for placeholders could make it easier to find and understand that it deviates from the rest of the code in the concerned code example, preferably “SCREAMING_SNAKE_CASE”. A placeholder-character is considered viable to use as a global standard if it complies with the following five requirements: It is universally used (A standard). Available easily (found on any keyboard). Shows what and what not to replace (keep quotation marks). Is understood by programming-software (displayed and compiled correctly). Not used for other purposes in coding already (has another implication). Otherwise it is not considered supposable for implementation.
|
Page generated in 0.036 seconds