Skip to content

[essreduce] Add a parameter in unwrap workflow to decide whether to raise or publish blank table if chopper is unusable #758

Description

@nvaytet

In #751 , if a chopper frequency is not synced with the source, we change that chopper to just block everything and the result is a LUT with all NaNs.

This is what we want for livedata, as chopper settings can be changed on the fly and we don't want the entire workflow to crash.
However, when processing from files, it may be better to just raise with a good error message, so that the user doesn't wonder why all wavelengths are NaN.

We should add a parameter on the workflow: raise or block, with default raise. Block means the chopper contributes no openings (empty open and close arrays).

Activity

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

Metadata

Metadata

Assignees

Labels

essreduceIssues for essreduce.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions