... | ... | @@ -151,7 +151,7 @@ In the example below the first script is number [1]. After it is complete both s |
|
|
* This order structure allows for infinite combinations and layouts of pipelines. As you may have noticed the first order number does not matter, **but** remember that files are loaded into the history script field alphabetically, so you may need to adjust the files names to ensure that the jobs that start first must be higher in the call order. In our case the file name for job [5,2] must be alphabetically smaller then the file name for job [6,4,5].
|
|
|
|
|
|
**4. Job Name**
|
|
|
* This will indicate what the job name will be. Batch swap string rules apply.
|
|
|
* This will indicate what the job name will be. Batch swap string rules apply. This name is used as the .m file name that is runs the scripts on your files, as well as the name of the cluster job name. Make sure that this name is under 64 characters as matlab can not run scripts with names that are too long.
|
|
|
:b: Default as *[batch_hfn,.,1]_[batch_dfn,.,1]* indicating that the job name will be named after the current script followed by the the name of the data file.
|
|
|
|
|
|
**5. Session Init**
|
... | ... | |