-
Notifications
You must be signed in to change notification settings - Fork 28
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
solve issue #83: generate_steady_states fails when you edit a model's optimal percentage twice #83 #85
Conversation
Thanks for opening this PR. It seems there is a segfault at the end of your output. Did you debug it? Any ideas for the reason? |
Hi, thanks for your response, and sorry for the late reply. I am currently involved with mid evaluation of my research project. I believe I have a good idea of what's causing it. I will work on it this Saturday and will get back to you with my findings. |
I have been working on this issue for the past few days and tried multiple solutions(not yet resolved) like this https://itslinuxfoss.com/fix-segmentation-fault-core-dumped-linux. According to this the Python segmentation fault is a standard error that arises when a program tries to access a memory that can not be accessed, and this may occur when either the memory location is not accessible or the memory is only available for reading. Below is one of the implementations: Installed everything from the beginning and ran the below code after the previously suggested modification and suggested according to https://www.pythonclear.com/errors/python-segmentation-fault/ CODE(sample.py):
OUTPUT:
Any suggestions on how to approach this efficiently? |
You have to debug the code to see exactly where the segfault comes from. It is possible that it comes from the c++ code (roughly speaking it is compiled to python modules via cython). So this is one link that you could start https://cython.readthedocs.io/en/latest/src/userguide/debugging.html |
This is related to GeomScale/dingo issue #83 - #83
Reproduced the specified issue (referenced as #83) in my local development environment.
Error is related to the
dingo/dingo/gurobi_based_implementations.py
Line 109 in aaae4ae
Source: - Trying to access a variable which is defined only if status == GRB.OPTIMAL in
Solution: - Access variable only if it is declared
OUTPUT after modification :