Skip to main content

seamm_scheduler

GitHub Actions Build Status

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: #SBATCH directives, sbatch, squeue/sacct (with --json where the cluster has it, text otherwise), scancel.
  • seamm_scheduler.pbs.Pbs -- PBS Professional / OpenPBS: #PBS directives with one select statement, 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 rsync for 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.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for seamm-scheduler 2026.11.4
File Size Uploaded Provenance Actions
seamm_scheduler-2026.11.4.tar.gz 71.8 kB Without provenance Details for seamm_scheduler-2026.11.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for seamm-scheduler 2026.11.4
File Interpreter ABI Platform Actions
seamm_scheduler-2026.11.4-py3-none-any.whl Python 3 none any Details for seamm_scheduler-2026.11.4-py3-none-any.whl

Total release size: 152.0 kB

Release files / seamm_scheduler-2026.11.4.tar.gz

Download URL seamm_scheduler-2026.11.4.tar.gz
Size 71.8 kB
Tags Source
SHA-256 checksum
How to use checksums
ae62351d694abcb0d932665901ce1ba8338b02f9f21b78025bdc8ac3a207a38e
BLAKE2b-256 checksum
How to use checksums
e2c571bef9543b4a1e3d4590ac13e604d8a6dc5f73b122c89fd0333cfdc541da
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.4-py3-none-any.whl

Download URL seamm_scheduler-2026.11.4-py3-none-any.whl
Size 80.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
74e373b0d78ca00d4d26bd7fbb2089f8a206b0b8882d3f481405e68a52b85fb2
BLAKE2b-256 checksum
How to use checksums
a8448179b387dc8c13729d31be7df05cbafaa0cc72afa4c1624f5bd4d1de0891
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.4

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page