Skip to content

Use specific exception type when encountering unsupported versions of input files #2676

Open
@maxnoe

Description

Please describe the use case that requires this feature.

When encountering unsupported (not yet or old, dropped versions) we raise inconsistent, generic python errors.

ValueError for the optics table, OSError else (I think it used to be the more fitting IOError but was changed in an automatic refactoring.

Describe the solution you'd like

We should use a specific exception in this case that is a ctapipe exception type for this explicit purpose.

Additional context

LST chain wants to add back explicit support for older files, which would be better handled with a specific exception type.
cta-observatory/cta-lstchain#1329 (comment)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions