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

derivate ViSP’s photometric VS to defocus-based and non-linear scale space-based #3

Open
GuicarMIS opened this issue Jan 12, 2023 · 5 comments
Assignees

Comments

@GuicarMIS
Copy link
Collaborator

derivate ViSP’s photometric VS to (existing but slightly differently developed) defocus-based and non-linear scale space-based (actually nothing to do on the VS side 😉 just need to prepare the desired image so it might just be code copy-paste for me). Guillaume validates on JRL’s devices and Belinda validates on MIS’ devices.

@GuicarMIS
Copy link
Collaborator Author

GuicarMIS commented Jan 13, 2023

Transfer of defocus-based DVS ongoing on branch DefocusDVS. New DVS program created, thin lens camera model added.
TODO: adapt CFeatureDefocusedLuminance so that it derives vpFeatureLuminance and ensures its correct use in the vpServo task.

@GuicarMIS
Copy link
Collaborator Author

CFeatureDefocusedLuminance added. A last simulation test to do to compare with photometric VS using the same camera parameters (Yakumo lens) before trying Defocus-based DVS on UR10 robot too.

@GuicarMIS
Copy link
Collaborator Author

Defocus-based DVS on UR10 robot tested. OK But poor performances due to latencies in the new Spinnaker-based Flir camera capture (see issue #6).

@GuicarMIS
Copy link
Collaborator Author

Thanks to solving issue #6, performances are good.

20230120_131212.mp4

On the video, when the program is started the robot goes to the desired articular configuration, takes the desired image (click to continue), moves to the initial pose and starts to capture current images (click to continue) and output commands for the robot to reach back the desired image (thus pose) until the number of iterations set in the code is reached. After that the program outputs all the recorded data (images, residuals, etc).

plotResiduals

@GuicarMIS
Copy link
Collaborator Author

The recorded data (images, residuals, etc) are in the directory "resultat"

Screenshot_2023-01-20_05-37-59

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

2 participants