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

fill negative tracers in chgres #810

Open
KevinViner-NOAA opened this issue Apr 12, 2023 · 6 comments
Open

fill negative tracers in chgres #810

KevinViner-NOAA opened this issue Apr 12, 2023 · 6 comments

Comments

@KevinViner-NOAA
Copy link

Some (All?) old output of FV3GFS has some negative tracer values. These values get interpolated, but not filled, when using chgres and are read into the model as initial conditions. The input of negative tracers can perpetuate the problem of negative tracers and so on and so forth. We need to get rid of them. Clipping is generally considered a conservation no-go, but I'm much more worried about it in the forecast model than I am in preparing initial conditions. I'm certainly open to other methods if somebody has another idea.

@GeorgeGayno-NOAA
Copy link
Collaborator

@KevinViner-NOAA How is this impacting your work? Could we try clipping as a first solution?

@KevinViner-NOAA
Copy link
Author

@GeorgeGayno-NOAA I noticed the negatives in some RRFS cold starts I was running. Right now, given sharp gradients in tracer fields, the vertical remapping in the model can produce negatives. Knowing that this is the case, there is code implemented to try to fill the negatives with an elaborate (but conservative) borrowing scheme. However, sometimes this still fails to fill the negatives. Perhaps my issue is premature, but my thinking is that we don't want the initial conditions to be introducing negatives, especially in a (hopefully) near future where the model doesn't create them. I think clipping would be a great start.

@GeorgeGayno-NOAA
Copy link
Collaborator

@GeorgeGayno-NOAA I noticed the negatives in some RRFS cold starts I was running. Right now, given sharp gradients in tracer fields, the vertical remapping in the model can produce negatives. Knowing that this is the case, there is code implemented to try to fill the negatives with an elaborate (but conservative) borrowing scheme. However, sometimes this still fails to fill the negatives. Perhaps my issue is premature, but my thinking is that we don't want the initial conditions to be introducing negatives, especially in a (hopefully) near future where the model doesn't create them. I think clipping would be a great start.

Do you have an example case I can look at (i.e., the chgres script/config file used, and the input data)?

@GeorgeGayno-NOAA
Copy link
Collaborator

@KevinViner-NOAA do you still want this issue worked?

@GeorgeGayno-NOAA
Copy link
Collaborator

@KevinViner-NOAA what is the status of this issue?

@GeorgeGayno-NOAA
Copy link
Collaborator

@KevinViner-NOAA - there has been no recent activity on this issue. Do you still want it worked? If not, I will close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants