| At line 0 added 1 line. |
| + !!!Importing DAP data into Kepler: \\ Minimal User Interface |
| Removed line 2 |
| - !!!Name: Importing DAP data into Kepler. |
| Removed line 4 |
| - |
| Lines 7-10 were replaced by lines 6-8 |
| - !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. |
| + !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. |
| + !1.0.2 Imported into REAP wiki. |
| Line 13 was replaced by line 11 |
| - !!Summary: |
| + !!Summary: |
| Line 15 was replaced by line 13 |
| - A user imports DAP data into Kepler. The data is available in the Kepler data model for further processing. |
| + A user imports DAP data into Kepler. The data is available in the Kepler data model for further processing. |
| Line 18 was replaced by line 16 |
| - !!Actors: |
| + !!Actors: |
| Lines 20-23 were replaced by lines 18-21 |
| - * User. |
| - * Kepler software application |
| - * OPeNDAP Kepler "Actor" |
| - * A server on the web with DAP accessible data. |
| + * User. |
| + * Kepler software application |
| + * OPeNDAP Kepler "Actor" |
| + * A server on the web with DAP accessible data. |
| Line 26 was replaced by line 24 |
| - !!Preconditions: |
| + !!Preconditions: |
| Lines 29-32 were replaced by lines 27-28 |
| - * The data URL SHOULD subset array variables such that they are reduced to 1 or 2 effective (See Note 01)) dimensions. |
| - |
| - |
| - !!Triggers: |
| + * The data URL SHOULD subset array variables such that they are reduced to 1 or 2 effective (See Note 01)) dimensions. |
| + |
| At line 33 added 1 line. |
| + !!Triggers: |
| Removed line 35 |
| - !!Basic course of events: |
| Line 37 was replaced by lines 33-35 |
| - # The user starts the Kelper application. |
| + !!Basic course of events: |
| + |
| + # The user starts the Kelper application. |
| Lines 39-44 were replaced by lines 37-41 |
| - # 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 enters the data URL for the DAP dataset that they wish to access in the first text field. This URL must not contain the |
| - 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. |
| + # 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 enters the data URL for the DAP dataset that they wish to access in the first text field. This URL must not contain the 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 43-44 |
| - #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. |
| + |
| Line 49 was replaced by line 46 |
| - !!Alternative Paths: |
| + !!Alternative Paths: |
| Lines 51-53 were replaced by line 48 |
| - Exisiting Workflow: |
| - 2. The user opens a Workflow stored in a file. |
| - 3. Goto Step 4. (Main Path) |
| + __''Existing Workflow:''__ |
| At line 54 added 2 lines. |
| + __2__ The user opens a Workflow stored in a file.\\ |
| + __3__ Goto Step 4. (Main Path) |
| Removed line 56 |
| - !!Postconditions: |
| Lines 58-62 were replaced by line 54 |
| - 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. |
| + !!Postconditions: |
| At line 63 added 2 lines. |
| + # DAP data is available to Kepler actors by connecting to the data source terminals on the configured OpendapDataSource Actor.\\ \\ |
| + #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 66 |
| - (01) |
| + !!Notes: |
| Lines 75-78 were replaced by lines 68-69 |
| - 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 72 |
| - 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 74 |
| - |
| - !!Author |
| + Nathan Potter, 12/10/2007 |
| Removed lines 93-95 |
| - Nathan Potter, 12/05/2007 |
| - |
| - |
