-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update varobs and cx writers for visibility #221
Conversation
VAR expects aerosol (for visibility) to be called logm.
A search using the stash code reveals that the field using the correct stash code is named aerosol rather than logm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice! Does this require any modifications to sith KGO output?
I don't think so: don't KGOs only use the NetCDF output from the jopa background task? This ought not to effect that. |
I believe they check ODB, Varobs and CX output. It might be worth running it just to be on the safe side. |
Yes you are correct, the kgos will need to be remade. Unless it's very straightforward, it's probably only worth doing once the jjdocs PR is ready since that will also need new kgos. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the change. The ctest failure is fixed in #222
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ran OK in my environment. No failures detected for mo-bundle main build + ctest, and sith/malak kgo runs (apart from what's expected).
OFFICIAL
I guess we don't have a UKV surface KGO set up then. Please merge if you are happy.
OFFICIAL
…________________________________
From: Matt Shin ***@***.***>
Sent: 16 August 2024 4:16 PM
To: MetOffice/opsinputs ***@***.***>
Cc: Reuben Nixon-Hill ***@***.***>; Assign ***@***.***>
Subject: Re: [MetOffice/opsinputs] Update varobs and cx writers for visibility (PR #221)
This email was received from an external source. Always check sender details, links & attachments.
@matthewrmshin approved this pull request.
Ran OK in my environment. No failures detected for mo-bundle main build + ctest, and sith/malak kgo runs.
—
Reply to this email directly, view it on GitHub<#221 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB4I73KNSWJ5T3DO565QRXDZRYJWVAVCNFSM6AAAAABMSNKOV6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDENBSHE2TGNRRGY>.
You are receiving this because you were assigned.Message ID: ***@***.***>
|
OFFICIAL
Hi Reuben,
I just realised my typing was cut off halfway. I actually meant that there were no unexpected KGO issues. I've now amended my comment in the PR. Sorry for the confusion.
Best,
Matt
---
Dr Matt Shin Expert Scientific Software Engineer
Met Office FitzRoy Road Exeter EX1 3PB United Kingdom
Tel: +44 (0)330135 1724
***@***.*** http://www.metoffice.gov.uk/
OFFICIAL
…________________________________
From: Reuben W. Nixon-Hill ***@***.***>
Sent: 16 August 2024 16:26
To: MetOffice/opsinputs ***@***.***>
Cc: Matthew Shin ***@***.***>; Mention ***@***.***>
Subject: Re: [MetOffice/opsinputs] Update varobs and cx writers for visibility (PR #221)
This email was received from an external source. Always check sender details, links & attachments.
OFFICIAL
I guess we don't have a UKV surface KGO set up then. Please merge if you are happy.
OFFICIAL
________________________________
From: Matt Shin ***@***.***>
Sent: 16 August 2024 4:16 PM
To: MetOffice/opsinputs ***@***.***>
Cc: Reuben Nixon-Hill ***@***.***>; Assign ***@***.***>
Subject: Re: [MetOffice/opsinputs] Update varobs and cx writers for visibility (PR #221)
This email was received from an external source. Always check sender details, links & attachments.
@matthewrmshin approved this pull request.
Ran OK in my environment. No failures detected for mo-bundle main build + ctest, and sith/malak kgo runs.
—
Reply to this email directly, view it on GitHub<#221 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB4I73KNSWJ5T3DO565QRXDZRYJWVAVCNFSM6AAAAABMSNKOV6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDENBSHE2TGNRRGY>.
You are receiving this because you were assigned.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub<#221 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAG52RI6HYFYIO53FAAZ3NLZRYK2NAVCNFSM6AAAAABMSNKOV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTG4YTIMZVG4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
This reverts commit b4efa39. Either the syntax is wrong or this is not allowed.
This change appears to require KGO changes for various |
The varobs writer now outputs visibility - since these are in the list of observed variables for both global and ukv yamls, I therefore expect both sets of varobs files to change. The changes here should not effect global surface cx files, though I can imagine that a change to a varobs file might somehow necessitate a change to a cx file. What exact differences do you see? |
Differences reported for these files: malak:
sith:
See outputs of these suites of mine: http://fcm1/cylc-review/suites?user=frsn&names=*oi221-kgo_glu*+*oi221-kgo_ukv |
These are as expected. Whilst the global varobs files now contain visibility (as the OPS ones always have), the global JOPA VAR task |
The changes made in this PR are necessary for the assimilation of visibility by VAR. There are three key changes:
qt2
) and aerosol (specifically with stash code 90, called "Total Aerosol (for Vis)").ObsValue/horizonalVisibility
values toVarField_logvis
.Updating the cx writer for outputting aerosol was non-trivial:
90
is the correct one to use for the calculation of background visibility in VAR.src/opsinputs/opsinputs_fill_mod.F90
for details. This required special case code.@adammaycock this was the code you were helping me to debug last month: the issue was an incorrect stash code causing the necessary select case to be skipped over.
@ss421 I have now confirmed that I need the following for VAR to run, so please don't exclude them from FieldNameCompare.xlsx:
NOTE: the ukv surface KGO will need to be remade once this is merged.