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

Merge changes for v0.3.0 #86

Merged
merged 63 commits into from
May 19, 2018
Merged

Merge changes for v0.3.0 #86

merged 63 commits into from
May 19, 2018

Conversation

juliangehring
Copy link
Owner

@juliangehring juliangehring commented May 19, 2018

Version 0.3.0

New Features

Changes

User-facing changes

Internal changes

Removed

Support

  • Requires julia 0.6
  • Preliminary support for julia 0.7 nightly builds

Addresses deprecation warnings and updates examples in documentation.
Compat is no longer needed since only julia 0.6 is currently supported.
Fixes #57 (part 1) by joining reports.
Add convex decreasing density estimator for π0
Adds methods and interfaces for the estimation of higher criticism scores and thresholds
Remove leftovers from julia v0.5
- Update details of software packages
- Merge papers and software packages
Simple test case: `@benchmark sortperm(pv) setup=(pv=PValues(rand(1000)))`
Before: 3.2ms
After: 110μs
Reference: 54μs: `@benchmark sortperm(pv) setup=(pv=rand(1000))`
Update documentation notebooks
Update tests and references for p-value combinations
`digamma` has been deprecated in base.
Fix slow `PValues` operations by using concrete types
Address some deprecations in future julia versions
Drop qvalues in favour of BH-adjusted p-values
* Use faster computation for sum of squares
* Use partial sorting for a faster Wilkinson combination
* Simplify boundary checks for p-value combinations
* Define return types for p-value combinations: `combine(PValues{T}, ...)` now always returns a p-value of type `T`.
* Add tests for type stability and defined return types for combinations.
- The modification of the p-values is now part of the main `adjust` functions,
no additional `_step` functions are needed: This gives us fewer functions to
worry about, cleaner code and better performance (e.g. we only
have to compute the harmonic number once per adjustment and don't need to
recompute the same value for each call of the step function).
- `stepup!` and `stepdown!` are now only performing the monotisation with
`cummin` and `cummax`; the modification of the p-values happens beforehand.
- The new variable names reflect their usage more clearly and consistently.
Fixes `ForwardStop` and `Hommel` adjustment with unsorted p-values. Note that the sorting order of the output is not well-defined for the `ForwardStop` adjustment in case the input has ties (see the test cases).
Reference citation for the convex decreasing estimator
- Don't use the vectorised min/max for a scalar
- Use `clamp` instead of max(min(x)) which is cleaner and faster
Update reference for Tippett's combination
Drops the generic `combine` methods with weights: Only the Stouffer method
currently supports weights.

Unifies the `combine` methods with `StatsBase.Weights` and `Vector` weights to
support only an `AbstractVector` input: This handles both existing cases with
one method, and provides a more flexible interface for additional types of
weights.
Unify methods for weighted Stouffer combination
Use `clamp` for better bounding of estimates
@juliangehring juliangehring merged commit 2892bb2 into master May 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant