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 has been archived by the owner on Mar 12, 2022. It is now read-only.
Is your feature request related to a problem? Please describe.
The query script(s) require to specify a region in the chrN:XXX,YYY format, which forces the user to label chromosomes (or fragments) with the "chr" prefix, which can be useless in certain scenarios.
Describe the solution you'd like
Add a new script argument where the regular expression can be defined by the user.
The text was updated successfully, but these errors were encountered:
Or, even better, replace the input string to be parsed with three separate input arguments: feature, start and end. This would solve many issues due to parsing and remove the requirement for regexp knowledge from the user.
Implemented the following in v2.0.4 (soon to be released).
Both probe and probe set query scripts have two arguments instead of the previous region:
a mandatory "chrom" argument, which is not strictly a chromosome, but any feature in the database
a facultative "--region" argument that accepts a start-end string.
When the --region argument is not used, the whole feature is queried.
Also, note that when the --region argument is not used, the feature size is obtained by querying a DAS server. To use the size based on the database oligos use the --no-net option.
a facultative "--region" argument that accepts a start-end string.
to a facultative --region argument that accepts two space-separated int values: start and end respectively. If start and end coincide, the effect is the same as when --region is omitted.
Is your feature request related to a problem? Please describe.
The query script(s) require to specify a region in the chrN:XXX,YYY format, which forces the user to label chromosomes (or fragments) with the "chr" prefix, which can be useless in certain scenarios.
Describe the solution you'd like
Add a new script argument where the regular expression can be defined by the user.
The text was updated successfully, but these errors were encountered: