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
and it would return results. (below output is from calling api/utilities/get_exon?chromosome=NC_000001.11&start=99999999999999999999999999999&gene=TPM3 from the fusion-builder api, which calls genomic_to_tx_segment directly.)
As a user, I might accidentally enter an incorrect coordinate that gets resolved to the nearest transcript junction and get some odd results that may be confusing. I would benefit from a message warning me that my entered data or the returned data could be unexpected.
Proposed solution
Add a warning when the coordinate occurs so many base pairs away from the start/end of a transcript
Alternatives considered
No response
Implementation details
When genomic_to_tx_segment is called with get_nearest_transcript_junction=True, return an error if the coordinates occur over 100 base pairs away from the transcript start / end
Potential Impact
No response
Additional context
Example of response from calling genomic_to_tx_segment with erroneous coordinates
you can see that the entered coordinate and corresponding offset will scale infinitely
Contribution
Yes, I can create a PR for this feature.
The text was updated successfully, but these errors were encountered:
katiestahl
changed the title
Add warning for when a coordinate occurs within a certain # of base pairs of the start/end of a transcript
Add warning for when a coordinate occurs within 100 base pairs of the start/end of a transcript
Sep 26, 2024
katiestahl
changed the title
Add warning for when a coordinate occurs within 100 base pairs of the start/end of a transcript
Add warning for when a coordinate occurs outside of 100 base pairs of the start/end of a transcript
Sep 26, 2024
Feature description
We should have a warning for when a coordinate occurs outside 100 base pairs of the start or end of a transcript.
Example:
a user could call
genomic_to_tx_segment
withand it would return results. (below output is from calling
api/utilities/get_exon?chromosome=NC_000001.11&start=99999999999999999999999999999&gene=TPM3
from the fusion-builder api, which callsgenomic_to_tx_segment
directly.)Use case
As a user, I might accidentally enter an incorrect coordinate that gets resolved to the nearest transcript junction and get some odd results that may be confusing. I would benefit from a message warning me that my entered data or the returned data could be unexpected.
Proposed solution
Add a warning when the coordinate occurs so many base pairs away from the start/end of a transcript
Alternatives considered
No response
Implementation details
When
genomic_to_tx_segment
is called withget_nearest_transcript_junction=True
, return an error if the coordinates occur over 100 base pairs away from the transcript start / endPotential Impact
No response
Additional context
Example of response from calling
genomic_to_tx_segment
with erroneous coordinatesyou can see that the entered coordinate and corresponding offset will scale infinitely
Contribution
Yes, I can create a PR for this feature.
The text was updated successfully, but these errors were encountered: