SSDS Processing Report for data sets from Deployment 2009.103.02 Processing began at 2009-04-14T20:54:48Z Going to try to convert any outputs of deployment 2009.103.02 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 6 of them) 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/navigation.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:48Z - NetCDF creation finished at 2009-04-14T20:54:49Z - 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/2009/2009103/2009.103.02/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-04-14T20:54:48Z(start date = 2009-04-14T20:54:48Z, end date = 2009-04-14T20:54:49Z). - 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:41:47Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:55:29Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.81198097908767 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.81264368632516 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.97502066722264 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.96992316272527 to the max longitude of navigation.log. - Set the content length of navigation.log to 973154. - UpdateBot DataProducer persisted and has ID 31199. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-04-14T20:12:15Z_519748246 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-04-14T20:12:15Z_73460552 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-04-14T20:12:15Z_53529725 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 31190. 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/dvl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:51Z - NetCDF creation finished at 2009-04-14T20:54: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/2009/2009103/2009.103.02/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-04-14T20:54:51Z(start date = 2009-04-14T20:54:51Z, end date = 2009-04-14T20:54:51Z). - 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:41:27Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:55:29Z to the end date of dvl.log. - Set the content length of dvl.log to 205317. - UpdateBot DataProducer persisted and has ID 31200. - Deployment dvl was changed and persisted to the database with ID 31194. 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/tailCone.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:53Z - NetCDF creation finished at 2009-04-14T20:54: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/2009/2009103/2009.103.02/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-04-14T20:54:53Z(start date = 2009-04-14T20:54:53Z, end date = 2009-04-14T20:54:53Z). - 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:41:30Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:55:29Z to the end date of tailCone.log. - Set the content length of tailCone.log to 41515. - UpdateBot DataProducer persisted and has ID 31201. - Deployment tailCone was changed and persisted to the database with ID 31195. 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/parosci.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:54Z - NetCDF creation finished at 2009-04-14T20:54:54Z - 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/2009/2009103/2009.103.02/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-04-14T20:54:54Z(start date = 2009-04-14T20:54:54Z, end date = 2009-04-14T20:54:54Z). - 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:41:32Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:55:29Z 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 71.25532 to the max depth of parosci.log. - Set the content length of parosci.log to 329510. - UpdateBot DataProducer persisted and has ID 31202. - Deployment parosci was changed and persisted to the database with ID 31196. 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/gps.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:56Z - NetCDF creation finished at 2009-04-14T20:54: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/2009/2009103/2009.103.02/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-04-14T20:54:56Z(start date = 2009-04-14T20:54:56Z, end date = 2009-04-14T20:54:56Z). - 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:41:27Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:55:29Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.811981666666675 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.81253883333335 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.9736851666667 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.97501850000003 to the max longitude of gps.log. - Set the content length of gps.log to 5036. - UpdateBot DataProducer persisted and has ID 31203. - Deployment gps was changed and persisted to the database with ID 31197. 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/dynamicControl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:57Z - NetCDF creation finished at 2009-04-14T20:54:58Z - 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/2009/2009103/2009.103.02/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-04-14T20:54:57Z(start date = 2009-04-14T20:54:57Z, end date = 2009-04-14T20:54:58Z). - 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/2009/2009103/2009.103.02/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/2009/2009103/2009.103.02/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:41:47Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:55:29Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 1029936. - UpdateBot DataProducer persisted and has ID 31204. - Deployment dynamicControl was changed and persisted to the database with ID 31198. - Deployment 2009.103.02 was changed and persisted to the database with ID 31189. Processing for deployment 2009.103.02 ended at 2009-04-14T20:54:59Z