seamm_scheduler
Queueing systems for SEAMM: one module per queueing system behind a shared
Scheduler interface, with local and ssh transports and staging.
seamm_scheduler.slurm.Slurm-- SLURM:#SBATCHdirectives,sbatch,squeue/sacct(with--jsonwhere the cluster has it, text otherwise),scancel.seamm_scheduler.pbs.Pbs-- PBS Professional / OpenPBS:#PBSdirectives with oneselectstatement,qsub,qstat,qdel. Tested against recorded output only so far.QueueBackend(scheduler, transport)-- submit a script, poll many jobs in as few commands as the scheduler allows, cancel, count the user's jobs.LocalTransport/SshTransport-- run the commands on this host, or on a login node over passwordless ssh.LocalStager/RsyncStager-- move job (or task) directories when the caller and the cluster share no filesystem.seamm_scheduler.config-- the JobServer's<root>/<jobserver-name>.ini: each section is a target, describing where a job's flowchart evaluator runs and, with the optional task keys, where its tasks run.
Every scheduler translates the same scheduler-neutral resources (ntasks,
cpus_per_task, mem_per_cpu, ngpus, walltime, partition, account,
qos, nodes) into its own directives, and reports job states in one small
vocabulary (pending, running, completed, cancelled, failed).
The package has no dependencies. It is used by seamm_jobserver (whole
flowcharts as batch jobs) and seamm_exec's task layer (bundles of tasks as
batch jobs). seamm_slurm, which this package generalizes, remains as a
compatibility shim that re-exports from here.
Features
- SLURM 20.11 (no
--json) to 25.11 (nested JSON) handled transparently - Per-user queue limits (
count_jobs()) - Poll failures (an ssh outage) are reported as such, never as vanished jobs
- One
rsyncfor many directories (push/pull)
Acknowledgements
Developed by the Molecular Sciences Software Institute (MolSSI), which receives funding from the National Science Foundation under award CHE-2136142.
Metadata
Release files for seamm-scheduler 2026.11.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| seamm_scheduler-2026.11.8.tar.gz | 72.4 kB | Without provenance | Details for seamm_scheduler-2026.11.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| seamm_scheduler-2026.11.8-py3-none-any.whl | Python 3 | none | any | Details for seamm_scheduler-2026.11.8-py3-none-any.whl |
Total release size: 153.2 kB
Release files / seamm_scheduler-2026.11.8.tar.gz
| Download URL | seamm_scheduler-2026.11.8.tar.gz |
|---|---|
| Size | 72.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c78a9a9769b18d0518e27a72b27ef4cbb2f771382be847e744a7662ac6fe4b8
|
|
BLAKE2b-256 checksum How to use checksums |
dca2ed907ad5739ad2bea93fb7d275889ea18df5c5a1dac302cf26c3642198f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / seamm_scheduler-2026.11.8-py3-none-any.whl
| Download URL | seamm_scheduler-2026.11.8-py3-none-any.whl |
|---|---|
| Size | 80.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d67d77b639b0059e4f46f1155beba508cdbe9ad12c99422e0d8572d79fee2c9f
|
|
BLAKE2b-256 checksum How to use checksums |
61e0289982b8bf0d07decd8559f67d2f4aedf8da4a2e3540257c82f34cc1b1e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for seamm-scheduler 2026.11.8
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.