SSDS Processing Report for data sets from Deployment 2008.328.00 Processing began at 2009-06-26T15:32:37Z Going to try to convert any outputs of deployment 2008.328.00 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 navigation to NetCDF files: - Working on output navigation.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/navigation.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/navigation.nc - Starting the NetCDF creation at 2009-06-26T15:32:38Z - NetCDF creation finished at 2009-06-26T15:32: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/2008/2008328/2008.328.00/navigation.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T15:32:38Z(start date = 2009-06-26T15:32:38Z, end date = 2009-06-26T15:32:38Z). - 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/2008/2008328/2008.328.00/navigation.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/navigation.nc.log. - UpdateBot DataProducer persisted and has ID 32515. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_652530375 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_368384302 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_1109470624 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32338. Going to try to convert any outputs of deployment ctdDriver to NetCDF files: - Working on output ctdDriver.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/ctdDriver.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/ctdDriver.nc - Starting the NetCDF creation at 2009-06-26T15:32:40Z - NetCDF creation finished at 2009-06-26T15:32: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/2008/2008328/2008.328.00/ctdDriver.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T15:32:40Z(start date = 2009-06-26T15:32:40Z, end date = 2009-06-26T15:32:40Z). - 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/auvbi/missionlogs/2008/2008328/2008.328.00/ctdDriver.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/ctdDriver.nc.log. - UpdateBot DataProducer persisted and has ID 32516. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_1077321487 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_775593227 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_1803391387 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_1401972405 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:16Z_889358795 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 32342. 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/2008/2008328/2008.328.00/tailCone.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/tailCone.nc - Starting the NetCDF creation at 2009-06-26T15:32:42Z - NetCDF creation finished at 2009-06-26T15:32: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/2008/2008328/2008.328.00/tailCone.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T15:32:42Z(start date = 2009-06-26T15:32:42Z, end date = 2009-06-26T15:32:42Z). - 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/2008/2008328/2008.328.00/tailCone.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/tailCone.nc.log. - UpdateBot DataProducer persisted and has ID 32517. - Deployment tailCone was changed and persisted to the database with ID 32348. 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/2008/2008328/2008.328.00/dvl.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/dvl.nc - Starting the NetCDF creation at 2009-06-26T15:32:44Z - NetCDF creation finished at 2009-06-26T15:32:44Z - 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/2008/2008328/2008.328.00/dvl.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T15:32:44Z(start date = 2009-06-26T15:32:44Z, end date = 2009-06-26T15:32:44Z). - 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/2008/2008328/2008.328.00/dvl.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-11-23T19:56:29Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-11-23T19:56:31Z to the end date of dvl.log. - Set the content length of dvl.log to 2205. - UpdateBot DataProducer persisted and has ID 32518. - Deployment dvl was changed and persisted to the database with ID 32349. 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/2008/2008328/2008.328.00/gps.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/gps.nc - Starting the NetCDF creation at 2009-06-26T15:32:46Z - NetCDF creation finished at 2009-06-26T15:32:46Z - 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/2008/2008328/2008.328.00/gps.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T15:32:46Z(start date = 2009-06-26T15:32:46Z, end date = 2009-06-26T15:32:46Z). - 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/2008/2008328/2008.328.00/gps.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-11-23T19:56:30Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-11-23T19:56:31Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.802302000000005 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80230216666667 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.7879301666667 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.7879301666667 to the max longitude of gps.log. - Set the content length of gps.log to 932. - UpdateBot DataProducer persisted and has ID 32519. - Deployment gps was changed and persisted to the database with ID 32350. 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/2008/2008328/2008.328.00/dynamicControl.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T15:32:49Z - NetCDF creation finished at 2009-06-26T15:32:49Z - 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/2008/2008328/2008.328.00/dynamicControl.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T15:32:49Z(start date = 2009-06-26T15:32:49Z, end date = 2009-06-26T15:32:49Z). - 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/2008/2008328/2008.328.00/dynamicControl.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/dynamicControl.nc.log. - UpdateBot DataProducer persisted and has ID 32520. - Deployment dynamicControl was changed and persisted to the database with ID 32351. 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/2008/2008328/2008.328.00/parosci.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF was flagged that it needed creating so it will be created at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/parosci.nc - Starting the NetCDF creation at 2009-06-26T15:32:51Z - NetCDF creation finished at 2009-06-26T15:32:51Z - 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/2008/2008328/2008.328.00/parosci.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2009-06-26T15:32:51Z(start date = 2009-06-26T15:32:51Z, end date = 2009-06-26T15:32:51Z). - 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/2008/2008328/2008.328.00/parosci.nc. - NetCDF creation log file Resource will be NetCDF Creation Log File at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008328/2008.328.00/parosci.nc.log. - UpdateBot DataProducer persisted and has ID 32521. - Deployment parosci was changed and persisted to the database with ID 32352. - Deployment 2008.328.00 was changed and persisted to the database with ID 32337. Processing for deployment 2008.328.00 ended at 2009-06-26T15:32:52Z