Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "STEM Installation Guide"

(add javadoc instructions)
(Downloading and Installing STEM)
(138 intermediate revisions by 8 users not shown)
Line 1: Line 1:
'''[http://wiki.eclipse.org/index.php/STEM STEM Contents Page]'''
+
[[Image:STEM TOP BAR.gif|800px]]
 +
{| align="right"
 +
  | __TOC__
 +
  |}
  
=STEM Installation Guide=
+
'''[[STEM|Back to STEM Contents Page]]'''
==Installing  Java™ JVM==
+
STEM requires Java Version 1.5.
+
IBMers should obtain the IBM version of Java 1.5.  Others can use either IBM's Java 1.5 or the Sun Java 1.5 [[http://java.sun.com/j2se/1.5.0/download.jsp]].
+
  
For MacOS, you should install Java SE 1.6
+
== STEM Video on YouTube<sup>TM</sup> ==
 +
The STEM Project published full-length video tutorials for STEM on YouTube in several languages.
  
==Installing the Eclipse Environment==
+
#[http://www.youtube.com/watch?v=MtQlS7g7Qnw STEM Model Generator (new!!)] ''requires STEM V2.0 milestone''
If you might contribute to STEM development or if you want to always have the most recent code then you will need to install Eclipse.  
+
#Full length video [http://www.youtube.com/watch?v=LfiibQX4IFE In English]
 +
#Full length video [http://www.youtube.com/watch?v=AFYXvazKkms In Hebrew]
 +
#Full length video [http://www.youtube.com/watch?v=NM5X8-MaiKo In Japanese]
 +
#Full length video [http://www.youtube.com/watch?v=3S5DbjCHsx4 In Spanish]
 +
#[http://www.youtube.com/watch?v=OoiFLemepw4 5 min Video (English)]
 +
#Avian Influenza
 +
##Only [https://youtu.be/tI0Ogy-8O10 Poultry-Human Transmission]
 +
##Including  [https://youtu.be/0YJ6FxdhFm8 Human-Human Transmission]
  
Go to [[STEM Eclipse Setup]]
+
== Getting Started ==
 +
There are two paths to running STEM:  from a downloaded binary installed as a standalone application or built from source and launched in Eclipse.  Here are some considerations regarding which path to choose:
  
==Obtaining the STEM source code==
+
* If you want to use STEM to compose models, scenarios, and run simulations, you can download and install STEM as a standalone application following the instructions in this guide.
If you want to obtain the latest version of the STEM source code then you will need to obtain it from the Eclipse CVS repository.  
+
* If you want to extend or add new functionality to STEM, including new disease and computational models, you need to build STEM from source.  See the [[STEM_Eclipse_Setup|Setting up a STEM Development Environment]] page for more instructions.
  
Goto [[STEM Source Code]]
+
=== Prerequisites ===
 +
STEM is a Java application built on top of the Eclipse Rich Client Platform (RCP).  To run STEM, please verify you have the following prerequisites installed:
  
==Installing/Running the STEM application==
+
# A workstation running an Eclipse-supported operating system:
 +
#* Windows (XP, Vista, 7)
 +
#* Linux (GTK)
 +
#* Mac OS X (10.5 or later)
 +
#* A supported Java Standard Edition from either Oracle (Sun) or IBM
 +
#'''For STEM V3.0.0M1 or above the minimum requirement is (J2SE) 8.0 JVM'''
 +
#: [https://java.com/en/download/  Oracle Java SE 8.0 (JRE8U65 or higher)]
 +
# For STEM V 2.0.x or earlier
 +
#: (J2SE) 6.0 JVM
 +
#: [http://www.oracle.com/technetwork/java/javase/downloads/jre6u37-downloads-1859589.html Oracle Java SE 6.0 (6.0.26 or higher)]
 +
#: [http://www.ibm.com/developerworks/java/jdk/ IBM Java SE 6.0]
 +
#* '' '''Note:''' Mac OS X users can use the version included with the operating system ''
 +
#* '' '''Note:''' The GNU for Java (GCJ) compiler and libraries are not supported.  If you're running on Linux, it's strongly recommended you use an Oracle or IBM JRE''
 +
#* '' '''Note:''' While STEM V2.0.x should work with Java 7, it is not tested or supported at this time. STEM V3.0.x is is based on Eclipse 4.x and requires Java 8''
 +
# A tool to extract zipped archives
 +
#: ''Most operating systems have this built-in, although Windows users may wish to install a standalone utility like [http://www.7-zip.org/ 7-Zip]''
  
 +
=== Which File To Download? ===
 +
The STEM Project publishes several different binary versions of the application.  Please consider these options when choosing which to download.
  
There are 2 ways to run STEMOne is as a STEM user that has installed Java 1.5 and is running Windows or Linux, and wants to use STEM as a modeling and simulation tool. They would download the STEM application and run it as a standalone application.  
+
==== 32-bit vs. 64-bit ====
 +
Most modern operating systems from 2009 and on support 64-bit (x86_64) compiled binariesThe 64-bit version of STEM can take advantage of larger memory spaces (beyond 2 GB), which is necessary to run very large (global) simulations.
  
The other way to run STEM is as a STEM developer that has installed
+
The STEM project publishes both 32-bit ('''x86''') and 64-bit ('''x86_64''') versions of the application for each supported operating system.  ''' The version you download strictly depends on whether you have a 32-bit or 64-bit Java Runtime Environment (JRE) installed. '''  If you have a 64-bit JRE installed, download the '''x86_64''' version. Otherwise, download the '''x86''' version.
Java, the Eclipse development tools and the STEM source code. These users can be running on any platform supported by Eclipse.
+
  
