On Nov 5, 2012, at 2:15 PM, Carlos Borroto wrote:
> On Fri, Nov 2, 2012 at 6:03 PM, Oleksandr Moskalenko wrote:
>> Here is the blastn rule procedure code and the relevant snippet of the
>> default runner procedure. I just added the database based multiplier, so
>> this part is very simple at
On Fri, Nov 2, 2012 at 6:03 PM, Oleksandr Moskalenko wrote:
> Here is the blastn rule procedure code and the relevant snippet of the
> default runner procedure. I just added the database based multiplier, so this
> part is very simple at the moment. I just set a bogus multiplier of "4" for
> th
On Nov 2, 2012, at 3:58 PM, Carlos Borroto wrote:
>
> Please, could you share your rules related to blast. I would love to
> take a look at them.
>
> Thanks,
> Carlos
Here is the blastn rule procedure code and the relevant snippet of the default
runner procedure. I just added the database ba
On Nov 2, 2012, at 4:42 PM, Carlos Borroto wrote:
> On Fri, Nov 2, 2012 at 3:58 PM, Carlos Borroto
> wrote:
>> On Fri, Nov 2, 2012 at 9:53 AM, Oleksandr Moskalenko
>> wrote:
>>>
>>> The dynamic runner is alive and well thanks to the continuous work of the
>>> author John Chilton and others
On Fri, Nov 2, 2012 at 3:58 PM, Carlos Borroto wrote:
> On Fri, Nov 2, 2012 at 9:53 AM, Oleksandr Moskalenko wrote:
>>
>> The dynamic runner is alive and well thanks to the continuous work of the
>> author John Chilton and others. For instance, yesterday John committed code
>> to galaxy-central
Hi Alex,
On Fri, Nov 2, 2012 at 9:53 AM, Oleksandr Moskalenko wrote:
>
> The dynamic runner is alive and well thanks to the continuous work of the
> author John Chilton and others. For instance, yesterday John committed code
> to galaxy-central that propagates tracebacks from the dynamic job ru
On Nov 1, 2012, at 4:22 PM, Carlos Borroto wrote:
> Hi,
>
> I've been researching the possibility of using dynamic job runner in
> combination with job splitting for blast jobs. My main interest is to
> create a rule where both the size of the query and the database are
> taken into considerati
Hi,
I've been researching the possibility of using dynamic job runner in
combination with job splitting for blast jobs. My main interest is to
create a rule where both the size of the query and the database are
taken into consideration in order to select DRMAA and splitting
options.
My first ques