Convience methods existed for printing available CMOR names based on the table and what could be produced based upon what is available in the output folder.
What is available depended on some hard coded "string" which was a copy of an element of the FORTRAN code. @pgierz does not like this.
Below a list of the methods related to this issue. We might need them all or not. This issue is to discuss which ones do we include and to track which ones we have already included:
[ ] print-request: Print data request variables for json tables at PATH
[ ] print_available: Prints FESOM output variables available in the specified directory.
[ ] print_possible: Prints variables that FESOM could possibly produce. This is the one @pgierz does not like. I don't love it either.
[ ] match_available: Prints matches of FESOM output variables for a given data request.
[ ] match_possible: Prints matches of variables that FESOM could possibly produce for a given data request.
[ ] print_experiment_ids: Prints experiment IDs from a controlled vocabulary file. TODO: understand what this even means
[x] process: Processes rules from the given file to create the cmorized files. This is the main command of SEAMORE
[ ] create_directories: Creates MIP directory structure and hard links the given CMOR files.
Convience methods existed for printing available CMOR names based on the table and what could be produced based upon what is available in the output folder.
What is available depended on some hard coded "string" which was a copy of an element of the FORTRAN code. @pgierz does not like this.