===Running Stem as a standalone application===
+
Some 64-bit JREs can run in 32-bit mode.  Please see your JRE's documentation for instructions.
  
If you want to first run STEM as an application then we provide a standalone version of STEM that only requires that you have Java 1.5 or higher installed.  
+
==== Release, Milestone, or Integration Builds ====
 +
The best version of STEM to download is generally the latest '''Release'''. In addition to being fully tested and stable, it's approved for distribution by the Eclipse Foundation and subject to the terms of the [http://www.eclipse.org/legal/epl/notice.php Eclipse Software User Agreement] and the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License].
  
You can get the file by going to the  
+
However, power users or those looking for the latest features may choose to download the latest '''Weekly Integration''', '''Milestone''', or '''Release Candidate''' build. These builds may not be stable and are not sanctioned by the Eclipse Foundation.  ''Use at your own risk''.
[http://www.eclipse.org/ohf/components/stem project page]:
+
and then clicking on '''Getting Started'''
+
From the '''Getting Started''' page you can download either a zip file for Windows XP/Vista or a gz file for Linux x86.   If you are running on another platform, you will have to download the STEM source code and build STEM for your platform.
+
  
Once you have downloaded the zip file, ('''Warning: the download is a very large file and will take awhile to download.''')
+
== Downloading and Installing STEM ==
you would "unzip" the file into your favorite directory.  
+
The STEM application is bundled as a platform-specific, zipped archive and does not contain an installer. To install STEM, download the appropriate bundle and unzip it to your desired installation path.
  
This is a self-contained stand-alone version of STEM that is launched by double-clicking on the "STEM.exe" executable file in the root directory of the expanded archive.  You'll need to have Java 1.5 installed for it to run, but if you do and it's on the path,  you should be greeted by the STEM "splash screen" while it starts up.
+
<span style="color:#ff0000">'''The STEM installation path cannot contain whitespace charactersEnsure that the install path contains no spaces, tabs, etc.'''</span>
The Eclipse application at this point shows the STEM Simulation Perspective.
+
<br>
+
STEM Simulation screen.
+
[[Image:Simulation1.jpg|300px]]
+
*The '''Help->Help Context''' menubar selection has extensive information on running STEM.   
+
*The following "views" are shown in the STEM Simulation window.
+
** '''Map''' <br>Canvas that will show the image of the geographic area where the simulation is being run.
+
** '''Simulation Control''' view <br>Panel that both describes the status of the simulation and provides buttons to start and stop the simulation.
+
** '''Scenarios''' <br>The Scenarios window is use to select a prebuilt scenario for a simulation.  By selecting leafs in the tree you can discover an existing scenario for running a simulation.  Select the scenario of choice and click the '''Run''' or '''Advance''' icon on the toolbar. 
+
** '''ErrorLog''' <br>This log will contain information about any errors that occur while running the application.  If things don't work as you expect,  check this view to see if there are any errors or exceptions that have occurred. Note that the ErrorLog on the secondary Eclipse will show errors and exceptions that occur in the application being tested but stdout/stderr will be sent to the Console of the Primary Eclipse.  Also if an exception is caught by the application and not passed to the built in log facility it will only show up on the Primary console.  Likewise, if an exception is not caught and  sent to stdout/stderr then it will only show up on the secondary ErrorLog.  Confusing!
+
+
  
There are also secondary application that may be selected from the ''Windows'' menu.
+
''' If you already have STEM 1.4 or newer installed and wish to upgrade, see the [[#STEM_Updates|STEM Updates section]]. '''
  
* Select '''windows'''
+
# In your browser, go to the '''[http://www.eclipse.org/stem/downloads.php STEM Downloads page]'''
** Select '''GoogleEarth View''' <br> This is an interface between STEM and the GoogleEarth application.  
+
# Choose the appropriate bundle to download (see [[#Which_File_To_Download.3F|previous section]] for help) and click the link
 +
# On the mirrors page, select a nearby mirror site.  This will begin the download.
 +
# If prompted, choose to '''Save''' the file.  Note where the file is downloading to.
 +
#: '' On some systems, the browser may automatically execute (unzip) the file when it finishes downloading.  If this is the case, skip to '''step 8''' when the download finishes. ''
 +
# ''Wait while the STEM bundle downloads...''
 +
#:  '' '''Note:''' STEM is approximately 150 MB in size.  Depending on your connection and mirror speeds, the download will take from a few minutes to an hour or more. ''
 +
# When the download finishes, open the folder where the downloaded file sits
 +
# Extract/unzip the STEM archive
 +
#: '' '''Note:''' On most systems, double clicking the the .zip file will automatically extract it. ''
 +
# Extracting the archive should create a folder called '''stem'''.  Move this folder to the path you wish to install STEM at.
 +
#: '' ''' IMPORTANT REMINDER: ''' Verify that the install path does not contain whitespace or non-ASCII characters, including spaces, tabs, etc. ''
 +
#* Windows users may want to place '''stem''' folder in a drive root.  Example is '''c:\stem'''
 +
#* Mac OS X users may want to place the '''stem''' folder in the '''Applications''' folder
 +
# Optionally, you can create a shortcut on your desktop, start menu, dock, etc to quickly launch STEM
 +
# Increasing the system memory available to STEM. Some large scenarios (e.g. with thousands of nodes and edges), require that you make sure you allocate enough system memory for STEM. If you don't do this the application may hang or crash with a "Heap Space" error. To allocate enough memory in Windows, create a shortcut for launching STEM. You may place this anywhere (e.g., on your desktop or on the quicklaunch bar).
 +
#* Right click on the shortcut. Select "Properties" You should see a field in the Properties Dialogue labeled Target: to the right in the text field you will see something like:
 +
#: C:\stem_builds\stem\STEM.exe -vmargs -Xms812M -Xmx812M
 +
#* To launch STEM with more memory you must add "virtual machine arguments" to the target line. For example, to set the min heap size to 1 GB and max heap size to 4GB use:
 +
#: C:\stem_builds\stem\STEM.exe -vmargs -Xms1024M -Xmx4096M
 +
#* On MAC OS X, using the finder, navigate to where the STEM application is located, right click and select "Show Package Content". Navigate to Contents-&gt;MacOS and open the STEM.ini file in an editor. Change the -Xms and the -Xmx lines to increase the memory, e.g. -Xms1024M -Xmx4096M or more depending on how much memory is available.  
  
The basic idea of the GoogleEarth Interface is to allow the information about the geographic spread of diseases to be reflected on the GoogleEarth Web map. Detailed instructions for using the GoogleEarth Interface are included below.
 
[http://wiki.eclipse.org/index.php/Welcome_STEM_Developers#STEM_-_GoogleEarth_Interface]
 
  
===Preparing to Run STEM as a STEM developer===
 
  
It is possible to run STEM as an application from the Eclipse Development environment without actually creating the standalone Stem application. 
+
That's it!  STEM is now installedSee the next section for instructions to launch STEM.
Earlier sections described how to set up the environment and checkout the STEM source filesOnce you have done that you will want to run the application using the compiled source. A later section will describe how to build the standalone  Stem application.
+
  
This section will describe how to run and test the STEM application from the source projects.  It assumes that you have downloaded the following projects from CVS and the build was error free.  
+
== Launching and Running STEM ==
 +
After STEM is unzipped and placed in the install folder, you can launch the application. STEM can run both with a full Graphical User Interface (GUI) or "headlessly" in a text-only console. For more information about the text-only option, see the [[STEM Headless|headless STEM article]].
  
* STEM projects (required)
+
# Navigate to the folder STEM is installed in
** '''org.eclipse.ohf.stem.core'''
+
# Double click the STEM executable file
** '''org.eclipse.ohf.stem.definitions'''
+
#: [[Image:STEM-Install-FinderView.png|400px]]
** '''org.eclipse.ohf.stem.diseasemodels'''
+
#* For Windows, the file is named '''STEM.exe'''
** '''org.eclipse.ohf.stem.diseases'''
+
#* For Mac OS X, the file is named '''STEM''' or '''STEM.app'''
** '''org.eclipse.ohf.stem.geography'''
+
#* For Linux, the file is named '''STEM'''
** '''org.eclipse.ohf.stem.internal.data'''
+
# On some system, you may get a security warning about launching a downloaded application.  Click '''OK''' or '''Open'''
** '''org.eclipse.ohf.stem.jobs'''
+
#: '' '''Note:''' This warning message varies depending on your operating system ''
** '''org.eclipse.ohf.stem.sequencers'''
+
#: [[Image:STEM-Install-DownloadedApplicationWarning.png|200px]]
** '''org.eclipse.ohf.stem.ui'''
+
# The STEM splash screen should immediately appear
** '''org.eclipse.ohf.stem.ui.diseasemodels'''
+
#: [[Image:STEM-Install-Splash.png|200px]]
** '''org.eclipse.ohf.stem.ui.ge'''
+
# The first time STEM is launched, several configuration tasks have to run in the background
** '''org.eclipse.ohf.stem.ui.reports'''
+
#: ''These tasks may take 1-2 minutes depending on system speed. During this time, only the splash screen is displayed.''
 +
# When STEM finishes loading, the workbench will launch the '''Simulation''' perspective
 +
#: The first time you run STEM, the '''Welcome to STEM''' screen will display. You can close this by click the '''X''' on the '''Welcome''' tab.
 +
#: [[Image:STEM-Install-WelcomeScreen.png|200px]]
 +
# Congratulations! STEM is loaded and ready to use
 +
#: [[Image:STEM-Install-Workbench.png|500px]]
 +
# To get started using STEM, start by going through the tutorials on the [[STEM#STEM_Documentation|STEM Documentation]] page
 +
#: '' You may find it helpful to watch the [http://www.youtube.com/watch?v=LfiibQX4IFE YouTube tutorial] before you go on to learn to [[Creating_a_STEM_Scenario|create a scenario]] ''
  
 +
===Installing Additional STEM Features===
 +
: '' See section on [[STEM Addons | STEM Add-ons]] ''
  
* STEM projects (optional)
+
STEM uses the Automated Eclipse Updates to make it easier for users to install additional features to STEM. Today, one feature you may want to add
** '''org.eclipse.ohf.stem.jobs.nl1'''
+
is the Earth Science data plugin that contains global climate data for the years 2001-2010. This plugin is '''required''', for example, if you want to use the ''Anopheles'' Mosquito model.
** '''org.eclipse.ohf.stem.sample'''
+
** '''org.eclipse.ohf.stem.tests.core'''
+
** '''org.eclipse.ohf.stem.tests.definitions'''
+
** '''org.eclipse.ohf.stem.tests.diseasemodels'''
+
** '''org.eclipse.ohf.stem.tests.jobs'''
+
** '''org.eclipse.ohf.stem.tests.sequencers'''
+
** '''org.eclipse.ohf.stem.tests.ui'''
+
** '''org.eclipse.ohf.stem.ui.nl1'''
+
** '''org.eclipse.ohf.stem.utility'''
+
  
'''Preparing the STEM scenario'''
+
See the [[STEM Addons | main article]]  for instructions on how to install new features into STEM.
  
The first step is to run a utility that will build the scenarios that you will later use to run the STEM application.  
+
== Updating STEM ==
 +
Starting with version 1.4, you can use the update mechanism built into STEM to perform upgrades without re-downloading the full installation bundle.  Most of the time, this means you don't have to re-download the large denominator data sets packaged in STEM or have to export and import your scenarios.
  
*Select the '''org.eclipse.ohf.stem.internal.data''' project
+
PLEASE NOTE. STEM V2.0.x and earlier are based on Eclipse 3.x The Latest versions of STEM beginning with STEM V 3.0.0M1 are base on Eclipse 4.x and therefore require that Java 8 be installed.  
**Select the '''update.xml''' file from the project
+
  Please see system requirements above. The following procedure will not update your Java installation. This must be done first.
**RightClick and select '''run As: ant build...''' (note the ...)
+
**On the '''Modify attributes and launch'' screen:
+
***select '''JRE'''
+
****Specify '''Separate JRE''' (should show some version of JDK 1.5 or later)
+
****For VM arguments: Specify -Xmx512m (or more)
+
***select '''Properties'''
+
***verify that '''eclipse.contrib''' and '''eclipse.home2''' are defined.  If not, refer to [http://wiki.eclipse.org/index.php?title=STEM_Eclipse_Setup#Installing_Eclipse_Features]
+
***Select '''Run'''
+
  
It will churn away for awhile (maybe 10 minutes or more)  displaying a lot of console output ending with:
+
# Verify the computer is connected to a network and launch '''STEM'''
<code>
+
#: '''If STEM is already open, save all edited files and stop any running simulations'''
  BUILD SUCCESSFUL
+
# Open the '''Help''' Menu and choose '''Check for Updates'''
  Total time: n minutes n seconds
+
#: [[Image:STEM-Update-CheckForUpdatesMenu.png|200px]]
</code>
+
# ''Wait while STEM contacts the updates server and checks for new versions''
If you get error messages about eclipse.home2 or eclipse.contrib then refer to [http://wiki.eclipse.org/index.php/STEM_Eclipse_Setup#Installing_Eclipse_Features]
+
#* If no updates are available, a message saying '''No updates were found''' will appear. Click '''OK''' to return to STEM
 +
#* If an update is available, the '''Available Updates''' wizard will appear
 +
# On the '''Available Updates''' page, verify '''STEM''' is selected, and click '''Next'''
 +
#: [[Image:STEM-Update-AvailableUpdates.png|400px]]
 +
# Verify the list of items to be installed is correct and click '''Next'''
 +
# Review the the licenses of the software being installed to verify you still accept
 +
#: If you accept the terms, select ''' I Accept the terms of the license agreements''' and click '''Finish'''
 +
#: If you do not accept the terms, click '''Cancel'''
 +
# ''Wait while STEM downloads and installs the updates''
 +
# If prompted with a security warning about installing unsigned software, click '''OK'''
 +
# When prompted to apply changes, verify all open files are saved and click '''Restart Now'''
 +
# STEM should automatically restart.  If not, relaunch it manually
  
===Start STEM product===
+
=== Checking the Version of STEM Installed ===
 +
After updating STEM, the version displayed on the splash screen at startup may not change to reflect the new version.  To verify STEM updated successfully, check the STEM Installation Details.
 +
# Open the '''Help''' menu and select '''About STEM'''
 +
# Click '''Installation Details'''
 +
# In the '''STEM Installation Details''' dialog, verify the installed version for '''STEM'''
 +
#: [[Image:STEM-Update-InstalledDetailsVersion.png]]
  
Once the scenario is builtyou need to startup STEM and run
+
=== Updating to Latest Integration or Milestone Build ===
the simulation.   
+
By default, the STEM update feature only checks for the latest, official release approved by the Eclipse Foundation. However, users will often want to take advantage of new features published in weekly integration and/or periodic milestone and release candidate buildsYou can easily configure STEM to download and install these updates.
  
* Go to the Package Explorer view
+
# Launch '''STEM'''
* Select the '''org.eclipse.ohf.stem.ui''' project
+
# Open the '''Window''' menu and select '''Preferences'''
* Select the appropriate '''.product''' file for your platform.
+
#: '' On Mac OS X, '''Preferences''' is under the '''STEM''' menu ''
** Select '''stem.product''' for Windows
+
# In the '''Preferences''' window, expand '''Install/Update''' and select '''Available Software Sites'''
** Select '''stemLinux.product''' for Linux x86
+
# Under '''Available Software Sites''', click '''Add'''
** Select '''stemMacOS.product''' for MacOS
+
# In the '''Add Site''' dialog, enter the appropriate '''Name''' and '''Location'''
** For other platforms, ??? To be Added ???
+
#: For weekly integration builds:
* From the ''launcher'' tab
+
#:* '''Name''':  STEM Integration Builds
** specify Program arguments "-consoleLog"
+
#:* '''Location:''' <nowiki>http://download.eclipse.org/stem/update-site/integration/</nowiki>
** specify VM arguments "-Xmx600M"
+
#: For periodic milestone and release candidate builds:
* From the Overview tab
+
#:* '''Name''':  STEM Stable Builds
**  select ''Launch'' or ''Launch in Debug mode''.
+
#:* '''Location:''' <nowiki>http://download.eclipse.org/stem/update-site/stable/</nowiki>
 +
# Click '''OK''' to add the site
 +
# Click '''OK''' to save '''Preferences''' and return to '''STEM'''
 +
# Follow the steps in the [[#Updating_STEM|previous section]] to update '''STEM'''
 +
# ''To disable checking for non-release versions, disable or remove the sites added to the '''Available Software Sites''' list ''
  
It should build a new image of STEM and launch it.
+
== Setting up the STEM Development Environment in Eclipse ==
 +
If you might contribute to STEM development or if you want to always have the most recent code, then you will need to install Eclipse.  
  
The system will grind away and start a new instance of Eclipse with support just for STEM.  If you have not done this before, you should be aware that this new instance is being controlled by your primary Eclipse instance and console output from your application will be sent back to your primary Eclipse.  Also you can use the debugger and the debugging controls for the application will be on the primary eclipse window as the application runs in the secondary Eclipse.
+
: '' Go to tutorial on [[STEM Eclipse Setup | Setting up a STEM Development Environment]]
 
+
You are now running the STEM application.  See the instructions for running the Standalone version of STEM
+
[http://wiki.eclipse.org/index.php/Installation_Guide#Running_Stem_as_a_standalone_application]
+
 
+
Also, use the '''Help->Help Context''' from the menubar to get extensive '''Help''' information.
+
 
+
===Generate JavaDoc for STEM===
+
You can easily generate JavaDoc for STEM with the following process.
+
*Select the '''org.eclipse.ohf.stem.doc''' project
+
**Select the '''javadoc.xml''' file from the project
+
**RightClick and select '''run As: ant build'''
+
 
+
This will generate javadoc in '''org.eclipse.ohf.stem.doc/javadoc''' and
+
it can be displayed by selecting the '''index.html''' member.
+
 
+
===Understanding '''stem.product'''===
+
The file '''stem.product''' in '''org.eclipse.ohf.stem.ui''' is a very important piece of the process to launch an application. 
+
However it appears to be a trial and error process to
+
generate the list of  plugins. 
+
 
+
 
+
Also it is important to note that there seems to be a difference between launching STEM from "Run" on the eclipse menubar and from the "launch" or "Debug" buttons on the "Overview" tab from the '''org.eclipse.ogh.stem.ui'''  '''stem.product''' selection.
+
 
+
If you update the list of plugins in the "Configuration" tap for stem.product that does
+
not update the list of plugins that are used when you select a launch entry from the menubar.  However, using the launch entry from stem.product overview appears to then update the menubar launch.    Very confusing!!!
+
 
+
+
The following section is to give some info about the reason for
+
including each of the plugins.  There are lots of ? because
+
short of trying it without the plugin there is no way to
+
be sure.
+
Col 1 has the following codes
+
R  Required for base system
+
R? probably required for base
+
B  BIRT
+
H  Help
+
W  Webserver
+
O  OHF STEM required projects for RCP
+
-  Platform specific
+
?  unknown but appears to be required
+
?? unknown and not tried to run without.
+
-----------------------------------------------------
+
?    <plugin id="com.ibm.icu"/>
+
B?    <plugin id="com.lowagie.itext"/>    ** only for specific functions
+
H    <plugin id="javax.servlet"/>
+
H?    <plugin id="javax.servlet.jsp"/>
+
R?    <plugin id="org.apache.ant"/>
+
??    <plugin id="org.apache.batik.pdf"/>
+
??    <plugin id="org.apache.commons.codec"/>
+
??    <plugin id="org.apache.commons.el"/>
+
??    <plugin id="org.apache.commons.logging"/>
+
H?    <plugin id="org.apache.jasper"/>
+
H    <plugin id="org.apache.lucene"/>
+
H?    <plugin id="org.apache.lucene.analysis"/>
+
??    <plugin id="org.apache.xerces"/>
+
??    <plugin id="org.apache.xml.resolver"/>
+
??    <plugin id="org.eclipse.ant.core"/>
+
B    <plugin id="org.eclipse.birt.chart.device.extension"/>
+
B    <plugin id="org.eclipse.birt.chart.device.svg"/>
+
B    <plugin id="org.eclipse.birt.chart.device.swt"/>
+
B    <plugin id="org.eclipse.birt.chart.engine"/>
+
B    <plugin id="org.eclipse.birt.chart.engine.extension"/>
+
B    <plugin id="org.eclipse.birt.chart.ui"/>
+
B    <plugin id="org.eclipse.birt.chart.ui.extension"/>
+
B    <plugin id="org.eclipse.birt.core"/>
+
B    <plugin id="org.eclipse.birt.core.ui"/>
+
R?    <plugin id="org.eclipse.core.commands"/>
+
R?    <plugin id="org.eclipse.core.contenttype"/>
+
R?    <plugin id="org.eclipse.core.databinding"/>
+
R?    <plugin id="org.eclipse.core.expressions"/>
+
?    <plugin id="org.eclipse.core.filesystem"/>
+
-    <plugin id="org.eclipse.core.filesystem.win32.x86" fragment="true"/>
+
R?    <plugin id="org.eclipse.core.jobs"/>
+
R    <plugin id="org.eclipse.core.net"/>
+
R?    <plugin id="org.eclipse.core.resources"/>
+
R?    <plugin id="org.eclipse.core.resources.compatibility" fragment="true"/>
+
R?    <plugin id="org.eclipse.core.resources.win32" fragment="true"/>
+
R?    <plugin id="org.eclipse.core.runtime"/>
+
R?    <plugin id="org.eclipse.core.runtime.compatibility.auth"/>
+
R?    <plugin id="org.eclipse.core.runtime.compatibility.registry" fragment="true"/>
+
R?    <plugin id="org.eclipse.core.variables"/>
+
R?    <plugin id="org.eclipse.emf.common"/>
+
R?    <plugin id="org.eclipse.emf.common.ui"/>
+
R?    <plugin id="org.eclipse.emf.ecore"/>
+
R?    <plugin id="org.eclipse.emf.ecore.change"/>
+
R?    <plugin id="org.eclipse.emf.ecore.xmi"/>
+
R?    <plugin id="org.eclipse.emf.edit"/>
+
R?    <plugin id="org.eclipse.emf.edit.ui"/>
+
R?    <plugin id="org.eclipse.equinox.app"/>
+
R?    <plugin id="org.eclipse.equinox.common"/>
+
H    <plugin id="org.eclipse.equinox.http.jetty"/>
+
H    <plugin id="org.eclipse.equinox.http.registry"/>
+
H    <plugin id="org.eclipse.equinox.http.servlet"/>
+
H    <plugin id="org.eclipse.equinox.jsp.jasper"/>
+
H    <plugin id="org.eclipse.equinox.jsp.jasper.registry"/>
+
?    <plugin id="org.eclipse.equinox.preferences"/>
+
?    <plugin id="org.eclipse.equinox.registry"/>
+
H    <plugin id="org.eclipse.help"/>
+
H    <plugin id="org.eclipse.help.appserver"/>
+
H    <plugin id="org.eclipse.help.base"/>
+
H    <plugin id="org.eclipse.help.ui"/>
+
H    <plugin id="org.eclipse.help.webapp"/>
+
?    <plugin id="org.eclipse.jdt.core"/>
+
?    <plugin id="org.eclipse.jface"/>
+
?    <plugin id="org.eclipse.jface.databinding"/>
+
?    <plugin id="org.eclipse.jface.text"/>
+
O    <plugin id="org.eclipse.ohf.stem.core"/>
+
O    <plugin id="org.eclipse.ohf.stem.definitions"/>
+
O    <plugin id="org.eclipse.ohf.stem.diseasemodels"/>
+
O    <plugin id="org.eclipse.ohf.stem.diseases"/>
+
O    <plugin id="org.eclipse.ohf.stem.geography"/>
+
O    <plugin id="org.eclipse.ohf.stem.jobs"/>
+
O    <plugin id="org.eclipse.ohf.stem.jobs.nl1" fragment="true"/>
+
O    <plugin id="org.eclipse.ohf.stem.sequencers"/>
+
O    <plugin id="org.eclipse.ohf.stem.ui"/>
+
O    <plugin id="org.eclipse.ohf.stem.ui.diseasemodels"/>
+
O    <plugin id="org.eclipse.ohf.stem.ui.ge"/>
+
O    <plugin id="org.eclipse.ohf.stem.ui.nl1" fragment="true"/>
+
O    <plugin id="org.eclipse.ohf.stem.ui.reports"/>
+
R?    <plugin id="org.eclipse.osgi"/>
+
R?    <plugin id="org.eclipse.osgi.services"/>
+
R?    <plugin id="org.eclipse.osgi.util"/>
+
R?    <plugin id="org.eclipse.pde.runtime"/>
+
R?    <plugin id="org.eclipse.swt"/>
+
-    <plugin id="org.eclipse.swt.win32.win32.x86" fragment="true"/>
+
??    <plugin id="org.eclipse.team.core"/>
+
?    <plugin id="org.eclipse.text"/>
+
W    <plugin id="org.eclipse.tomcat"/>
+
R?    <plugin id="org.eclipse.ui"/>
+
R?    <plugin id="org.eclipse.ui.forms"/>
+
R?    <plugin id="org.eclipse.ui.ide"/>
+
R?    <plugin id="org.eclipse.ui.views"/>
+
-    <plugin id="org.eclipse.ui.win32" fragment="true"/>
+
R?    <plugin id="org.eclipse.ui.workbench"/>
+
?    <plugin id="org.eclipse.update.configurator"/>
+
?    <plugin id="org.eclipse.update.core"/>
+
?    <plugin id="org.eclipse.update.core.win32" fragment="true"/>
+
?    <plugin id="org.eclipse.update.ui"/>
+
??    <plugin id="org.eclipse.xsd"/>
+
??    <plugin id="org.junit"/>
+
H    <plugin id="org.mortbay.jetty"/>
+
B    <plugin id="org.mozilla.rhino"/>
+
??    <plugin id="org.w3c.dom"/>
+
 
+
 
+
The following plugins get added to stem.product by
+
the "add required plugins" but they should be deleted
+
because they are not needed and caused error messages at
+
startup.  They appear to require Java 6
+
 
+
org.eclipse.jdt.compiler.apt
+
org.eclipse.jdt.internal.compiler.tool
+

Revision as of 13:45, 24 July 2017

STEM TOP BAR.gif

Back to STEM Contents Page

STEM Video on YouTubeTM

The STEM Project published full-length video tutorials for STEM on YouTube in several languages.

  1. STEM Model Generator (new!!) requires STEM V2.0 milestone
  2. Full length video In English
  3. Full length video In Hebrew
  4. Full length video In Japanese
  5. Full length video In Spanish
  6. 5 min Video (English)
  7. Avian Influenza
    1. Only Poultry-Human Transmission
    2. Including Human-Human Transmission

Getting Started

There are two paths to running STEM: from a downloaded binary installed as a standalone application or built from source and launched in Eclipse. Here are some considerations regarding which path to choose:

  • If you want to use STEM to compose models, scenarios, and run simulations, you can download and install STEM as a standalone application following the instructions in this guide.
  • If you want to extend or add new functionality to STEM, including new disease and computational models, you need to build STEM from source. See the Setting up a STEM Development Environment page for more instructions.

Prerequisites

STEM is a Java application built on top of the Eclipse Rich Client Platform (RCP). To run STEM, please verify you have the following prerequisites installed:

  1. A workstation running an Eclipse-supported operating system:
    • Windows (XP, Vista, 7)
    • Linux (GTK)
    • Mac OS X (10.5 or later)
    • A supported Java Standard Edition from either Oracle (Sun) or IBM
  2. For STEM V3.0.0M1 or above the minimum requirement is (J2SE) 8.0 JVM
    Oracle Java SE 8.0 (JRE8U65 or higher)
  3. For STEM V 2.0.x or earlier
    (J2SE) 6.0 JVM
    Oracle Java SE 6.0 (6.0.26 or higher)
    IBM Java SE 6.0
    • Note: Mac OS X users can use the version included with the operating system
    • Note: The GNU for Java (GCJ) compiler and libraries are not supported. If you're running on Linux, it's strongly recommended you use an Oracle or IBM JRE
    • Note: While STEM V2.0.x should work with Java 7, it is not tested or supported at this time. STEM V3.0.x is is based on Eclipse 4.x and requires Java 8
  4. A tool to extract zipped archives
    Most operating systems have this built-in, although Windows users may wish to install a standalone utility like 7-Zip

Which File To Download?

The STEM Project publishes several different binary versions of the application. Please consider these options when choosing which to download.

32-bit vs. 64-bit

Most modern operating systems from 2009 and on support 64-bit (x86_64) compiled binaries. The 64-bit version of STEM can take advantage of larger memory spaces (beyond 2 GB), which is necessary to run very large (global) simulations.

The STEM project publishes both 32-bit (x86) and 64-bit (x86_64) versions of the application for each supported operating system. The version you download strictly depends on whether you have a 32-bit or 64-bit Java Runtime Environment (JRE) installed. If you have a 64-bit JRE installed, download the x86_64 version. Otherwise, download the x86 version.

Some 64-bit JREs can run in 32-bit mode. Please see your JRE's documentation for instructions.

Release, Milestone, or Integration Builds

The best version of STEM to download is generally the latest Release. In addition to being fully tested and stable, it's approved for distribution by the Eclipse Foundation and subject to the terms of the Eclipse Software User Agreement and the Eclipse Public License.

However, power users or those looking for the latest features may choose to download the latest Weekly Integration, Milestone, or Release Candidate build. These builds may not be stable and are not sanctioned by the Eclipse Foundation. Use at your own risk.

Downloading and Installing STEM

The STEM application is bundled as a platform-specific, zipped archive and does not contain an installer. To install STEM, download the appropriate bundle and unzip it to your desired installation path.

The STEM installation path cannot contain whitespace characters. Ensure that the install path contains no spaces, tabs, etc.

If you already have STEM 1.4 or newer installed and wish to upgrade, see the STEM Updates section.

  1. In your browser, go to the STEM Downloads page
  2. Choose the appropriate bundle to download (see previous section for help) and click the link
  3. On the mirrors page, select a nearby mirror site. This will begin the download.
  4. If prompted, choose to Save the file. Note where the file is downloading to.
    On some systems, the browser may automatically execute (unzip) the file when it finishes downloading. If this is the case, skip to step 8 when the download finishes.
  5. Wait while the STEM bundle downloads...
    Note: STEM is approximately 150 MB in size. Depending on your connection and mirror speeds, the download will take from a few minutes to an hour or more.
  6. When the download finishes, open the folder where the downloaded file sits
  7. Extract/unzip the STEM archive
    Note: On most systems, double clicking the the .zip file will automatically extract it.
  8. Extracting the archive should create a folder called stem. Move this folder to the path you wish to install STEM at.
    IMPORTANT REMINDER: Verify that the install path does not contain whitespace or non-ASCII characters, including spaces, tabs, etc.
    • Windows users may want to place stem folder in a drive root. Example is c:\stem
    • Mac OS X users may want to place the stem folder in the Applications folder
  9. Optionally, you can create a shortcut on your desktop, start menu, dock, etc to quickly launch STEM
  10. Increasing the system memory available to STEM. Some large scenarios (e.g. with thousands of nodes and edges), require that you make sure you allocate enough system memory for STEM. If you don't do this the application may hang or crash with a "Heap Space" error. To allocate enough memory in Windows, create a shortcut for launching STEM. You may place this anywhere (e.g., on your desktop or on the quicklaunch bar).
    • Right click on the shortcut. Select "Properties" You should see a field in the Properties Dialogue labeled Target: to the right in the text field you will see something like:
    C:\stem_builds\stem\STEM.exe -vmargs -Xms812M -Xmx812M
    • To launch STEM with more memory you must add "virtual machine arguments" to the target line. For example, to set the min heap size to 1 GB and max heap size to 4GB use:
    C:\stem_builds\stem\STEM.exe -vmargs -Xms1024M -Xmx4096M
    • On MAC OS X, using the finder, navigate to where the STEM application is located, right click and select "Show Package Content". Navigate to Contents->MacOS and open the STEM.ini file in an editor. Change the -Xms and the -Xmx lines to increase the memory, e.g. -Xms1024M -Xmx4096M or more depending on how much memory is available.


That's it! STEM is now installed. See the next section for instructions to launch STEM.

Launching and Running STEM

After STEM is unzipped and placed in the install folder, you can launch the application. STEM can run both with a full Graphical User Interface (GUI) or "headlessly" in a text-only console. For more information about the text-only option, see the headless STEM article.

  1. Navigate to the folder STEM is installed in
  2. Double click the STEM executable file
    STEM-Install-FinderView.png
    • For Windows, the file is named STEM.exe
    • For Mac OS X, the file is named STEM or STEM.app
    • For Linux, the file is named STEM
  3. On some system, you may get a security warning about launching a downloaded application. Click OK or Open
    Note: This warning message varies depending on your operating system
    STEM-Install-DownloadedApplicationWarning.png
  4. The STEM splash screen should immediately appear
    STEM-Install-Splash.png
  5. The first time STEM is launched, several configuration tasks have to run in the background
    These tasks may take 1-2 minutes depending on system speed. During this time, only the splash screen is displayed.
  6. When STEM finishes loading, the workbench will launch the Simulation perspective
    The first time you run STEM, the Welcome to STEM screen will display. You can close this by click the X on the Welcome tab.
    STEM-Install-WelcomeScreen.png
  7. Congratulations! STEM is loaded and ready to use
    STEM-Install-Workbench.png
  8. To get started using STEM, start by going through the tutorials on the STEM Documentation page
    You may find it helpful to watch the YouTube tutorial before you go on to learn to create a scenario

Installing Additional STEM Features

See section on STEM Add-ons

STEM uses the Automated Eclipse Updates to make it easier for users to install additional features to STEM. Today, one feature you may want to add is the Earth Science data plugin that contains global climate data for the years 2001-2010. This plugin is required, for example, if you want to use the Anopheles Mosquito model.

See the main article for instructions on how to install new features into STEM.

Updating STEM

Starting with version 1.4, you can use the update mechanism built into STEM to perform upgrades without re-downloading the full installation bundle. Most of the time, this means you don't have to re-download the large denominator data sets packaged in STEM or have to export and import your scenarios.

PLEASE NOTE. STEM V2.0.x and earlier are based on Eclipse 3.x The Latest versions of STEM beginning with STEM V 3.0.0M1 are base on Eclipse 4.x and therefore require that Java 8 be installed. 
Please see system requirements above. The following procedure will not update your Java installation. This must be done first.
  1. Verify the computer is connected to a network and launch STEM
    If STEM is already open, save all edited files and stop any running simulations
  2. Open the Help Menu and choose Check for Updates
    STEM-Update-CheckForUpdatesMenu.png
  3. Wait while STEM contacts the updates server and checks for new versions
    • If no updates are available, a message saying No updates were found will appear. Click OK to return to STEM
    • If an update is available, the Available Updates wizard will appear
  4. On the Available Updates page, verify STEM is selected, and click Next
    STEM-Update-AvailableUpdates.png
  5. Verify the list of items to be installed is correct and click Next
  6. Review the the licenses of the software being installed to verify you still accept
    If you accept the terms, select I Accept the terms of the license agreements and click Finish
    If you do not accept the terms, click Cancel
  7. Wait while STEM downloads and installs the updates
  8. If prompted with a security warning about installing unsigned software, click OK
  9. When prompted to apply changes, verify all open files are saved and click Restart Now
  10. STEM should automatically restart. If not, relaunch it manually

Checking the Version of STEM Installed

After updating STEM, the version displayed on the splash screen at startup may not change to reflect the new version. To verify STEM updated successfully, check the STEM Installation Details.

  1. Open the Help menu and select About STEM
  2. Click Installation Details
  3. In the STEM Installation Details dialog, verify the installed version for STEM
    STEM-Update-InstalledDetailsVersion.png

Updating to Latest Integration or Milestone Build

By default, the STEM update feature only checks for the latest, official release approved by the Eclipse Foundation. However, users will often want to take advantage of new features published in weekly integration and/or periodic milestone and release candidate builds. You can easily configure STEM to download and install these updates.

  1. Launch STEM
  2. Open the Window menu and select Preferences
    On Mac OS X, Preferences is under the STEM menu
  3. In the Preferences window, expand Install/Update and select Available Software Sites
  4. Under Available Software Sites, click Add
  5. In the Add Site dialog, enter the appropriate Name and Location
    For weekly integration builds:
    • Name: STEM Integration Builds
    • Location: http://download.eclipse.org/stem/update-site/integration/
    For periodic milestone and release candidate builds:
    • Name: STEM Stable Builds
    • Location: http://download.eclipse.org/stem/update-site/stable/
  6. Click OK to add the site
  7. Click OK to save Preferences and return to STEM
  8. Follow the steps in the previous section to update STEM
  9. To disable checking for non-release versions, disable or remove the sites added to the Available Software Sites list

Setting up the STEM Development Environment in Eclipse

If you might contribute to STEM development or if you want to always have the most recent code, then you will need to install Eclipse.

Go to tutorial on Setting up a STEM Development Environment

Back to the top