-
Notifications
You must be signed in to change notification settings - Fork 10
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
Improve maxatac prepare
#107
Comments
Hey, I gave maxatac prepare this input: `#!/bin/bash module load anaconda#module load anaconda (I don't remember the exact number but I think it is 3 you can check with module avail) conda activate your env#conda activate YOUR_CONDA_ENV_NAME # This env should have maxatac installed No need for the sh infront of maxatacmaxatac prepare `[2022-07-15 16:28:03,370] As elsewhere in samtools, use '-' as the filename for stdin/stdout. The input There seems to be a problem when preparing a bam file from snakeATAC. Note I am able to bypass the prepare step by using the bw generated. |
The
maxatac prepare
function was initially created as a convenience function for filtering, inferring Tn5 sites, and converting cut -site level coverage to min-max normalized bigwig tracks in one step. This function calls on the bash scripts that were used by our snakemake/cwl/bash workflows for ATAC-seq data processing. This will most likely be how most users prepare data as opposed to going through each step individually, so we should think about improving the user experience.maxatac prepare
to prepare scATAC-seq fragment files. He was able to run the script to completion and did not get an error message that:The problem is that it appears to the user that the run completes correctly, despite having encountered some error during running the shell script. We should add more logging information during processing. We should also look into whether we should use python to execute the shell commands as opposed to just running a shell script from python with the commands internally. We could also add code to the shell script to catch problems with execution.
We should also add a test for
maxatac
functions that will make sure pybigwig is installed and can find numpy correctly, before running through the entire workflow. This is related tomaxatac prepare
erroring out at normalization #96. We should point to the fix if the issue is detected.Double check that all of the unnecessary bedgraphs and intermediate files are removed to save space. We might want to add flags for whether to save specific intermediate files.
Update and add better logging messages for different processes running. At least add messages for major events like saving files or removing files. We could also have a final printout that has the names and locations of all files and their sizes.
The text was updated successfully, but these errors were encountered: