Re-architect around pipelines
Removed loosely structured workflows. Now compose multistep work as pipeline modules, e.g. base.pipelines.segment, with the following blocks:
- input parameters (Pydantic model)
- output record (Pydantic model)
- API mapping and docstring; also any special input validation that doesn't play well Pydantic, and special exception routing
- pipeline logic function, which pushes results onto PipelineTrace
Refactored existing base and ilastik "workflows" into this pattern.
Merge request reports
Activity
Filter activity
mentioned in commit 541953cd
mentioned in issue #5 (closed)
mentioned in issue #7 (closed)
mentioned in issue #15 (closed)
mentioned in issue #9 (closed)
mentioned in issue #11 (closed)
mentioned in issue #39 (closed)
mentioned in issue #44 (closed)
Please register or sign in to reply