Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

3. Test existing (P0.0) domaincfg for HPG errors #26

Open
3 tasks
jpolton opened this issue Jul 20, 2021 · 2 comments
Open
3 tasks

3. Test existing (P0.0) domaincfg for HPG errors #26

jpolton opened this issue Jul 20, 2021 · 2 comments
Assignees
@davbyr @anwiseNOCL

Comments

@jpolton
Copy link
Contributor

jpolton commented Jul 20, 2021 •
edited by davbyr
Loading

Assess spurious HPG velocities in existing domain_cfg.nc file.

Requires (from AMM7 tests):

  • Closed boundaries.
  • Idealised initial conditions
  • couple of months simulation.
    Idealised stratification: Summertime off-shelf. Option 2 in userdef_istate.
@jpolton jpolton changed the title Test existing domaincfg Test existing domaincfg for HPG errors Jul 20, 2021
@jpolton jpolton changed the title Test existing domaincfg for HPG errors 3. Test existing domaincfg for HPG errors Jul 20, 2021
@jpolton jpolton changed the title 3. Test existing domaincfg for HPG errors 3. Test existing (P0.0) domaincfg for HPG errors Jul 20, 2021
@jpolton
Copy link
Contributor Author

jpolton commented Jul 20, 2021

I'm assuming that @davbyr can run P0.0 on MONSooN and that @anwiseNOCL can help with the idealised testing (i.e. initial condition, namelist and xml choices)

@davbyr
Copy link
Contributor

davbyr commented Aug 2, 2021 •
edited
Loading

Maximum currents for a month of simulation when closed boundaries, no forcing, analytical ICs, CO9p0 domain_cfg.nc:

Screenshot 2021-08-02 at 09 04 57

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

@davbyr davbyr

@anwiseNOCL anwiseNOCL

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jpolton @davbyr @anwiseNOCL