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.

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

Replace jupyter notebooks with scripts #16

Open
AshlinHarris opened this issue Nov 4, 2021 · 3 comments
Open

Replace jupyter notebooks with scripts #16

AshlinHarris opened this issue Nov 4, 2021 · 3 comments
Labels
breaking change ☠️ API change likely to affect existing code
Milestone

Comments

@AshlinHarris
Copy link
Contributor

Jupyter notebooks contain segmented python scripts with their outputs. Currently, they are used for many analysis steps for which simple scripts are better suited. Ideally, they should be reserved for plotting and quality control, and elsewhere replaced with scripts.

@AshlinHarris AshlinHarris added the breaking change ☠️ API change likely to affect existing code label Nov 4, 2021
@AshlinHarris AshlinHarris added this to the 2.0.0 milestone Nov 4, 2021
@AshlinHarris AshlinHarris self-assigned this Dec 1, 2021
@aydemiro
Copy link
Contributor

This is possible using the freebayes caller script instead of the jupyter route. We need to include it in the documentation. https://github.com/bailey-lab/MIPTools/blob/master/src/freebayes_caller.py

@arisp99
Copy link
Member

arisp99 commented Feb 18, 2022

A possible path forwards for this could be to take individual functions that are typically run from the jupyter notebook and package the functions into another container. For instance, we could make a new freebayes app that calls the freebayes caller script.

We could then generate apps for other commonly used functions like the vcf_to_tables function or the repool function.

@JeffAndBailey
Copy link
Member

Note. we want both options. Notebook and script based method. Not mutually exclusive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change ☠️ API change likely to affect existing code
Projects
None yet
Development

No branches or pull requests

4 participants