CyberShake Data Request - Revision history

Maechlin at 20:30, 30 June 2013

2013-06-30T20:30:48Z

Davidgil: /* XML Document */

2013-04-26T17:03:53Z

XML Document

Davidgil: /* XML Document */

2013-04-26T17:02:43Z

XML Document

Davidgil at 17:02, 26 April 2013

2013-04-26T17:02:04Z

Davidgil at 16:53, 26 April 2013

2013-04-26T16:53:41Z

Davidgil at 22:00, 24 April 2013

2013-04-24T22:00:08Z

Davidgil: /* Use Case 3 */

2013-04-24T21:59:21Z

Use Case 3

Davidgil at 21:49, 24 April 2013

2013-04-24T21:49:33Z

Davidgil at 21:25, 24 April 2013

2013-04-24T21:25:26Z

Davidgil: /* Use Case 1 */

2013-04-24T21:25:10Z

Use Case 1

@@ Line 1: / Line 1: @@
 CyberShake Data Request Web Site is a first stage in automating CyberShake data requests. The variety of CyberShake data products is growing, so we propose to develop a web site that will help user request CyberShake data. We will use current CyberShake data requests to try out the proposed data request system. The goal of this first system is to generate a well defined data request. For now, we will continue to process the data requests manually, but will look to automating the retrieval if useful.
 == General Workflow ==
 At a SCEC URL, the user is presented with a series of choices that selects some subset of all our CyberShake data products. The user makes all the choices and presses send and the web page generates a data request specification that someone can then processes and post. The user can check on the status of their request while waiting.
@@ Line 112: / Line 113: @@
 #Administrative panel to see requests and update links for download
 #Check on status of request via web interface
 == Related Entries ==
 *[[CyberShake]]
 *[[CME Project]]

@@ Line 57: / Line 57: @@
 &nbsp;&nbsp;&nbsp;&nbsp;</product><br />
 </datarequest><br />
 == Backend Workflow ==

@@ Line 41: / Line 41: @@
 When the front-end steps are completed a XML document is generated. The format of this XML document is:
-<datarequest>
+<datarequest><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<first_name>John</first_name>
+&nbsp;&nbsp;&nbsp;&nbsp;<first_name>John</first_name><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<last_name>Doe</last_name>
+&nbsp;&nbsp;&nbsp;&nbsp;<last_name>Doe</last_name><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<email>john.doe@usc.edu</email>
+&nbsp;&nbsp;&nbsp;&nbsp;<email>john.doe@usc.edu</email><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<study>CyberShake 13.4</study>
+&nbsp;&nbsp;&nbsp;&nbsp;<study>CyberShake 13.4</study><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<map>AWP CVM-S</map>
+&nbsp;&nbsp;&nbsp;&nbsp;<map>AWP CVM-S</map><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<sites>
+&nbsp;&nbsp;&nbsp;&nbsp;<sites><br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<site>USC</site>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<site>USC</site><br />
-&nbsp;&nbsp;&nbsp;&nbsp;</sites>
+&nbsp;&nbsp;&nbsp;&nbsp;</sites><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<ruptures>none</ruptures>
+&nbsp;&nbsp;&nbsp;&nbsp;<ruptures>none</ruptures><br />
-&nbsp;&nbsp;&nbsp;&nbsp;<product>
+&nbsp;&nbsp;&nbsp;&nbsp;<product><br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<name>Hazard Curves</name>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<name>Hazard Curves</name><br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<format>log-linear</format>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<format>log-linear</format><br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;...
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;...<br />
-&nbsp;&nbsp;&nbsp;&nbsp;</product>
+&nbsp;&nbsp;&nbsp;&nbsp;</product><br />
-</datarequest>
+</datarequest><br />
 == Backend Workflow ==

← Older revision		Revision as of 17:02, 26 April 2013
Line 36:		Line 36:

	User would like to get a list of the peak amplitudes for given periods at USC from the Study 13.4 AWP CVM-H map. User can go to the site, select 13.4, AWP CVM-H, site USC, and then select the data product of peak amplitudes.		User would like to get a list of the peak amplitudes for given periods at USC from the Study 13.4 AWP CVM-H map. User can go to the site, select 13.4, AWP CVM-H, site USC, and then select the data product of peak amplitudes.
		+
		+	== XML Document ==
		+
		+	When the front-end steps are completed a XML document is generated. The format of this XML document is:
		+
		+	<datarequest>
		+	<first_name>John</first_name>
		+	<last_name>Doe</last_name>
		+	<email>john.doe@usc.edu</email>
		+	<study>CyberShake 13.4</study>
		+	<map>AWP CVM-S</map>
		+	<sites>
		+	<site>USC</site>
		+	</sites>
		+	<ruptures>none</ruptures>
		+	<product>
		+	<name>Hazard Curves</name>
		+	<format>log-linear</format>
		+	...
		+	</product>
		+	</datarequest>
		+
		+	== Backend Workflow ==
		+
		+	The backend is comprised of three components:
		+
		+	# csdrs.py
		+	# requestprocessor.py
		+	# Separate Python scripts for each data product (e.g. map.py, peakamps.py, etc.)
		+
		+	csdrs.py is an interface Python script allowing for the following functionality:
		+
		+	# List requests (state) - get a list of all requests in the system matching state.
		+	# Submit request (request XML) - submits request XML to be parsed by requestprocessor.py, returns a request ID
		+	# Cancel request (request ID) - halts processing on request ID
		+	# Status of request (request ID) - gets the status of a particular request ID
		+
		+	When a job is submitted, it spawns a new requestprocessor.py and records the id of that thread (for canceling a request). Requestprocessor.py is intended to be a background process and takes an XML document as input.

	== User Choices CyberShake Data Sets ==		== User Choices CyberShake Data Sets ==

@@ Line 1: / Line 1: @@
 CyberShake Data Request Web Site is a first stage in automating CyberShake data requests. The variety of CyberShake data products is growing, so we propose to develop a web site that will help user request CyberShake data. We will use current CyberShake data requests to try out the proposed data request system. The goal of this first system is to generate a well defined data request. For now, we will continue to process the data requests manually, but will look to automating the retrieval if useful.
 == Use Case 1 ==
-User selects CyberShake 13.4. Show me the Graves-Pitarka CVM-S hazard maps.
+User would like the Graves-Pitarka CVM-S hazard map from CyberShake Study 13.4. User can go to the site, select 13.4, Graves-Pitarka CVM-S, all sites, with data product of map. The system will then calculate and return that map.
 == Use Case 2 ==
-Another use case, 13.4, what is available at USC.
+User would like the hazard curve for USC from the Graves-Pitarka CVM-S map from CyberShake Study 13.4. User can go to site, select 13.4, Graves-Pitarka CVM-S, site USC only, and then select hazard curve. The system will generate the hazard curve and notify the user.
 == Use Case 3 ==
-CyberShake 13.4, site list, Graves and Pitarka CVM-H, specifying intensity measure type, give all peak amplitudes applicable to the given site. Users specifies these, system returns list of rupture variations, peak amplitudes for each combination. Possible other information (user selectable), probability of rupture, time occurred, magnitude.
+User would like to see visual seismograms available for USC from the AWP CVM-H map from CyberShake Study 13.4. User can go to the site, select 13.4, AWP CVM-H, site USC, and then select seismograms as the data product. The system will generate images and return all applicable seismograms in PNG format.
 == Use Case 4 ==
-User specifies ERF ID, source ID, rupture ID, system returns text description.
+User would like to get a list of the top 20 sources that contribute to the hazard at USC from the Study 13.4 AWP CVM-S map. User can go to the site, select 13.4 , AWP CVM-S, site USC, and then select rupture list as the data product, sorted by top contributors.
 == User Choices CyberShake Data Sets ==
@@ Line 22: / Line 41: @@
 #CyberShake 1.0 Map
 #CyberShake 2.2 Map
 '''Other User Choices of data sets:'''

← Older revision		Revision as of 22:00, 24 April 2013
Line 13:		Line 13:

	CyberShake 13.4, site list, Graves and Pitarka CVM-H, specifying intensity measure type, give all peak amplitudes applicable to the given site. Users specifies these, system returns list of rupture variations, peak amplitudes for each combination. Possible other information (user selectable), probability of rupture, time occurred, magnitude.		CyberShake 13.4, site list, Graves and Pitarka CVM-H, specifying intensity measure type, give all peak amplitudes applicable to the given site. Users specifies these, system returns list of rupture variations, peak amplitudes for each combination. Possible other information (user selectable), probability of rupture, time occurred, magnitude.
		+
		+	== Use Case 4 ==
		+
		+	User specifies ERF ID, source ID, rupture ID, system returns text description.

	== User Choices CyberShake Data Sets ==		== User Choices CyberShake Data Sets ==

← Older revision		Revision as of 21:49, 24 April 2013
Line 9:		Line 9:

	Another use case, 13.4, what is available at USC.		Another use case, 13.4, what is available at USC.
		+
		+	== Use Case 3 ==
		+
		+	CyberShake 13.4, Graves and Pitarka CVM-H, give all peak amplitudes.

	== User Choices CyberShake Data Sets ==		== User Choices CyberShake Data Sets ==

← Older revision		Revision as of 21:25, 24 April 2013
Line 5:		Line 5:

	User selects CyberShake 13.4. Show me the Graves-Pitarka CVM-S hazard maps.		User selects CyberShake 13.4. Show me the Graves-Pitarka CVM-S hazard maps.
		+
		+	== Use Case 2 ==

	Another use case, 13.4, what is available at USC.		Another use case, 13.4, what is available at USC.