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

radar data assimilation #37

Closed
timhoar opened this issue Jun 30, 2020 · 1 comment
Closed

radar data assimilation #37

timhoar opened this issue Jun 30, 2020 · 1 comment
Labels
Discussion Requires team discussion Documentation Improvements or additions to documentation Emailed Issue Was originally emailed to DAReS team FAQ Frequently asked questions Question Further information is requested

Comments

@timhoar
Copy link
Contributor

timhoar commented Jun 30, 2020

Ed note: This issue was originally an email and is being manually ported over to GitHub.

Dear DART Team;

I have a query related to radar data assimilation. It is found from the DART documentation that only NEXRAD data can be assimilated using create_obs_radar_sequence. But I want to use our own Doppler Weather Radar data. I have converted the binary data to "lat, long, Reflectivity, Radial Velocity, Elevation" format. Now, what do I need to do so that the data can be read by the DART module?

Your suggestions will be highly appreciated.

@timhoar timhoar added Good First Issue Good for newcomers Question Further information is requested Discussion Requires team discussion labels Jun 30, 2020
@timhoar
Copy link
Contributor Author

timhoar commented Jun 30, 2020

Thank you for your interest in DART. We offer limited support for the conversion of radar observations to the DART observation format. Still, there are avenues that can allow you to get there. As an end goal, you'll want to have radar observations that have been quality controlled to remove non-meteorological scatterers and other artifacts, and reduce the native data resolution to something closer to twice the expected horizontal grid spacing in your model (e.g., with 3 km grid spacing, radar observations every 6 km) interpolated along the sweep plane. Reflectivity observations are often partitioned into two types - regular reflectivity observations, and clear air reflectivity observations (where no radar echoes are observed). Quality control is best done with the raw data, so I trust you have an ability to do so on your end. Once quality control is applied, a tool for the interpolation and conversion to DART observation format is provided by the OPAWS utility: https://code.google.com/archive/p/opaws/

Before you can use the OPAWS tool, you'll need to convert your native data format into something that can be read by OPAWS (e.g., DORADE sweep files). You can see if the RADX utility is helpful for this: https://ral.ucar.edu/projects/titan/docs/radial_formats/radx.html

Assuming you are using WRF, you'll need to make some code modifications to allow for forward operator calculations. For reflectivity, most of the available microphysics schemes have built in capability to output reflectivity, assuming a 10-cm wavelength. If you are not using an S-band radar, be aware that attenuation is not accounted for in the built-in reflectivity operator. For radial velocity, you'll need to also generate a new diagnostic field, terminal fall velocity. There is very limited support for fall velocity in WRF, although it is partially supported in the Thompson microphysics scheme (though you would still need to modify WRF code to get this diagnostic output to history files). With these two fields available in your WRF history files, you can add them to your DART wrf_state_variables list and should be ready to assimilate radar observations. Before assimilating radar observations, you'll also want to use special localization for radar observations, typically 12-24 km. If you leave range-folding in your radar observations, you'll need to build the special version of DART that unfolds the velocity observations on-the-fly.

@timhoar timhoar added Emailed Issue Was originally emailed to DAReS team and removed Good First Issue Good for newcomers labels Jul 1, 2020
@timhoar timhoar added Documentation Improvements or additions to documentation FAQ Frequently asked questions labels Jul 8, 2020
hkershaw-brown pushed a commit that referenced this issue Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Requires team discussion Documentation Improvements or additions to documentation Emailed Issue Was originally emailed to DAReS team FAQ Frequently asked questions Question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants