Search
Question: CollapsedVCF and ExpandedVCF rownames and vcfs with large ref/alt columns
0
18 months ago by
Sean Davis21k
United States
Sean Davis21k wrote:

With some newer VCF files, particularly those that have come from structural variant callers, the rownames of the resulting VCF objects (when the ID column is missing) can become problematic or excessively large. To give a concrete example, we have VCFs with insertions of dozens or hundreds of bases that lead to very long rownames. While human-readable rownames are useful in some cases, would it be possible to maintain uniqueness while enforcing some further constraints on the constructed rownames to keep them manageably short and printable?

modified 18 months ago by Valerie Obenchain ♦♦ 6.5k • written 18 months ago by Sean Davis21k
1

Or perhaps also have an option to drop rownames altogether...

2
18 months ago by
Valerie Obenchain ♦♦ 6.5k
United States
Valerie Obenchain ♦♦ 6.5k wrote:

Yes, I can imagine that's the case. The pasting of CHROM:POS_REF/ALT was a reasonable solution when ALT was just a few bases. I'm open to other suggestions of how to handle this - what information would you like to see as the row names?

We do have the option to turn off rownames with readVcf(..., row.names=FALSE).

Val