Closed FariborzDaneshvar-NOAA closed 1 year ago
Here are the first few lines of hurricane track files:
Downloaded from stormevent (/lustre/hurricanes/dorian_2019_.../nhc_track/hurricane-track.dat
):
AL, 05, 2019082412, 03, OFCL, 0, 103N, 474W, 30, 1010, TD, 34, NEQ, 0, 0, 0, 0, 1014, 0, 30, 35, 0, , 0, SRS, 0, 0, ,,,,,,,,
AL, 05, 2019082418, 03, OFCL, 0, 106N, 486W, 30, 1009, TD, 34, NEQ, 0, 0, 0, 0, 1014, 0, 30, 40, 0, , 0, SRS, 284, 6, ,,,,,,,,
AL, 05, 2019082500, 03, OFCL, 0, 108N, 499W, 35, 1008, TS, 34, NEQ, 20, 0, 0, 20, 1014, 0, 10, 45, 0, , 0, DAZ, 279, 7, ,,,,,,,,
AL, 05, 2019082506, 03, OFCL, 0, 109N, 510W, 35, 1008, TS, 34, NEQ, 20, 0, 0, 20, 1014, 0, 10, 45, 0, , 0, ESB, 275, 6, ,,,,,,,,
AL, 05, 2019082512, 03, OFCL, 0, 111N, 523W, 35, 1008, TS, 34, NEQ, 20, 0, 0, 20, 1014, 0, 10, 45, 0, , 0, JLB, 279, 7, ,,,,,,,,
AL, 05, 2019082518, 03, OFCL, 0, 114N, 535W, 40, 1006, TS, 34, NEQ, 30, 0, 0, 30, 1015, 0, 10, 50, 0, , 0, JLB, 284, 6, ,,,,,,,,
AL, 05, 2019082600, 03, OFCL, 0, 116N, 547W, 45, 1003, TS, 34, NEQ, 40, 30, 20, 40, 1012, 0, 10, 55, 0, , 0, RJP, 280, 6, ,,,,,,,,
AL, 05, 2019082606, 03, OFCL, 0, 118N, 558W, 50, 1002, TS, 34, NEQ, 40, 30, 20, 40, 1012, 0, 10, 60, 0, , 0, JPC, 281, 6, ,,,,,,,,
AL, 05, 2019082606, 03, OFCL, 0, 118N, 558W, 50, 1002, TS, 50, NEQ, 20, 0, 0, 0, 1012, 0, 10, 60, 0, , 0, JPC, 281, 6, ,,,,,,,,
AL, 05, 2019082612, 03, OFCL, 0, 121N, 571W, 50, 1002, TS, 34, NEQ, 40, 30, 20, 40, 1012, 0, 10, 60, 0, , 0, SRS, 283, 7, ,,,,,,,,
In the spinup directory (/lustre/hurricanes/dorian_2019_.../setup/ensemble.dir/spinup/hurricane-track.dat
):
AL, 05, 2019082406, , BEST, 0, 103N, 464W, 25, 1011, TD, 34, NEQ, 0, 0, 0, 0, 1015, 130, 30, 35, 0, L, 0, , 0, 0, INVEST,,,,,,,,
AL, 05, 2019082412, , BEST, 0, 104N, 475W, 30, 1010, TD, 34, NEQ, 0, 0, 0, 0, 1014, 120, 30, 0, 0, L, 0, , 275, 6, FIVE,,,,,,,,
AL, 05, 2019082418, , BEST, 0, 106N, 487W, 35, 1008, TS, 34, NEQ, 30, 0, 0, 30, 1014, 120, 30, 40, 0, L, 0, , 280, 6, FIVE,,,,,,,,
AL, 05, 2019082500, , BEST, 0, 108N, 499W, 35, 1008, TS, 34, NEQ, 30, 0, 0, 30, 1014, 120, 30, 45, 0, L, 0, , 280, 6, DORIAN,,,,,,,,
AL, 05, 2019082506, , BEST, 0, 110N, 510W, 35, 1008, TS, 34, NEQ, 30, 0, 0, 30, 1014, 120, 30, 45, 0, L, 0, , 281, 6, DORIAN,,,,,,,,
AL, 05, 2019082512, , BEST, 0, 112N, 523W, 40, 1007, TS, 34, NEQ, 30, 0, 0, 30, 1013, 120, 30, 45, 0, L, 0, , 279, 7, DORIAN,,,,,,,,
AL, 05, 2019082518, , BEST, 0, 114N, 535W, 45, 1007, TS, 34, NEQ, 30, 0, 0, 30, 1014, 120, 30, 50, 0, L, 0, , 280, 6, DORIAN,,,,,,,,
AL, 05, 2019082600, , BEST, 0, 116N, 547W, 45, 1007, TS, 34, NEQ, 40, 30, 30, 40, 1012, 120, 30, 55, 0, L, 0, , 280, 6, DORIAN,,,,,,,,
AL, 05, 2019082606, , BEST, 0, 119N, 560W, 45, 1006, TS, 34, NEQ, 40, 30, 30, 40, 1012, 120, 30, 60, 0, L, 0, , 283, 7, DORIAN,,,,,,,,
AL, 05, 2019082612, , BEST, 0, 122N, 572W, 45, 1006, TS, 34, NEQ, 40, 30, 30, 40, 1012, 120, 30, 60, 0, L, 0, , 284, 6, DORIAN,,,,,,,,
The issue is that in the spinup case that we are not supposed to have any track, somehow it picks up the best track and uses it. And the issues of duplication is actually in the best track file directly downloaded from ATCF webpage. I need to find out why the best track is used and just get rid of it.
@SorooshMani-NOAA Thanks for looking into it.
@FariborzDaneshvar-NOAA this issue should be fixed for OFCL. I'm still working on remove duplication for the best track. If you rerun the workflow for OFCL (past forecast) it should work fine. I tested for a 7-member ensemble for Dorian 2019 and it went through (spinup ran was successful)
@saeed-moghimi-noaa When trying Dorian 2019 with the workflow, I noticed an issue. In the workflow when deciding when to start perturbing the track, I need to calculate a rough estimate of landfall time, so I take the shapefile of US and intersect it with the track. In case of Dorian best track, the track doesn't seem to intersect the US shape at all! so I was wondering if you have any suggestion for how to improve the logic?
One way is to just say perturb before the landfall on any country; but the reason I didn't do that is that sometimes some storm in the gulf might landfall on a country and then again on US coast, and we'd like to perturb before US landfall. Please let me know what you think.
@FariborzDaneshvar-NOAA I added a fix for this for now. Both best track and official track should work for all storms (including Ian and Dorian) please let me know if you notice any issues.
Hi @SorooshMani-NOAA Please discuss about this with our friends from NHC. Perhaps they have a specific way of handling this. Thanks.
I asked this question in the NHC meeting and they said that they use a subjective approach. In cases where there is no actual landfall (Marco 2020, Dorian 2019, ...) the take the point of closes approach as the landfall and then calculate the perturbation location. For the 25 storms to test for skill assessment (https://github.com/saeed-moghimi-noaa/Next-generation-psurge-tasks/issues/14) there's a fixed table that is used for lead times.
We can take this table and put it in our workflow when we run these storms.
@SorooshMani-NOAA Thanks for the fix. New runs of Ian
and Dorian
with the OFCL
track completed successfully. There was only a memory issue during the post-processing step for Dorian
that I documented it here: Memory issue for combining results #111
Since the spinup issues are resolved, I close this ticket.
A test run for
Dorian 2019
(withOFCL
track) stock in theSetting up the model ...
step and runs did not launch (DependencyNeverSatisfied). Here is the content of the slurm.out file for the failed step, noting thatThe GAHM asymmetric data structure has more than 4 iSotachs in cycle 59.
Run directory on NHC_COLAB_2 cluster:
/lustre/hurricanes/dorian_2019_b90c3ac1-d946-47d1-878c-322e8a63a34d