ParaView 3 Telecon 02/27/2007

From ParaQ Wiki
Jump to navigationJump to search
Item People Description
1 All ParaView 3.0 Deliverables
2 Goldman User ParaView/VisIt perspective
3 Scott Exodus global variables
4 Moreland Resolved bugs

Deliverables

Plotting (Ayachit)

Been working on making x-y plots working with cell arrays as well as point arrays. Cleaning up the updates so that it refreshes only when data actually changes. Mostly optimizing the way the charts render.

Commited a CSV writer, but still needs to make a CSV reader. Need to make the color editor work with the histogram plot.

Color map (Richardson)

Tried to get the new transfer function viewer into the dialog for editing colors. That part is probably not going to make it in by the end of the month. Put back in the old Qt version of the color editor for now.

Added the ability yesterday to add and remove points. Will check that in before the end of the month. Still have the QVTKWidget transfer function editor.

Multiple outputs (Geveci)

Berk was on vacation, so he did not do much. He wrote a document that suggests all the changes that should be made to support multiple outputs.

Berk will delay doing that to help Dave work on selection stuff.

Selection (DeMarle)

Put the selection by id, point, frustum, and threshold and extract them. There are a slew of bugs to work on. After that, have to make the selection state get saved in the pipeline so that they are usable.

So, there is still lots to do.

Plugins (Stimpson/Cedilnik)

Finished ability to add reader and writer to the file dialog. Working on custom toolbars and menues.

Changed the QtChart and QtWidget plugins. They are moved into one library. Gives the ability to load UI files at runtime and instantiate these widgets.

Lookmarks (Stanton)

Eric is not here today.

New Deliverable

On line documentation. Actually, we already have this deliverable, but it failed to be put on the timeline.

User's ParaView/VisIt Perspective

One of Jon's colleagues at Argon was using ParaView (2.4) and switch to VisIt. Here are some of the issues that he had with ParaView.

  • VisIt's volume rendering worked for all the formats, whereas it only works on some in ParaView.
  • VisIt supported some file formats (FLASH and FITS) he was using that ParaView did not.
  • The ability to start the server from the GUI client was easier.
  • There is an expressions panel that you can then assign to a menu item.
    • It was easier to specify the expression. You don't have to use iHat, jHat, kHat.
    • If you loaded a second data set with the same variables, it put the same expression in the menu item.
  • There were more functions that scientists wanted on the menu bar and tool bar. ParaView seemed to require more wiring.
  • ParaView had no free documentation.
  • VisIt could create multiple view windows.
  • The ParaView releases did not tend to work as advertised whereas the VisIt releases did.

Exodus Global Variables

Exodus files have variables that are a single scalar for the mesh per time step. Users want to be able plot that over time, run them through the calculator, and access them in custom filters.

Rather than try to shove something int ParaView 3.0, we want to take some time to do this right. The consensus is to wait until after the 3.0 release and address this 3.2.

Schedule

Berk suggests that at the end of March we branch 3.0 and make it a beta. Soon after we will release a patch that will be the official release.

PV 3.2 will probably follow in the July/August timeframe.

Current time value in programmable filter

Dave wants to get the current time value in a programmable filter. Right now it's a pain because you have to parse some time value string. It should be easier. Dave will add a bug for this.

Retrieved from "http://www.paraview.org/ParaView/index.php?title=ParaView_3_Telecon_02/27/2007&oldid=4786"