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
I did some deep digging tonight to build a bar graph showing CTs per dataset that contribute to the AS shown in the fig. below. However, if you look at the provenance for the first dataset (https://portal.hubmapconsortium.org/browse/dataset/d6e6c8e452ed628425e9e928306a6db0#provenance), you will notice that the donor is male while the dataset is listed in the aggregated_summaries for the female, Azimuth annotation.
andreasbueckle
changed the title
Found instance of HuBMAP dataset in wrong as-cell-summary
🐛 Found instance of HuBMAP dataset in wrong as-cell-summary
Aug 13, 2024
@bherr2
The fig. below shows as-cell-summaries for two AS in the female heart, annotated with Azimuth:
The datasets contributing to these are here:
https://github.com/x-atlas-consortia/hra-pop/blob/main/output-data/v0.10.2/atlas-as-cell-summaries.jsonld#L11329-L11343
I did some deep digging tonight to build a bar graph showing CTs per dataset that contribute to the AS shown in the fig. below. However, if you look at the provenance for the first dataset (https://portal.hubmapconsortium.org/browse/dataset/d6e6c8e452ed628425e9e928306a6db0#provenance), you will notice that the donor is male while the dataset is listed in the
aggregated_summaries
for the female, Azimuth annotation.I only noticed this discrepancy, because I was getting cell summaries for the datasets in the
aggregated_summaries
from this report: https://github.com/x-atlas-consortia/hra-pop/blob/main/output-data/v0.10.2/reports/atlas-ad-hoc/datasets-ct-bm-data.csvBut I only saw male summaries for this particular dataset (https://entity.api.hubmapconsortium.org/ancestors/d6e6c8e452ed628425e9e928306a6db0).
My code to build the bar graphs is here: https://github.com/cns-iu/hra-construction-usage-supporting-information/blob/main/hra_pop/figure_1_g_hra_pop.ipynb
Can we investigate?
The text was updated successfully, but these errors were encountered: