You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,15 +28,14 @@ If you don't use our hosted version of the MDPvis web application, you will need
28
28
29
29
# Bridging MDPvis and Your Domain
30
30
31
-
MDPvis interfaces with any MDP simulator+optimizer that is callable by a web server. We have a few read-to-go
31
+
MDPvis interfaces with any MDP simulator+optimizer that is callable by a web server.
32
32
33
-
Your domain web server is responsible for serving four HTTP requests from the visualization, transforms the query parameters to those expected by the simulator or optimizer, invokes the simulator or optimizer, then returns the results to MDPvis. There are four distinct requests that the bridge should support. We detail these requests below
33
+
Your domain web server is responsible for serving four HTTP requests from the visualization, transforms the query parameters to those expected by the simulator or optimizer, invokes the simulator or optimizer, then returns the results to MDPvis. There are four distinct requests that the bridge should support. We detail these requests below.
34
34
35
-
The visualization expects your code to support the following requests. If your domain is written in Python, we recommend porting one of the example `domain_bridge.py` files to your domain.
36
35
37
36
## /initialize
38
37
39
-
The `/initialize` endpoint provides a set of parameters that will be sent to the simulator or optimizer on future requests. Here your responsibility is to return a [JSON](http://www.copterlabs.com/blog/json-what-it-is-how-it-works-how-to-use-it/) object listing the:
38
+
The `/initialize` endpoint provides a set of parameters that will be sent to the simulator or optimizer on future requests. Here your responsibility is to return a [JSON](http://www.copterlabs.com/blog/json-what-it-is-how-it-works-how-to-use-it/) object listing these properties:
40
39
41
40
* Name
42
41
* Description
@@ -46,7 +45,7 @@ The `/initialize` endpoint provides a set of parameters that will be sent to the
46
45
* Step (How fast the value changes when pressing a button)
47
46
* Units
48
47
49
-
of each parameter. An example of this data structure in Python is:
48
+
An example of this data structure in Python is:
50
49
51
50
return {
52
51
@@ -89,32 +88,33 @@ of each parameter. An example of this data structure in Python is:
89
88
]
90
89
}
91
90
92
-
In the MDPvis user interface, each control will be grouped into panels under the `panel_title`.
91
+
In the MDPvis user interface, each control will be grouped into panels under the `panel_title`
92
+
and display the [icon](http://getbootstrap.com/components/#glyphicons) specified by `panel_icon`.
93
93
94
94
## /trajectories?QUERY
95
95
96
96
When requesting Monte Carlo trajectories, MDPvis will send the current set of parameters as defined in the initialization and assigned in the user interface. The job of the web server is to map the parameters of the user interface into parameters to invoke the simulator. After simulations have completed, the data should be JSON serialized. An example of the data in Python is:
0 commit comments