Default run infeasibilities in v4.3.5 q35_land_other(LAM_80) #333
-
Hello again! I've just upgraded to MAgPIE v4.3.5, but sadly I can't seem to get it to run properly. Even with a clean install without any of my project-specific changes the default run stops due to an infeasibility:
The lst gives me the following:
R and R packages are on their respective newest versions, GAMS is v35.2.0. R also gives the following warnings, but those don't seem to be actual issues as none of the files are used:
Is this a known issue of the current release or something unique to my default runs? Any suggestions what to fix where? Or should I simply revert to v4.3.4 - obviously not my preferred solution? Thanks and all the best! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 28 replies
-
Possible solution here : #333 (reply in thread) To replicate the issue, can you confirm if the following fails :
We always make sure that the default runs work as expected before every release. Additionally, if you paste the config.log from your failing runs we can compare it to a known 4.3.5 default run and see what's going on/what changed. I have a feeling that somehow the land protection policies are playing a role in your infeasibilities but this should not happen for a default run with freshly downloaded data. |
Beta Was this translation helpful? Give feedback.
-
Since it came up in Wednesday's meeting, a quick update on the 4.4.0 RC: The default run does indeed solve without any infeasibilities on Windows. So, no problem there, it seems. (Still confused about my 51 page report, though. But that's another issue) |
Beta Was this translation helpful? Give feedback.
Possible solution here : #333 (reply in thread)
To replicate the issue, can you confirm if the following fails :
We always make sure that the default runs work as expected before every release. Additionally, if you paste the config.log from your failing runs we can compare it to a known 4.3.5 default run and see what's going on/what changed.
I have a feeling that somehow the land protection policies are playing a role in your infeasibilities but this should not happen for a default run with freshly downloaded data.