Dave
Thanks,
The page you sent me to was quite helpful, I also came across this page, which
was very useful for generating scripts for multiple parameters a job submissions
http://www.umbc.edu/hpcf/resources-tara-2010/generating-batch-scripts.html
I used info from both those pages and got my
Download link is broken:
404 File not found!*
/projects/FTP/pub/paraview/nightly/ParaView-3.98.0-Linux-64bit-glibc-2.3.6-NIGHTLY.tar.gz
but also this is the previous version. The 3.98.1 NIGHTLY is not
accesible.
Regards,
--
## Requests to visualizat...@bsc.es ##
--
Carlos Tripiana Montes
The paraview.benchmarks module should help in either case. What it does is
grab all processes' vtktimerlogs, which contain in text form the time taken
by every filter and rendering element in the pipeline, and saves/restores
them to analyze at your leisure. That part at least should still be
Hi,
I found the bug that was causing these strange results. See
http://review.source.kitware.com/#/c/10748/ for a very quick easy fix.
Best,
Charl
On Thu, Mar 21, 2013 at 9:15 PM, Charl parav...@turingbirds.com wrote:
Dear list,
Forgive me being obtuse. I am attempting to integrate a
So I'm trying to use the Material Interface Filter:
http://www.paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#Material_Interface_Filter
and have carefully created XML datafiles using vtkNonOverlappingAMR (*.vth)
format. Unfortunately the v3.98.1 gui does not furnish the Properties
Hi Andy,
Many thanks for your very helpful responses. Now I think I have a good
understanding on the ParaView in-situ viz process. I have also cleared up the
email thread history a bit and changed the subject to reflect my new question
below.
I have got an in-situ example running without live
Hi Bucky,
I have been meaning to investigate this but I have been sick. I will have
an answer for you in a day or two.
-berk
On Tue, Apr 9, 2013 at 11:44 AM, Kashiwa, Bucky b...@lanl.gov wrote:
So I'm trying to use the Material Interface Filter:
Bucky,
I believe that the problem is that - as you suggest below - the material
interface filter only accepts down converted unsigned chars. In my mind, this
is a bug/feature hole. Either, 1) the Material Interface Filter should accept
down converted unsigned chars or default variables, 2) a