Skip to content

Migrating TRestRawReadoutAnalysisProcess to detector library #3

@jgalan

Description

@jgalan

This process is actually placed at the connectors library.

I believe it makes sense to migrate this process to the detector library. There would be a reason to prevent us from migrating this process to the domain of TRestDetector>?

If we are in the hypothetical scenario that we do not compile the raw library but we compile the detector library, this process will not be available. But if we are in the other scenario, raw library active, but detector library disabled, it will not be considered either.

But probably, we would be willing to have this process even if raw library was not compiled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    invalidThis doesn't seem rightquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions