<version>

[wachsylon]

Hi, in https://cmor.llnl.gov/mydoc_cmor3_c/ you recommend to set: "output_path_template": "<mip_era><activity_id><institution_id><source_id><experiment_id><_member_id><table><variable_id><grid_label><version>" where the version has the format "v<date>". If a User integrates CMOR in the operational workflow in which model output is produced over a time period of several days, model output will have different <version>s although it originates from the same model run. This has lead to some confusions. How should a user find a file which contains a particular variable in this structure during the workflow? Furthermore, the directories needs to be merged and a unique version needs to be assigned to the whole experiment output eventually. I suggest three solutions:

• Disable CMOR to construct <version>. This depends on how often CMOR is used for small experiments completely finished within a day.
• Only to remove <version> from output_path_template when performing operational experiment simulations and adding the subdirectory before publication. If the <version> build rule remains, I think this operational issue needs to be pointed out in the documentation for the users.
• The other ( probably unrealistic ) solution is to change the build rule of <version>.

What is your opinion? Did I miss something? Is there another reason for the <version> build rule? Best regards, Fabi