You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After building the AMBF as the instruction here, I met below error when running ambf_simulator. I am using Dockerfile (Ubuntu 20.04 with ROS Noetic) according to this repo. Do you know how to fix this problem? Thank you!
ambf_simulator Command Line Options:
-h [ --help ] Show help
-n [ --ndevs ] arg (=0) Number of Haptic Devices to Load
-i [ --load_devices ] arg Index number of devices to load which is
specified in input_device.yaml
-e [ --enableforces ] arg (=0) Enable Force Feedback on Haptic Devices
-p [ --phx_frequency ] arg (=1000) Physics Update Frequency (default: 1000
Hz)
-d [ --htx_frequency ] arg (=1000) Haptics Update Frequency (default: 1000
Hz)
-t [ --fixed_phx_timestep ] arg (=0) Use Fixed Time-Step for Physics
(default: False)
-f [ --fixed_htx_timestep ] arg (=0) Use Fixed Time-Step for Haptics
(default: False)
--override_max_comm_freq arg Override the maximum publishing
frequency for all afObjects (default:
1000 Hz)
--override_min_comm_freq arg Override the minimum publishing
frequency for all afObjects (default: 50
Hz)
-g [ --show_gui ] arg (=1) Show GUI
--ns arg Global namespace prefix for ROS
Communication
-s [ --sim_speed_factor ] arg (=1) Override the speed of "NON REAL-TIME"
simulation by a specified factor
(Default 1.0)
--plugins arg Simulator plugins to load, .e.g.
--plugins <plugin1_filepath>,
<plugin2_filepath> loads plugin1 and
plugin2 simualtor plugin
--launch_file arg Launch file path to load (default:
<ROOT_PATH>/ambf_models/descriptions/lau
nch.yaml
-a [ --load_multibody_files ] arg Description Filenames of Multi-Body(ies)
to Launch, .e.g. -a /test.yaml,
<another_path>/test2.yaml will load
multibodies test.yaml and test2.yaml if
they are valid files
-l [ --load_multibodies ] arg Index of Multi-Body(ies) to Launch,
.e.g. -l 1,2,3 will load multibodies at
indexes 1,2,3. See launch.yaml file
ERROR! FAILED TO INITIALIZE GLFW LIBRARY
`
The text was updated successfully, but these errors were encountered:
Thanks for the issue. If you are running ambf_simulator via Docker, you will not get the GUI to work. Instead you can run the simulator headless using ambf_simulator -g 0. Please see here for more command line options.
Hi Adnan,
After building the AMBF as the instruction here, I met below error when running
ambf_simulator
. I am using Dockerfile (Ubuntu 20.04 with ROS Noetic) according to this repo. Do you know how to fix this problem? Thank you!`
ASYNCHRONOUS MULTI-BODY FRAMEWORK SIMULATOR (AMBF Simulator)
STARTUP COMMAND LINE OPTIONS:
ambf_simulator Command Line Options:
-h [ --help ] Show help
-n [ --ndevs ] arg (=0) Number of Haptic Devices to Load
-i [ --load_devices ] arg Index number of devices to load which is
specified in input_device.yaml
-e [ --enableforces ] arg (=0) Enable Force Feedback on Haptic Devices
-p [ --phx_frequency ] arg (=1000) Physics Update Frequency (default: 1000
Hz)
-d [ --htx_frequency ] arg (=1000) Haptics Update Frequency (default: 1000
Hz)
-t [ --fixed_phx_timestep ] arg (=0) Use Fixed Time-Step for Physics
(default: False)
-f [ --fixed_htx_timestep ] arg (=0) Use Fixed Time-Step for Haptics
(default: False)
--override_max_comm_freq arg Override the maximum publishing
frequency for all afObjects (default:
1000 Hz)
--override_min_comm_freq arg Override the minimum publishing
frequency for all afObjects (default: 50
Hz)
-g [ --show_gui ] arg (=1) Show GUI
--ns arg Global namespace prefix for ROS
Communication
-s [ --sim_speed_factor ] arg (=1) Override the speed of "NON REAL-TIME"
simulation by a specified factor
(Default 1.0)
--plugins arg Simulator plugins to load, .e.g.
--plugins <plugin1_filepath>,
<plugin2_filepath> loads plugin1 and
plugin2 simualtor plugin
--launch_file arg Launch file path to load (default:
<ROOT_PATH>/ambf_models/descriptions/lau
nch.yaml
-a [ --load_multibody_files ] arg Description Filenames of Multi-Body(ies)
to Launch, .e.g. -a /test.yaml,
<another_path>/test2.yaml will load
multibodies test.yaml and test2.yaml if
they are valid files
-l [ --load_multibodies ] arg Index of Multi-Body(ies) to Launch,
.e.g. -l 1,2,3 will load multibodies at
indexes 1,2,3. See launch.yaml file
ERROR! FAILED TO INITIALIZE GLFW LIBRARY
`
The text was updated successfully, but these errors were encountered: