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

Recalculate component positions when motion axis updates #76

Closed
matthew-d-jones opened this issue May 10, 2021 · 1 comment
Closed

Recalculate component positions when motion axis updates #76

matthew-d-jones opened this issue May 10, 2021 · 1 comment

Comments

@matthew-d-jones
Copy link
Contributor

matthew-d-jones commented May 10, 2021

The full chain of transformations from the run start message should be cached and new pixel positions emitted with the streamed data chunk when one of the transformation values changes (motion axis has new value).
This can occur when one or more of the transformations in the chain contains a stream.

It might make sense to tackle #34 first because it is closely related and probably easier to implement.

@matthew-d-jones matthew-d-jones changed the title Recalculate pixel positions when motion axis updates Recalculate component positions when motion axis updates Jul 7, 2021
@Tom-Willemsen Tom-Willemsen self-assigned this Feb 14, 2022
@Tom-Willemsen Tom-Willemsen removed their assignment Mar 10, 2022
@SimonHeybrock
Copy link
Member

For future reference, scipp/essreduce#96.

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

3 participants