ParaView 3 Telecon 04/24/2007: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 7: Line 7:
| 1 || Moreland || Summit/celebration
| 1 || Moreland || Summit/celebration
|-
|-
| 2 || Shead || [http://www.paraview.org/Bug/bug.php?op=show&bugid=4722&pos=3 Programmable filter parameterization]
| 2 || Geveci || ParaView 3.0.0 binaries
|-
|-
| 3 || Karelitz || Python scripting @ Sandia
| 3 || Shead || [http://www.paraview.org/Bug/bug.php?op=show&bugid=4722&pos=3 Programmable filter parameterization]
|-
|-
| 4 || All || [http://www.paraview.org/Bug/query.php?status%5B%5D=1&status%5B%5D=2&status%5B%5D=3&status%5B%5D=4&priority%5B%5D=4&priority%5B%5D=5&emailsearch1=email&email1=&emailtype1=like&emailfield1%5B%5D=owner&title=&title_type=like&description=&description_type=like&url=&url_type=like&start_date=&end_date=&closed_start_date=&closed_end_date=&projects=14&versions=&closedinversion=&tobeclosedinversion=&components=&op=doquery&savedqueryoverride=0&order=bug_id&sort=asc&savedqueryname= Open level 4 bugs]
| 4 || Karelitz || Python scripting @ Sandia
|-
|-
| 5 || Moreland || [http://www.paraview.org/Bug/query.php?status%5B%5D=5&emailsearch1=email&email1=&emailtype1=like&emailfield1%5B%5D=owner&title=&title_type=like&description=&description_type=like&url=&url_type=like&start_date=&end_date=&closed_start_date=&closed_end_date=&projects=14&versions=&closedinversion=&tobeclosedinversion=&components=&op=doquery&savedqueryoverride=0&order=severity.sort_order&sort=asc&op=doquery Resolved bugs]
| 5 || All || [http://www.paraview.org/Bug/query.php?status%5B%5D=1&status%5B%5D=2&status%5B%5D=3&status%5B%5D=4&priority%5B%5D=4&priority%5B%5D=5&emailsearch1=email&email1=&emailtype1=like&emailfield1%5B%5D=owner&title=&title_type=like&description=&description_type=like&url=&url_type=like&start_date=&end_date=&closed_start_date=&closed_end_date=&projects=14&versions=&closedinversion=&tobeclosedinversion=&components=&op=doquery&savedqueryoverride=0&order=bug_id&sort=asc&savedqueryname= Open level 4 bugs]
|-
| 6 || Moreland || [[ParaView 3.2 Deliverables]]
|}
|}
== Summit/celebration ==
Summit is now set for June 4-5.  This is now set in stone.
== ParaView 3.0.0 Binaries ==
Binaries are made.  They are all uploaded to the usual place.  The announcement and web page links are forthcomming (probably this week).
== Programmable filter parameterization ==
V&V customer's main use case to iterate over hundereds of runs.  Have a python script that is populating programmable filters with other python scripts.  Need a way to parameterize the programmable filters from the pvpython script that is setting up the filters.
The best solution is probably to define a string vector property on the programable filter that push variable/value pairs to a SetParameter type method in the filter.  Berk will send an example to Tim.  I am reducing the priority to 3 so that we do not have to address this on the 3.0 branch.

Latest revision as of 12:18, 24 April 2007

Item People Description
1 Moreland Summit/celebration
2 Geveci ParaView 3.0.0 binaries
3 Shead Programmable filter parameterization
4 Karelitz Python scripting @ Sandia
5 All Open level 4 bugs
6 Moreland ParaView 3.2 Deliverables

Summit/celebration

Summit is now set for June 4-5. This is now set in stone.

ParaView 3.0.0 Binaries

Binaries are made. They are all uploaded to the usual place. The announcement and web page links are forthcomming (probably this week).

Programmable filter parameterization

V&V customer's main use case to iterate over hundereds of runs. Have a python script that is populating programmable filters with other python scripts. Need a way to parameterize the programmable filters from the pvpython script that is setting up the filters.

The best solution is probably to define a string vector property on the programable filter that push variable/value pairs to a SetParameter type method in the filter. Berk will send an example to Tim. I am reducing the priority to 3 so that we do not have to address this on the 3.0 branch.