update to v2.0.2

[sorelfitzgibbon]

Checklist

Formatting

• I have read the code review guidelines and the code review best practice on GitHub check-list.

• The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)-[brief_description_of_branch].

• I have set up or verified the branch protection rule following the github standards before opening this pull request.

File Updates

• I have ensured that the version number update follows the versioning standards.

• I have updated the version number/dependencies and added my name to the maintainer list in the Dockerfile.

• I have updated the version number/feature changes in the README.md.

• I have updated the version number and added my name to the contributors list in the metadata.yaml.

• I have added the changes included in this pull request to the CHANGELOG.md under the next release version or unreleased, and updated the date.

• I have drafted the new version release with any additions/changes and have linked the CHANGELOG.md in the release.

Docker Hub Auto Build Rules

• I have created automated build rules following this page and I have not manually pushed this Docker image to the blcdsdockerregistry on Docker Hub.

Docker Image Testing

• I have tested the Docker image with the docker run command as described below.

My command:

/hot/user/sfitzgibbon/git/docker-MuSE/runTestMuse.sh

Description

Closes #8

Updated to MuSE v2.0.2

[sorelfitzgibbon]

Should I test this on the large input BAMs before making the release, or should I test it within call-sSNV after updating to this release?

[yashpatel6]

One suggestion about the version encoding in the Dockerfile:

[yashpatel6]

Code looks good to me! I'll leave it for Mao's final review

[maotian06]

Looks good to me too!

[tyamaguchi-ucla]

I have a few things to add.

L26 - associate this repo with the GitHub package and update the label.

https://github.com/uclahs-cds/template-docker/blob/736215a19cc5e87a29121f4f4b9abbfb956da852/Dockerfile#L25

Also, not for this PR, it would be nice to update the PR template to use github packages instead of dockerhub. Lastly, consider using /hot/software/image for the standardized dev/release structure.