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
Currently, steps/tools define their own reference naming conventions.
This can lead to incompatibilities between steps, accidentally selecting incorrect references etc.
Unifying the way references are handled could help prevent that.
However, tools sometimes rely on specific aliases. Therefore, we could add support for aliases, something along the lines of:
In principle, we could also directly specify the source and release directly, such that the reference sequence can be downloaded (and cached) automatically, e.g. for ensembl:
Currently, steps/tools define their own reference naming conventions.
This can lead to incompatibilities between steps, accidentally selecting incorrect references etc.
Unifying the way references are handled could help prevent that.
However, tools sometimes rely on specific aliases. Therefore, we could add support for aliases, something along the lines of:
In principle, we could also directly specify the source and release directly, such that the reference sequence can be downloaded (and cached) automatically, e.g. for ensembl:
or local:
The text was updated successfully, but these errors were encountered: