Line 3 was replaced by line 3 |
- The overall idea of this sequence is to statistically compare two or more SST data sets. The data sets are assumed to consist of 2D SST fields in time; i.e., each field is a lat, lon field, one for each instant in time, with many time steps. (This workflow compromises the colored elements of the [modified ocean use case|WorkFlowGridComparisons.pdf] shown in the proposal.) Although this workflow is designed to compare SST fields, it should work for many geo-based arrays. |
+ The overall idea of this sequence is to statistically compare two or more SST data sets. The data sets are assumed to consist of 2D SST fields in time; i.e., each field is a lat, lon field, one for each instant in time, with many time steps. (This workflow compromises the colored elements of the modified ocean use (Figure 1) shown in the proposal.) Although this workflow is designed to compare SST fields, it should work for many geo-based arrays. |
At line 4 added 3 lines. |
+ [{Image src='WorkFlowGridComparisons.png' caption='Figure 1. Functions associated with SST field comparison are indicated in color in the overall Ocean Workflow.} |
+ height=400}] |
+ |
Lines 9-10 were replaced by line 12 |
- |
- # [User Input Module|UserSelectionModule.pdf] |
+ 1) User Input Module (Figure 2 below.) |
Line 18 was replaced by lines 20-22 |
- # [Build Match-Up Data Set Module|AcquireMatchups.pdf] |
+ [{Image src='UserSelectionModule.png' caption='Figure 2. User selection module.' height=1000}] |
+ |
+ 2) Build Match-Up Data Set Module (Figure 3 below.) |
At line 39 added 1 line. |
+ [{Image src='AcquireMatchups.png' caption='Figure 3. Development of the Match-up Data base.' height=1200}] |
Line 41 was replaced by line 46 |
- # [Analysis Module|AnalysisModule.pdf] |
+ 3) Analysis Module (Figure 4 below.) |
At line 58 added 12 lines. |
+ [{Image src='AnalysisModule.png' caption='Analysis module.' height=800}] |
+ |
+ |
+ ! ACTION ITEMS AND FUTURE STEPS FROM THE SST BREAK OUT |
+ # Layman version (without technical and scientific buzwords) of the description of the goals for each step and workflow(couple of paragraphs) (April 4th; 1 week) |
+ # Peter will write up his realization of why this is useful on top of just matlab with a few bullets(April 4th; 1 week) (provenance, chaining what is available, ...) |
+ # Conceptual workflow with input/output details and placeholders for different computational components (April 9th; 2 weeks) |
+ # Design the schema ad build a relational database for the match up datasets (April 11th; 2 weeks) |
+ # Recollection of requirements and comments (April 17th; 3 weeks) |
+ # Working version0 (May 15th; 1.5 months - 4 weeks for implementation) |
+ # Definition of additional analysis steps (June 1st; 2 months) |
+ # GHRSST Meeting (June 9-13, 2008; France) presentation and demonstration (June 9th; 2 months) |