The question | The tools | The plan | Scenario A: the full trial | Scenario B: one site, one replicate, three rates | The plan as a file | Writing a plan | The schema and the repair loop | A mistyped edge | Provenance and a targets pipeline
Package: conductoR 0.2.0
Max Moldovan
conductoR: Perform a Contract-Typed Analytical Plan Across Analytics Components
Declares an analytical plan as a directed acyclic graph of nodes, each bound to a tool that returns an 'orchestraManifest' result, and performs it in topological order. Every edge is typed by the inferential target the upstream node declares, and a mismatched handoff stops the run before the downstream node executes rather than coercing across a contract boundary. Two epistemic operators are built in: a power-aware abstention gate that refuses to pass a null verdict the design could not have resolved, and a triangulation operator that reconciles any number of independent lenses on one question. A plan serialises to 'YAML' and back, compiles to a 'targets' pipeline, and every run writes a provenance record with the integrity chain of the manifests it produced.
Authors:
conductoR_0.2.0.tar.gz
conductoR_0.2.0.zip(r-4.7-any)conductoR_0.2.0.zip(r-4.6-any)conductoR_0.2.0.zip(r-4.5-any)
conductoR_0.2.0.tgz(r-4.6-any)conductoR_0.2.0.tgz(r-4.5-any)
conductoR_0.2.0.tar.gz(r-4.7-any)conductoR_0.2.0.tar.gz(r-4.6-any)
conductoR_0.2.0.tgz(r-4.6-emscripten)
manual.pdf |manual.html✨
DESCRIPTION |NEWS
card.svg |card.png
conductoR/json (API)
| # Install 'conductoR' in R: |
| install.packages('conductoR', repos = c('https://max578.r-universe.dev', 'https://cloud.r-project.org')) |
Bug tracker:https://github.com/max578/conductor/issues
Last updated from:3ecdb1b23a (on main). Checks:9 OK. Indexed: yes.
| Target | Result | Time | Files | Syslog |
|---|---|---|---|---|
| linux-devel | OK | 138 | ||
| source / vignettes | OK | 274 | ||
| linux-release | OK | 119 | ||
| macos-release | OK | 108 | ||
| macos-oldrel | OK | 125 | ||
| windows-devel | OK | 101 | ||
| windows-release | OK | 101 | ||
| windows-oldrel | OK | 69 | ||
| wasm-release | OK | 98 |
Exports:compile_to_targetsconductconduct_stepdecision_to_manifestedgelens_to_manifestnodeoap_nodeoap_planplan_from_jsonplan_from_yamlplan_nodeplan_orderplan_schemaplan_to_yamlplan_validateregister_toolresolve_toolrun_provenancesame_planterminal_target
Dependencies:digestjsonliteorchestraManifestS7yaml
Readme and manuals
Help Manual
| Help page | Topics |
|---|---|
| Compile a plan to a targets script | compile_to_targets |
| Perform a plan | conduct |
| Perform one node | conduct_step |
| Lift a decision into a decisions manifest | decision_to_manifest |
| Declare a typed edge | edge |
| Lift a binary verdict into a treatment-effects manifest | lens_to_manifest |
| Declare a node | node |
| A node of an analytical plan | oap_node |
| An analytical plan | oap_plan |
| Read a plan from JSON | plan_from_json |
| Read a plan from YAML | plan_from_yaml |
| Fetch a node by id | plan_node |
| Topological order of a plan | plan_order |
| The JSON Schema of the plan language | plan_schema |
| Write a plan as YAML | plan_to_yaml |
| Check a plan file and list every problem | plan_validate |
| Register a tool by name | register_tool |
| Resolve a tool reference | resolve_tool |
| A run's provenance as a table | run_provenance |
| Check that two runs used the same plan | same_plan |
| The target that holds a plan's terminal result | terminal_target |