I think that this was done because datasetDoc.json and problemDoc.json followed the same file path structure, but I found an example that breaks.
Using the dataset id: LL1_terra_canopy_height_long_form_s4_90_MIN_METADATA_dataset_TEST
Corresponding problem id: LL1_terra_canopy_height_long_form_s4_90_MIN_METADATA_problem
I suggest an alternative implementation that uses D3M's get_datasets_and_problems() function that traverses the datasets directory and returns dictionaries mapping dataset and problem ids to their corresponding file paths. PR coming soon...
Currently,
get_dataset_doc_path()
just does some string manipulation on the dataset id that is given. https://github.com/byu-dml/d3m-experimenter/blob/001a68aa988d58cecf2de078ce6bdc72c266641b/experimenter/utils.py#L13-L24get_problem_path()
does something similar. https://github.com/byu-dml/d3m-experimenter/blob/001a68aa988d58cecf2de078ce6bdc72c266641b/experimenter/utils.py#L40-L49I think that this was done because datasetDoc.json and problemDoc.json followed the same file path structure, but I found an example that breaks.
Using the dataset id:
LL1_terra_canopy_height_long_form_s4_90_MIN_METADATA_dataset_TEST
Corresponding problem id:LL1_terra_canopy_height_long_form_s4_90_MIN_METADATA_problem
The correct paths for these files are:
I suggest an alternative implementation that uses D3M's
get_datasets_and_problems()
function that traverses the datasets directory and returns dictionaries mapping dataset and problem ids to their corresponding file paths. PR coming soon...