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

set_calibration_table removed from engine #13189

Merged

Conversation

remibettan
Copy link
Contributor

No description provided.

@remibettan remibettan requested a review from OhadMeir July 28, 2024 09:03
@@ -225,7 +225,17 @@ namespace librealsense

void d500_auto_calibrated::set_calibration_table(const std::vector<uint8_t>& calibration)
{
_calib_engine->set_calibration_table(calibration, _curr_calibration);
if (_curr_calibration.size() != sizeof(ds::table_header) && // First time setting table, only header set by get_calibration_table
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is _curr_calibration here is same as in d500_debug_protocol_calibration_engine? Notice that d500_debug_protocol_calibration_engine::get_calibration_table still uses the member

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

get_valibration_table remained in the engine, because it uses the debug protocol interface.
It gets the current_calibration as param - this is the same as the one used in the set_calibration_table method:
std::vector<uint8_t> d500_auto_calibrated::get_calibration_table() const
{
return _calib_engine->get_calibration_table(_curr_calibration);
}

@remibettan remibettan requested a review from OhadMeir July 28, 2024 12:44
@remibettan remibettan merged commit 90f2f30 into IntelRealSense:development Jul 29, 2024
21 of 22 checks passed
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