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.

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

Added thkcello diagnostic #150

Merged
merged 1 commit into from
Apr 28, 2015

Conversation

adcroft
Copy link
Collaborator

@adcroft adcroft commented Apr 27, 2015

@StephenGriffies , Since you spotted how I messed up the last attempt at this, you now have the role of reviewing this commit. I have not provided a branch on MOM6-examples but this commit will cause changes to the available_diags. We should also add thkcello to a diag_table in the usual places.

From commit 00ba2d7:

Added thkcello diagnostic

  • Corrected calculation of thkcello, cell thickness in meters,
    for non-Boussinesq mode.
  • Moved diagnostic of thkcello into MOM_diagnostics.F90 from
    MOM.F90.
  • Renamed a temporary 3d array which is re-used by various
    diagnostics.
  • Closes issue Add diagnostic: thkcello #98.

- Corrected calculation of thkcello, cell thickness in meters,
  for non-Boussinesq mode.
- Moved diagnostic of thkcello into MOM_diagnostics.F90 from
  MOM.F90.
- Renamed a temporary 3d array which is re-used by various
  diagnostics.
- Closes issue #98.
@adcroft adcroft added this to the CMOR-ization of diagnostics milestone Apr 27, 2015
@StephenGriffies StephenGriffies merged commit 00ba2d7 into dev/master Apr 28, 2015
@StephenGriffies StephenGriffies deleted the user/aja/issue98_thkcello_diag branch April 28, 2015 20:52
@StephenGriffies
Copy link
Contributor

Fixed a diagnostic bug related to thkcello. The field p_surf was incorrectly accessed for cases where this field was not allocated.

The bug fix was applied in commit ad5aab0

@StephenGriffies
Copy link
Contributor

the diagnostic appears to be fine now for both Bouss and non-Bouss. Will thus close the issue.

@StephenGriffies
Copy link
Contributor

not sure how to close the ticket...there is no "close and comment" button on my window...

@adcroft
Copy link
Collaborator Author

adcroft commented Apr 28, 2015

The pull request (ticket #150) was labelled "merged" by GitHub once you pushed the merge commit to dev/master. You can relax.

@adcroft adcroft mentioned this pull request Apr 28, 2015
alperaltuntas pushed a commit to gustavo-marques/MOM6 that referenced this pull request May 19, 2020
OpenMP and KPP performance changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants