SSDS Processing Report for data sets from Deployment 2023.123.00 Processing began at 2023-05-04T20:08:46Z Going to try to convert any outputs of deployment 2023.123.00 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/2023123/2023.123.00/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/2023123/2023.123.00/biolume.nc - Starting the NetCDF creation at 2023-05-04T20:08:47Z - NetCDF creation finished at 2023-05-04T20:09:16Z - 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/2023123/2023.123.00/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-04T20:08:47Z(start date = 2023-05-04T20:08:47Z, end date = 2023-05-04T20:09:16Z). - 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/2023123/2023.123.00/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/2023123/2023.123.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:34Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:49Z to the end date of biolume.log. - Set the content length of biolume.log to 19842650. - UpdateBot DataProducer persisted and has ID 52444. - Deployment biolume was changed and persisted to the database with ID 52424. 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/2023123/2023.123.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/2023/2023123/2023.123.00/ctdDriver.nc - Starting the NetCDF creation at 2023-05-04T20:09:17Z - NetCDF creation finished at 2023-05-04T20:09: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/2023/2023123/2023.123.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 2023-05-04T20:09:17Z(start date = 2023-05-04T20:09:17Z, end date = 2023-05-04T20:09: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/2023/2023123/2023.123.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/2023/2023123/2023.123.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:58Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:50Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 27275910. - UpdateBot DataProducer persisted and has ID 52445. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_1027408551 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_1108786579 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_169503243 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_857147204 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_987304925 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 52438. 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/2023123/2023.123.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/2023/2023123/2023.123.00/ctdDriver2.nc - Starting the NetCDF creation at 2023-05-04T20:09:25Z - NetCDF creation finished at 2023-05-04T20:09: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/2023/2023123/2023.123.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 2023-05-04T20:09:25Z(start date = 2023-05-04T20:09:25Z, end date = 2023-05-04T20:09:31Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:46:30Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:50Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 27263517. - UpdateBot DataProducer persisted and has ID 52446. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_1715950086 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_451937997 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_724644280 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 52428. 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/2023123/2023.123.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/2023/2023123/2023.123.00/dvl.nc - Starting the NetCDF creation at 2023-05-04T20:09:31Z - NetCDF creation finished at 2023-05-04T20:09:32Z - 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/2023123/2023.123.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 2023-05-04T20:09:31Z(start date = 2023-05-04T20:09:31Z, end date = 2023-05-04T20:09:32Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:39Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:44Z to the end date of dvl.log. - Set the content length of dvl.log to 7456167. - UpdateBot DataProducer persisted and has ID 52447. - Deployment dvl was changed and persisted to the database with ID 52422. 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/2023123/2023.123.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/2023/2023123/2023.123.00/dynamicControl.nc - Starting the NetCDF creation at 2023-05-04T20:09:33Z - NetCDF creation finished at 2023-05-04T20:09: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/2023/2023123/2023.123.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 2023-05-04T20:09:33Z(start date = 2023-05-04T20:09:33Z, end date = 2023-05-04T20:09:54Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:46:24Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:50Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 110059918. - UpdateBot DataProducer persisted and has ID 52448. - Deployment dynamicControl was changed and persisted to the database with ID 52437. 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/2023123/2023.123.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/2023/2023123/2023.123.00/gps.nc - Starting the NetCDF creation at 2023-05-04T20:09:55Z - NetCDF creation finished at 2023-05-04T20:09:55Z - 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/2023123/2023.123.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 2023-05-04T20:09:55Z(start date = 2023-05-04T20:09:55Z, end date = 2023-05-04T20:09:55Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:34Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:49Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.658048500000014 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.90003300000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.82344683333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.02894683333336 to the max longitude of gps.log. - Set the content length of gps.log to 954140. - UpdateBot DataProducer persisted and has ID 52449. - Deployment gps was changed and persisted to the database with ID 52426. 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/2023123/2023.123.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/2023/2023123/2023.123.00/hydroscatlog.nc - Starting the NetCDF creation at 2023-05-04T20:09:55Z - NetCDF creation finished at 2023-05-04T20:09: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/2023123/2023.123.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 2023-05-04T20:09:55Z(start date = 2023-05-04T20:09:55Z, end date = 2023-05-04T20:09:59Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:40Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:50Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 23860138. - UpdateBot DataProducer persisted and has ID 52450. - Deployment hydroscatlog was changed and persisted to the database with ID 52425. 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/2023123/2023.123.00/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/2023123/2023.123.00/lisstlog.nc - Starting the NetCDF creation at 2023-05-04T20:10:00Z - NetCDF creation finished at 2023-05-04T20:10:02Z - 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/2023123/2023.123.00/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-04T20:10:00Z(start date = 2023-05-04T20:10:00Z, end date = 2023-05-04T20:10:02Z). - 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/2023123/2023.123.00/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/2023123/2023.123.00/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:39Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:50Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 8492023. - UpdateBot DataProducer persisted and has ID 52451. - Deployment lisstlog was changed and persisted to the database with ID 52432. 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/2023123/2023.123.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/2023/2023123/2023.123.00/navigation.nc - Starting the NetCDF creation at 2023-05-04T20:10:04Z - NetCDF creation finished at 2023-05-04T20:10:34Z - 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/2023123/2023.123.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 2023-05-04T20:10:04Z(start date = 2023-05-04T20:10:04Z, end date = 2023-05-04T20:10:34Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:46:24Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:50Z to the end date of navigation.log. - Set the content length of navigation.log to 137753368. - UpdateBot DataProducer persisted and has ID 52452. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_105710099 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_1926163672 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2023-05-04T20:08:39Z_486644655 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 52433. 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/2023123/2023.123.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/2023/2023123/2023.123.00/parosci.nc - Starting the NetCDF creation at 2023-05-04T20:10:35Z - NetCDF creation finished at 2023-05-04T20:10:41Z - 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/2023123/2023.123.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 2023-05-04T20:10:35Z(start date = 2023-05-04T20:10:35Z, end date = 2023-05-04T20:10:41Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:48Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:50Z 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.13986 to the max depth of parosci.log. - Set the content length of parosci.log to 33937718. - UpdateBot DataProducer persisted and has ID 52453. - Deployment parosci was changed and persisted to the database with ID 52423. 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/2023123/2023.123.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/2023/2023123/2023.123.00/tailCone.nc - Starting the NetCDF creation at 2023-05-04T20:10:42Z - NetCDF creation finished at 2023-05-04T20:10: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/2023/2023123/2023.123.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 2023-05-04T20:10:42Z(start date = 2023-05-04T20:10:42Z, end date = 2023-05-04T20:10:46Z). - 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/2023123/2023.123.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/2023/2023123/2023.123.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2023-05-03T19:45:44Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2023-05-04T15:29:02Z to the end date of tailCone.log. - Set the content length of tailCone.log to 17039883. - UpdateBot DataProducer persisted and has ID 52454. - Deployment tailCone was changed and persisted to the database with ID 52427. - Deployment 2023.123.00 was changed and persisted to the database with ID 52421. Processing for deployment 2023.123.00 ended at 2023-05-04T20:10:46Z