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
{{ message }}
This repository was archived by the owner on Apr 20, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 20, 2026. It is now read-only.
Mask not computed correctly. Possible off-by-1 error? #152
broadinstitute/SpliceAI-lookup#59
has several examples of apparently inconsistent masking. For example, for 1-237727120-T-C
the mask only affects the Acceptor Gain score, but should arguably be applied to both the Acceptor Gain and Donor Gain:
This is unfortunately caused because of the fact that the mask implementation is a super-hacky one and not precise. We only look for the closest exon boundary
This worked most of the time when the distance parameter is less (like the default 50) as you are unlikely to see two ends of an exon within such a short distance, but completely falls apart when the distances are large. I would recommend ignoring the mask property for larger distances for the time-being.
Activity
kishorejaganathan commentedon Nov 21, 2024
This is unfortunately caused because of the fact that the mask implementation is a super-hacky one and not precise. We only look for the closest exon boundary
SpliceAI/spliceai/utils.py
Line 62 in f364513
SpliceAI/spliceai/utils.py
Lines 185 to 188 in f364513