-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joss paper #296
Joss paper #296
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
…ramework into joss-paper
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #296 +/- ##
=======================================
Coverage 97.02% 97.02%
=======================================
Files 29 29
Lines 1849 1849
=======================================
Hits 1794 1794
Misses 55 55 Continue to review full report in Codecov by Sentry.
|
9b06a8c
to
be44f5d
Compare
paper/paper.md
Outdated
There is an R package for local use, but the tool does not aim to facilitate causal inference. | ||
For this, the doWhy [@sharma2020dowhy; @blobaum2024dowhy] is a python package which can be used to estimate causal effects from data. | ||
However, the package is intended for general causal inference. | ||
It does not explicitly support causal testing, nor does it support temporal feedback loops. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw that another new end-to-end causal inference framework was launched the other day: https://cstructure.dev/
Might not be relevant here but thought it's worth flagging to the CITCoM team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jmafoster1 LGTM thanks Michael!
Article for submission to the Journal of Open Source Software