Masking qVio

droen8

I am using ov7251 for tracking. I think I have made everything as described but it's still not working.

https://ibb.co/XyDGG7w
https://ibb.co/WkSDC2V
https://ibb.co/6X5N6YV

Regards

Alex Kushleyev

@droen8 , quick question, did you move the camera after starting vio or has it been stationary?

Can you please try again by pointing the camera at a feature rich environment to make sure that top and bottom have many features and do not move the camera after you start qvio. I just want to double check.

Also, something to check, if you provide an incorrect file name in qvio (or rename your mask), do you get a warning from qvio server saying that the file could not be loaded?

Thanks

Alex

droen8

@Alex-Kushleyev
Yes I have tried multiple times, the screenshoot was taken after few restarts of voxl-qvio-server. It's for sure not using a mask.
I have tried renaming mask and I have not seen any errors when mask do not exist in provided path. I have tried to display printf("Mask file name = %s \n", staticMaskFileName); in _hard_reset function and the path is displayed properely. I do not have idea how can I debug this issue.

With existing file in mask_file_path:

Renamed file:

After renaming to ...maskWrongFilename.pgm :

Alex Kushleyev

@droen8 , i believe there is a special command that silences the output of QVIO during initialization:

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/server/main.cpp?ref_type=heads#L368

Please try to remove that wrapper SILENT_STD around the mvVISLAM_Initialize call and see if you get any messages about the mask file (when it has correct or incorrect file name).

Sorry, there is no good way to debug this, but hopefully this will provide more information.

Alex

droen8

@Alex-Kushleyev thank you, I have not noticed that init function is wrapped. Now I can see that path is relative to /home/root

I will try in few if it's working but it will for sure There is another error with Configuration.SF.xml should I have It in mind?

Alex Kushleyev

@droen8 ,

Oh yes... you found the issue.

I believe the other error (Configuration.SF.xml) is OK, we never used that file, so the configuration is passed via the mvVISLAM_Initialize call.

I'll discuss with the team how to fix this path issue for the mask file

Alex

droen8

This post is deleted!

droen8

@Alex-Kushleyev It is not complaining about mask opening fail now but It is still not working:

Voxl is stationary and I have tried reseting qvio:

//edit the relativity of a path was due to me running voxl-qvio-server from there. When I run It as a service It is using absolute paths now. But still not working with repository example mask nor with my own mask.

Alex Kushleyev

@droen8 , it looks like the mask file that I shared is not working. I did some digging and found that there is a formatting issue. if you open the pgm file with vi, you can see:

P5 160 120 255
^@^@^@^@^@^@^@^@...

but it should be:

P5
#
160 120
255
^@^@^@^@^@^@^

I am not sure how this happened.

I used vi to fix the sample mask, can you please try it? https://storage.googleapis.com/modalai_public/temp/voxl2-misc-packages/mask_example_160x120_fixed.pgm . Also, can you inspect the mask that you created? The PGM file should have the header above and then 8-bit mask entries where white (255) being where NO features should be found and black (0) where ok to have features.

Alex

droen8

@Alex-Kushleyev said in Masking qVio:

P5

160 120
255
^@^@^@^@^@^@^

It is working now thanks. I have created mask in monochrome bmp and then used online tool to convert it into pgm but output had wrong header:

P5
160 120
1
^@^@^@^@^@^@^

I have used gimp now and exported with .pgm (binary) and it's working

I put a preview mask on output image.