Duplicate of #160. See also #151
Issue #179 highlighted that if the list of parameters and sets in the config.yaml file does not match what is in the data file, otoole returns a cryptic error message from Amply.
It is currently not possible to validate parameters and sets against what is in a datafile as Amply requires these to parse the datafile.
There are some hacky ways to extract parameters and sets from datafiles using string matching or regex, but it's fragile.
Catching the Amply error and returning a more useful error in otoole e.g. "DatafileParseError: Please check that the config file provided matches the parameters and sets in your datafile" maybe a quicker route to something usable...
Duplicate of #160. See also #151
Issue #179 highlighted that if the list of parameters and sets in the
config.yamlfile does not match what is in the data file, otoole returns a cryptic error message from Amply.It is currently not possible to validate parameters and sets against what is in a datafile as Amply requires these to parse the datafile.
There are some hacky ways to extract parameters and sets from datafiles using string matching or regex, but it's fragile.
Catching the Amply error and returning a more useful error in otoole e.g. "DatafileParseError: Please check that the config file provided matches the parameters and sets in your datafile" maybe a quicker route to something usable...