SSDS Processing Report for data sets from Deployment 2009.103.05 Processing began at 2009-04-14T20:55:46Z Going to try to convert any outputs of deployment 2009.103.05 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.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/2009/2009103/2009.103.05/navigation.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:55:46Z - NetCDF creation finished at 2009-04-14T20:55:47Z - 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.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-04-14T20:55:46Z(start date = 2009-04-14T20:55:46Z, end date = 2009-04-14T20:55:47Z). - 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.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/2009/2009103/2009.103.05/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T18:33:58Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:59:24Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.809811832931636 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.81345718575725 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.97593624421752 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.9700261407785 to the max longitude of navigation.log. - Set the content length of navigation.log to 1802930. - UpdateBot DataProducer persisted and has ID 31247. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-04-14T20:19:27Z_22485424 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-04-14T20:19:27Z_1079216113 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-04-14T20:19:27Z_1097245098 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 31238. 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.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/2009/2009103/2009.103.05/parosci.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:55:49Z - NetCDF creation finished at 2009-04-14T20:55: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.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-04-14T20:55:49Z(start date = 2009-04-14T20:55:49Z, end date = 2009-04-14T20:55:49Z). - 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.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/2009/2009103/2009.103.05/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T18:33:43Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:59:24Z 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 89.914894 to the max depth of parosci.log. - Set the content length of parosci.log to 606422. - UpdateBot DataProducer persisted and has ID 31248. - Deployment parosci was changed and persisted to the database with ID 31242. 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.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/2009/2009103/2009.103.05/dvl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:55:51Z - NetCDF creation finished at 2009-04-14T20:55: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.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-04-14T20:55:51Z(start date = 2009-04-14T20:55:51Z, end date = 2009-04-14T20:55: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.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/2009/2009103/2009.103.05/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T18:33:37Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:59:24Z to the end date of dvl.log. - Set the content length of dvl.log to 380661. - UpdateBot DataProducer persisted and has ID 31249. - Deployment dvl was changed and persisted to the database with ID 31243. 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.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/2009/2009103/2009.103.05/tailCone.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:55:53Z - NetCDF creation finished at 2009-04-14T20:55: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.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-04-14T20:55:53Z(start date = 2009-04-14T20:55:53Z, end date = 2009-04-14T20:55: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.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/2009/2009103/2009.103.05/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T18:33:42Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:59:23Z to the end date of tailCone.log. - Set the content length of tailCone.log to 75403. - UpdateBot DataProducer persisted and has ID 31250. - Deployment tailCone was changed and persisted to the database with ID 31244. 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.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/2009/2009103/2009.103.05/dynamicControl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:55:54Z - NetCDF creation finished at 2009-04-14T20:55:55Z - 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.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-04-14T20:55:54Z(start date = 2009-04-14T20:55:54Z, end date = 2009-04-14T20:55:55Z). - 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.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/2009/2009103/2009.103.05/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T18:33:58Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:59:24Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 1908936. - UpdateBot DataProducer persisted and has ID 31251. - Deployment dynamicControl was changed and persisted to the database with ID 31245. 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.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/2009/2009103/2009.103.05/gps.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:55:57Z - NetCDF creation finished at 2009-04-14T20:55:57Z - 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.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-04-14T20:55:57Z(start date = 2009-04-14T20:55:57Z, end date = 2009-04-14T20:55:57Z). - 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.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/2009/2009103/2009.103.05/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T18:33:37Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:59:23Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.81152083333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.812436000000005 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.97317450000003 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.97543400000004 to the max longitude of gps.log. - Set the content length of gps.log to 9644. - UpdateBot DataProducer persisted and has ID 31252. - Deployment gps was changed and persisted to the database with ID 31246. - Deployment 2009.103.05 was changed and persisted to the database with ID 31237. Processing for deployment 2009.103.05 ended at 2009-04-14T20:55:58Z