SSDS Processing Report for data sets from Deployment 2008.339.05 Processing began at 2009-06-26T16:49:35Z Going to try to convert any outputs of deployment 2008.339.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 dvl to NetCDF files: - Working on output dvl.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008339/2008.339.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/2008339/2008.339.05/dvl.nc - Starting the NetCDF creation at 2009-06-26T16:49:36Z - NetCDF creation finished at 2009-06-26T16:49:36Z - 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.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-26T16:49:36Z(start date = 2009-06-26T16:49:36Z, end date = 2009-06-26T16:49:36Z). - 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.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/2008339/2008.339.05/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:12:29Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:13:44Z to the end date of dvl.log. - Set the content length of dvl.log to 17805. - UpdateBot DataProducer persisted and has ID 32904. - Deployment dvl was changed and persisted to the database with ID 32649. 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.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/2008339/2008.339.05/tailCone.nc - Starting the NetCDF creation at 2009-06-26T16:49:37Z - NetCDF creation finished at 2009-06-26T16:49:37Z - 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.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-26T16:49:37Z(start date = 2009-06-26T16:49:37Z, end date = 2009-06-26T16:49:37Z). - 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.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/2008339/2008.339.05/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:12:32Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:13:44Z to the end date of tailCone.log. - Set the content length of tailCone.log to 4459. - UpdateBot DataProducer persisted and has ID 32905. - Deployment tailCone was changed and persisted to the database with ID 32650. 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.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/2008339/2008.339.05/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T16:49:39Z - NetCDF creation finished at 2009-06-26T16:49:39Z - 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.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-26T16:49:39Z(start date = 2009-06-26T16:49:39Z, end date = 2009-06-26T16:49:39Z). - 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.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/2008339/2008.339.05/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:12:56Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:13:06Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 1487. - UpdateBot DataProducer persisted and has ID 32906. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:49Z_658628789 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:49Z_1100598932 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:49Z_932544661 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32651. 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.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/2008339/2008.339.05/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T16:49:40Z - NetCDF creation finished at 2009-06-26T16:49: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/2008339/2008.339.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-26T16:49:40Z(start date = 2009-06-26T16:49:40Z, end date = 2009-06-26T16:49:40Z). - 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.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/2008339/2008.339.05/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:13:00Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:13:44Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 57186. - UpdateBot DataProducer persisted and has ID 32907. - Deployment dynamicControl was changed and persisted to the database with ID 32655. 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.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/2008339/2008.339.05/gps.nc - Starting the NetCDF creation at 2009-06-26T16:49:42Z - NetCDF creation finished at 2009-06-26T16:49: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/2008339/2008.339.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-26T16:49:42Z(start date = 2009-06-26T16:49:42Z, end date = 2009-06-26T16:49:42Z). - 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.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/2008339/2008.339.05/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:12:29Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:13:43Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.829850166666674 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.830000000000005 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.87328433333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.87347033333337 to the max longitude of gps.log. - Set the content length of gps.log to 6188. - UpdateBot DataProducer persisted and has ID 32908. - Deployment gps was changed and persisted to the database with ID 32656. 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.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/2008339/2008.339.05/navigation.nc - Starting the NetCDF creation at 2009-06-26T16:49:43Z - NetCDF creation finished at 2009-06-26T16:49: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/2008339/2008.339.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-26T16:49:43Z(start date = 2009-06-26T16:49:43Z, end date = 2009-06-26T16:49:44Z). - 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.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/2008339/2008.339.05/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:13:00Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:13:44Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.82984993896235 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.8300019443101 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.87347126216308 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.87328450466187 to the max longitude of navigation.log. - Set the content length of navigation.log to 54878. - UpdateBot DataProducer persisted and has ID 32909. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:50Z_2109444519 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:50Z_1967561763 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:50Z_552434138 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32657. 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.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/2008339/2008.339.05/parosci.nc - Starting the NetCDF creation at 2009-06-26T16:49:45Z - NetCDF creation finished at 2009-06-26T16:49:45Z - 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.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-26T16:49:45Z(start date = 2009-06-26T16:49:45Z, end date = 2009-06-26T16:49:45Z). - 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.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/2008339/2008.339.05/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:12:35Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:13:44Z 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.22107324 to the max depth of parosci.log. - Set the content length of parosci.log to 27398. - UpdateBot DataProducer persisted and has ID 32910. - Deployment parosci was changed and persisted to the database with ID 32661. - Deployment 2008.339.05 was changed and persisted to the database with ID 32648. Processing for deployment 2008.339.05 ended at 2009-06-26T16:49:46Z