Make use the time of the acquisition.
There are steps should be performed per image and can be done right after the image is available. These steps are checking the images and preprocessing them. The process does this steps would be able to check the machinery of the microscope and send warnings to the right person if something happens (like the microscope stops acquiring).
In the “Process Files” step (see graph above), different image checks and processings should be done:
The created files, should then be placed in the corresponding openBIS dropbox for storage.
|Using the workflow manager||Separate service like integration integrated in the workflow manager code||Implementing as separate application|
|Pros||- We could use the workflow description to describe the necessary steps and to configure notifications. |
- We don't need to develop a new daemon if we can get the workflow manager to schedule this acquisition “workflows”.
|- It would be possible to reuse existing solutions from the source of the workflow-manager.|
- The processing can be tailored for this image based processing to provide effective solution.
- It can be started separately or from the daemon.
|- The processing can be tailored for this image based processing to provide effective solution.|
|Cons||- Probably using the workflow manager would be overkill, specially if this tasks are computationally cheap. Several database statements/loggings per tool per file. |
- The workflow engine needs modification to run this processing on unregistered datasets which are not directories.
|- The whole logic would be defined in the source or if we try to make it general/ customizable it would lead to develop similar things than in the scheduler of the workflow manager.||- The whole logic would be defined in the source or if we try to make it general/ customizable it would lead to develop similar things than in the scheduler of the workflow manager.|