Bingo! My Catalyst-instrumented sample code now works like a charm on my VM as
well.
Thanks a lot for your help.
Matthieu
From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Tuesday, September 15, 2015 3:21 PM
To: Dorier, Matthieu
Cc:
Thanks for the info – will try the new release with OSMESA next week. Still
waiting to get an allocation on our Tesla K40 nodes to test the large dataset
with OpenGL2 and hardware rendering.
Thanks again,
--
David Trudgian Ph.D.
Computational Scientist, BioHPC
UT Southwestern Medical Center
On Mon, Sep 14, 2015 at 21:41:09 +, Anthony Crognale wrote:
> Looks like building for release worked properly, the resulting
> Paraview runs fine now.
>
> Thanks much for your help!
Great!
FYI, the release mode improvments are here:
Thanks a lot Utkarsh!
In the mean time I tried my code on the Blue Waters machine at NCSA and it
works like a charm, so yes, it has to be the VM. I'll try with OSMesa. I don't
need the ParaView GUI on the VM anyway.
Thanks,
Matthieu
From: Utkarsh
Hey Cory
Thanks for the tip with the array [(0,0,0) (0,0,0),
(x,y,time),(0,0,0)...(0,0,0)] While this was easy to do, I still get a
point in Paraview at 0/0 for each time, or, if I choose to draw a line, one
that starts at 0/0 - which is kind of understandable, when looking at my
table,
Am currently using Mesa 10.5.4 as I’d seen that as a working config mentioned
somewhere on the web, so will try newer. Any reason to avoid the 10.6 series?
I guess I should also try moving to Paraview 4.4 now :-)
--
David Trudgian Ph.D.
Computational Scientist, BioHPC
UT Southwestern Medical
I just realized you are on PV 4.3.1, that version is probably old enough
that we did not have OpenGL2 working with Mesa back then. Updating to a
more recent PV/VTK will be needed to use OpenGL2 with Mesa (I think we got
it working three or four months ago). As far as I know the 10.6 versions of
Yes, unsigned short values.
DT
--
David Trudgian Ph.D.
Computational Scientist, BioHPC
UT Southwestern Medical Center
Dallas, TX 75390-9039
Tel: (214) 648-4833
From: Berk Geveci [mailto:berk.gev...@kitware.com]
Sent: Tuesday, September 15, 2015 2:43 PM
To: David Trudgian
Matthieu,
Simply set the CMake variable OPENGL_glu_LIBRARY to empty. I think
you're pointing it to non-existant
/home/mdorier/local/mesa/lib/libGLU.so and hence the issue. If I am
not mistaken, GLU is optional only required for certain tests.
Utkarsh
On Tue, Sep 15, 2015 at 3:26 PM, Dorier,
I compiled and installed Mesa locally (Gallium llvmpipe state-tracker), but
when compiling ParaView I get this error:
make[2]: *** No rule to make target `/home/mdorier/local/mesa/lib/libGLU.so',
needed by `lib/libIceTGL.so'. Stop.
It appears that libGLU.so is not built by Mesa. Is this
Hey David,
I am hoping to have some time to play around with volume rendering and
hopefully tracking this issue, one thing that I wanted to clarify: it
sounds from you description that you have a short (2 byte) value. Is that
correct?
Thanks,
-berk
On Wed, Sep 9, 2015 at 5:00 PM, David Trudgian
Thanks for reporting, Eric. I've reported a bug:
http://www.paraview.org/Bug/view.php?id=15727
Utkarsh
On Tue, Sep 15, 2015 at 9:36 AM, Eric Nodwell
wrote:
> Oops, correction to that previous post. The actual fix (bit of a
> sledgehammer) is
>
> sudo chmod -R a+rx
Richard,
I understand. Sorry, I don't think there is a way to do this.
Having an annotation mechanism for your use case might be something we can
do in the future, but there are currently no plans to do this that I know
of.
Best,
Cory
On Tue, Sep 15, 2015 at 7:13 AM, no name
In an attempt to clear my bug backlog, I revisited this issue. I am happy
to report that this is now fixed. I am even happier to report that I didn't
have to do anything. It seems like our overhaul of the ghost information
addressed it. The version I tested is several months all so this is
Matthieu,
Good news, I just saw the black window issue too on my build. I'll
track it down and get back to you.
Utkarsh
On Tue, Sep 15, 2015 at 9:12 AM, Utkarsh Ayachit
wrote:
> Matthieu,
>
>> - If I run the application from the VM's graphical interface, it runs
NVM...those were from your original tarball. I thought they were
generated as an output from my run :). It's indeed an X issue in both
cases. Couple of options:
1. Do a Mesa3D build locally on the VM. Then set LD_LIBRARY_PATH to
point to the generated OpenGL libs and run ParaView/Catalyst.
Duh, found it … -D Enable_qt4 ….
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone: 410-278-6266
-Original Message-
From: ParaView on behalf of Rick Angelini
After unpacking ParaView-4.4.0-Qt4-Linux-64bit.tar.gz I was unable to
launch it. Attempting to launch it from the command line resulted in:
$ /opt/ParaView-4.4.0-Qt4-Linux-64bit/lib/paraview-4.4/paraview
/opt/ParaView-4.4.0-Qt4-Linux-64bit/lib/paraview-4.4/paraview: error
while loading shared
Oops, correction to that previous post. The actual fix (bit of a
sledgehammer) is
sudo chmod -R a+rx /opt/ParaView-4.4.0-Qt4-Linux-64bit/
On Tue, Sep 15, 2015 at 3:34 PM, Eric Nodwell
wrote:
> After unpacking ParaView-4.4.0-Qt4-Linux-64bit.tar.gz I was unable to
>
If I go to the download page , I can download something called '4.4
(Latest Stable)' which to me implies that’s still a development build and
not the final production release?
http://www.paraview.org/download/
Rick Angelini
USArmy Research Laboratory
CISD/HPC
Hmm...I was using it to point to the "latest stable" release. I
suppose I'll just remove the text to avoid confusion fixed.
Utkarsh
On Tue, Sep 15, 2015 at 8:27 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) wrote:
> If I go to the download page
Thanks Utkarsh. That makes it consistent with other production releases
are tagged for download …. 8-)
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone: 410-278-6266
-Original Message-
From: Utkarsh Ayachit
How do I tell the superbuild to use QT4?
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone: 410-278-6266
-Original Message-
From: Utkarsh Ayachit
Date: Tuesday, September 15, 2015 at 9:05 AM
To:
Matthieu,
> - If I run the application from the VM's graphical interface, it runs fine.
> It only gives me the OpenGL warning I mentioned before. BUT the generated
> file has a big black area (see image_2.png attached). Also I see a window
> appear for a brief moment with the correct (full)
24 matches
Mail list logo