Skip to content
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

Segmentation fault #25

Open
parlange opened this issue Nov 21, 2017 · 2 comments
Open

Segmentation fault #25

parlange opened this issue Nov 21, 2017 · 2 comments

Comments

@parlange
Copy link

Hi. I am trying to run MultiCol-SLAM on the dataset in the example.
However, after I ran the command:

./Examples/Lafida/multi_col_slam_lafida ./Examples/small_orb_omni_voc_9_6.yml ./Examples/Lafida/Slam_Settings_indoor1.yaml ./Examples/Lafida/ $HOME$/Downloads/IndoorDynamic

I get the following error (segmentation fault)

MultiCol-SLAM Copyright (C) 2015-2016 Steffen Urban.
This program comes with ABSOLUTELY NO WARRANTY;
This is free software, and you are welcome to redistribute it
under certain conditions. See LICENSE.txt.


Loading ORB Vocabulary. This could take a while...
Vocabulary loaded!


Loading camera and MCS calibrations
Camera Parameters: 
- fps: 25
- color order: RGB (ignored if grayscale)

Extractor Parameters: 
- Number of Features: 400
- Scale Levels: 8
- Scale Factor: 1.2
- Fast Threshold: 20
- Learn Masks: 0
- Descriptor Size (byte): 32
- Use AGAST: 0
- FAST/AGAST Type: 2
- Score: HARRIS

Motion Model: Enabled


-------
Start processing sequence ...
Images in the sequence: 0

System shutdown
Requested to finish local mapper, loop closer and map publisher
init done
MakeCurrent: Not available with non-pangolin window.
All threads stopped...
-------

Segmentation fault (core dumped)

I have installed all the dependecies as required by the compilation instructions. Am i missing something?
Thank you @urbste

@SHERLOCKLS
Copy link

I met the same problem. Have you solved the problem? @Prlng

@AlexWKEvil
Copy link

Do not run it with the program arguments of the welcome page. I also encountered the same problem according to the instructions of the READ.me file.
Instead, replacing the arguments with your own file path, say absolute path as an example, would make the program running.
Well, at least this works for me.
@Prlng , @SHERLOCKLS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants