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
@jreniel, I've been mostly using older version of PySCHISM (before ModelConfig API was introduced). I recently started using the later version and I noticed an issue with stations.
I create a Stations object and pass it to the coldstart method of ModelConfig. Then when I write the config to disk, using the coldstart object's write method, I don't see output for iout_sta and nspool_sta in the param file.
I tried to look at the code to see if I'm using it wrong, but it seems that in the definition of SCHOUT object nspool_sta needs to be passed
@jreniel, I've been mostly using older version of PySCHISM (before ModelConfig API was introduced). I recently started using the later version and I noticed an issue with stations.
I create a
Stations
object and pass it to thecoldstart
method ofModelConfig
. Then when I write the config to disk, using the coldstart object'swrite
method, I don't see output foriout_sta
andnspool_sta
in the param file.I tried to look at the code to see if I'm using it wrong, but it seems that in the definition of
SCHOUT
objectnspool_sta
needs to be passedpyschism/pyschism/param/schout.py
Lines 104 to 124 in ec00dff
otherwise it won't write the parameters to
param.nml
:pyschism/pyschism/param/schout.py
Lines 138 to 149 in ec00dff
And it seems that during the creation of
SCHOUT
object withinParam
object,nspool_sta
is not passed:pyschism/pyschism/param/param.py
Line 40 in ec00dff
I don't see anywhere else where
nspool_sta
is getting updated. So my guess is that this is a bug.Please let me know if I'm missing anything. Thanks!
The text was updated successfully, but these errors were encountered: