binsanity-checkm directory created in current working directory

[donova...@gmail.com]

Hello,

I'm using BinSanity v0.2.5.9 and have encountered a small issue. When running the program it creates the directory 'binsanity-checkm' in the current working directory. As a consequence, if another instance o f BinSanity is run in the same directory it will fail as this directory will already exist. Would it be possible to give this directory a unique/temporary name in order to avoid this conflict? I often run binning methods in parallel over multiple independent samples so this situation is problematic.

I also posted this as a GitHub issue, before running across this group. Sorry for the cross post.

Thanks,
Donovan

[egrah...@gmail.com]

Hi Donovan,

That is definitely an issue I hadn't considered, but should be easily fixable. I'll play around with the most efficient way to do this and let you know as soon as it's updated.

If there are any more user issues like this you've noticed that could be improved upon I'm happy to look in to trying to make the outputs more friendly!

Regards,

Elaina

--
You received this message because you are subscribed to the Google Groups "BinSanity" group.
To unsubscribe from this group and stop receiving emails from it, send an email to binsanity+...@googlegroups.com.
To post to this group, send email to bins...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/binsanity/75e90143-ef27-4d61-889f-4822665290c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Elaina Graham]

Hi Donovan, 

I updated Binsanity-wf and Binsanity-lc with a new flag to make running things in paralell in the same directory possible. There is now a `--Prefix` flag that can be invoked and whatever prefix you specify will be appended to the all of the directories, logfiles, etc. that BinSanity produces throughout. 

Regards,

Elaina

On Sun, Jul 23, 2017 at 10:57 AM, <egrah...@gmail.com> wrote:

Hi Donovan,

That is definitely an issue I hadn't considered, but should be easily fixable. I'll play around with the most efficient way to do this and let you know as soon as it's updated.

If there are any more user issues like this you've noticed that could be improved upon I'm happy to look in to trying to make the outputs more friendly!

Regards,

Elaina

On Jul 23, 2017, at 9:13 AM, donova...@gmail.com wrote:

Hello,

I'm using BinSanity v0.2.5.9 and have encountered a small issue. When running the program it creates the directory 'binsanity-checkm' in the current working directory. As a consequence, if another instance o f BinSanity is run in the same directory it will fail as this directory will already exist. Would it be possible to give this directory a unique/temporary name in order to avoid this conflict? I often run binning methods in parallel over multiple independent samples so this situation is problematic.

I also posted this as a GitHub issue, before running across this group. Sorry for the cross post.

Thanks,
Donovan

--
You received this message because you are subscribed to the Google Groups "BinSanity" group.

To unsubscribe from this group and stop receiving emails from it, send an email to binsanity+unsubscribe@googlegroups.com.