SSDS Processing Report for data sets from Deployment 2019.029.00 Processing began at 2019-01-30T17:23:59Z Going to try to convert any outputs of deployment 2019.029.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/2019029/2019.029.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/2019029/2019.029.00/biolume.nc - Starting the NetCDF creation at 2019-01-30T17:24:00Z - NetCDF creation finished at 2019-01-30T17:24:05Z - 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/2019029/2019.029.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-01-30T17:24:00Z(start date = 2019-01-30T17:24:00Z, end date = 2019-01-30T17:24:05Z). - 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/2019029/2019.029.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/2019029/2019.029.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:09:56Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:32Z to the end date of biolume.log. - Set the content length of biolume.log to 22160658. - UpdateBot DataProducer persisted and has ID 50100. - Deployment biolume was changed and persisted to the database with ID 50089. 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/2019029/2019.029.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/2019029/2019.029.00/ctdDriver.nc - Starting the NetCDF creation at 2019-01-30T17:24:07Z - NetCDF creation finished at 2019-01-30T17:24: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/2019029/2019.029.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-01-30T17:24:07Z(start date = 2019-01-30T17:24:07Z, end date = 2019-01-30T17:24:11Z). - 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/2019029/2019.029.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/2019029/2019.029.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:39Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:33Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 30457830. - UpdateBot DataProducer persisted and has ID 50101. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_1317010335 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_153728508 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_1569001772 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_387851703 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_605687515 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50082. 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/2019029/2019.029.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/2019029/2019.029.00/ctdDriver2.nc - Starting the NetCDF creation at 2019-01-30T17:24:12Z - NetCDF creation finished at 2019-01-30T17: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/2019029/2019.029.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-01-30T17:24:12Z(start date = 2019-01-30T17:24:12Z, end date = 2019-01-30T17:24:15Z). - 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/2019029/2019.029.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/2019029/2019.029.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:23Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:33Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 30464159. - UpdateBot DataProducer persisted and has ID 50102. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_1010417166 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_1036955449 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_66136541 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50095. 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/2019029/2019.029.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/2019029/2019.029.00/dvl.nc - Starting the NetCDF creation at 2019-01-30T17:24:16Z - NetCDF creation finished at 2019-01-30T17:24:17Z - 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/2019029/2019.029.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-01-30T17:24:16Z(start date = 2019-01-30T17:24:16Z, end date = 2019-01-30T17:24:17Z). - 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/2019029/2019.029.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/2019029/2019.029.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:01Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:32Z to the end date of dvl.log. - Set the content length of dvl.log to 7927941. - UpdateBot DataProducer persisted and has ID 50103. - Deployment dvl was changed and persisted to the database with ID 50081. 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/2019029/2019.029.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/2019029/2019.029.00/dynamicControl.nc - Starting the NetCDF creation at 2019-01-30T17:24:18Z - NetCDF creation finished at 2019-01-30T17:24: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/2019029/2019.029.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-01-30T17:24:18Z(start date = 2019-01-30T17:24:18Z, end date = 2019-01-30T17:24:36Z). - 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/2019029/2019.029.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/2019029/2019.029.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:35Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:33Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 116606844. - UpdateBot DataProducer persisted and has ID 50104. - Deployment dynamicControl was changed and persisted to the database with ID 50078. 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/2019029/2019.029.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/2019029/2019.029.00/gps.nc - Starting the NetCDF creation at 2019-01-30T17:24:37Z - NetCDF creation finished at 2019-01-30T17:24: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/2019029/2019.029.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-01-30T17:24:37Z(start date = 2019-01-30T17:24:37Z, end date = 2019-01-30T17:24:37Z). - 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/2019029/2019.029.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/2019029/2019.029.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:09:55Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:32Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65892850000001 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.90414900000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81285933333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.03045533333335 to the max longitude of gps.log. - Set the content length of gps.log to 1064228. - UpdateBot DataProducer persisted and has ID 50105. - Deployment gps was changed and persisted to the database with ID 50079. 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/2019029/2019.029.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/2019029/2019.029.00/hydroscatlog.nc - Starting the NetCDF creation at 2019-01-30T17:24:38Z - NetCDF creation finished at 2019-01-30T17: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/2019029/2019.029.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-01-30T17:24:38Z(start date = 2019-01-30T17:24:38Z, end date = 2019-01-30T17:24:42Z). - 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/2019029/2019.029.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/2019029/2019.029.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:01Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:33Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 26651626. - UpdateBot DataProducer persisted and has ID 50106. - Deployment hydroscatlog was changed and persisted to the database with ID 50088. 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/2019029/2019.029.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/2019029/2019.029.00/isuslog.nc - Starting the NetCDF creation at 2019-01-30T17:24:43Z - NetCDF creation finished at 2019-01-30T17: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/2019029/2019.029.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-01-30T17:24:43Z(start date = 2019-01-30T17:24:43Z, end date = 2019-01-30T17:24:44Z). - 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/2019029/2019.029.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/2019029/2019.029.00/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:56Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:32Z to the end date of isuslog.log. - Set the content length of isuslog.log to 1981237. - UpdateBot DataProducer persisted and has ID 50107. - Deployment isuslog was changed and persisted to the database with ID 50090. 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/2019029/2019.029.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/2019029/2019.029.00/lisstlog.nc - Starting the NetCDF creation at 2019-01-30T17:24:44Z - NetCDF creation finished at 2019-01-30T17:24: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/2019029/2019.029.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-01-30T17:24:44Z(start date = 2019-01-30T17:24:44Z, end date = 2019-01-30T17:24:45Z). - 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/2019029/2019.029.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/2019029/2019.029.00/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:00Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:31Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 6662335. - UpdateBot DataProducer persisted and has ID 50108. - Deployment lisstlog was changed and persisted to the database with ID 50080. 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/2019029/2019.029.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/2019029/2019.029.00/navigation.nc - Starting the NetCDF creation at 2019-01-30T17:24:46Z - NetCDF creation finished at 2019-01-30T17:25: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/2019029/2019.029.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-01-30T17:24:46Z(start date = 2019-01-30T17:24:46Z, end date = 2019-01-30T17:25:04Z). - 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/2019029/2019.029.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/2019029/2019.029.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:35Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:33Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.65874897213383 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.90414913352518 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.03045591908518 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.81285869813318 to the max longitude of navigation.log. - Set the content length of navigation.log to 117401214. - UpdateBot DataProducer persisted and has ID 50109. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_145007309 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_163548617 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-01-30T17:23:54Z_1861926555 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50091. 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/2019029/2019.029.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/2019029/2019.029.00/parosci.nc - Starting the NetCDF creation at 2019-01-30T17:25:05Z - NetCDF creation finished at 2019-01-30T17:25: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/2019029/2019.029.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-01-30T17:25:05Z(start date = 2019-01-30T17:25:05Z, end date = 2019-01-30T17:25:12Z). - 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/2019029/2019.029.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/2019029/2019.029.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:00Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:33Z 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.94593 to the max depth of parosci.log. - Set the content length of parosci.log to 37910198. - UpdateBot DataProducer persisted and has ID 50110. - Deployment parosci was changed and persisted to the database with ID 50099. 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/2019029/2019.029.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/2019029/2019.029.00/tailCone.nc - Starting the NetCDF creation at 2019-01-30T17:25:13Z - NetCDF creation finished at 2019-01-30T17:25: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/2019/2019029/2019.029.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-01-30T17:25:13Z(start date = 2019-01-30T17:25:13Z, end date = 2019-01-30T17:25:16Z). - 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/2019029/2019.029.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/2019029/2019.029.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-01-29T17:10:00Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-01-30T15:12:33Z to the end date of tailCone.log. - Set the content length of tailCone.log to 19046347. - UpdateBot DataProducer persisted and has ID 50111. - Deployment tailCone was changed and persisted to the database with ID 50077. - Deployment 2019.029.00 was changed and persisted to the database with ID 50076. Processing for deployment 2019.029.00 ended at 2019-01-30T17:25:17Z