SSDS Processing Report for data sets from Deployment 2024.023.00 Processing began at 2024-01-25T17:10:49Z Going to try to convert any outputs of deployment 2024.023.00 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 12 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/biolume.nc - Starting the NetCDF creation at 2024-01-25T17:10:50Z - NetCDF creation finished at 2024-01-25T17:10: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/2024/2024023/2024.023.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 2024-01-25T17:10:50Z(start date = 2024-01-25T17:10:50Z, end date = 2024-01-25T17:10:55Z). - 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:35Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of biolume.log. - Set the content length of biolume.log to 21241918. - UpdateBot DataProducer persisted and has ID 52854. - Deployment biolume was changed and persisted to the database with ID 52845. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/ctdDriver.nc - Starting the NetCDF creation at 2024-01-25T17:10:56Z - NetCDF creation finished at 2024-01-25T17:11: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/2024/2024023/2024.023.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 2024-01-25T17:10:56Z(start date = 2024-01-25T17:10:56Z, end date = 2024-01-25T17:11: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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:58Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 29227110. - UpdateBot DataProducer persisted and has ID 52855. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_134103068 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_1538926670 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_1834891801 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_2120450963 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_709424516 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 52838. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/ctdDriver2.nc - Starting the NetCDF creation at 2024-01-25T17:11:01Z - NetCDF creation finished at 2024-01-25T17:11: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/2024/2024023/2024.023.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 2024-01-25T17:11:01Z(start date = 2024-01-25T17:11:01Z, end date = 2024-01-25T17:11: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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:25:30Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 29214813. - UpdateBot DataProducer persisted and has ID 52856. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_1365638862 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_1568695021 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_270223392 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 52847. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/dvl.nc - Starting the NetCDF creation at 2024-01-25T17:11:05Z - NetCDF creation finished at 2024-01-25T17:11: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/2024/2024023/2024.023.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 2024-01-25T17:11:05Z(start date = 2024-01-25T17:11:05Z, end date = 2024-01-25T17:11: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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:40Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:32:26Z to the end date of dvl.log. - Set the content length of dvl.log to 8029591. - UpdateBot DataProducer persisted and has ID 52857. - Deployment dvl was changed and persisted to the database with ID 52844. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/dynamicControl.nc - Starting the NetCDF creation at 2024-01-25T17:11:07Z - NetCDF creation finished at 2024-01-25T17:11: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/2024/2024023/2024.023.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 2024-01-25T17:11:07Z(start date = 2024-01-25T17:11:07Z, end date = 2024-01-25T17:11: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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:25:24Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 117937948. - UpdateBot DataProducer persisted and has ID 52858. - Deployment dynamicControl was changed and persisted to the database with ID 52837. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/gps.nc - Starting the NetCDF creation at 2024-01-25T17:11:24Z - NetCDF creation finished at 2024-01-25T17:11: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/2024/2024023/2024.023.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 2024-01-25T17:11:24Z(start date = 2024-01-25T17:11:24Z, end date = 2024-01-25T17:11: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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:34Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65694616666667 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.90162966666667 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.82320166666669 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.02774766666668 to the max longitude of gps.log. - Set the content length of gps.log to 1494716. - UpdateBot DataProducer persisted and has ID 52859. - Deployment gps was changed and persisted to the database with ID 52853. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/hydroscatlog.nc - Starting the NetCDF creation at 2024-01-25T17:11:26Z - NetCDF creation finished at 2024-01-25T17:11:30Z - 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/2024/2024023/2024.023.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 2024-01-25T17:11:26Z(start date = 2024-01-25T17:11:26Z, end date = 2024-01-25T17:11:30Z). - 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:40Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 25566514. - UpdateBot DataProducer persisted and has ID 52860. - Deployment hydroscatlog was changed and persisted to the database with ID 52852. Going to try to convert any outputs of deployment isuslog to NetCDF files: - Working on output isuslog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2024/2024023/2024.023.00/isuslog.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/2024/2024023/2024.023.00/isuslog.nc - Starting the NetCDF creation at 2024-01-25T17:11:31Z - NetCDF creation finished at 2024-01-25T17:11: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/2024/2024023/2024.023.00/isuslog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2024-01-25T17:11:31Z(start date = 2024-01-25T17:11:31Z, end date = 2024-01-25T17:11:31Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be isuslog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2024/2024023/2024.023.00/isuslog.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/2024/2024023/2024.023.00/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:25:50Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of isuslog.log. - Set the content length of isuslog.log to 1203861. - UpdateBot DataProducer persisted and has ID 52861. - Deployment isuslog was changed and persisted to the database with ID 52836. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/lisstlog.nc - Starting the NetCDF creation at 2024-01-25T17:11:32Z - NetCDF creation finished at 2024-01-25T17:11:33Z - 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/2024/2024023/2024.023.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 2024-01-25T17:11:32Z(start date = 2024-01-25T17:11:32Z, end date = 2024-01-25T17:11:33Z). - 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:39Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:31Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 9033487. - UpdateBot DataProducer persisted and has ID 52862. - Deployment lisstlog was changed and persisted to the database with ID 52851. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/navigation.nc - Starting the NetCDF creation at 2024-01-25T17:11:34Z - NetCDF creation finished at 2024-01-25T17:12: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/2024/2024023/2024.023.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 2024-01-25T17:11:34Z(start date = 2024-01-25T17:11:34Z, end date = 2024-01-25T17:12:01Z). - 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:25:24Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z to the end date of navigation.log. - Set the content length of navigation.log to 147613612. - UpdateBot DataProducer persisted and has ID 52863. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_1088473998 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_1760278795 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2024-01-25T17:10:43Z_45966378 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 52831. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/parosci.nc - Starting the NetCDF creation at 2024-01-25T17:12:03Z - NetCDF creation finished at 2024-01-25T17:12: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/2024/2024023/2024.023.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 2024-01-25T17:12:03Z(start date = 2024-01-25T17:12:03Z, end date = 2024-01-25T17:12:10Z). - 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:49Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:32Z 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.2034 to the max depth of parosci.log. - Set the content length of parosci.log to 36364022. - UpdateBot DataProducer persisted and has ID 52864. - Deployment parosci was changed and persisted to the database with ID 52846. 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/tailCone.nc - Starting the NetCDF creation at 2024-01-25T17:12:11Z - NetCDF creation finished at 2024-01-25T17:12:15Z - 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/2024/2024023/2024.023.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 2024-01-25T17:12:11Z(start date = 2024-01-25T17:12:11Z, end date = 2024-01-25T17:12:15Z). - 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/2024/2024023/2024.023.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/2024/2024023/2024.023.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2024-01-23T20:24:45Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2024-01-24T17:33:22Z to the end date of tailCone.log. - Set the content length of tailCone.log to 18268683. - UpdateBot DataProducer persisted and has ID 52865. - Deployment tailCone was changed and persisted to the database with ID 52835. - Deployment 2024.023.00 was changed and persisted to the database with ID 52830. Processing for deployment 2024.023.00 ended at 2024-01-25T17:12:15Z