<div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">I think this is a case of passing the output file path in scripts where -in path can be different from -out path (such as in normalize-by-median).</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">--<br><div><font face="garamond, serif">Ram</font></div></div></div>
<br><div class="gmail_quote">On Thu, Sep 25, 2014 at 12:06 PM, C. Titus Brown <span dir="ltr"><<a href="mailto:ctb@msu.edu" target="_blank">ctb@msu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, Sep 25, 2014 at 10:58:46AM -0500, Adina Chuang Howe wrote:<br>
> Hi team,<br>
><br>
> I was running diginorm today on two different disks (one for the<br>
> intermediate normalized files) and one on another disk (containing the raw<br>
> sequences) . I think this will be fairly typical in the future.<br>
> Currently, a test (file.py check_space) will error out, given this setup.<br>
> I think it'd be nice to be able to bypass this check or at least make it<br>
> more robust (to checking the write-out disk only).<br>
><br>
> Low priority, but notable, hopefully helpful.<br>
<br>
</div></div>Agreed -- see<br>
<br>
<a href="https://github.com/ged-lab/khmer/issues/399" target="_blank">https://github.com/ged-lab/khmer/issues/399</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--titus<br>
--<br>
C. Titus Brown, <a href="mailto:ctb@msu.edu">ctb@msu.edu</a><br>
<br>
_______________________________________________<br>
khmer mailing list<br>
<a href="mailto:khmer@lists.idyll.org">khmer@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/khmer" target="_blank">http://lists.idyll.org/listinfo/khmer</a><br>
</font></span></blockquote></div><br></div>