ParaView 3 Telecon 12-16-2010: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
(Created page with '{| cellpadding="2" cellspacing="4" |- ! style="background:#abcdef" | Item ! style="background:#abcdef" | People ! style="background:#abcdef" | Description |- | 1 || Moreland || P…')
 
No edit summary
 
(14 intermediate revisions by the same user not shown)
Line 5: Line 5:
! style="background:#abcdef" | Description
! style="background:#abcdef" | Description
|-
|-
| 1 || Moreland || Project Randy
| 1 || Moreland, Nathan || Project Randy
|-
|-
| 2 || Moreland || SC Tutorial
| 2 || Greg Weirs || CTH Tracer data
|-
|-
| 3 || Greg Weirs || CTH Tracer data
| 3 || Mauldin, Alan || Visit bridge/data files
|-
|-
| 4 || Mauldin || Visit bridge/data files
| 4 || Pebay || Statistics package
|-
|-
| 5 || Pebay || Statistics package
| 5 || Mauldin, Weirs || Prism
|-
|-
| 6 || Mauldin, Weirs || Prism
| 6 || Alan, kitware || ParaView 3.10 Release
|-
|-
| 7 || Geveci || ParaView + ADIOS
| 7 || Mauldin || ParaView roadmap?
|-
|-
| 8 || Scott || ParaView 3.8.1 Release
| 8 || Moreland || Warning when ProcessRequests modifies itself
|-
|-
| 9 || Moreland || Documenting Plugins
| 9 || Moreland || Book omissions and errata
|-
|-
| 10 || Moreland || Warning when ProcessRequests modifies itself
| 10 || Moreland || Stronger Dashboard
|-
|-
| 11 || Moreland || Book omissions and errata
| 11 || branchy workflow
|-
|-
| 12 || Utkarsh || Transition to git
| 12 || Geveci || ParaView + ADIOS
|-
| 13 || Moreland || Stronger Dashboard
* Test consolidation
* Test consolidation
* Boiling the frog coverage
* Boiling the frog coverage
Line 38: Line 36:
'''Today:'''
'''Today:'''


Ken has been emailing an abstrct(?) around.  Help, support needed?
may need help later on feature comparison table, time to go


Call to everyone: a list of features to put in a comparative matrix between ParaView Coprocessing and other solutions.
Ken has been emailing a proposal around. Help, support needed?


Nathan:  in situ on which multicores?
Nathan:  in situ on which multicores?  In situ project on vtksnl?


Getting on to Cielito or Cielo?
Alan:  zia app stuff done? was run on ciello unclassified, passed;
 
Alan:  zia app stuff done?
 
Any related meetings at supercomputing?


Need good I/O comparisons between solver output and coprocessing output.
Need good I/O comparisons between solver output and coprocessing output.
Line 56: Line 50:
'''Previously:'''
'''Previously:'''


turn into more of a kitware/sandia project with roadmap
== CTH tracer data ==
 
== Supercomputing Tutorial ==
 
'''Today:'''
any report?
 
'''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
starting to get particle and tracer data issues from users
 
particle data isn't working
== CTH tracer data ==
one dataset is 200 gig in size
Alan working


== VISIT bridge/data files ==
== VISIT bridge/data files ==
works, but issues with updates on silo
(not paraview)
silo is file format that visit reads, sort of separate library


== Statistics Package ==
== Statistics Package, min/max ==


work in parallel
select data filter
select data filter
complext filter interface
complex filter interface
 
touches lots of things, not in 3.10, hoepfully in 3.10.1


== PRISM ==
== PRISM ==


== ParaView + ADIOS ==
== ParaView 3.10 Release ==
 
'''Today:'''
 
'''Previously:'''
 
modifying reader so that it can suck data through staging?
jaguar issues?
oakridge booth?
demo at supercomputing?


adios is in mainstream paraview--young project
waiting for hdf5 to move over vtk
 
moving of whole directory
== ParaView 3.8.1 Release ==
selection bug (selection points)
 
mesa issue
'''Today'''
(alan, jeff)
any machines with problems?


== Documenting Plugins ==
== Documenting Plugins ==
Line 118: Line 100:
Lisa is going to create a bug-tracker like functionality for the Kitware books.
Lisa is going to create a bug-tracker like functionality for the Kitware books.


== Transition to git ==
== Transition to git, branchy workflow, topics, masternext ==


'''Previously:'''
'''Previously:'''


Branchy workflow.  Tie in to stronger dashboard.
Branchy workflow.  Tie in to stronger dashboard.
dashboard greenness!
maintainers?  slowdown in development?
Berk
data in paraview/baseline paraview
== ParaView + ADIOS ==
'''Today:'''
'''Previously:'''
adios is in mainstream paraview--young project
== vtkArray ==
shallow copy vs. deep copy
design doc on paraview's developer wiki

Latest revision as of 13:58, 16 December 2010

Item People Description
1 Moreland, Nathan Project Randy
2 Greg Weirs CTH Tracer data
3 Mauldin, Alan Visit bridge/data files
4 Pebay Statistics package
5 Mauldin, Weirs Prism
6 Alan, kitware ParaView 3.10 Release
7 Mauldin ParaView roadmap?
8 Moreland Warning when ProcessRequests modifies itself
9 Moreland Book omissions and errata
10 Moreland Stronger Dashboard
11 branchy workflow
12 Geveci ParaView + ADIOS
  • Test consolidation
  • Boiling the frog coverage

Project Randy

Today:

may need help later on feature comparison table, time to go

Ken has been emailing a proposal around. Help, support needed?

Nathan: in situ on which multicores? In situ project on vtksnl?

Alan: zia app stuff done? was run on ciello unclassified, passed;

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

Can we distribute PHASTA with coprocessing adapter?

Previously:

CTH tracer data

starting to get particle and tracer data issues from users particle data isn't working one dataset is 200 gig in size Alan working

VISIT bridge/data files

works, but issues with updates on silo (not paraview) silo is file format that visit reads, sort of separate library

Statistics Package, min/max

work in parallel select data filter complex filter interface

touches lots of things, not in 3.10, hoepfully in 3.10.1

PRISM

ParaView 3.10 Release

waiting for hdf5 to move over vtk moving of whole directory selection bug (selection points) mesa issue (alan, jeff)

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, branchy workflow, topics, masternext

Previously:

Branchy workflow. Tie in to stronger dashboard.

dashboard greenness!

maintainers? slowdown in development?

Berk

data in paraview/baseline paraview

ParaView + ADIOS

Today:

Previously:

adios is in mainstream paraview--young project

vtkArray

shallow copy vs. deep copy design doc on paraview's developer wiki

Retrieved from "http://www.paraview.org/ParaView/index.php?title=ParaView_3_Telecon_12-16-2010&oldid=7020"