elijahcole commited on
Commit
40bfd86
·
verified ·
1 Parent(s): d264d10

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +9 -1
README.md CHANGED
@@ -44,4 +44,12 @@ We discard all cells for a `cell+tissue` type if:
44
  For each donor, all cells were randomly assigned to exactly one split: train (70%), validation (15%), or test (15%).
45
 
46
  ### Mapping `development_stage` values to numeric ages
47
- Coming soon!
 
 
 
 
 
 
 
 
 
44
  For each donor, all cells were randomly assigned to exactly one split: train (70%), validation (15%), or test (15%).
45
 
46
  ### Mapping `development_stage` values to numeric ages
47
+
48
+ Age information in CELLxGENE is derived from the `development_stage` field.
49
+
50
+ * Some values of `development stage` give a precise age in years.
51
+ * Example: `80 year-old human`. In this case, we assign a numerical value of `80`.
52
+ * Other values of `development_stage` are broader.
53
+ * Example: `child_stage`. [It turns out](https://ontology.archive.data.humancellatlas.org/ontologies/hcao/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FHsapDv_0000081) that this is synonymous with the age range of 2-12 years. In this case, we assign a numerical value of `7`, corresponding to the midpoint of the range.
54
+
55
+ This means that some of our numerical age values are more precise than others. This is reflected in the `age_precision` variable, which gives the maximum error in the assigned value of `age`. For instance, for `child_stage` we have a value of `5` for `age_precision`, since the assigned age (`7`) could be 5 years too low (i.e. age `12`) or too high (i.e. age `2`).