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

P0 always needs to be on history file #150

Closed
gold2718 opened this issue Jun 3, 2024 · 3 comments
Closed

P0 always needs to be on history file #150

gold2718 opened this issue Jun 3, 2024 · 3 comments
Labels
invalid This doesn't seem right wontfix This will not be worked on
Milestone

Comments

@gold2718
Copy link

gold2718 commented Jun 3, 2024

What happened?

In prototype NorESM2.5 (e.g. noresm_v11_cam6_3_123), P0 is not showing up on CAM history files.

What are the steps to reproduce the bug?

Run a CAM-SE simulation using noresm_v11_cam6_3_123, look at history files.

What CAM-Nor tag were you using?

noresm_v11_cam6_3_123

What machine were you running CAM (or NorESM) on?

Betzy

What compiler were you using?

Intel

Path to a case directory, if applicable

No response

Will you be addressing this bug yourself?

No

Extra info

No response

@gold2718 gold2718 added the bug Something isn't working label Jun 3, 2024
@gold2718 gold2718 added this to the NorESM2.5 milestone Jun 3, 2024
@adagj
Copy link

adagj commented Jun 26, 2024

Did we decide that P0 doesn't need to be on history files with SE?

@MichaelSchulzMETNO
Copy link

Yes - my understanding is, that it does not make sense to be put on the raw output files.

@gold2718 gold2718 added invalid This doesn't seem right wontfix This will not be worked on and removed bug Something isn't working labels Jun 26, 2024
@gold2718
Copy link
Author

Agree. For background, see this comment and below in #146.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right wontfix This will not be worked on
Projects
Status: Done
Development

No branches or pull requests

3 participants