SSDS Processing Report for data sets from Deployment 2009.168.03 Processing began at 2009-06-26T17:41:28Z Going to try to convert any outputs of deployment 2009.168.03 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 7 of them) Going to try to convert any outputs of deployment bluefinBattlog to NetCDF files: - Working on output bluefinBattlog.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/bluefinBattlog.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/auvbi/missionlogs/2009/2009168/2009.168.03/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T17:41:29Z - NetCDF creation finished at 2009-06-26T17:41:29Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/bluefinBattlog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T17:41:29Z(start date = 2009-06-26T17:41:29Z, end date = 2009-06-26T17:41:29Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be bluefinBattlog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/bluefinBattlog.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/auvbi/missionlogs/2009/2009168/2009.168.03/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T17:36:24Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T17:52:14Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 9807. - UpdateBot DataProducer persisted and has ID 34157. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:01Z_1620772236 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:01Z_250601374 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:01Z_1740616852 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 33829. Going to try to convert any outputs of deployment tailCone to NetCDF files: - Working on output tailCone.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/tailCone.nc - Starting the NetCDF creation at 2009-06-26T17:41:30Z - NetCDF creation finished at 2009-06-26T17:41:31Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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 2009-06-26T17:41:30Z(start date = 2009-06-26T17:41:30Z, end date = 2009-06-26T17:41:31Z). - 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/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T17:35:57Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T17:52:17Z to the end date of tailCone.log. - Set the content length of tailCone.log to 235579. - UpdateBot DataProducer persisted and has ID 34158. - Deployment tailCone was changed and persisted to the database with ID 33833. Going to try to convert any outputs of deployment dynamicControl to NetCDF files: - Working on output dynamicControl.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T17:41:33Z - NetCDF creation finished at 2009-06-26T17:41:33Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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 2009-06-26T17:41:33Z(start date = 2009-06-26T17:41:33Z, end date = 2009-06-26T17:41:33Z). - 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/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T17:36:19Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T17:52:17Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 1199186. - UpdateBot DataProducer persisted and has ID 34159. - Deployment dynamicControl was changed and persisted to the database with ID 33834. Going to try to convert any outputs of deployment gps to NetCDF files: - Working on output gps.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/gps.nc - Starting the NetCDF creation at 2009-06-26T17:41:35Z - NetCDF creation finished at 2009-06-26T17:41:35Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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 2009-06-26T17:41:35Z(start date = 2009-06-26T17:41:35Z, end date = 2009-06-26T17:41:35Z). - 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/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T17:35:58Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T17:52:16Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.81167083333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.81435316666667 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.96889400000002 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.9750181666667 to the max longitude of gps.log. - Set the content length of gps.log to 29588. - UpdateBot DataProducer persisted and has ID 34160. - Deployment gps was changed and persisted to the database with ID 33835. Going to try to convert any outputs of deployment dvl to NetCDF files: - Working on output dvl.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/dvl.nc - Starting the NetCDF creation at 2009-06-26T17:41:38Z - NetCDF creation finished at 2009-06-26T17:41:38Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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 2009-06-26T17:41:38Z(start date = 2009-06-26T17:41:38Z, end date = 2009-06-26T17:41:38Z). - 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/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T17:35:58Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T17:52:17Z to the end date of dvl.log. - Set the content length of dvl.log to 217953. - UpdateBot DataProducer persisted and has ID 34161. - Deployment dvl was changed and persisted to the database with ID 33836. Going to try to convert any outputs of deployment navigation to NetCDF files: - Working on output navigation.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/navigation.nc - Starting the NetCDF creation at 2009-06-26T17:41:39Z - NetCDF creation finished at 2009-06-26T17:41:40Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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 2009-06-26T17:41:39Z(start date = 2009-06-26T17:41:39Z, end date = 2009-06-26T17:41:40Z). - 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/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T17:36:18Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T17:52:17Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.81167036380628 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.81433133333188 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.9750184922342 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.96889379215474 to the max longitude of navigation.log. - Set the content length of navigation.log to 1132926. - UpdateBot DataProducer persisted and has ID 34162. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:02Z_2072862364 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:02Z_1637635229 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:02Z_220525575 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 33837. Going to try to convert any outputs of deployment parosci to NetCDF files: - Working on output parosci.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/parosci.nc - Starting the NetCDF creation at 2009-06-26T17:41:42Z - NetCDF creation finished at 2009-06-26T17:41:42Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.03/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 2009-06-26T17:41:42Z(start date = 2009-06-26T17:41:42Z, end date = 2009-06-26T17:41:42Z). - 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/auvbi/missionlogs/2009/2009168/2009.168.03/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/auvbi/missionlogs/2009/2009168/2009.168.03/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T17:36:04Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T17:52:17Z 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 60.78452 to the max depth of parosci.log. - Set the content length of parosci.log to 378278. - UpdateBot DataProducer persisted and has ID 34163. - Deployment parosci was changed and persisted to the database with ID 33841. - Deployment 2009.168.03 was changed and persisted to the database with ID 33828. Processing for deployment 2009.168.03 ended at 2009-06-26T17:41:44Z