SSDS Processing Report for data sets from Deployment 2008.339.09 Processing began at 2009-06-26T16:51:33Z Going to try to convert any outputs of deployment 2008.339.09 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.09/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.09/dvl.nc - Starting the NetCDF creation at 2009-06-26T16:51:34Z - NetCDF creation finished at 2009-06-26T16:51:34Z - 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.09/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:34Z(start date = 2009-06-26T16:51:34Z, end date = 2009-06-26T16:51:34Z). - 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.09/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.09/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T20:16:57Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T20:25:38Z to the end date of dvl.log. - Set the content length of dvl.log to 130281. - UpdateBot DataProducer persisted and has ID 32952. - Deployment dvl was changed and persisted to the database with ID 32713. 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.09/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.09/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T16:51:35Z - NetCDF creation finished at 2009-06-26T16:51: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.09/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:35Z(start date = 2009-06-26T16:51:35Z, end date = 2009-06-26T16:51:36Z). - 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.09/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.09/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T20:17:29Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T20:25:38Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 612436. - UpdateBot DataProducer persisted and has ID 32953. - Deployment dynamicControl was changed and persisted to the database with ID 32714. 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.09/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.09/tailCone.nc - Starting the NetCDF creation at 2009-06-26T16:51:37Z - NetCDF creation finished at 2009-06-26T16:51: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.09/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:37Z(start date = 2009-06-26T16:51:37Z, end date = 2009-06-26T16:51: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.09/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.09/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T20:17:01Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T20:25:37Z to the end date of tailCone.log. - Set the content length of tailCone.log to 27019. - UpdateBot DataProducer persisted and has ID 32954. - Deployment tailCone was changed and persisted to the database with ID 32715. 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.09/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.09/navigation.nc - Starting the NetCDF creation at 2009-06-26T16:51:39Z - NetCDF creation finished at 2009-06-26T16:51: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.09/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:39Z(start date = 2009-06-26T16:51:39Z, end date = 2009-06-26T16:51: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/2008/2008339/2008.339.09/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.09/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T20:17:29Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T20:25:38Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.83420891455081 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.8344304663559 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.88511825648152 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.87776409762162 to the max longitude of navigation.log. - Set the content length of navigation.log to 579034. - UpdateBot DataProducer persisted and has ID 32965. - 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:23Z_1209268999 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:23Z_1568609453 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:23Z_1243300602 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32716. 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.09/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.09/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T16:51:41Z - NetCDF creation finished at 2009-06-26T16:51:41Z - 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.09/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:41Z(start date = 2009-06-26T16:51:41Z, end date = 2009-06-26T16:51:41Z). - 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.09/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.09/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T20:17:25Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T20:24:55Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 2895. - UpdateBot DataProducer persisted and has ID 32966. - 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:23Z_706309198 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:23Z_483446557 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:23Z_68228076 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32720. 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.09/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.09/gps.nc - Starting the NetCDF creation at 2009-06-26T16:51:43Z - NetCDF creation finished at 2009-06-26T16:51:43Z - 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.09/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:43Z(start date = 2009-06-26T16:51:43Z, end date = 2009-06-26T16:51:43Z). - 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.09/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.09/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T20:16:59Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T20:18:32Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.83419966666667 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.83422633333335 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.87771533333334 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.87840316666671 to the max longitude of gps.log. - Set the content length of gps.log to 7556. - UpdateBot DataProducer persisted and has ID null. - Deployment gps was changed and persisted to the database with ID 32724. 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.09/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.09/parosci.nc - Starting the NetCDF creation at 2009-06-26T16:51:48Z - NetCDF creation finished at 2009-06-26T16:51: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/2008339/2008.339.09/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:48Z(start date = 2009-06-26T16:51:48Z, end date = 2009-06-26T16:51:48Z). - 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.09/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.09/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T20:17:05Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T20:25:38Z 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 66.890274 to the max depth of parosci.log. - Set the content length of parosci.log to 201782. - UpdateBot DataProducer persisted and has ID 32981. - Deployment parosci was changed and persisted to the database with ID 32725. - Deployment 2008.339.09 was changed and persisted to the database with ID 32712. Processing for deployment 2008.339.09 ended at 2009-06-26T16:51:50Z