DUNE-DAQ / DUNE-DAQ/crtmodules

Could connections between CRT apps be shown in our configuration diagrams?

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
0
Forks
0
Avg merge
5h 32m
Merged PRs (30d)
4

Description

I noticed that sometimes CRT applications show up in our configuration diagrams with no connections into, or out of, them. As an example, I've attached a full system diagram from the local-crt-grenoble-1x1-config session in the daqsystemtest sample configs (example-configs.data.xml).

In that diagram, there are no connections shown for the crt-grenoble-01 app.

I suspect that this is a "configuration generation" issue. By that, I mean that when we run a generate-modules script (e.g. generate_modules_test), the needed input or output connections are not generated for the CRT modules. (I believe that those input and output connection declarations are what the "create diagram" script uses.). Given this, it may be that the changes to fix this will be in the daqconf repo instead of this repo, but I wasn't sure, so I'm filing this Issue in crtmodules.

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the local-crt-grenoble-1x1-config session in the daqsystemtest sample configs and inspect example-configs.data.xml. Trace the declarations produced by generate_modules_test and consumed by the create diagram script, checking whether the CRT module connections are missing there or belong in daqconf. Done means crt-grenoble-01 shows its expected input and output connections in the configuration diagram.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.