SO Campaign Manager
This repository holds the code of the software tools that will run the mapmaking campaign on So resources.
The project has three big aspects:
- Providing a method to submit new workflows, update existing ones and delete via configuration or a series of commands
- Based on the workflow configuration set the resource requirement accordingly and submit it to SLURM. Resource configuration can be based on:
- Total size of observations and their file distribution
- A specific observation mapping between processes and files
- Node memory and node processor performance.
- Use a workflow management tool to execute all workflows in the minimum amount of time.
Documentation
📚 Full Documentation - Complete documentation including:
- Installation Guide - Setup and installation instructions
- Quick Start - Get started quickly with examples
- User Guide - Comprehensive usage guide
- API Reference - Complete API documentation
- Workflow Guide - Available workflows and how to use them
- Developer Guide - Contributing and development setup
Building Documentation
To build the HTML documentation locally:
cd docs
pip install sphinx sphinx-rtd-theme
make html
The documentation will be available in docs/_build/html/index.html.
Quick Start
Install the package:
pip install so_campaign_manager
Create a configuration file (campaign.toml):
[campaign]
deadline = "2d"
[campaign.resources]
nodes = 4
cores-per-node = 112
[campaign.ml-mapmaking]
context = "file:///path/to/context.yaml"
output_dir = "/path/to/output"
bands = "f090"
# ... other parameters
Run your campaign:
socm -t campaign.toml
For detailed examples and configuration options, see the documentation.
For information on contributing, branching model, and code style requirements, see CONTRIBUTING.md.
Release files for so-campaign-manager 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| so_campaign_manager-0.2.0.tar.gz | 238.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| so_campaign_manager-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 308.7 kB
Release files / so_campaign_manager-0.2.0.tar.gz
| Download URL | so_campaign_manager-0.2.0.tar.gz |
|---|---|
| Size | 238.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d101d5dfe5dd89effe1da8657fb19681761329c1a09b244ac913f9b84b96fa99
|
|
BLAKE2b-256 checksum How to use checksums |
14da5620c12bc969a2a71220165b504724e11858e3d33fe24cb50bf6b1233b7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / so_campaign_manager-0.2.0-py3-none-any.whl
| Download URL | so_campaign_manager-0.2.0-py3-none-any.whl |
|---|---|
| Size | 69.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4eb855e4dc158c55aab1271c536e1b4b62de5d410b9a774da9b238ba15f6bbdb
|
|
BLAKE2b-256 checksum How to use checksums |
b5c086391ec54888b779fed4fec08bf548b81ab2815a883e4d27007d4b11a813
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency log