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
The way this is written write now, if a smrf_ipysnobal run (when forcing data is passed in the queue) is restarted, the smrf start date must also change. This should be fine as long as the forcing data is not output as well (currently not an option for this type of run). This issue this could cause is that the re-initialized smrf run will try to set a new start date for indexing in the netCDF, and this could cause issues. Not very pressing right now.
The text was updated successfully, but these errors were encountered:
The way this is written write now, if a smrf_ipysnobal run (when forcing data is passed in the queue) is restarted, the smrf start date must also change. This should be fine as long as the forcing data is not output as well (currently not an option for this type of run). This issue this could cause is that the re-initialized smrf run will try to set a new start date for indexing in the netCDF, and this could cause issues. Not very pressing right now.
The text was updated successfully, but these errors were encountered: