stroblme
34243e6902
save_artifact/load_artifact outside a node use the worker's own store code in $FLUKSIO_ARTIFACT_DIR or <tmp>/fluksio-artifacts, so a node can be called by hand. --follow prints status changes and each node's resource wait; the placer's waiting snapshot now carries the run. fluksio cancel <run>...
10 lines
514 B
Python
10 lines
514 B
Python
"""A research package that knows nothing about Fluksio, except where it says so.
|
|
|
|
Each node is a thin wrapper over a plain function: `prepare` stores what
|
|
`make_rows` made, `fit` yields what `train_curve` computed, `evaluate` reports
|
|
what `score` worked out. That split is the point — the arithmetic stays plain
|
|
Python, so `python -m myresearch.pipeline` runs it with no engine anywhere,
|
|
while the wrappers own the artifact storage. `fluksio sync examples/myresearch`
|
|
is what turns the wrappers into a flow.
|
|
"""
|