Closed averydavisbell closed 3 years ago
Hi Avery! Thank you very much for your note. It was originally developed in py2 and I am currently porting it to py3. There may be some more hick-ups along this line. I am embarrassed as new conda decided not to support some older dependencies that EMASE had to use. The installation used to be one liner but now it is broken as you pointed out. I will get to it soon. Anyways I see you are performing allele-specific expression analysis. Please feel free to contact me at kb.choi@jax.org if you get any other issue running EMASE.
I am just getting started with alntools and ran into an issue with bam2ec that I was able to remedy by modifying one line of code; I thought I'd let you know in case this is an issue others might have! (I don't feel confident enough to try to contribute to the codebase.)
Call: Using Anaconda 2.1 (I couldn't get EMASE dependencies to resolve with newer versions of conda) on linux (high performance compute cluster), alntools environment created and loaded as specified in https://churchill-lab.github.io/alntools/ BAM was aligned with bowtie2; has ~3M reads
alntools bam2ec -t /storage/home/hcoda1/2/abell65/scratch/testdiptranscripts/firsttest/N2ws263_JU1088/emase.pooled.transcripts.info -c 1 --verbose AP01-88_alignedN2ws263_JU1088.bam AP01-88.bin
Output including error:
Fix: I simply modified line 828 of the bam_utils.py script to make the ec_ids a numpy array so that the line would work:
read_names=np.array(ec_ids).astype(str),
After this change, bam2ec completes: