ciflyr
Reachability-Based Primitives for Graphical Causal Inference
v0.1.2
·
Oct 5, 2025
·
MIT + file LICENSE
Description
Provides a framework for specifying and running flexible linear-time reachability-based algorithms for graphical causal inference. Rule tables are used to encode and customize the reachability algorithm to typical causal and probabilistic reasoning tasks such as finding d-connected nodes or more advanced applications. For more information, see Wienöbst, Weichwald and Henckel (2025) <doi:10.48550/arXiv.2506.15758>.
Downloads
148
Last 30 days
20058th
578
Last 90 days
2K
Last year
Trend: -16.4% (30d vs prior 30d)
CRAN Check Status
13
OK
Show all 13 flavors
| Flavor | Status |
|---|---|
| r-devel-linux-x86_64-debian-clang | OK |
| r-devel-linux-x86_64-debian-gcc | OK |
| r-devel-linux-x86_64-fedora-clang | OK |
| r-devel-linux-x86_64-fedora-gcc | OK |
| r-devel-windows-x86_64 | OK |
| r-oldrel-macos-arm64 | OK |
| r-oldrel-macos-x86_64 | OK |
| r-oldrel-windows-x86_64 | OK |
| r-patched-linux-x86_64 | OK |
| r-release-linux-x86_64 | OK |
| r-release-macos-arm64 | OK |
| r-release-macos-x86_64 | OK |
| r-release-windows-x86_64 | OK |
Check History
OK 13 OK · 0 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE May 2, 2026
NOTE 11 OK · 1 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Apr 25, 2026
NOTE
r-release-macos-x86_64
compiled code
File ‘ciflyr/libs/ciflyr.so’: Found non-API calls to R: ‘R_MissingArg’, ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
OK 14 OK · 0 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Apr 16, 2026
NOTE 13 OK · 1 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Mar 27, 2026
NOTE
r-devel-linux-x86_64-debian-gcc
compiled code
File ‘ciflyr/libs/ciflyr.so’: Found non-API calls to R: ‘R_MissingArg’, ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.