Feature/plot#50
Open
marcelaxrivera wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi! The changes include the code to plot single cell lineages using the tree figure and plotting single cell properties over time. The code applies the Safe color map from plotly to set the color for each new lineage highlighted + Pycellin purple, in total 12 different lineages can be highlighted before color repetition. The properties over time plotted follow the same colored order of appearance as the single cell lineages when they don't overlap. When overlapping, the overlapped lineages take the same color together. Included some tests in test_lineage.py to test for example, that the start cell is in the same lineage as the target cell. I tested the code in the Getting started notebook, maybe this one can be skipped from the merge?