Hi, I am wondering if there is a way to output snarls with path size information. Currently, if I go the route of 'vg snarls', then 'vg deconstruct', the vcf file contains only the variant sequences, and I am forced to parse those out and calculate the string size for each one, which is not too efficient when you throw a whole pangenome at it. If this information is already available internally during snarl calling, is there a way to extract/output it?
Thanks!