dpct-run
Runtime-only package for running saved Deep Perceptual Control Theory (DPCT) individuals.
dpct-run is intended for external users who need to replay/evaluate trained DPCT individuals in Gymnasium environments without access to the full private DPCT evolution and optimization stack.
What is included
- Load saved
DHPCTIndividual.config()/best_individual.jsonfiles - Reconstruct the Keras runtime controller
- Run/evaluate individuals in Gymnasium environments
- Optional model summaries, network images, rollout history graphs, and videos
- Optional Comet
best_individual.jsondownload helper - Optional legacy
pctconfig loading/conversion support
What is deliberately not included
- Evolution (
DHPCTEvolver) - Optuna optimization (
DHPCTOptimizer) - Genetic mutation/mating APIs
- DEAP/Optuna dependencies
- Comet experiment logging for evolutionary runs
Install
From PyPI:
pip install dpct-run
Optional extras:
pip install "dpct-run[plots,video,comet,legacy]"
From GitHub:
pip install git+https://github.com/perceptualrobots/dpct-run.git
CLI examples
Show a saved config summary:
dpct-run-individual best_individual.json --show-config
Run a saved individual:
dpct-run-individual best_individual.json --run --steps 500 --seed 42
Save rollout history graphs:
dpct-run-individual best_individual.json --run --history-dir ./history --history-graphs all
Use the short alias:
dpct-run best_individual.json --run --steps 500
Python example
from dpct_run import DHPCTIndividual
config = DHPCTIndividual.load_config("best_individual.json")
individual = DHPCTIndividual.from_config(config)
fitness = individual.evaluate(steps=500, early_termination=True)
print(fitness, individual.success, individual.total_reward)
Compatibility notes
dpct-run follows the saved DPCT config schema produced by the full DPCT package. Treat best_individual.json as the primary interchange artifact.
This initial extraction targets classic Gymnasium-style environments and generic built-in fitness methods (cumulative_reward, evaluation_steps, rms, mae, adjusted RMS/MAE). Environment-specific scoring from dpct-env is optional and only used if that package is separately installed.
Metadata
Release files for dpct-run 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| dpct_run-0.1.0.tar.gz | 73.9 kB | Without provenance | Details for dpct_run-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dpct_run-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for dpct_run-0.1.0-py3-none-any.whl |
Total release size: 151.4 kB
Release files / dpct_run-0.1.0.tar.gz
| Download URL | dpct_run-0.1.0.tar.gz |
|---|---|
| Size | 73.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5db1fbd1b1f020df2e559daba42c0ba2624a1a36c8d5c891c406d565ebdb6e74
|
|
BLAKE2b-256 checksum How to use checksums |
3be47fe39d86719db6511084b45c5b890acd9508d10076834aa78441d7b059f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Release files / dpct_run-0.1.0-py3-none-any.whl
| Download URL | dpct_run-0.1.0-py3-none-any.whl |
|---|---|
| Size | 77.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f566888c133757e2664dd1e51bcf97300487b835f583ce01bd38cf4fb2e18c7a
|
|
BLAKE2b-256 checksum How to use checksums |
f22e52cda53839faf822ea6952e322e4a2eff3e2b96e712474a2773629abb83e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Security for dpct-run 0.1.0
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.