Map blueprint ontology to CL names #983
Merged
+327
−317
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose/implementation Section
Please link to the GitHub issue that this pull request addresses.
Closes #979
What is the goal of this pull request?
Here I am adding a column that maps the ontology ID in
BlueprintEncodeData
to the CL name found in the cell type ontology.Briefly describe the general approach you took to achieve this goal.
blueprint_annotation_cl
. This also means a huge diff for this file since it includes a new column.blueprint_annotation_fine
column altogether and just use theblueprint_annotation_cl
column.Author checklists
Check all those that apply.
Note that you may find it easier to check off these items after the pull request is actually filed.
Analysis module and review
README.md
has been updated to reflect code changes in this pull request.Reproducibility checklist
Dockerfile
.environment.yml
file.renv.lock
file.