You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
buildTaxonomy() is able to take in the existing dendrogram associated with the taxonomy, but buildPatchseqTaxonomy() doesn’t have this feature. It would be helpful to add a feature in buildPatchseqTaxonomy() to take in an existing patcheq dendrogram as well.
In the previous code that used the tree-mapping method for the mouse VISp taxonomy, a consolidated/collapsed dendrogram (where a branch could have more than two children) was used, which at the time improved mapping performance. For consistency with the past work, it would be good to be able to use the same dendrogram for that kind of mapping.
We could also have checks to ensure that the collapsed dendrogram given as input has a structure consistent with the original dendrogram and that it includes all the expected types.
The text was updated successfully, but these errors were encountered:
buildTaxonomy() is able to take in the existing dendrogram associated with the taxonomy, but buildPatchseqTaxonomy() doesn’t have this feature. It would be helpful to add a feature in buildPatchseqTaxonomy() to take in an existing patcheq dendrogram as well.
In the previous code that used the tree-mapping method for the mouse VISp taxonomy, a consolidated/collapsed dendrogram (where a branch could have more than two children) was used, which at the time improved mapping performance. For consistency with the past work, it would be good to be able to use the same dendrogram for that kind of mapping.
We could also have checks to ensure that the collapsed dendrogram given as input has a structure consistent with the original dendrogram and that it includes all the expected types.
The text was updated successfully, but these errors were encountered: