Skip to content

Releases: opensha/opensha

OpenSHA Version 1.5.2

03 Jun 23:28
Choose a tag to compare

OpenSHA application release. See the OpenSHA website for more information.

This release is copied over and is the final release from the old repository.

Note: A 64-bit version of Java 8 (aka 1.8) or above is required.

First download the jar file[s] of interest. Some users may be able to launch them by simply double clicking on the jar file in a file browser. If this doesn't work, you will need to launch it in a terminal:

java -jar /path/to/jarFile.jar

For example, if I'm in a directory containing HazardCurveGUI-1.5.2.jar and want to run it:

java -jar HazardCurveGUI-1.5.1.jar

If you see any error messages related to "OutOfMemoryException" or java "heap size", or the app stalls when loading a large model (e.g. UCERF3), you'll need to allocate more memory to java. You can do this most easily with the -Xmx argument. For example, to run with 4 GB of memory:

java -Xmx4G -jar HazardCurveGUI-1.5.1.jar

Non-executable library jar files of builds of the OpenSHA code are also supplied:

  • opensha-apps.jar: Class files and resources from the opensha-apps project, not including any upstream dependencies
  • opensha-apps-all.jar: 'Fat' jar file containing class files and resources from this and upstream projects, including all dependencies

Release notes:

New to 1.5.2:

  • Improved chances that out of memory exceptions are successfully caught and show a useful error message to users. Also added memory information to bug reports.
  • Cleaned out some necessary data files

Previous (1.5.1):

  • Release is now from a maintenance branch in each repository: release-v<major.version>-<minor.version>
  • Tomcat server preferences updated such that apps talk to servlets built at release time, rather than being built from master
  • Bug reports now put the root cause of a stack track at the top, as long exceptions may be truncated
  • UCERF3 ERFs now detect corrupted/truncated data files from failed earlier downloads, and prompt the user to delete and re-download (for #6)