-
Notifications
You must be signed in to change notification settings - Fork 10
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
env.reset() error #13
Comments
@EtienneMenager @hunoutl Is anyone of you able to answer? |
Hi |
It is surprising to have mutliple "sofapython3::PythonEnvironment::getPythonCallingPointAsFileInfo" in the callstack and I wonder why. |
Hi,
it raises the same issue. |
Hi, I have never seen this mistake. Did you try to run the scene outside of SofaGym (to see if the problem was due to a missing plugin, or a problem with the structure of the scene)? For example, go to the folder containing the trunk scene and run the command "pathto/runSofa TrunkScene.py". |
Thank you, it did go wrong when loading the scene. Is it due to the STLIB library?
|
Indeed it is a problem with STLIB, it does not find the addNewData attribute in the init. What version of STLIB and SOFA are you using? If anyone else had this kind of problem with STLIB @alxbilger @hunoutl |
Yes, issue #12 on last Sofa (v22.12)
|
Hi, |
Hi, Nice to hear. The first errors are not a problem: the mesh cannot load all the point, but this not affect the simulation. It seems that there is an error in the subprocess call. But we don't have enough information to know where is the problem (it just says that there is a problem). Can you try to do a step in the runSofa API? (runSofa your_path/TrunkScene.py then push the step button) |
Thank you!
However when I put them in a python file for example called test.py, then in the command line: |
The Sofa GUI is not linked with SofaGym at the moment (display in SofaGym is done with pygame). This is the way to launch the environment in SofaGym, but what I would like to do is to launch the scene in Sofa and make it work in Sofa. The error you got closes the subprocess that launches the scene, so I guess it is related to the Sofa scene and not to SofaGym, and as you show, it seems to happen at runtime (not at initialization or reset). Can you go back to this configuration: and run the simulation? |
Yes, with the report:
|
Hmmm, okay. You have to figure out where the error is. I don't have it in my version of Sofa and SofaGym, so I suggest that we see where the problem is together by doing this:
Let me know :) |
Thank you to be this supportive! I added print lines in these 3 files as you said. Problem seems to be Line49 in simulate.py, specifically |
We're getting close, even if it's strange that it happens in this part of the code ... If it's a problem while the scene is working I don't really understand. I was told that someone had already had a problem like this with windows. @hunoutl does anyone work with windows and sofagym ? |
Ok, it's a problem i had previously. |
|
Can you try from #14 ? |
Thank you! it did not work and cannot solve the previous problems.
|
Hi, The thread closure can come from many different places. Did you check if the errors came from the scene creation like last time? Question : is the python executable (/usr/bin/python3) the one used by Sofa? |
the scene can be successfully loaded in sofa and stepping forward. |
Please send me an email at etienne.menager@inria.fr, I have some time to help. I will summarise here after solving the problem. |
I suggested a fix for the |
No activity after 2 months. Closing the issue, but don't hesitate to open it again if necessary. |
Hi
I've tried to load a sample in test_env.py, but found an error raising when executed to env.reset().
The text was updated successfully, but these errors were encountered: