Re: [Paraview] [EXTERNAL] Client/Server connection problems

2014-01-15 Thread Fabian, Nathan
=ON ' From: Fabian, Nathan Sent: Tuesday, January 14, 2014 5:41 PM To: Fabian, Nathan; Utkarsh Ayachit; Scott, W Alan Cc: paraview@paraview.orgmailto:paraview@paraview.org Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems Okay, I figured it out, although I'm still confused. Resolution

Re: [Paraview] [EXTERNAL] Client/Server connection problems

2014-01-14 Thread Fabian, Nathan
have one, unless I add it in on the command line run. Any idea why the server is requiring one? Also is there a way to add in the connect_id through the GUI as opposed to through the command line? Thanks, From: Fabian, Nathan Fabian ndfa...@sandia.govmailto:ndfa...@sandia.gov Date: Monday

Re: [Paraview] [EXTERNAL] Client/Server connection problems

2014-01-13 Thread Fabian, Nathan
between pulls, that is your problem. This has been an issue for me when one of the two (client or server) is behind a firewall, but the other can connect back to Kitware and find that git tag. Make sure the source trees are exactly the same. Alan -Original Message- From: Fabian, Nathan

[Paraview] Client/Server connection problems

2014-01-10 Thread Fabian, Nathan
Hi, I've been trying to figure this one out for a few days and I'm finally giving in for help. I've got a code base on my server that should be a duplicate of the one on my desktop, built differently. In one case I did pulls from master at the same time. I've more recently just tried pulling

Re: [Paraview] [EXTERNAL] Client/Server connection problems

2014-01-10 Thread Fabian, Nathan
. But... If this is the problem, please let me know. You may have an easier setup that we can use to get to the root cause of the problem. Alan -Original Message- From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On Behalf Of Fabian, Nathan Sent: Friday, January 10, 2014 3:59 PM

[Paraview] Calculator removes cell data

2012-02-15 Thread Fabian, Nathan
Hi, I just submitted a bug on this: http://paraview.org/Bug/view.php?id=12944 But I'm wondering if there's a way to work around it. The problem is that I'm trying to modify the coordinates insitu using the displacement, but that ends up deleting the cell data. Is there any way to merge the

[Paraview] Screen flicker

2011-09-07 Thread Fabian, Nathan
Hi, I've had a problem recently with paraview causing my whole screen to flicker when it's rendering. I've tried recompiling with different versions of Qt and with carbon vs cocoa with no luck either way. It seems to be an opengl problem because it only happens when I'm rendering surfaces or

Re: [Paraview] Screen flicker

2011-09-07 Thread Fabian, Nathan
, Sep 7, 2011 at 2:41 PM, Fabian, Nathan ndfa...@sandia.gov wrote: Hi, I've had a problem recently with paraview causing my whole screen to flicker when it's rendering. I've tried recompiling with different versions of Qt and with carbon vs cocoa with no luck either way. It seems

[Paraview] targets not in export set

2011-05-19 Thread Fabian, Nathan
Hi, When I enable install with development install, I'm getting the errors below. Am I missing a flag for install CS wrapped or something like that? This is on a git pull from about 20 minutes ago. Thanks, Nathan. CMake Error: INSTALL(EXPORT ParaViewTargets ...) includes target

[Paraview] Mesa-7.8.2 incompatible?

2011-02-15 Thread Fabian, Nathan
Hi, I've built a recent pull of the master branch against Mesa-7.8.2. I'm building pure Offscreen with no X or GL. When I try to render I get the following fatal error: main/renderbuffer.c:1924: _mesa_add_renderbuffer: Assertion `bufferName == BUFFER_DEPTH || bufferName == BUFFER_STENCIL ||

Re: [Paraview] Mesa-7.8.2 incompatible?

2011-02-15 Thread Fabian, Nathan
Yep. 7.9 works great. I've used 7.8.2 with 3.8.x. Is Mesa something people should expect to upgrade going to paraview 3.10? On 2/15/11 2:40 PM, David Partyka david.part...@kitware.com wrote: Use an older (7.6?) or newer mesa (7.9). On Tue, Feb 15, 2011 at 4:38 PM, Fabian, Nathan ndfa

Re: [Paraview] Fwd: Amazon EC2 Cluster + Paraview

2011-02-14 Thread Fabian, Nathan
didn't see anywhere that I could disable it in cmake On Fri, Feb 11, 2011 at 4:37 PM, Fabian, Nathan ndfa...@sandia.gov wrote: The OSMESA_LIBRARY should also point to libOSMesa.so (btw you can also compile leaving OPENGL_gl_LIBRARY and OPENGL_glu_LIBRARY empty. I found I needed to do this when

Re: [Paraview] Fwd: Amazon EC2 Cluster + Paraview

2011-02-11 Thread Fabian, Nathan
OPENGL_xmesa_INCLUDE_DIR OPENGL_xmesa_INCLUDE_DIR-NOTFOUND OSMESA_INCLUDE_DIR /home/ubuntu/osmesa/include OSMESA_LIBRARY /home/ubuntu/osmesa/lib On Fri, Feb 11, 2011 at 4:19 PM, Fabian, Nathan ndfa...@sandia.gov wrote: The cmake variable needs to point to the library itself

Re: [Paraview] CoProcessing - Export State

2010-09-02 Thread Fabian, Nathan
updated in the build directory even though they updated their code in the source tree. I'll check on that to see why it's happening. Thanks, Andy On Wed, Sep 1, 2010 at 6:16 PM, Fabian, Nathan ndfa...@sandia.gov wrote: Okay thanks. Apparently, I'm doing some version of building that includes

[Paraview] CoProcessing - Export State

2010-09-01 Thread Fabian, Nathan
Hi, When I export state with the image data into the coprocessing python script it includes some properties which don't appear when I use coprocessing. For instance, DataRepresentation1.SelectOrientationVectors = [None, '']. It complains with: File

Re: [Paraview] CoProcessing - Export State

2010-09-01 Thread Fabian, Nathan
association, +# just pick POINTS. +val = str(ASSOCIATIONS['POINTS']) self.SMProperty.SetElement(3, str(val)) self.SMProperty.SetElement(4, values[1]) else: Andy On Wed, Sep 1, 2010 at 5:43 PM, Fabian, Nathan ndfa...@sandia.gov wrote

Re: [Paraview] CoProcessing question

2010-07-28 Thread Fabian, Nathan
Hi, I originally tried the following on each piece: SetOrigin(0,0,0) SetSpacing(.1,.1,0) SetExtent(0,xmax,ystart(myproc),ystop(myproc),0,0) And when I output it to XMLPImageDataWriter, paraview couldn't read it complaining about the extents. It actually correctly showed the first piece. I

Re: [Paraview] node ordering mismatch when saving vtu as exodus and vice versa

2010-05-10 Thread Fabian, Nathan
Okay, this one I can repeat. I'll take a look. Thanks, Nathan. On 5/7/10 8:17 AM, pat marion pat.mar...@kitware.com wrote: I think you can repeat it like this: create wavelet source apply append datasets to convert to unstructured grid save as exodus, then reopen the saved file Pat On Fri,

Re: [Paraview] node ordering mismatch when saving vtu as exodus and vice versa

2010-05-06 Thread Fabian, Nathan
I just tried opening the file and saved as a .e file and then opened the .e and did not notice any difference. What version of paraview is this happening? Thanks, Nathan. On 5/6/10 10:59 AM, Scott, W Alan wasc...@sandia.gov wrote: Please write this up as a bug in the ParaView bug tracker.

[Paraview] Process id from within pvbatch

2010-04-09 Thread Fabian, Nathan
Hi, Is there any way to get the local process id from within a python script? I can't seem to get hold of vtkMultiProcessController and can't find any other way through the modules... Thanks, Nathan. ___ Powered by www.kitware.com Visit other

Re: [Paraview] Process id from within pvbatch

2010-04-09 Thread Fabian, Nathan
That did it. Thanks On 4/9/10 12:40 PM, Andy Bauer andy.ba...@kitware.com wrote: I think what you want is: pid = servermanager.vtkProcessModule.GetProcessModule().GetPartitionId() Andy On Fri, Apr 9, 2010 at 2:34 PM, Fabian, Nathan ndfa...@sandia.gov wrote: Hi, Is there any way to get

[Paraview] Turn off text progress output in pvbatch

2009-09-02 Thread Fabian, Nathan
Hi, When I run pvbatch I get progress to stdout like this: vtkFilter(10) : [ .] vtkFilter(135) : [ .] vtkFilter(137) : [ .] vtkFilter(127) : [ .] vtkFilter(139) : [ .] How do I turn that off? Thanks, Nathan.

Re: [Paraview] Turn off text progress output in pvbatch

2009-09-02 Thread Fabian, Nathan
Along a similar line, it seems like this might be convenient as a command line parameter where when I'm running the script as a debug I would leave the output on, but once I send it over to the cluster I'd just add the flag to disable it in the qsub instead of needing to change the script. On