Skip to content

393 noinv alignment#396

Open
andpet1324 wants to merge 4 commits intomainfrom
393-noinv-alignment
Open

393 noinv alignment#396
andpet1324 wants to merge 4 commits intomainfrom
393-noinv-alignment

Conversation

@andpet1324
Copy link
Copy Markdown
Contributor

Adds noinv_vref alignment to existing inv_vref alignment. Caught by bad fits and boundary cases.

inv_vref_tgt[0] = fitter_l0.fit(target_adc);
inv_vref_tgt[1] = fitter_l1.fit(target_adc);
break;
} catch (...) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please add a specific type to the exception you are catching. As written, we could (for example) have a bug in DataFitter that is causing an std::out_of_range exception but we are treating that like a "bad fit" exception. I would like DataFitter to be updated to be able to inform the user when the fit fails (what exception is being thrown when a fit "fails"?)

@tomeichlersmith tomeichlersmith linked an issue Apr 13, 2026 that may be closed by this pull request
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.

Better selection criteria for tasks/inv_vref_scan_lund

2 participants