Paths to preset files with arguments can be provided using the preset or presets arguments. An already loaded preset can be given as a string using the preset_yml argument.
When providing a list of presets using presets, arguments in later presets override earlier ones. In this case, each element in the list should be a 2-tuple [file, namespace], identifying the preset file name and the namespace in the parameter tree where it should be applied.
The preset argument and the first element in each list of the presets argument can either point to a file or be a preset name, as returned by list-presets.
Arguments can also be provided on the command line. These override arguments in presets.
When this command is called from a script, the namespace argument is mandatory and specifies the name of the inner node in the parameter tree whose corresponding sub-tree should be provided to the target.
When this command is called interactively from the top level, the namespace argument specifies the parameter system namespace where the resulting arguments are placed, after the command has finished. In this case the argument is optional and defaults to the script or target name, plus a suffix in case the script/target has already run, so that the same command can be run multiple times.
Examples:
run-script "targets/qsp-x86/qsp-clear-linux.target.yml"
The -local flag is provided for compatibility with run-command-file. It only has effect when running scripts with old style script declarations blocks and works as specified by run-command-file.
If run-script is issued in a script-branch and the -main-branch flag is specified, then the code in the file will execute in the main script branch the next time it is scheduled.
The namespace used, or the calculated default namespace, is returned, unless -main-branch was specified.