-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
a04f529
commit 28b1cec
Showing
9 changed files
with
44 additions
and
24 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,13 +9,20 @@ Suggests: | |
Author: Yalin Zhu, Wenge Guo | ||
Maintainer: Yalin Zhu <[email protected]> | ||
BugReports: https://github.com/allenzhuaz/FixSeqMTP/issues | ||
Description: Several generalized/directional Fixed Sequence Multiple Testing Procedures (g- | ||
FSMTPs/d-FSMTPs) are developed for testing a sequence of pre-ordered hypotheses while | ||
controlling the FWER, FDR and Directional Error (mdFWER). All three FWER controlling g-FSMTPs are designed under arbitrary dependence, which allow any number of acceptances. Two FDR controlling g-FSMTPs are respectively designed under arbitrary dependence and independence, which allow more but a given number of acceptances. Two mdFWER controlling d-FSMTPs are respectively designed under arbitrary dependence and independence, which can also make directional decisions based on the signs of the test statistics. The main | ||
functions for each proposed g-FSMTPs are designed to calculate adjusted p-values | ||
and critical values, respectively. For users' convenience, the output results | ||
also include the option of decision rules for convenience. | ||
Description: Several generalized / directional Fixed Sequence Multiple Testing | ||
Procedures (FSMTPs) are developed for testing a sequence of pre-ordered | ||
hypotheses while controlling the FWER, FDR and Directional Error (mdFWER). | ||
All three FWER controlling generalized FSMTPs are designed under arbitrary | ||
dependence, which allow any number of acceptances. Two FDR controlling | ||
generalized FSMTPs are respectively designed under arbitrary dependence and | ||
independence, which allow more but a given number of acceptances. Two mdFWER | ||
controlling directional FSMTPs are respectively designed under arbitrary | ||
dependence and independence, which can also make directional decisions based | ||
on the signs of the test statistics. The main functions for each proposed | ||
generalized / directional FSMTPs are designed to calculate adjusted p-values | ||
and critical values, respectively. For users' convenience, the functions also | ||
provide the output option for printing decision rules. | ||
License: GPL (>= 2) | ||
Encoding: UTF-8 | ||
LazyData: TRUE | ||
RoxygenNote: 5.0.1 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
Version: 1.0 | ||
|
||
RestoreWorkspace: Default | ||
SaveWorkspace: Default | ||
AlwaysSaveHistory: Default | ||
|
||
EnableCodeIndexing: Yes | ||
UseSpacesForTab: Yes | ||
NumSpacesForTab: 2 | ||
Encoding: UTF-8 | ||
|
||
RnwWeave: Sweave | ||
LaTeX: pdfLaTeX | ||
|
||
AutoAppendNewline: Yes | ||
StripTrailingWhitespace: Yes | ||
|
||
BuildType: Package | ||
PackageUseDevtools: Yes | ||
PackageInstallArgs: --no-multiarch --with-keep.source | ||
PackageRoxygenize: rd,collate,namespace |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Binary file not shown.