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

Add GNSSRO yaml files #67

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

Add GNSSRO yaml files #67

wants to merge 3 commits into from

Conversation

XuanliLi-NOAA
Copy link
Collaborator

Adding gnssro_mission.yaml.j2 data. The GNSS RO data is reorganized so each satellite mission has its own yaml file.

Copy link
Contributor

@CoryMartin-NOAA CoryMartin-NOAA left a comment

Choose a reason for hiding this comment

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

Any reason in particular there are QC procedures commented out? Should they be kept but commented out or removed?

@XuanliLi-NOAA
Copy link
Collaborator Author

Commented-out QCs have been removed from the YAML files.

Comment on lines +35 to +53
# Apply gross check using pccf
# Step 0-A: Create Diagnostic Flags
# Diagnostic flag for pccf
- filter: Create Diagnostic Flags
filter variables:
- name: bendingAngle
flags:
- name: pccfCheckReject
initial value: false
force reinitialization: true

# Diagnostic flag for qfro
- filter: Create Diagnostic Flags
filter variables:
- name: bendingAngle
flags:
- name: qfroCheckReject
initial value: false
force reinitialization: true
Copy link
Contributor

Choose a reason for hiding this comment

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

We will not be using "Create Diagnostic Flags" for QC flags because, with this method, we will be creating a diagnostic flag variable for each filter. This could make the output diagnostic file huge.

We are aiming to create one variable to store QC decisions.

So, my suggestion is that you remove the diagnostic flag variables (pccfChecReject and qfroCheckReject) if you do not need them to do anything. But If they help you diagnose problems at the current stage, it is good to keep them for now.

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