SSDS Processing Report for data sets from Deployment 2019.066.02 Processing began at 2019-03-08T19:50:22Z Going to try to convert any outputs of deployment 2019.066.02 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/2019066/2019.066.02/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/2019066/2019.066.02/biolume.nc - Starting the NetCDF creation at 2019-03-08T19:50:22Z - NetCDF creation finished at 2019-03-08T19:50: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/2019066/2019.066.02/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-03-08T19:50:22Z(start date = 2019-03-08T19:50:22Z, end date = 2019-03-08T19:50: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/2019066/2019.066.02/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/2019066/2019.066.02/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:21:51Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of biolume.log. - Set the content length of biolume.log to 24432658. - UpdateBot DataProducer persisted and has ID 50172. - Deployment biolume was changed and persisted to the database with ID 50154. 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/2019066/2019.066.02/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/2019066/2019.066.02/ctdDriver.nc - Starting the NetCDF creation at 2019-03-08T19:50:32Z - NetCDF creation finished at 2019-03-08T19:50: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/2019066/2019.066.02/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-03-08T19:50:32Z(start date = 2019-03-08T19:50:32Z, end date = 2019-03-08T19:50:36Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:22:19Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 33589446. - UpdateBot DataProducer persisted and has ID 50173. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:58Z_1972240859 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:58Z_2034043287 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:58Z_445079344 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:58Z_501415723 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:58Z_798231751 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50163. 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/2019066/2019.066.02/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/2019066/2019.066.02/ctdDriver2.nc - Starting the NetCDF creation at 2019-03-08T19:50:37Z - NetCDF creation finished at 2019-03-08T19:50: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/2019066/2019.066.02/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-03-08T19:50:37Z(start date = 2019-03-08T19:50:37Z, end date = 2019-03-08T19:50:42Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:22:19Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 33589535. - UpdateBot DataProducer persisted and has ID 50174. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:57Z_1079903546 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:57Z_119103501 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:57Z_1985380015 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50157. 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/2019066/2019.066.02/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/2019066/2019.066.02/dvl.nc - Starting the NetCDF creation at 2019-03-08T19:50:43Z - NetCDF creation finished at 2019-03-08T19:50: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/2019066/2019.066.02/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-03-08T19:50:43Z(start date = 2019-03-08T19:50:43Z, end date = 2019-03-08T19:50: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/2019066/2019.066.02/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/2019066/2019.066.02/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:21:56Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:07Z to the end date of dvl.log. - Set the content length of dvl.log to 8850057. - UpdateBot DataProducer persisted and has ID 50175. - Deployment dvl was changed and persisted to the database with ID 50156. 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/2019066/2019.066.02/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/2019066/2019.066.02/dynamicControl.nc - Starting the NetCDF creation at 2019-03-08T19:50:45Z - NetCDF creation finished at 2019-03-08T19:51:07Z - 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/2019066/2019.066.02/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-03-08T19:50:45Z(start date = 2019-03-08T19:50:45Z, end date = 2019-03-08T19:51:07Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:22:30Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 128572056. - UpdateBot DataProducer persisted and has ID 50176. - Deployment dynamicControl was changed and persisted to the database with ID 50162. 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/2019066/2019.066.02/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/2019066/2019.066.02/gps.nc - Starting the NetCDF creation at 2019-03-08T19:51:08Z - NetCDF creation finished at 2019-03-08T19:51:08Z - 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/2019066/2019.066.02/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-03-08T19:51:08Z(start date = 2019-03-08T19:51:08Z, end date = 2019-03-08T19:51:08Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:21:51Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.658343166666675 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.903693000000004 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.8360266666667 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.0215446666667 to the max longitude of gps.log. - Set the content length of gps.log to 1562540. - UpdateBot DataProducer persisted and has ID 50177. - Deployment gps was changed and persisted to the database with ID 50161. 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/2019066/2019.066.02/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/2019066/2019.066.02/hydroscatlog.nc - Starting the NetCDF creation at 2019-03-08T19:51:09Z - NetCDF creation finished at 2019-03-08T19:51:14Z - 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/2019066/2019.066.02/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-03-08T19:51:09Z(start date = 2019-03-08T19:51:09Z, end date = 2019-03-08T19:51:14Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:21:56Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 29383306. - UpdateBot DataProducer persisted and has ID 50178. - Deployment hydroscatlog was changed and persisted to the database with ID 50170. 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/2019066/2019.066.02/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/2019066/2019.066.02/isuslog.nc - Starting the NetCDF creation at 2019-03-08T19:51:14Z - NetCDF creation finished at 2019-03-08T19:51: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/2019066/2019.066.02/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-03-08T19:51:14Z(start date = 2019-03-08T19:51:14Z, end date = 2019-03-08T19:51:15Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:23:13Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T15:45:02Z to the end date of isuslog.log. - Set the content length of isuslog.log to 2103829. - UpdateBot DataProducer persisted and has ID 50179. - Deployment isuslog was changed and persisted to the database with ID 50155. 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/2019066/2019.066.02/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/2019066/2019.066.02/lisstlog.nc - Starting the NetCDF creation at 2019-03-08T19:51:16Z - NetCDF creation finished at 2019-03-08T19:51: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/2019066/2019.066.02/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-03-08T19:51:16Z(start date = 2019-03-08T19:51:16Z, end date = 2019-03-08T19:51:16Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:21:59Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:05Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 3482767. - UpdateBot DataProducer persisted and has ID 50180. - Deployment lisstlog was changed and persisted to the database with ID 50169. 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/2019066/2019.066.02/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/2019066/2019.066.02/navigation.nc - Starting the NetCDF creation at 2019-03-08T19:51:17Z - NetCDF creation finished at 2019-03-08T19:51: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/2019066/2019.066.02/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-03-08T19:51:17Z(start date = 2019-03-08T19:51:17Z, end date = 2019-03-08T19:51:36Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:22:30Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.658344217845034 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.90369287793104 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.03043412073029 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.834735886311 to the max longitude of navigation.log. - Set the content length of navigation.log to 129447822. - UpdateBot DataProducer persisted and has ID 50181. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:57Z_1626641991 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:57Z_471026707 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-03-08T19:05:57Z_472187308 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50150. 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/2019066/2019.066.02/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/2019066/2019.066.02/parosci.nc - Starting the NetCDF creation at 2019-03-08T19:51:38Z - NetCDF creation finished at 2019-03-08T19:51:46Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019066/2019.066.02/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-03-08T19:51:38Z(start date = 2019-03-08T19:51:38Z, end date = 2019-03-08T19:51:46Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:21:56Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40: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 231.95265 to the max depth of parosci.log. - Set the content length of parosci.log to 41798870. - UpdateBot DataProducer persisted and has ID 50182. - Deployment parosci was changed and persisted to the database with ID 50171. 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/2019066/2019.066.02/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/2019066/2019.066.02/tailCone.nc - Starting the NetCDF creation at 2019-03-08T19:51:47Z - NetCDF creation finished at 2019-03-08T19:51:50Z - 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/2019066/2019.066.02/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-03-08T19:51:47Z(start date = 2019-03-08T19:51:47Z, end date = 2019-03-08T19:51:50Z). - 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/2019066/2019.066.02/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/2019066/2019.066.02/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-03-07T16:21:56Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-03-08T16:40:08Z to the end date of tailCone.log. - Set the content length of tailCone.log to 20999755. - UpdateBot DataProducer persisted and has ID 50183. - Deployment tailCone was changed and persisted to the database with ID 50149. - Deployment 2019.066.02 was changed and persisted to the database with ID 50148. Processing for deployment 2019.066.02 ended at 2019-03-08T19:51:51Z