summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorFrederick Muriuki Muriithi2024-09-19 10:36:06 -0500
committerFrederick Muriuki Muriithi2024-09-19 10:36:06 -0500
commit261da8756dc1176114bd844a0d17d3a8a77fcaec (patch)
treeb4d44e593892f0b00badcc3ca243221be292a055 /issues
parent8af89c03833d02b7025427072a3de9d293a1c50b (diff)
downloadgn-gemtext-261da8756dc1176114bd844a0d17d3a8a77fcaec.tar.gz
Update issue.
Diffstat (limited to 'issues')
-rw-r--r--issues/gn-uploader/uploading-samples.gmi9
1 files changed, 9 insertions, 0 deletions
diff --git a/issues/gn-uploader/uploading-samples.gmi b/issues/gn-uploader/uploading-samples.gmi
index 237843d..11842b9 100644
--- a/issues/gn-uploader/uploading-samples.gmi
+++ b/issues/gn-uploader/uploading-samples.gmi
@@ -29,6 +29,15 @@ This is really goofy and should probably change. I've brought up the idea of jus
We need to explore whether such a change might need updates to the GN2/GN3 code to ensure code that depends on these dummy files can also use the new format JSON files too.
+Regarding the order of the samples, from the email thread:
+
+```
+Regarding the order of samples, it can basically be whatever we decide it is. It just needs to stay consistent (like if there are multiple genotype files). It only really affects how it's displayed, and any other genotype files we use for mapping needs to share the same order.
+```
+
+The ordering of the samples has no bearing on the analysis of the data, i.e. it does not affect the results of computations.
+
+
### Curation
```