SSDS Processing Report for data sets from Deployment 2008.339.08 Processing began at 2009-06-26T16:51:02Z Going to try to convert any outputs of deployment 2008.339.08 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 parosci to NetCDF files: - Working on output parosci.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008339/2008.339.08/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/2008339/2008.339.08/parosci.nc - Starting the NetCDF creation at 2009-06-26T16:51:02Z - NetCDF creation finished at 2009-06-26T16:51:03Z - 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/2008339/2008.339.08/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-26T16:51:02Z(start date = 2009-06-26T16:51:02Z, end date = 2009-06-26T16:51:03Z). - 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/2008339/2008.339.08/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/2008339/2008.339.08/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:49:10Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T19:03:33Z 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 69.65856 to the max depth of parosci.log. - Set the content length of parosci.log to 339254. - UpdateBot DataProducer persisted and has ID 32935. - Deployment parosci was changed and persisted to the database with ID 32695. 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/2008339/2008.339.08/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/2008339/2008.339.08/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T16:51:04Z - NetCDF creation finished at 2009-06-26T16:51:05Z - 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/2008339/2008.339.08/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-26T16:51:04Z(start date = 2009-06-26T16:51:04Z, end date = 2009-06-26T16:51:05Z). - 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/2008339/2008.339.08/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/2008339/2008.339.08/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:49:34Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T19:03:33Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 1049686. - UpdateBot DataProducer persisted and has ID 32936. - Deployment dynamicControl was changed and persisted to the database with ID 32696. 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/2008339/2008.339.08/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/2008339/2008.339.08/dvl.nc - Starting the NetCDF creation at 2009-06-26T16:51:07Z - NetCDF creation finished at 2009-06-26T16: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/auvbi/missionlogs/2008/2008339/2008.339.08/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-26T16:51:07Z(start date = 2009-06-26T16:51:07Z, end date = 2009-06-26T16:51:07Z). - 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/2008339/2008.339.08/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/2008339/2008.339.08/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:49:03Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T19:03:32Z to the end date of dvl.log. - Set the content length of dvl.log to 217329. - UpdateBot DataProducer persisted and has ID 32937. - Deployment dvl was changed and persisted to the database with ID 32697. 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/2008339/2008.339.08/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/2008339/2008.339.08/navigation.nc - Starting the NetCDF creation at 2009-06-26T16:51:08Z - NetCDF creation finished at 2009-06-26T16:51:09Z - 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/2008339/2008.339.08/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-26T16:51:08Z(start date = 2009-06-26T16:51:08Z, end date = 2009-06-26T16:51:09Z). - 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/2008339/2008.339.08/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/2008339/2008.339.08/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:49:34Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T19:03:33Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.83105225737119 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.83301182596289 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.89684280697408 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.8824054999962 to the max longitude of navigation.log. - Set the content length of navigation.log to 991798. - UpdateBot DataProducer persisted and has ID 32938. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:11Z_438083376 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:11Z_1055678546 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:11Z_561476940 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32698. 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/2008339/2008.339.08/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/2008339/2008.339.08/gps.nc - Starting the NetCDF creation at 2009-06-26T16:51:11Z - NetCDF creation finished at 2009-06-26T16:51:11Z - 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/2008339/2008.339.08/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-26T16:51:11Z(start date = 2009-06-26T16:51:11Z, end date = 2009-06-26T16:51:11Z). - 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/2008339/2008.339.08/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/2008339/2008.339.08/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:49:04Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T19:03:32Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.83105200000001 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.83252883333334 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.8823791666667 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.89684250000002 to the max longitude of gps.log. - Set the content length of gps.log to 7268. - UpdateBot DataProducer persisted and has ID 32939. - Deployment gps was changed and persisted to the database with ID 32702. 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/2008/2008339/2008.339.08/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/2008/2008339/2008.339.08/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T16:51:12Z - NetCDF creation finished at 2009-06-26T16:51:13Z - 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/2008339/2008.339.08/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-26T16:51:12Z(start date = 2009-06-26T16:51:12Z, end date = 2009-06-26T16:51:13Z). - 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/2008/2008339/2008.339.08/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/2008/2008339/2008.339.08/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:49:31Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T19:03:31Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 4431. - UpdateBot DataProducer persisted and has ID 32940. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:11Z_298388885 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:11Z_1111303093 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:11Z_1950890128 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32703. 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/2008339/2008.339.08/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/2008339/2008.339.08/tailCone.nc - Starting the NetCDF creation at 2009-06-26T16:51:14Z - NetCDF creation finished at 2009-06-26T16: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/auvbi/missionlogs/2008/2008339/2008.339.08/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-26T16:51:14Z(start date = 2009-06-26T16:51:14Z, end date = 2009-06-26T16:51:14Z). - 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/2008339/2008.339.08/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/2008339/2008.339.08/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:49:08Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T19:03:32Z to the end date of tailCone.log. - Set the content length of tailCone.log to 42763. - UpdateBot DataProducer persisted and has ID 32941. - Deployment tailCone was changed and persisted to the database with ID 32707. - Deployment 2008.339.08 was changed and persisted to the database with ID 32694. Processing for deployment 2008.339.08 ended at 2009-06-26T16:51:16Z