-
Notifications
You must be signed in to change notification settings - Fork 8
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
ATCF fields are incorrect lengths when written to file #24
Labels
bug
Something isn't working
Comments
ghost
self-assigned this
Mar 17, 2022
ghost
added this to observational data retrieval
Mar 17, 2022
ghost
moved this to Todo
in observational data retrieval
Mar 17, 2022
@zacharyburnettNOAA aswip does the conversion for fort.19 and fort.20 so don't need to worry about that.
Just make sure both BEST and e.g., OFCL from a-deck fit the ATCF specifications.
From: Zachary Burnett ***@***.***>
Date: Thursday, March 17, 2022 at 7:54 AM
To: oceanmodeling/StormEvents ***@***.***>
Cc: Pringle, William ***@***.***>, Mention ***@***.***>
Subject: [oceanmodeling/StormEvents] ATCF fields are incorrect lengths when written to file (Issue #24)
@WPringle<https://github.com/WPringle> caught the following issue in noaa-ocs-modeling/EnsemblePerturbation#74 (comment)<noaa-ocs-modeling/EnsemblePerturbation#74 (comment)>:
@zacharyburnettNOAA<https://github.com/zacharyburnettNOAA> I'm noticing some changes in the column spacings and the forecast times are not being entered in correctly. The fort.22 columns need to be formatted exactly.
NEW: AL, 06, 2018091106, , BEST, 0,260N, 632W, 115
OLD: AL, 06, 2018091106, , BEST, 0, 260N, 632W, 115
for reference, according to the specification
https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html
https://wiki.adcirc.org/wiki/Fort.22_file
for NWS 19 and 20, the column lengths should be the following:
column
length
BASIN
CY
TECHNUM/MIN
TECH
TAU
LatN/S
LonE/W
VMAX
MSLP
TY
RAD
WINDCODE
RAD1
RAD2
RAD3
RAD4
RADP
RRP
MRD
GUSTS
EYE
SUBREGION
MAXSEAS
INITIALS
DIR
SPEED
STORMNAME
DEPTH
SEAS
SEASCODE
SEAS1
SEAS2
SEAS3
SEAS4
—
Reply to this email directly, view it on GitHub<#24>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFBHFHTLHVN47X3DAAS7M7DVAMTQNANCNFSM5Q64GHCQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
ok, so for reference the conversion from ATCF to -AL, 06, 2018090200, , BEST, 0, 159N, 296W, 45, 1000, TS, 34, NEQ, 40, 40, 20, 40, 1010, 150, 30, 55, 0, L, 0, , 0, 0, FLORENCE, M, 12, NEQ, 45, 0, 0, 60, genesis-num, 019,
+AL, 06, 2018090200, , BEST, 0,159N, 296W, 45, 1000, TS, 34, NEQ, 40, 40, 20, 40, 1010, 150, 30, 55, 0, L, 0, , 0, 0, FLORENCE , 12 |
Apart from the column spacings I think that’s good yep.
From: Zachary Burnett ***@***.***>
Date: Thursday, March 17, 2022 at 9:31 AM
To: oceanmodeling/StormEvents ***@***.***>
Cc: Pringle, William ***@***.***>, Mention ***@***.***>
Subject: Re: [oceanmodeling/StormEvents] ATCF fields are incorrect lengths when written to file (Issue #24)
ok, so for reference the conversion from ATCF to fort.22 looks like this:
…-AL, 06, 2018090200, , BEST, 0, 159N, 296W, 45, 1000, TS, 34, NEQ, 40, 40, 20, 40, 1010, 150, 30, 55, 0, L, 0, , 0, 0, FLORENCE, M, 12, NEQ, 45, 0, 0, 60, genesis-num, 019,
+AL, 06, 2018090200, , BEST, 0,159N, 296W, 45, 1000, TS, 34, NEQ, 40, 40, 20, 40, 1010, 150, 30, 55, 0, L, 0, , 0, 0, FLORENCE , 12
—
Reply to this email directly, view it on GitHub<#24 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFBHFHWRVCSDQYWOJFKTGBLVAM643ANCNFSM5Q64GHCQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
what are the correct column spacings for the |
ghost
linked a pull request
Mar 28, 2022
that will
close
this issue
Merged
ghost
pushed a commit
that referenced
this issue
Mar 29, 2022
ghost
pushed a commit
that referenced
this issue
Mar 29, 2022
ghost
pushed a commit
that referenced
this issue
Mar 29, 2022
* use Florence 2018 as test case * set ATCF field lengths based on #24 * update reference files * add test for ATCF Co-authored-by: zacharyburnett <[email protected]>
Repository owner
moved this from Todo
to Done
in observational data retrieval
Mar 29, 2022
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@WPringle caught the following issue in noaa-ocs-modeling/EnsemblePerturbation#74 (comment):
ATCF specification:
https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html
ATCF example file:
https://ftp.nhc.noaa.gov/atcf/btk/bal012021.dat
fort.22
specification forNWS
19
:https://wiki.adcirc.org/wiki/Fort.22_file#NWS_.3D_19_Dynamic_Asymmetric_Holland_Vortex_Model
for
NWS
19
and20
, the column lengths should be the following:fort.22
BASIN
CY
YYYYMMDDHH
TECHNUM/MIN
TECH
TAU
LatN/S
LonE/W
VMAX
MSLP
TY
RAD
WINDCODE
RAD1
RAD2
RAD3
RAD4
RADP
RRP
MRD
GUSTS
EYE
SUBREGION
MAXSEAS
INITIALS
DIR
SPEED
STORMNAME
DEPTH
N/A
SEAS
N/A
SEASCODE
N/A
SEAS1
N/A
SEAS2
N/A
SEAS3
N/A
SEAS4
N/A
RECORD_NUMBER
N/A
The text was updated successfully, but these errors were encountered: