SSDS Processing Report for data sets from Deployment 2025.008.00 Processing began at 2025-01-09T19:47:22Z Going to try to convert any outputs of deployment 2025.008.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/2025008/2025.008.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/2025008/2025.008.00/ctdDriver.nc - Starting the NetCDF creation at 2025-01-09T19:47:23Z - NetCDF creation finished at 2025-01-09T19:47:25Z - 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/2025008/2025.008.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-01-09T19:47:23Z(start date = 2025-01-09T19:47:23Z, end date = 2025-01-09T19:47:25Z). - 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/2025008/2025.008.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/2025008/2025.008.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:07:39Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:44:19Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 35404038. - UpdateBot DataProducer persisted and has ID 53356. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_2115873646 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_248863527 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_322283526 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_488258001 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_64834095 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 53349. 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/2025008/2025.008.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/2025008/2025.008.00/ctdDriver2.nc - Starting the NetCDF creation at 2025-01-09T19:47:26Z - NetCDF creation finished at 2025-01-09T19:47:29Z - 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/2025008/2025.008.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-01-09T19:47:26Z(start date = 2025-01-09T19:47:26Z, end date = 2025-01-09T19:47:29Z). - 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/2025008/2025.008.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/2025008/2025.008.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:08:11Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:44:19Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 35391645. - UpdateBot DataProducer persisted and has ID 53357. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_1221440353 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_1331915755 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_554666662 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 53345. 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/2025008/2025.008.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/2025008/2025.008.00/dvl.nc - Starting the NetCDF creation at 2025-01-09T19:47:30Z - NetCDF creation finished at 2025-01-09T19:47:31Z - 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/2025008/2025.008.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-01-09T19:47:30Z(start date = 2025-01-09T19:47:30Z, end date = 2025-01-09T19:47:31Z). - 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/2025008/2025.008.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/2025008/2025.008.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:07:21Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:42:53Z to the end date of dvl.log. - Set the content length of dvl.log to 9979239. - UpdateBot DataProducer persisted and has ID 53358. - Deployment dvl was changed and persisted to the database with ID 53355. 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/2025008/2025.008.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/2025008/2025.008.00/dynamicControl.nc - Starting the NetCDF creation at 2025-01-09T19:47:32Z - NetCDF creation finished at 2025-01-09T19:47: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/2025008/2025.008.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-01-09T19:47:32Z(start date = 2025-01-09T19:47:32Z, end date = 2025-01-09T19:47:45Z). - 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/2025008/2025.008.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/2025008/2025.008.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:08:05Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:44:19Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 142871558. - UpdateBot DataProducer persisted and has ID 53359. - Deployment dynamicControl was changed and persisted to the database with ID 53336. 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/2025008/2025.008.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/2025008/2025.008.00/gps.nc - Starting the NetCDF creation at 2025-01-09T19:47:46Z - NetCDF creation finished at 2025-01-09T19:47:46Z - 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/2025008/2025.008.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-01-09T19:47:46Z(start date = 2025-01-09T19:47:46Z, end date = 2025-01-09T19:47:46Z). - 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/2025008/2025.008.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/2025008/2025.008.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:07:15Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:44:19Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.68751316666668 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80682050000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.82213033333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.37598700000002 to the max longitude of gps.log. - Set the content length of gps.log to 931244. - UpdateBot DataProducer persisted and has ID 53360. - Deployment gps was changed and persisted to the database with ID 53342. 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/2025008/2025.008.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/2025008/2025.008.00/hydroscatlog.nc - Starting the NetCDF creation at 2025-01-09T19:47:47Z - NetCDF creation finished at 2025-01-09T19:47:50Z - 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/2025008/2025.008.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-01-09T19:47:47Z(start date = 2025-01-09T19:47:47Z, end date = 2025-01-09T19:47:50Z). - 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/2025008/2025.008.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/2025008/2025.008.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:07:21Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:44:19Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 30968470. - UpdateBot DataProducer persisted and has ID 53361. - Deployment hydroscatlog was changed and persisted to the database with ID 53341. 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/2025008/2025.008.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/2025008/2025.008.00/navigation.nc - Starting the NetCDF creation at 2025-01-09T19:47:51Z - NetCDF creation finished at 2025-01-09T19:48: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/2025008/2025.008.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-01-09T19:47:51Z(start date = 2025-01-09T19:47:51Z, end date = 2025-01-09T19:48:13Z). - 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/2025008/2025.008.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/2025008/2025.008.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:08:05Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:44:19Z to the end date of navigation.log. - Set the content length of navigation.log to 178820840. - UpdateBot DataProducer persisted and has ID 53362. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_1017734443 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_1323825195 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-01-09T19:47:16Z_1794423412 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 53337. 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/2025008/2025.008.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/2025008/2025.008.00/parosci.nc - Starting the NetCDF creation at 2025-01-09T19:48:14Z - NetCDF creation finished at 2025-01-09T19:48:19Z - 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/2025008/2025.008.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-01-09T19:48:14Z(start date = 2025-01-09T19:48:14Z, end date = 2025-01-09T19:48:19Z). - 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/2025008/2025.008.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/2025008/2025.008.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:07:30Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:44:19Z 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.23848 to the max depth of parosci.log. - Set the content length of parosci.log to 44049830. - UpdateBot DataProducer persisted and has ID 53363. - Deployment parosci was changed and persisted to the database with ID 53344. 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/2025008/2025.008.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/2025008/2025.008.00/tailCone.nc - Starting the NetCDF creation at 2025-01-09T19:48:20Z - NetCDF creation finished at 2025-01-09T19:48:23Z - 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/2025008/2025.008.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-01-09T19:48:20Z(start date = 2025-01-09T19:48:20Z, end date = 2025-01-09T19:48:23Z). - 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/2025008/2025.008.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/2025008/2025.008.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-01-08T16:07:25Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2025-01-09T17:43:25Z to the end date of tailCone.log. - Set the content length of tailCone.log to 22118919. - UpdateBot DataProducer persisted and has ID 53364. - Deployment tailCone was changed and persisted to the database with ID 53343. - Deployment 2025.008.00 was changed and persisted to the database with ID 53335. Processing for deployment 2025.008.00 ended at 2025-01-09T19:48:23Z