SSDS Processing Report for data sets from Deployment 2019.042.00 Processing began at 2019-02-12T21:12:24Z Going to try to convert any outputs of deployment 2019.042.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/2019/2019042/2019.042.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/2019/2019042/2019.042.00/biolume.nc - Starting the NetCDF creation at 2019-02-12T21:12:25Z - NetCDF creation finished at 2019-02-12T21:12: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/2019/2019042/2019.042.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 2019-02-12T21:12:25Z(start date = 2019-02-12T21:12:25Z, end date = 2019-02-12T21:12:31Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:03Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:04Z to the end date of biolume.log. - Set the content length of biolume.log to 19637602. - UpdateBot DataProducer persisted and has ID 50136. - Deployment biolume was changed and persisted to the database with ID 50119. 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/2019042/2019.042.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/2019/2019042/2019.042.00/ctdDriver.nc - Starting the NetCDF creation at 2019-02-12T21:12:33Z - NetCDF creation finished at 2019-02-12T21:12:37Z - 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/2019042/2019.042.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 2019-02-12T21:12:33Z(start date = 2019-02-12T21:12:33Z, end date = 2019-02-12T21:12:37Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:46Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:05Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 26982438. - UpdateBot DataProducer persisted and has ID 50137. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_1274903173 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_1620890394 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_1963986373 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_2079743470 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_390005271 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50123. 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/2019042/2019.042.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/2019/2019042/2019.042.00/ctdDriver2.nc - Starting the NetCDF creation at 2019-02-12T21:12:38Z - NetCDF creation finished at 2019-02-12T21:12:43Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019042/2019.042.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 2019-02-12T21:12:38Z(start date = 2019-02-12T21:12:38Z, end date = 2019-02-12T21:12:43Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:29Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:05Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 26987519. - UpdateBot DataProducer persisted and has ID 50138. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:18Z_2089759080 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:18Z_2109569460 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:18Z_574840717 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50115. 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/2019042/2019.042.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/2019/2019042/2019.042.00/dvl.nc - Starting the NetCDF creation at 2019-02-12T21:12:44Z - NetCDF creation finished at 2019-02-12T21:12:45Z - 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/2019042/2019.042.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 2019-02-12T21:12:44Z(start date = 2019-02-12T21:12:44Z, end date = 2019-02-12T21:12:45Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:08Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:04Z to the end date of dvl.log. - Set the content length of dvl.log to 7039521. - UpdateBot DataProducer persisted and has ID 50139. - Deployment dvl was changed and persisted to the database with ID 50135. 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/2019042/2019.042.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/2019/2019042/2019.042.00/dynamicControl.nc - Starting the NetCDF creation at 2019-02-12T21:12:46Z - NetCDF creation finished at 2019-02-12T21:13:03Z - 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/2019042/2019.042.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 2019-02-12T21:12:46Z(start date = 2019-02-12T21:12:46Z, end date = 2019-02-12T21:13:03Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:42Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:05Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 103323336. - UpdateBot DataProducer persisted and has ID 50140. - Deployment dynamicControl was changed and persisted to the database with ID 50121. 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/2019042/2019.042.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/2019/2019042/2019.042.00/gps.nc - Starting the NetCDF creation at 2019-02-12T21:13:04Z - NetCDF creation finished at 2019-02-12T21:13: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/2019/2019042/2019.042.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 2019-02-12T21:13:04Z(start date = 2019-02-12T21:13:04Z, end date = 2019-02-12T21:13:04Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:02Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:04Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65933616666668 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.906002166666674 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81311283333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.02774083333338 to the max longitude of gps.log. - Set the content length of gps.log to 502988. - UpdateBot DataProducer persisted and has ID 50141. - Deployment gps was changed and persisted to the database with ID 50122. 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/2019042/2019.042.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/2019/2019042/2019.042.00/hydroscatlog.nc - Starting the NetCDF creation at 2019-02-12T21:13:07Z - NetCDF creation finished at 2019-02-12T21:13:11Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019042/2019.042.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 2019-02-12T21:13:07Z(start date = 2019-02-12T21:13:07Z, end date = 2019-02-12T21:13:11Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:08Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:05Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 23616538. - UpdateBot DataProducer persisted and has ID 50142. - Deployment hydroscatlog was changed and persisted to the database with ID 50113. 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/2019042/2019.042.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/2019/2019042/2019.042.00/isuslog.nc - Starting the NetCDF creation at 2019-02-12T21:13:12Z - NetCDF creation finished at 2019-02-12T21:13:12Z - 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/2019042/2019.042.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 2019-02-12T21:13:12Z(start date = 2019-02-12T21:13:12Z, end date = 2019-02-12T21:13:12Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:17:03Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:04Z to the end date of isuslog.log. - Set the content length of isuslog.log to 1756021. - UpdateBot DataProducer persisted and has ID 50143. - Deployment isuslog was changed and persisted to the database with ID 50129. 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/2019042/2019.042.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/2019/2019042/2019.042.00/lisstlog.nc - Starting the NetCDF creation at 2019-02-12T21:13:13Z - NetCDF creation finished at 2019-02-12T21:13:13Z - 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/2019042/2019.042.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 2019-02-12T21:13:13Z(start date = 2019-02-12T21:13:13Z, end date = 2019-02-12T21:13:13Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:10Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:02Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 2799007. - UpdateBot DataProducer persisted and has ID 50144. - Deployment lisstlog was changed and persisted to the database with ID 50120. 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/2019042/2019.042.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/2019/2019042/2019.042.00/navigation.nc - Starting the NetCDF creation at 2019-02-12T21:13:14Z - NetCDF creation finished at 2019-02-12T21:13:29Z - 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/2019042/2019.042.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 2019-02-12T21:13:14Z(start date = 2019-02-12T21:13:14Z, end date = 2019-02-12T21:13:29Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:42Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:05Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.65871374830594 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.90600118724316 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.02868485018746 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.81311087146516 to the max longitude of navigation.log. - Set the content length of navigation.log to 104027342. - UpdateBot DataProducer persisted and has ID 50145. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_1091736776 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_1518466312 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-02-12T21:12:19Z_2080980741 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50131. 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/2019042/2019.042.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/2019/2019042/2019.042.00/parosci.nc - Starting the NetCDF creation at 2019-02-12T21:13:30Z - NetCDF creation finished at 2019-02-12T21:13:36Z - 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/2019042/2019.042.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 2019-02-12T21:13:30Z(start date = 2019-02-12T21:13:30Z, end date = 2019-02-12T21:13:36Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:07Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:05Z 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 103.67452 to the max depth of parosci.log. - Set the content length of parosci.log to 33593990. - UpdateBot DataProducer persisted and has ID 50146. - Deployment parosci was changed and persisted to the database with ID 50130. 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/2019042/2019.042.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/2019/2019042/2019.042.00/tailCone.nc - Starting the NetCDF creation at 2019-02-12T21:13:37Z - NetCDF creation finished at 2019-02-12T21:13: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/2019/2019042/2019.042.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 2019-02-12T21:13:37Z(start date = 2019-02-12T21:13:37Z, end date = 2019-02-12T21:13:41Z). - 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/2019042/2019.042.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/2019/2019042/2019.042.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-02-11T23:16:07Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-02-12T18:48:05Z to the end date of tailCone.log. - Set the content length of tailCone.log to 16877659. - UpdateBot DataProducer persisted and has ID 50147. - Deployment tailCone was changed and persisted to the database with ID 50114. - Deployment 2019.042.00 was changed and persisted to the database with ID 50112. Processing for deployment 2019.042.00 ended at 2019-02-12T21:13:42Z