cellmap_flow.dashboard.routes.blockwise

The pipeline builder’s blockwise steps: validate, generate (the task YAML the blockwise CLI runs), precheck, and submit (the task’s master, to LSF).

Each answers 200 whatever happens, with “valid” (validate) or “success” false beside an “error” when it cannot go on: the builder reads that flag at each step and shows the error. A body a step cannot take is refused before anything is done (the requests.Blockwise* models); a failure after that, writing the YAML, a precheck or bsub, is answered the same way.

Attributes

`logger`
`blockwise_bp`

Functions

`validate_blockwise`()	Whether the builder's pipeline is ready for blockwise processing, as
`generate_blockwise_task`()	Write the task YAML the blockwise CLI runs, for the builder's pipeline;
`precheck_blockwise_task`()	Check the task YAMLs generate wrote, as blockwise_processor.precheck
`submit_blockwise_task`()	Submit the task's master to LSF, which runs the task's workers.

Module Contents

cellmap_flow.dashboard.routes.blockwise.logger

cellmap_flow.dashboard.routes.blockwise.blockwise_bp

cellmap_flow.dashboard.routes.blockwise.validate_blockwise(): Whether the builder’s pipeline is ready for blockwise processing, as requests.BlockwisePipeline describes it: {“valid”: True, “message”}, or {“valid”: False, “error”}.

cellmap_flow.dashboard.routes.blockwise.generate_blockwise_task()

Write the task YAML the blockwise CLI runs, for the builder’s pipeline; one per bounding box when each box gets its own zarr.

{“success”: True, “task_paths”, “task_name”, “task_yaml”, “task_config”, “message”}, or {“success”: False, “error”}.

cellmap_flow.dashboard.routes.blockwise.precheck_blockwise_task(): Check the task YAMLs generate wrote, as blockwise_processor.precheck does: {“success”: True, “message”: “success”}, or {“success”: False, “error”} with the first one’s problem.

cellmap_flow.dashboard.routes.blockwise.submit_blockwise_task()

Submit the task’s master to LSF, which runs the task’s workers.

{“success”: True, “job_id”, “task_name”, “task_paths”, “log_path”, “command”, “message”}, or {“success”: False, “error”}; “job_id” is “unknown” when bsub accepted the job without naming it.