OSTIR performs predictions for different start codons within each input sequence in parallel (using --threads). This works well when the input is one or a few long sequences. However, it currently is not set up to multithread execution over multiple different input sequences. This functionality would be helpful for speeding up certain workflows. One example is that for performing RBS design (see #1), one might want to test many mutated versions of the sequence around a start codon at the same time.
Probably the best way to implement multithreading across multiple sequences would be to allow run_oster() and OSTIRFactory() to accept a list of sequences so they can set things up in the same process queue that is already being used for multithreading.
OSTIR performs predictions for different start codons within each input sequence in parallel (using
--threads). This works well when the input is one or a few long sequences. However, it currently is not set up to multithread execution over multiple different input sequences. This functionality would be helpful for speeding up certain workflows. One example is that for performing RBS design (see #1), one might want to test many mutated versions of the sequence around a start codon at the same time.Probably the best way to implement multithreading across multiple sequences would be to allow
run_oster()andOSTIRFactory()to accept a list of sequences so they can set things up in the same process queue that is already being used for multithreading.