As I mentioned in my last post the next incremental version of OpenVDM is going to include hooks that will allow vessel operators to leverage OpenVDM for automatically executing their own custom data QA/QC and processing software exactly when those custom programs need to be run. In this post I’ll explain how that works.
The short trip out on the R/V Endeavor was a huge success. After leaving the dock and going to the VSAT internet connection I was able to quickly identify and squash a long-standing yet elusive bug in the ship-to-shore transfer code. I also discovered (and promptly squashed) quite a few minor bugs within OpenVDMv2, none of which had appeared in my development environment.
Up until now almost all developments on the new user-interface and under-the-hood improvements with OpenVDMv2 have been centered around software and a web-interface installed shipboard. And while OpenVDMv2 provides mechanism for getting data off the vessel, not as much effort has been made to provide a slick portal for accessing that data on shore… until now.