-
Notifications
You must be signed in to change notification settings - Fork 0
Result folder of subpipelines. #15
Comments
@olineumann do you have any further ideas or opinions? |
A problem would be if the same instance of a subpipeline is added to multiple other pipelines... |
I would expect that there are different directories for each subpipeline if each (sub-)pipeline has set a specific path. If the path of a subpipeline is None, I would like to have the option, that the path or FileManager of the parent Pipeline is used. Maybe by a flag in the train/test routine? pipeline.train(overwrite_none_paths=True) or pipeline.train(overwrite_subpipeline_paths=True)? If we think about pipelines as modules in the future we could pass a path parameter to the __init__ method of the BasePipelineModule class? Would that solve this issue? |
Probably this would be the most intuitive solution.
Not sure, since we have to consider the time stamped folder created by the parent pipeline? I think problems may arise if the same instance of a subpipeline is used in two pipelines at the same time.. So the filemanager of the subpipeline would be the same for both parent pipelines. Consequently, in one case the time stamped folder of a parent pipeline would not be considered. |
Describe the bug
Each subpipeline stores its result in its own result folder.
To Reproduce
See Day and night example
Expected behavior
I think it would be more intuitive, if all results of one run are stored in the same time stamped folder.
Possible solutions
For subpipelines the path argument is ignored, instead they get the file manager of the containing pipeline.
The text was updated successfully, but these errors were encountered: