SSDS Processing Report for data sets from Deployment 2025.161.00 Processing began at 2025-06-11T20:51:54Z Going to try to convert any outputs of deployment 2025.161.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/2025161/2025.161.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/2025161/2025.161.00/ctdDriver.nc - Starting the NetCDF creation at 2025-06-11T20:51:54Z - NetCDF creation finished at 2025-06-11T20:51:59Z - 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/2025161/2025.161.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-06-11T20:51:54Z(start date = 2025-06-11T20:51:54Z, end date = 2025-06-11T20:51:59Z). - 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/2025161/2025.161.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/2025161/2025.161.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:55:07Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 34892838. - UpdateBot DataProducer persisted and has ID 53485. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_1565936348 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_1775964617 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_1982062082 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_304928353 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_470765721 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 53477. 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/2025161/2025.161.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/2025161/2025.161.00/ctdDriver2.nc - Starting the NetCDF creation at 2025-06-11T20:52:00Z - NetCDF creation finished at 2025-06-11T20:52:04Z - 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/2025161/2025.161.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-06-11T20:52:00Z(start date = 2025-06-11T20:52:00Z, end date = 2025-06-11T20:52:04Z). - 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/2025161/2025.161.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/2025161/2025.161.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:55:38Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 34880541. - UpdateBot DataProducer persisted and has ID 53486. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_1158492601 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_1923673647 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_247908930 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 53473. 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/2025161/2025.161.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/2025161/2025.161.00/dvl.nc - Starting the NetCDF creation at 2025-06-11T20:52:04Z - NetCDF creation finished at 2025-06-11T20:52:06Z - 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/2025161/2025.161.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-06-11T20:52:04Z(start date = 2025-06-11T20:52:04Z, end date = 2025-06-11T20:52:06Z). - 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/2025161/2025.161.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/2025161/2025.161.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:54:48Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:07:00Z to the end date of dvl.log. - Set the content length of dvl.log to 9749871. - UpdateBot DataProducer persisted and has ID 53487. - Deployment dvl was changed and persisted to the database with ID 53472. 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/2025161/2025.161.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/2025161/2025.161.00/dynamicControl.nc - Starting the NetCDF creation at 2025-06-11T20:52:07Z - NetCDF creation finished at 2025-06-11T20:52: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/2025161/2025.161.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-06-11T20:52:07Z(start date = 2025-06-11T20:52:07Z, end date = 2025-06-11T20:52:23Z). - 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/2025161/2025.161.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/2025161/2025.161.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:55:32Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 140808818. - UpdateBot DataProducer persisted and has ID 53488. - Deployment dynamicControl was changed and persisted to the database with ID 53471. 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/2025161/2025.161.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/2025161/2025.161.00/gps.nc - Starting the NetCDF creation at 2025-06-11T20:52:23Z - NetCDF creation finished at 2025-06-11T20:52:24Z - 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/2025161/2025.161.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-06-11T20:52:23Z(start date = 2025-06-11T20:52:23Z, end date = 2025-06-11T20:52:24Z). - 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/2025161/2025.161.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/2025161/2025.161.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:54:42Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.69110733333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80576200000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81690600000005 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.37731083333337 to the max longitude of gps.log. - Set the content length of gps.log to 704660. - UpdateBot DataProducer persisted and has ID 53489. - Deployment gps was changed and persisted to the database with ID 53484. 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/2025161/2025.161.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/2025161/2025.161.00/hydroscatlog.nc - Starting the NetCDF creation at 2025-06-11T20:52:25Z - NetCDF creation finished at 2025-06-11T20:52:28Z - 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/2025161/2025.161.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-06-11T20:52:25Z(start date = 2025-06-11T20:52:25Z, end date = 2025-06-11T20:52:28Z). - 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/2025161/2025.161.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/2025161/2025.161.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:54:48Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 30521758. - UpdateBot DataProducer persisted and has ID 53490. - Deployment hydroscatlog was changed and persisted to the database with ID 53466. 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/2025161/2025.161.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/2025161/2025.161.00/navigation.nc - Starting the NetCDF creation at 2025-06-11T20:52:28Z - NetCDF creation finished at 2025-06-11T20:52: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/2025161/2025.161.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-06-11T20:52:28Z(start date = 2025-06-11T20:52:28Z, end date = 2025-06-11T20:52:48Z). - 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/2025161/2025.161.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/2025161/2025.161.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:55:32Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z to the end date of navigation.log. - Set the content length of navigation.log to 176239088. - UpdateBot DataProducer persisted and has ID 53491. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_1408719731 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_1612890648 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-06-11T20:51:48Z_766310489 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 53467. 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/2025161/2025.161.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/2025161/2025.161.00/parosci.nc - Starting the NetCDF creation at 2025-06-11T20:52:49Z - NetCDF creation finished at 2025-06-11T20:52:53Z - 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/2025161/2025.161.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-06-11T20:52:49Z(start date = 2025-06-11T20:52:49Z, end date = 2025-06-11T20:52:53Z). - 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/2025161/2025.161.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/2025161/2025.161.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:54:57Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z 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.01642 to the max depth of parosci.log. - Set the content length of parosci.log to 43413974. - UpdateBot DataProducer persisted and has ID 53492. - Deployment parosci was changed and persisted to the database with ID 53465. 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/2025161/2025.161.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/2025161/2025.161.00/tailCone.nc - Starting the NetCDF creation at 2025-06-11T20:52:54Z - NetCDF creation finished at 2025-06-11T20:52: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/2025161/2025.161.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-06-11T20:52:54Z(start date = 2025-06-11T20:52:54Z, end date = 2025-06-11T20:52:56Z). - 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/2025161/2025.161.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/2025161/2025.161.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-06-10T17:54:52Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2025-06-11T19:09:36Z to the end date of tailCone.log. - Set the content length of tailCone.log to 21812103. - UpdateBot DataProducer persisted and has ID 53493. - Deployment tailCone was changed and persisted to the database with ID 53483. - Deployment 2025.161.00 was changed and persisted to the database with ID 53464. Processing for deployment 2025.161.00 ended at 2025-06-11T20:52:57Z