| Line 1 was replaced by line 1 |
| - ===REAP VTC=== |
| + ===REAP VTC===\\ |
| Line 5 was replaced by line 5 |
| - ==Participants== |
| + ==Participants==\\ |
| Lines 7-8 were replaced by line 7 |
| - Matt Jones, Derik Barseghian, Aaron Schultz, Jianwu Wang, Dan Crawl, James Gallagher, Bertram Ludaescher, Shawn Bowers, |
| - Mark Schildhauer, Parviez Hosseini |
| + Matt Jones, Derik Barseghian, Aaron Schultz, Jianwu Wang, Dan Crawl, James Gallagher, Bertram Ludaescher, Shawn Bowers,Mark Schildhauer, Parviez Hosseini |
| Line 11 was replaced by line 10 |
| - ==Agenda and Notes== |
| + ==Agenda and Notes==\\ |
| Lines 13-17 were replaced by lines 12-17 |
| - convert provenance API into the UCD format for the provenance browser |
| - focus on what is recorded to make it more generic |
| - want to keep aligning provenance tools in Kepler |
| - want to add some stuff to the reporting subsystem |
| - two master's students will working on Data Turbine -- one will switch off, other (Supria) looking at DT + OpenDAP |
| + * convert provenance API into the UCD format for the provenance browser |
| + * focus on what is recorded to make it more generic |
| + * want to keep aligning provenance tools in Kepler |
| + * want to add some stuff to the reporting subsystem |
| + * two master's students will working on Data Turbine -- one will switch off, other (Supria) looking at DT + OpenDAP |
| + |
| Lines 19-22 were replaced by lines 19-22 |
| - Derik -- overall coordination + UCSB |
| - James for OpeNDAP |
| - Bertram for UCD |
| - Ilkay for UCSD |
| + * Derik -- overall coordination + UCSB |
| + * James for OpeNDAP |
| + * Bertram for UCD |
| + * Ilkay for UCSD |
| Lines 27-38 were replaced by lines 27-38 |
| - -- Daniel and Derik available to work on this |
| - -- bertram has 'process manager' concept partly implemented |
| - -- should have a larger or more general proxy architecture |
| - -- need to think through design of how remote systems are being reflected in Kepler |
| - -- should do survey of domains in ptolemy to find the ones most related to the engineering view |
| - -- e.g., wireless domain |
| - -- end product is model of deployment to see where there are points of failure |
| - -- derik will need to estimate time to complete run manager coding effort |
| - -- start with articulation of use case and problems to be solved |
| - -- how far can we push DT into the sensor stack? |
| - -- Derik back to McLaughlin |
| - -- equipment budget for working locally |
| + * Daniel and Derik available to work on this |
| + * Bertram has 'process manager' concept partly implemented |
| + * should have a larger or more general proxy architecture |
| + * need to think through design of how remote systems are being reflected in Kepler |
| + * should do survey of domains in ptolemy to find the ones most related to the engineering view |
| + ** e.g., wireless domain |
| + * end product is model of deployment to see where there are points of failure |
| + * Derik will need to estimate time to complete run manager coding effort |
| + * start with articulation of use case and problems to be solved |
| + * how far can we push DT into the sensor stack? |
| + * Derik back to McLaughlin |
| + * equipment budget for working locally |
