All,
Thank you all for your interest and feedback on the updated Atlases. There are always limitations to model output, especially complex flow models, so remember: “all models are wrong, some are useful.”
It should be noted that I could run the model for any time and location. So if there is some exact site and exact time when you observe some tidal flow / feature, let me know and I’ll run the model for that exact time and we can see how it does.
The Atlases have several compromises. First, the time step is one hour, which is large. I’d rather use something smaller, or even variable, like 15 or 30 minutes, but then the Atlases would be over 1000 pages and truly huge (GB).
As an example of this, I ran the model at finer time steps for a high slack period and low slack period, at 10 minute intervals. These are already posted at
https://www.dewey.ca/
I also generated 1 mjnute = 1 frame animations for these slack transitions, and I’ll post those there as well.
The approach adapted by Pat Crean, and I followed to leverage existing use, was to model only six tidal phases, three floods and three ebbs, for small, medium, and large tides (each). THEN, I do my very best to match up any future hourly time/tide to one of the hours within those six cycles (43 maps). This can be a fairly good match, or not so much. For Volume 2 (Puget Sound) I use 8 tidal cycles, and more than 60 maps. So the matching is a best approximation, not a perfect independent model run for that time. The lookup table shows the time match is sometime close, but may be as much as 30 minutes off from even the best fit. I could look into a means of assessing ‘goodness of match’ and colour code the boxes in the lookup tables to provide some estimate of confidence.
Please continue to assess and comment of the utility of these Atlases, as I can adjust and regenerate them if the updates are warranted.
Richard