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
For cases where there is no tidal forcing, should the bctides.in be empty or should it include some information. For a given test in coupledmodeldriver I used to get:
2008-08-23 00:00:00+00:00
0 50.0
0
1
75 0 0 0 0
from pyschism, but with the API change, now I get:
for my bctides.in. Which one is correct?
The text was updated successfully, but these errors were encountered:
@cuill thanks for your quick reply. I will update coupledmodeldriver to get the desired output based on your instructions.
From a usability perspective, with the old tides API, it made more sense; when you didn't setup the tide at all you would get the right bctides.in. However with the new API, we need to specify the no-tide input. As you pointed out above.
For cases where there is no tidal forcing, should the
bctides.in
be empty or should it include some information. For a given test incoupledmodeldriver
I used to get:from
pyschism
, but with the API change, now I get:for my
bctides.in
. Which one is correct?The text was updated successfully, but these errors were encountered: