Job configuration files are those files containing the details of a particular job execution. Consequently, they are created in each run when the end user clicks the Compute button having already selected the input files and the argument values. So in principle, you wouldn’t need to prepare them. However, if your are willing to test your tool and emulate how it is to be called once integrated into the MuGVRE infrastructure, it is good to prepare toy samples for these two configuration files.
Input metadata file
Contains all the metadata associated with the selected input files as stored in the metadata database. This metadata include attributes as important as the ‘file_path’ as seen in the virtualized environment.
| Example of input file metadata | input_metadata.json |
Tool configuration file
Contains the values that arguments and input files take for that particular run.
| Example of input file metadata | config.json |