Test Dask Script
The test-dask script is designed to test deploying two instances of
a Dask execution engine and executing a simple function on each one.
The sequence of actions carried out by the script is:
Claims processing block
Sets processing block
statusto'WAITING'Waits for
resources_availableto beTrueThis is the signal from the processing controller that the script can start
Sets processing block
statusto'RUNNING'Deploys two Dask execution engines in parallel
Does some simple operations. Constructs a graph to add two numbers together and computes the result by calling the ‘compute’ method.
Sets processing block
statusto'FINISHED'
Full description of processing block parameters of this script can be found at the bottom of this page.
Processing block parameters
- pydantic settings TestDaskParams
test-dask script parameters
Show JSON schema
{ "title": "test-dask", "description": "test-dask script parameters", "type": "object", "properties": { "n_workers": { "default": 2, "description": "Number of workers for Dask processing", "title": "Number of workers", "type": "integer" } }, "additionalProperties": false }
- Config:
strict: bool = True
extra: str = forbid
arbitrary_types_allowed: bool = False
validate_assignment: bool = True
title: str = test-dask
- Fields:
Changelog
1.1.0
use ska-sdp-scripting 3.0.1 and dask 2026.1.2 (MR428)
1.0.1
use ska-sdp-scripting 2.0.0 (MR360)
1.0.0
0.8.0
Update ska-sdp-scripting to 0.12.0 (MR202)
Processing script reports internal errors in pb state (MR185)
Pydantic model included in documentation (MR189)
JSON parameter schema added to tmdata (MR186)
Validate processing block parameters using scripting library 0.10.0 (MR180)
Added processing block parameter JSON schema and Pydantic model (MR174, MR177)
0.7.0
0.6.0
Update to scripting library 0.7.0
BREAKING This and newer versions are not compatible with SDP version < 0.21.0
0.5.0
Update to scripting library 0.6.1
0.4.0
Update to latest scripting library (0.5.0). This required the update of how phase.wait_loop is used in the script.
0.3.0
Port to use SDP scripting library (formerly known as the workflow library).
0.2.6
Use dependencies from the central artefact repository and publish the workflow image there.
0.2.5
Ported to use the latest version of workflow library (0.2.4).
0.2.4
use python:3.9-slim as the base docker image
slimmed down the requirements file as well