Difference between revisions of "Category:Use-Cases-and-Stories"

From Epos WiKi
Jump to: navigation, search
(Created page with "Short introduction")
 
Line 1: Line 1:
Short introduction
+
Use cases and user stories introduction.....
 +
 
 +
 
 +
== '''SIMPLE USER STORY FOR GUI''' ==
 +
 
 +
By a simple user story we are talking about Research Scientist (RS) who is searching for one specific type of data and want to visualize it and download either the whole dataset or just part of it.
 +
Story description
 +
As an example we have chosen seismologist (as RS) searching for earthquakes in a specific area (bounding box) and in specific time period. Once the earthquake catalogue (list of earthquakes with other specific parameters) is chosen (there could be more RI/agencies providing regionally overlapping catalogues) the RS wants to do some filtering of earthquakes:
 +
 +
o select earthquakes only (i.e. not explosions)
 +
o select events larger than a specific magnitude threshold (e.g. M>3)
 +
o select only those which have been recorded by at least 5 stations within 150 km distance (all stations must be within that range)
 +
For this selection the RS wants to
 +
 +
o visualize the cataloque in a map
 +
o save the map view as a figure for publication - e.g. PNG, PDF, SVG, PS
 +
o download the complete earthquake catalogue (locations, phase readings, MT solutions, ...) in QuakeML format
 +
o download waveforms starting 2 minutes before origin time (time of earthquake) and ending 10 minutes after that time
 +
 
 +
Expected discovery - basic sequences and needed steps (user view)
 +
LOG IN
 +
1.  <Research Scientist> logs into EPOS-ICS portal and navigates to the search interface. (After successful login is redirected to EPOS Discovery page. The map can show the RI in EPOS as a default view.)
 +
SEARCH
 +
Task: Find the proper earthquake catalogue / DDSS element by browsing and searching. Further analysis of data is performed later from the workspace.
 +
2.1 <RS> searches for "earthquake catalogue" using the free text search box.
 +
 +
o result is list of DDSS elements organized in a list or grid (similar to GeoNetwork prototype). A map is shown aside with all bounding boxes (polygones) of shown DDSS elements - DDSS element is highlighted in the map when selected.
 +
2.2 <RS> uses the faceted search to narrow down the list of DDSS elements by choosing specific RI / agency (or other category/criteria)
 +
2.3 <RS> selects the EQ catalogue from list/grid and adds it to its own workspace/basket
 +
The individual elements (RIs, DDSSs) can be added to personal workspace/basket at any level of the search. User can also explore details of individual element at any time. User can also navigate further using the "full connectivity" of CERIF.
 +
 
 +
VISUALISATION
 +
Task: Visualize the item(s) from the workspace
 +
3.1 <RS> navigates to its workspace (Q: Workspace as a new tab?)
 +
3.2 The earthquake catalogue (DDSS element) allows several actions (buttons) which are specific for this element, e.g.
 +
 +
o Download EQ catalogue (in QuakeML format)
 +
o Analyze EQ catalogue (= visualize + filter data)
 +
o Download waveforms
 +
o etc. 
 +
