Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filtering in Mantid reduction backend based on meta data #8

Closed
SimonHeybrock opened this issue Nov 10, 2015 · 1 comment
Closed

Filtering in Mantid reduction backend based on meta data #8

SimonHeybrock opened this issue Nov 10, 2015 · 1 comment

Comments

@SimonHeybrock
Copy link
Contributor

Mantid supports this, e.g., via the two algorithms GenerateEventsFilter and FilterEvents. There are a few questions regarding interaction with the stream, however:

  • Can meta data be late? Jon says (2015-11-11): Aggregator will work with one pulse delay and send meta data together with corresponding pulse. So we can work under that assumption for now (but this may change).
  • Consider a slowly changing variable, e.g., temperature. Will its value be transmitted for each pulse, or not? If not the Mantid reduction backend must be capable of inferring its value from previously received frames. See Last-value cache for meta data #17.
@SimonHeybrock
Copy link
Contributor Author

This is bascially identical to #20, closing it for now.

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

No branches or pull requests

1 participant