69 | | {{{ |
70 | | title: Comparison of imputation methods Beagle, Impute and MACH |
71 | | |
72 | | component: gwas |
73 | | |
74 | | description: |
75 | | |
76 | | Why or for whom? |
77 | | For medgen and bbmri we want to compare imputation methods Beagle, Impute and MACH. |
78 | | |
79 | | Expected output? |
80 | | An Excel document that describes a comparable percentage correctly estimated SNPs. |
81 | | |
82 | | Action plan? |
83 | | Take existing genotype data from 1M arrays and split the data randomly in two. The first half we input into the impute methods. Then we compare the SNPs called with those actually called on the array and calculate percentage correctly estimated SNPs. |
84 | | |
85 | | Evaluation plan? |
86 | | We will feed back results to Lude and Cisca's teams to evaluate outcomes and if necessary propose further testing. |
| 69 | ||title: ||Comparison of imputation methods Beagle, Impute and MACH || |
| 70 | ||component: ||gwas || |
| 71 | ||description: ||Why or for whom?[[BR]]For medgen and bbmri we want to compare imputation methods Beagle, Impute and MACH.[[BR]][[BR]]Expected output?[[BR]]An Excel document that describes a comparable percentage correctly estimated SNPs.[[BR]][[BR]]Action plan?[[BR]]Take existing genotype data from 1M arrays and split the data randomly in two. The first half we input into the impute methods. Then we compare the SNPs called with those actually called on the array and calculate percentage correctly estimated SNPs.[[BR]][[BR]]Evaluation plan?[[BR]]We will feed back results to Lude and Cisca's teams to evaluate outcomes and if necessary propose further testing. || |
119 | | {{{ |
120 | | title: Fix JPA if primary key is not named 'id' |
121 | | |
122 | | component: molgenis |
123 | | |
124 | | description: |
125 | | |
126 | | Why or for whom? |
127 | | This ticket is a showstopper for ticket xyz. |
128 | | |
129 | | Expected output? |
130 | | 1. checkout molgenis and molgenis_test |
131 | | 2. add a new <entity> with a <field name="myid" type="autoid"/> |
132 | | 2. generate code |
133 | | 3. run build.xml without errors |
134 | | |
135 | | Action plan? |
136 | | Correct generators to get rid of compile errors. |
137 | | |
138 | | Evaluation method? |
139 | | UnitTest. If it is a user interface error you have to describe the procedure here. |
| 98 | ||title: ||Fix JPA if primary key is not named 'id' || |
| 99 | ||component: ||molgenis || |
| 100 | ||description: ||Why or for whom?[[BR]]This ticket is a showstopper for ticket xyz.[[BR]][[BR]]Expected output?[[BR]]1. checkout molgenis and molgenis_test[[BR]]2. add a new <entity> with a <field name="myid" type="autoid"/>[[BR]]2. generate code[[BR]]3. run build.xml without errors[[BR]][[BR]]Action plan?[[BR]]Correct generators to get rid of compile errors.[[BR]][[BR]]Evaluation method? UnitTest. If it is a user interface error you have to describe the procedure here. || |
153 | | title: Java REST client doesn't work |
154 | | |
155 | | component: molgenis |
156 | | |
157 | | description: |
158 | | Why or for whom? |
159 | | We got a report stating that the REST api doesn't work from Java client |
160 | | |
161 | | Expected output? |
162 | | Have a test case that uses the REST api and succeeded/fails |
163 | | |
164 | | Action plan? |
165 | | Create a small REST client |
166 | | |
167 | | Evaluation method? |
168 | | Feed back to the bug reporter what we found and what actions we will take. |
| 114 | ||title: ||Java REST client doesn't work || |
| 115 | ||component: ||molgenis || |
| 116 | ||description: ||Why or for whom?[[BR]]We got a report stating that the REST api doesn't work from Java client[[BR]][[BR]]Expected output?[[BR]]Have a test case that uses the REST api and succeeded/fails[[BR]][[BR]]Action plan?[[BR]] |
| 117 | Create a small REST client[[BR]][[BR]]Evaluation method?[[BR]]Feed back to the bug reporter what we found and what actions we will take.|| |