If I recall correctly -- and I might not, as this popped up during the VEP 111 update -- this affects what position and length is assigned to SVLEN when two or more variants are merged, which for example messes with loqusdb artefact matching.
i.e. a frequent artefact might be mismatched with a less-frequent entry in loqusdb because the svlen/positions have been shuffled between the merged variants
Issue is in the title. Possible bug?
If I recall correctly -- and I might not, as this popped up during the VEP 111 update -- this affects what position and length is assigned to
SVLENwhen two or more variants are merged, which for example messes with loqusdb artefact matching.i.e. a frequent artefact might be mismatched with a less-frequent entry in loqusdb because the svlen/positions have been shuffled between the merged variants