User Tools

Site Tools


development:best_practices_estimation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
development:best_practices_estimation [2016/04/20 09:15]
schuemie
development:best_practices_estimation [2016/04/20 09:17]
schuemie
Line 13: Line 13:
  
  
-  * Make all analysis code available as open source ​+  * Make all analysis code available as **open source** 
  
-  * Validate all code used to produce estimates. Possible options are+  ​* **Validate** all code used to produce estimates. The purpose of validation is to ensure the code is doing what we require it to do. Possible options are:
     * Unit testing     * Unit testing
     * Simulation     * Simulation
Line 21: Line 21:
     * Code review     * Code review
  
-  * Include negative controls (exposure-outcome pairs where we believe there is no effect) ​+  * Include ​**negative controls** (exposure-outcome pairs where we believe there is no effect) ​
  
-  * Produce calibrated p-values+  * Produce ​**calibrated p-values**
  
  
Line 36: Line 36:
  
  
-  * Include a risk window just prior to start of exposure to detect time-varying confounding (e.g. contra-indications,​ protopathic bias)+  * Include a **risk window just prior to start of exposure** to detect time-varying confounding (e.g. contra-indications,​ protopathic bias)
development/best_practices_estimation.txt ยท Last modified: 2020/03/09 05:18 by schuemie