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

Incorrect Axis Dimensions Set for 3D Sinking Flux Diagnostic Variables #98

Open
yichengt900 opened this issue Sep 25, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@yichengt900
Copy link
Collaborator

yichengt900 commented Sep 25, 2024

Currently, the 3D sinking diagnostic variables aren't working because the axis dimensions were not set correctly (thanks to @feida6996).

Incorrect Axis Dimensions Set for 3D Sinking Flux Diagnostic Variables

Since we already have an integrated one (i.e., fcadet_arag_100), I'm not sure if we still want to keep those diagnostic variables. Any suggestions are welcome.

@yichengt900 yichengt900 added the bug Something isn't working label Sep 25, 2024
@charliestock
Copy link
Contributor

Hello @yichengt900, @feida6996, I'm sorry I missed this when it was raised. We definitely do want to maintain 3D sinking flux diagnostics. I wasn't aware that we were having a problem with this. There is a somewhat cryptic note above this that seems to provide an explanation, but I'm not sure that I follow it. Do you have any output that illustrates the problem?

@feida6996
Copy link
Collaborator

Hi @charliestock and @yichengt900, the issue occurs only when writing out the 3D diagnostics. If the axis dimensions aren't fixed, the model won't start, so there's no outputs to compare. Once I fixed the axis dimensions, the model runs fine and outputs are generated. Correcting the axis dimension in cobalt_reg_diag.F90 should resolve this without affecting the model results.

@charliestock
Copy link
Contributor

Thanks @feida6996. I will be diving into the diagnostics later this week and will address this.

@yichengt900
Copy link
Collaborator Author

As @feida6996 mentioned (and Niki's notes above this code section), the register_diag_field wrapper currently only requires the size of the axes, not the actual values. So, if you're trying to output a 3D diagnostic, the size of the axes input needs to be 3 instead of 1. This should be an easy fix—either by changing axesTi(1:1) to axesTi(1:3), or by making it consistent with other 3D diagnostics and using axes(1:3).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants