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

Namelist options for commercial RO #128

Closed
KristenBathmann opened this issue Mar 11, 2021 · 5 comments · Fixed by #131
Closed

Namelist options for commercial RO #128

KristenBathmann opened this issue Mar 11, 2021 · 5 comments · Fixed by #131
Assignees

Comments

@KristenBathmann
Copy link
Contributor

Two namelist options will be added for commercial RO assimilation. These will be included in setup. The option gpstopalt will cutoff commercial data above this height. For example, setting gpstopalt=45.0 rejects all commercial data above 45 km. The option gpserrinf inflates commercial data errors. For example gpserrinf=1.5 multiplies the error by 1.5 at all levels.

This work is being done under release/gfsda.v16.1.0

@dtkleist
Copy link
Contributor

Do we want to make the names of these parameters more explicit so it is obvious that they apply to commercial GPSRO only and not all bending angle obs?

@KristenBathmann
Copy link
Contributor Author

Sure, how about commgpstop and commgpserrinf?

@dtkleist
Copy link
Contributor

Works for me.

@KristenBathmann
Copy link
Contributor Author

The new namelist options are working correctly. The cost function is lowered by cutting off commerical RO at 45 km, and by inflating the errors:
cost4

Setting commgpstop to 55. (the current value for gpstop) allows all commerical RO below 55 km to be assimilated:

spirectl

Setting commgpstop to 45. cuts off the commerical RO at 45 km:

spirecut

Setting commgpstop to 45. does not affect other instruments:

kompsatcut

@MichaelLueken
Copy link
Contributor

These changes have been merged to the authoritative repo at 51a6564. Closing this issue.

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 a pull request may close this issue.

3 participants