Packs the current workflow in a shell script. The shell script contains the
workflow definition as a string. The workflow definition is then piped into
grapevine at start up. Also, grapevine doesn't save the configuration when
closed, runs in headless mode and defaults the logfile to <empty>. Since
command line options are parsed one after another, parameters can be
overwritten when the switch is used more than once. Therefore, grapevine is
always started like this in the script:
cat $config | grapevine --Logfile "" --Headless --ReadConfigurationFromStdin
Also, generating a different batch completion file that contains also the
parameters of the model along with the usual grapevine parameters.
Original issue reported on code.google.com by brosch....@gmail.com on 12 Dec 2012 at 5:15
Original issue reported on code.google.com by
brosch....@gmail.com
on 12 Dec 2012 at 5:15