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
I'm suddenly getting a lot of failed runs in a model where i extended the model with 1 stress period that runs just fine.
Looking in the RMR file i see that there are alot of DA_CYCLE = -9999 messages for which I cant find anything in the manuals.
What can be the reason for this? The model has 0 failed runs before the added stress period. After the addition the model carries three stress periods, the only difference being that I add one active BC (again) which was active in the first stress period. It runs without any problems really and the majority of the IES-ensemble runs are completed. However, lots of workers seem to be failing due to the message. I Attatched an image from the RMR-file of the message.
The text was updated successfully, but these errors were encountered:
That da cycle value is irrelevant - its only for pestpp-da. You can add panther_agent_freeze_on_fail(true) to the control file and the workers will freeze when the model fails. Then you can see what happened in the worker dir.
Your right. It had something to do with a bad observation. I rebuilt the
tok file and it got sorted.
ons 10 apr. 2024 kl. 04:14 skrev J Dub ***@***.***>:
Hi,
I'm suddenly getting a lot of failed runs in a model where i extended the model with 1 stress period that runs just fine.
Looking in the RMR file i see that there are alot of DA_CYCLE = -9999 messages for which I cant find anything in the manuals.
What can be the reason for this? The model has 0 failed runs before the added stress period. After the addition the model carries three stress periods, the only difference being that I add one active BC (again) which was active in the first stress period. It runs without any problems really and the majority of the IES-ensemble runs are completed. However, lots of workers seem to be failing due to the message. I Attatched an image from the RMR-file of the message.
The text was updated successfully, but these errors were encountered: