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

Add tests to ensure API can recreate source BAM/SAM/CRAM/VCF #123

Open
diekhans opened this issue Nov 2, 2015 · 4 comments
Open

Add tests to ensure API can recreate source BAM/SAM/CRAM/VCF #123

diekhans opened this issue Nov 2, 2015 · 4 comments

Comments

@diekhans
Copy link
Contributor

diekhans commented Nov 2, 2015

This appears not to be the case:
ga4gh/ga4gh-server#758

@diekhans diekhans changed the title Add tests to ensure API can recreate source BAM/SAM/CRAM/VF Add tests to ensure API can recreate source BAM/SAM/CRAM/VCF Nov 2, 2015
@macieksmuga
Copy link
Contributor

Not sure this is a compliance suite issue, but rather an issue with the API proper (as defined in the schemas repo), as per the above-mentioned discussion in the server repo.

@diekhans
Copy link
Contributor Author

This is an compliance suite issue, in the sense that we should
test that be can to get back the data you put in. However is
current impossible to code this test.

There are a number of subtle issues that need to be understood
and addressed, such a `placed' reads. The compliance suite can
be one force in resolving these issues.

Maciek Smuga-Otto [email protected] writes:

Not sure this issue is a compliance suite issue, but rather an issue with the
API proper (as defined in the schemas repo), as per the above-mentioned
discussion in the server repo.


Reply to this email directly or view it on GitHub.*

@david4096
Copy link
Member

Is there somewhere I can read more about this?

@diekhans
Copy link
Contributor Author

ga4gh/ga4gh-schemas#505

Although it might be necessary to define exactly what `round
trip' means which certain types of data.

David Steinberg [email protected] writes:

Is there somewhere I can read more about this?


Reply to this email directly or view it on GitHub.*

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants