Release 2.1.5

MOOS

• Bug fix for "register_time" in GobyMOOSApp to allow use with MOOSTimeWarp #15
• Bug fix for "inverse_publish" in moos_translators #14
• Cleanups for Dependencies list.

See 2.1.4...2.1.5

Release 2.1.4

MOOS

• Added function "register_timer" to GobyMOOSApp to allow for low frequency (<AppTick) register events. Ofter it is usual to do something every 10 sec, every 60 sec, etc. This functionality simplifies doing so.

See 2.1.3...2.1.4

Release 2.1.3

This release contains minor bug fixes.

See 2.1.2a...2.1.3

Minor fixes to 2.1.2 release

2.1.2a

Removed stray header in HDF5 plugin test

Release 2.1.2

Version 2.1.2

Acomms

• Improved support for Flexible Data Packet (FDP) in Micro-Modem 2. Now supports both mini-packet and full packets (previ
  ously only mini-packets were supported), and an optional application acknowledgment is available that can be used to get
  acks from FDP messages.
• Added ability to update MicroModem NVRAM configuration while driver is running, rather than just at initialization.
• Added option for MACManager to use a fixed reference (in Unix time) rather than the start of the current day).
• Fix to set RTS line low to avoid garbled messages with the MicroModem2 in Linux.
• (experimental). New goby_ip_gateway application: Linux tun interface to ease sending of IP/UDP datagrams over Goby.

PB

• Added new tool (goby_hdf5) for converting Google Protocol Buffers (protobuf) logs into an HDF5 file (https://www.hdfgroup.org/HDF5/) suitable for easy data analysis by common scientific tools such as MATLAB, Octave, and Python. This tool is extensible to work on any format log that stores protobuf messages by a plugin interface, where the plugin is responsible for reading and parsing the protobuf log and providing Messages to goby_hdf5 to process. An example plugin is given in goby/src/test/common/hdf5/test-plugin.cpp. See Github #8.

Compiling

• Various improvements to the build system. See Github #12.
  • All compiled objects (binaries, libraries, etc.) are now stored in subdirectories of the ${CMAKE_BINARY_DIR} (defaults to goby/build when using the build.sh script), and symlinks are created from goby/lib, goby/bin, goby/include, and goby/share to the actual built directories. This makes the out-of-source build more proper, and thus all autogenerated code can by removed by simply removing the contents of ${CMAKE_BINARY_DIR} (e.g. rm -r goby/build/*)
  • Added support for CMake's install(EXPORT) and export(...) functions that produces a file (goby-config.cmake) that makes it easier for a project dependent on Goby to find the Goby libraries and include the appropriate headers.

Bug fixes

Various bug fixes. See 2.1.1...2.1.2

Release 2.1.1

This is the first release in the 2.1 series.

Goby 2.1 is a new release series primarily since it uses the standalone DCCL3 release instead of including DCCL in the libgoby_acomms library. The old API to DCCL remains in Goby 2.1 to allow easy transition from Goby 2.0 to 2.1. One exception: users of Google Protocol Buffers versions prior to 2.5.0 will need to change all DCCL .proto files to import the DCCL extensions .proto instead of the Goby one. That is:
From:
import "goby/acomms/protobuf/dccl_option_extensions.proto";
To:
import "dccl/protobuf/option_extensions.proto";

If you're using Google Protobuf 2.5.0 or newer, no changes should be necessary to use Goby 2.1.

In addition to this change and numerous bug fixes, a new IridiumDriver that fully supports Iridium Short Burst Data and RUDICS is included in Goby 2.1.