ATCF fields are incorrect lengths when written to file
opened this issue · comments
@WPringle caught the following issue in noaa-ocs-modeling/EnsemblePerturbation#74 (comment):
@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
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 for NWS 19:
https://wiki.adcirc.org/wiki/Fort.22_file#NWS_.3D_19_Dynamic_Asymmetric_Holland_Vortex_Model
for NWS 19 and 20, the column lengths should be the following:
| column | ATCF | fort.22 |
|---|---|---|
BASIN |
2 | 2 |
CY |
3 | 3 |
YYYYMMDDHH |
11 | 11 |
TECHNUM/MIN |
3 | 3 |
TECH |
5 | 5 |
TAU |
4 | 4 |
LatN/S |
5 | -> 4 <- |
LonE/W |
6 | -> 5 <- |
VMAX |
4 | 4 |
MSLP |
5 | 5 |
TY |
3 | 3 |
RAD |
4 | 4 |
WINDCODE |
4 | 4 |
RAD1 |
5 | 5 |
RAD2 |
5 | 5 |
RAD3 |
5 | 5 |
RAD4 |
5 | 5 |
RADP |
5 | 5 |
RRP |
5 | 5 |
MRD |
4 | 4 |
GUSTS |
4 | -> 5 <- |
EYE |
4 | 4 |
SUBREGION |
4 | 4 |
MAXSEAS |
4 | 4 |
INITIALS |
4 | 4 |
DIR |
4 | -> 3 <- |
SPEED |
4 | 4 |
STORMNAME |
11 | -> 12 <- |
DEPTH |
2 | N/A |
SEAS |
3 | N/A |
SEASCODE |
4 | N/A |
SEAS1 |
5 | N/A |
SEAS2 |
5 | N/A |
SEAS3 |
5 | N/A |
SEAS4 |
5 | N/A |
RECORD_NUMBER |
N/A |
4 |
@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 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 , 12Apart 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: ***@***.***>
Apart from the column spacings I think that’s good yep
what are the correct column spacings for the fort.22? I've not had much success finding that on the ADCIRC wiki, as it says "use the ATCF format" but the fort.22 files we have been using have slightly different column widths than ATCF