ParaView 3 Telecon 11-04-2010

Item	People	Description
1	Moreland	Project Randy
2	Moreland	SC Tutorial
3	Greg Weirs	CTH Tracer data
4	Mauldin	Visit bridge/data files
5	Pebay	Statistics package
6	Geveci	ParaView + ADIOS
7	Scott	ParaView 3.8.1 Release
8	Moreland	Documenting Plugins
9	Moreland	Warning when ProcessRequests modifies itself
10	Moreland	Book omissions and errata
11	Utkarsh	Transition to git
12	Moreland	Stronger Dashboard Test consolidation Boiling the frog coverage

Project Randy

Today: Nathan has in situ working with CTH and XTP? Plan for Cielito and/or Cielo? Papers?

Previously:

Alan is still having problems scaling up past 5.5K cores or so, but this might be caused by the Red Sky system itself. Nathan reports similar problems using solvers without ParaView at all.

Ken got timings from Pat for running on Intrepid up to 32K cores. Pat has mentioned that might be some issues with the timings, possibly the job size being too big for the problem size.

In two weeks, Pat is going to Argonne and working with Vankate, who has been doing research on moving data quickly from computation platforms to visualization clusters. Going to integrate that into the coprocessing library.

We talked a bit about data staging. Everyone's doing it. Ken and Scott Klasky have had talked in the past about combining the paraview server with ADIOS data staging. Ken has an action item to send an email to Scott to perhaps organize a meeting at SC between Scott, Ken, and Berk.

Need good I/O comparisons between solver output and coprocessing output.

Can we distribute PHASTA with coprocessing adapter?

Pat's trip to Argonne: "It was a very productive visit." Working on using Vankate's library to deliver data from the supercomputer to the vis cluster. Made some good progress but has not finished. Still moving forward.

Nathan has been able to compile coprocessing static with CTH on XTP (small Cielo clone). With the AMR dual grid filter, there is some odd MPI abort with a tag value. Works fine on point contouring.

Call to everyone: a list of features to put in a comparative matrix between ParaView Coprocessing and other solutions.

Kitware: everything is releaseable; everything will be in paraview kitware--no scalability changes turn into more of a kitware/sandia project with roadmap Jeff: rollout with Cielo; coprocesson on cielo in situ

   alan will find out unclassified time window
   

alan compiling on cielo; zia app

   dataset
   pat going to push stuff to paraview
   kitware has access to jaguar
   plan/roadmap

Supercomputing Tutorial

Today: Ken doing supercomputing tutorial?

Previously:

We got permission to distribute PHASTA as an example for integration. However, the only compelling use cases use a commercial solver. There is some completely open solver, but it has no real compelling use case.

oakridge booth--jaguar, adios, staging, paraview

Statistics Package

select data filter complext filter interface

ParaView + ADIOS

Today:

modifying reader so that it can suck data through staging? jaguar issues? oakridge booth? demo at supercomputing?

Previously:

paraview works reading adios data from disk next step working with them to modify reader such that it can suck data through staging paraview will read from staging via adios issues on jaguar oakridge booth adios works find on desktop demo at supercomputing adios is in mainstream paraview--young project

ParaView 3.8.1 Release

Today SNL 3.8.1 released for all/most machines, classified side?

Previously:

release is done at Kitware; many SNL builds done; Alan still working a few

released into unclassified side; trying to release into classified side;

Documenting Plugins

The new rule should be that if a plugin is distributed with the ParaView binaries, it must have a wiki page documenting it. These wiki pages will then be integerated in the new ParaView electronic book.

Warning when ProcessRequest modifies itself

Previously:

A while ago we talked about adding a check to the executive that issues a warning if it detects that its MTime changes during a call to ProcessRequest. Whatever happened to that? I just spent 2 days tracking down a parallel pipeline update problem that would have been quickly alerted had this been in place (and was easily fixed once I put my own check in place).

Berk suggested first adding the check only to ParaView. We will see how that works, and then possibly move to VTK. Kitware will take care of that.

On Berk's todo list. Berk is working on proposals for the ARB. One is to change the modularization of VTK. The other is to yank out VTK 4.0 compatibility, which will allow us to clean up vtkExecutive change.

Book omissions and errata

Previously:

Lisa is going to create a bug-tracker like functionality for the Kitware books.

Transition to git

Previously:

Branchy workflow. Tie in to stronger dashboard.

Jeff wants to set up ParaView building and dashboard submission on his desktop. Utkarsh promised how-to information.