pyphi.campaign#
Distribute PyPhi computations across an HTCondor pool as batch campaigns.
A campaign is a self-contained directory of serialized task files that
independent condor jobs execute via python -m pyphi.campaign run; results
are collected from per-task output files. prepare() writes the
directory, the user submits the generated submit file with condor_submit,
and status() / collect() operate purely on the directory’s
files — a task is done exactly when its output file exists and loads.
Functions
|
Reassemble a campaign's outputs into its result. |
|
Materialize a sweep as a self-contained HTCondor campaign directory. |
|
Materialize a scoped CES sweep as a campaign. |
|
Read the scope report(s) a CES campaign's collection wrote. |
|
Classify every task from the output files and refresh |
Classes
|
One shard of a scoped cause-effect computation for one system. |
|
A campaign's task ledger: which tasks are done, failed, or pending. |
|
One condor job's worth of work: the cells it owns and their context. |
|
A task's per-cell outcomes, aligned 1:1 with the task's cells. |
|
One cell's outcome: |
|
One stride of the system-partition sweep for one system. |
|
What a scoped campaign computed, excluded, and certifies. |
Submodules