Open ctb opened 5 years ago
Hmm - my guess is that dammit is attempting to use a file generated with the previous assembly, and then getting an error when it runs into mismatched transcript names.
This means we need to change the way dammit is called (perhaps specify more targets) so that it properly reruns. Will look into it.
if I remove the assembly, and then
run_eelpond trinity default
, the dammit step fails. output below.I can get it to work properly by removing the annotation directory. I suspect that there is a stale indexed file or another dammit intermediate file in there. not sure if this is a dammit but or an eelpond bug - seems like a dammit bug?