You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Nicholas,
I have received a complaint from our sysadmins because my jobs were using double the number of CPUs for bowtie. Looking at the bowtie_wrap.sh scripts I see that you set bwt_cpu=$(( $N_CPU / 2 )) but then that variable is not used and instead still uses
cmd="${BOWTIE2_PATH}/bowtie2 ${BOWTIE2_GLOBAL_OPTIONS} --rg-id BMG --rg SM:${prefix} -p ${N_CPU} -x ${BOWTIE2_IDX} -U ${infile} 2>> ${ldir}/${prefix}_bowtie2.log"
This seems to result in calling bowtie with the full number of CPUs
Can you confirm this?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi Nicholas,
I have received a complaint from our sysadmins because my jobs were using double the number of CPUs for bowtie. Looking at the bowtie_wrap.sh scripts I see that you set bwt_cpu=$(( $N_CPU / 2 )) but then that variable is not used and instead still uses
cmd="${BOWTIE2_PATH}/bowtie2 ${BOWTIE2_GLOBAL_OPTIONS} --rg-id BMG --rg SM:${prefix} -p ${N_CPU} -x ${BOWTIE2_IDX} -U ${infile} 2>> ${ldir}/${prefix}_bowtie2.log"
This seems to result in calling bowtie with the full number of CPUs
Can you confirm this?
Thanks!
The text was updated successfully, but these errors were encountered: