Re: [Paraview] making the leap to v5.1 on the cray

2016-07-05 Thread Burlen Loring 

got it thanks!

On 07/05/2016 02:16 PM, Utkarsh Ayachit wrote:

first of all, is 5.1 production ready? or is 4.4 still the way to go in a 
production environment? this would be the only install available for users so 
it's important that it function reliably/correctly.

See this thread:
http://public.kitware.com/pipermail/paraview/2016-June/037389.html


re: 5.1, I'm wondering what the recommended mesa config for use with pv 5.1 on 
cray is?  Which version of mesa have been tested/recommended? is open swr an 
option yet? or is llvmpipe still a better bet?

11.2.* is recommended. OpenSWR is not yet in official release of
Mesa3D (it's still in the RC stage), llvmpipe would still be the best
bet.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] making the leap to v5.1 on the cray

2016-07-05 Thread Utkarsh Ayachit 
> first of all, is 5.1 production ready? or is 4.4 still the way to go in a 
> production environment? this would be the only install available for users so 
> it's important that it function reliably/correctly.

See this thread:
http://public.kitware.com/pipermail/paraview/2016-June/037389.html

> re: 5.1, I'm wondering what the recommended mesa config for use with pv 5.1 
> on cray is?  Which version of mesa have been tested/recommended? is open swr 
> an option yet? or is llvmpipe still a better bet?

11.2.* is recommended. OpenSWR is not yet in official release of
Mesa3D (it's still in the RC stage), llvmpipe would still be the best
bet.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] making the leap to v5.1 on the cray

2016-07-05 Thread Burlen Loring 

Hi All,

first of all, is 5.1 production ready? or is 4.4 still the way to go in 
a production environment? this would be the only install available for 
users so it's important that it function reliably/correctly.


re: 5.1, I'm wondering what the recommended mesa config for use with pv 
5.1 on cray is?  Which version of mesa have been tested/recommended? is 
open swr an option yet? or is llvmpipe still a better bet?


Thanks
Burlen
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] problems using pvbatch in frozen build

2016-07-05 Thread Burlen Loring 

Hi All,

I'm encountering some issues when trying to use pvbatch from a frozen 
build(PARAVIEW_FREEZE_PYTHON=ON). Seems that certain key python modules 
are missing.ie math. However, I can use Python shell feature in the GUI 
from the same build. Do we have any idea about what may be wrong with 
pvbatch?



here is output from a simple test:

   nid00048:~$pvbatch pvbatch-test.py
   started
   Traceback (most recent call last):
  File "pvbatch-test.py", line 3, in 
from paraview.simple import *
  File
   
"/usr/common/graphics/ParaView/builds/PV-4.4.0/lib/site-packages/paraview/simple.py",
   line 40, in 
import lookuptable
  File
   
"/usr/common/graphics/ParaView/builds/PV-4.4.0/lib/site-packages/paraview/lookuptable.py",
   line 21, in 
from math import sqrt
   ImportError: No module named math

I tried this as well:

   nid00048:~$pvpython
   Python 2.7.9 (default, Jan  8 2015, 22:29:31)
   [GCC 4.9.1 20140716 (Cray Inc.)] on linux2
   Traceback (most recent call last):
  File "/etc/pythonstart", line 7, in 
import readline
   ImportError: Excluded frozen object named readline
>>> import math
   Traceback (most recent call last):
  File "", line 1, in 
   ImportError: No module named math
>>>

Thanks
Burlen
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Suggestion for STL import

2016-07-05 Thread Utkarsh Ayachit 
Eugene,

I am pretty sure the community will be interested in this! While I'll need
to look into the reader to understand, to get things going, do you have a
sample dataset to demonstrate the issue?

Utkarsh

On Tue, Jul 5, 2016 at 10:28 AM, Eugene de Villiers 
wrote:

> Hi,
>
>
>
> When importing STL format geometry or similar, where connectivity
> information is not implicit in the data structure, it appears that the
> connectivity is reconstructed via an  octree search. This is very
> inefficient when surfaces with large differences in edge length are
> imported – we have had a recent case where an STL took 45mins to load. If
> the same input geometry is converted to OBJ format via an external tool,
> the load time reduces to minutes.
>
>
>
> A generally more efficient method is to calculate the distance of each
> point from a location outside the point cloud bounding box and then to
> bubble-sort the resulting list. Unless you are dealing with a pathological
> case your local search neighbourhood of identical distance points will be
> small and the algorithm very fast. More complex, multi-origin algorithms
> are also possible to counter pathological instances.
>
>
>
> I can provide more details and sample code if you are interested.
>
>
>
> Best regards,
>
>
>
> *Eugene de Villiers*
>
> *Managing Director*
>
> e.devilli...@engys.com
>
> Mob: +44 (0) 77 89748490
>
> Tel: +44 (0)20 32393041 (ext. 102)
>
> Fax: +44 (0)20 33573123
>
> [image: logo_red-black_fonts_signature] 
>
>
>
> This message is intended only for the use of the addressee and may contain
> information that is privileged, confidential and exempt from disclosure
> under applicable law. If the reader of this message is not the intended
> recipient, or the employee or agent responsible for delivering the message
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this e-mail in error, please notify us immediately by
> return e-mail and delete this e-mail and all attachments from your system.
>
>
>
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Suggestion for STL import

2016-07-05 Thread Eugene de Villiers 
Hi,

When importing STL format geometry or similar, where connectivity information 
is not implicit in the data structure, it appears that the connectivity is 
reconstructed via an  octree search. This is very inefficient when surfaces 
with large differences in edge length are imported – we have had a recent case 
where an STL took 45mins to load. If the same input geometry is converted to 
OBJ format via an external tool, the load time reduces to minutes.

A generally more efficient method is to calculate the distance of each point 
from a location outside the point cloud bounding box and then to bubble-sort 
the resulting list. Unless you are dealing with a pathological case your local 
search neighbourhood of identical distance points will be small and the 
algorithm very fast. More complex, multi-origin algorithms are also possible to 
counter pathological instances.

I can provide more details and sample code if you are interested.

Best regards,

Eugene de Villiers
Managing Director
e.devilli...@engys.com
Mob: +44 (0) 77 89748490
Tel: +44 (0)20 32393041 (ext. 102)
Fax: +44 (0)20 33573123
[logo_red-black_fonts_signature]

This message is intended only for the use of the addressee and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If the reader of this message is not the intended recipient, or 
the employee or agent responsible for delivering the message to the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received this 
e-mail in error, please notify us immediately by return e-mail and delete this 
e-mail and all attachments from your system.


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview