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
Hi,
I'm running SURVIVOR v1.0.7 and. I've noticed that the number of SVs events generated by SURVIVOR simSV (in both the .bed and .vcf files) does not correspond to the .parmams file and differs depending on the value of option 3 (0 or 1).
Here's what I see:
$ SURVIVOR simSV test.param
Output:
PARAMETER FILE: DO JUST MODIFY THE VALUES AND KEEP THE SPACES!
DUPLICATION_minimum_length: 100
DUPLICATION_maximum_length: 10000
DUPLICATION_number: 3
INDEL_minimum_length: 20
INDEL_maximum_length: 500
INDEL_number: 1
TRANSLOCATION_minimum_length: 1000
TRANSLOCATION_maximum_length: 3000
TRANSLOCATION_number: 2
INVERSION_minimum_length: 600
INVERSION_maximum_length: 800
INVERSION_number: 4
INV_del_minimum_length: 600
INV_del_maximum_length: 800
INV_del_number: 2
INV_dup_minimum_length: 600
INV_dup_maximum_length: 800
INV_dup_number: 2
Then using SURVIVOR simSV to generate SVs:
Using option 3 = 1, I see the correct number of everything, other than zero DUP (I presume for inversions, INV_del_number + INV_dup_number = INVERSION_number). Also, the DUP value is always zero in the true positives and false negatives section of SURVIVOR eval.
Using option 3 = 0, I see the following (ordered by SV-type for ease):
5 Duplication events, not 3
5 INDELS (1 INS and 4 DEL), not 1
8 INVERSIONS, not 4
Can you comment on this? I've never really understood why SURVIVOR generates different data depending on what the downstream use of it will be (SVs in reference, or SVs in reads). But what is obvious here is that it appears to be generating a different number of SVs than requested in the params file.
Cheers,
Graham
The text was updated successfully, but these errors were encountered:
Hi,
I'm running SURVIVOR v1.0.7 and. I've noticed that the number of SVs events generated by
SURVIVOR simSV
(in both the .bed and .vcf files) does not correspond to the .parmams file and differs depending on the value of option 3 (0 or 1).Here's what I see:
$ SURVIVOR simSV test.param
Output:
Then using
SURVIVOR simSV
to generate SVs:Using option 3 = 1, I see the correct number of everything, other than zero DUP (I presume for inversions,
INV_del_number
+INV_dup_number
=INVERSION_number
). Also, the DUP value is always zero in the true positives and false negatives section ofSURVIVOR eval
.Using option 3 = 0, I see the following (ordered by SV-type for ease):
5 Duplication events, not 3
5 INDELS (1 INS and 4 DEL), not 1
8 INVERSIONS, not 4
Can you comment on this? I've never really understood why SURVIVOR generates different data depending on what the downstream use of it will be (SVs in reference, or SVs in reads). But what is obvious here is that it appears to be generating a different number of SVs than requested in the params file.
Cheers,
Graham
The text was updated successfully, but these errors were encountered: