Skip to content

[Feature]: Required changes once daphne v2 is discontinued #257

@mroda88

Description

@mroda88

Description

The current DaphneApplication supports both v2 and mezzanine boards. This makes the schema a bit fragile: for example

  • a DaphenApplication without hermes configuraiton is valid
  • There are plenty of objects that refer to v2

The code and the schema should be clean up when the v2 line is discontinued.

Potential impact radius

Medium

Reason for change

We know that eventually Daphne v2 will be discontinued.

Suggested implementations

This list is not comprehensive at the time of writing and it will grow over time.

  • Allow only Network Detector to Daq connections in the DaphneApplications
  • Require one Hermes configuration at least
  • Clean up the configuration object names from v2

Testing suggestions

Running correctly with Daphne v3.

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions