SSDS Processing Report for data sets from Deployment 2023.132.02 Processing began at 2023-05-12T20:37:59Z Going to try to convert any outputs of deployment 2023.132.02 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 11 of them) Going to try to convert any outputs of deployment biolume to NetCDF files: - Working on output biolume.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2023/2023132/2023.132.02/biolume.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/2023/2023132/2023.132.02/biolume.nc - Starting the NetCDF creation at 2023-05-12T20:37:59Z - NetCDF creation finished at 2023-05-12T20:37: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/2023/2023132/2023.132.02/biolume.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2023-05-12T20:37:59Z(start date = 2023-05-12T20:37:59Z, end date = 2023-05-12T20:37:59Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be biolume.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2023/2023132/2023.132.02/biolume.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/2023/2023132/2023.132.02/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:49:50Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of biolume.log. - Set the content length of biolume.log to 120270. - UpdateBot DataProducer persisted and has ID 52479. - Deployment biolume was changed and persisted to the database with ID 52461. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/ctdDriver.nc - Starting the NetCDF creation at 2023-05-12T20:38:00Z - NetCDF creation finished at 2023-05-12T20:38:00Z - 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/2023/2023132/2023.132.02/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 2023-05-12T20:38:00Z(start date = 2023-05-12T20:38:00Z, end date = 2023-05-12T20:38:00Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:50:14Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 152550. - UpdateBot DataProducer persisted and has ID 52480. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_1232961965 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_1302450468 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_1385595708 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_1722953274 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_469772822 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 52464. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/ctdDriver2.nc - Starting the NetCDF creation at 2023-05-12T20:38:01Z - NetCDF creation finished at 2023-05-12T20:38:01Z - 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/2023/2023132/2023.132.02/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 2023-05-12T20:38:01Z(start date = 2023-05-12T20:38:01Z, end date = 2023-05-12T20:38:01Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:50:13Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 152829. - UpdateBot DataProducer persisted and has ID 52481. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_1978799382 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_245439295 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_349445165 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 52457. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/dvl.nc - Starting the NetCDF creation at 2023-05-12T20:38:04Z - NetCDF creation finished at 2023-05-12T20:38: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/2023/2023132/2023.132.02/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 2023-05-12T20:38:04Z(start date = 2023-05-12T20:38:04Z, end date = 2023-05-12T20:38:04Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:49:58Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:54:46Z to the end date of dvl.log. - Set the content length of dvl.log to 34395. - UpdateBot DataProducer persisted and has ID 52482. - Deployment dvl was changed and persisted to the database with ID 52478. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/dynamicControl.nc - Starting the NetCDF creation at 2023-05-12T20:38:06Z - NetCDF creation finished at 2023-05-12T20:38: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/2023/2023132/2023.132.02/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 2023-05-12T20:38:06Z(start date = 2023-05-12T20:38:06Z, end date = 2023-05-12T20:38:06Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:50:39Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 575358. - UpdateBot DataProducer persisted and has ID 52483. - Deployment dynamicControl was changed and persisted to the database with ID 52474. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/gps.nc - Starting the NetCDF creation at 2023-05-12T20:38:07Z - NetCDF creation finished at 2023-05-12T20:38:07Z - 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/2023/2023132/2023.132.02/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 2023-05-12T20:38:07Z(start date = 2023-05-12T20:38:07Z, end date = 2023-05-12T20:38:07Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:49:49Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:55:40Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.80257783333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80266383333334 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.78710366666671 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.7872001666667 to the max longitude of gps.log. - Set the content length of gps.log to 26132. - UpdateBot DataProducer persisted and has ID 52484. - Deployment gps was changed and persisted to the database with ID 52462. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/hydroscatlog.nc - Starting the NetCDF creation at 2023-05-12T20:38:07Z - NetCDF creation finished at 2023-05-12T20:38:07Z - 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/2023/2023132/2023.132.02/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 2023-05-12T20:38:07Z(start date = 2023-05-12T20:38:07Z, end date = 2023-05-12T20:38:07Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:49:56Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 140134. - UpdateBot DataProducer persisted and has ID 52485. - Deployment hydroscatlog was changed and persisted to the database with ID 52477. Going to try to convert any outputs of deployment lisstlog to NetCDF files: - Working on output lisstlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2023/2023132/2023.132.02/lisstlog.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/2023/2023132/2023.132.02/lisstlog.nc - Starting the NetCDF creation at 2023-05-12T20:38:08Z - NetCDF creation finished at 2023-05-12T20:38:08Z - 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/2023/2023132/2023.132.02/lisstlog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2023-05-12T20:38:08Z(start date = 2023-05-12T20:38:08Z, end date = 2023-05-12T20:38:08Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be lisstlog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2023/2023132/2023.132.02/lisstlog.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/2023/2023132/2023.132.02/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:49:55Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 55231. - UpdateBot DataProducer persisted and has ID 52486. - Deployment lisstlog was changed and persisted to the database with ID 52463. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/navigation.nc - Starting the NetCDF creation at 2023-05-12T20:38:09Z - NetCDF creation finished at 2023-05-12T20:38:09Z - 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/2023/2023132/2023.132.02/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 2023-05-12T20:38:09Z(start date = 2023-05-12T20:38:09Z, end date = 2023-05-12T20:38:09Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:50:39Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of navigation.log. - Set the content length of navigation.log to 721080. - UpdateBot DataProducer persisted and has ID 52487. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_1005134525 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_1331552262 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-12T20:37:52Z_528459878 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 52470. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/parosci.nc - Starting the NetCDF creation at 2023-05-12T20:38:09Z - NetCDF creation finished at 2023-05-12T20:38:09Z - 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/2023/2023132/2023.132.02/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 2023-05-12T20:38:09Z(start date = 2023-05-12T20:38:09Z, end date = 2023-05-12T20:38:09Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:50:04Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:56:49Z to the end date of parosci.log. - Since a min depth was found in the NetCDF file, will assign 9.0434204E-4 to the min depth of parosci.log. - Since a max depth was found in the NetCDF file, will assign 0.21546923 to the max depth of parosci.log. - Set the content length of parosci.log to 194054. - UpdateBot DataProducer persisted and has ID 52488. - Deployment parosci was changed and persisted to the database with ID 52476. 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/tailCone.nc - Starting the NetCDF creation at 2023-05-12T20:38:10Z - NetCDF creation finished at 2023-05-12T20:38:10Z - 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/2023/2023132/2023.132.02/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 2023-05-12T20:38:10Z(start date = 2023-05-12T20:38:10Z, end date = 2023-05-12T20:38:10Z). - 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/2023/2023132/2023.132.02/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/2023/2023132/2023.132.02/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-12T19:50:09Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2023-05-12T19:55:50Z to the end date of tailCone.log. - Set the content length of tailCone.log to 82443. - UpdateBot DataProducer persisted and has ID 52489. - Deployment tailCone was changed and persisted to the database with ID 52475. - Deployment 2023.132.02 was changed and persisted to the database with ID 52456. Processing for deployment 2023.132.02 ended at 2023-05-12T20:38:11Z