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
When you look at a dataset derived from VCF in a notebook, you get this:
The attributes are automatically "open",and this means that the VCF header attibute (which will be several megabytes for large datasets) dominates.
I'm not sure this is something we can influence, but can we either truncate the vcf header attribute for display, or tweak the display of the dataset somehow to at least keep the attributes "closed" by default?
The text was updated successfully, but these errors were encountered:
Alternatively we could discard the "#CHROM ..." line of the VCF header, since we can reproduce it using the sample_id variable. Also, it's wrong when we do a subset operation.
As a quick aside @tomwhite, do we ever use the "#CHROM POS.." line from the vcf header? If not I think we should discard it, as there's no real information there (i'll open an issue)
When you look at a dataset derived from VCF in a notebook, you get this:
The attributes are automatically "open",and this means that the VCF header attibute (which will be several megabytes for large datasets) dominates.
I'm not sure this is something we can influence, but can we either truncate the vcf header attribute for display, or tweak the display of the dataset somehow to at least keep the attributes "closed" by default?
The text was updated successfully, but these errors were encountered: