SSDS Processing Report for data sets from Deployment 2008.338.05 Processing began at 2009-06-26T15:39:44Z Going to try to convert any outputs of deployment 2008.338.05 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/2008/2008338/2008.338.05/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/2008338/2008.338.05/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T15:39:45Z - NetCDF creation finished at 2009-06-26T15:39: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/2008338/2008.338.05/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-26T15:39:45Z(start date = 2009-06-26T15:39:45Z, end date = 2009-06-26T15:39:46Z). - 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/2008338/2008.338.05/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/2008338/2008.338.05/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:11:27Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:12:27Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 2127. - UpdateBot DataProducer persisted and has ID 32566. - 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:34Z_440647517 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:34Z_1450862381 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:34Z_1257257516 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32460. 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/2008338/2008.338.05/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/2008338/2008.338.05/dvl.nc - Starting the NetCDF creation at 2009-06-26T15:39:48Z - NetCDF creation finished at 2009-06-26T15:39:48Z - 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/2008338/2008.338.05/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:39:48Z(start date = 2009-06-26T15:39:48Z, end date = 2009-06-26T15:39:48Z). - 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/2008338/2008.338.05/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/2008338/2008.338.05/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:10:59Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:12:31Z to the end date of dvl.log. - Set the content length of dvl.log to 23889. - UpdateBot DataProducer persisted and has ID 32567. - Deployment dvl was changed and persisted to the database with ID 32464. 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/2008338/2008.338.05/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/2008338/2008.338.05/gps.nc - Starting the NetCDF creation at 2009-06-26T15:39:51Z - NetCDF creation finished at 2009-06-26T15:39: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/2008338/2008.338.05/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:39:51Z(start date = 2009-06-26T15:39:51Z, end date = 2009-06-26T15:39:51Z). - 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/2008338/2008.338.05/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/2008338/2008.338.05/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:11:01Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:12:31Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.80234083333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80247066666668 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.78754983333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.78788083333336 to the max longitude of gps.log. - Set the content length of gps.log to 7340. - UpdateBot DataProducer persisted and has ID 32568. - Deployment gps was changed and persisted to the database with ID 32465. 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/2008338/2008.338.05/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/2008338/2008.338.05/navigation.nc - Starting the NetCDF creation at 2009-06-26T15:39:53Z - NetCDF creation finished at 2009-06-26T15:39:53Z - 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/2008338/2008.338.05/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:39:53Z(start date = 2009-06-26T15:39:53Z, end date = 2009-06-26T15:39:53Z). - 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/2008338/2008.338.05/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/2008338/2008.338.05/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:11:31Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:12:31Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.80236316666485 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.80247066666487 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.78788083332664 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.78754983332662 to the max longitude of navigation.log. - Set the content length of navigation.log to 73994. - UpdateBot DataProducer persisted and has ID 32569. - 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:34Z_375949494 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:34Z_1081944249 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:34Z_1513244348 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32466. 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/2008338/2008.338.05/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/2008338/2008.338.05/tailCone.nc - Starting the NetCDF creation at 2009-06-26T15:39:56Z - NetCDF creation finished at 2009-06-26T15:39:56Z - 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/2008338/2008.338.05/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:39:56Z(start date = 2009-06-26T15:39:56Z, end date = 2009-06-26T15:39:56Z). - 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/2008338/2008.338.05/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/2008338/2008.338.05/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:11:04Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:12:31Z to the end date of tailCone.log. - Set the content length of tailCone.log to 5803. - UpdateBot DataProducer persisted and has ID 32570. - Deployment tailCone was changed and persisted to the database with ID 32470. 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/2008338/2008.338.05/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/2008338/2008.338.05/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T15:39:59Z - NetCDF creation finished at 2009-06-26T15:39:59Z - 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/2008338/2008.338.05/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:39:59Z(start date = 2009-06-26T15:39:59Z, end date = 2009-06-26T15:39:59Z). - 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/2008338/2008.338.05/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/2008338/2008.338.05/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:11:31Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:12:31Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 77436. - UpdateBot DataProducer persisted and has ID 32571. - Deployment dynamicControl was changed and persisted to the database with ID 32471. 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/2008338/2008.338.05/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/2008338/2008.338.05/parosci.nc - Starting the NetCDF creation at 2009-06-26T15:40:01Z - NetCDF creation finished at 2009-06-26T15:40:02Z - 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/2008338/2008.338.05/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:40:01Z(start date = 2009-06-26T15:40:01Z, end date = 2009-06-26T15:40:02Z). - 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/2008338/2008.338.05/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/2008338/2008.338.05/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:11:06Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:12:31Z 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 0.04446983 to the max depth of parosci.log. - Set the content length of parosci.log to 33686. - UpdateBot DataProducer persisted and has ID 32572. - Deployment parosci was changed and persisted to the database with ID 32472. - Deployment 2008.338.05 was changed and persisted to the database with ID 32459. Processing for deployment 2008.338.05 ended at 2009-06-26T15:40:03Z