SSDS Processing Report for data sets from Deployment 2025.203.00 Processing began at 2025-07-23T20:57:47Z Going to try to convert any outputs of deployment 2025.203.00 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 9 of them) Going to try to convert any outputs of deployment ctdDriver to NetCDF files: - Working on output ctdDriver.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver.nc - Starting the NetCDF creation at 2025-07-23T20:57:48Z - NetCDF creation finished at 2025-07-23T20:57:51Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:57:48Z(start date = 2025-07-23T20:57:48Z, end date = 2025-07-23T20:57:51Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be ctdDriver.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:06:43Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:55:11Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 34293606. - UpdateBot DataProducer persisted and has ID 53553. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_1703828370 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_18035132 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_2053690853 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_2074729044 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_341401926 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 53546. Going to try to convert any outputs of deployment ctdDriver2 to NetCDF files: - Working on output ctdDriver2.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver2.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver2.nc - Starting the NetCDF creation at 2025-07-23T20:57:51Z - NetCDF creation finished at 2025-07-23T20:57:54Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver2.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:57:51Z(start date = 2025-07-23T20:57:51Z, end date = 2025-07-23T20:57:54Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be ctdDriver2.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver2.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:07:15Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:55:11Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 34281309. - UpdateBot DataProducer persisted and has ID 53554. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_1112180281 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_1496300861 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_412846558 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 53540. Going to try to convert any outputs of deployment dvl to NetCDF files: - Working on output dvl.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dvl.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dvl.nc - Starting the NetCDF creation at 2025-07-23T20:57:55Z - NetCDF creation finished at 2025-07-23T20:57:56Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dvl.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:57:55Z(start date = 2025-07-23T20:57:55Z, end date = 2025-07-23T20:57:56Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be dvl.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dvl.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:06:24Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:54:39Z to the end date of dvl.log. - Set the content length of dvl.log to 9667951. - UpdateBot DataProducer persisted and has ID 53555. - Deployment dvl was changed and persisted to the database with ID 53538. Going to try to convert any outputs of deployment dynamicControl to NetCDF files: - Working on output dynamicControl.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dynamicControl.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dynamicControl.nc - Starting the NetCDF creation at 2025-07-23T20:57:56Z - NetCDF creation finished at 2025-07-23T20:58:13Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dynamicControl.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:57:56Z(start date = 2025-07-23T20:57:56Z, end date = 2025-07-23T20:58:13Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be dynamicControl.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dynamicControl.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:07:08Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:55:11Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 138388958. - UpdateBot DataProducer persisted and has ID 53556. - Deployment dynamicControl was changed and persisted to the database with ID 53539. Going to try to convert any outputs of deployment gps to NetCDF files: - Working on output gps.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/gps.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/gps.nc - Starting the NetCDF creation at 2025-07-23T20:58:14Z - NetCDF creation finished at 2025-07-23T20:58:14Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/gps.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:58:14Z(start date = 2025-07-23T20:58:14Z, end date = 2025-07-23T20:58:14Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be gps.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/gps.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:06:18Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:55:11Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.68895183333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.81012750000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81935483333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.3768971666667 to the max longitude of gps.log. - Set the content length of gps.log to 629276. - UpdateBot DataProducer persisted and has ID 53557. - Deployment gps was changed and persisted to the database with ID 53552. Going to try to convert any outputs of deployment hydroscatlog to NetCDF files: - Working on output hydroscatlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/hydroscatlog.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/hydroscatlog.nc - Starting the NetCDF creation at 2025-07-23T20:58:14Z - NetCDF creation finished at 2025-07-23T20:58:17Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/hydroscatlog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:58:14Z(start date = 2025-07-23T20:58:14Z, end date = 2025-07-23T20:58:17Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be hydroscatlog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/hydroscatlog.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:06:25Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:55:11Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 29997178. - UpdateBot DataProducer persisted and has ID 53558. - Deployment hydroscatlog was changed and persisted to the database with ID 53544. Going to try to convert any outputs of deployment navigation to NetCDF files: - Working on output navigation.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/navigation.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/navigation.nc - Starting the NetCDF creation at 2025-07-23T20:58:18Z - NetCDF creation finished at 2025-07-23T20:58:39Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/navigation.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:58:18Z(start date = 2025-07-23T20:58:18Z, end date = 2025-07-23T20:58:39Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be navigation.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/navigation.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:07:09Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:55:11Z to the end date of navigation.log. - Set the content length of navigation.log to 173210360. - UpdateBot DataProducer persisted and has ID 53559. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_1299156891 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_1567479835 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-07-23T20:57:42Z_741638719 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 53533. Going to try to convert any outputs of deployment parosci to NetCDF files: - Working on output parosci.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/parosci.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/parosci.nc - Starting the NetCDF creation at 2025-07-23T20:58:40Z - NetCDF creation finished at 2025-07-23T20:58:45Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/parosci.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:58:40Z(start date = 2025-07-23T20:58:40Z, end date = 2025-07-23T20:58:45Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be parosci.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/parosci.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:06:33Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:55:11Z to the end date of parosci.log. - Since a min depth was found in the NetCDF file, will assign 0.0 to the min depth of parosci.log. - Since a max depth was found in the NetCDF file, will assign 203.15723 to the max depth of parosci.log. - Set the content length of parosci.log to 42668006. - UpdateBot DataProducer persisted and has ID 53560. - Deployment parosci was changed and persisted to the database with ID 53537. Going to try to convert any outputs of deployment tailCone to NetCDF files: - Working on output tailCone.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/tailCone.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/tailCone.nc - Starting the NetCDF creation at 2025-07-23T20:58:45Z - NetCDF creation finished at 2025-07-23T20:58:48Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/tailCone.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2025-07-23T20:58:45Z(start date = 2025-07-23T20:58:45Z, end date = 2025-07-23T20:58:48Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be tailCone.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/tailCone.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2025/2025203/2025.203.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-07-22T17:06:29Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2025-07-23T17:54:42Z to the end date of tailCone.log. - Set the content length of tailCone.log to 21430791. - UpdateBot DataProducer persisted and has ID 53561. - Deployment tailCone was changed and persisted to the database with ID 53545. - Deployment 2025.203.00 was changed and persisted to the database with ID 53532. Processing for deployment 2025.203.00 ended at 2025-07-23T20:58:48Z