Skip to main content
Skip table of contents

2.19.0

Release date: October 04 2022

New features

RBRtridente

RBR's new RBRtridente multi-channel optical sensor is now fully integrated into Ruskin. Connect your sensor to change its sampling speed and record data in real-time.

Did you know?

You can simulate a sensor even if you don't yet have one. Ruskin lets you simulate the RBRtridente as a standalone sensor or as part of a larger integration. We've updated Ruskin's autonomy engine to let you easily plan deployments using this tool too.

Other notable additions
  • Added RBR Instrument Guide (RIG) for RBRquartz3 APT and Standard instruments
  • Added Quick Start Guide (QSG) for RBRquartz3 APT
  • Updated Quick Start Guide (QSG)for RBRfermata
  • Updated Ruskin User Guide (RUG)for RBRcoda3, Compact instruments, and Standard instruments

Improvements

  • RSK-6356 - Added link to release notes to get full history
  • RSK-7886 - Added copy/paste functionality to RBRquartz3 calibration coefficient tables
  • RSK-8672 - Added channel indices to RSK analysis data table
  • RSK-8703 - Removed column auto-sizing on Excel exports
  • RSK-8756 - Release notes window was renamed from 'Welcome' to 'Release notes'
  • RSK-8762 - Added dialog to view all user activated feature codes
  • RSK-8941 - Added temperature channel to the simulations of Rinko III sensors

Bug fixes

  • RSK-7836 - Point GPS annotations are not exported in NetCDF format
  • RSK-8527 - Ruskin tries to set times outside of instrument clock range
  • RSK-8559 - Event annotations aren't always mapping to the correct channels
  • RSK-8694 - RSK overview doesn't always indicate the correct sampling mode used in the deployment
  • RSK-8773 - 'Comment on Ruskin' dialog colours are not consistent
  • RSK-8775 - Language selection on General preference page has incorrectly displays non standard characters
  • RSK-9002 - Output data format should not be configured while instrument is enabled
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.