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.

Sign up for GitHub

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

Jump to bottom

Error message from PAHM #26

Open
yunfangsun opened this issue Jun 8, 2023 · 10 comments
Open

Error message from PAHM #26

yunfangsun opened this issue Jun 8, 2023 · 10 comments

Comments

@yunfangsun
Copy link

Hi @pvelissariou1 @SorooshMani-NOAA,

Do you have any ideas on how to fix the following error in PAHM that I run into it:

---------- MODEL PARAMETERS ----------

InitLogging not called :: ProcessAsymmetricVortexData: 4 isotachs were nonzero.
InitLogging not called :: ProcessAsymmetricVortexData: 6 isotachs were nonzero.
InitLogging not called :: ProcessAsymmetricVortexData: 6 isotachs were nonzero.
InitLogging not called :: ProcessAsymmetricVortexData: 4 isotachs were nonzero.
InitLogging not called :: ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@: The GAHM asymmetric data structure has more than 4 iSotachs in cycle 37.

Thank you!

Yunfang
@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Jun 8, 2023 via email

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Jun 8, 2023 via email

@yunfangsun
Copy link
Author

Hi Takis, @pvelissariou1

I am working on the 2022 Hurricane Ian case, my input files are in the folder of /scratch2/STI/coastal/noscrub/Yunfang.Sun/run_schism/pahm on Hera.

Thank you!

Yunfang

@SorooshMani-NOAA
Copy link
Contributor

@yunfangsun I'm not sure what that error is, but I have a couple of questions that might help find the answer: Are you using stormevents to download the track file? If so what advisory are you using?

One thing is that using stormevents for non-BEST tracks gives you a track file where the date for each advisory is the advisory issuance date, not the forecasted date. I'm not sure if that's a problem. In BEST track file you only get the hindcast dates.

I'm also tagging @FariborzDaneshvar-NOAA here as well as he will start using PaHM on SCHISM soon.

@yunfangsun
Copy link
Author

@SorooshMani-NOAA
Yes, I am using stormevents to download the track file.

The commands are as follows:

from stormevents.nhc import VortexTrack
track = VortexTrack.from_storm_name('ian', 2022)
storm_best_track = storm.track()
storm_best_track.to_file('hurricane-track.dat')

@SorooshMani-NOAA
Copy link
Contributor

@pvelissariou1 please let me know if anything needs to change in stormevents when writing the .dat file for PaHM. Based on @yunfangsun's script, he's getting the best track, so the date issue described at #26 (comment) shouldn't be the issue here!

@pvelissariou1
Copy link
Collaborator

pvelissariou1 commented Jun 8, 2023 via email

@yunfangsun
Copy link
Author

Hi Takis, @pvelissariou1

I will be on leave tomorrow, we can talk about it next week, and I will try the original PAHM to see how it works.

@yunfangsun
Copy link
Author

yunfangsun commented Jun 12, 2023 •
edited by SorooshMani-NOAA
Loading

Forwarding email for documenting communication related to this issue:

On Mon, Jun 12, 2023 at 12:45 PM Panagiotis Velissariou - NOAA Affiliate <panagiotis.velissariou@noaa.gov> wrote:
Hi Yunfang,

I used your data file for Ian in PaHM. My mesh was set to ESTOFS-250m.
PaHM digested the file just fine.

Holland model: no errors reported and it generated the output wind data just fine.

GAHM model: errors reported for number of isotachs > 4
Offending lines:
AL, 09, 2022093018, , BEST, 0, 333N, 792W, 70, 978, HU, 34, NEQ, 190, 130, 100, 60, 1007, 210, 40, 90, 0, L, 0, , 355, 9, IAN,,,,,,,,
AL, 09, 2022093018, , BEST, 0, 333N, 792W, 70, 978, HU, 50, NEQ, 80, 60, 80, 40, 1007, 210, 40, 90, 0, L, 0, , 355, 9, IAN,,,,,,,,
AL, 09, 2022093018, , BEST, 0, 333N, 792W, 70, 978, HU, 64, NEQ, 0, 30, 40, 0, 1007, 210, 40, 90, 0, L, 0, , 355, 9, IAN,,,,,,,,
AL, 09, 2022093018, 05, BEST, 0, 333N, 792W, 70, 978, HU, 34, NEQ, 190, 130, 100, 60, 1007, 210, 40, 0, 0, L, 0, , 0, 0, IAN,,,,,,,,
AL, 09, 2022093018, 05, BEST, 0, 333N, 792W, 70, 978, HU, 50, NEQ, 80, 60, 80, 40, 1007, 210, 40, 0, 0, L, 0, , 0, 0, IAN,,,,,,,,
AL, 09, 2022093018, 05, BEST, 0, 333N, 792W, 70, 978, HU, 64, NEQ, 0, 30, 40, 0, 1007, 210, 40, 0, 0, L, 0, , 0, 0, IAN,,,,,,,,
So, basically the 3 "red" lines are duplicates of the 3 "green" lines. Delete the 3 "red" lines in the file and you should be ok.

I am not sure that if this is a rare occurrence or, we need to filter out the extra entries based on some criteria. I'll investigate further.
It is the first time I encountered this type of error.
In SCHISM, the PaHM code is identical to the standalone PaHM so, it shouldn't be an issue from SCHISM's side.

SCHISM, by default uses the GAHM model (hardcoded in schism/src/Core/PaHM/PaHM_Utilities.F90, modelType=10 - line 266).
You might want to change this by setting modelType=1 to use the Holland model.

Takis

Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Physical Scientist - Project Lead
cell: (205) 227-9141
email: panagiotis.velissariou@noaa.gov

@SorooshMani-NOAA
Copy link
Contributor

Just for the sake of completeness and to document all of our discussion:

This seems to be coming directly from file from ATCF website and is not an issue related to stormevents reformatting as I previously assumed. However this comment can explain oceanmodeling/StormEvents#80 I think, which is related to non-BEST tracks.

@yunfangsun yunfangsun mentioned this issue Jun 15, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pvelissariou1 @SorooshMani-NOAA @yunfangsun