Skip to content
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

[REVIEW]: konfound: An R Sensitivity Analysis Package to Quantify the Robustness of Causal #5779

Closed
editorialbot opened this issue Aug 24, 2023 · 95 comments
Assignees
Labels
accepted HTML published Papers published in JOSS R recommend-accept Papers recommended for acceptance in JOSS. review TeX Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences

Comments

@editorialbot
Copy link
Collaborator

editorialbot commented Aug 24, 2023

Submitting author: @jrosen48 (Joshua Rosenberg)
Repository: https://github.com/konfound-project/konfound
Branch with paper.md (empty if default branch):
Version: 0.4.0
Editor: @fabian-s
Reviewers: @fartist, @wjakethompson
Archive: 10.5281/zenodo.10708094

Status

status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/c53ffd4bff0f14c6533e45423d7deb82"><img src="https://joss.theoj.org/papers/c53ffd4bff0f14c6533e45423d7deb82/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/c53ffd4bff0f14c6533e45423d7deb82/status.svg)](https://joss.theoj.org/papers/c53ffd4bff0f14c6533e45423d7deb82)

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer instructions & questions

@fartist & @wjakethompson, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @fabian-s know.

Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest

Checklists

📝 Checklist for @wjakethompson

@editorialbot editorialbot added HTML R review TeX Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences labels Aug 24, 2023
@editorialbot
Copy link
Collaborator Author

Hello humans, 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:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

Software report:

