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

Use case: pipeline multiple execution #6

Open
denisri opened this issue Jan 13, 2022 · 0 comments
Open

Use case: pipeline multiple execution #6

denisri opened this issue Jan 13, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@denisri
Copy link
Contributor

denisri commented Jan 13, 2022

Author: Yann C.

Summary: Run several time the same pipeline on the same data

Description:

This pipeline assess the ability of the system to handle several executions of the same pipeline on the same data. The main difficulties addressed would be the automatic naming of the output file names (several files generated with exactly the same metadata in inputs) and ability to identify output data according to pipeline parameter set.

The targeted pipeline could be Morphologist. It would be run three times with three different sets of parameters (TDB which parameters; for instance different normalizations). An interesting feature would be to have the possibility to add custom metadata on output data on each execution. This way the output could be sorted according to, for example, the value of my_dataset attribute that would be "first", "second" or "third".

Participants: single user

Datasets: The input dataset is not very important here but a large dataset could be interesting to assess the speed of the metadata query on output files using custom attributes.

Data flow: NA

Security: NA

Workgroup(s): pipeline, metadata

@denisri denisri added the enhancement New feature or request label Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant