-
Notifications
You must be signed in to change notification settings - Fork 4
Compound tasks #6
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
Comments
That's an interesting topic. Would also be interesting from a user side if there is a compound task to call that does both. i.e. a user should not need to know that parsing form yokogawa to zarr needs to task, all they think is "I want my yokogawa data in a Zarr file". |
For the record, yesterday we re-discussed the option of a compound task, possibly made of pre/main/post phases. For the moment we did not go too far into this direction, apart from noting that this "compound task" would still need to correspond to two actual tasks being run (independently from how transparent this is for the user), or it would be difficult to parallelize the second task (the "fill" one, in a create&fill scenario). |
Good summary. On the priority of this: Compound tasks in the way described above may offer a useful simplification from the users perspective. It's not a current priority to push those though, as we first want to build the features that would make up the useful pre-phases. |
Additional notes on what we could do with it were made here: #514 |
This issue in the current form is made obsolete by ongoing V2 work. |
Uh oh!
There was an error while loading. Please reload this page.
We have two cases with a create&fill structure:
create_zarr_structure
, orreplicate_zarr_structure
);yokogawa_to_zarr
, ormaximum_intensity_projection
).We could find a new way to define them together.
Note that this only concerns fractal, while the tasks would remain as they are now.
The text was updated successfully, but these errors were encountered: