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

Running sv-channels without training #78

Open
lsantuari opened this issue Nov 25, 2020 · 5 comments
Open

Running sv-channels without training #78

lsantuari opened this issue Nov 25, 2020 · 5 comments
Assignees
Milestone

Comments

@lsantuari
Copy link
Contributor

lsantuari commented Nov 25, 2020

  • rename run.sh as train.sh
  • create a new bash script call.sh:

input:

  • 5 pre-trained models, one for each SV type
  • the array windows.npz to run the models on for prediction/calling

The script

The snakemake way

  • 2 parallel workflows, one for the training and one for the calling:
  • the training workflow outputs the model(.hdf5)
  • the test sample output windows(.npz)
  • the calling is done by processing the windows of the test sample with the model trained on the training sample
@lsantuari lsantuari added the code label Nov 30, 2020
@lsantuari lsantuari added this to the 0.1.0 milestone Nov 30, 2020
@arnikz
Copy link
Contributor

arnikz commented Nov 30, 2020

* rename [run.sh](https://github.com/GooglingTheCancerGenome/sv-channels/blob/dev/run.sh) as _train.sh_

* create a new bash script _call.sh_:

Instead, these could be the two modes (param) of the same "workflow" (to-be) implemented in one script run.sh. Could you indicate it in this figure?

@arnikz
Copy link
Contributor

arnikz commented Nov 30, 2020

I've just noticed that this was added half-way

exit 0

which means that the final checks were not executed. For now, I've disabled the code related to training (923b9ce)

@arnikz arnikz closed this as completed Nov 30, 2020
@arnikz arnikz reopened this Nov 30, 2020
@arnikz
Copy link
Contributor

arnikz commented Nov 30, 2020

Ooops

lsantuari added a commit that referenced this issue Jan 20, 2021
@arnikz arnikz removed this from the 0.1.0 milestone Jan 21, 2021
@arnikz arnikz added this to the 0.1.0 milestone Jan 21, 2021
@lsantuari
Copy link
Contributor Author

Add a smoke test with the predict.py function here:


with the windows generated by run.sh

lsantuari added a commit that referenced this issue Jan 21, 2021
@arnikz
Copy link
Contributor

arnikz commented Jan 25, 2021

I don't know what you'd like to pass via CLI so added a place-holder here:

#p=predict.py

Please continue in dev-merge branch (7d0d18e).

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

No branches or pull requests

2 participants