You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GFDL directory structure logic I use is specific to my own naming conventions, i.e. atmos_level_inst for instantaneous atmospheric data on model-native coordinates. However, not all people use these same names -- they can be named basically arbitrarily in the simulation's XML. Therefore, the logic for traversing a GFDL directory of model output should support user-supplied names.
The good thing is that, besides the names of the components, the structure is pretty much locked in, meaning that only the strings would have to be modified. The specification of these names could potentially vary from run to run within a model, and so it should be supported to be specified at the Run, Model, or Proj level. E.g. `component_names={'p.inst': 'atmos_inst', 'eta.inst': 'atmos_level_inst'}. This needs to be thought out further.
The text was updated successfully, but these errors were encountered:
This hasn't been accomplished yet, but it has been subsumed by the larger revamp of the file-finding methods addressed by #32 so no need for its own open issue.
The GFDL directory structure logic I use is specific to my own naming conventions, i.e.
atmos_level_inst
for instantaneous atmospheric data on model-native coordinates. However, not all people use these same names -- they can be named basically arbitrarily in the simulation's XML. Therefore, the logic for traversing a GFDL directory of model output should support user-supplied names.The good thing is that, besides the names of the components, the structure is pretty much locked in, meaning that only the strings would have to be modified. The specification of these names could potentially vary from run to run within a model, and so it should be supported to be specified at the Run, Model, or Proj level. E.g. `component_names={'p.inst': 'atmos_inst', 'eta.inst': 'atmos_level_inst'}. This needs to be thought out further.
The text was updated successfully, but these errors were encountered: