SSDS Processing Report for data sets from Deployment 2025.139.04 Processing began at 2025-05-21T15:47:15Z Going to try to convert any outputs of deployment 2025.139.04 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/2025139/2025.139.04/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/2025139/2025.139.04/ctdDriver.nc - Starting the NetCDF creation at 2025-05-21T15:47:15Z - NetCDF creation finished at 2025-05-21T15:47:18Z - 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/2025139/2025.139.04/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-05-21T15:47:15Z(start date = 2025-05-21T15:47:15Z, end date = 2025-05-21T15:47:18Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:32Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 33759078. - UpdateBot DataProducer persisted and has ID 53450. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_14181830 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_1805548176 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_2032562940 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_708918848 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_94686094 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 53442. 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/2025139/2025.139.04/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/2025139/2025.139.04/ctdDriver2.nc - Starting the NetCDF creation at 2025-05-21T15:47:19Z - NetCDF creation finished at 2025-05-21T15:47:22Z - 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/2025139/2025.139.04/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-05-21T15:47:19Z(start date = 2025-05-21T15:47:19Z, end date = 2025-05-21T15:47:22Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:32Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 33758973. - UpdateBot DataProducer persisted and has ID 53451. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_1359379053 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_485768116 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_775284439 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 53436. 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/2025139/2025.139.04/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/2025139/2025.139.04/dvl.nc - Starting the NetCDF creation at 2025-05-21T15:47:23Z - NetCDF creation finished at 2025-05-21T15:47: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/2025139/2025.139.04/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-05-21T15:47:23Z(start date = 2025-05-21T15:47:23Z, end date = 2025-05-21T15:47:24Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:13Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:06Z to the end date of dvl.log. - Set the content length of dvl.log to 9520499. - UpdateBot DataProducer persisted and has ID 53452. - Deployment dvl was changed and persisted to the database with ID 53435. 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/2025139/2025.139.04/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/2025139/2025.139.04/dynamicControl.nc - Starting the NetCDF creation at 2025-05-21T15:47:25Z - NetCDF creation finished at 2025-05-21T15:47:38Z - 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/2025139/2025.139.04/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-05-21T15:47:25Z(start date = 2025-05-21T15:47:25Z, end date = 2025-05-21T15:47:38Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:58Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 136229808. - UpdateBot DataProducer persisted and has ID 53453. - Deployment dynamicControl was changed and persisted to the database with ID 53441. 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/2025139/2025.139.04/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/2025139/2025.139.04/gps.nc - Starting the NetCDF creation at 2025-05-21T15:47:39Z - NetCDF creation finished at 2025-05-21T15:47: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/2025139/2025.139.04/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-05-21T15:47:39Z(start date = 2025-05-21T15:47:39Z, end date = 2025-05-21T15:47:39Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:08Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.69009300000001 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80574116666668 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81172466666668 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.37787583333336 to the max longitude of gps.log. - Set the content length of gps.log to 646988. - UpdateBot DataProducer persisted and has ID 53454. - Deployment gps was changed and persisted to the database with ID 53449. 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/2025139/2025.139.04/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/2025139/2025.139.04/hydroscatlog.nc - Starting the NetCDF creation at 2025-05-21T15:47:40Z - NetCDF creation finished at 2025-05-21T15:47:43Z - 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/2025139/2025.139.04/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-05-21T15:47:40Z(start date = 2025-05-21T15:47:40Z, end date = 2025-05-21T15:47:43Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:14Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 29529970. - UpdateBot DataProducer persisted and has ID 53455. - Deployment hydroscatlog was changed and persisted to the database with ID 53448. 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/2025139/2025.139.04/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/2025139/2025.139.04/navigation.nc - Starting the NetCDF creation at 2025-05-21T15:47:44Z - NetCDF creation finished at 2025-05-21T15:48:05Z - 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/2025139/2025.139.04/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-05-21T15:47:44Z(start date = 2025-05-21T15:47:44Z, end date = 2025-05-21T15:48:05Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:58Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z to the end date of navigation.log. - Set the content length of navigation.log to 170507940. - UpdateBot DataProducer persisted and has ID 53456. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_110190255 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_1177001683 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2025-05-20T23:58:51Z_1591937665 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 53431. 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/2025139/2025.139.04/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/2025139/2025.139.04/parosci.nc - Starting the NetCDF creation at 2025-05-21T15:48:07Z - NetCDF creation finished at 2025-05-21T15:48:11Z - 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/2025139/2025.139.04/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-05-21T15:48:07Z(start date = 2025-05-21T15:48:07Z, end date = 2025-05-21T15:48:11Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:22Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z 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.18425 to the max depth of parosci.log. - Set the content length of parosci.log to 42003398. - UpdateBot DataProducer persisted and has ID 53457. - Deployment parosci was changed and persisted to the database with ID 53430. 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/2025139/2025.139.04/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/2025139/2025.139.04/tailCone.nc - Starting the NetCDF creation at 2025-05-21T15:48:12Z - NetCDF creation finished at 2025-05-21T15:48: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/2025139/2025.139.04/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-05-21T15:48:12Z(start date = 2025-05-21T15:48:12Z, end date = 2025-05-21T15:48:14Z). - 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/2025139/2025.139.04/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/2025139/2025.139.04/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2025-05-19T18:52:17Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2025-05-20T19:17:48Z to the end date of tailCone.log. - Set the content length of tailCone.log to 21104007. - UpdateBot DataProducer persisted and has ID 53458. - Deployment tailCone was changed and persisted to the database with ID 53440. - Deployment 2025.139.04 was changed and persisted to the database with ID 53429. Processing for deployment 2025.139.04 ended at 2025-05-21T15:48:15Z