@@ -24,10 +24,10 @@ the Swift script to launch a NT3 run, and to
24
24
25
25
For each run of the benchmark model, the following is produced:
26
26
27
- * ` run.json ` - a json file containing data describing the individual run: the
27
+ * ` run.[run_id]. json ` - a json file containing data describing the individual run: the
28
28
parameters for that run and per epoch details such as the validation loss. This
29
29
file will be written to the output directory for that particular run (e.g.)
30
- ` nt3_mlrMBO/experiments/E1/run_1_1_0/output/run.json ` .
30
+ ` nt3_mlrMBO/experiments/E1/run_1_1_0/output/run.1.1.0. json ` .
31
31
32
32
33
33
## User requirements ##
@@ -286,22 +286,68 @@ cd Supervisor/workflows/nt3_mlrMBO/ext/EQ-R/eqr
286
286
287
287
Launching the workflow:
288
288
289
- Edit
290
- ` cori_workflow3.sh ` setting the relevant variables as appropriate. All easily
289
+ 1 . Make a copy of ` cori_workflow3.sh `
290
+ 2 . Edit the copy setting the relevant variables there
291
+ as appropriate. All easily
291
292
changed settings are delineated by the ` USER SETTINGS START ` and ` USER SETTINGS END `
292
293
markers. Note that these variables can be easily overwritten from the calling
293
294
environment (use ` export ` in your shell). By default these are set up for a short-ish
294
295
debugging runs and will need to be changed for a production run.
296
+ 3 . ` source cori_settings.sh `
297
+ 4 . Run the workflow by running your workflow script, passing an experiment id.
295
298
296
299
An example:
297
300
298
301
```
299
302
cd Supervisor/workflows/nt3_mlrMBO/swift
303
+ cp cori_workflow3.sh my_cori_workflow.sh
304
+ # edit my my_cori_workflow.sh
300
305
source cori_settings.sh
301
- ./cori_workflow .sh T1
306
+ ./my_cori_workflow .sh T1
302
307
```
303
308
where T1 is the experiment ID.
304
309
305
310
### Running on Theta ###
306
311
307
- TODO
312
+ * Download, install etc. the user requirements listed at the top of this
313
+ document.
314
+
315
+ All the system requirements (see above) have been installed on Theta for except
316
+ for the EQ/R swift extension.
317
+
318
+ * Compile the EQ/R swift-t extension.
319
+ ```
320
+ cd Supervisor/workflows/nt3_mlrMBO/ext/EQ-R/eqr
321
+ ./bootstrap
322
+ source ./theta_build_settings.sh
323
+ ./configure
324
+ make install
325
+ ```
326
+
327
+ Launching the workflow:
328
+
329
+ 1 . Make a copy of ` theta_workflow.sh `
330
+ 2 . Edit the copy setting the relevant variables there
331
+ as appropriate. All easily
332
+ changed settings are delineated by the ` USER SETTINGS START ` and ` USER SETTINGS END `
333
+ markers. Note that these variables can be easily overwritten from the calling
334
+ environment (use ` export ` in your shell). By default these are set up for a short-ish
335
+ debugging runs and will need to be changed for a production run.
336
+ 3 . Run the workflow by running your workflow script, passing an experiment id.
337
+
338
+ An example:
339
+
340
+ ```
341
+ cd Supervisor/workflows/nt3_mlrMBO/swift
342
+ cp theta_workflow.sh my_theta_workflow.sh
343
+ # edit my theta_workflow.sh if necesasry
344
+ ./theta_workflow.sh T1
345
+ ```
346
+
347
+ where T1 is the experiment ID.
348
+
349
+ Note that Theta use the _ ai_ -version of the workflow. The benchmark is launched
350
+ using Supervisor/workflows/nt3_mlrMBO/scripts/theta_run_model.sh. In there, the
351
+ ` PYTHONHOME ` shell variable can be changed to specify a different python installation to
352
+ run the model with. If you do change the python installation, the python
353
+ system requirements mentioned above will need to be satisfied.
0 commit comments