Feature: A Closer Look At Tides

[fgarcia0128]

Context:

• Currently, StormSim allows users to add random tides to the CSTORM modeling outputs.
• In the case of Timeseries, a random seed date is sampled and then we pull the data points needed for the tidal record to cover the length of the storm hydrograph.
• We don't account for what phase of the tide we pulled. (i.e did we get the highest or lowest point of the tidal signal).
• StormSim was designed for using CHS post0 | Base runs ( no tides | no SLR | no post)

Discussion Point:

• Do we need to add tidal uncertainty to StormSim? This would increased data volume in computations.
• Should we look into a more static way to add tides (i.e search for tidal signal for the explicit event date)? Specifically in the context of:
• 1. PROS: I only have the modeled date for the TC (CSTORM Run Date). We would pull the tidal signal for this seed date.
• 2. LCS: We have a projected date in the future. We can pull tidal signal for projected date but requires LCS sampling to upscale from yearly to monthly.
• What would it require?
• Is it worth it ?

Considerations:

• Solution must be something we can automate through the contents of CHS Files (i.e timestamp for PROS).
• LCS sampling scheme only has a yearly resolution. This would need to be up-scaled.
• Upscaling the sampling scheme ultimately boils down to recomputing the underlying storm statistics from a yearly basis to a monthly or daily basis.
• Big question is: Can we automate this process with the files that we have currently?
• 1. TC Storm Recurrence Rates [stm/ yr * Km] -> At 1025 Coastal Reference Locations along the Atlantic Basin (3 intensities)
• 2. TC Discrete Storm Weights -> Likelihood of occurrence in a year
• 3. XC Rate [stm/yr]

@KHodgens @astehno @jmelby @Piro628