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

Merge a new atms_npp.yaml file to replace the old atms_npp_qc_bc.yaml. #237

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

xyzemc
Copy link
Contributor

@xyzemc xyzemc commented Nov 26, 2024

The file name has been changed to the standard of the templates yaml file.
The new yaml file also included the following items:

  • added the Clouds Inputs
  • removed the 'circle domain check' filter, and added the online domain check filter.
  • changed the channel use flag to be same as it in RRFSv1
  • changed the ioda file name with the standard of other data type

The file name has been changed to the standarid of the templates yaml file.
The new file also included the following items:
* added the Clouds Inputs
* removed the 'circle domain check' filter, and added the online domain check filter.
* changed the channel use flag to the same as it in RRFSv1
* changed the ioda file name with the standard of other data type
Comment on lines +243 to +252
# Regional Domain Check
- filter: Bounds Check
filter variables:
- name: brightnessTemperature
channels: *atms_npp_channels
test variables:
- name: GeoVaLs/observable_domain_mask
flag all filter variables if any test variable is out of bounds: true
minvalue: 0.0
maxvalue: 0.5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you know what the flag all filter variables if any test variable is out of bounds option does? That option is not enabled for our mesonet yamls. Also, for the mesonet yamls the minvalue and maxvalue keys are are indented under the main filter section and not under test variables. I am not sure if that matters though.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I don't know. Let's say if @HuiLiu-NOAA can answer this question.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. "flag all filter variables if any test variable is out of bounds" can be removed here since only one test variable is involved.
  2. I think minvalue and maxvalue keys should be listed under "test variables"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @HuiLiu-NOAA for the input. For #⁠2, it seems like it worked for mesonet obs with the min/maxvalue indented under the filter and not under test variables. So maybe it works either way?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it may be better to move minvalue and maxvalue keys under "test variables", just to be logically more clear.

@SamuelDegelia-NOAA
Copy link
Contributor

Also, could you add an obs localizations: section like in the existing atms_npp_qc_bc.yaml file?

@xyzemc
Copy link
Contributor Author

xyzemc commented Nov 27, 2024

Also, could you add an obs localizations: section like in the existing atms_npp_qc_bc.yaml file?

I have added back the localization part.

@HuiLiu-NOAA
Copy link
Collaborator

HuiLiu-NOAA commented Nov 27, 2024 via email

@xyzemc
Copy link
Contributor Author

xyzemc commented Nov 27, 2024

Agree. it may work either way.

On Wed, Nov 27, 2024 at 10:42 AM Samuel Degelia @.> wrote: @.* commented on this pull request. ------------------------------ In rrfs-test/validated_yamls/templates/obtype_config/atms_npp.yaml <#237 (comment)>: > + # Regional Domain Check + - filter: Bounds Check + filter variables: + - name: brightnessTemperature + channels: atms_npp_channels + test variables: + - name: GeoVaLs/observable_domain_mask + flag all filter variables if any test variable is out of bounds: true + minvalue: 0.0 + maxvalue: 0.5 Thanks @HuiLiu-NOAA https://github.com/HuiLiu-NOAA for the input. For #⁠2, it seems like it worked for mesonet obs with the min/maxvalue indented under the filter and not under test variables. So maybe it works either way? — Reply to this email directly, view it on GitHub <#237 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOF252DUDNVLY2FAQU36BT32CX767AVCNFSM6AAAAABSRFFFXCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINRVGY2TCOBVHE . You are receiving this because you were mentioned.Message ID: @.**>

Thanks @HuiLiu-NOAA for your answer. I will test this again.

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

Successfully merging this pull request may close these issues.

3 participants