Jason Fleming

Need to include a fix for #1002 for this to be useful.

@wwlwpd my initial impression based on Carola's description is that we hotstarted from a URL that had a hotstart file that was later than the advisory time. In these cases,...

I think this issue is also related to the use of NAM meteorological data to provide guidance for a tropical cyclone. The data get labelled as belonging to a particular...

This is related to the timing of the NHC updating its forecast `index-at.xml` and BEST track files and how that lines up with the time that the ASGS picked up...

After researching this issue, I think the right path forward is for the default ASGS behavior is to use the BEST track file up to the forecast advisory time, then...

Hey @wwlwpd sorry for the delay, it is actually the `unhcat.exe` in SWAN that decomposes/recomposes the SWAN hotstart files. I think it is a memory hog, and this mesh is...

There is a lot to keep track of with SWAN, I think we need a SWAN tag for issues, like we currently do for OPeNDAP. :-) However in this instance,...

This will be addressed in the refactoring of our adcprep infrastructure.

At a minimum, we need to have more fine grained control over SWAN hotstart recomposition in the ASGS config file.

I think the solution to this is going to be to submit this job to the queueing system via qscript.pl and qscript.template.