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

Bias corrected confidence interval #237

Closed
wants to merge 14 commits into from
Closed

Bias corrected confidence interval #237

wants to merge 14 commits into from

Conversation

davidbaniadam
Copy link

Hello,
Thanks for your package.
I have included a bias corrected confidence interval in get_confidence_interval.
I have used the formulas on this page: https://www.jmp.com/support/help/14-2/bias-corrected-percentile-intervals.shtml

I hope it can get implemented.
Thanks
David

@codecov-io
Copy link

codecov-io commented May 31, 2019

Codecov Report

Merging #237 into develop will decrease coverage by 0.76%.
The diff coverage is 40%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #237      +/-   ##
===========================================
- Coverage      100%   99.23%   -0.77%     
===========================================
  Files           15       15              
  Lines         1163     1173      +10     
===========================================
+ Hits          1163     1164       +1     
- Misses           0        9       +9
Impacted Files Coverage Δ
R/generate.R 100% <ø> (ø) ⬆️
R/visualize.R 100% <100%> (ø) ⬆️
R/get_confidence_interval.R 77.5% <30.76%> (-22.5%) ⬇️

@andrewpbray
Copy link
Collaborator

Hi David,
Thanks very much for the PR - these type of extensions are great to see. I'm currently traveling but I'll have a look at this next week.

@davidbaniadam
Copy link
Author

Hi Andrew,
Thanks! I look forward to hear from you.
David

@echasnovski
Copy link
Collaborator

Hello, @davidbaniadam!

Sorry for such a huge delay. Are you still interested in this PR? It needs some git "sorcery", test and documentation updates. Functionality seems useful, so I am happy to help here.

@davidbaniadam
Copy link
Author

Hi @echasnovski I don't understand what I should do?

@echasnovski
Copy link
Collaborator

There are at least two choices here:

  • We work together on making this PR ready to merge. This includes:
    • Synchronize this git branch with current 'develop' branch.
    • Update 'testthat' tests to reflect newly added functionality.
    • Update 'roxygen2' documentation with description of this new option.
  • I take this code from here and make all necessary changes myself, while including you as original author of suggestion.

@davidbaniadam
Copy link
Author

@echasnovski If you could finish it it would be great.

@echasnovski
Copy link
Collaborator

Sure, no problem. Hope, this will take less than a year :)

@andrewpbray, @ismayc, @simonpcouch: do you agree that this update (combined with future #311) will be useful?

@ismayc
Copy link
Collaborator

ismayc commented Jun 16, 2020

Makes sense to me. Thanks for your patience, @davidbaniadam.

@simonpcouch
Copy link
Collaborator

Agreed!

@echasnovski
Copy link
Collaborator

Great! I'll try to make this during next couple of weeks.

@echasnovski
Copy link
Collaborator

This functionality is now implemented in #318. I couldn't work locally with this PR, so started a new one.

Thank you once again @davidbaniadam for suggesting this method and for initial implementation.

simonpcouch added a commit that referenced this pull request Jun 22, 2020
Updates to the get_confidence_interval() function.

* There is a new type argument option "bias-corrected" following #237's initial implementation.
* Outputs for different type values now have consistent column names (#317).
* Message is given if level isn't explicitly supplied
* Tests are now more thorough.
* Code is slightly refactored.
@github-actions
Copy link

github-actions bot commented Mar 8, 2021

This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants