-
Rename to `ga4gh-server` from `ga4gh-reference-implementation`
As discussed in #1585
-
From email chain:
```
As an initial test, we thought it would be good to have examples of the various forms genetic data comes in for us:
1) 1619_A02_Calls.vcf – an exome VCF, directly outp…
kozbo updated
7 years ago
-
The reference server currently converts VCF data into GA4GH variant objects. It would also be useful to convert in the other direction for many purposes (for example, providing a stream to programs th…
-
It's currently ga4gh-reference-implementation, we can change it to ga4gh-server and change our documentation.
-
To maintain consistency with other ga4gh repositories, perhaps we should rename this one to `ga4gh-server`?
https://help.github.com/articles/renaming-a-repository/
We also would need to:
- chan…
-
Edit the datamodel to parse out the messages for filters using the pysam record (to the greatest fidelity available).
Add the fields to the `toProtocolElement` message.
https://github.com/ga4gh/…
-
## Bug Report
### Affected tool(s)
ValidateSamFile and possibly other Picard tools with the same dependencies
### Affected version(s)
- [x] Latest public release version 2.9.2
### Descripti…
-
Now that we coordinate releases of packages to pypi, we need to provide documentation for performing a release. Notably, python packages are versioned separately from the protocol currently. Let's set…
-
The protocol functions for coercing to and from JSON would be nice to package with the schemas so that projects don't need to get protobuf themselves if they want to do serialization. @dcolligan
-
I think this:
```
from ga4gh.server.frontend import app as application
import ga4gh.server.frontend as frontend
frontend.configure("/srv/ga4gh/config.py")
```
should now be:
```
from ga4gh.fro…