github.com/AlDanial/cloc v 1.88  T=0.08 s (1123.7 files/s, 203606.0 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
HTML                            25           1134            137           5871
R                               28            435            586           2970
TeX                              8            316            113           1821
CSS                              4             98             53            445
Markdown                         5            108              0            389
JavaScript                       6             69             42            301
Rmd                              3            184            310            137
YAML                             6             19             11            128
XML                              1              0              0             75
SVG                              1              0              1             11
-------------------------------------------------------------------------------
SUM:                            87           2363           1253          12148
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1016/j.envsoft.2020.104954 is OK
- 10.1111/rssb.12348 is OK
- 10.1177/0049124100029002001 is OK
- 10.1111/j.1467-9531.2007.00186.x is OK
- 10.3102/0162373707313781 is OK
- 10.3102/0162373713493129 is OK
- 10.1016/j.jclinepi.2021.01.025 is OK
- 10.1016/j.ssresearch.2022.102815 is OK
- 10.2139/ssrn.4305243 is OK
- 10.1177/1536867X19874223 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

Wordcount for paper.md is 2100

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@fabian-s
Copy link

fabian-s commented Aug 24, 2023

👋🏼 @jrosen48 @fartist @wjakethompson this is the review thread for the paper. All of our communications will happen here from now on.

As a reviewer, the first step is to create a checklist for your review by entering

@editorialbot generate my checklist

as the top of a new comment in this thread.

These checklists contain the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. The first comment in this thread also contains links to the JOSS reviewer guidelines.

The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention openjournals/joss-reviews#REVIEW_NUMBER so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package.

We aim for reviews to be completed within about 2-4 weeks (@fartist, please let us know how much additional time you think you'll need).
We can also use EditorialBot (our bot) to set automatic reminders if you know you'll be away for a known period of time.

Please feel free to ping me (@fabian-s) if you have any questions/concerns.

@fabian-s
Copy link

fabian-s commented Sep 4, 2023

@jrosen48 : to speed up the review process it would be good to start working on konfound-project/konfound#50 while we wait for reviews by @fartist and @wjakethompson

@fabian-s
Copy link

Hi @fartist, @wjakethompson --
it's been 2 weeks, please create your checklists for the review by typing @editorialbot generate my checklist and please let us know your timeframe for completing your reviews.

@wjakethompson
Copy link

wjakethompson commented Sep 19, 2023

Review checklist for @wjakethompson

Conflict of interest

  • I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

General checks

  • Repository: Is the source code for this software available at the https://github.com/konfound-project/konfound?
  • License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
  • Contribution and authorship: Has the submitting author (@jrosen48) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
  • Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
  • Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
  • Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
  • Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

  • Installation: Does installation proceed as outlined in the documentation?
  • Functionality: Have the functional claims of the software been confirmed?
  • Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

  • A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
  • Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
  • Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
  • Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
  • Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

  • Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
  • A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
  • State of the field: Do the authors describe how this software compares to other commonly-used packages?
  • Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
  • References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

@wjakethompson
Copy link

I have completed my review, with a few outstanding issues:

  1. A few recommendations from goodpractice::gp() to ensure functionality of the package works as intended, as noted by @fabian-s. crossref: Code quality issues konfound-project/konfound#50
  2. Test coverage is very low (~27%). I think this should be substantially higher to meet the documentation criterion. crossref: Test coverage konfound-project/konfound#53
  3. There are currently no contributor guidelines. Specific guidelines should be added, and I would also recommend adding a code of conduct. crossref: Add community guidelines konfound-project/konfound#54
  4. Finally, a two notes on the paper:
    • The statement of need does not address a specific target audience. To me the implied audience is applied researchers, but that's not explicitly stated anywhere.
    • The paper does not currently describe how this software compares to existing packages for sensitivity analyses, or mention what other packages are available.
    • Some of the output in the example uses runs off the edge of the page (this may be a typesetting issue?)

@fabian-s
Copy link

@jrosen48 : to speed up the review process it would be good to start working on these while we wait for the missing review by @fartist. please let us know your timeframe for doing so.

@fartist
Copy link

fartist commented Sep 20, 2023 via email

@fabian-s
Copy link

hi @fartist, we are still waiting for your review of this JOSS submission.
It's been a month since your last post to this thread, please let us know how much more time you will need.

@fartist
Copy link

fartist commented Oct 23, 2023 via email

@fabian-s
Copy link

@fartist sure, it can't be helped if it takes this long. to speed things up at least a little bit:

no need to hold back your feedback until you are all done.

@fabian-s
Copy link

@jrosen48: to speed up the review process it would be good to start working on the issues me and https://github.com/wjakethompson have opened in your repo while we wait for the missing review by @fartist
please reply to this message so I can confirm you are still monitoring this thread.

@jrosen48
Copy link

Thank you. We will do that. I'm sorry, I am returning from parental leave and am catching up. This is a priority for the next two weeks.

@fabian-s
Copy link

fabian-s commented Nov 6, 2023

@fartist two more weeks have now passed, can we please have your review?

@fartist
Copy link

fartist commented Nov 7, 2023 via email

@fabian-s
Copy link

fabian-s commented Nov 7, 2023

@jrosen48 please adress those points in addition to the ones pointed out by the other reviewer and me.
what's your timeframe for submitting those patches?

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1016/j.envsoft.2020.104954 is OK
- 10.1177/1536867X20909696 is OK
- 10.1111/rssb.12348 is OK
- 10.1177/0049124100029002001 is OK
- 10.1111/j.1467-9531.2007.00186.x is OK
- 10.3102/0162373707313781 is OK
- 10.3102/0162373713493129 is OK
- 10.1016/j.jclinepi.2021.01.025 is OK
- 10.1016/j.ssresearch.2022.102815 is OK
- 10.2139/ssrn.4305243 is OK
- 10.1177/1536867X19874223 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@fabian-s
Copy link

@editorialbot set 10.5281/zenodo.10708094 as archive

@editorialbot
Copy link
Collaborator Author

Done! archive is now 10.5281/zenodo.10708094

@fabian-s
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1016/j.envsoft.2020.104954 is OK
- 10.1177/1536867X20909696 is OK
- 10.1111/rssb.12348 is OK
- 10.1177/0049124100029002001 is OK
- 10.1111/j.1467-9531.2007.00186.x is OK
- 10.3102/0162373707313781 is OK
- 10.3102/0162373713493129 is OK
- 10.1016/j.jclinepi.2021.01.025 is OK
- 10.1016/j.ssresearch.2022.102815 is OK
- 10.2139/ssrn.4305243 is OK
- 10.1177/1536867X19874223 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👋 @openjournals/sbcs-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#5052, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

@editorialbot editorialbot added the recommend-accept Papers recommended for acceptance in JOSS. label Feb 26, 2024
@jrosen48
Copy link

Noticed a small typo I corrected - changed &beta (thought that would render to β) to β.

@jrosen48
Copy link

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@jrosen48
Copy link

@fabian-s just thought to confirm - there is nothing I must do at this stage; is that correct?

@fabian-s
Copy link

@jrosen48 you're good -- I think @openjournals/sbcs-eics are just busy but they should get to this soon.

@oliviaguest
Copy link
Member

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1016/j.envsoft.2020.104954 is OK
- 10.1177/1536867X20909696 is OK
- 10.1111/rssb.12348 is OK
- 10.1177/0049124100029002001 is OK
- 10.1111/j.1467-9531.2007.00186.x is OK
- 10.3102/0162373707313781 is OK
- 10.3102/0162373713493129 is OK
- 10.1016/j.jclinepi.2021.01.025 is OK
- 10.1016/j.ssresearch.2022.102815 is OK
- 10.2139/ssrn.4305243 is OK
- 10.1177/1536867X19874223 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👋 @openjournals/sbcs-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#5083, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

@oliviaguest
Copy link
Member

@editorialbot accept

@editorialbot
Copy link
Collaborator Author

Doing it live! Attempting automated processing of paper acceptance...

@editorialbot
Copy link
Collaborator Author

Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.

If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.

You can copy the contents for your CITATION.cff file here:

CITATION.cff

cff-version: "1.2.0"
authors:
- family-names: Narvaiz
  given-names: Sarah
- family-names: Lin
  given-names: Qinyun
- family-names: Rosenberg
  given-names: Joshua M.
- family-names: Frank
  given-names: Kenneth A.
- family-names: Maroulis
  given-names: Spiro J.
- family-names: Wang
  given-names: Wei
- family-names: Xu
  given-names: Ran
contact:
- family-names: Rosenberg
  given-names: Joshua M.
doi: 10.5281/zenodo.10708094
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Narvaiz
    given-names: Sarah
  - family-names: Lin
    given-names: Qinyun
  - family-names: Rosenberg
    given-names: Joshua M.
  - family-names: Frank
    given-names: Kenneth A.
  - family-names: Maroulis
    given-names: Spiro J.
  - family-names: Wang
    given-names: Wei
  - family-names: Xu
    given-names: Ran
  date-published: 2024-03-09
  doi: 10.21105/joss.05779
  issn: 2475-9066
  issue: 95
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 5779
  title: "konfound: An R Sensitivity Analysis Package to Quantify the
    Robustness of Causal Inferences"
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.05779"
  volume: 9
title: "konfound: An R Sensitivity Analysis Package to Quantify the
  Robustness of Causal Inferences"

If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.

Find more information on .cff files here and here.

@editorialbot
Copy link
Collaborator Author

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

@editorialbot
Copy link
Collaborator Author

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.05779 joss-papers#5110
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05779
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

@editorialbot editorialbot added accepted published Papers published in JOSS labels Mar 9, 2024
@oliviaguest
Copy link
Member

Huge thanks to the editor: @fabian-s and the reviewers: @fartist, @wjakethompson! ✨ JOSS appreciates your work and effort. ✨ Also, big congratulations to the @jrosen48! 🥳 🍾

@editorialbot
Copy link
Collaborator Author

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.05779/status.svg)](https://doi.org/10.21105/joss.05779)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05779">
  <img src="https://joss.theoj.org/papers/10.21105/joss.05779/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05779/status.svg
   :target: https://doi.org/10.21105/joss.05779

This is how it will look in your documentation:

DOI

We need your help!

The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:

@jrosen48
Copy link

jrosen48 commented Mar 9, 2024 via email

qinyun-lin added a commit to konfound-project/konfound that referenced this issue Mar 19, 2024
* add missing dois

* Update README.md to include coding team meeting note link

* fix typo in title

* Update README.md

* change default to control group throughout

* fixed formatting issues with output

* Update helper_output_dataframe.R

The default assignment of function parameters retains the value "=", and when assigning values to the columns of the dplyr::tibble I chose to replace the assignment "=" with the value "<-", (this change can be retained or not).

* Update nonlinear_auxiliary.R

The main change comes from the assignment of variables with T changed to "TRUE", not all = changed to <-, the main principle is: function parameter assignment with "=", variable assignment for "<-". "

In addition, for the definition of the matrix "byrow = TRUE" this way usually use "=", instead of the assignment symbol <-. This is a way of passing a function parameter without using the assignment "<-" symbol.

* Update helper_plot_threshold.R

 change“ est_eff = est_eff,
  beta_threshold = beta_threshold”

to
  est_eff <- est_eff,
      beta_threshold <- beta_threshold

* Update test_cop.R

Maintain "=" for function parameter assignments and "<-" for variable assignments.

* Update test_pse.R

 Maintain "=" for function parameter assignments and "<-" for variable assignments.

* Update test_sensitivity_ln.R

T to TRUE;F to FALSE

* Update tkonfound.R

T to TRUE

* Update tkonfound_fig.R

T to TRUE; F to FALSE

* update nrow issue

* add CONTRIBUTING and update README; also change email for JR

* add CONTRIBUTING and update README; also change email for S narvaiz

* fix the bug pkonfound error #64

* fix bug error with thresh_plot output #63

* Update links in DESCRIPTION

* remove rounding in itcv calculation

* work on tests

* move

* minor edits to tests

* to close #65 and to close #70

* add tests

* update docs

* update docs

* update README

* add check badges

* setting covr up again

* undo lme4 edits

trying another approach

* Revert "undo lme4 edits"

This reverts commit 2810fd0.

* update Matrix depends

* update lme4 version

* update README

* edit description

* update tests and docs

* update testing with Qinyun

* get rid of test_all = TRUE

* remove test_all = TRUE

* remove test_all = TRUE

* patch to konfound to address test_all = TRUE error

* add pkgdown action

* address warnings in tests that were due to an unititialized column

* iterate version

* fix minor discrepancy with package name

* continue to update tests, remove unused code

* further enhancing tests

* add badges and update README

* address error in vignette

* remove mention of functionality to call multiple forms of output at once

* address error in mkonfound

* remove calling of multiple forms of output

* remove commented out code

* address NOTES in R CMD CHECK

* add a few more tests

* address note about class(flag_cov)

* work on documentation to address imports issue

* edits to JOSS paper in response to feedback from @fartist and @wjakethompson

* simplify the function test_sensitivity_ln

now almost all calculations are moved to subfunctions in nonlinear_auxiliary

* minor edits to DESCRIPTION, removing aes_string and data_frame to address warnings, and moving print output out of test_sensitivity_ln

* Update helper_output_print.R

round up 'r_con' for ITCV

* Update helper_output_print.R

* Update cop_pse_auxiliary.R(F - FALSE) (#78)

* Update cop_pse_auxiliary.R

* Update cop_pse_auxiliary.R

* Update concord1.R

* Update cop_pse_auxiliary.R

* Update helper_output_print.R

* Update helper_output_dataframe.R

* Update helper_plot_correlation.R

* Update helper_plot_threshold.R

* Update konfound-glm-dichotomous.R

* Update konfound-glm.R

* Update konfound-lm.R

* Update konfound-lmer.R

* Update konfound.R

* Update mkonfound-data.R

* Update mkonfound.R

* Update core-sensitivity-mkonfound.R

* Update pkonfound.R

* Update test_cop.R

* Update test_cop.R

* Update test_pse.R

* Update test_sensitivity.R

* Update test_sensitivity_ln.R

* Update tkonfound.R

* Update tkonfound_fig.R

* Update zzz.R

* Update helper_output_table.R

* Update nonlinear_auxiliary.R

* Update test_cop.R

* Update test_pse.R

* Update test_sensitivity_ln.R

* Update test_pse.R

* Update test_cop.R

* Update cop_pse_auxiliary.R

* Update concord1.R

* Update cop_pse_auxiliary.R

* Update core-sensitivity-mkonfound.R

* Update konfound-glm.R

* Update konfound-lmer.R

* Update mkonfound.R

* Update nonlinear_auxiliary.R

* Update zzz.R

* Update DESCRIPTION

* addressing namespace issue - trying to rewrite the NAMESPACE and docs

* delete dup doc file

* remove glue and lifecycle

* make edits to remove import lavaan and import ggplot2

* remove summary function

* remove summary function to simplify codebase and address remaining NAMESPACE issue

* Update paper.md

* Update paper.bib

* Update paper.bib

* Update paper.bib

* Update paper.bib

* Update paper.bib

* edits to paper.bib to address APA issues

* edits to the paper and .bib to related to issues 3 and 5 in #80

* minor edits to .bib

* Update CONTRIBUTING.md

* a few more edits to address formatting issues with the paper

* a few more minor edits to the paper after viewing the rendered PDF

* update README to link to CONTRIBUTING.md and minor edits to paper.md based on Ken's feedback

* Update helper_output_print.R

* Update CONTRIBUTING.md

* edits to paper.bib and paper.md in response to request from @fabian-s: openjournals/joss-reviews#5779 (comment)

* minor edit to .bib

* additional edits to .bib

* fix bug when single predictor and test_all == T

* minor copy edits to paper

* Update helper_output_print.R

* a few more edits in response to Ken's feedback

* Update test_sensitivity_ln.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* remove mice and tibble as they are not used

* Revert "remove mice and tibble as they are not used"

This reverts commit 16cad9f.

* updates to links

* add Wei to DESCRIPTION, remove unused license

* edit license

* rename license

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update konfound-lm.R

* Update konfound-lm.R

* Update konfound-lm.R

* Update konfound-lm.R

* Update konfound-lm.R

* Update helper_output_print.R

* edits in response to @fabian-s feedback on the paper

* Update helper_output_print.R

* Update helper_output_print.R

* Update helper_output_print.R

* Update test_sensitivity_ln.R

* Update test_sensitivity_ln.R

* Update test_sensitivity_ln.R

* Update test_sensitivity_ln.R

* super small edit to the paper - changing &beta so it appears correctly as β

* fix the bug when est_eff_start = 0 and needtworows

fix the bug when est_eff_start = 0 and needtworows

* update URL in README

* update urls

* CRAN submission

* Update CONTRIBUTING.md

* Update konfound.R

revised warning message for non-linear model in konfound

* update testing

no errors now in devtools::check()

* Revert "Merge branch 'master' into newitcv_output"

This reverts commit fc199f7, reversing
changes made to 04fbc43.

---------

Co-authored-by: jrosen48 <[email protected]>
Co-authored-by: Bret Staudt Willet <[email protected]>
Co-authored-by: wwang93 <[email protected]>
Co-authored-by: Joshua Rosenberg <[email protected]>
Co-authored-by: olivroy <[email protected]>
Co-authored-by: Jihoon_Choi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted HTML published Papers published in JOSS R recommend-accept Papers recommended for acceptance in JOSS. review TeX Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences
Projects
None yet
Development

No branches or pull requests

7 participants