1NSGR_SUBMIT(1)                   User Commands                  NSGR_SUBMIT(1)
2
3
4

NAME

6       nsgr_submit - manual page for nsgr_submit 1.0.3
7

DESCRIPTION

9              nsgr_submit TEMPLATE_DIRECTORY validate|run [results_directory]
10
11              Where  TEMPLATE_DIRECTORY  is  the name of a directory that con‐
12              tains the job's input data files and two  property  files  named
13              testInput.properties and testParam.properties.
14
15       -c
16
17              path to config file
18
19              By  default, it looks in the users's home directory (~) for .ns‐
20              grest.conf, then for nsgrest.conf (without a dot)
21
22              validate
23
24       Ask's the REST API whether the job is valid.
25              If valid, prints to stdout, the command line that
26
27       would be run on the execution host if the job were submitted to run.
28              If invalid, prints an
29
30              error message that explains which fields have errors.
31
32              run
33
34              Submits the job to the REST API, waits for it to  complete,  and
35              downloads the results to a subdirectory of the current directory
36              whose name is the jobhandle (i.e, starts with "NGBW-"))
37
38              [results_directory]
39
40       Absolute or relative path of a directory to which results will be down‐
41       loaded.
42              If the directory
43
44              doesn't exist, nsgr_submit will create it. Intermediate directo‐
45              ries, however, will not be created.  If results_directory  isn't
46              specified,  the  default  is directory name is ./jobhandle where
47              jobhandle is the CIPRES assigned job handle, a long guid, start‐
48              ing with "NGBW-".
49
50
51
52nsgr_submit 1.0.3                October 2023                   NSGR_SUBMIT(1)
Impressum