SSDS Processing Report for data sets from Deployment 2019.093.01 Processing began at 2019-04-04T21:58:51Z Going to try to convert any outputs of deployment 2019.093.01 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 12 of them) Going to try to convert any outputs of deployment biolume to NetCDF files: - Working on output biolume.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/biolume.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/biolume.nc - Starting the NetCDF creation at 2019-04-04T21:58:51Z - NetCDF creation finished at 2019-04-04T21:58:58Z - 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/2019093/2019.093.01/biolume.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:58:51Z(start date = 2019-04-04T21:58:51Z, end date = 2019-04-04T21:58:58Z). - 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/2019093/2019.093.01/biolume.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:05Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of biolume.log. - Set the content length of biolume.log to 23885958. - UpdateBot DataProducer persisted and has ID 50208. - Deployment biolume was changed and persisted to the database with ID 50191. 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/2019093/2019.093.01/ctdDriver.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/ctdDriver.nc - Starting the NetCDF creation at 2019-04-04T21:58:59Z - NetCDF creation finished at 2019-04-04T21:59: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/2019093/2019.093.01/ctdDriver.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:58:59Z(start date = 2019-04-04T21:58:59Z, end date = 2019-04-04T21:59:03Z). - 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/2019093/2019.093.01/ctdDriver.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:33Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 32732838. - UpdateBot DataProducer persisted and has ID 50209. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:46Z_1014012125 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:46Z_111855499 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:46Z_1961954112 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:46Z_2027492903 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:46Z_373749648 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50200. 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/2019093/2019.093.01/ctdDriver2.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/ctdDriver2.nc - Starting the NetCDF creation at 2019-04-04T21:59:04Z - NetCDF creation finished at 2019-04-04T21:59: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/2019093/2019.093.01/ctdDriver2.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:04Z(start date = 2019-04-04T21:59:04Z, end date = 2019-04-04T21:59:08Z). - 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/2019093/2019.093.01/ctdDriver2.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:33Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 32739071. - UpdateBot DataProducer persisted and has ID 50210. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:45Z_1240299413 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:45Z_1335993595 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:45Z_876748420 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50195. 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/2019093/2019.093.01/dvl.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/dvl.nc - Starting the NetCDF creation at 2019-04-04T21:59:09Z - NetCDF creation finished at 2019-04-04T21:59:10Z - 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/2019093/2019.093.01/dvl.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:09Z(start date = 2019-04-04T21:59:09Z, end date = 2019-04-04T21:59:10Z). - 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/2019093/2019.093.01/dvl.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:10Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of dvl.log. - Set the content length of dvl.log to 8624325. - UpdateBot DataProducer persisted and has ID 50211. - Deployment dvl was changed and persisted to the database with ID 50207. 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/2019093/2019.093.01/dynamicControl.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/dynamicControl.nc - Starting the NetCDF creation at 2019-04-04T21:59:11Z - NetCDF creation finished at 2019-04-04T21:59:28Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/dynamicControl.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:11Z(start date = 2019-04-04T21:59:11Z, end date = 2019-04-04T21:59:28Z). - 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/2019093/2019.093.01/dynamicControl.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:46Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 125688798. - UpdateBot DataProducer persisted and has ID 50212. - Deployment dynamicControl was changed and persisted to the database with ID 50194. 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/2019093/2019.093.01/gps.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/gps.nc - Starting the NetCDF creation at 2019-04-04T21:59:32Z - NetCDF creation finished at 2019-04-04T21:59:32Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/gps.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:32Z(start date = 2019-04-04T21:59:32Z, end date = 2019-04-04T21:59:32Z). - 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/2019093/2019.093.01/gps.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:05Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:41Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65774383333335 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.927169500000005 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81193183333335 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.01744083333337 to the max longitude of gps.log. - Set the content length of gps.log to 602852. - UpdateBot DataProducer persisted and has ID 50213. - Deployment gps was changed and persisted to the database with ID 50192. 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/2019093/2019.093.01/hydroscatlog.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/hydroscatlog.nc - Starting the NetCDF creation at 2019-04-04T21:59:33Z - NetCDF creation finished at 2019-04-04T21:59: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/2019093/2019.093.01/hydroscatlog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:33Z(start date = 2019-04-04T21:59:33Z, end date = 2019-04-04T21:59:37Z). - 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/2019093/2019.093.01/hydroscatlog.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:10Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 28725166. - UpdateBot DataProducer persisted and has ID 50214. - Deployment hydroscatlog was changed and persisted to the database with ID 50193. 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/2019093/2019.093.01/isuslog.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/isuslog.nc - Starting the NetCDF creation at 2019-04-04T21:59:38Z - NetCDF creation finished at 2019-04-04T21:59:39Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/isuslog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:38Z(start date = 2019-04-04T21:59:38Z, end date = 2019-04-04T21:59:39Z). - 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/2019093/2019.093.01/isuslog.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:03:29Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:41Z to the end date of isuslog.log. - Set the content length of isuslog.log to 2138133. - UpdateBot DataProducer persisted and has ID 50215. - Deployment isuslog was changed and persisted to the database with ID 50186. 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/2019093/2019.093.01/lisstlog.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/lisstlog.nc - Starting the NetCDF creation at 2019-04-04T21:59:39Z - NetCDF creation finished at 2019-04-04T21:59:40Z - 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/2019093/2019.093.01/lisstlog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:39Z(start date = 2019-04-04T21:59:39Z, end date = 2019-04-04T21:59:40Z). - 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/2019093/2019.093.01/lisstlog.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:13Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:38Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 3403975. - UpdateBot DataProducer persisted and has ID 50216. - Deployment lisstlog was changed and persisted to the database with ID 50199. 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/2019093/2019.093.01/navigation.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/navigation.nc - Starting the NetCDF creation at 2019-04-04T21:59:41Z - NetCDF creation finished at 2019-04-04T21:59:58Z - 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/2019093/2019.093.01/navigation.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T21:59:41Z(start date = 2019-04-04T21:59:41Z, end date = 2019-04-04T21:59:58Z). - 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/2019093/2019.093.01/navigation.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:45Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.657741111830966 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.927169989008675 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.02934937083954 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.81192707317177 to the max longitude of navigation.log. - Set the content length of navigation.log to 126544950. - UpdateBot DataProducer persisted and has ID 50217. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:45Z_1315684517 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:45Z_1353197626 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-04-04T21:58:45Z_463573594 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50187. 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/2019093/2019.093.01/parosci.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/parosci.nc - Starting the NetCDF creation at 2019-04-04T22:00:01Z - NetCDF creation finished at 2019-04-04T22:00: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/2019093/2019.093.01/parosci.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T22:00:01Z(start date = 2019-04-04T22:00:01Z, end date = 2019-04-04T22:00: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/2019093/2019.093.01/parosci.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:09Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z 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 203.18967 to the max depth of parosci.log. - Set the content length of parosci.log to 40863398. - UpdateBot DataProducer persisted and has ID 50218. - Deployment parosci was changed and persisted to the database with ID 50206. 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/2019093/2019.093.01/tailCone.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/tailCone.nc - Starting the NetCDF creation at 2019-04-04T22:00:16Z - NetCDF creation finished at 2019-04-04T22:00:20Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/tailCone.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-04-04T22:00:16Z(start date = 2019-04-04T22:00:16Z, end date = 2019-04-04T22:00:20Z). - 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/2019093/2019.093.01/tailCone.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019093/2019.093.01/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-04-03T21:02:11Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-04-04T20:47:42Z to the end date of tailCone.log. - Set the content length of tailCone.log to 20529403. - UpdateBot DataProducer persisted and has ID 50219. - Deployment tailCone was changed and persisted to the database with ID 50185. - Deployment 2019.093.01 was changed and persisted to the database with ID 50184. Processing for deployment 2019.093.01 ended at 2019-04-04T22:00:25Z