3.3 The "Analyze" tool allows visualizing EQs in map with filtering options (panel on left side of the window) for dedicated parameters (magnitude, depth, bounding box coordinates, time interval, minimum number of stations, etc.  - basically all information which is in the EQ catalogue
 +
3.3.1 There is a map interface allowing interactive selection of EQs by a bounding box
 +
3.3.2 Earthquakes are plotted as points and their size corresponds to magnitude, color corresponds to depth or time (optional)
 +
3.3.3 Other additional tools for checking the catalogue are present, e.g. completeness check, magnitude-frequency distribution, etc. (as a new window ?)
 +
3.3.4 Filtered catalogue (i.e. selected part of the "earthquake catalogue") can be saved to workspace as a new EQ catalogue for later processing.
 +
3.3.5 All derived results can be saved in RS's workspace (i.e. not published back into CERIF)
 +
DOWNLOAD
 +
4.1 <RS> goes back to workspace and requests
 +
4.1.1 download of earthquake catalogue as QuakeML
 +
4.1.2 extracts of waveforms using the self-defined time window (2 min before origin time and 10 minutes after that) - the extraction is separated from download because the extracts could be saved in the workspace for later use
 +
4.1.3 download of waveforms in MSEED format and station configurations as StationXML (this may require an independent service related to download of waveform data)
 +
4.4 <RS> gets some feedback on the time required to process the request and download the data (as large amount of waveform data will take time) and approves the execution.
 +
4.5 The sytem then starts downloading and delivers data in the standard formats (i.e. MSEED, StationXML and QuakeML).
 +
 
 +
Appendix
 +
Task 2.1: Search for "earthquake catalogue" using the free text search box.
 +
Q1: How detailed metadata will be used for this search (what level of details)?
 +
Q2.1: How the search will be performed if an additional string as geolocation will be added to the search (e.g. Norway)? Should we expose/return whatever is available in the CERIF metadata catalogue with links to "Norway"? (SCB feedback on this in Madrid - expecting to do such search)
 +
Q2.2: How to treat the search for "Norway"? (either as a research infrastructure location or geocoded position of a bounding box or both?)
 +
 +
Task 2.3: Select the EQ catalogue from list/grid and adds it to its own workspace/basket
 +
Q2.3.1: What will be the basic description of the DDSS elements? How the record will look like? Color coding by category?
 +
 
 +
Task 3.2: Download of waveforms
 +
Q3.2.1: The waveforms are obviously not in the EQ catalogue but another service (FDSN via EIDA) can be simply connected to extract waveforms for stations present in the EQ cataloque. This is just a comment on what we should keep in mind when developing the GUI that other DDSS elements can be connected to the selected DDSS element.
 +
 +
 
 +
 
 +
== '''COMPLEX USER STORY FOR GUI''' ==
 +
 
 +
By a complex user story we are talking about Research Scientist (RS) who is searching for multiple types of data and want to visualize them together, compare similar data types, do its own analysis (do programming) and save the results for later use. Download either the whole dataset or just parts of it. A presentation of results/conclusions should be also part of the system.   
 +
At the same time we want to activate all the architecture elements in this complex use case.
 +
Example
 +
Event: A strong earthquake hit southern Italy near the Vesuvius volcano. As a scientist I want to get different datasets, display them and compare. I want to select subset of data that shows some specific trend and perform analysis on that subset. After that I want to use the results in another context and prepare figures for publication or web presentation. 
 +
Initial hypothesis: There may be relations between large EQs affecting the local stress conditions and magma chamber underneath the volcano. Changes in stress can trigger volcanic activity.
 +
Aims: Investigate possible relations between different data types, analyse such relations (statistical significance). Verify or reject the initial hypothesis and possibly come with new suggestions/conclusions. 
 +
A. Discovery / search for relevant trends / correlations
 +
1. Get overview - show me: (visual / spatio-temporal relations in maps)
 +
1.1 Historical seismicity in that area (map within a bounding box) - earthquake catalogue (interactive map; filtering of events)
 +
EXAMPLES: http://www.emsc-csem.org/Earthquake/?filter=yes
 +
https://earthquake.usgs.gov/earthquakes/search/
 +
WEBSERVICE: http://www.seismicportal.eu/fdsn-wsevent.html
 +
1.2 Mapped faults + geology (map, WMS)
 +
EXAMPLE: http://geo.ngu.no/kart/berggrunn/ (exists as WMS as well)
 +
1.3 Previous volcanic activity (interactive map)
 +
EXAMPLE: http://icelandicvolcanoes.is/
 +
1.4 GNSS velocity field (map)
 +
1.5 Plot those datasets (maps) together or in different pairs
 +
 +
o seismicity and distribution of lava flows
 +
o seismicity and faults
 +
o GNSS velocity map and faults
 +
including various subsets of data (e.g. specific volcanic eruption in a given time and space and the associated seismicity in the same space and time window).
 +
1.6 Save selected search results into my workspace
 +
2. Investigate possible indicators of geodynamic activity (map and graphic visualisation of parametric data)
 +
2.1 Show positions of all measuring stations in map (interactive map) - those can be GPS/GNSS stations, seismic stations, monitored boreholes, dilatometers in field, water level gauges, etc.
 +
2.2 Allow filtering for specific data types as mentioned above (using faceted search) (add selected stations to a basket/workspace for later processing)
 +
    2.2.1 In-situ stress measurements (time series)
 +
    2.2.2 Water level in surrounding boreholes (time series)
 +
    2.2.3 Real time GPS/GNSS (time series)
 +
    2.2.4 Amount of CO2 production in boreholes near volcano (time series)
 +
2.2.5 Compare all time series in time-aligned plots and save figure.
 +
2.3 Plot various combinations of subsets of data and do an agnostic data discovery, e.g. "Does CO2 production correlates with seismicity?" (this analysis can involve ICS-D for visualization and trend analysis)
 +
2.4 Add selected datasets to my workspace
 +
3. Download data or their subsets
 +
3.1 Make a request (e.g. specify time window for waveform extraction)
 +
3.2 The user will get response from the system on execution time for preparation of data
 +
3.2 Confirm and download
 +
 +
B. Analysis
 +
Using the selected subsets of data from various resources
 +
4. Analyse the earthquake
 +
4.1 Plot waveforms and check automatic phase onsets (process online; data download, catalogue record download)
 +
EXAMPLE: https://quakelink.gempa.de/gaps/
 +
4.2 Do corrections of phase onsets (plot waveforms)
 +
4.3 Relocate earthquake (using different velocity models - 1D, 3D), magnitude estimate
 +
4.3 MT inversion
 +
4.3.1 Compare MT solution with historical MTs of EQs in that area
 +
4.4 Do processing in any software (domestic or external) - ICS-D (HPC)
 +
4.5 Analyse static stress transfer -> see if additional stress in magma chamber is significant (?)
 +
5. Analyse co-seismic processes
 +
5.1 Show InSAR images (map)
 +
5.2 Show static displacement from GNSS after the earthquake (map)
 +
5.3 Slip inversion - ICS-D (CES, modelling)
 +
Compare, save figure.
 +
C. Results and presentation of output from analysis for decisions
 +
6. Interactive check points for validation of the hypothesis (i.e. summarise results from points 2, 4 and 5)
 +
6.1 From point 2: "Is there any statistically significant correlation between any observations?"
 +
6.2 From point 4:
 +
6.2.1 "Is the volumetric (or non-DC) part of the moment tensor significant? Can it be related to magma intrusion?"
 +
6.2.2 "Could be the additional stress caused by EQ in magma chamber significant?"
 +
 +
6.3 From point 5:
 +
6.3.1 "Does the InSAR data show any movement (inflation/subsidence)?"
 +
6.3.2 "Does the static displacement from GNSS data show any movement (inflation/subsidence)?"
 +
6.3.3 "What is the slip distribution along the fault plane?"
 +
D. Display and download results / conclusions / interpretations
 +
7. Presenting the results for various end users (using specific web templates)
 +
• for my own research publication
 +
• for another research group
 +
• for external use by different stake holders (e.g. public / governmental / emergency services / industry)
 +
 +
Some implications for GUI
 +
1. Individual DDSS elements should have specific dedicated tools which allows their discovery / exploration (e.g. earthquake catalogue - map, filters allowing sorting/selecting by various catalogue parameters, 2D plots for statistical evaluation - various standardised tools)
 +
o Ask WP IT Contacts (or DDSS IT Contacts) for standard tools commonly used within TCS associated to individual DDSS elements
 +
2. How to combine similar type of DDSS elements and visualize them together (map overlay, aligned 2D plots, aligned time series)? What tools do we have (table below)?
 +
3. To plot earthquake locations in map directly in discovery mode would require storage of EQ catalogue values at ICS level to avoid delays by requesting data via API to TCS level. How and where to store the data?
 +
4. How the workspace/basket will be organized? Suggestions? Examples on web?
 +
5. To set up a workflow for specific processing will require programmatic skills and tools allowing it. What tools do we know?
 +
1. Jupyter tool which in connection with Enlighten (developed by CMR, Norway) can provide intuitive data exploration
 +
2. (add more)
 +
 +
INDIVIDUAL DATA TYPES
 +
DATA TYPE VISUALISATION WEB SERVICES TOOLS
 +
WAVEFORMS 2D plots fdsnws-dataselect, obspy.fdsn
 +
obsPy
 +
 
 +
MAP map WMS, WFS, ... GIS, GeoNetwork
 +
3D MODEL slices of 3D model, 3D visualization EMC (slices)
 +
IRIS EMC, IRIS EMC 3D Visualizer
 +
 
 +
MATERIAL PROPERTIES 2D plots ? GoogleCharts, Plotly
 +
BOREHOLE 2D plots ? ?
 +
TIME SERIES GoogleCharts, Plotly
 +
?

Revision as of 12:02, 27 January 2017

Use cases and user stories introduction.....


SIMPLE USER STORY FOR GUI

By a simple user story we are talking about Research Scientist (RS) who is searching for one specific type of data and want to visualize it and download either the whole dataset or just part of it. Story description As an example we have chosen seismologist (as RS) searching for earthquakes in a specific area (bounding box) and in specific time period. Once the earthquake catalogue (list of earthquakes with other specific parameters) is chosen (there could be more RI/agencies providing regionally overlapping catalogues) the RS wants to do some filtering of earthquakes: • o select earthquakes only (i.e. not explosions) o select events larger than a specific magnitude threshold (e.g. M>3) o select only those which have been recorded by at least 5 stations within 150 km distance (all stations must be within that range) For this selection the RS wants to • o visualize the cataloque in a map o save the map view as a figure for publication - e.g. PNG, PDF, SVG, PS o download the complete earthquake catalogue (locations, phase readings, MT solutions, ...) in QuakeML format o download waveforms starting 2 minutes before origin time (time of earthquake) and ending 10 minutes after that time

Expected discovery - basic sequences and needed steps (user view)

LOG IN

1. <Research Scientist> logs into EPOS-ICS portal and navigates to the search interface. (After successful login is redirected to EPOS Discovery page. The map can show the RI in EPOS as a default view.) SEARCH Task: Find the proper earthquake catalogue / DDSS element by browsing and searching. Further analysis of data is performed later from the workspace. 2.1 <RS> searches for "earthquake catalogue" using the free text search box. • o result is list of DDSS elements organized in a list or grid (similar to GeoNetwork prototype). A map is shown aside with all bounding boxes (polygones) of shown DDSS elements - DDSS element is highlighted in the map when selected. 2.2 <RS> uses the faceted search to narrow down the list of DDSS elements by choosing specific RI / agency (or other category/criteria) 2.3 <RS> selects the EQ catalogue from list/grid and adds it to its own workspace/basket The individual elements (RIs, DDSSs) can be added to personal workspace/basket at any level of the search. User can also explore details of individual element at any time. User can also navigate further using the "full connectivity" of CERIF.

VISUALISATION Task: Visualize the item(s) from the workspace 3.1 <RS> navigates to its workspace (Q: Workspace as a new tab?) 3.2 The earthquake catalogue (DDSS element) allows several actions (buttons) which are specific for this element, e.g. • o Download EQ catalogue (in QuakeML format) o Analyze EQ catalogue (= visualize + filter data) o Download waveforms o etc. 3.3 The "Analyze" tool allows visualizing EQs in map with filtering options (panel on left side of the window) for dedicated parameters (magnitude, depth, bounding box coordinates, time interval, minimum number of stations, etc. - basically all information which is in the EQ catalogue 3.3.1 There is a map interface allowing interactive selection of EQs by a bounding box 3.3.2 Earthquakes are plotted as points and their size corresponds to magnitude, color corresponds to depth or time (optional) 3.3.3 Other additional tools for checking the catalogue are present, e.g. completeness check, magnitude-frequency distribution, etc. (as a new window ?) 3.3.4 Filtered catalogue (i.e. selected part of the "earthquake catalogue") can be saved to workspace as a new EQ catalogue for later processing. 3.3.5 All derived results can be saved in RS's workspace (i.e. not published back into CERIF) DOWNLOAD 4.1 <RS> goes back to workspace and requests 4.1.1 download of earthquake catalogue as QuakeML 4.1.2 extracts of waveforms using the self-defined time window (2 min before origin time and 10 minutes after that) - the extraction is separated from download because the extracts could be saved in the workspace for later use 4.1.3 download of waveforms in MSEED format and station configurations as StationXML (this may require an independent service related to download of waveform data) 4.4 <RS> gets some feedback on the time required to process the request and download the data (as large amount of waveform data will take time) and approves the execution. 4.5 The sytem then starts downloading and delivers data in the standard formats (i.e. MSEED, StationXML and QuakeML).

Appendix Task 2.1: Search for "earthquake catalogue" using the free text search box. Q1: How detailed metadata will be used for this search (what level of details)?

Q2.1: How the search will be performed if an additional string as geolocation will be added to the search (e.g. Norway)? Should we expose/return whatever is available in the CERIF metadata catalogue with links to "Norway"? (SCB feedback on this in Madrid - expecting to do such search)

Q2.2: How to treat the search for "Norway"? (either as a research infrastructure location or geocoded position of a bounding box or both?)

Task 2.3: Select the EQ catalogue from list/grid and adds it to its own workspace/basket

Q2.3.1: What will be the basic description of the DDSS elements? How the record will look like? Color coding by category?

Task 3.2: Download of waveforms Q3.2.1: The waveforms are obviously not in the EQ catalogue but another service (FDSN via EIDA) can be simply connected to extract waveforms for stations present in the EQ cataloque. This is just a comment on what we should keep in mind when developing the GUI that other DDSS elements can be connected to the selected DDSS element.


COMPLEX USER STORY FOR GUI

By a complex user story we are talking about Research Scientist (RS) who is searching for multiple types of data and want to visualize them together, compare similar data types, do its own analysis (do programming) and save the results for later use. Download either the whole dataset or just parts of it. A presentation of results/conclusions should be also part of the system. At the same time we want to activate all the architecture elements in this complex use case. Example Event: A strong earthquake hit southern Italy near the Vesuvius volcano. As a scientist I want to get different datasets, display them and compare. I want to select subset of data that shows some specific trend and perform analysis on that subset. After that I want to use the results in another context and prepare figures for publication or web presentation. Initial hypothesis: There may be relations between large EQs affecting the local stress conditions and magma chamber underneath the volcano. Changes in stress can trigger volcanic activity. Aims: Investigate possible relations between different data types, analyse such relations (statistical significance). Verify or reject the initial hypothesis and possibly come with new suggestions/conclusions. A. Discovery / search for relevant trends / correlations 1. Get overview - show me: (visual / spatio-temporal relations in maps) 1.1 Historical seismicity in that area (map within a bounding box) - earthquake catalogue (interactive map; filtering of events) EXAMPLES: http://www.emsc-csem.org/Earthquake/?filter=yes https://earthquake.usgs.gov/earthquakes/search/ WEBSERVICE: http://www.seismicportal.eu/fdsn-wsevent.html 1.2 Mapped faults + geology (map, WMS) EXAMPLE: http://geo.ngu.no/kart/berggrunn/ (exists as WMS as well) 1.3 Previous volcanic activity (interactive map) EXAMPLE: http://icelandicvolcanoes.is/ 1.4 GNSS velocity field (map) 1.5 Plot those datasets (maps) together or in different pairs • o seismicity and distribution of lava flows o seismicity and faults o GNSS velocity map and faults

including various subsets of data (e.g. specific volcanic eruption in a given time and space and the associated seismicity in the same space and time window).

1.6 Save selected search results into my workspace 2. Investigate possible indicators of geodynamic activity (map and graphic visualisation of parametric data) 2.1 Show positions of all measuring stations in map (interactive map) - those can be GPS/GNSS stations, seismic stations, monitored boreholes, dilatometers in field, water level gauges, etc.

2.2 Allow filtering for specific data types as mentioned above (using faceted search) (add selected stations to a basket/workspace for later processing)
   2.2.1 In-situ stress measurements (time series)
   2.2.2 Water level in surrounding boreholes (time series)
   2.2.3 Real time GPS/GNSS (time series)
   2.2.4 Amount of CO2 production in boreholes near volcano (time series)
2.2.5 Compare all time series in time-aligned plots and save figure. 

2.3 Plot various combinations of subsets of data and do an agnostic data discovery, e.g. "Does CO2 production correlates with seismicity?" (this analysis can involve ICS-D for visualization and trend analysis) 2.4 Add selected datasets to my workspace 3. Download data or their subsets 3.1 Make a request (e.g. specify time window for waveform extraction) 3.2 The user will get response from the system on execution time for preparation of data 3.2 Confirm and download

B. Analysis Using the selected subsets of data from various resources 4. Analyse the earthquake 4.1 Plot waveforms and check automatic phase onsets (process online; data download, catalogue record download)

EXAMPLE: https://quakelink.gempa.de/gaps/

4.2 Do corrections of phase onsets (plot waveforms) 4.3 Relocate earthquake (using different velocity models - 1D, 3D), magnitude estimate 4.3 MT inversion 4.3.1 Compare MT solution with historical MTs of EQs in that area 4.4 Do processing in any software (domestic or external) - ICS-D (HPC) 4.5 Analyse static stress transfer -> see if additional stress in magma chamber is significant (?) 5. Analyse co-seismic processes 5.1 Show InSAR images (map) 5.2 Show static displacement from GNSS after the earthquake (map) 5.3 Slip inversion - ICS-D (CES, modelling) Compare, save figure. C. Results and presentation of output from analysis for decisions 6. Interactive check points for validation of the hypothesis (i.e. summarise results from points 2, 4 and 5) 6.1 From point 2: "Is there any statistically significant correlation between any observations?" 6.2 From point 4: 6.2.1 "Is the volumetric (or non-DC) part of the moment tensor significant? Can it be related to magma intrusion?" 6.2.2 "Could be the additional stress caused by EQ in magma chamber significant?"

6.3 From point 5: 6.3.1 "Does the InSAR data show any movement (inflation/subsidence)?" 6.3.2 "Does the static displacement from GNSS data show any movement (inflation/subsidence)?" 6.3.3 "What is the slip distribution along the fault plane?" D. Display and download results / conclusions / interpretations 7. Presenting the results for various end users (using specific web templates) • for my own research publication • for another research group • for external use by different stake holders (e.g. public / governmental / emergency services / industry)

Some implications for GUI 1. Individual DDSS elements should have specific dedicated tools which allows their discovery / exploration (e.g. earthquake catalogue - map, filters allowing sorting/selecting by various catalogue parameters, 2D plots for statistical evaluation - various standardised tools) o Ask WP IT Contacts (or DDSS IT Contacts) for standard tools commonly used within TCS associated to individual DDSS elements 2. How to combine similar type of DDSS elements and visualize them together (map overlay, aligned 2D plots, aligned time series)? What tools do we have (table below)? 3. To plot earthquake locations in map directly in discovery mode would require storage of EQ catalogue values at ICS level to avoid delays by requesting data via API to TCS level. How and where to store the data? 4. How the workspace/basket will be organized? Suggestions? Examples on web? 5. To set up a workflow for specific processing will require programmatic skills and tools allowing it. What tools do we know? 1. Jupyter tool which in connection with Enlighten (developed by CMR, Norway) can provide intuitive data exploration 2. (add more)

INDIVIDUAL DATA TYPES DATA TYPE VISUALISATION WEB SERVICES TOOLS WAVEFORMS 2D plots fdsnws-dataselect, obspy.fdsn obsPy

MAP map WMS, WFS, ... GIS, GeoNetwork 3D MODEL slices of 3D model, 3D visualization EMC (slices) IRIS EMC, IRIS EMC 3D Visualizer

MATERIAL PROPERTIES 2D plots ? GoogleCharts, Plotly BOREHOLE 2D plots ? ? TIME SERIES GoogleCharts, Plotly

?

Pages in category "Use-Cases-and-Stories"

The following 2 pages are in this category, out of 2 total.