-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
[PRE REVIEW]: The Causal Testing Framework #7671
Comments
Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks. For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: ✅ License found: |
Five most similar historical JOSS papers: GRAPL: A computational library for nonparametric structural causal modelling, analysis and inference CORA and LOGIGRAM: A Duo of Python Packages for Combinational Regularity Analysis (CORA) chronovise: Measurement-Based Probabilistic Timing Analysis framework Monte Carlo / Dynamic Code (MC/DC): An accelerated Python package for fully transient neutron transport and rapid methods development dtrackr: An R package for tracking the provenance of data |
👋 @jmafoster1 - thanks for your submission. I'll assign myself to edit it. Please suggest ~5 potential reviewers. You can search the list of people that have already agreed to review and may be suitable for this submission. Or people who aren't in the JOSS system would also be ok. If you know their GitHub usernames, then please mention them here in this thread (without tagging them with an @). |
@editorialbot assign me as editor |
Assigned! @danielskatz is now the editor |
@danielskatz, thanks for being our editor. Some potential reviewers could be the following (in no particular order): From the list of people:
Others:
I have included as many as possible as I know people are very busy. |
👋 @VincentStimper & @tedinburgh, would one or both of you be willing to review this submission for JOSS? |
👋 @afd & @juliensiebert & @torkar, would one or more of you be willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html |
@editorialbot add @akothen as review 👋 @akothen - Thanks for volunteering to review (via email). I'm adding you now, but we won't start the review until we get a few more reviewers as well. |
I'm sorry human, I don't understand that. You can see what commands I support by typing:
|
@editorialbot add @akothen as reviewer |
@akothen added to the reviewers list! |
Sorry, about too much on my plate coming months. |
@editorialbot add yinfangchen as reviewer 👋 @yinfangchen - Thanks for volunteering to review (via email). I'm adding you now, but we won't start the review until we get a few more reviewers as well. |
I can't add that reviewer: yinfangchen is not a username |
@editorialbot add @yinfangchen as reviewer |
@yinfangchen added to the reviewers list! |
Submitting author: @jmafoster1 (Michael Foster)
Repository: https://github.com/CITCOM-project/CausalTestingFramework
Branch with paper.md (empty if default branch):
Version: v9.0.2
Editor: @danielskatz
Reviewers: @akothen, @yinfangchen
Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @jmafoster1. Currently, there isn't a JOSS editor assigned to your paper.
@jmafoster1 if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: