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

Update README to indicate 0.1.3 dcd-mapping release #75

Merged
merged 2 commits into from
Oct 29, 2024
Merged

Update README to indicate 0.1.3 dcd-mapping release #75

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b61aa5
Update README to indicate 0.1.3 dcd-mapping release
jarbesfeld Oct 25, 2024
661c742
Add URL to README
jarbesfeld Oct 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion notebooks/analysis/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Code for data analysis and figure generation for ["Mapping MAVE data for use in
* [`mapping_analysis.ipynb`](mapping_analysis.ipynb): This notebook computes reference sequence concordance across the generated VRS mapping pairs. The notebook also computes the number of unique pre-mapped and post-mapped variants.
* [`mavedb_scoreset_breakdown.ipynb`](mavedb_scoreset_breakdown.ipynb): This notebook generates the summary statistics that are described in the manuscript.

**Note that these notebooks may not be using the most recent release of the `dcd_mapping` library** -- they are intended to reflect the state of the code at the time of artifact generation, without any features that have been added since. The included `requirements.txt` file should produce an environment matching this expectation.
**Note that these notebooks are using the 0.1.3 release of the `dcd_mapping` library** -- they are intended to reflect the state of the code at the time of artifact generation, without any features that have been added since. The included `requirements.txt` file should produce an environment matching this expectation.
jarbesfeld marked this conversation as resolved.
Show resolved Hide resolved

## Environment

Expand Down