TPXO7 demo and TPXO9 routines are very similar but different in that the large TPXO9 data are stored one-constituent-per-file.
Currently tpxo9_extract_HC.py and tpxo_extract_HC.py are pretty much duplicates and should/could be harmonised.
The FES routines are slightly different as the data are stored as amplitude and phases, so need to be converted to complex components for the interpolation. Maybe keep that separate for now.
Issue:
TPXO9 (global atlas) data is very large and it takes a few minutes to process. How to cut this down as a demo or unit test?
Acceptance criteria:
Harmonise TPXO7 and TPXO9 methods.
Introduce a way, or make a plan, (or turn this into a new Issue), to verify routine
TPXO7 demo and TPXO9 routines are very similar but different in that the large TPXO9 data are stored one-constituent-per-file.
Currently
tpxo9_extract_HC.pyandtpxo_extract_HC.pyare pretty much duplicates and should/could be harmonised.The FES routines are slightly different as the data are stored as amplitude and phases, so need to be converted to complex components for the interpolation. Maybe keep that separate for now.
Issue:
Acceptance criteria: