Skip to content

Default run infeasibilities in v4.3.5 q35_land_other(LAM_80) #333

Answered by abhimishr
jansteinhauser asked this question in Q&A
Discussion options

You must be logged in to vote

Possible solution here : #333 (reply in thread)


To replicate the issue, can you confirm if the following fails :

  1. Fresh clone of 4.3.5 release
  2. Using the default start script

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.

Replies: 2 comments 28 replies

Comment options

You must be logged in to vote
27 replies
@tscheypidi
Comment options

@flohump
Comment options

@devenazevedo
Comment options

@jansteinhauser
Comment options

@devenazevedo
Comment options

Answer selected by abhimishr
Comment options

You must be logged in to vote
1 reply
@flohump
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
5 participants