At line 0 added 1 line. |
+ !!!Name: Importing DAP data into Kepler. |
Removed line 2 |
- !!!Name: Importing DAP data into Kepler. |
Removed line 4 |
- |
Line 7 was replaced by lines 6-10 |
- !1.0.0 Initial draft |
+ !1.0.0 Initial draft |
+ |
+ 1.0.1 Minor edits. Since were writing this after the fact, we might as well |
+ skip the future-tense. |
+ |
Lines 9-10 were replaced by line 12 |
- 1.0.1 Minor edits. Since were writing this after the fact, we might as well |
- skip the future-tense. |
+ !!Summary: |
At line 11 added 1 line. |
+ A user imports DAP data into Kepler. The data is available in the Kepler data model for further processing. |
Removed line 13 |
- !!Summary: |
Line 15 was replaced by line 17 |
- A user imports DAP data into Kepler. The data is available in the Kepler data model for further processing. |
+ !!Actors: |
At line 16 added 4 lines. |
+ * User. |
+ * Kepler software application |
+ * OPeNDAP Kepler "Actor" |
+ * A server on the web with DAP accessible data. |
Removed line 18 |
- !!Actors: |
Lines 20-23 were replaced by line 25 |
- * User. |
- * Kepler software application |
- * OPeNDAP Kepler "Actor" |
- * A server on the web with DAP accessible data. |
+ !!Preconditions: |
At line 24 added 2 lines. |
+ * User has a complete DAP data URL that accesses and subsets the data that they wish to use. |
+ * The data URL SHOULD subset array variables such that they are reduced to 1 or 2 effective (See Note 01)) dimensions. |
Removed line 26 |
- !!Preconditions: |
Lines 28-32 were replaced by line 31 |
- * User has a complete DAP data URL that accesses and subsets the data that they wish to use. |
- * The data URL SHOULD subset array variables such that they are reduced to 1 or 2 effective (See Note 01)) dimensions. |
- |
- |
- !!Triggers: |
+ !!Triggers: |
Line 35 was replaced by line 34 |
- !!Basic course of events: |
+ !!Basic course of events: |
Line 37 was replaced by line 36 |
- # The user starts the Kelper application. |
+ # The user starts the Kelper application. |
Lines 39-41 were replaced by lines 38-40 |
- # The user adds an instance of the OpendapDataSource Actor to the Workflow. |
- # The user configures the OpendapDataSource Actor by: |
- ## Right-clicking on it and selecting "Configure Actor" from the Actor's pop-up menu. This causes a window containing a form to appear. The form has two text fields. |
+ # The user adds an instance of the OpendapDataSource Actor to the Workflow. |
+ # The user configures the OpendapDataSource Actor by: |
+ ## Right-clicking on it and selecting "Configure Actor" from the Actor's pop-up menu. This causes a window containing a form to appear. The form has two text fields. |
Lines 43-44 were replaced by lines 42-43 |
- constraint expression or a DAP response suffix. |
- ## The user then enters the constraint expression (CE) that subsets the data set into the second text field. (See Note 02) The CE may be null. |
+ constraint expression or a DAP response suffix. |
+ ## The user then enters the constraint expression (CE) that subsets the data set into the second text field. (See Note 02) The CE may be null. |
Lines 46-47 were replaced by lines 45-48 |
- #The OpendapDataSource Actor reconfigures it's output terminals to reflect the variables specified in the CE. |
- |
+ #The OpendapDataSource Actor reconfigures it's output terminals to reflect the variables specified in the CE. |
+ |
+ |
+ !!Alternative Paths: |
Line 49 was replaced by line 50 |
- !!Alternative Paths: |
+ __Exisiting Workflow:__ |
Lines 51-53 were replaced by lines 52-53 |
- Exisiting Workflow: |
- 2. The user opens a Workflow stored in a file. |
- 3. Goto Step 4. (Main Path) |
+ 2. The user opens a Workflow stored in a file.\\ |
+ 3. Goto Step 4. (Main Path) |
Line 56 was replaced by line 56 |
- !!Postconditions: |
+ !!Postconditions: |
Lines 58-62 were replaced by lines 58-59 |
- 1. DAP data is available to Kepler actors by connecting to the data |
- source terminals on the configured OpendapDataSource Actor. |
- |
- 2. The User connects one or more of these data source terminals |
- to additional Kepler Actors for data processing and display. |
+ # DAP data is available to Kepler actors by connecting to the data |
+ source terminals on the configured OpendapDataSource Actor. |
At line 63 added 2 lines. |
+ #The User connects one or more of these data source terminals |
+ to additional Kepler Actors for data processing and display. |
Removed line 67 |
- !!Business Rules: |
At line 68 added 1 line. |
+ !!Business Rules: |
Removed line 71 |
- !!Notes: |
Line 73 was replaced by line 71 |
- (01) |
+ !!Notes: |
Lines 75-78 were replaced by lines 73-74 |
- Multidimensional arrays can be subset so that their "effective" |
- dimensionality is reduced by specifying (in the DAP constraint |
- expression) a single index for one or more of the array's |
- dimensions. |
+ # Multidimensional arrays can be subset so that their "effective" dimensionality is reduced by specifying (in the DAP constraint expression) a single index for one or more of the array's dimensions.\\\\ |
+ # The CE is made up of a "projection" and a "selection". The "projection" specifies which variables in the data set the user wishes to access. The "selection" is a series of clauses that specify which conditions data must meet. If the user requests array variables then they SHOULD provide a CE that subsets them in order to reduce their effective dimensions to 1 or 2. Arrays of 1 or 2 dimensions can be represented efficintly in the Kepler data model as a MatrixToken. |
Removed line 80 |
- (02) |
Lines 82-88 were replaced by line 77 |
- The CE is made up of a "projection" and a "selection". The "projection" |
- specifies which variables in the data set the user wishes to |
- access. The "selection" is a series of clauses that specify which |
- conditions data must meet. If the user requests array variables then |
- they SHOULD provide a CE that subsets them in order to reduce their |
- effective dimensions to 1 or 2. Arrays of 1 or 2 dimensions can be |
- represented efficintly in the Kepler data model as a MatrixToken. |
+ !!Author |
Lines 90-91 were replaced by line 79 |
- |
- !!Author |
+ Nathan Potter, 12/05/2007 |
Removed lines 93-95 |
- Nathan Potter, 12/05/2007 |
- |
- |