ParaQ:Telecon 04/18/2006 1PM EST: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 36: | Line 36: | ||
=Notes= | =Notes= | ||
==Prism over ParaQ== | |||
Prism will use the following two features: | |||
*Compound filters. | |||
*PGraph | |||
Both of these need to work before Prism will work. | |||
==Process Discussion== | |||
*For the monthy release, do not branch. Instead, just tag the release. Any fixes will become bug reports and simply fixed in the next montly release. | |||
*Need some sort of versioning to demark which release. | |||
**Should be some sort of date affixed to the version number. This can be retrieved from vtkVersion, which is updated nightly. | |||
==PGraph== | ==PGraph== | ||
| Line 45: | Line 60: | ||
==ParaQ interm release support== | ==ParaQ interm release support== | ||
* Alan: build on SCICO, | * Currently building by hand on select systems. | ||
* Alan: build on SCICO, server on Rouge (but that is just ParaView server). | |||
==Mini login app planning== | ==Mini login app planning== | ||
* First deliverable: stand-alone app to nicely connect to one designated system from any client OS, start a ParaView Server and provide info for client connection. | * First deliverable: stand-alone app to nicely connect to one designated system from any client OS, start a ParaView Server and provide info for client connection. | ||
* Work to develop list of supported systems, connection requirements. | * Work to develop list (matrix?) of supported server systems, connection requirements. | ||
* Also need to start thinking about how we have the site specific builds of ParaQ. | |||
==Time Support== | |||
Both Kitware and Sandia will write up requirements documentation so that they can be compared and argued about. | |||
Dave Rogers needs to comment on when time support is to be released within ParaQ. | |||
==Track Sandia Action Items== | |||
As long as there are no sensitivity issues, let's go ahead and put them in the Kitware issue tracker. There is already a ParaQ admin catagory that is good for this. Kitware has already agreed to let us use that, and there may be some advantages to having Kitware see our needs. | |||
=Action Items= | =Action Items= | ||
* [Dave Rogers] Create requirements document for time support. | * [Dave Rogers] Create requirements document for time support. | ||
* [Kitware] Produce | * [Kitware] Produce requirements document for time support. | ||
* [Berk] Add date to version number. | |||
* [Cory] Make requirements for Prism of PGraph. | |||
* [Alan] Make list of supported server systems. | |||
* [Tim] Develop plan for site specific builds (or runtime support) automated server startup/connections. | |||
* [Alan] Attempt ParaQ server compile for red storm. | |||
Latest revision as of 12:45, 18 April 2006
Agenda
| Item | People | Description |
|---|---|---|
| 1 | Rogers | Overview of today's meeting |
| 2 | McBride | Report on Prism over ParaQ |
| 3 | Geveci | Process discussion: Tags, branches and fixing things that are broken in a monthly release. |
| 4 | Moreland | PGraph planning |
| 5 | Rogers | ParaQ interim release support |
| 6 | Rogers | Mini login app planning |
| 7 | Rogers | Discussion of Time support |
Notes
Prism over ParaQ
Prism will use the following two features:
- Compound filters.
- PGraph
Both of these need to work before Prism will work.
Process Discussion
- For the monthy release, do not branch. Instead, just tag the release. Any fixes will become bug reports and simply fixed in the next montly release.
- Need some sort of versioning to demark which release.
- Should be some sort of date affixed to the version number. This can be retrieved from vtkVersion, which is updated nightly.
PGraph
- Tim will code vtkAlgorithm stuff
- Schedule Kitware
- Delivery: June release (client side graphing)
ParaQ interm release support
- Currently building by hand on select systems.
- Alan: build on SCICO, server on Rouge (but that is just ParaView server).
Mini login app planning
- First deliverable: stand-alone app to nicely connect to one designated system from any client OS, start a ParaView Server and provide info for client connection.
- Work to develop list (matrix?) of supported server systems, connection requirements.
- Also need to start thinking about how we have the site specific builds of ParaQ.
Time Support
Both Kitware and Sandia will write up requirements documentation so that they can be compared and argued about.
Dave Rogers needs to comment on when time support is to be released within ParaQ.
Track Sandia Action Items
As long as there are no sensitivity issues, let's go ahead and put them in the Kitware issue tracker. There is already a ParaQ admin catagory that is good for this. Kitware has already agreed to let us use that, and there may be some advantages to having Kitware see our needs.
Action Items
- [Dave Rogers] Create requirements document for time support.
- [Kitware] Produce requirements document for time support.
- [Berk] Add date to version number.
- [Cory] Make requirements for Prism of PGraph.
- [Alan] Make list of supported server systems.
- [Tim] Develop plan for site specific builds (or runtime support) automated server startup/connections.
- [Alan] Attempt ParaQ server compile for red storm.
