test_axis.py timeout #82
Labels
bug
Something isn't working
Comments
|
Thanks for the detailed report. Do you observe the same behavior if you install GymFC without the -e flag? |
|
Same output without the -e flag What would be the exact steps from having gymfc installed and build_plugin.sh built to actually running the test_axis.py script? I know they are in /examples, but I try to reproduce them and think I must be doing something wrong |
|
Your motor and IMU models are loaded it says it right in your output, Are you running this in a VM? I'll have to see if I can reproduce your steps. |
|
I'm running it on a native Ubuntu, but I could try it on a VM Exact steps I followed, in case it helps or want to reproduce the steps I followed: 1.installed gymfc both in normal and development mode (below in development) 2.went to gymfc/envs/assets/gazebo/plugins and run the plugin 3.went to the model path and created plugins and build inside plugins directories 4.went to projects root folder and git cloned aircraft plugins 5.went inside this cloned git and 6.finally, inside /home/cuda/projects/gymfc/examples/gymfc_nf/twins/nf1/ |
|
okay @wil3, I can confirm it's working on a VM but not on a native ubuntu system. Have reproduced exact steps above and the VM gets to the end of the test_axis.py script while the native one stays at Aircraft fixed to the world and eventually timeouts. Both VM and native are running same ubuntu 18.04.04 LS This could be a problem in the future, as Tensorflow requires GPU support and VM are not allowed to fully access the GPU, right? |
|
I suspect if you have it working in a clean VM there is a problem with your native install. All of your plugins are showing they are loaded and working. Its possible your network settings for some reason on your machine are preventing communication with Gazebo. Can you post the verbose output of the VM run here? |
|
verbose output of the VM run |
|
Any updates on this? I suspect it will take opening up wireshark and making sure messages are being passed to the Gazebo flight controller plugin. |
|
I will update this on Friday as cannot access the virtual machine atm. UPDATE: Im closing the thread as it seems to do with being the machine mounted via remote access, if any further things come up Ill re-open it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
Description
test_axis.py timeouts. GymFC and all aircraft plugins are built according to /examples
This was discussed in #40 but never tried with the new install_dependencies.sh system
STEP 1 INSTALLATION
sudo MAKE_FLAGS=-j4 ./install_dependencies.sh
pip3 install -e .
gymfc/envs/assets/gazebo/plugins/build_plugin.sh
STEP 2 BUILDING AIRCRAFT PLUGINS in /examples
mkdir gymfc_nf/twins/nf1/plugins && cd gymfc_nf/twins/nf1/plugins
git clone https://github.com/wil3/gymfc-aircraft-plugins.git
mkdir build
cd build
cmake ../gymfc-aircraft-plugins
make
Steps to Reproduce
with --verbose
python3 tests/test_axis.py --verbose examples/gymfc_nf/twins/nf1/model.sdf
without --verbose
python3 tests/test_axis.py examples/gymfc_nf/twins/nf1/model.sdf
Expected behavior
It's expected to show keyboard input to simulate steps
[enter] = Step, n= NExt Command, q = Quit
Additional context
Have tried too linking plugins manually inside build folder, as @varunag18 commented
Output
ln: failed to create symbolic link 'libgazebo_imu_plugin.so': File existsSo I check whats inside build folder
The text was updated successfully, but these errors were encountered: