Running jobs: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 476: Line 476:
<!--T:143-->
<!--T:143-->
'''Please note:''' The test to determine whether to submit a followup job, abbreviated as <code>work_should_continue</code> in the above example, should be a ''positive test''. There may be a temptation to test for a stopping condition (e.g. is some convergence criterion met?) and submit a new job if the condition is ''not'' detected. But if some error arises that you didn't foresee, the stopping condition might never be met and your chain of jobs may continue indefinitely, doing nothing useful.
'''Please note:''' The test to determine whether to submit a followup job, abbreviated as <code>work_should_continue</code> in the above example, should be a ''positive test''. There may be a temptation to test for a stopping condition (e.g. is some convergence criterion met?) and submit a new job if the condition is ''not'' detected. But if some error arises that you didn't foresee, the stopping condition might never be met and your chain of jobs may continue indefinitely, doing nothing useful.
== Automating job submission ==
Compute Canada provides a few different tools designed to facilitate running a large number of related serial, parallel, or GPU calculations. This practice is sometimes called "farming", "serial farming", or "task farming". In addition to automating the workflow, these tools can also improve computational efficiency by bundling up many short computations into fewer tasks of longer duration.
The following tools are available on our clusters:
* [[META: A package for job farming]]
* [[GNU Parallel]]
* [[GLOST]]


== Cluster particularities == <!--T:154-->
== Cluster particularities == <!--T:154-->
cc_staff
238

edits