Jonathan Manning

Okay, I'll clarify, apologies for any misplaced assumptions in the following. All of fasta_txome, hisatw_index, bowtie_index etc just need the reference genome to exist, but can be run alongside one...

Don't worry about the 'each assembly' bit, I haven't got that far anyway. I only meant that I can run a reduce once I know I have all assets in...

Though of course if I can't run a single reduce alongside running maps that won't work either. That's the bottom line here: I understand that I can't run multiple reduce...

Ahh, I'd thought that each assembly needed a /fasta in place as a starting point (to establish the SHA digest), before any /fasta_txomes. Anyway, now things are clear I can...

> > But would it not be possible for the reduce process to actually check for completion of the mapped processes? > > It would be possible, I just wasn't...

That said, thanks for the quick work on getting things this far.

I can confirm that this works fine now. If we could get that release when you're ready so the new Conda package etc become available that'd help with our production.

That's really awesome- thank you.

I confirm that this works in our test case- thanks again.

Thanks @stolarczyk . I've just finished attempting to build all our assets. The issues I encountered seem mostly due assets not from Ensembl, namely: - Files not passing the post-processing...