Thanks! One of the attractions is the portability, so we don't have to recode if we outgrow or change schedulers. Part of the problem seems to be the abstraction. For example, setting the outputPath field in the job to myhost:/some/path/to/some/file.txt didn't deliver the result to the headnode in the way -o would. The problem seemed to be in how the drmaa layer was rewriting the path, assumptions about whether the intermediate path /some/path / etc existed on the node vs the submit host. So I assume most people are using either the shell or torque api to submit then?<br>
<br>Darren<br><br><div class="gmail_quote">On Tue, Jun 3, 2008 at 1:14 PM, Joshua Bernstein <<a href="mailto:jbernstein@penguincomputing.com">jbernstein@penguincomputing.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Darren,<br>
<br>
While I haven't used DRMAA with TORQUE directly, my understanding of DRMAA is that it is still in its infancy. Though my other limited experience with DRMAA has shown that it provides a nice abstracting between your software and a scheduler, a layer of portability if you well.<br>
Though that said, different DRMAA layers are at different states of maturity, so some have different gotchas here there.<br>
<br>
-Joshua Bernstein<br>
Software Engineer<br>
Penguin Computing<br>
<br>
<br>
<br>
Darren Platt wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
Hi,<br>
<br>
we've been testing out Torque + DRMAA combination and using DRMAA-py that was written for SGE. I've<br>
encountered a few issues and was wondering if there are many users out there using Torque+DRMAA. The underlying<br>
Torque implementation seems to be behaving correctly, but I've had a lot of issues trying to get input/output files to stage<br>
correctly using scp. I ran into some slight problems compiling the python wrappers as well that required a small addition to<br>
the torque/DRMAA headers. Has anyone used DRMAA-py with Torque? Any comments appreciated. We're testing<br>
a variety of different schedulers and I was impressed with the relative ease of installation for Torque. The docs were a little out<br>
of date in places, but overall good. We're testing 2.3.0,<br>
<br>
Thanks,<br>
<br>
-- <br>
Darren Platt<br>
Senior Director, Research<br>
23andMe, inc<br>
<br>
<br></div></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
torqueusers mailing list<br>
<a href="mailto:torqueusers@supercluster.org" target="_blank">torqueusers@supercluster.org</a><br>
<a href="http://www.supercluster.org/mailman/listinfo/torqueusers" target="_blank">http://www.supercluster.org/mailman/listinfo/torqueusers</a><br>
</blockquote>
</blockquote></div><br><br clear="all"><br>-- <br>Darren Platt<br>Senior Director, Research<br>23andMe, inc