| Lines 2-5 were replaced by lines 2-5 |
| - PDR (Prelim design Review) -- May 2007 |
| - FDR (Final Design Review) -- May 2008 |
| - MRE construction, 5 years |
| - MRE operations + maintenance from there |
| + * PDR (Prelim design Review) -- May 2007 |
| + * FDR (Final Design Review) -- May 2008 |
| + * MRE construction, 5 years |
| + * MRE operations + maintenance from there |
| Line 7 was replaced by line 7 |
| - Currently focused on Single String testbed |
| + * Currently focused on Single String testbed |
| Lines 10-14 were replaced by lines 10-14 |
| - Compact RIO controller (NI) |
| - POP in SDSC (moving to James Reserve this week) |
| - -- runs ORB |
| - -- RBNB (Ring Buffered Network Bus) (Data Turbine) |
| - -- CREARE agreed to go open-source with DataTurbine |
| + * Compact RIO controller (NI) |
| + * POP in SDSC (moving to James Reserve this week) |
| + ** runs ORB |
| + ** RBNB (Ring Buffered Network Bus) (Data Turbine) |
| + *** CREARE agreed to go open-source with DataTurbine |
| Line 16 was replaced by line 16 |
| - RDFA --> RDF Annotations |
| + * RDFA --> RDF Annotations |
| At line 20 added 2 lines. |
| + * need technical use cases to drive development |
| + ** e.g., import opendap data into a kepler workflow |
| Lines 22-23 were replaced by lines 24-33 |
| - -- need technical use cases to drive development |
| - -- e.g., import opendap data into a kepler workflow |
| + # reconcile data models of kepler/opendap/eml/sensorml/other sensor models?/OGC data sources/(V)ORB/RBNB |
| + # develop opendap datasource adapter for kepler |
| + # transport: shared transport library usable by several datasource adapters |
| + # expose opendap/ODC metadata search in Kepler? |
| + # determine how to express queries (server-command language?) |
| + ** subsetting on remote servers |
| + ** aggregation on remote servers |
| + ** server side processing (how does this relate to workflow processing?) |
| + # determine how to handle authentication/authorization to opendap services |
| + # ability for opendap and others servers to self-register with a service registry |
| Removed lines 25-36 |
| - a. reconcile data models of kepler/opendap/eml/sensorml/other sensor |
| - models?/OGC data sources/(V)ORB/RBNB |
| - b. develop opendap datasource adapter for kepler |
| - c. transport: shared transport library usable by several datasource adapters |
| - d. expose opendap/ODC metadata search in Kepler? |
| - e. determine how to express queries (server-command language?) |
| - -- subsetting on remote servers |
| - -- aggregation on remote servers |
| - -- server side processing (how does this relate to workflow processing?) |
| - f. determine how to handle authentication/authorization to opendap services |
| - g. ability for opendap and others servers to self-register with a service registry |
| - |
| Line 40 was replaced by line 38 |
| - Monthly Updates -- target scientists to keep people updated |
| + * Monthly Updates -- target scientists to keep people updated |
| Lines 44-64 were replaced by lines 42-60 |
| - a) running models |
| - -- features we need |
| - -- for SST use case need ability to compare fields statistically |
| - -- advanced search capability for spatio-temporal data discovery |
| - -- adaptive models, change during course of execution |
| - -- data assimilation? e.g., the COMET examples |
| - -- hybrid models? |
| - -- yes, for 2 different physical models |
| - -- different temporal behaviors? multiscale? |
| - -- different types of modeling (e.g., IBMs, CT, |
| - stochastic/deterministic) |
| - -- checkpointing for long running models |
| - -- asynchronous execution |
| - -- detachable from GUI |
| - -- everybody in project should be able to check status of |
| - execution, e.g., from the web |
| - -- new components needed |
| - -- spatial statistics components (statistical comparison of fields) |
| - -- spatial and temporal buffering (e.g., convex hull buffer) (matchups) |
| - -- new components for GAs, simulated annealing, NN, etc. |
| - -- fix MATLAB expression actor to support data output |
| + # running models |
| + ** features we need |
| + *** for SST use case need ability to compare fields statistically |
| + *** advanced search capability for spatio-temporal data discovery |
| + *** adaptive models, change during course of execution |
| + *** data assimilation? e.g., the COMET examples |
| + *** hybrid models? |
| + **** yes, for 2 different physical models |
| + **** different temporal behaviors? multiscale? |
| + **** different types of modeling (e.g., IBMs, CT,stochastic/deterministic) |
| + *** checkpointing for long running models |
| + *** asynchronous execution |
| + **** detachable from GUI |
| + **** everybody in project should be able to check status of execution, e.g., from the web |
| + *** new components needed |
| + **** spatial statistics components (statistical comparison of fields) |
| + **** spatial and temporal buffering (e.g., convex hull buffer) (matchups) |
| + **** new components for GAs, simulated annealing, NN, etc. |
| + **** fix MATLAB expression actor to support data output |
| Lines 69-76 were replaced by lines 65-71 |
| - 1. many people or many workshops? |
| - 2. eco + oceans workshops separate? |
| - 3. Workshop in late June or July in Santa Barbara |
| - 4. Conference call to be scheduled to plan with eco people |
| - 5. Peter C. to possibly present mockup at GHSST meeting in Melbourne in May to start getting people involved |
| - 6. Mark S. to plan ws and get rooms, hotels, etc. |
| - 7. Action item: develop wf mockups to show current and |
| - candidate features and components |
| + # many people or many workshops? |
| + # eco + oceans workshops separate? |
| + # Workshop in late June or July in Santa Barbara |
| + # Conference call to be scheduled to plan with eco people |
| + # Peter C. to possibly present mockup at GHSST meeting in Melbourne in May to start getting people involved |
| + # Mark S. to plan ws and get rooms, hotels, etc. |
| + # Action item: develop wf mockups to show current and candidate features and components |
