-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New user "un-boxing" experience #272
Labels
Comments
Make docs more visible, such as https://github.com/ga4gh/vrs-python/blob/main/docs/extras/vcf_annotator.md |
Per the last call, @katiestahl and I will be taking a crack at this in the medium-term |
jsstevenson
added
documentation
Changes to documentation only
priority:medium
Medium priority
labels
Oct 12, 2023
This issue was marked stale due to inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Use case: install vrs-python, run vcf_annotation
It would be useful to have a command line oriented "quick start":
--seqrepo_dp_type
--seqrepo_base_url
. I was stumped by this until I read through python notebooks to find values.It would be useful to have a command line oriented "production ready":
/usr/local/share/seqrepo
by default. This may not be possible in environments where user lacks privileges. Perhaps feature--seqrepo_root_dir
more prominently in documentation?Usage:
--vrs_pickle_out
I might be missing something obvious, but I needed to do an eval() in order to use the results.Application
Once vrs identifiers are calculated, the question is
What can I do with them?
. It would be useful if there was a known endpoint using the same schema versions. See attached notebook example.The text was updated successfully, but these errors were encountered: