-
Notifications
You must be signed in to change notification settings - Fork 11
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
Errors when starting the Choreonoid project #4
Comments
Here is the content of the question: Messages on Choreonoid:
Messages on terminal:
I have investigated the error messages from the terminal, and found these were from the Messages on Choreonoid:
Messages on terminal:
It seems that there are two problems:
|
Hi @kx-guan You need to use cmake/make/make install in the repo to correctly install the project (in You should also run |
Hi, Dear Dr. @gergondet:
==================================
|
Hi @kx-guan You don't need to run We need to figure out why the script does not start correctly in the simulation and we should be good to go :)
Actually this is ok. I have the same message and it works fine. Few things to check (note: not all of these could be really needed but none will hurt either):
(note: Choreonoid interface will be in English at this point) |
Hi, Dear Dr. @gergondet: Execution of Python script "sim_mc.py" has been started. Thank you very much again. |
Could you paste the full output of Choreonoid console? What's the output of Another thing you can try is to change OpenRTM verbosity setting, in Choreonoid go in Tools -> OpenRTM -> Preferences. Then check the |
Hi, Dear Dr. @gergondet: Thank you very much again. |
Hello @gergondet I am trying to lauch chorenoid from a fresh install and I believe I am a similar issue. I am doing
I looked at the Could you help me fix this please ? This is preventing me from using Thanks a lot, |
Hi guys,
Re-posting here this question from @kx-guan. I hope you can help him with this, I don't remember the OpenRTM peculiarities well enough to be of any help here 😅
The text was updated successfully, but these errors were encountered: