Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
View | Details | Raw Unified | Return to bug 206405
Collapse All | Expand All

(-)help/html/tutorials/projecttutorial.html (-1 / +100 lines)
Lines 6-11 Link Here
6
</head>
6
</head>
7
<body>
7
<body>
8
<h1>Creating a new Project Tutorial</h1>
8
<h1>Creating a new Project Tutorial</h1>
9
Not written yet.
9
10
<p>
11
The names used to create the Test project are in parentheses. 
12
Substitute your names as appropriate. 
13
In this example, the scenario will be for Japan.
14
<p>
15
Note: There are icons for many of the actions but for clarity 
16
the menubar items are used.. 
17
18
<h3>Creating the Project</h3>
19
<ul>
20
<li>Click on New->STEM project and create new STEM project (Test)
21
<li>Click "Next" if you want to update the DublinCore data.
22
<li>Click "Finish"
23
<li> Open the new project – you should see several folders including: decorators, graphs, etc.
24
</ul>
25
26
<h3>Creating a new Model</h3>
27
<ul>
28
<li> Click on New->Model to create new model (TestModel)
29
<li> Click "Next" to fill in any Dublin core data you want to add
30
<li> Select "Finish"
31
</ul>
32
33
<h3>Add either a New or Built-in Disease</h3>
34
35
<h4>Adding an existing built-in Disease to the Model</h4>
36
<ul>
37
<li>On the bottom Diseases tab, click on STEM->Built-in
38
<li>select "Spanish Flu"  
39
<li>DRAG your disease (e.g., Spanish Flu) into the model (TestModel)
40
 in the Rescource Set window. Expand the "TestModel" in the Resource Set window to see that it worked.
41
</ul>
42
43
<h4>Adding a New Disease to the Model</h4>
44
<ul>
45
<li>On the menu bar click New>New Disease
46
<li>Fill in the Name: (TestDisease)
47
<li>Fill in the Disease Name: (TestDiseaseName). 
48
    Remember this name for the Infector creation.
49
<li>Select the DiseaseModel in the ComboBox: 
50
   e.g., select  "DeterministicSEIRDiseaseModelImpl"
51
<li>Fill in any Dublin core data you want to add ((ignore type)
52
<li>Click finish
53
<li>Under decorators you should see TestDisease.standard
54
<li>DoubleClick models->TestModel in the project explorer. You should see TestModel in the Resource Set.
55
<li>DRAG your new disease (e.g., TestDisease.Standard) from decorators (in the project explorer window)  into the model "TestModel" in the Rescource Set window. Expand the "TestModel" in the Resource Set window to see that it worked.
56
</ul>
57
58
<h3>Adding the Geographical data to the Model</h3>
59
<ul>
60
<li>To add the geography data for Japan, at the bottom panel under Models, 
61
click on >STEM>Geography>Political>Country>JPN>JPN(0,1,2) full infrastructure
62
<li>Drag this up to the Model (TestModel) in the Resource set window
63
64
<li>save your work at this point by hitting <b>ctrl-s</b>
65
</ul>
66
<h3>Create a Scenario and add your model to it</h3>
67
<ul>
68
<li>click on New->Scenario to create new scenario
69
<li>give it a name (TestScenario))
70
<li>Fill in any Dublin core data you want to add
71
<li>click finish
72
<li>From the Project Explorer window, 
73
under Models, Drag the new model (TestModel) into 
74
the new Scenario in the Resource Set. 
75
<li>Expand the scenario so you can see that it worked.
76
</ul>
77
78
<h3>Add a sequencer to the Scenario</h3>
79
<ul>
80
<li>Go to Sequencers on the bottom window - expand fully
81
<li>drag Sequential Sequencer 2006 into the Scenario in the Resource Set
82
<li>An alternative would be to use New->SequentialSequencer 
83
to create the sequencer.
84
</ul>
85
86
<h3>Creating and adding an Infector</h3>
87
<ul>
88
<li>Click on New->New Infector 
89
<li>Name it (TestInfector), 
90
<li>Enter Disease Name;  
91
    if you created a new Disease it will be the name that 
92
    you specified (TestDiseaseName)  or  
93
   "Spanish Flu" if you used the builtin disease.
94
<li>Fill in location for Infector:
95
  <ul>
96
   <li>Select "Japan" for country.
97
   <li>Select a level 1 admin area name. (e.g. "Kinki")
98
   <li>Select a Level 2 admin area name. (e.g. "Kyoto")
99
  </ul> 
100
<li>Click on the Scenario to open it in the Resource set
101
<li>drag the TestInfector from Decorators into the scenario 
102
103
</ul>
104
105
<h3>Save your work at this point by hitting <b>ctrl-s</b></h3>
106
107
<h3>Select the scenario from the Project window  and select
108
<b>run</b> from the popup menu.</h3>
10
</body>
109
</body>
11
</html>
110
</html>
(-)help/html/interface/views/ge.html (-2 / +37 lines)
Lines 43-50 Link Here
43
	<li>Select the GoogleEarth View from the Tabbed Window. <br>
43
	<li>Select the GoogleEarth View from the Tabbed Window. <br>
44
	This should start the GoogleEarth application if it was not
44
	This should start the GoogleEarth application if it was not
45
	already started. The STEM-GoogleEarth interface has many options that
45
	already started. The STEM-GoogleEarth interface has many options that
46
	can be set from <b>Windows->preferences->STEM->GoogleEarth</b> However,
46
	can be set from 
47
	we can use the defaults for our first run. 
47
	<b>Windows->preferences->STEM->Visualization->Geographic->GoogleEarth</b> 
48
	However, we can use the defaults for our first run. 
48
	<li>Start a new simulation by selecting the Scenario window. 
49
	<li>Start a new simulation by selecting the Scenario window. 
49
	<li>Select the USA scenario. STEM->Geography->Political->Country->USA
50
	<li>Select the USA scenario. STEM->Geography->Political->Country->USA
50
	<li>double clicking the "Spanish Flu" <a href="../../concepts/modelingframework.html#scenario"> Scenario</a>.
51
	<li>double clicking the "Spanish Flu" <a href="../../concepts/modelingframework.html#scenario"> Scenario</a>.
Lines 89-93 Link Here
89
  If you are running the STEM standalone executable, the above steps were 
90
  If you are running the STEM standalone executable, the above steps were 
90
  already done for you and you just need to start STEM.exe.
91
  already done for you and you just need to start STEM.exe.
91
  
92
  
93
  <h2>Context Menu</h2>
94
  If you bring up the context menu (Right click in Windows) then you will 
95
  get a menu where you can issue some control commands or options for the 
96
  STEM/GoogleEarth interface.  The difference between the context menu and 
97
  the <b>Prefereces</b> is that the context menu only affects the current 
98
  invocation.  
99
  <ul>
100
   <li><em>Display Admin Area</em><br>
101
     This will bring up a menu where you can specify an admin area and 
102
     have if displayed on the GoogleEarth map.  This has nothing to do 
103
     with STEM but it was useful during our develpment of the STEM 
104
     geography files and has been left in.
105
   <li><em>Display Status</em><br>
106
     This will display on the console the status of the STEM/GoogleEarth 
107
     internal interface.  It is a useful debug tool.
108
   <li><em>Debug On/Off</em><br>
109
     Turns on  or off the debug output.
110
   <li><em>GoogleEarth Start</em><br>
111
     Startup GoogleEarth application if it is not already started.
112
   <li><em>GoogleEarth Restart</em><br>
113
     If GoogleEarth was for any reason stopped or crashed, 
114
     this will attempt to get it running again with the current 
115
     STEM status. It may not work.
116
   <li><em>GoogleEarth Run</em><br>
117
     This is used if you have already captured the KML log files and 
118
     you want to run them after the simulation is complete.
119
     It will let you specify the folder containing the KML files and 
120
     will send them one by one to GoogleEarth.
121
   <li><em>GoogleEarth Stop</em><br>
122
     This will stop the sending of files to GoogleEarth and 
123
     clear the polygons already displayed. 
124
   
125
  </ul>
126
    
92
</body>
127
</body>
93
</html>
128
</html>
(-)help/html/interface/preferences/preferencesgetoplevel.html (-3 / +6 lines)
Lines 26-32 Link Here
26
	overlaying the file written for the previous cycle. GoogleEarth 
26
	overlaying the file written for the previous cycle. GoogleEarth 
27
	asks for new data on a predetermined interval and is sent the 
27
	asks for new data on a predetermined interval and is sent the 
28
	current KML.  The advantage over the previous method is that 
28
	current KML.  The advantage over the previous method is that 
29
	it helps keep GoogleEarth from falling to far behind the STEM processing.</li>
29
	it helps keep GoogleEarth from falling too far behind the STEM processing.</li>
30
	<li><em>"DirectLaunch"</em><br>With this option, the KML files 
30
	<li><em>"DirectLaunch"</em><br>With this option, the KML files 
31
	are directly sent to GoogleEarth without using an intermediate 
31
	are directly sent to GoogleEarth without using an intermediate 
32
	web server. This can cause problems because GoogleEarth may get 
32
	web server. This can cause problems because GoogleEarth may get 
Lines 38-44 Link Here
38
	STEM will write the KML files that GoogleEarth will read.  
38
	STEM will write the KML files that GoogleEarth will read.  
39
	If it already contains KML files, the user will be given 
39
	If it already contains KML files, the user will be given 
40
	the oportunity to delete them, keep them or choose a new folder.</li>
40
	the oportunity to delete them, keep them or choose a new folder.</li>
41
  <li><em>"User internal webserver"</em><br>This is used to cause the 
41
  <li><em>"Use internal webserver"</em><br>This is used to cause the 
42
    webserver built into Eclipse to be used.</li>
42
    webserver built into Eclipse to be used.</li>
43
  <li><em>"Hostname:port for external webserver"</em>
43
  <li><em>"Hostname:port for external webserver"</em>
44
    <br>This is the required hostname and port for an external webserver. 
44
    <br>This is the required hostname and port for an external webserver. 
Lines 50-61 Link Here
50
  <li><em>"Automatically process every simulation"</em>
50
  <li><em>"Automatically process every simulation"</em>
51
    <br>if specified, then when you start any simulation running, 
51
    <br>if specified, then when you start any simulation running, 
52
    it will automatically have its processing be mapped to GoogleEarth.  
52
    it will automatically have its processing be mapped to GoogleEarth.  
53
    Only the first one will be displayed by GE since it would 
53
    Only one simulation will be displayed by GE since it would 
54
    be counterproductive to show 2 different views at the same time. </li>
54
    be counterproductive to show 2 different views at the same time. </li>
55
  <li><em>"Write KML files only every N th cycle"</em>
55
  <li><em>"Write KML files only every N th cycle"</em>
56
    <br>If the simulation does not change rapidly from cycle to cycle, 
56
    <br>If the simulation does not change rapidly from cycle to cycle, 
57
    significant overhead can be saved by only sending data to 
57
    significant overhead can be saved by only sending data to 
58
    GoogleEarth every Nth cycle.</li>
58
    GoogleEarth every Nth cycle.</li>
59
  <li><em>"Chose Aspect to be Logged.cycle"</em>
60
    <br>Select the disease aspect to be displayed as colored polygons
61
    on the GoogleEarth map.</li>
59
</ul>
62
</ul>
60
<img src="img/preferencesgetoplevel.jpg" />
63
<img src="img/preferencesgetoplevel.jpg" />
61
</body>
64
</body>

Return to bug 206405