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

C# an example of calling on-chip calibration #8773

Conversation

DenisGeek
Copy link
Contributor

issue: 7788 an example of calling on-chip calibration from C#

This example based on cs-tutorial-2-capture
Works like viewer for colored depth and color streams.

when in console press C, then:

  • stops rendering pipeline
  • starts calibration pipeline

dialog in console:

If you want to start calibration mode, switch to opened application console and press C
Stopping rendering pipeline...
Please choose:
1 - Calibrate
2 - Reset calibration to factory defaults
3 - Exit
Getting context...
Calibration device
Serial number:
Firmware version:

Starting pipeline for calibration mode
1 Calibration table before running on-chip calibration.
Step 1 : done
2 Runs the on-chip self-calibration routine that returns pointer to new calibration table.
Accept calibration? (Y\N)
Step 2 : done
3 Toggle between calibration tables to assess which is better. This is optional.
Compare and select better calibration table between current and FW device (Y\N)
Step 3 : done
4 Burns the new calibration to FW persistently. (Y\N)
Step 4 : done
Calibration complete
Stopping calibration pipeline...
Starting rendering pipeline...
If you want to start calibration mode, switch to opened application console and press C

using each Depth profile, which available for device performs next 16 calibration combinations (in case of windows otherwise 8):

CalibrationSpeed
            VeryFast,   // (0.66 seconds), for small depth degradation
            Fast,       // (1.33 seconds), medium depth degradation.This is the recommended setting.
            Medium,     // (2.84 seconds), medium depth degradation.
            Slow,       // (Default) (2.84 seconds), for significant depth degradation.
CalibrationScanParameter
            Intrinsic,  // (default) Intrinsic calibration correction. The intrinsic distortion comes about through microscopic shifts in the lens positions
            Extrinsic,  // Extrinsic calibration correction. Extrinsic distortions are related to microscopic bending and twisting of the stiffener on which the two stereo sensors are mounted
CalibrationDataSampling
            WindowsAndLinux,// default is 0 which uses a polling approach that works on Windows and Linux
            Windows,        // Windows it is possible to select 1 which is interrupt data sampling which is slightly faster

Test calibration report will be written to the file ReportTestCalibrationModes.csv in application working directory
@DenisGeek
Copy link
Contributor Author

Added Calibration tests:
using each Depth profile, which available for device performs next 16 calibration combinations (in case of windows otherwise 8):

CalibrationSpeed
VeryFast, // (0.66 seconds), for small depth degradation
Fast, // (1.33 seconds), medium depth degradation.This is the recommended setting.
Medium, // (2.84 seconds), medium depth degradation.
Slow, // (Default) (2.84 seconds), for significant depth degradation.
CalibrationScanParameter
Intrinsic, // (default) Intrinsic calibration correction. The intrinsic distortion comes about through microscopic shifts in the lens positions
Extrinsic, // Extrinsic calibration correction. Extrinsic distortions are related to microscopic bending and twisting of the stiffener on which the two stereo sensors are mounted
CalibrationDataSampling
WindowsAndLinux,// default is 0 which uses a polling approach that works on Windows and Linux
Windows, // Windows it is possible to select 1 which is interrupted data sampling which is slightly faster

Test calibration report will be written to the file ReportTestCalibrationModes.csv in application working directory

@maloel maloel requested a review from ev-mp May 25, 2021 08:06
@ev-mp
Copy link
Collaborator

ev-mp commented Jun 20, 2021

The PR shall be closed in favor of the follow up work continued in #9256

@ev-mp ev-mp closed this Jun 20, 2021
@DenisGeek

This comment has been minimized.

@IntelRealSense IntelRealSense deleted a comment from DenisGeek Jun 20, 2021
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

Successfully merging this pull request may close these issues.

2 participants