Skip to content

Cleanup CFO loopback behavior#314

Open
rrivera747 wants to merge 4 commits into
developfrom
rrivera/loopbackCleanup
Open

Cleanup CFO loopback behavior#314
rrivera747 wants to merge 4 commits into
developfrom
rrivera/loopbackCleanup

Conversation

@rrivera747

Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR refines CFO/DTC loopback-related FE macros to make loopback behavior and outputs clearer during manual setup and automated testing, including adding Plotly histogram output for delay measurements.

Changes:

  • Updated the DTC “Loopback Manual Setup” macro interface to better communicate the default passthrough behavior and to return a formatted control-register result.
  • Forced the CFO loopback test “exponent” behavior to a fixed value (0) and removed it from the user-facing argument list.
  • Added Plotly histogram generation for loopback delay measurements in both the DTC emulator loopback tests and the CFO loopback test.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
otsdaq-mu2e/FEInterfaces/DTCFrontEndInterfaceImpl.cc Updates loopback manual-setup macro arguments/outputs and adds Plotly histogram output for emulator loopback delay measurements.
otsdaq-mu2e/FEInterfaces/CFOFrontEndInterfaceImpl.cc Fixes loopback test parameterization (fixed exponent), adds Plotly histogram output, and adds a user-facing message for failed measurements (currently with a logic issue).

Comment on lines +974 to +977
if(ostr.str().empty())
ostr << "No loopback measurements were successful. Check the link status of "
"targeted links."
<< std::endl;
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.

5 participants