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

Fix: Make it so that bamlist generation is re-run if sample order changes, keeping meta-data consistent #51

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

zjnolen
Copy link
Owner

@zjnolen zjnolen commented Sep 30, 2024

If sample order changed in the samples.tsv after a completed run, and a new run was made, poplists would be re-generated, but not bamlists, which would cause samples info to line up with the wrong samples in the beagle files. Now, the bamlist will also be generated. This is not the most efficient way to handle this, as it will trigger many re-runs, but it seems a safe way without changing how GL files are made in the workflow. This should only trigger when samples are being changed anyway, so re-runs are mostly going to be desired anyway.

Closes #48.

This will force a rerun of the rule. I am not quite sure why it wouldn't before. The code should change if input order changes, but maybe Snakemake doesn't look inside input list expansions when determining code changes?
@zjnolen zjnolen merged commit cd6e2ff into develop Sep 30, 2024
4 checks passed
@zjnolen zjnolen deleted the fix-bamlist-order branch September 30, 2024 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant