SSDS Processing Report for data sets from Deployment 2008.339.01 Processing began at 2009-06-26T16:48:27Z Going to try to convert any outputs of deployment 2008.339.01 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 gps to NetCDF files: - Working on output gps.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008339/2008.339.01/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.01/gps.nc - Starting the NetCDF creation at 2009-06-26T16:48:28Z - NetCDF creation finished at 2009-06-26T16:48:28Z - 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.01/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:48:28Z(start date = 2009-06-26T16:48:28Z, end date = 2009-06-26T16:48:28Z). - 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.01/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.01/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T16:48:44Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T16:50:15Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.80267400000001 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80268983333334 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.78692183333335 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.78693266666669 to the max longitude of gps.log. - Set the content length of gps.log to 7412. - UpdateBot DataProducer persisted and has ID 32770. - Deployment gps was changed and persisted to the database with ID 32619. 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.01/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.01/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T16:48:30Z - NetCDF creation finished at 2009-06-26T16:48:30Z - 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.01/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:48:30Z(start date = 2009-06-26T16:48:30Z, end date = 2009-06-26T16:48:30Z). - 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.01/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.01/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T16:49:11Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T16:50:11Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 2127. - UpdateBot DataProducer persisted and has ID 32781. - 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:42Z_1983994220 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:42Z_277480917 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:42Z_433051166 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32620. 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.01/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.01/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T16:48:32Z - NetCDF creation finished at 2009-06-26T16:48:32Z - 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.01/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:48:32Z(start date = 2009-06-26T16:48:32Z, end date = 2009-06-26T16:48:32Z). - 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.01/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.01/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T16:49:15Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T16:50:15Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 77186. - UpdateBot DataProducer persisted and has ID 32782. - Deployment dynamicControl was changed and persisted to the database with ID 32624. 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.01/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.01/parosci.nc - Starting the NetCDF creation at 2009-06-26T16:48:34Z - NetCDF creation finished at 2009-06-26T16:48: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.01/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:48:34Z(start date = 2009-06-26T16:48:34Z, end date = 2009-06-26T16:48:34Z). - 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.01/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.01/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T16:48:50Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T16:50:15Z 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.047470693 to the max depth of parosci.log. - Set the content length of parosci.log to 33638. - UpdateBot DataProducer persisted and has ID null. - Deployment parosci was changed and persisted to the database with ID 32625. 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.01/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.01/tailCone.nc - Starting the NetCDF creation at 2009-06-26T16:48:38Z - NetCDF creation finished at 2009-06-26T16:48: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/2008339/2008.339.01/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:48:38Z(start date = 2009-06-26T16:48:38Z, end date = 2009-06-26T16:48:38Z). - 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.01/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.01/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T16:48:47Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T16:50:15Z to the end date of tailCone.log. - Set the content length of tailCone.log to 5851. - UpdateBot DataProducer persisted and has ID 32794. - Deployment tailCone was changed and persisted to the database with ID 32626. 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.01/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.01/navigation.nc - Starting the NetCDF creation at 2009-06-26T16:48:39Z - NetCDF creation finished at 2009-06-26T16:48: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.01/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:48:39Z(start date = 2009-06-26T16:48:39Z, end date = 2009-06-26T16:48: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.01/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.01/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T16:49:15Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T16:50:15Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.80267385960738 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.80268804936118 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.78693286638659 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.7869245017499 to the max longitude of navigation.log. - Set the content length of navigation.log to 73758. - UpdateBot DataProducer persisted and has ID 32795. - 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:43Z_1930066386 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:43Z_416831691 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:43Z_1184616805 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32627. 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.01/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.01/dvl.nc - Starting the NetCDF creation at 2009-06-26T16:48:41Z - NetCDF creation finished at 2009-06-26T16:48: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.01/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:48:41Z(start date = 2009-06-26T16:48:41Z, end date = 2009-06-26T16:48:41Z). - 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.01/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.01/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T16:48:43Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T16:50:15Z to the end date of dvl.log. - Set the content length of dvl.log to 23733. - UpdateBot DataProducer persisted and has ID 32796. - Deployment dvl was changed and persisted to the database with ID 32631. - Deployment 2008.339.01 was changed and persisted to the database with ID 32618. Processing for deployment 2008.339.01 ended at 2009-06-26T16:48:43Z