juniper-cascor-worker
Distributed candidate-training worker for the Juniper Cascade-Correlation platform.
juniper-cascor-worker connects outbound to a running juniper-cascor instance, receives
candidate-unit training tasks, trains them, and returns the trained candidates for selection into the
growing network. Run several workers to parallelise candidate-pool training across hosts.
Part of the Juniper platform. juniper-cascor-worker is the distributed candidate-training worker for juniper-cascor in Juniper — a multi-package ML research platform built around constructive (Cascade-Correlation) and recurrent neural networks. It is managed by cascor over a wire protocol, with no code-import dependency between the two.
Install
pip install juniper-cascor-worker
Run
The default WebSocket mode connects to a juniper-cascor instance:
juniper-cascor-worker \
--server-url ws://<cascor-host>:8200/ws/v1/workers \
--auth-token <worker-token>
…or via the canonical environment variables:
export JUNIPER_CASCOR_WORKER_SERVER_URL=ws://<cascor-host>:8200/ws/v1/workers
export JUNIPER_CASCOR_WORKER_AUTH_TOKEN=<worker-token>
juniper-cascor-worker
Legacy --legacy mode (a multiprocessing.managers worker) is deprecated and kept only for
transitional deployments.
Configuration
Key environment variables (WebSocket mode); the full surface and the deprecated CASCOR_* legacy
aliases (pre-CFG-06) are documented in AGENTS.md:
| Variable | Required | Default | Notes |
|---|---|---|---|
JUNIPER_CASCOR_WORKER_SERVER_URL |
Yes | — | Worker endpoint URL (ws:// or wss://) |
JUNIPER_CASCOR_WORKER_AUTH_TOKEN |
No | empty | Token sent as the X-API-Key header |
JUNIPER_CASCOR_WORKER_HEARTBEAT_INTERVAL |
No | 10.0 |
Seconds between heartbeats |
JUNIPER_CASCOR_WORKER_TASK_TIMEOUT |
No | 3600.0 |
Max seconds for a single training task |
JUNIPER_CASCOR_WORKER_TLS_CERT / _TLS_KEY / _TLS_CA |
No | unset | mTLS client cert / key / CA bundle |
Docker
docker build -t juniper-cascor-worker:latest .
docker run --rm \
-e JUNIPER_CASCOR_WORKER_SERVER_URL=ws://<cascor-host>:8200/ws/v1/workers \
-e JUNIPER_CASCOR_WORKER_AUTH_TOKEN=<worker-token> \
juniper-cascor-worker:latest
The Dockerfile defaults to WebSocket mode against ws://juniper-cascor:8200/ws/v1/workers. For the
full stack, see juniper-deploy.
Status
Live on PyPI. The current version is shown by the badge above; see CHANGELOG.md.
License
MIT — see LICENSE.
Metadata
Release files for juniper-cascor-worker 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| juniper_cascor_worker-0.6.1.tar.gz | 97.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| juniper_cascor_worker-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 135.8 kB
Release files / juniper_cascor_worker-0.6.1.tar.gz
| Download URL | juniper_cascor_worker-0.6.1.tar.gz |
|---|---|
| Size | 97.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c69d9439b9191269811a64dd171d68b75b49759a27575c26f2a89c99aba6c900
|
|
BLAKE2b-256 checksum How to use checksums |
a960f1ccfde602cae5732936b63fac9707c4ac85230b59346dd3b81e8a355100
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency logRelease files / juniper_cascor_worker-0.6.1-py3-none-any.whl
| Download URL | juniper_cascor_worker-0.6.1-py3-none-any.whl |
|---|---|
| Size | 38.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1b5b7fc0b7ab909b25ad7852f186fb59b91da1d06dae8821020c4e1147c3e242
|
|
BLAKE2b-256 checksum How to use checksums |
f3639f4024f93faa2dfa60d6b8945877d7334feda7d4898e0675b99f018016fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency log