Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolving Scan Type Discrepancies in CfRadial RHI Data Visualization #1533

Closed
HappyXiaoAnAn opened this issue Mar 21, 2024 · 2 comments · Fixed by #1578
Closed

Resolving Scan Type Discrepancies in CfRadial RHI Data Visualization #1533

HappyXiaoAnAn opened this issue Mar 21, 2024 · 2 comments · Fixed by #1578

Comments

@HappyXiaoAnAn
Copy link
Contributor

  • Py-ART version: 1.18.0
  • Python version: 3.11.6
  • Operating System: linux

Description

I'm working with RHI data from a CfRadial format file. The data's radar.sweep_mode is 'rhi', yet the radar.scan_type is incorrectly marked as 'other'. This discrepancy causes errors when attempting to visualize the data using pyart.graph.RadarDisplay(radar).

The issue originates from

mode = scan_name

and is related commit #1484 #1030.

My data's scan_name is 'PrecipRhi2', which fails to meet any criteria in the fallback types, resulting in the scan_type defaulting to 'other'.

Using scan_mode to determine scan_type seems inappropriate, as it leads to this type of error.

@zssherman
Copy link
Collaborator

@HappyXiaoAnAn Thanks for raising the issue! Yeah we are discussing on ways or how to approach this. The original intent was dealing with Atmospheric Radiation Measurement group radar files. We'll take a look and see how we can adjust this. For your case for now, you should be able to set:

radar.scan_type = 'rhi'

in the meantime before your plotting code.

@HappyXiaoAnAn
Copy link
Contributor Author

Understood, that works. Looking forward to the upcoming adjustments and thanks for the interim solution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants