Diff between a base DAG and an augmented DAG — causal_augment

3.10.0

Reference
- Capstone — six pillars integrated
- Cross-pillar campaign
- Pilar 1 — Causal AI
- Causal backdoor on br_cerrado
- Causal on 1 095 real WoSIS profiles
- Causal-discovery trio (expert × LLM × data-driven)
- LLM-KG benchmark (Gemma 4 × GPT × Claude)
- Annotation workflow (pre-annotation + Shiny review)
- Pilar 2 — Physics-Informed ML
- Parametric ODE + Neural ODE
- Pilar 3 — 4D Pedometry
- ConvLSTM on synthetic cube
- Real MODIS + NASA POWER + EnKF
- Pilar 4 — Foundation Models
- SimCLR / MoCo embeddings
- Pilar 5 — Active Learning
- Hybrid policy + physics gate
- SoilGrids-BR live
- Pilar 6 — Quantum ML
- ZZFeatureMap + Q-KRR
- Cross-pillar bridges
- Pilar 1 × Pilar 4 — Foundation IVs
- Pilar 4 × Pilar 6 — Quantum-foundation kernel
- Unified infrastructure
- Unified uncertainty API
- Case — end-to-end Cerrado benchmark
- Releases
- v2.0.0 — Quantum kernel × Foundation (Pilar 4 × Pilar 6)
- v1.9.x — Foundation embeddings as causal IVs + Sargan/Cinelli-Hazlett
- v1.8.x — LLM benchmark infrastructure + Shiny annotation tool
- v1.7.x — Capstone vignette + native-query calibration + causal discovery
- Changelog

Convenience helper that shows which edges are inherited from the base_dag, which are new from the Knowledge Graph, and (if any) which were rejected as cycle-forming. Handy for vignettes and auditing.

Usage

causal_augment_diff(base_dag, augmented_dag)

Arguments

base_dag, augmented_dag: Two dagitty DAG objects — typically the second is the return value of causal_augment_dag().

Value

A data frame with columns cause, effect, origin ("base" or "kg").