Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

mentioning range matches for start + end #292

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions beacon.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ paths:
- typical use are queries for SNV and small InDels
- the use of "start" without an "end" parameter requires the use of "referenceBases"
* start and end:
- special use case for exactly determined structural changes
- special use case for exactly determined structural changes or range matches
in: query
required: false
schema:
Expand All @@ -55,7 +55,7 @@ paths:
description: |
Minimum start coordinate
* startMin + startMax + endMin + endMax
- for querying imprecise positions (e.g. identifying all structural variants starting anywhere between startMin <-> startMax, and ending anywhere between endMin <-> endMax)
- for querying imprecise positions (e.g. identifying all specified SNVs or structural variants starting anywhere between startMin <-> startMax, and ending anywhere between endMin <-> endMax)
- single or double sided precise matches can be achieved by setting startMin = startMax XOR endMin = endMax
in: query
schema:
Expand Down Expand Up @@ -367,7 +367,7 @@ components:
- typical use are queries for SNV and small InDels
- the use of "start" without an "end" parameter requires the use of "referenceBases"
* start and end:
- special use case for exactly determined structural changes
- special use case for exactly determined structural changes or range matches
type: integer
format: int64
minimum: 0
Expand All @@ -378,7 +378,7 @@ components:
description: |
Minimum start coordinate
* startMin + startMax + endMin + endMax
- for querying imprecise positions (e.g. identifying all structural variants starting anywhere between startMin <-> startMax, and ending anywhere between endMin <-> endMax)
- for querying imprecise positions (e.g. identifying all specified SNVs or structural variants starting anywhere between startMin <-> startMax, and ending anywhere between endMin <-> endMax)
- single or double sided precise matches can be achieved by setting startMin = startMax XOR endMin = endMax
type: integer
startMax:
Expand Down