Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Convert fragment dataset to alignment dataset directly #2162

Merged
merged 1 commit into from
May 27, 2019
Merged

Convert fragment dataset to alignment dataset directly #2162

merged 1 commit into from
May 27, 2019

Conversation

heuermh
Copy link
Member

@heuermh heuermh commented May 26, 2019

No description provided.

@heuermh heuermh added this to the 0.28.0 milestone May 26, 2019
@heuermh heuermh mentioned this pull request May 26, 2019
Closed
@heuermh heuermh changed the title Convert fragment dataset to alignment dataset directly. Convert fragment dataset to alignment dataset directly May 26, 2019
@coveralls
Copy link

Coverage Status

Coverage remained the same at ?% when pulling 04c01f4 on heuermh:convert-fragment-dataset into 38f916f on bigdatagenomics:master.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/3008/
Test PASSed.

@heuermh
Copy link
Member Author

heuermh commented May 27, 2019

Thank you @henrydavidge for the original contribution!

@heuermh heuermh closed this May 27, 2019
@heuermh heuermh reopened this May 27, 2019
@heuermh heuermh merged commit f947c52 into bigdatagenomics:master May 27, 2019
@heuermh heuermh deleted the convert-fragment-dataset branch May 27, 2019 03:36
@heuermh heuermh mentioned this pull request May 31, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.28.0
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@heuermh @coveralls @AmplabJenkins