summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPjotr Prins2024-09-13 17:00:13 +0200
committerPjotr Prins2024-09-13 17:00:19 +0200
commit1cbfd8995265251683078d5b911072321072519a (patch)
tree6d45eeda9be12b5e4ada883818f14d35eacd36c4
parent5d206e5a6acb612705395198d7e591fd5ae0fd07 (diff)
downloadgn-gemtext-1cbfd8995265251683078d5b911072321072519a.tar.gz
GEMMA permutations continued
-rw-r--r--topics/lmms/gemma/permutations.gmi3
1 files changed, 1 insertions, 2 deletions
diff --git a/topics/lmms/gemma/permutations.gmi b/topics/lmms/gemma/permutations.gmi
index e1beaea..5a5e356 100644
--- a/topics/lmms/gemma/permutations.gmi
+++ b/topics/lmms/gemma/permutations.gmi
@@ -442,8 +442,7 @@ and, of course, as this reduced file is generated it not available yet. That was
./bin/gemma-wrapper:230:in `block in <main>': Do not use the GEMMA -p switch with gemma-wrapper if you are using JSON phenotypes!
```
-Hmm. This is a bit harder. The call to GWAS takes a kinship matrix and it gets reduced with every permutation. That is probably OK because it runs quickly, but I'll need to remove the -p switch... TBC
-
+Hmm. This is a bit harder. The call to GWAS takes a kinship matrix and it gets reduced with every permutation. That is probably OK because it runs quickly, but I'll need to remove the -p switch... OK. Done that and permutations are running in a second for 28 BXD!
## Dealing with epoch