retrodesign (Q53296): Difference between revisions
From MaRDI portal
Changed an Item |
Swh import (talk | contribs) SWHID from Software Heritage |
||||||||||||||
| (2 intermediate revisions by 2 users not shown) | |||||||||||||||
| Property / source code repository | |||||||||||||||
| Property / source code repository: https://github.com/cran/retrodesign / rank | |||||||||||||||
Normal rank | |||||||||||||||
| Property / Software Heritage ID | |||||||||||||||
| Property / Software Heritage ID: swh:1:snp:61ca431c266d3c31081bf886675212a0bf2e493a / rank | |||||||||||||||
Normal rank | |||||||||||||||
| Property / Software Heritage ID: swh:1:snp:61ca431c266d3c31081bf886675212a0bf2e493a / qualifier | |||||||||||||||
| Property / Software Heritage ID: swh:1:snp:61ca431c266d3c31081bf886675212a0bf2e493a / qualifier | |||||||||||||||
point in time: 23 November 2023
| |||||||||||||||
| links / mardi / name | links / mardi / name | ||||||||||||||
Latest revision as of 03:13, 22 March 2024
Tools for Type S (Sign) and Type M (Magnitude) Errors
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | retrodesign |
Tools for Type S (Sign) and Type M (Magnitude) Errors |
Statements
2 November 2023
0 references
Provides tools for working with Type S (Sign) and Type M (Magnitude) errors, as proposed in Gelman and Tuerlinckx (2000) <doi:10.1007/s001800000040> and Gelman & Carlin (2014) <doi:10.1177/1745691614551642>. In addition to simply calculating the probability of Type S/M error, the package includes functions for calculating these errors across a variety of effect sizes for comparison, and recommended sample size given "tolerances" for Type S/M errors. To improve the speed of these calculations, closed forms solutions for the probability of a Type S/M error from Lu, Qiu, and Deng (2018) <doi:10.1111/bmsp.12132> are implemented. As of 1.0.0, this includes support only for simple research designs. See the package vignette for a fuller exposition on how Type S/M errors arise in research, and how to analyze them using the type of design analysis proposed in the above papers.
0 references
