You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In coupledmodeldriver when we setup spin up it adds the duration of spin up as ramp-up forcing time as well. Assuming we want to have a "spin-up" up to the perturbation point, we might want to have the ramp time separated from the full spin up time. In this case the spin up means that there's is a simulation of unperturbed track, but the forces are not necessarily ramped up to the final time of simulation, i.e. dramp* is not equal to rnday for the spinup run.
This is just following the same logic that was implemented for adcirc in ensemble perturbation.
Instead of just having a fixed tidal spinup, use the spin up with all forcing all the way to the point where we start perturbing the track.
The text was updated successfully, but these errors were encountered: