SSDS Processing Report for data sets from Deployment 2009.103.01 Processing began at 2009-04-14T20:54:26Z Going to try to convert any outputs of deployment 2009.103.01 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 parosci to NetCDF files: - Working on output parosci.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009103/2009.103.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/2009/2009103/2009.103.01/parosci.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:26Z - NetCDF creation finished at 2009-04-14T20:54:27Z - 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.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-04-14T20:54:26Z(start date = 2009-04-14T20:54:26Z, end date = 2009-04-14T20:54:27Z). - 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.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/2009/2009103/2009.103.01/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:16:24Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:33:21Z 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.20049 to the max depth of parosci.log. - Set the content length of parosci.log to 400022. - UpdateBot DataProducer persisted and has ID 31183. - Deployment parosci was changed and persisted to the database with ID 31174. 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.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/2009/2009103/2009.103.01/navigation.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:29Z - NetCDF creation finished at 2009-04-14T20:54:29Z - 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.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-04-14T20:54:29Z(start date = 2009-04-14T20:54:29Z, end date = 2009-04-14T20:54:29Z). - 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.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/2009/2009103/2009.103.01/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:16:39Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:33:21Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.811833806850196 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.812801455519796 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.97510609300892 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.96991813790251 to the max longitude of navigation.log. - Set the content length of navigation.log to 1184610. - UpdateBot DataProducer persisted and has ID 31184. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-04-14T20:11:41Z_1721506668 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-04-14T20:11:41Z_1228250276 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-04-14T20:11:41Z_1940704853 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 31175. 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.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/2009/2009103/2009.103.01/dynamicControl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:32Z - NetCDF creation finished at 2009-04-14T20:54: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/2009/2009103/2009.103.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-04-14T20:54:32Z(start date = 2009-04-14T20:54:32Z, end date = 2009-04-14T20:54: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/2009/2009103/2009.103.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/2009/2009103/2009.103.01/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:16:39Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:33:21Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 1253936. - UpdateBot DataProducer persisted and has ID 31185. - Deployment dynamicControl was changed and persisted to the database with ID 31179. 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.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/2009/2009103/2009.103.01/dvl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:35Z - NetCDF creation finished at 2009-04-14T20:54:35Z - 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.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-04-14T20:54:35Z(start date = 2009-04-14T20:54:35Z, end date = 2009-04-14T20:54:35Z). - 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.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/2009/2009103/2009.103.01/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:16:18Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:33:20Z to the end date of dvl.log. - Set the content length of dvl.log to 244317. - UpdateBot DataProducer persisted and has ID 31186. - Deployment dvl was changed and persisted to the database with ID 31180. 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.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/2009/2009103/2009.103.01/gps.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:37Z - NetCDF creation finished at 2009-04-14T20:54: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/2009/2009103/2009.103.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-04-14T20:54:37Z(start date = 2009-04-14T20:54:37Z, end date = 2009-04-14T20:54:37Z). - 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.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/2009/2009103/2009.103.01/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:16:19Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:33:21Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.81183400000001 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.81280133333334 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.97488150000002 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.97509383333335 to the max longitude of gps.log. - Set the content length of gps.log to 12452. - UpdateBot DataProducer persisted and has ID 31187. - Deployment gps was changed and persisted to the database with ID 31181. 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.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/2009/2009103/2009.103.01/tailCone.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-14T20:54:38Z - NetCDF creation finished at 2009-04-14T20:54: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/2009/2009103/2009.103.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-04-14T20:54:38Z(start date = 2009-04-14T20:54:38Z, end date = 2009-04-14T20:54:39Z). - 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.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/2009/2009103/2009.103.01/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-04-13T16:16:22Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-04-13T16:33:20Z to the end date of tailCone.log. - Set the content length of tailCone.log to 51067. - UpdateBot DataProducer persisted and has ID 31188. - Deployment tailCone was changed and persisted to the database with ID 31182. - Deployment 2009.103.01 was changed and persisted to the database with ID 31173. Processing for deployment 2009.103.01 ended at 2009-04-14T20:54:41Z