Lrose Wiki - User contributions [en]

Main Page

2022-07-26T22:59:01Z

Mmbell:

== '''LROSE: The Lidar Radar Open Software Environment''' ==

=== Overview ===
[[File:Topaz-small.png|thumb|right|'''Topaz''']]
The current LROSE release is called '''“Topaz”''' (a bright hot pink rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''[http://wiki.lrose.net/index.php?title=Main_Page#Convert Convert], [http://wiki.lrose.net/index.php?title=Main_Page#Display Display], [http://wiki.lrose.net/index.php?title=Main_Page#Quality_Control QC], [http://wiki.lrose.net/index.php?title=Main_Page#Grid Grid], [http://wiki.lrose.net/index.php?title=Main_Page#Echo Echo], and [http://wiki.lrose.net/index.php?title=Main_Page#Wind Winds].'' '''Topaz''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

Some highlights for Topaz:
* This release contains further refinements in radial data format translation.
* The cmake-based build option is available.
* Packages are available for Centos, Ubuntu, Fedora 32, 33, 34, Alma Linux, Suse.
* Only dependent on the HDF5 C library, the C++ library is now included in libs/Ncxx in LROSE.
* HawkEdit is now a beta version, and has undergone considerable testing from users.

Topaz can be compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

We encourage users to [http://lrose.net/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[http://lrose.net/help.html Help] can be obtained by posting issues directly to the lrose-cyclone Github repository, via our help mailing list, or Discourse user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

=== Citations for LROSE tools ===

Please cite the version of LROSE tools you use for publication. If you are unsure of the version, please cite the latest stable release.

* '''[https://doi.org/10.5281/zenodo.6909479 lrose-topaz, 2022]''': Michael M. Bell, Michael Dixon, Wen-Chau Lee, Brenda Javornik, Jennifer DeHart, Ting-Yu Cha, and Alex DesRosiers. (2022). nsf-lrose/lrose-topaz: lrose-topaz stable final release 20220222 (lrose-topaz-2022022). Zenodo. https://doi.org/10.5281/zenodo.6909479
* '''[https://doi.org/10.5281/zenodo.5523312 lrose-elle, 2021]''': Michael M. Bell, Michael Dixon, Wen-Chau Lee, Brenda Javornik, Jennifer DeHart, & Ting-Yu Cha. (2021). nsf-lrose/lrose-elle: lrose-elle stable final release 20210312 (lrose-elle-20210312). Zenodo. https://doi.org/10.5281/zenodo.5523312
* '''[https://doi.org/10.5281/zenodo.3604387 lrose-cyclone, 2020]''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Bruno Melli, Jennifer DeHart and Ting-Yu Cha (2020). nsf-lrose/lrose-cyclone: lrose-cyclone release 20200110 (lrose-cyclone-20200110). Zenodo. https://doi.org/10.5281/zenodo.3604387
* '''[https://doi.org/10.5281/zenodo.2532758 lrose-blaze, 2019]''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Bruno Melli, Jennifer DeHart and Ting-Yu Cha (2019). nsf-lrose/lrose-blaze: lrose-blaze-20190105 (lrose-blaze-20190105). Zenodo. https://doi.org/10.5281/zenodo.2532758

=== Installation Instructions ===

*'''Homebrew Installation'''
** '''[https://github.com/NCAR/lrose-core/blob/master/docs/download/install_using_homebrew.mac_osx.md Mac Homebrew installation]''' - For Native applications on the Mac, the recommended method is to use Homebrew. The formula contains all the necessary dependencies and builds instructions.

* '''Source Installation''' - Intended for users who wish to do a manual build or build in a non-standard location. Source compilation is best performed using a supplied Python script.
** '''[https://github.com/NCAR/lrose-core/blob/master/docs/build/LROSE_build_main_page.md Build system]''' - For LINUX and MAC OS cmake/autoconf/manual builds and code development

* '''CIDD Binary Installation'''
** '''[https://github.com/NCAR/lrose-core/blob/master/docs/download/CIDD_binary_download_and_install.linux.md CIDD Binary Release]''' - CIDD depends on a 32-bit build, which complicates the build and install for the core. The CIDD display application is not included in the standard lrose-core packages (above).

=== Tutorials ===

* '''quick start'''
** '''[http://wiki.lrose.net/index.php/lrose_quickstart lrose quickstart tutorial]''' - Go over the basics to get up and running quickly with LROSE.

* '''echo tutorials'''
** '''[http://wiki.lrose.net/index.php/elle_basic basic elle echo tutorial]''' - Go through the basic steps necessary to convert a raw radar file to CfRadial, calculate Kdp and three-dimensional rain rate, and estimate the surface rainfall. The purpose of this tutorial is to confirm that the install process was successful and that some programs are working.
** '''[http://wiki.lrose.net/index.php/elle_basic_plus basic+ elle echo tutorial]''' - Similar to the basic elle tutorial with the added tasks of downloading GFS analysis from which to estimate a sounding near the radar and running the RadxBeamBlock application.
** '''[http://wiki.lrose.net/index.php/elle_full full elle echo tutorial]''' - This tutorial assumes the user has radar data downloaded in an [http://wiki.lrose.net/index.php/RadxConvert acceptable radar format] and walks through the most important parameters that need to be edited to run the Quantitative Precipitation Estimation (QPE) workflow.

* '''grid tutorial'''
** '''[http://wiki.lrose.net/index.php/elle_grid elle regrid and convective/stratiform tutorial]''' - Convert raw NEXRAD data to the cfradial format and then interpolate to a cartesian grid and applies a convective stratiform separation algorithm.

* '''wind tutorial'''
** '''[http://wiki.lrose.net/index.php/vortrac_tutorial VORTRAC tutorial]''' - run VORTRAC to retrieve the winds using the GBVTD/GVTD algorithm from a single Doppler radar data.

* '''CSU Radartools tutorial'''
** '''[http://wiki.lrose.net/index.php/csu_radartools_tutorial CSU-Radartools tutorial]''' - Step through the processing of a raw radar file through editing, QC and gridding using LROSE and CSU-Radartools

* ''' Airborne radar navigation correction tutorial'''
** '''[https://github.com/csu-tropical/Airborne-Radar-Navigation-Correction/blob/main/Tutorial.md Airborne radar navigation correction]''' - Go through the steps of applying navigation correction on airborne radar data. Airborne radar navigation correction package can be found [https://github.com/csu-tropical/Airborne-Radar-Navigation-Correction here].

=== Toolsets ===
In the current release, the following tools are available:

==== Convert ====

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''[http://wiki.lrose.net/index.php/RadxBufr RadxBufr]''' - Convert Bufr format to CfRadial NetCDF format

==== Display ====

* '''[http://wiki.lrose.net/index.php/HawkEye HawkEye]''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

==== Quality Control ====

* '''[http://wiki.lrose.net/index.php/RadxDiffFields RadxDiffFields]''' - Compare two fields in different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxDiffVol RadxDiffVol]''' - Compare two volumes in different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxMergeFields RadxMergeFields]''' - Merge fields from different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxFilter RadxFilter]''' - Perform simple filtering operations
* '''[http://wiki.lrose.net/index.php/RadxPersistentClutter RadxPersistentClutter]''' - Create a mask for persistent ground clutter
* '''[http://wiki.lrose.net/index.php/RadxDealias RadxDealias]''' - Dealias single-Doppler data
* '''[http://wiki.lrose.net/index.php/RadxQc RadxQc]''' - General quality control
* '''[http://wiki.lrose.net/index.php/IntfRemove IntfRemove]''' - Identify and remove interference in Titan data
* '''[http://wiki.lrose.net/index.php/RadxModelQc RadxModelQc]''' - Filter Radx data
* '''[http://wiki.lrose.net/index.php/RadxClutMon RadxClutMon]''' - Clutter analysis
* '''[http://wiki.lrose.net/index.php/TsCalAuto TsCalAuto]''' - Radar calibration analysis
* '''[http://wiki.lrose.net/index.php/RadarCal RadarCal]''' - Analyze calibration data
* '''[http://wiki.lrose.net/index.php/RadxSunMon RadxSunMon]''' - Search for sun spikes and perform solar analysis
* '''[http://wiki.lrose.net/index.php/SunCal SunCal]''' - Analyze time series data from sun scans

==== Grid ====

* '''[http://wiki.lrose.net/index.php/Radx2Grid Radx2Grid]''' - Gridding and interpolation of ground-based radar data

==== Echo ====

* '''[http://wiki.lrose.net/index.php/RadxKdp RadxKdp]''' - KDP and Attenuation calculations
* '''[http://wiki.lrose.net/index.php/RadxPid RadxPid]''' - KDP, Attenuation, and Particle Identification
* '''[http://wiki.lrose.net/index.php/RadxRate RadxRate]''' - KDP, Attenuation, PID, and Rain Rate
* '''[http://wiki.lrose.net/index.php/RadxQpe RadxQpe]''' - Accumulated Quantitative Precipitation Estimation
* '''[http://wiki.lrose.net/index.php/RadxHca RadxHca]''' - NEXRAD Hydrometeor Classification Algorithm
* '''[http://wiki.lrose.net/index.php/RateAccum RateAccum]''' - Accumulated Precipitation (''recommended'')
* '''[http://wiki.lrose.net/index.php/PrecipAccum PrecipAccum]''' - Accumulated Precipitation (''not recommended'')
* '''[http://wiki.lrose.net/index.php/RadxBeamBlock RadxBeamBlock]''' - Beam Blockage Estimation
* '''[http://wiki.lrose.net/index.php/ConvStrat ConvStrat]''' - Identify convective and stratiform regions in Cartesian radar volume
* '''[http://wiki.lrose.net/index.php/RadxMesoCyclone RadxMesoCyclone]''' - Identify mesocyclones in radar data
* '''[http://wiki.lrose.net/index.php/QpeVerify QpeVerify]''' - Compare radar-derived and observed precipitation accumulation
* '''[http://wiki.lrose.net/index.php/RefractCompute RefractCompute]''' - Compute refractivity
* '''[http://wiki.lrose.net/index.php/RefractCalib RefractCalib]''' - Create calibration file used by RefractCompute
* '''[http://wiki.lrose.net/index.php/CalcMoisture CalcMoisture]''' - Calculate moisture fields from refractivity
* '''[http://wiki.lrose.net/index.php/Titan Titan]''' - Thunderstorm Identification, Tracking, Analysis, and Nowcasting application
* '''[http://wiki.lrose.net/index.php/Tracks2Ascii Tracks2Ascii]''' - Print out storm and track data in ASCII format
* '''[http://wiki.lrose.net/index.php/Tstorms2Xml Tstorms2Xml]''' - Convert storms data to XML or Spdb
* '''[http://wiki.lrose.net/index.php/StormInitLocation StormInitLocation]''' - Write out the initiation location of significant storms
* '''[http://wiki.lrose.net/index.php/ScaleSep ScaleSep]''' - Separate a radar image into different spatial scales
* '''[http://wiki.lrose.net/index.php/Colide Colide]''' - Detect and extrapolate boundaries
* '''[http://wiki.lrose.net/index.php/ctrec ctrec]''' - Track echo motion
* '''[http://wiki.lrose.net/index.php/Rview Rview]''' - Visualize Titan data (spatially)
* '''[http://wiki.lrose.net/index.php/TimeHist TimeHist]''' - Visualize Titan data (through time)

==== Wind ====

* '''[http://wiki.lrose.net/index.php/RadxEvad RadxEvad]''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/FRACTL FRACTL]''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/SAMURAI SAMURAI]''' - Variational multi-Doppler retrieval and analysis package
* '''[http://wiki.lrose.net/index.php/VORTRAC VORTRAC]''' - Vortex Objective Radar Tracking and Circulation single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/OpticalFlow OpticalFlow]''' - Estimate 2-D velocity of a radar field

== '''Practical Radar Meteorology''' ==

The material contained here is designed to supplement radar textbooks and course materials with scientific background on common procedures used in radar meteorology. When combined with the above tutorials and documentation, these practical guides will help apply LROSE tools for scientific applications.

# [http://wiki.lrose.net/index.php/Radx2Grid_Gridding_Options Cartesian Gridding of Polar Radar Data]
# [http://wiki.lrose.net/index.php/Radx2Grid_Convective_Stratiform Convective/Stratiform Partitioning]
# [http://wiki.lrose.net/index.php/KDP_estimation Kdp Calculation]
# [http://wiki.lrose.net/index.php/RadxRate_equations Rain Rate Calculations]
# [http://wiki.lrose.net/index.php/Estimated_Attenuation Attenuation Correction]
# [http://wiki.lrose.net/index.php/RadxPid_fuzzylogic Particle Identification using Fuzzy Logic]
# [http://wiki.lrose.net/index.php/RadxQpe_expanded Quantitative Precipitation Estimation]
# [http://wiki.lrose.net/index.php/RadxDealias_James_and_Houze_2001 Velocity Dealiasing]

== '''LROSE Workshops''' ==

=== LROSE AMS 2020 Mini Workshop ===
*'''[http://wiki.lrose.net/images/a/ae/LROSE_AMS_2020_Mini-Workshop_Agenda.pdf Meeting Notes]'''
*'''[http://wiki.lrose.net/images/8/89/Mmbell_LROSE_AMSannual2020_small.pdf LROSE Mini-Workshop Slides]'''
*'''[http://wiki.lrose.net/images/9/9c/LROSE-CycloneDoppler_small.pdf LROSE Cyclone Multi-Doppler Tutorial Slides]'''
*'''[http://wiki.lrose.net/images/0/09/HawkEye_Tutorial.pdf Brief Hawkeye Tutorial Slides]'''

=== LROSE Fall 2021 Virtual Workshop ===
*'''Meeting Notes'''
*'''[http://wiki.lrose.net/index.php/2021_Fall_Workshop_Videos Pre-recorded Videos]'''
*'''[http://wiki.lrose.net/index.php/2021_Fall_Workshop_Sessions Session Recordings]'''

Main Page

2021-07-20T20:16:37Z

Mmbell:

== '''LROSE: The Lidar Radar Open Software Environment''' ==

=== Overview ===

The current LROSE release is called '''“Elle”''' (a pink blend fragrant rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''[http://wiki.lrose.net/index.php?title=Main_Page#Convert Convert], [http://wiki.lrose.net/index.php?title=Main_Page#Display Display], [http://wiki.lrose.net/index.php?title=Main_Page#Quality_Control QC], [http://wiki.lrose.net/index.php?title=Main_Page#Grid Grid], [http://wiki.lrose.net/index.php?title=Main_Page#Echo Echo], and [http://wiki.lrose.net/index.php?title=Main_Page#Wind Winds].'' '''Elle''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

Elle can be compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

We encourage users to [http://lrose.net/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[http://lrose.net/help.html Help] can be obtained by posting issues directly to the lrose-cyclone Github repository, via our help mailing list, or Discourse user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

=== Citations for LROSE tools ===

Please cite the version of LROSE tools you use for publication. If you are unsure of the version, please cite the latest stable release.

* '''lrose-elle, 2021''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Jennifer DeHart and Ting-Yu Cha (2021). nsf-lrose/lrose-elle: lrose-elle-20210216.
* '''[https://doi.org/10.5281/zenodo.3604387 lrose-cyclone, 2020]''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Bruno Melli, Jennifer DeHart and Ting-Yu Cha (2020). nsf-lrose/lrose-cyclone: lrose-cyclone-20200110. https://doi.org/10.5281/zenodo.3604387
* '''[https://doi.org/10.5281/zenodo.2532758 lrose-blaze, 2019]''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Bruno Melli, Jennifer DeHart and Ting-Yu Cha (2019). nsf‐lrose/lrose‐blaze: lrose‐blaze‐20190105. https://doi.org/10.5281/zenodo.2532758

=== Installation Instructions ===

*'''Homebrew Installation'''
** '''[http://wiki.lrose.net/index.php/Mac-Homebrew-Installation Mac Homebrew installation]''' - For Native applications on the Mac, the recommended method is to use Homebrew. The formula contains all the necessary dependencies and builds instructions.

* '''Source Installation''' - Intended for users who wish to do a manual build or build in a non-standard location. Source compilation is best performed using a supplied Python script.
** '''[https://github.com/NCAR/lrose-core/blob/master/docs/build/LROSE_build_main_page.md Build system]''' - For LINUX and MAC OS cmake/autoconf/manual builds and code development

* '''CIDD Binary Installation'''
** '''[https://github.com/NCAR/lrose-core/blob/master/docs/download/CIDD_binary_download_and_install.linux.md CIDD Binary Release]''' - CIDD depends on a 32-bit build, which complicates the build and install for the core. The CIDD display application is not included in the standard lrose-core packages (above).

=== Tutorials ===

* '''quick start'''
** '''[http://wiki.lrose.net/index.php/lrose_quickstart lrose quickstart tutorial]''' - Go over the basics to get up and running quickly with LROSE.

* '''echo tutorials'''
** '''[http://wiki.lrose.net/index.php/elle_basic basic elle echo tutorial]''' - Go through the basic steps necessary to convert a raw radar file to CfRadial, calculate Kdp and three-dimensional rain rate, and estimate the surface rainfall. The purpose of this tutorial is to confirm that the install process was successful and that some programs are working.
** '''[http://wiki.lrose.net/index.php/elle_basic_plus basic+ elle echo tutorial]''' - Similar to the basic elle tutorial with the added tasks of downloading GFS analysis from which to estimate a sounding near the radar and running the RadxBeamBlock application.
** '''[http://wiki.lrose.net/index.php/elle_full full elle echo tutorial]''' - This tutorial assumes the user has radar data downloaded in an [http://wiki.lrose.net/index.php/RadxConvert acceptable radar format] and walks through the most important parameters that need to be edited to run the Quantitative Precipitation Estimation (QPE) workflow.

* '''grid tutorial'''
** '''[http://wiki.lrose.net/index.php/elle_grid elle regrid and convective/stratiform tutorial]''' - Convert raw NEXRAD data to the cfradial format and then interpolate to a cartesian grid and applies a convective stratiform separation algorithm.

* '''wind tutorial'''
** '''[http://wiki.lrose.net/index.php/vortrac_tutorial VORTRAC tutorial]''' - run VORTRAC to retrieve the winds using the GBVTD/GVTD algorithm from a single Doppler radar data.

* '''CSU Radartools tutorial'''
** '''[http://wiki.lrose.net/index.php/csu_radartools_tutorial CSU-Radartools tutorial]''' - Step through the processing of a raw radar file through editing, QC and gridding using LROSE and CSU-Radartools

* ''' Airborne radar navigation correction tutorial'''
** '''[https://github.com/csu-tropical/Airborne-Radar-Navigation-Correction/blob/main/Tutorial.md Airborne radar navigation correction]''' - Go through the steps of applying navigation correction on airborne radar data. Airborne radar navigation correction package can be found [https://github.com/csu-tropical/Airborne-Radar-Navigation-Correction here].

=== Toolsets ===
In the current release, the following tools are available:

==== Convert ====

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''[http://wiki.lrose.net/index.php/RadxBufr RadxBufr]''' - Convert Bufr format to CfRadial NetCDF format

==== Display ====

* '''[http://wiki.lrose.net/index.php/HawkEye HawkEye]''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

==== Quality Control ====

* '''[http://wiki.lrose.net/index.php/RadxDiffFields RadxDiffFields]''' - Compare two fields in different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxDiffVol RadxDiffVol]''' - Compare two volumes in different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxMergeFields RadxMergeFields]''' - Merge fields from different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxFilter RadxFilter]''' - Perform simple filtering operations
* '''[http://wiki.lrose.net/index.php/RadxPersistentClutter RadxPersistentClutter]''' - Create a mask for persistent ground clutter
* '''[http://wiki.lrose.net/index.php/RadxDealias RadxDealias]''' - Dealias single-Doppler data
* '''[http://wiki.lrose.net/index.php/RadxQc RadxQc]''' - General quality control
* '''[http://wiki.lrose.net/index.php/IntfRemove IntfRemove]''' - Identify and remove interference in Titan data
* '''[http://wiki.lrose.net/index.php/RadxModelQc RadxModelQc]''' - Filter Radx data
* '''[http://wiki.lrose.net/index.php/RadxClutMon RadxClutMon]''' - Clutter analysis
* '''[http://wiki.lrose.net/index.php/TsCalAuto TsCalAuto]''' - Radar calibration analysis
* '''[http://wiki.lrose.net/index.php/RadarCal RadarCal]''' - Analyze calibration data
* '''[http://wiki.lrose.net/index.php/RadxSunMon RadxSunMon]''' - Search for sun spikes and perform solar analysis
* '''[http://wiki.lrose.net/index.php/SunCal SunCal]''' - Analyze time series data from sun scans

==== Grid ====

* '''[http://wiki.lrose.net/index.php/Radx2Grid Radx2Grid]''' - Gridding and interpolation of ground-based radar data

==== Echo ====

* '''[http://wiki.lrose.net/index.php/RadxKdp RadxKdp]''' - KDP and Attenuation calculations
* '''[http://wiki.lrose.net/index.php/RadxPid RadxPid]''' - KDP, Attenuation, and Particle Identification
* '''[http://wiki.lrose.net/index.php/RadxRate RadxRate]''' - KDP, Attenuation, PID, and Rain Rate
* '''[http://wiki.lrose.net/index.php/RadxQpe RadxQpe]''' - Accumulated Quantitative Precipitation Estimation
* '''[http://wiki.lrose.net/index.php/RadxHca RadxHca]''' - NEXRAD Hydrometeor Classification Algorithm
* '''[http://wiki.lrose.net/index.php/PrecipAccum PrecipAccum]''' - Accumulated Precipitation
* '''[http://wiki.lrose.net/index.php/RadxBeamBlock RadxBeamBlock]''' - Beam Blockage Estimation
* '''[http://wiki.lrose.net/index.php/ConvStrat ConvStrat]''' - Identify convective and stratiform regions in Cartesian radar volume
* '''[http://wiki.lrose.net/index.php/RadxMesoCyclone RadxMesoCyclone]''' - Identify mesocyclones in radar data
* '''[http://wiki.lrose.net/index.php/QpeVerify QpeVerify]''' - Compare radar-derived and observed precipitation accumulation
* '''[http://wiki.lrose.net/index.php/RefractCompute RefractCompute]''' - Compute refractivity
* '''[http://wiki.lrose.net/index.php/RefractCalib RefractCalib]''' - Create calibration file used by RefractCompute
* '''[http://wiki.lrose.net/index.php/CalcMoisture CalcMoisture]''' - Calculate moisture fields from refractivity
* '''[http://wiki.lrose.net/index.php/Titan Titan]''' - Thunderstorm Identification, Tracking, Analysis, and Nowcasting application
* '''[http://wiki.lrose.net/index.php/Tracks2Ascii Tracks2Ascii]''' - Print out storm and track data in ASCII format
* '''[http://wiki.lrose.net/index.php/Tstorms2Xml Tstorms2Xml]''' - Convert storms data to XML or Spdb
* '''[http://wiki.lrose.net/index.php/StormInitLocation StormInitLocation]''' - Write out the initiation location of significant storms
* '''[http://wiki.lrose.net/index.php/ScaleSep ScaleSep]''' - Separate a radar image into different spatial scales
* '''[http://wiki.lrose.net/index.php/Colide Colide]''' - Detect and extrapolate boundaries
* '''[http://wiki.lrose.net/index.php/ctrec ctrec]''' - Track echo motion
* '''[http://wiki.lrose.net/index.php/Rview Rview]''' - Visualize Titan data (spatially)
* '''[http://wiki.lrose.net/index.php/TimeHist TimeHist]''' - Visualize Titan data (through time)

==== Wind ====

* '''[http://wiki.lrose.net/index.php/RadxEvad RadxEvad]''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/FRACTL FRACTL]''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/SAMURAI SAMURAI]''' - Variational multi-Doppler retrieval and analysis package
* '''[http://wiki.lrose.net/index.php/VORTRAC VORTRAC]''' - Vortex Objective Radar Tracking and Circulation single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/OpticalFlow OpticalFlow]''' - Estimate 2-D velocity of a radar field

== '''Practical Radar Meteorology''' ==

The material contained here is designed to supplement radar textbooks and course materials with scientific background on common procedures used in radar meteorology. When combined with the above tutorials and documentation, these practical guides will help apply LROSE tools for scientific applications.

# [http://wiki.lrose.net/index.php/Radx2Grid_Gridding_Options Cartesian Gridding of Polar Radar Data]
# [http://wiki.lrose.net/index.php/Radx2Grid_Convective_Stratiform Convective/Stratiform Partitioning]
# [http://wiki.lrose.net/index.php/KDP_estimation Kdp Calculation]
# [http://wiki.lrose.net/index.php/RadxRate_equations Rain Rate Calculations]
# [http://wiki.lrose.net/index.php/Estimated_Attenuation Attenuation Correction]
# [http://wiki.lrose.net/index.php/RadxPid_fuzzylogic Particle Identification using Fuzzy Logic]
# [http://wiki.lrose.net/index.php/RadxQpe_expanded Quantitative Precipitation Estimation]
# [http://wiki.lrose.net/index.php/RadxDealias_James_and_Houze_2001 Velocity Dealiasing]

== '''LROSE Workshops''' ==

=== LROSE AMS 2020 Mini Workshop ===
*'''[http://wiki.lrose.net/images/a/ae/LROSE_AMS_2020_Mini-Workshop_Agenda.pdf Meeting Notes]'''
*'''[http://wiki.lrose.net/images/8/89/Mmbell_LROSE_AMSannual2020_small.pdf LROSE Mini-Workshop Slides]'''
*'''[http://wiki.lrose.net/images/9/9c/LROSE-CycloneDoppler_small.pdf LROSE Cyclone Multi-Doppler Tutorial Slides]'''
*'''[http://wiki.lrose.net/images/0/09/HawkEye_Tutorial.pdf Brief Hawkeye Tutorial Slides]'''

Main Page

2021-05-15T12:45:00Z

Mmbell:

== '''LROSE: The Lidar Radar Open Software Environment''' ==

=== Overview ===

The current LROSE release is called '''“Elle”''' (a pink blend fragrant rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''[http://wiki.lrose.net/index.php?title=Main_Page#Convert Convert], [http://wiki.lrose.net/index.php?title=Main_Page#Display Display], [http://wiki.lrose.net/index.php?title=Main_Page#Quality_Control QC], [http://wiki.lrose.net/index.php?title=Main_Page#Grid Grid], [http://wiki.lrose.net/index.php?title=Main_Page#Echo Echo], and [http://wiki.lrose.net/index.php?title=Main_Page#Wind Winds].'' '''Elle''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

Elle can be compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

We encourage users to [http://lrose.net/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[http://lrose.net/help.html Help] can be obtained by posting issues directly to the lrose-cyclone Github repository, via our help mailing list, or Discourse user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

=== Citations for LROSE tools ===

Please cite the version of LROSE tools you use for publication. If you are unsure of the version, please cite the latest stable release.

* '''lrose-elle, 2021''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Jennifer DeHart and Ting-Yu Cha (2021). nsf-lrose/lrose-elle: lrose-elle-20210216.
* '''[https://doi.org/10.5281/zenodo.3604387 lrose-cyclone, 2020]''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Bruno Melli, Jennifer DeHart and Ting-Yu Cha (2020). nsf-lrose/lrose-cyclone: lrose-cyclone-20200110. https://doi.org/10.5281/zenodo.3604387
* '''[https://doi.org/10.5281/zenodo.2532758 lrose-blaze, 2019]''': Michael M. Bell, Michael Dixon, Brenda Javornik, Wen-Chau Lee, Bruno Melli, Jennifer DeHart and Ting-Yu Cha (2019). nsf‐lrose/lrose‐blaze: lrose‐blaze‐20190105. https://doi.org/10.5281/zenodo.2532758

=== Installation Instructions ===

*'''Homebrew Installation'''
** '''[http://wiki.lrose.net/index.php/Mac-Homebrew-Installation Mac Homebrew installation]''' - For Native applications on the Mac, the recommended method is to use Homebrew. The formula contains all the necessary dependencies and builds instructions.

* '''Source Installation''' - Intended for users who wish to do a manual build or build in a non-standard location. Source compilation is best performed using a supplied Python script.
** '''[https://github.com/NCAR/lrose-core/blob/master/docs/build/LROSE_build_main_page.md Build system]''' - For LINUX and MAC OS cmake/autoconf/manual builds and code development

* '''CIDD Binary Installation'''
** '''[https://github.com/NCAR/lrose-core/blob/master/docs/download/CIDD_binary_download_and_install.linux.md CIDD Binary Release]''' - CIDD depends on a 32-bit build, which complicates the build and install for the core. The CIDD display application is not included in the standard lrose-core packages (above).

=== Tutorials ===

* '''quick start'''
** '''[http://wiki.lrose.net/index.php/lrose_quickstart lrose quickstart tutorial]''' - Go over the basics to get up and running quickly with LROSE.

* '''echo tutorials'''
** '''[http://wiki.lrose.net/index.php/elle_basic basic elle echo tutorial]''' - Go through the basic steps necessary to convert a raw radar file to CfRadial, calculate Kdp and three-dimensional rain rate, and estimate the surface rainfall. The purpose of this tutorial is to confirm that the install process was successful and that some programs are working.
** '''[http://wiki.lrose.net/index.php/elle_basic_plus basic+ elle echo tutorial]''' - Similar to the basic elle tutorial with the added tasks of downloading GFS analysis from which to estimate a sounding near the radar and running the RadxBeamBlock application.
** '''[http://wiki.lrose.net/index.php/elle_full full elle echo tutorial]''' - This tutorial assumes the user has radar data downloaded in an [http://wiki.lrose.net/index.php/RadxConvert acceptable radar format] and walks through the most important parameters that need to be edited to run the Quantitative Precipitation Estimation (QPE) workflow.

* '''grid tutorial'''
** '''[http://wiki.lrose.net/index.php/elle_grid elle regrid and convective/stratiform tutorial]''' - Convert raw NEXRAD data to the cfradial format and then interpolate to a cartesian grid and applies a convective stratiform separation algorithm.

* '''wind tutorial'''
** '''[http://wiki.lrose.net/index.php/vortrac_tutorial VORTRAC tutorial]''' - run VORTRAC to retrieve the winds using the GBVTD/GVTD algorithm from a single Doppler radar data.

=== Toolsets ===
In the current release, the following tools are available:

==== Convert ====

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''[http://wiki.lrose.net/index.php/RadxBufr RadxBufr]''' - Convert Bufr format to CfRadial NetCDF format

==== Display ====

* '''[http://wiki.lrose.net/index.php/HawkEye HawkEye]''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

==== Quality Control ====

* '''[http://wiki.lrose.net/index.php/RadxDiffFields RadxDiffFields]''' - Compare two fields in different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxDiffVol RadxDiffVol]''' - Compare two volumes in different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxMergeFields RadxMergeFields]''' - Merge fields from different CfRadial files
* '''[http://wiki.lrose.net/index.php/RadxFilter RadxFilter]''' - Perform simple filtering operations
* '''[http://wiki.lrose.net/index.php/RadxPersistentClutter RadxPersistentClutter]''' - Create a mask for persistent ground clutter
* '''[http://wiki.lrose.net/index.php/RadxDealias RadxDealias]''' - Dealias single-Doppler data

==== Grid ====

* '''[http://wiki.lrose.net/index.php/Radx2Grid Radx2Grid]''' - Gridding and interpolation of ground-based radar data

==== Echo ====

* '''[http://wiki.lrose.net/index.php/RadxKdp RadxKdp]''' - KDP and Attenuation calculations
* '''[http://wiki.lrose.net/index.php/RadxPid RadxPid]''' - KDP, Attenuation, and Particle Identification
* '''[http://wiki.lrose.net/index.php/RadxRate RadxRate]''' - KDP, Attenuation, PID, and Rain Rate
* '''[http://wiki.lrose.net/index.php/RadxQpe RadxQpe]''' - Accumulated Quantitative Precipitation Estimation
* '''[http://wiki.lrose.net/index.php/PrecipAccum PrecipAccum]''' - Accumulated Precipitation
* '''[http://wiki.lrose.net/index.php/RadxBeamBlock RadxBeamBlock]''' - Beam Blockage Estimation

==== Wind ====

* '''[http://wiki.lrose.net/index.php/RadxEvad RadxEvad]''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/FRACTL FRACTL]''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/SAMURAI SAMURAI]''' - Variational multi-Doppler retrieval and analysis package
* '''[http://wiki.lrose.net/index.php/VORTRAC VORTRAC]''' - Vortex Objective Radar Tracking and Circulation single-Doppler retrieval

==== Other ====

* '''[http://wiki.lrose.net/index.php/RadarCal RadarCal]''' - Analyze calibration data

== '''Practical Radar Meteorology''' ==

The material contained here is designed to supplement radar textbooks and course materials with scientific background on common procedures used in radar meteorology. When combined with the above tutorials and documentation, these practical guides will help apply LROSE tools for scientific applications.

# [http://wiki.lrose.net/index.php/Radx2Grid_Gridding_Options Cartesian Gridding of Polar Radar Data]
# [http://wiki.lrose.net/index.php/Radx2Grid_Convective_Stratiform Convective/Stratiform Partitioning]
# [http://wiki.lrose.net/index.php/RadxKdp Kdp Calculation]
# [http://wiki.lrose.net/index.php/RadxRate_equations Rain Rate Calculations]
# [http://wiki.lrose.net/index.php/Estimated_Attenuation Attenuation Correction]
# [http://wiki.lrose.net/index.php/RadxPid_fuzzylogic Particle Identification using Fuzzy Logic]
# [http://wiki.lrose.net/index.php/RadxQpe_expanded Quantitative Precipitation Estimation]
# [http://wiki.lrose.net/index.php/RadxDealias_James_and_Houze_2001 Velocity Dealiasing]

== '''LROSE Workshops''' ==

=== LROSE AMS 2020 Mini Workshop ===
*'''[http://wiki.lrose.net/images/a/ae/LROSE_AMS_2020_Mini-Workshop_Agenda.pdf Meeting Notes]'''
*'''[http://wiki.lrose.net/images/8/89/Mmbell_LROSE_AMSannual2020_small.pdf LROSE Mini-Workshop Slides]'''
*'''[http://wiki.lrose.net/images/9/9c/LROSE-CycloneDoppler_small.pdf LROSE Cyclone Multi-Doppler Tutorial Slides]'''
*'''[http://wiki.lrose.net/images/0/09/HawkEye_Tutorial.pdf Brief Hawkeye Tutorial Slides]'''

MediaWiki:Sidebar

2020-07-08T21:16:38Z

Mmbell:

Main Page

2019-08-06T06:17:18Z

Mmbell: /* The Lidar Radar Open Software Environment */

= '''LROSE''' =

== The Lidar Radar Open Software Environment ==

[https://zenodo.org/badge/latestdoi/199713573 [[File:https://zenodo.org/badge/199713573.svg|DOI]]]

The current LROSE release is called '''“Cyclone”''' (a bright red rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''Convert, Display, QC, Grid, Echo, and Winds''

Cyclone can be used from a ‘Virtual Toolbox’ using Docker and a wrapper script, or compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

Full documentation for Cyclone is available on the [https://lrose.net LROSE website]

We encourage users to [https://lrose.net/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[https://lrose.net/help.html Help] can be obtained by posting issues directly to the lrose-cyclone Github repository, via our help mailing list, or Discourse user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

'''Cyclone''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

In the current release, the following tools are available:

== Convert ==

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''RadxBufr''' - Convert Bufr format to CfRadial NetCDF format

== Display ==

* '''[http://wiki.lrose.net/index.php/HawkEye HawkEye]''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

== Quality Control ==

* '''RadxDiffFields''' - Compare two fields in different CfRadial files
* '''RadxDiffVol''' - Compare two volumes in different CfRadial files
* '''RadxMergeFields''' - Merge fields from different CfRadial files
* '''RadxFilter''' - Perform simple filtering operations
* '''RadxPersistentClutter''' - Create a mask for persistent ground clutter

== Grid ==

* '''[http://wiki.lrose.net/index.php/Radx2Grid Radx2Grid]''' - Gridding and interpolation of ground-based radar data

== Echo ==

* '''[http://wiki.lrose.net/index.php/RadxKdp RadxKdp]''' - KDP and Attenuation calculations
* '''[http://wiki.lrose.net/index.php/RadxPid RadxPid]''' - KDP, Attenuation, and Particle Identification
* '''[http://wiki.lrose.net/index.php/RadxRate RadxRate]''' - KDP, Attenuation, PID, and Rain Rate
* '''[http://wiki.lrose.net/index.php/RadxQpe RadxQpe]''' - Accumulated Quantitative Precipitation Estimation
* '''[http://wiki.lrose.net/index.php/RadxBeamBlock RadxBeamBlock]''' - Beam Blockage Estimation

== Wind ==

* '''RadxEvad''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/FRACTL FRACTL]''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/SAMURAI SAMURAI]''' - Variational multi-Doppler retrieval and analysis package
* '''[http://wiki.lrose.net/index.php/VORTRAC VORTRAC]''' - Vortex Objective Radar Tracking and Circulation single-Doppler retrieval

Main Page

2019-08-06T06:16:46Z

Mmbell:

= '''LROSE''' =

== The Lidar Radar Open Software Environment ==

[https://zenodo.org/badge/latestdoi/199713573 [[File:https://zenodo.org/badge/199713573.svg|DOI]]]

The current LROSE release is called '''“Cyclone”''' (a bright red rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''Convert, Display, QC, Grid, Echo, and Winds''

Blaze can be used from a ‘Virtual Toolbox’ using Docker and a wrapper script, or compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

Full documentation for Cyclone is available on the [https://lrose.net LROSE website]

We encourage users to [https://lrose.net/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[https://lrose.net/help.html Help] can be obtained by posting issues directly to the lrose-cyclone Github repository, via our help mailing list, or Discourse user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

'''Cyclone''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

In the current release, the following tools are available:

== Convert ==

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''RadxBufr''' - Convert Bufr format to CfRadial NetCDF format

== Display ==

* '''[http://wiki.lrose.net/index.php/HawkEye HawkEye]''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

== Quality Control ==

* '''RadxDiffFields''' - Compare two fields in different CfRadial files
* '''RadxDiffVol''' - Compare two volumes in different CfRadial files
* '''RadxMergeFields''' - Merge fields from different CfRadial files
* '''RadxFilter''' - Perform simple filtering operations
* '''RadxPersistentClutter''' - Create a mask for persistent ground clutter

== Grid ==

* '''[http://wiki.lrose.net/index.php/Radx2Grid Radx2Grid]''' - Gridding and interpolation of ground-based radar data

== Echo ==

* '''[http://wiki.lrose.net/index.php/RadxKdp RadxKdp]''' - KDP and Attenuation calculations
* '''[http://wiki.lrose.net/index.php/RadxPid RadxPid]''' - KDP, Attenuation, and Particle Identification
* '''[http://wiki.lrose.net/index.php/RadxRate RadxRate]''' - KDP, Attenuation, PID, and Rain Rate
* '''[http://wiki.lrose.net/index.php/RadxQpe RadxQpe]''' - Accumulated Quantitative Precipitation Estimation
* '''[http://wiki.lrose.net/index.php/RadxBeamBlock RadxBeamBlock]''' - Beam Blockage Estimation

== Wind ==

* '''RadxEvad''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/FRACTL FRACTL]''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/SAMURAI SAMURAI]''' - Variational multi-Doppler retrieval and analysis package
* '''[http://wiki.lrose.net/index.php/VORTRAC VORTRAC]''' - Vortex Objective Radar Tracking and Circulation single-Doppler retrieval

Main Page

2019-08-06T06:15:01Z

Mmbell: /* The Lidar Radar Open Software Environment */

= '''LROSE''' =

== The Lidar Radar Open Software Environment ==

[https://zenodo.org/badge/latestdoi/199713573 [[File:https://zenodo.org/badge/199713573.svg|DOI]]]

The current LROSE release is called '''“Cyclone”''' (a bright red rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''Convert, Display, QC, Grid, Echo, and Winds''

Blaze can be used from a ‘Virtual Toolbox’ using Docker and a wrapper script, or compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

Full documentation for Cyclone is available on the [https://lrose.net LROSE website]

We encourage users to [https://lrose.net/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[https://lrose.net/help.html Help] can be obtained by posting issues directly to the lrose-cyclone Github repository, via our help mailing list, or Discourse user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

'''Cyclone''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

In the current release, the following tools are available:

== Convert ==

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''RadxBufr''' - Convert Bufr format to CfRadial NetCDF format

== Display ==

* '''[http://wiki.lrose.net/index.php/HawkEye HawkEye]''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

== Grid ==

* '''[http://wiki.lrose.net/index.php/Radx2Grid Radx2Grid]''' - Gridding and interpolation of ground-based radar data

== Echo ==

* '''[http://wiki.lrose.net/index.php/RadxKdp RadxKdp]''' - KDP and Attenuation calculations
* '''[http://wiki.lrose.net/index.php/RadxPid RadxPid]''' - KDP, Attenuation, and Particle Identification
* '''[http://wiki.lrose.net/index.php/RadxRate RadxRate]''' - KDP, Attenuation, PID, and Rain Rate
* '''[http://wiki.lrose.net/index.php/RadxQpe RadxQpe]''' - Accumulated Quantitative Precipitation Estimation
* '''[http://wiki.lrose.net/index.php/RadxBeamBlock RadxBeamBlock]''' - Beam Blockage Estimation

== Wind ==

* '''RadxEvad''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/FRACTL FRACTL]''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/SAMURAI SAMURAI]''' - Variational multi-Doppler retrieval and analysis package
* '''[http://wiki.lrose.net/index.php/VORTRAC VORTRAC]''' - Vortex Objective Radar Tracking and Circulation single-Doppler retrieval

SAMURAI

2019-07-16T18:46:36Z

Mmbell: Created page with "= SAMURAI Users Manual 1.0 = == Spline Analysis at Mesoscale Utilizing Radar and Aircraft Instrumentation == SAMURAI is a variational analysis technique developed based prim..."

= SAMURAI Users Manual 1.0 =

== Spline Analysis at Mesoscale Utilizing Radar and Aircraft Instrumentation ==

SAMURAI is a variational analysis technique developed based primarily on the work of Ooyama (1987), Ooyama (2002) and Gao et al.(2004). The SAMURAI analysis yields a maximum likelihood estimate of the atmospheric state for a given set of observations and error estimates by minimizing a variational cost function.

The technique has several advantages over traditional objective analysis techniques, including:

* observational error specifications for different instrumentation
* more complex observation operators for remote sensing data
* the addition of balance constraints such as mass continuity
* including a priori background estimates of the atmospheric state when available.

A distinguishing characteristic of the SAMURAI technique compared to other variational solvers is that the analysis can be performed directly in an axisymmetric cylindrical coordinate system or in a 3D Cartesian coordinate system. The two-dimensional solver improves the computational efficiency and minimizes potential errors in mass conservation that arise when interpolating from a three-dimensional domain.

Another distinguishing characteristic from other variational solvers is the use of a Galerkin approach, which is similar to the Fourier spectral transform but uses the cubic B-spline as a basis Ooyama (2002). The disadvantage of the B-spline basis is that it is not orthogonal and therefore requires an extra matrix to obtain the spline coefficients, but this is a fair trade-off with its other desirable characteristics. The basis is computationally efficient and continuously differentiable to second order, allowing for efficient, accurate interpolation to observation locations, flexible incorporation of boundary conditions, and high numerical accuracy of kinematic derivatives.

The analysis is performed in a manner similar to the spectral transform method Machenhauer (1979), transforming to and from the spline coefficients and physical space at each step of the cost function minimization.

A more technical description of SAMURAI is given in the appendix of Bell et al. (2012).

Please reference Bell et al. (2012) if you use SAMURAI in your research. A description of the 3D version including analytic tests is currently in preparation, and will serve as a useful citation for v1.x shortly.

== Contributing to SAMURAI ==

* Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet
* Check out the [http://github.com/mmbell/samurai/issues issue tracker] to make sure someone already hasn’t requested it and/or contributed it
* Fork the project
* Start a feature/bugfix branch
* Commit and push until you are happy with your contribution, then open a Pull Request.
* Make sure to add tests for the feature/bugfix. This is important so I don’t break it in a future version unintentionally.

== Copyright ==

Copyright (c) 2012 Michael Bell

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

See LICENSE for a copy of the GNU General Public License, or [gnu.org] (http://www.gnu.org/licenses/).

=== References ===

Bell, M. M., M. T. Montgomery, and K. A. Emanuel, 2012: Air-sea enthalpy and momentum exchange at major hurricane wind speeds observed during CBLAST. ''J. Atmos. Sci.'', ''in press''.

Gao, J., M. Xue, K. Brewster, and K. K. Droegemeier, 2004: A three-dimensional variational data analysis method with recursive filter for Doppler radars. ''J. Atmos. Oceanic Technol.'', '''21''', 457–469.

Machenhauer, B., 1979: The spectral method. ''Numerical methods used in atmospheric models'', A. Kasahara, Ed., GARP Publications Series No 17, WMO and ICSU, Vol. 2, pp. 121–275.

Ooyama, K. V., 1987: Scale controlled objective analysis. ''Mon. Wea. Rev.'', '''115''', 2479–2506.

Ooyama, K. V., 2002: The cubic-spline transform method: Basic definitions and tests in a 1d single domain. ''Mon. Wea. Rev.'', '''130''', 2392–2415.

= Compilation =

To compile, use [CMake] (http://www.cmake.org) from the top-level directory:

<pre> $ cmake .</pre>
to create a Makefile or Xcode project for your machine. Run <code>make</code> or build via Xcode to create the <code>samurai</code> binary. Run <code>make install</code> to install the binary to /usr/local/bin

To install samurai in an alternate location:

<pre> $ cmake -DCMAKE_INSTALL_PREFIX=/some/other/location .</pre>
To use an alternate compiler (for example the Intel C++ compiler):

<pre> $ cmake -DCMAKE_CXX_COMPILER="icpc" .</pre>
The program is known to work with GCC and Intel compilers, but has not been tested with other compilers.

A few external libraries are required:

[Geographiclib] (http://geographiclib.sourceforge.net) is used for geolocation of data and map projection.

[Qt] (http://qt.nokia.com/products) is used for helper classes including XML parsing. A graphical user interface based on Qt will be available in a future release.

[NetCDF] (http://www.unidata.ucar.edu/software/netcdf) is used for output of the gridded analysis results.

[cURL] (http://curl.haxx.se/libcurl) and [HDF5] (http://www.hdfgroup.org/HDF5) are prerequisites for NetCDF4.

= Installation =

The pre-compiled binaries for Mac and Linux contain the necessary libraries in the tarfile. You can untar the binary and libraries into your favorite directory and it should work from there. On Linux, run the shell script <code>samurai.sh</code> instead of <code>samurai</code> in the bin directory to use the included libraries. The Mac version has the library paths embedded in the binary. If you compiled from source, then you can run the binary from anywhere as long as the system libraries are in your path.

= Running SAMURAI =

The <code>samurai</code> binary takes a single argument in the form of an XML configuration file describing the analysis. Observational data and reference frame information should be placed in a subdirectory specified in the configuration.

The current interface is available for 3D Cartesian and 3D cylindrical analysis. The 2D Cylindrical interface will be added soon.

Several utility scripts are included in the <code>util</code> subdirectory, and more will be added as available.

This documentation covers the configuration and interface for the 1.x release series. There are no plans to change the mandatory elements of the XML configuration structure through the 1.x releases. Optional elements may be added, but no changes would be required for existing analysis configurations.

Example XML files for Cartesian and cylindrical analyses are included in the <code>bin</code> directory and are described below. During initialization the program looks for data in the specified <code>data_directory</code> subdirectory.

The only requirement for doing an analysis is a frame-of-reference file in the <code>data_directory</code>. This file contains 1 second positions of a lat/lon reference point for the domain, and the motion of the frame. For tropical cyclone (TC) analyses this is usually the center of circulation, but can be any arbitrary reference point. The filename is ''YYYYMMDD.cen'' where the date refers to the first line of the file. The file structure is multiple lines consisting of ''HHMMSS Latitude Longitude V-speed U-speed''. Times are in UTC, and exceed 240000 when crossing over to the following day. Note that V and U follow latitude and longitude (not U then V). Only data from the first time to last time in the file will be used in the analysis, so this file sets both the time limits and analysis location. A simple linear track can be generated using the supplied <code>samurai_lineartrack.pl</code> script in the util directory.

If a background state is used, the software looks for a file called <code>samurai_Background.in</code>. This is a textfile consisting of kinematic and thermodynamic data for an ''a priori'' estimate of the atmosphere. Numerical model analyses, idealized states, or other estimates can be used in this file. The file format is:

Time (UTC unix seconds past 1-1-1970) Latitude Longitude (deg) Altitude (m) U V W (m/s) Temperature (K) Qv (g/kg) Dry air density (kg/m-3)

The time has to be in the limits specified by the frame-of-reference file, and the data should extend beyond the analysis domain boundaries. The data does not have to be evenly spaced, but the ordering of the positions is important. Data should be sorted by altitude, such that each successive column of data is grouped together with altitude increasing. The data from the background file is objectively analyzed and then transformed to spline coefficients. If greater fidelity and mass-conservation of the background is desired, the background state can be “adjusted” to closely match the pseudo-observations given in the file and mass-balanced.

SAMURAI can read several text data formats commonly used for aircraft observations. All datafiles in the <code>data_directory</code> will be included in the analysis. The read subroutine for each datatype is determined by the file suffix.

* frd = Dropsonde format used by HRD
* cls = Dropsonde format used by older versions of ASPEN
* sec = 1 second flight level data format used by HRD
* ten = 10 second flight level data format used by USAF
* swp = Doppler radar format used by NCAR/EOL
* sfmr = Custom format for SFMR data
* Wwind = Dropsonde format used by some versions of ASPEN (modified CLASS)
* eol = Dropsonde format used by most recent version of ASPEN (modified CLASS)
* qscat = Custom format for QUIKSCAT data
* ascat = Custom format for ASCAT data
* nopp = Custom format for NOPP scatterometer products
* cimss = Atmospheric motion vector format used by CIMSS/Wisconsin
* dwl = Doppler lidar format used by Simpsons Weather Associates
* insitu = Custom format for insitu observations

Native formats should work without too much trouble. Please refer to the VarDriver.cpp code for details on the custom formats. Instrument errors are configurable in the XML configuration, but are currently limited to fixed errors per instrument except for Doppler radar.

= Configuration =

The configuration file is a standard XML format that allows the user to customize the analysis. Details on the specific options are given below.

== grid ==

These options define the analysis grid.

=== i_min, i_max, i_incr, j_min, j_max, j_incr, k_min, k_max, k_incr ===

The minimum and maximum horizontal distances are relative to the moving frame-of-reference. The vertical distance is relative to the surface. Topography is not currently supported, but will be in a future release. All distances are in kilometers, and the number of gridpoints is calculated from the given parameters. For the RTZ mode, the j dimension is in degrees. For periodic boundary conditions, the min and max should be the points where the domain matches (e.g. 0 and 360).

== operation ==

These options determine how the program runs.

=== mode ===

The mode of operation. Two modes are currently supported. The “XYZ” option performs a 3D Cartesian analysis. The “RTZ” option performs a 3D cylindrical analysis. A 2D cylindrical mode is available in the code, but is not currently exposed to the interface. An axisymmetric version of the 3D cylindrical analysis mode will be available later in the 1.x series.

=== load_background ===

If this option is set to ‘true’ then the <code>samurai_Background.in</code> file will be loaded and objectively analyzed.

=== adjust_background ===

If this option is set to ‘true’ then a variational analysis will be conducted using the pseudo-observations. The analysis parameters will be set to those from iteration 1 below.

=== preprocess_obs ===

If this option is set to ‘true’ then the raw data files will be preprocessed according to their file suffixes. The output of the preprocessor is a text file called <code>samurai_Observations.in</code>. If this option is set to ‘false’ then the program will load the observations directly from the Observations.in file, located in the <code>data_directory</code>. Setting this to ‘false’ is useful for synthetic observations, but is not recommended for restarts at the current time.

=== num_iterations ===

Multiple iterations of the analysis can be performed by incrementing this number. The parameters for each iteration can change, which is useful for multi-pass (i.e. coarse to fine) analyses. The analysis from the previous iteration is used as the background for the next iteration.

=== output_mish ===

The analysis is performed computationally on a Gaussian quadrature “mish” that is finer resolution than the analysis grid defined above. Normally you just want the nodal values, but you can also output the mish values if you like. This would be useful if you are planning to integrate any of the quantities. The mish values are only output to the text file, not to the NetCDF or Asi files.

=== output_txt ===

The data can be output in a tab-delimited text file for easy ingest into Matlab or other analysis software. Columns are labeled with the variable names, but see the NetCDF output for units and long names. The output file name is samurai_<mode>_analysis.out (e.g. samurai_XYZ_analysis.out).

=== output_qc ===

A summary text file of all the observations and their weights that went into the analysis can be output. This file is useful for comparing the analysis versus the observations. The output file name is samurai_QC_analysis.out

=== output_netcdf ===

The most compact and complete output format is NetCDF. Metadata follows the COARDS conventions for use with GRaDs. The output file name is samurai_<mode>_analysis.nc

=== output_asi ===

This output format is an ASCII representation of the CEDRIC data format used in radar analysis. It can be used with the [grid2ps] (https://github.com/mmbell/grid2ps) graphics package.

== background ==

These options set information about the background state.

=== ref_state ===

This is a filename containing parameters that define the hydrostatic reference state used in the analysis. The default is the Dunion (2011) moist tropical sounding (dunion_mt.snd) which will be used if the specified sounding file cannot be found. The sounding must be given in terms of a surface pressure value in hPa, and 4th order polynomial curvefit coefficients for vertical profiles of qv, dry air density, and vertical pressure gradient. Note that qv is given in terms of a biased hyperbolic transform, which is approximately 0.5*qv for values above 10^-7 g/kg. The pressure gradient is in Pa/m. Temperature is calculated from the other quantities. The 4th order fit allows for easy differentiation and integration to ensure hydrostatic balance and accurate vertical derivatives. The drawback is that complex reference states are not possible. Since the main purpose of the reference state is to remove strong vertical gradients from the analysis, not necessarily provide a perfectly realistic sounding for numerical weather prediction, the 4th order representation is believed sufficient. Different (better?) sounding specifications may be available in a later release as requested.

=== ref_time ===

This defines the reference time HH:MM:SS when outputting to netCDF. This time needs to be within the defined frame-of-reference time limits, and will be used to convert the Cartesian analysis to lat/lon in the netCDF file.

=== i_background_roi, j_background_roi ===

The background radius of influence in km, or degrees in j dimension of RTZ mode. This sets the radius of influence for the exponential weighting function used to objectively analyze the background estimates. The ROI should be set to approximately the resolution of your background field, or slightly longer for a smoother background. The exponential weighting function is given by exp(-2.302585092994045*r<sup>2/R</sup>2) where r is the distance from the background estimate to the mish location, and R is the magnitude of the radius of influence vector. The multiplier is used such that the weight drops to 0.1 for one node increment, and 0.01 for two node increments.

The vertical interpolation is performed by cubic B-splines in a logarithmic height coordinate. This allows for better interpolation from pressure or sigma coordinate background fields and maintains high resolution in the vertical.

“Adjustment” of the background field is recommended for large departures from the original background geometry to the regular SAMURAI height grid.

== radar ==

These options set radar analysis parameters.

=== radar_skip ===

This option can be used to skip beams in the radar data. When set to ‘1’, all beams are used. This is primarily used to thin the data to decrease the computational burden when using a lot of radar data.

=== radar_stride ===

This option sets the number of gates over which averaging occurs along the beam. A stride of ‘1’ uses all data, and higher numbers average multiple gates of the given stride. This is used to thin the data for computational reasons, to reduce noise, or to reduce the spatial scale of the radar observations.

=== dynamic_stride ===

When set to ‘1’ the stride is dynamically determined based on the range. At short range, the minimum stride is set to the radarstride value. As the range increases, the stride increases to try and approximate spherical pulse volumes.

=== qr_variable ===

In the default ‘dbz’ mode, the reflectivity is objectively analyzed and not included in the cost function. If this is set to ‘qr’, then reflectivity is converted to liquid water using Z-M relationships defined in Gamache et al. (1993) and used as an additional variable in the cost function minimization. This could be used to combine reflectivity with other liquid water measurements, but does increase the computation time.

=== i_reflectivity_roi, j_reflectivity_roi, k_reflectivity_roi ===

The reflectivity radius of influence in km, or degrees in j dimension of RTZ mode. This sets the radius of influence for the exponential weighting function used to objectively analyze the reflectivity. A vertical radius of influence is included here, as opposed to the background ROI, to account for the interpolation from a spherical coordinate system used in radar scanning as opposed to (generally) from pressure or sigma coordinates for background fields. See background_roi description above for details on the exponential weighting function.

=== dbz_pseudow_weight ===

Setting this greater than ‘0’ will create pseudo-observations of the vertical velocity boundary condition based on the reflectivity. A non-zero value sets a weak constraint for zero vertical velocity at echo-top and at the surface. The number specifies the pseudo-error in m/s. Note that larger values set a weaker constraint, and smaller numbers greater than zero set a stronger constraint. Strong vertical velocity constraints at the surface and domain top can be set using boundary conditions, but this is provides a weak constraint at the surface and a variable height in the middle of the domain.

=== radar_dbz ===

The name of the reflectivity field in the radar data.

=== radar_vel ===

The name of the Doppler velocity field in the radar data.

=== radar_sw ===

The name of the spectrum width field in the radar data.

=== mask_reflectivity ===

The analysis can be set to missing data where there is no reflectivity. If set to ‘None’ then no masking is performed. A numerical value will be used as a threshold for the masking, with all data at nodes having less than the given reflectivity value removed.

== parameters ==

These parameters set the errors, filtering, and weights for the cost function for each iteration of the outer loop. The iteration is set via the “iter” attribute. If the number of iterations is less than “iter” then the parameter values are ignored.

=== bg_rhou_error, bg_rhov_error, bg_rhow_error, bg_tempk_error, bg_qv_error, bg_rhoa_error, bg_qr_error ===

The error numbers represent the standard deviation of the background error for each variable. If no background field is used, these should be set relatively high.

=== mc_weight ===

This number specifies the weight given to the mass continuity constraint. Mass continuity is enforced by pseudo-observations of the momentum gradients at the spline nodes. Larger numbers indicate a stronger constraint, zero means no constraint.

=== i_filter_length, j_filter_length, k_filter_length ===

These numbers set the Gaussian recursive filter length scale in gridpoints. If set to ‘-1’, the recursive filter is turned off for the given dimension. The minimum recommended value is 2.0, with higher values corresponding to larger spatial influence of the observations. Higher values also result in a smoother analysis. A journal article and Wiki page describing the available filters in SAMURAI are in preparation.

=== i_spline_cutoff, j_spline_cutoff, k_spline_cutoff ===

These numbers set the spline cutoff length scale in gridpoints. See Ooyama (2002) for a discussion of the spline cutoff length. The recommended value is 2.0.

=== i_max_wavenumber, j_max_wavenumber, k_max_wavenumber ===

These numbers act as a direct filter in frequency space. They are currently NOT implemented, but are included as placeholder for future 1.x versions.

== boundary_conditions ==

Homogeneous spline boundary conditions can be enforced in either or both the horizontal and vertical. Available options are R0, R1T0, R1T1, R1T2, R2T10, R2T20, R3, and PERIODIC following Ooyama (2002). The default “non”-boundary condition (R0) adds a buffer set of gridpoints that are used to calculate the solution but are discarded for output. Different boundary conditions can be set on the left (L) or right (R) side of the domain for each variable and dimension. The most common option other than R0 would be R1T0 for vertical velocity (rhow = 0) at the surface and/or domain top. Periodic domains are only valid for the i and j dimension, but are available in both the XYZ and RTZ mode. R1T10 and non-homogeneous boundary conditions should be available in a future release.

== observation_errors ==

Errors for a variety of standard instrumentation are included in the example configurations. Note that the specified error is given in terms of a standard deviation, and includes both instrument and representation error. Errors are fixed for all observations from a particular instrument except radar. In the radar case, the spectrum width and elevation angle are used to define the error for each radar gate. A minimum error (radar_min_error) is also enforced.

== options ==

This group is reserved for future options that are not mandatory. Users wishing to implement new options are encouraged to add them here for inclusion in a future release.

=== spline_approximation ===

The cubic B-spline used in the analysis requires several mathematical evaluations to compute, and is called many times during an analysis. To reduce computation time, the spline can be approximated by a pre-calculated look-up table with ~1e-12 or ~1e-6 precision. A value of ‘0’ here uses the full, unapproximated spline calculation, with ‘1’ or ‘2’ increasing the approximation and decreasing the precision. Tests suggest that the results are minimally changed with the ‘2’ approximation, but computation time can be decreased significantly.

Main Page

2019-07-16T18:44:38Z

Mmbell: /* LROSE */

= '''LROSE''' =

== The Lidar Radar Open Software Environment ==

[https://zenodo.org/badge/latestdoi/139178089 [[File:https://zenodo.org/badge/139178089.svg|DOI]]]

The current LROSE release is called '''“Blaze”''' (a climbing rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''Convert, Display, QC, Grid, Echo, and Winds''

Blaze can be used from a ‘Virtual Toolbox’ using Docker and a wrapper script, or compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

Full documentation for Blaze is available on the [https://nsf-lrose.github.io LROSE website]

We encourage users to [https://nsf-lrose.github.io/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[https://nsf-lrose.github.io/software.html Help] can be obtained by posting issues directly to the lrose-blaze Github repository, via our help mailing list, or Gitter user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

'''Blaze''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

In the current release, the following tools are available:

== Convert ==

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''RadxBufr''' - Convert Bufr format to CfRadial NetCDF format

== Display ==

* '''HawkEye''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

== Grid ==

* '''Radx2Grid''' - Gridding and interpolation of ground-based radar data
** 3-D Cartesian gridding (x, y, z)
** Cartesian PPIs (x, y, elevation)
** Regular polar grid (range, azimuth, elevation)

== Echo ==

* '''[http://wiki.lrose.net/index.php/RadxKdp RadxKdp]''' - KDP and Attenuation calculations
* '''[http://wiki.lrose.net/index.php/RadxPid RadxPid]''' - KDP, Attenuation, and Particle Identification
* '''[http://wiki.lrose.net/index.php/RadxRate RadxRate]''' - KDP, Attenuation, PID, and Rain Rate
* '''[http://wiki.lrose.net/index.php/RadxQpe RadxQpe]''' - Accumulated Quantitative Precipitation Estimation

== Wind ==

* '''RadxEvad''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''FRACTL''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''[http://wiki.lrose.net/index.php/SAMURAI SAMURAI]''' - Variational multi-Doppler retrieval and analysis package

RadxConvert

2019-07-15T22:27:12Z

Mmbell: Created page with "RadxConvert allows you to convert data stored in one format to a different format. = Supported Lidar and Radar Data Formats = {| !width="51%"| Format !width="19%"| Read Acce..."

RadxConvert allows you to convert data stored in one format to a different format.

= Supported Lidar and Radar Data Formats =

{|
!width="51%"| Format
!width="19%"| Read Access
!width="20%"| Write Access
|-
| CfRadial-1
| Yes
| Yes
|-
| CfRadial-2 (WMO) (in development)
| Yes
| Yes
|-
| BUFR (in development)
| Yes(partial)
| No
|-
| CFARR
| Yes
| No
|-
| DORADE - NCAR/EOL
| Yes
| Yes
|-
| D23R
| Yes
| No
|-
| DOE ARM netCDF (precedes CfRadial)
| Yes
| No
|-
| EEC-Edge
| Yes(partial)
| No
|-
| Foray-1 netCDF - NCAR/EOL
| Yes
| Yes
|-
| GAMIC
| Yes
| No
|-
| Gematronik Rainbow
| Yes
| No
|-
| HSRL (Lidar)
| Yes
| No
|-
| HRD (Hurricane Research Division)
| Yes
| No
|-
| Leosphere (LIDAR ASCII format)
| Yes
| No
|-
| MDV radial - NCAR/RAL
| Yes
| Yes
|-
| NEXRAD Level 2
| Yes
| Yes
|-
| NEXRAD Level 1, 3
| Yes
| No
|-
| NOXP
| Yes
| No
|-
| NSSL-MRD
| Yes
| No
|-
| ODIM-H5 (in development)
| Yes
| Yes
|-
| RAPIC - BOM Australia
| Yes
| No
|-
| SIGMET - raw format (Vaisala)
| Yes
| No
|-
| TDWR
| Yes
| No
|-
| TWOLF
| Yes
| No
|-
| UF - Universal Format
| Yes
| Yes
|}

= Running RadxConvert =

RadxConvert uses the Radx engine as a backend to convert between many different data formats. Since RadxPrint, RadxConvert, and Radx2Grid all have the same backend engine, they work seamlessly together. Many researchers spend a lot of time writing code just to get their data into a format they can use with their analysis software, and RadxConvert solves that problem for many common lidar and radar data formats. At a basic level, RadxConvert can do a simple conversion from one format to another, but it has a lot of flexibility and power options for advanced use cases. To see all command line options for RadxConvert, type the following command into a terminal:

<code lang="bash">lrose -- RadxConvert -h</code>

'''Important Note:''' If you just type 'RadxConvert' on the command line without any options it goes into 'REALTIME' mode and waits for streaming data to come in. For most use cases with data files stored locally the preferred mode of operation is to use command line arguments or a parameter file. This can be a little confusing for first time users. If you forget the '-f' or '-params' flag then this can also trigger REALTIME mode, and can appear like the conversion is taking a long time when in fact it is just waiting for data. While accidentally using REALTIME mode can occasionally cause some confusion, it allows for a powerful streaming capability to convert data directly from an instrument into a different format in real time.

For most applications, user's will have the data stored locally and want to convert to CfRadial or another data format. There are two different ways to specify the output file format, either on the command line or in a parameter file. If you don’t have specific requirements for the conversion settings, the easiest way to convert data to CfRadial format is to just use the command line '-f' option, which specifies a list of files:

<code lang="bash">lrose -- RadxConvert -f <path/to/data/file_name></code>

For example, to convert a NEXRAD Level 2 file from the Miami radar into CfRadial and place the file in an 'output' subdirectory:

<code lang="bash">lrose -- RadxConvert -f $PWD/Level2_KAMX_20161006_1906.ar2v -outdir $PWD/output</code>

Note that RadxConvert will create the output subdirectory if it doesn't exist.

'''Important Note:''' We encourage users to not move the converted data from the date subdirectory directory or rename the files. Many data file formats (such as both CfRadial and DORADE) keep metadata in the filename, and other LROSE tools such as HawkEye will work better when the data is organized by date at the subdirectory level. RadxConvert will automatically name and sort the files chronologically, and will organize the converted data by date into subdirectories with a YYYYMMDD naming convention.

We recommend migrating your workflow to use the CfRadial netCDF format for your data analysis. CfRadial has well defined metadata standards and version 2.0 has been selected by the World Meteorological Organization (WMO) as the new international standard for lidar and radar data. The format has many advantages over older formats such as UF or DORADE, and works well with other open source radar packages such as PyART. Users are also encouraged to compile their CfRadial files as an aggregation of sweep files that make up a single volume scan. This is the default for file types that the Radx engine can recognize as volume scans (such as NEXRAD Level 2 archives), and can prescribed via the parameter file in other cases.

RadxConvert does support the conversion to DORADE sweep format which can still be utilized by Solo users. CfRadial files can be displayed by HawkEye, but cannot yet be directly edited in that program. Editing capability for HawkEye is currently in development and will continue to add more functionality to eventually replace soloii and solo3. In the meantime, data can be converted to sweepfiles for interactive editing using:

<code lang="bash">lrose -- RadxConvert -dorade -f <path/to/data/file_name></code>

A parameter file can also be generated and modified similarly to the other LROSE tools.

<code lang="bash">lrose -- RadxConvert -print_params > $PWD/RadxConvert.params</code>

The user can specify the specific output format in RadxConvert.params file. For example:

Open RadxConvert.params in the terminal and find the line with 'output_format'. Set the desired output format as one of the options. For example, to choose CfRadial:

<code lang="bash">output_format = OUTPUT_FORMAT_CFRADIAL</code>

or for DORADE:

<code lang="bash">output_format= OUTPUT_FORMAT_DORADE</code>

Use the following command to convert using the settings provided by the parameter file:

<code lang="bash">lrose -- RadxConvert -f <path/to/data/file_name> -params $PWD/RadxConvert.params</code>

The next page of the documentation has all the options for RadxConvert automatically generated from the default parameter file. If you've had enough of format conversion, you can move on to the next step of the workflow and [[howtorun_hawkeye.html|display]] your data in CfRadial exchange format.

Main Page

2019-07-15T22:22:41Z

Mmbell: /* LROSE */

= '''LROSE''' =

== The Lidar Radar Open Software Environment ==

[https://zenodo.org/badge/latestdoi/139178089 [[File:https://zenodo.org/badge/139178089.svg|DOI]]]

The current LROSE release is called '''“Blaze”''' (a climbing rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''Convert, Display, QC, Grid, Echo, and Winds''

Blaze can be used from a ‘Virtual Toolbox’ using Docker and a wrapper script, or compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

Full documentation for Blaze is available on the [https://nsf-lrose.github.io LROSE website]

We encourage users to [https://nsf-lrose.github.io/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[https://nsf-lrose.github.io/software.html Help] can be obtained by posting issues directly to the lrose-blaze Github repository, via our help mailing list, or Gitter user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

'''Blaze''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

In the current release, the following tools are available:

== Convert ==

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''[http://wiki.lrose.net/index.php/RadxConvert RadxConvert]''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''RadxBufr''' - Convert Bufr format to CfRadial NetCDF format

== Display ==

* '''HawkEye''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

== Grid ==

* '''Radx2Grid''' - Gridding and interpolation of ground-based radar data
** 3-D Cartesian gridding (x, y, z)
** Cartesian PPIs (x, y, elevation)
** Regular polar grid (range, azimuth, elevation)

== Echo ==

* '''RadxKdp''' - KDP and Attenuation calculations
* '''RadxPid''' - KDP, Attenuation, and Particle Identification
* '''RadxRate''' - KDP, Attenuation, PID, and Rain Rate
* '''RadxQpe''' - Accumulated Quantitative Precipitation Estimation

== Wind ==

* '''RadxEvad''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''FRACTL''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''SAMURAI''' - Variational multi-Doppler retrieval and analysis package

RadxPrint

2019-07-09T22:12:10Z

Mmbell: Initial edit of RadxPrint documentation

RadxPrint allows you to print data header from any of the files supported by Radx, such as CfRadial and sweep format. It is one of the simplest, but most useful tools in the LROSE Virtual Toolbox.

= Prerequisites =

* A working LROSE Blaze installation is required. Complete the free [[../../../software.html|registration]] and follow the install instructions.
* Throughout the documentation, terms in brackets should be replaced with actual path and/or file names.
* The following instructions assume you are using the Virtual Toolbox. Any supported LROSE Blaze command can be invoked in the toolbox using 'lrose -- <command>'. The lrose script automatically maps your home directory to the toolbox, but requires absolute paths in order to find files. Use the $PWD environmental variable to designate the current path in a terminal.
* For native LROSE Blaze apps installed in your executable path, just drop 'lrose -- ' or replace with the absolute path to the location where the binaries are installed.
* The Radx Engine that powers LROSE can handle 24 radar and lidar [[howtorun_radxconvert.html#supported-lidar-and-radar-data-formats|formats]] (and counting). To see if your data works with LROSE, first use RadxPrint to query the metadata.

= Running RadxPrint =

At a basic level, the primary function of RadxPrint is to query a file to find out if it is supported by LROSE, and to look at the metadata. To print the data for a file in a generic form, type the following command into a terminal:

<code lang="bash">lrose -- RadxPrint -f </path/to/data/file_name></code>

Printing data with any Radx supported format works the same way. For example, a CfRadial file in the current directory from the Miami NEXRAD can be examined:

<code lang="bash">lrose -- RadxPrint -f $PWD/cfrad.20161006_190750.006_to_20161006_191339.679_KAMX_Surveillance_SUR.nc</code>

Sometimes the output can be too long to read, so you can pipe to 'more':

<code lang="bash">lrose -- RadxPrint -f </path/to/CfRadial_filename> | more</code>

or store the printed information in a .txt file. For example:

<code lang="bash">lrose -- RadxPrint -f $PWD/Level2_KAMX_20161006_1906.ar2v > KAMX_20161006_1906_metadata.txt</code>

In addition, RadxPrint also allows you to print out a specific field. For example, print the information of REF field onto a .txt file:

<code lang="bash">lrose -- RadxPrint -field REF -f $PWD/Level2_KAMX_20161006_1906.ar2v > KAMX_20161006_1906_metadata.txt > KAMX_20161006_1906_REF.txt</code>

RadxPrint supports many different command line options. To see all the command line options for RadxPrint, type：

<code lang="bash">lrose -- RadxPrint -h</code>

In addition to command line options, even greater control can be achieved using a "parameter" file. The parameter file is self-describing, but a formatted version is also included in this documentation. To produce a parameter file, just print the parameters and pipe them to a text file:

<code lang="bash">lrose -- RadxPrint -print_params > RadxPrint.params</code>

You can modify the parameter file using any text editor. A RadxPrint parameter file is particularly helpful if you want to do the same command over and over again, for example to extract specific metadata, set time limits, or print extra information. Once you have the parameters set the way you like, then just add the '-params' flag to the command. A app-specific parameter file and -params flag is a common feature of all the Radx engine tools.

<code lang="bash">lrose -- RadxPrint -params RadxPrint.params -f </path/to/CfRadial_filename></code>

The next page of the documentation has all the options for RadxPrint automatically generated from the default parameter file. If you've seen enough metadata, you can move on to the next step of the workflow and [[howtorun_radxconvert.html|convert]] your data to CfRadial exchange format.

= RadxPrint Parameter Descriptions =

== Prints out radial RADAR/LIDAR data ==

== DEBUGGING ==

=== debug ===

Debug option.

If set, debug messages will be printed appropriately.

Type: enum

Options:

<ul>
<li><pre> DEBUG_OFF</pre></li>
<li><pre> DEBUG_NORM</pre></li>
<li><pre> DEBUG_VERBOSE</pre></li>
<li><pre> DEBUG_EXTRA</pre></li></ul>

'''debug = DEBUG_OFF;'''

== DATA RETRIEVAL CONTROL ==

=== path ===

Path string - full path specified.

File will be read from this path.

Type: string

'''path = “.”;'''

=== specify_file_by_time ===

Option to specify file by time.

If true, paths for reads and writes are based on time and the data directory. If false, reads and writes use the specified path.

Type: boolean

'''specify_file_by_time = FALSE;'''

=== dir ===

Data directory.

Used to locate file if specify_file_by_time is true.

Type: string

'''dir = “.”;'''

=== read_search_mode ===

Mode for searching for data in time domain.

For all except LATEST, you must specify the search time and the search margin.

Type: enum

Options:

<ul>
<li><pre> READ_LATEST</pre></li>
<li><pre> READ_CLOSEST</pre></li>
<li><pre> READ_FIRST_BEFORE</pre></li>
<li><pre> READ_FIRST_AFTER</pre></li>
<li><pre> READ_RAYS_IN_INTERVAL</pre></li></ul>

'''read_search_mode = READ_LATEST;'''

=== read_search_time ===

Data time string.

Time for data requested. Format is YYYY MM DD HH MM SS.

Type: string

'''read_search_time = “1970 01 01 00 00 00”;'''

=== read_search_margin ===

Margin around search time (secs).

Applies to all search modes except LATEST.

Type: int

'''read_search_margin = 3600;'''

=== read_start_time ===

Start time for rays search.

Applies to READ_RAYS_IN_INTERVAL mode.

Type: string

'''read_start_time = “1970 01 01 00 00 00”;'''

=== read_end_time ===

End time for rays search.

Applies to READ_RAYS_IN_INTERVAL mode.

Type: string

'''read_end_time = “1970 01 01 00 00 00”;'''

=== read_dwell_secs ===

Dwell width (secs).

Applies to READ_RAYS_IN_INTERVAL mode.

Type: double

'''read_dwell_secs = 1;'''

=== read_dwell_stats ===

Method for computing stats on the dwell.

Applies to READ_RAYS_IN_INTERVAL mode. MIDDLE refers to the middle ray in the dwell sequence.

Type: enum

Options:

<ul>
<li><pre> DWELL_STATS_MEAN</pre></li>
<li><pre> DWELL_STATS_MEDIAN</pre></li>
<li><pre> DWELL_STATS_MAXIMUM</pre></li>
<li><pre> DWELL_STATS_MINIMUM</pre></li>
<li><pre> DWELL_STATS_MIDDLE</pre></li></ul>

'''read_dwell_stats = DWELL_STATS_MIDDLE;'''

== READ CONTROL OPTIONS ==

=== read_meta_data_only ===

Option to only read the meta data.

In this case sweep and field metadata will be read, but the ray and field data will not be read.

Type: boolean

'''read_meta_data_only = FALSE;'''

=== read_set_field_names ===

Option to set field names.

Type: boolean

'''read_set_field_names = FALSE;'''

=== read_field_names ===

Field name list.

Type: string 1D array - variable length.

'''read_field_names = {'''

'''};'''

=== read_set_fixed_angle_limits ===

Option to set fixed angle limits.

If ‘read_apply_strict_angle_limits’ is set, only read sweeps within the specified fixed angle limits. If strict checking is false and no data lies within the limits, return the closest applicable sweep. NOTE - fixed angles are elevation in PPI mode and azimuth in RHI mode.

Type: boolean

'''read_set_fixed_angle_limits = FALSE;'''

=== read_lower_fixed_angle ===

Lower fixed angle limit - degrees.

Type: double

'''read_lower_fixed_angle = 0;'''

=== read_upper_fixed_angle ===

Upper fixed angle limit - degrees.

Type: double

'''read_upper_fixed_angle = 90;'''

=== read_set_sweep_num_limits ===

Option to set sweep number limits.

If ‘read_apply_strict_angle_limits’ is set, only read sweeps within the specified limits. If strict checking is false and no data lies within the limits, return the closest applicable sweep.

Type: boolean

'''read_set_sweep_num_limits = FALSE;'''

=== read_lower_sweep_num ===

Lower sweep number limit.

Type: int

'''read_lower_sweep_num = 0;'''

=== read_upper_sweep_num ===

Upper sweep number limit.

Type: int

'''read_upper_sweep_num = 0;'''

=== read_apply_strict_angle_limits ===

Option to apply strict checking for angle or sweep number limits on read.

If true, an error will occur if the fixed angle limits or sweep num limits are outside the bounds of the data. If false, a read is guaranteed to return at least 1 sweep - if no sweep lies within the angle limits set, the nearest sweep will be returned.

Type: boolean

'''read_apply_strict_angle_limits = TRUE;'''

=== read_set_radar_num ===

Option to set the radar number.

See read_radar_num.

Type: boolean

'''read_set_radar_num = FALSE;'''

=== read_radar_num ===

Set the radar number for the data to be extracted.

Most files have data from a single radar, so this does not apply. The NOAA HRD files, however, have data from both the lower fuselage (LF, radar_num = 1) and tail (TA, radar_num = 2) radars. For HRD files, by default the TA radar will be used, unless the radar num is set to 1 for the LF radar.

Type: int

'''read_radar_num = 0;'''

=== aggregate_sweep_files_on_read ===

Option to aggregate sweep files into a volume on read.

If false, and the input data is in sweeps rather than volumes (e.g. DORADE), the sweep files from a volume will be aggregated into a volume.

Type: boolean

'''aggregate_sweep_files_on_read = FALSE;'''

=== aggregate_all_files_on_read ===

Option to aggregate all files in the file list on read.

If true, all of the files specified with the ‘-f’ arg will be aggregated into a single volume as they are read in. This only applies to FILELIST mode. Overrides ‘aggregate_sweep_files_on_read’.

Type: boolean

'''aggregate_all_files_on_read = FALSE;'''

=== ignore_antenna_transitions ===

Option to ignore rays with antenna transition flag set.

The transition flag is set when the antenna is moving between sweeps. If this parameter is true, rays containing the transition flag will not be read in.

Type: boolean

'''ignore_antenna_transitions = FALSE;'''

=== load_volume_fields_from_rays ===

Option to load up fields on the volume by combining the fields from the rays into a single array.

If false, the fields will be left managed by the rays.

Type: boolean

'''load_volume_fields_from_rays = FALSE;'''

=== trim_surveillance_sweeps_to_360deg ===

Option to trip surveillance sweeps so that they only cover 360 degrees.

Some sweeps will have rays which cover more than a 360-degree rotation. Often these include antenna transitions. If this is set to true, rays are trimmed off either end of the sweep to limit the coverage to 360 degrees. The median elevation angle is computed and the end ray which deviates from the median in elevation is trimmed first.

Type: boolean

'''trim_surveillance_sweeps_to_360deg = FALSE;'''

=== remove_rays_with_all_data_missing ===

Option to remove rays for which all data is missing.

If true, ray data will be checked. If all fields have missing data at all gates, the ray will be removed after reading.

Type: boolean

'''remove_rays_with_all_data_missing = FALSE;'''

=== remove_rays_with_antenna_transitions ===

Option to remove rays taken while the antenna was in transition.

If true, rays with the transition flag set will not be used. The transiton flag is set when the antenna is in transtion between one sweep and the next.

Type: boolean

'''remove_rays_with_antenna_transitions = FALSE;'''

=== set_max_range ===

Option to set the max range for any ray.

Type: boolean

'''set_max_range = FALSE;'''

=== max_range_km ===

Specified maximim range - km.

Gates beyond this range are removed.

Type: double

'''max_range_km = 9999;'''

=== preserve_sweeps ===

Preserve sweeps just as they are in the file.

Applies generally to NEXRAD data. If true, the sweep details are preserved. If false, we consolidate sweeps from split cuts into a single sweep.

Type: boolean

'''preserve_sweeps = FALSE;'''

=== remove_long_range_rays ===

Option to remove long range rays.

Applies to NEXRAD data. If true, data from the non-Doppler long-range sweeps will be removed.

Type: boolean

'''remove_long_range_rays = FALSE;'''

=== remove_short_range_rays ===

Option to remove short range rays.

Applies to NEXRAD data. If true, data from the Doppler short-range sweeps will be removed.

Type: boolean

'''remove_short_range_rays = FALSE;'''

=== set_ngates_constant ===

Option to force the number of gates to be constant.

If TRUE, the number of gates on all rays will be set to the maximum, and gates added to shorter rays will be filled with missing values.

Type: boolean

'''set_ngates_constant = FALSE;'''

=== change_radar_latitude_sign ===

Option to negate the latitude.

Mainly useful for RAPIC files. In RAPIC, latitude is always positive, so mostly you need to set the latitiude to the negative value of itself.

Type: boolean

'''change_radar_latitude_sign = FALSE;'''

=== apply_georeference_corrections ===

Option to apply the georeference info for moving platforms.

For moving platforms, measured georeference information is sometimes available. If this is set to true, the georeference data is applied and appropriate corrections made. If possible, Earth-centric azimuth and elevation angles will be computed.

Type: boolean

'''apply_georeference_corrections = FALSE;'''

== PRINT CONTROL ==

=== print_mode ===

Print mode option.

Controls details of the printing. Generally set in response to the command line args.

Type: enum

Options:

<ul>
<li><pre> PRINT_MODE_NORM</pre></li>
<li><pre> PRINT_MODE_NATIVE</pre></li>
<li><pre> PRINT_MODE_DORADE_FORMAT</pre></li></ul>

'''print_mode = PRINT_MODE_NORM;'''

=== print_rays ===

Option to print out ray meta data.

If false, only sweep and calib information will be printed.

Type: boolean

'''print_rays = FALSE;'''

=== print_ray_summary ===

Option to print summary for each ray.

The main metadata will be printed, followed by the ray summary.

Type: boolean

'''print_ray_summary = FALSE;'''

=== print_ray_table ===

Option to print a space-delimited angle table.

If true, prints space-delimited table of ray properties.

Type: boolean

'''print_ray_table = FALSE;'''

=== print_data ===

Option to print out data.

If true, data values will be printed.

Type: boolean

'''print_data = FALSE;'''

Main Page

2019-07-09T22:06:23Z

Mmbell: /* Convert */

= '''LROSE''' =

== The Lidar Radar Open Software Environment ==

[https://zenodo.org/badge/latestdoi/139178089 [[File:https://zenodo.org/badge/139178089.svg|DOI]]]

The current LROSE release is called '''“Blaze”''' (a climbing rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''Convert, Display, QC, Grid, Echo, and Winds''

Blaze can be used from a ‘Virtual Toolbox’ using Docker and a wrapper script, or compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

Full documentation for Blaze is available on the [https://nsf-lrose.github.io LROSE website]

We encourage users to [https://nsf-lrose.github.io/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[https://nsf-lrose.github.io/software.html Help] can be obtained by posting issues directly to the lrose-blaze Github repository, via our help mailing list, or Gitter user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

'''Blaze''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

In the current release, the following tools are available:

== Convert ==

* '''[http://wiki.lrose.net/index.php/RadxPrint RadxPrint]''' - Query files to determine properties and support by the Radx engine
* '''RadxConvert''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''RadxBufr''' - Convert Bufr format to CfRadial NetCDF format

== Display ==

* '''HawkEye''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

== Grid ==

* '''Radx2Grid''' - Gridding and interpolation of ground-based radar data
** 3-D Cartesian gridding (x, y, z)
** Cartesian PPIs (x, y, elevation)
** Regular polar grid (range, azimuth, elevation)

== Echo ==

* '''RadxKdp''' - KDP and Attenuation calculations
* '''RadxPid''' - KDP, Attenuation, and Particle Identification
* '''RadxRate''' - KDP, Attenuation, PID, and Rain Rate
* '''RadxQpe''' - Accumulated Quantitative Precipitation Estimation

== Wind ==

* '''RadxEvad''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''FRACTL''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''SAMURAI''' - Variational multi-Doppler retrieval and analysis package

Main Page

2019-07-09T21:40:36Z

Mmbell:

= '''LROSE''' =

== The Lidar Radar Open Software Environment ==

[https://zenodo.org/badge/latestdoi/139178089 [[File:https://zenodo.org/badge/139178089.svg|DOI]]]

The current LROSE release is called '''“Blaze”''' (a climbing rose) and encompasses six key toolsets that define a core lidar/radar workflow: ''Convert, Display, QC, Grid, Echo, and Winds''

Blaze can be used from a ‘Virtual Toolbox’ using Docker and a wrapper script, or compiled in C++ for native apps on Linux or Mac. Preliminary support is available for some tools on Windows.

Full documentation for Blaze is available on the [https://nsf-lrose.github.io LROSE website]

We encourage users to [https://nsf-lrose.github.io/software.html register] in order to receive critical software updates, and sign up for the mailing list to help build the LROSE community.

[https://nsf-lrose.github.io/software.html Help] can be obtained by posting issues directly to the lrose-blaze Github repository, via our help mailing list, or Gitter user forum.

LROSE is a co-operative project between:

* [http://www.atmos.colostate.edu/ Dept. of Atmospheric Science at Colorado State University (CSU)] and the
* [https://www.eol.ucar.edu/content/lidar-radar-open-software-environment The Earth Observing Lab at the National Center for Atmospheric Research (NCAR)].

LROSE is funded by the [https://www.nsf.gov National Science Foundation].

'''Blaze''' focuses on high-quality, well-tested, well-maintained and well-documented key applications as ‘building blocks’, allowing users to assemble trusted, reproducible workflows to accomplish more complex scientific tasks.

In the current release, the following tools are available:

== Convert ==

* '''RadxPrint''' - Query files to determine properties and support by the Radx engine
* '''RadxConvert''' - Convert 24 different lidar and radar formats to CfRadial NetCDF format
* '''RadxBufr''' - Convert Bufr format to CfRadial NetCDF format

== Display ==

* '''HawkEye''' - Real-time and archive display suitable for both scanning and vertically pointing radars.

== Grid ==

* '''Radx2Grid''' - Gridding and interpolation of ground-based radar data
** 3-D Cartesian gridding (x, y, z)
** Cartesian PPIs (x, y, elevation)
** Regular polar grid (range, azimuth, elevation)

== Echo ==

* '''RadxKdp''' - KDP and Attenuation calculations
* '''RadxPid''' - KDP, Attenuation, and Particle Identification
* '''RadxRate''' - KDP, Attenuation, PID, and Rain Rate
* '''RadxQpe''' - Accumulated Quantitative Precipitation Estimation

== Wind ==

* '''RadxEvad''' - Extended Velocity Azimuth Display single-Doppler retrieval
* '''FRACTL''' - Fast Reorder and CEDRIC Technique in LROSE multi-Doppler retrieval
* '''SAMURAI''' - Variational multi-Doppler retrieval and analysis package