MétaCan
Menu
Back to cohort
Record W2158770811 · doi:10.1109/hpcs.2008.9

Models for Grid Applications and Jobs

2008· article· en· W2158770811 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueProceedings/Proceedings (International Symposium on High Performance Computing Systems and Applications) · 2008
Typearticle
Languageen
FieldComputer Science
TopicDistributed and Parallel Computing Systems
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsComputer scienceDistributed computingGridScheduling (production processes)Grid computingJob schedulerInteroperabilityFault toleranceAutomationProcessor schedulingResource (disambiguation)Operating systemCloud computingComputer network

Abstract

fetched live from OpenAlex

Grid computing technologies have made it possible for researchers to get access to more computational resources than ever before. However, heterogeneity of resources, scheduling policy and applications makes it difficult to manage the execution of jobs in such environments. The manner in which a job is configured to run on one resource may not be appropriate for another resource. Long running jobs need to be split into a series of shorter jobs with the aid of checkpointing to increase fault tolerance and to meet scheduling policy constraints of different resources. To take full advantage of grid environments, execution management systems need to be able to configure, reconfigure, checkpoint and migrate jobs as necessary. Information models that describe resources, policy and applications help automate execution management and allow for interoperability between tools. This paper presents application and job models that describe the processes required to configure and execute jobs on different resources. Example instances of the application and job models for the GROMACS molecular dynamics simulation example are also presented, illustrating how the models aid in automation.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.963
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.017
GPT teacher head0.234
Teacher spread0.216 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it