Release 1.15.09 January 2017



  1. Bug 306. Certain methods have been querying AcousticDataUnit.getDuration and expecting to receive a response in milliseconds. However, getDuration actually returns the number of samples.  This has been corrected.


A major change in this version of PAMGuard is how plug-ins are managed. PAMGuard now has the ability to dynamically load plug-in modules (saved as jar files) at runtime. This will greatly simplify the process of testing and distributing newly developed modules, since only a small jar file will be required rather than a new bespoke PAMGuard installation.

Module code development remains largely unchanged, in most cases simply requiring the addition of an interface class.  Instructions for the development of new modules utilizing the plug-in scheme can be found here.  Plug-in modules can be downloaded from the PAMGuard website here, but developers are encouraged to host and maintain their own modules.

Modules of interest to the general PAM community will remain as part of the core PAMGuard installation. However, specialized modules which are useful to only a small number of users have been removed and are available as a separate download. The following modules have been removed:

  1. Resource Monitor
  2. WILD ArcGIS Interface
  3. Workshop Demo Detector
  4. Echo Detector and IPI Demo (bundled together, due to dependencies)

Other Changes

The installer has been updated to handle both 64 bit and 32 bit installations. PAMGuard psf files are now registered in the Windows Registry, so double-clicking on a psf file should run PAMGuard in normal mode (as opposed to Viewer or Mixed modes). Note that the Windows Registry can only hold a single executable reference for psf files; therefore, for users with multiple installations of PAMGuard, double-clicking on a psf will run the most-recently installed version of PAMGuard on the system.