You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Conflict exists with current PR. Gribdata had a conflict related to pylint ignore statements.
Addressing review comments from earlier reviews.
No longer runs the way it used to.
Fields are in there, but pygraf can't find the fields.
---- Jan 25
Still no word. Craig to email thread to ping for status.
Branch is getting old/stale. Work is being wasted!
---- Jan 4
Still no word.
---- Dec 7
Emailed Steve/Curtis to find out which products/levels.
Plan to merge the PR and make changes later.
Steve is concerned over whether we have authority to plot these fields. Algorithm may be proprietary.
---- Nov 9
Still in a holding pattern for feedback from Steve on which products/levels.
---- Oct 27
Opened a PR with current state. Code is close, but there were some issues with linter and pytest. Also addressing the order of when the column max and reordering the categories is done.
Waiting on Stakeholder feedback on which select levels to plot.
Still need to address hardwired level. Is it needed or no?
Should we name it max or colmax to differentiate it from fields like "u/v max"? It might be more descriptive, but requires some additions to tests. It shouldn't be a problem to have "colmax" in the image file name on the frontend.
We need to add in-flight icing products for RRFS parallels. These products need no additional computation and show up in the RRFS output as:
ICPROB = icing probability
SIPD = Supercooled Large Droplet Icing
ICSEV = ICPROB separated into several thresholded categories
They're on flight levels, every 500 feet from 500 to 30000, hourly from lead times 1hr onward (the calculations need hourly accumulated precipitation). There is sample data on Jet, at the end of PRSLEV.GrbF06:
---- Feb 1
Conflict exists with current PR. Gribdata had a conflict related to pylint ignore statements.
Addressing review comments from earlier reviews.
No longer runs the way it used to.
Fields are in there, but pygraf can't find the fields.
---- Jan 25
Still no word. Craig to email thread to ping for status.
Branch is getting old/stale. Work is being wasted!
---- Jan 4
Still no word.
---- Dec 7
Emailed Steve/Curtis to find out which products/levels.
Plan to merge the PR and make changes later.
Steve is concerned over whether we have authority to plot these fields. Algorithm may be proprietary.
---- Nov 9
Still in a holding pattern for feedback from Steve on which products/levels.
---- Oct 27
Opened a PR with current state. Code is close, but there were some issues with linter and pytest. Also addressing the order of when the column max and reordering the categories is done.
Waiting on Stakeholder feedback on which select levels to plot.
Still need to address hardwired level. Is it needed or no?
Should we name it max or colmax to differentiate it from fields like "u/v max"? It might be more descriptive, but requires some additions to tests. It shouldn't be a problem to have "colmax" in the image file name on the frontend.
Anticipating new requests to do overlays similar to those at https://www.aviationweather.gov/icing/fip.
No current plans for HRRR, just RRFS.
May need to change the levels over which the colmax is computed.
---- Oct 12
Craig started working to add the new fields. Still working on color scales.
The text was updated successfully, but these errors were encountered: