<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Is anyone using Octave on Lonestar?</title>
  <link rel="alternate" href="https://conferences.xsede.org/c/message_boards/find_thread?p_l_id=&amp;threadId=454893" />
  <subtitle>Is anyone using Octave on Lonestar?</subtitle>
  <entry>
    <title>RE: Is anyone using Octave on Lonestar?</title>
    <link rel="alternate" href="https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=618908" />
    <author>
      <name>Yaakoub Youssef El Khamra</name>
    </author>
    <id>https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=618908</id>
    <updated>2013-11-06T16:30:16Z</updated>
    <published>2013-11-06T16:30:16Z</published>
    <summary type="html">Octave seems to work fine on the compute nodes. Did you submit a ticket about this issue sir? Did you get it resolved? &lt;br /&gt;&lt;br /&gt;&lt;div class="quote-title"&gt;Jingjing Li:&lt;/div&gt;&lt;div class="quote"&gt;&lt;div class="quote-content"&gt;For anyone who is interested: Octave on Lonestar is configured for login nodes only.  We can not run on working nodes yet.  They say they are working on installing octave on the working nodes.&lt;br /&gt;&lt;br /&gt;BTW, since we are supposed not to run jobs on login nodes, basically this means Octave on lonestar is very much useless, I assume.&lt;/div&gt;&lt;/div&gt;</summary>
    <dc:creator>Yaakoub Youssef El Khamra</dc:creator>
    <dc:date>2013-11-06T16:30:16Z</dc:date>
  </entry>
  <entry>
    <title>Is anyone using Octave on Lonestar?</title>
    <link rel="alternate" href="https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=454892" />
    <author>
      <name>Jingjing Li</name>
    </author>
    <id>https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=454892</id>
    <updated>2013-02-06T18:43:40Z</updated>
    <published>2013-02-06T18:43:40Z</published>
    <summary type="html">Is anyone successfully using Octave on Lonestar?  I am trying to use it (the version already installed on the system.  I heard that someone compile there own binary).  I met with the following issues:&lt;br /&gt;&lt;br /&gt;1) I can load the octave module (with other required modules such as mkl, etc.) on the login node, and run octave directly under login node.&lt;br /&gt;&lt;br /&gt;2) However, when I submit a jobscript in which octave is called with an absolute path to the queue, the job will fail with the following message:&lt;br /&gt;&lt;br /&gt;Lmod Warning: Did not find: octave/3.6.1&lt;br /&gt;&lt;br /&gt;/opt/apps/octave/3.6.1/bin/octave: bad interpreter: No such file or directory&lt;br /&gt;&lt;br /&gt;3) If I use idev and launch an interactive job, and working on an node I am assigned, I found out the following:&lt;br /&gt;    a) &amp;#034;module spider octave/3.6.1&amp;#034; returns correct octave module information.&lt;br /&gt;    b) &amp;#034;module load octave/3.6.1&amp;#034; fails with &amp;#034;Lmod Warning: Did not find: octave/3.6.1&amp;#034;&lt;br /&gt;    c) Other modules such as mkl can be successfully loaded in the interactive job&lt;br /&gt;&lt;br /&gt;4) If I load all the modules (including octave) under login node, and launch the idev job with -V option, then under the working node I am assigned&lt;br /&gt;    a) &amp;#034;module list&amp;#034; indeed shows all the modules loaded under the login node before launching the interactive job, including octave&lt;br /&gt;    b) However, &amp;#034;which octave&amp;#034; returns a message that &amp;#034;octave not found in ....(my PATH)&amp;#034;, although /usr/appl/octave/3.6.1/bin/ is indeed in the path.&lt;br /&gt;    c) If &amp;#034;ls /usr/appl/octave/3.6.1&amp;#034;, it shows an empty directory!&lt;br /&gt;&lt;br /&gt;So what is going on?  Anyone meet with the same issue or have any suggestions?</summary>
    <dc:creator>Jingjing Li</dc:creator>
    <dc:date>2013-02-06T18:43:40Z</dc:date>
  </entry>
</feed>

