ParaView 3 Telecon 01/09/2007: Difference between revisions
No edit summary |
|||
| Line 29: | Line 29: | ||
== Discussion == | == Discussion == | ||
=== January Release === | |||
All binaries are created. There is a little bit of testing left, and after that there will be an email and binaries posted on the Wiki. | |||
=== Deliverables === | |||
==== Time ==== | |||
Berk is in the process of updating the Wiki to determine how we are going to handle time. | |||
==== Animation ==== | |||
Still working on the panel. There are devices for changing keyframes and properties. Should have something in a few days. | |||
==== Volume Rendering GUI ==== | |||
We are skipping that for now. We are waiting on editors from Lisa et al. | |||
==== Client Side Delivery ==== | |||
Dave D. is making a new class that will perform arbitrary parallel reduction operations and move data to the client. It will have things like min/max, sum. Berk says he will incoporate time so that you can do things like min/max over time. You could give it any vtkAlgorithm or give it a canned algorithm. | |||
==== Linking ==== | |||
Started work yesterday. Can view existing links. There is currently an issue with the proxy manager where you cannot ask how many links. Geveci gives Stimpson the go-ahead to add any missing features. | |||
==== Lookmarks/custom filters ==== | |||
Not started yet because Stanton is still working on the data analysis filter. Deadline extended until next month. | |||
=== Finding Python libraries at runtime === | |||
When we compile with python, what version does it use if you give the binary to someone else? | |||
Berk says: what we currently do is to link against the Python that is specified in your CMake. For the binaries we are distributing, so far there are no changes to include the binaries. | |||
Potential fixes: include the python libraries (easy) and include the python modules (hard). Although the latter is more difficult, it could fix problems when the user is trying to link in their own modules. | |||
The solution may be to not distribute any python libraries. Instead, we just compile against the default version of python, which should work for most users. Of those left, we can provide a python-free version that they can download. For those one or two users where that still does not work, we can either provide a custom build or hold their hand so that they can build their own. | |||
Conclusion: Kitware needs to document how to include or not include the python libraries. | |||
=== Data analysis filter === | |||
The difficulty with the data analysis filter is that it is a multi-functionality filter so that you can do lots of query operation. The output can be either a line or point. The output is shown in the 3D window in ParaView 2. In ParaView 3, it becomes problematic because you need a different view for the output based on whether the output is line or point. | |||
Berk and Ken were discussing that maybe we go back to having multiple filters. We are holding back on that because we are not sure what the original user request was. The original reason is that the data analysis filter's precursor was the probe and pick filters, which made no sense to the users. | |||
After discussing, we are thinking that we need to split the filter into several more specific filters. These filters would work closely with the selection mechanism. This requires some improvements to our selection mechanism. | |||
# Make it possible to feed selection into filters. | |||
# Make it possible to change the selection of filters and share a filter's selection with another filter. | |||
# Make a new selection mechanism that "picks." That it, it defines a point in space. | |||
# Need a new menu item that brings up a dialog box that allows the user to type in a cell id of a pipeline object. | |||
=== New Filtier Input Visibility === | |||
Ken will create a new bug request and hand it to Mark. | |||
=== Materials and Textures === | |||
The GUIs for materials and texctures should be consistent. The easiest way to load them is how ParaView 2 now loads materials. In the chooser box in the Display page, the last item is "Load File...". | |||
For now, there will be no way to unload textures or materials. There will also be no way to load them in a plugin (necessarily). | |||
Latest revision as of 14:33, 9 January 2007
| Item | People | Description |
|---|---|---|
| 1 | Moreland | Action Items |
| 2 | Geveci | January Release |
| 3 | All | ParaView 3.0 Deliverables |
| 4 | Karelitz | Finding Python libraries at runtime |
| 5 | Moreland, Richardson | Multi-input edit Bug 4114 |
| 6 | Geveci | Data Analysis Filter Redux |
| 7 | Moreland | New Filter Input Visibility |
| 8 | Stimpson | Materials |
| 9 | Geveci | Time Implementation |
| 10 | Geveci | Icons |
| 11 | Moreland | Resolved bugs |
Discussion
January Release
All binaries are created. There is a little bit of testing left, and after that there will be an email and binaries posted on the Wiki.
Deliverables
Time
Berk is in the process of updating the Wiki to determine how we are going to handle time.
Animation
Still working on the panel. There are devices for changing keyframes and properties. Should have something in a few days.
Volume Rendering GUI
We are skipping that for now. We are waiting on editors from Lisa et al.
Client Side Delivery
Dave D. is making a new class that will perform arbitrary parallel reduction operations and move data to the client. It will have things like min/max, sum. Berk says he will incoporate time so that you can do things like min/max over time. You could give it any vtkAlgorithm or give it a canned algorithm.
Linking
Started work yesterday. Can view existing links. There is currently an issue with the proxy manager where you cannot ask how many links. Geveci gives Stimpson the go-ahead to add any missing features.
Lookmarks/custom filters
Not started yet because Stanton is still working on the data analysis filter. Deadline extended until next month.
Finding Python libraries at runtime
When we compile with python, what version does it use if you give the binary to someone else?
Berk says: what we currently do is to link against the Python that is specified in your CMake. For the binaries we are distributing, so far there are no changes to include the binaries.
Potential fixes: include the python libraries (easy) and include the python modules (hard). Although the latter is more difficult, it could fix problems when the user is trying to link in their own modules.
The solution may be to not distribute any python libraries. Instead, we just compile against the default version of python, which should work for most users. Of those left, we can provide a python-free version that they can download. For those one or two users where that still does not work, we can either provide a custom build or hold their hand so that they can build their own.
Conclusion: Kitware needs to document how to include or not include the python libraries.
Data analysis filter
The difficulty with the data analysis filter is that it is a multi-functionality filter so that you can do lots of query operation. The output can be either a line or point. The output is shown in the 3D window in ParaView 2. In ParaView 3, it becomes problematic because you need a different view for the output based on whether the output is line or point.
Berk and Ken were discussing that maybe we go back to having multiple filters. We are holding back on that because we are not sure what the original user request was. The original reason is that the data analysis filter's precursor was the probe and pick filters, which made no sense to the users.
After discussing, we are thinking that we need to split the filter into several more specific filters. These filters would work closely with the selection mechanism. This requires some improvements to our selection mechanism.
- Make it possible to feed selection into filters.
- Make it possible to change the selection of filters and share a filter's selection with another filter.
- Make a new selection mechanism that "picks." That it, it defines a point in space.
- Need a new menu item that brings up a dialog box that allows the user to type in a cell id of a pipeline object.
New Filtier Input Visibility
Ken will create a new bug request and hand it to Mark.
Materials and Textures
The GUIs for materials and texctures should be consistent. The easiest way to load them is how ParaView 2 now loads materials. In the chooser box in the Display page, the last item is "Load File...".
For now, there will be no way to unload textures or materials. There will also be no way to load them in a plugin (necessarily).
