<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Hong,<br>
      <br>
      It looks like you've found a bug in ParaView, there probably
      should be a check preventing this division when the render window
      is empty. However, it's likely a non issue when FPEs are disabled,
      which I believe is the default. Could you search the vtkPVConfig.h
      file (found in build/install dir) for PARAVIEW_ENABLE_FPE? If this
      is defined during the build then PV will enable FPE's when it
      starts. If that's the case in your build, then a quick fix for you
      would be to rebuild with that feature disabled. If that's not the
      case in your build, FPE's must be being enabled by a library
      that's being linked in. You may have to inquire about this with
      your sys admins, if they know of any such library.<br>
      <br>
      Burlen<br>
      <br>
      On 02/27/2013 10:01 AM, Hong Yi wrote:<br>
    </div>
    <blockquote
cite="mid:65F8B323A072504ABFC5D3D8751910514B1F1813@MAIL-MBX2.ad.renci.org"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
        {mso-style-name:msochpdefault;
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Calibri","sans-serif";}
span.emailstyle17
        {mso-style-name:emailstyle17;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D">OK, now I know
            why the floating point exception is raised after looking at
            the values of those variables and the source code.
            Specifically, the whole statement it fails is actually the
            following:<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Vx = 2.0 *
            (this-&gt;DisplayPoint[0]&nbsp; - sizex * Viewport[0])/</span><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">(sizex*(this-&gt;Viewport[2]-this-&gt;Viewport[0]))
            - 1.0,</span><span style="color:#1F497D"> where the
            denominator has a value of 0 when it fails: sizex = 0,
            this-&gt;Viewport[2]=1, and this-&gt;Viewport[0]=0, which
            results in &#8220;divide by zero&#8221; floating point exception. The
            key here is the sizex value which should not be zero, and
            sizex is equal to the first component of
            this-&gt;VTKWindow-&gt;GetSize(). So this VTKWindow gets a
            size of zero which results in this floating point exception.
            I am puzzled on why this could be the case since other
            filters like isocontouring does not have this problem.
            Hopefully someone in the list could provide some insight on
            this problem.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Hong<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                <a class="moz-txt-link-abbreviated" href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>
                [<a class="moz-txt-link-freetext" href="mailto:paraview-bounces@paraview.org">mailto:paraview-bounces@paraview.org</a>]
                <b>On Behalf Of </b>Hong Yi<br>
                <b>Sent:</b> Wednesday, February 27, 2013 12:26 PM<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
                <b>Subject:</b> Re: [Paraview] floating point exception
                error when doing slice filter (only happen when running
                pvserver remotely in parallel)<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <div>
          <p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">Just
              some follow-up information I hope to shed some light on
              this problem. I used pdb to debug pvserver running with
              mpirun on the server and found this floating point
              exception error happens on the line below:<br>
              <br>
              Program received signal SIGFPE, Arithmetic exception.<br>
              0x00002ad33e95021b in vtkViewport::DisplayToView
              (this=0x43a2670)<br>
              &nbsp;&nbsp;&nbsp; at
/home/hyi2/Download/ParaView-3.14.1-Source/VTK/Filtering/vtkViewport.cxx:204<br>
              204&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              (sizex*(this-&gt;Viewport[2]-this-&gt;Viewport[0])) - 1.0;<br>
              <br>
              which puzzles me since I cannot imagine why this could
              cause floating point exception (I cannot see possibility
              of "divide by zero" or other possible arithmetic
              exception). I did try to check or uncheck "Remote Render
              Threshold" checkbox both ways which results in the same
              failure in the same statement as noted above. Also,
              isocontouring filter runs fine with correct visual output,
              but slicing and clipping filters result in same errors as
              noted above.<br>
              <br>
              Hope this additional debug info could shed some light and
              trigger some idea on what could be the problem. Perhaps
              there is a possibility it is NVidia driver related? But in
              my configuration, HPC server uses MESA software rendering
              and my client NVidia driver is up to date with Geforce
              GTX580 graphics card. <br>
              <br>
              Thanks for any ideas on what could cause this problem!<br>
              <br>
              Hong <br>
              <br>
              <o:p></o:p></span></p>
          <div>
            <div class="MsoNormal" style="text-align:center"
              align="center"><span
                style="font-size:12.0pt;font-family:&quot;Times New
                Roman&quot;,&quot;serif&quot;;color:black">
                <hr size="2" width="100%" align="center">
              </span></div>
            <div id="divRpF39872">
              <p class="MsoNormal" style="margin-bottom:12.0pt"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">
                  <a moz-do-not-send="true"
                    href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>
                  [<a class="moz-txt-link-abbreviated" href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>] on behalf of Hong Yi
                  [<a class="moz-txt-link-abbreviated" href="mailto:hongyi@renci.org">hongyi@renci.org</a>]<br>
                  <b>Sent:</b> Friday, February 22, 2013 12:27 PM<br>
                  <b>To:</b> <a moz-do-not-send="true"
                    href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
                  <b>Subject:</b> [Paraview] floating point exception
                  error when doing slice filter (only happen when
                  running pvserver remotely in parallel)</span><span
                  style="font-size:12.0pt;font-family:&quot;Times New
                  Roman&quot;,&quot;serif&quot;;color:black"><o:p></o:p></span></p>
            </div>
            <div>
              <div>
                <p class="MsoNormal"><span style="color:black">I built
                    ParaView server with MPI on a HPC cluster with
                    OSMesa support since the cluster does not have
                    graphics hardware. The MPI compiler used to build
                    ParaView is mpich2/gnu412x64/1.4-shared. Paraview
                    server built successfully on the cluster without any
                    error. I can successfully connect to the pvserver
                    running on multiple nodes remotely via Paraview
                    client running on my local desktop, load data in,
                    and do gradient and vorticity computation, and look
                    at isosurfaces without problems. However, when I do
                    slice filter to look at one slice, as soon as I
                    click on slice filter, pvserver aborts with floating
                    point exception error. It is not the data problem
                    because I can do slice filter without problem for
                    the same data if I run builtin Paraview
                    server/client locally, so the problem only occurs
                    when the local client connects to pvserver running
                    remotely on multiple nodes (or on one node) via
                    mpirun. So far, the slice filter is the only filter
                    I have run into with this floating point exception
                    error raised by the remote pvserver. The other
                    filters such as gradient of unstructured data,
                    calculator of vorticity, isocontour all run
                    successfully with correct results produced. Any idea
                    on what could cause this problem is very much
                    appreciated!<o:p></o:p></span></p>
                <p class="MsoNormal"><span style="color:black">&nbsp;<o:p></o:p></span></p>
                <p class="MsoNormal"><span style="color:black">Thanks,<o:p></o:p></span></p>
                <p class="MsoNormal"><span style="color:black">&nbsp;<o:p></o:p></span></p>
                <p class="MsoNormal"><span style="color:black">Hong<o:p></o:p></span></p>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>

Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>

Please keep messages on-topic and check the ParaView Wiki at: <a class="moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>

Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>