-
Notifications
You must be signed in to change notification settings - Fork 49
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
Comments
@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. |
This simulation is an “ideal” WRF run. These cases usually do not have lat/lon set.
From: clyne <notifications@github.com>
Reply-To: NCAR/VAPOR <reply@reply.github.com>
Date: Monday, November 25, 2019 at 3:31 PM
To: NCAR/VAPOR <VAPOR@noreply.github.com>
Cc: "Lundquist, Katie" <lundquist3@llnl.gov>, Mention <mention@noreply.github.com>
Subject: Re: [NCAR/VAPOR] Problem with WRF file (#1947)
@kalundquist<https://github.com/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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1947?email_source=notifications&email_token=AFPMMVIRVWJQPP3VCJELQ53QVRN6FA5CNFSM4JQYNJ52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFEFNZA#issuecomment-558388964>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFPMMVMIXY2SZ5746LR6NG3QVRN6FANCNFSM4JQYNJ5Q>.
|
Is there an attribute in the WRF output file that can be used to flag the output as idealized? |
Yes. I think that MAP_PROJ_CHAR = “Cartesian” and SIMULATION_INITIALIZATION_TYPE = “IDEALIZED DATA” are candidates. Vapor 2 plots the wrfout file – perhaps a potential solution exists in Vapor 2 as well. My guess is that the map projection of Cartesian would be the most robust.
From: clyne <notifications@github.com>
Reply-To: NCAR/VAPOR <reply@reply.github.com>
Date: Monday, November 25, 2019 at 3:38 PM
To: NCAR/VAPOR <VAPOR@noreply.github.com>
Cc: "Lundquist, Katie" <lundquist3@llnl.gov>, Mention <mention@noreply.github.com>
Subject: Re: [NCAR/VAPOR] Problem with WRF file (#1947)
Is there an attribute in the WRF output file that can be used to flag the output as idealized?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1947?email_source=notifications&email_token=AFPMMVNJMY5VK5LCL2Q7KHLQVROVJA5CNFSM4JQYNJ52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFEF2RY#issuecomment-558390599>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFPMMVPHIFCTB2TFI4P2OMLQVROVJANCNFSM4JQYNJ5Q>.
|
Thanks. We should be able to get this addressed for the upcoming 3.2 release. |
clyne
added a commit
that referenced
this issue
Nov 26, 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
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
The text was updated successfully, but these errors were encountered: