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

Idealized WRF outputs not supported #1947

Closed
sgpearse opened this issue Nov 23, 2019 · 5 comments · Fixed by #1952
Closed

Idealized WRF outputs not supported #1947

sgpearse opened this issue Nov 23, 2019 · 5 comments · Fixed by #1952
Assignees

Comments

@sgpearse
Copy link
Collaborator

sgpearse commented Nov 23, 2019

Vapor is not correctly reading the WRF file below.

The file loads without error, but the extents are wrong. This file is from WRF v4, which was released in June 2018. This release introduced new options on the coordinate system, which may be related to this problem.

WRF File: /glade/p/cisl/vast/vapor/data/Source/WRF/idealized/kalundquist/wrfout_d01_2013-01-01_09_30_00

@clyne
Copy link
Collaborator

clyne commented Nov 25, 2019

@kalundquist this file does not contain valid XLONG or XLAT coordinate variables. The arrays are initialized to a constant value. If this is a valid WRF configuration I'm not aware of it.

@kalundquist
Copy link

kalundquist commented Nov 25, 2019 via email

@clyne
Copy link
Collaborator

clyne commented Nov 25, 2019

Is there an attribute in the WRF output file that can be used to flag the output as idealized?

@kalundquist
Copy link

kalundquist commented Nov 26, 2019 via email

@clyne
Copy link
Collaborator

clyne commented Nov 26, 2019

Thanks. We should be able to get this addressed for the upcoming 3.2 release.

@clyne clyne added the High label Nov 26, 2019
@clyne clyne self-assigned this Nov 26, 2019
@clyne clyne added the Fixed label Nov 27, 2019
@clyne clyne changed the title Problem with WRF file Idealized WRF outputs not supported Nov 27, 2019
clyne added a commit that referenced this issue Nov 27, 2019
* Added DerivedVar_CF2D class; creates a 2D coordinate variable from data in
memory.

* Optimized GetUserValue by caching z coordinate from previous search

* Fixed #1947. Added support for idealized WRF data (no lat or lon coordinates)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants