rsnt_translations
56,420
edits
No edit summary |
No edit summary |
||
Line 462: | Line 462: | ||
<!--T:143--> | <!--T:143--> | ||
<b>Please note:</b> The test to determine whether to submit a follow-up job, abbreviated as <code>work_should_continue</code> in the above example, should be a <i>positive test</i>. 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 <i>not</i> 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 == <!--T:174--> | == Automating job submission == <!--T:174--> | ||
Line 510: | Line 510: | ||
<!--T:159--> | <!--T:159--> | ||
<i>If you are unsure if your job requires a specific architecture, do not use this option.</i> Jobs that do not specify a CPU architecture can be scheduled on either Broadwell or Skylake nodes, and will therefore generally start earlier. | |||
</tab> | </tab> | ||
Line 537: | Line 537: | ||
==== Avoid hidden characters in job scripts ==== <!--T:43--> | ==== Avoid hidden characters in job scripts ==== <!--T:43--> | ||
Preparing a job script with a | Preparing a job script with a word processor instead of a text editor is a common cause of trouble. Best practice is to prepare your job script on the cluster using an editor such as nano, vim, or emacs. If you prefer to prepare or alter the script off-line, then: | ||
* '''Windows users:''' | * '''Windows users:''' | ||
** Use a text editor such as Notepad or [https://notepad-plus-plus.org/ Notepad++]. | ** Use a text editor such as Notepad or [https://notepad-plus-plus.org/ Notepad++]. |