-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ingest and dump MRMS radar data for RTMA model #19
Comments
The web link for the MRMS, radarl2, and staingest packages:
A couple of important information about the radarl2 package and processing:
|
MRMS/radarl2 variables information: There is MRMS data available on WCOSS2 in the following directory: /lfs/h1/ops/prod/dcom/ldmdata/obs/upperair/mrms, in grib2 format. A few netCDF files (pe0076.conv_uv_03.nc4 and Gridded_ref.nc) were used from the following directory, /lfs/h2/emc/stmp/Shun.Liu/stmp/tmpnwprd/rrfs_a/2022101800, to get information about the variables: |
@PraveenKumar-NOAA, These are the variables available from MRMS. If you list each dir, you'll see these files come every few minutes, like Shun told us. |
MRMS data directory structures on WCOSS2: There are five mrms sub-directories named as:
List of variables from mrms/conus grib2 files:
|
@PraveenKumar-NOAA , it is not clear to me what the "pe0076.conv_uv_03.nc4 and Gridded_ref.nc" files are, i.e. how were they generated - are they output from Shun's code? are they the netcdf version of the grib2-format files on wcoss2 ? |
I am pretty sure that |
@ilianagenkova these files are output from Shun's code taken from the following directory: /lfs/h2/emc/stmp/Shun.Liu/stmp/tmpnwprd/rrfs_a/2022101800), and I don't know how he generated these. But these files are not a direct product of the MRMS data. @JacobCarley-NOAA thank you for the clarification. |
But we don't care about Shun's code, do we? I thought he generates nexrad
dumps with lower res data, and they have only a couple of variables.
The reason we have the MRMS ingest task is to give the users high-res radar
data and more parameters (atmos state variables). So again, we need to know
what's in the:
$DCOMROOT/ldmdata/obs/upperair/mrms/conus/* files.
Go through the list of files, for example -
$DCOMROOT/ldmdata/obs/upperair/mrms/conus/MergedReflectivityQCComposite/MergedReflectivityQCComposite_00.50_20221122-165238.grib2.gz
and pull the variables from the grib2 files.
Some variables we will simply ingest, while others might need to be
computed, is my understanding.
…On Tue, Nov 22, 2022 at 10:15 AM PraveenKumar-NOAA ***@***.***> wrote:
@ilianagenkova <https://github.com/ilianagenkova> these files are output
from Shun's code taken from the following directory:
/lfs/h2/emc/stmp/Shun.Liu/stmp/tmpnwprd/rrfs_a/2022101800), and I don't
know how he generated these. But these files are not a direct product of
the MRMS data.
@JacobCarley-NOAA <https://github.com/JacobCarley-NOAA> thank you for the
clarification.
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOC4YXTDN5OI5PO73RGHTULWJTWTNANCNFSM6AAAAAAQ5AZ4FQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@ilianagenkova We might be conflating a couple different things. |
@ilianagenkova @JacobCarley-NOAA I extracted variables information from the MRMS data, which are listed in the following document, https://docs.google.com/document/d/1Uud8JMDnMLgk_kkMPZCJm1HaAchYurjDl1W38YBk8Bg/edit?pli=1. There are four main variables, latitude, longitude, time, and altitude_above_msl, and I think the rest are the computed ones. @ilianagenkova I listed variables information from Shun's code, i.e. radarl2 package at the very beginning., at that time I was not sure how to proceed. No, we don't care about Shun's code as far as my understanding. |
Next steps:
|
Once Radial Wind data is available, the next step will be:
|
Requested sample radial wind data from MRMS folks. |
This issue is on hold until the radial wind data is provided on WCOSS2 by the Dataflow team or radial wind data samples are provided by the MRMS folks. |
@JacobCarley-NOAA @ilianagenkova most of the data required by RTMA users is already available on WCOSS2. If no further action is needed, this issue can be closed. Thank you. |
@PraveenKumar-NOAA I missed the tag in GitHub - apologies. The reflectivity files are available - but are the winds also available? |
@JacobCarley-NOAA no, a Dataflow ticket is opened for the wind. A request is also made for the sample wind data. |
Thanks Praveen - makes sense. Was the request for the sample wind data made directly to the MRMS group? Am wondering if we ought to follow up if it's been a little while. |
Yes, it has been made directly to the MRMS group. I will send a reminder again. |
@JacobCarley-NOAA , I had advised @PraveenKumar-NOAA to make inquiries every two weeks at first, then we cut them down to monthly...I believe Anthony is very aware of our interest in the radial wind by now :) |
@ilianagenkova Ha! Hopefully he hasn't set up a spam filter for us :-) |
@ilianagenkova finally with the help of Jacob and Jian, I got the sample radial wind data, which is located into the following folder, EMC_radial_velocity. |
The sample radial velocity (Vr) data (both "raw" and dealiased) is from KCXX radar. The data are in radar coordinates and in NetCDF format. There are also example images of the raw ("Aliased Velocity") and dealiased ("Velocity") fields in this folder for the reference. Additional information about the data:
|
This issue is on hold until we get further input from the MRMS folks. |
MRMS radar data was requested by RTMA model team.
Work plan
A) Gather info on data (provider, format, contents)
B) Gather info on user/RTMA team needs (variables, formatting, frequency, etc)
C) Leverage off radarl2 package - how is data pre-processed, what can we learn from it
D) Leverage off existing satingest routines to write MRMS ingests code and generate tanks
E) Expand obsproc to dump MRMS data tanks
@PraveenKumar-NOAA, If you copy/paste the info we gathered already (from emails), you will have one-stop document to refer to.
The text was updated successfully, but these errors were encountered: