Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stress is null: cannot continue optimization #368

Open
jidel opened this issue Feb 16, 2016 · 2 comments
Open

Stress is null: cannot continue optimization #368

jidel opened this issue Feb 16, 2016 · 2 comments

Comments

@jidel
Copy link
Contributor

jidel commented Feb 16, 2016

Reproducable:

  1. Select some nodes
  2. disconnect nodes
  3. optimize
  4. re-enable nodes

Result: Stress is null, cannot continue optimization

@rohankoid
Copy link
Member

The case mentioned above is due to wrong use of re-enable feature.
However, Stress is null in other cases is a valid condition and not a system error.

@idrissou
Copy link
Contributor

@jidel: This bug seems to disappear as soon as you move nodes (step 5) after re-enabling them and optimizing again (step 6). Everything including the stress returns back to normal!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants