SSDS Processing Report for data sets from Deployment 2016.179.01 Processing began at 2016-06-28T19:42:40Z Going to try to convert any outputs of deployment 2016.179.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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/biolume.nc - Starting the NetCDF creation at 2016-06-28T19:42:41Z - NetCDF creation finished at 2016-06-28T19:42: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/2016/2016179/2016.179.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 2016-06-28T19:42:41Z(start date = 2016-06-28T19:42:41Z, end date = 2016-06-28T19:42:45Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:06Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of biolume.log. - Set the content length of biolume.log to 11655782. - UpdateBot DataProducer persisted and has ID 48251. - Deployment biolume was changed and persisted to the database with ID 48248. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/ctdDriver.nc - Starting the NetCDF creation at 2016-06-28T19:42:47Z - NetCDF creation finished at 2016-06-28T19:42: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/2016/2016179/2016.179.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 2016-06-28T19:42:47Z(start date = 2016-06-28T19:42:47Z, end date = 2016-06-28T19:42:50Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:33Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 16014726. - UpdateBot DataProducer persisted and has ID 48252. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_1019087299 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_126653126 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_1495291114 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_1902442624 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_454344757 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 48232. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/ctdDriver2.nc - Starting the NetCDF creation at 2016-06-28T19:42:51Z - NetCDF creation finished at 2016-06-28T19:42:54Z - 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/2016/2016179/2016.179.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 2016-06-28T19:42:51Z(start date = 2016-06-28T19:42:51Z, end date = 2016-06-28T19:42:54Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:21:15Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 15998687. - UpdateBot DataProducer persisted and has ID 48253. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_1548930504 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_1920280180 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:34Z_2005549676 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 48241. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/dvl.nc - Starting the NetCDF creation at 2016-06-28T19:42:55Z - NetCDF creation finished at 2016-06-28T19:42:55Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2016/2016179/2016.179.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 2016-06-28T19:42:55Z(start date = 2016-06-28T19:42:55Z, end date = 2016-06-28T19:42:55Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:18Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of dvl.log. - Set the content length of dvl.log to 3290061. - UpdateBot DataProducer persisted and has ID 48254. - Deployment dvl was changed and persisted to the database with ID 48246. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/dynamicControl.nc - Starting the NetCDF creation at 2016-06-28T19:42:56Z - NetCDF creation finished at 2016-06-28T19:43: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/2016/2016179/2016.179.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 2016-06-28T19:42:56Z(start date = 2016-06-28T19:42:56Z, end date = 2016-06-28T19:43: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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:44Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 61285746. - UpdateBot DataProducer persisted and has ID 48255. - Deployment dynamicControl was changed and persisted to the database with ID 48240. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/gps.nc - Starting the NetCDF creation at 2016-06-28T19:43:09Z - NetCDF creation finished at 2016-06-28T19:43:09Z - 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/2016/2016179/2016.179.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 2016-06-28T19:43:09Z(start date = 2016-06-28T19:43:09Z, end date = 2016-06-28T19:43:09Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:05Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.605227000000006 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.801889500000016 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.83984300000003 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.94340600000002 to the max longitude of gps.log. - Set the content length of gps.log to 1288004. - UpdateBot DataProducer persisted and has ID 48256. - Deployment gps was changed and persisted to the database with ID 48249. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/hydroscatlog.nc - Starting the NetCDF creation at 2016-06-28T19:43:10Z - NetCDF creation finished at 2016-06-28T19:43: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/2016/2016179/2016.179.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 2016-06-28T19:43:10Z(start date = 2016-06-28T19:43:10Z, end date = 2016-06-28T19:43:12Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:11Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 14013826. - UpdateBot DataProducer persisted and has ID 48257. - Deployment hydroscatlog was changed and persisted to the database with ID 48238. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/isuslog.nc - Starting the NetCDF creation at 2016-06-28T19:43:13Z - NetCDF creation finished at 2016-06-28T19:43: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/2016/2016179/2016.179.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 2016-06-28T19:43:13Z(start date = 2016-06-28T19:43:13Z, end date = 2016-06-28T19:43:14Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:21:06Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of isuslog.log. - Set the content length of isuslog.log to 1037685. - UpdateBot DataProducer persisted and has ID 48258. - Deployment isuslog was changed and persisted to the database with ID 48239. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/lisstlog.nc - Starting the NetCDF creation at 2016-06-28T19:43:14Z - NetCDF creation finished at 2016-06-28T19:43: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/2016/2016179/2016.179.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 2016-06-28T19:43:14Z(start date = 2016-06-28T19:43:14Z, end date = 2016-06-28T19:43:15Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:10Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 5329927. - UpdateBot DataProducer persisted and has ID 48259. - Deployment lisstlog was changed and persisted to the database with ID 48245. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/navigation.nc - Starting the NetCDF creation at 2016-06-28T19:43:16Z - NetCDF creation finished at 2016-06-28T19:43: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/2016/2016179/2016.179.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 2016-06-28T19:43:16Z(start date = 2016-06-28T19:43:16Z, end date = 2016-06-28T19:43:27Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:44Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.60522695140336 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.80189012730125 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.94324530904805 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.8398417080624 to the max longitude of navigation.log. - Set the content length of navigation.log to 61703782. - UpdateBot DataProducer persisted and has ID 48260. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:33Z_2040318387 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:33Z_560908095 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2016-06-28T19:42:33Z_788945372 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 48228. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/parosci.nc - Starting the NetCDF creation at 2016-06-28T19:43:28Z - NetCDF creation finished at 2016-06-28T19:43:33Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2016/2016179/2016.179.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 2016-06-28T19:43:28Z(start date = 2016-06-28T19:43:28Z, end date = 2016-06-28T19:43:33Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:11Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z 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 102.99885 to the max depth of parosci.log. - Set the content length of parosci.log to 19665734. - UpdateBot DataProducer persisted and has ID 48261. - Deployment parosci was changed and persisted to the database with ID 48250. 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/tailCone.nc - Starting the NetCDF creation at 2016-06-28T19:43:34Z - NetCDF creation finished at 2016-06-28T19:43: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/2016/2016179/2016.179.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 2016-06-28T19:43:34Z(start date = 2016-06-28T19:43:34Z, end date = 2016-06-28T19:43:37Z). - 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/2016/2016179/2016.179.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/2016/2016179/2016.179.01/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2016-06-27T18:20:10Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2016-06-28T05:55:35Z to the end date of tailCone.log. - Set the content length of tailCone.log to 10014571. - UpdateBot DataProducer persisted and has ID 48262. - Deployment tailCone was changed and persisted to the database with ID 48247. - Deployment 2016.179.01 was changed and persisted to the database with ID 48227. Processing for deployment 2016.179.01 ended at 2016-06-28T19:43:37Z