SSDS Processing Report for data sets from Deployment 2019.350.01 Processing began at 2019-12-18T20:24:12Z Going to try to convert any outputs of deployment 2019.350.01 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/biolume.nc - Starting the NetCDF creation at 2019-12-18T20:24:13Z - NetCDF creation finished at 2019-12-18T20:24: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/2019/2019350/2019.350.01/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 2019-12-18T20:24:13Z(start date = 2019-12-18T20:24:13Z, end date = 2019-12-18T20:24:15Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:30Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of biolume.log. - Set the content length of biolume.log to 5223466. - UpdateBot DataProducer persisted and has ID 50525. - Deployment biolume was changed and persisted to the database with ID 50515. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/ctdDriver.nc - Starting the NetCDF creation at 2019-12-18T20:24:17Z - NetCDF creation finished at 2019-12-18T20:24: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/2019/2019350/2019.350.01/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 2019-12-18T20:24:17Z(start date = 2019-12-18T20:24:17Z, end date = 2019-12-18T20:24: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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:58Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 7169862. - UpdateBot DataProducer persisted and has ID 50526. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_1597588239 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_1881168524 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_2096700274 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_500166728 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_687304269 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50507. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/ctdDriver2.nc - Starting the NetCDF creation at 2019-12-18T20:24:19Z - NetCDF creation finished at 2019-12-18T20:24:20Z - 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/2019/2019350/2019.350.01/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 2019-12-18T20:24:19Z(start date = 2019-12-18T20:24:19Z, end date = 2019-12-18T20:24:20Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:58Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 7169471. - UpdateBot DataProducer persisted and has ID 50527. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:04Z_1322390492 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:04Z_358775514 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:04Z_524347527 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50502. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/dvl.nc - Starting the NetCDF creation at 2019-12-18T20:24:21Z - NetCDF creation finished at 2019-12-18T20:24: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/2019/2019350/2019.350.01/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 2019-12-18T20:24:21Z(start date = 2019-12-18T20:24:21Z, end date = 2019-12-18T20:24:22Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:36Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of dvl.log. - Set the content length of dvl.log to 1847685. - UpdateBot DataProducer persisted and has ID 50528. - Deployment dvl was changed and persisted to the database with ID 50506. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/dynamicControl.nc - Starting the NetCDF creation at 2019-12-18T20:24:22Z - NetCDF creation finished at 2019-12-18T20:24:27Z - 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/2019/2019350/2019.350.01/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 2019-12-18T20:24:22Z(start date = 2019-12-18T20:24:22Z, end date = 2019-12-18T20:24:27Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:21:11Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 27429294. - UpdateBot DataProducer persisted and has ID 50529. - Deployment dynamicControl was changed and persisted to the database with ID 50522. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/gps.nc - Starting the NetCDF creation at 2019-12-18T20:24:27Z - NetCDF creation finished at 2019-12-18T20:24:28Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019350/2019.350.01/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 2019-12-18T20:24:27Z(start date = 2019-12-18T20:24:27Z, end date = 2019-12-18T20:24:28Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:30Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:08Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.71481583333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.795010000000005 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.84839633333334 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.87197566666671 to the max longitude of gps.log. - Set the content length of gps.log to 544172. - UpdateBot DataProducer persisted and has ID 50530. - Deployment gps was changed and persisted to the database with ID 50516. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/hydroscatlog.nc - Starting the NetCDF creation at 2019-12-18T20:24:28Z - NetCDF creation finished at 2019-12-18T20:24: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/2019/2019350/2019.350.01/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 2019-12-18T20:24:28Z(start date = 2019-12-18T20:24:28Z, end date = 2019-12-18T20:24: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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:36Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 6278602. - UpdateBot DataProducer persisted and has ID 50531. - Deployment hydroscatlog was changed and persisted to the database with ID 50521. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/isuslog.nc - Starting the NetCDF creation at 2019-12-18T20:24:32Z - NetCDF creation finished at 2019-12-18T20:24: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/2019/2019350/2019.350.01/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 2019-12-18T20:24:32Z(start date = 2019-12-18T20:24:32Z, end date = 2019-12-18T20:24:32Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:21:46Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:06Z to the end date of isuslog.log. - Set the content length of isuslog.log to 464533. - UpdateBot DataProducer persisted and has ID 50532. - Deployment isuslog was changed and persisted to the database with ID 50523. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/lisstlog.nc - Starting the NetCDF creation at 2019-12-18T20:24:34Z - NetCDF creation finished at 2019-12-18T20:24: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/2019/2019350/2019.350.01/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 2019-12-18T20:24:34Z(start date = 2019-12-18T20:24:34Z, end date = 2019-12-18T20:24:34Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:35Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-12-16T19:28:22Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 66151. - UpdateBot DataProducer persisted and has ID 50533. - Deployment lisstlog was changed and persisted to the database with ID 50524. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/navigation.nc - Starting the NetCDF creation at 2019-12-18T20:24:35Z - NetCDF creation finished at 2019-12-18T20:24: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/2019/2019350/2019.350.01/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 2019-12-18T20:24:35Z(start date = 2019-12-18T20:24:35Z, end date = 2019-12-18T20:24:39Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:21:11Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.71481688340727 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.800660602696865 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.87197314559342 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.84510223915386 to the max longitude of navigation.log. - Set the content length of navigation.log to 27617014. - UpdateBot DataProducer persisted and has ID 50534. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_1271447293 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_1715187982 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:24:05Z_952063780 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50517. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/parosci.nc - Starting the NetCDF creation at 2019-12-18T20:24:40Z - NetCDF creation finished at 2019-12-18T20:24:42Z - 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/2019/2019350/2019.350.01/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 2019-12-18T20:24:40Z(start date = 2019-12-18T20:24:40Z, end date = 2019-12-18T20:24:42Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:34Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:08Z 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 202.69547 to the max depth of parosci.log. - Set the content length of parosci.log to 8930726. - UpdateBot DataProducer persisted and has ID 50535. - Deployment parosci was changed and persisted to the database with ID 50514. 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/tailCone.nc - Starting the NetCDF creation at 2019-12-18T20:24:43Z - NetCDF creation finished at 2019-12-18T20:24:44Z - 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/2019/2019350/2019.350.01/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 2019-12-18T20:24:43Z(start date = 2019-12-18T20:24:43Z, end date = 2019-12-18T20:24:44Z). - 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/2019/2019350/2019.350.01/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/2019/2019350/2019.350.01/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-16T19:20:36Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-12-17T00:32:07Z to the end date of tailCone.log. - Set the content length of tailCone.log to 4486939. - UpdateBot DataProducer persisted and has ID 50536. - Deployment tailCone was changed and persisted to the database with ID 50513. - Deployment 2019.350.01 was changed and persisted to the database with ID 50501. Processing for deployment 2019.350.01 ended at 2019-12-18T20:24:44Z