Skip to content

diag_table #124

Description

@Dooruk

As I mentioned before, there are so many versions of diag_table around. I suggest we have certain fields and filenames share the similar names for making comparisons easier. If we decide to change them going forward we can do that or anyone can add their own in their own runs. These versions could live under:

https://github.com/GEOS-ESM/GEOS_OceanGridComp/tree/develop/MOM6_GEOSPlug/mom6_app/1440x1080

I'm saying "they", because we would need multiple options depending on:

  • DA or no-DA run (only a small section is needed for this, so not a big problem)
  • dataAtm vs. coupled (They are different but I think we can keep the fields the same?)
  • Length of the run segment. For DA-runs, we are limited by window length. So there would be three types of diag_table:
    1. Runs shorter than 1 day
    2. Runs between 1 day and 1 month
    3. Runs longer then a month

So I suggest we have three versions, with file names and averaging differences.

@zhaobin74 and @lren20, it would really help if you could eliminate unnecessary entries from this file/gpfsm/dnb07/projects/p138/lren1/mom6/datm-access/diag_table (there are so many commented out ones already) and let me know absolute necessary ones that you are actively using or will be using. For instance for AMOC calculations.

Others, I would appreciate your input in case you need certain outputs required for your applications.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions