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

Incorrect handling of hdf5 file for repeated runs of RiboCode #59

Open
jdcla opened this issue Dec 4, 2023 · 0 comments
Open

Incorrect handling of hdf5 file for repeated runs of RiboCode #59

jdcla opened this issue Dec 4, 2023 · 0 comments

Comments

@jdcla
Copy link

jdcla commented Dec 4, 2023

Ribocode does not correctly handle the hdf5 file it creates to store temperary data, resulting in identical results for multiple runs that are ran from the same folder.

For example, running this script resulted in all identical ORF libraries for each of the datasets.

while IFS= read -r folder; do
    echo "$folder"
    mkdir "$folder/GRCh38_110/ribocode/"
    RiboCode_onestep -g "$assembly/Homo_sapiens.GRCh38.110.gtf" \
                     -f "$assembly/Homo_sapiens.GRCh38.dna.primary_assembly.fa" \
                     -r "${folder}/GRCh38_110/aligned_tran.bam" \
                     -l no \
                     -o "${folder}/GRCh38_110/ribocode/ribo" \
                     -f0_percent 0.5
done < "$1"

I solved this by removing the hdf5 file created after each run

while IFS= read -r folder; do
    echo "$folder"
    mkdir "$folder/GRCh38_110/ribocode/"
    rm aligned_tran_psites.hd5                                               <-- remove file
    RiboCode_onestep -g "$assembly/Homo_sapiens.GRCh38.110.gtf" \
                     -f "$assembly/Homo_sapiens.GRCh38.dna.primary_assembly.fa" \
                     -r "${folder}/GRCh38_110/aligned_tran.bam" \
                     -l no \
                     -o "${folder}/GRCh38_110/ribocode/ribo" \
                     -f0_percent 0.5
done < "$1"
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

No branches or pull requests

1 participant