-
Notifications
You must be signed in to change notification settings - Fork 22
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
Can we use the PreQC obs filter? #307
Comments
@delippi @SamuelDegelia-NOAA @spanNOAA Is there a reason why we are not able to use the |
It is my understanding that I don't think there is any benefit of using the PreQC filter over what we do now. They both would do the same thing. |
Also, check the latest RDASApp yamls. I've made changes such as RejectList --> Perform Action. There are various other things as well. Probably won't impact results much though. |
Thanks for the information! @delippi |
Curious why we want to change from |
Both will do the same thing. I think the reason I had changed it was because I had some yamls using RejectList and others using Perform Action and I had just went with Perform Action. I believe RejectList can only reject obs, so it might be the more direct way to do this. Perform Action is more flexible and can do any action (for debugging purposes it could be helpful), but we probably have all the problems worked out by now. We can use either one. It doesn't make any real difference to me. The main reason I was pointing that out was that the yamls being used were a slightly older version than what we had in RDASApp. |
NCAR uses the following simple filter to reject all obs with a qcflag larger than 3
Could we use it as well?
Right now, we use the following filter corresponding to this capability:
The text was updated successfully, but these errors were encountered: