Skip to content

Boundary mismatch for ACMG scores #287

@leshaker

Description

@leshaker

Hello again,
while working with your code I just discovered that the boundaries for translating ACMG scores into classes seems to be inaccurate.

While the paper and your docs state

Image

the tcl code uses

		    if {$g_rankingScore($AnnotSV_ID) eq ""} {
			set class "NA"
		    } elseif {$g_rankingScore($AnnotSV_ID) >= "0.99"} {
			set class 5
		    } elseif {$g_rankingScore($AnnotSV_ID) >= "0.9"} {
			set class 4
		    } elseif {$g_rankingScore($AnnotSV_ID) >= "-0.9"} {
			set class 3
		    } elseif {$g_rankingScore($AnnotSV_ID) >= "-0.99"} {
			set class 2
		    } else {
			set class 1
		    }

} elseif {$g_rankingScore($AnnotSV_ID) >= "-0.9"} {

thus CNVs with score -0.90 are treated as VUS while they should be Likely Benign

Could you please double check if my observation is correct?

thanks!
Max

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions