Repository navigation
2113 nimrod regrid #2269
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
base: main
Are you sure you want to change the base?
2113 nimrod regrid #2269
Changes from all commits
0b52c83
391c433
8a091ec
a1fc575
4cfbdfd
fa0f7cd
d6d441b
93825e2
99cc537
3268736
33a20f2
4b81b55
493ddfa
79d9476
da7576d
2d973f2
a9e0d13
6073ff9
7acc815
36dd595
ae5ba6c
596cace
b4390e1
0b096ae
5323901
282e416
d2aff8b
2c7731d
5c0407f
39dcac2
2d3e72d
0901dd3
9870de7
20f101d
99478b6
6544638
bac16f5
5a6e228
5e0aa20
fcafe65
b327135
2327952
ae2380d
24701dc
e388bcc
141c246
145aab7
175101b
b5b7b80
f048348
26bb073
d73552e
0bcacf8
d0c00fe
c5683f3
0e33a0c
a2433b4
771adf7
aa56edf
d45db95
6c0a7ad
48192ab
5bfa342
d8b2c68
f40b3a6
0775861
ad49d00
ae32363
6d06605
5ebe827
0f66a89
caf8c62
103ada3
8af3a65
4e42c4d
7af6139
a61ebfc
4875f8e
d0c2029
f691244
83ed54d
d52c766
6315d47
cdee488
ea30b52
33a3ba0
86d2784
51fb232
9b4dcaa
b753505
d7b621c
3bfbe9c
1a0bcb4
d381a8e
465fc5b
d491106
660b776
e597460
65ed6d7
b2642c3
df5aace
fc74417
245f356
59c9546
66e37df
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -111,6 +111,8 @@ trigger=template variables=NIMROD_COMP_XKM: True; | |
| template variables=NIMROD_COMP_2KM: True; | ||
| template variables=NIMROD_WEIGHTS: True; | ||
| template variables=NIMROD_COMP_5MIN: True; | ||
| template variables=PROCESS_RADAR_2D: True; | ||
| template variables=PROCESS_RADAR_HISTOGRAMS: True; | ||
|
|
||
| [template variables=CARDINGTON_OBS] | ||
| ns=Observations | ||
|
|
@@ -223,8 +225,8 @@ title=Radar observations | |
|
|
||
| [template variables=NIMROD_COMP_XKM] | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What does XKM actually mean? Description suggests 5km?? |
||
| ns=Observations/Radar | ||
| title=UK Nimrod radar accumulated rainfall | ||
| description=Default UK Nimrod rainfall accumulation | ||
| title=UK Nimrod radar accumulated rainfall 5km gridding | ||
| description=5km gridded UK Nimrod rainfall accumulation | ||
| help=Switch to select default gridded UK Nimrod rainfall accumulation. | ||
| compulsory=true | ||
| type=python_boolean | ||
|
|
@@ -269,6 +271,28 @@ compulsory=true | |
| type=python_boolean | ||
| sort-key=nimrod-radar-7 | ||
|
|
||
| [template variables=PROCESS_RADAR_2D] | ||
| ns=Observations/Radar | ||
| title=Produce Nimrod 2D surface plots | ||
| description=Produce 2D surface plots of radar observations. | ||
| help=Switch to produce 2D surface plots utilising Nimrod radar observations. | ||
| Plots are produced of the 2D surface rainfall for each of the selected Nimrod sources. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. more precision needed: Nimrod provides rainfall amounts |
||
| Plots of the associated Nimrod weights fields are also produced. | ||
| compulsory=true | ||
| type=python_boolean | ||
| sort-key=nimrod-radar-8 | ||
|
|
||
| [template variables=PROCESS_RADAR_HISTOGRAMS] | ||
| ns=Observations/Radar | ||
| title=Produce Nimrod radar histograms | ||
| description=Produce histograms incorporating radar observations. | ||
| help=Switch to produce histograms utilising Nimrod radar observations. | ||
| The histograms will combine both model rainfall and radar observations. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This will likely change when lfric gives us accumulations as well, but worth being precise her that Nimrod gives as amounts as an accumulation for sum products and a 5min "snapshot" for the other product, whereas the models currently gives us rainfall_rate i.e. amount per time as a snapshot |
||
| The model rainfall variable is selected in the Rose tab Diagnostics/Surface (2D) fields. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this correct? Other code suggests rainfall variable is fixed, i.e. |
||
| compulsory=true | ||
| type=python_boolean | ||
| sort-key=nimrod-radar-9a | ||
|
|
||
| ################################################################ | ||
| # Cardington UK Research Observations | ||
| [ns=Observations/Cardington] | ||
|
|
||
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.
Do we really need the shift? Asking as we are loading radar data with a timestamp ending the hourly accumulation period. so we read an hourly accumulation for 11am which is representative for the accumulation from 10-11. Lfric gives us an instantaneous rainfall rate at 11. Apart from teh required conversions and getting accums from lfric isn't the timestamp actually correct?
Uh oh!
There was an error while loading. Please reload this page.
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.
I have been comparing the lfric files containing surface_microphysical_rainfall_rate i.e. the timeproc files and the diagnostic files against UK Nimrod
LFRic: When fetching CYCLE_TASK_CYCLE_POINT=00:00:00
point [00:30:00, 01:30:00, 02:30:00]
bounds [00:00:00, 01:00:00] [01:00:00:00, 02:00:00][02:00:00,03:00:00 ]
point [01:00:00, 02:00:00, 03:00:00]
bounds [01:00:00, 01:00:00] [02:00:00, 02:00:00][03:00:00, 03:00:00]
hence timeproc gives a meaned (?) field on the halfway point and diagnostics gives a truly instantaneous point.
UKNimrod radar when fetching CYCLE_TASK_CYCLE_POINT=00:00:00
points [00:00:00]
bounds [23:00:00,00:00:00]
For fetching a filename for lfric and radar for CYCLE_TASk_CYCLE_POINT
Hence, we need to shift UK nimrod radar data filename by +1 to fetch the correpsonding time bounds between lfric and radar. I suspect that when outputting accumulations in lfric for a filename with CYCLE_TASK_CYCLE_POINT we need to check if the output bounds still start at [CYCLE_TASK_CYCLE_POINT, CYCLE_TASK_CYCLE_POINT+1] with a point at CYCLE_TASK_CYCLE_POINT+1 or if a point exists at CYCLE_TASK_CYCLE_POINT.
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.
So for now we require the +1 correction to CYCLE_TASK_CYCLE_POINT to fetch the correct radar file.