This is work in progress and not ready to merge yet. But the general idea would be that the user would specify certain directory paths in input/paths.yml. Everything else about the data (e.g. file name convention) is encoded in a class called DataModel. This is hidden from the user. Other classes like NoiseModel will inherit this structure. So a typical use case after the user sets their directory paths would be something like:
This is work in progress and not ready to merge yet. But the general idea would be that the user would specify certain directory paths in
input/paths.yml. Everything else about the data (e.g. file name convention) is encoded in a class called DataModel. This is hidden from the user. Other classes like NoiseModel will inherit this structure. So a typical use case after the user sets their directory paths would be something like:The branch "covtesting" has a working version of this, but I'm developing a better API into this branch (not currently working).