SSDS Processing Report for data sets from Deployment 2009.085.02 Processing began at 2009-03-27T03:12:28Z Going to try to convert any outputs of deployment 2009.085.02 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 13 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/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/dvl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-03-27T03:12:29Z - NetCDF creation finished at 2009-03-27T03:12:29Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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-03-27T03:12:29Z(start date = 2009-03-27T03:12:29Z, end date = 2009-03-27T03:12:29Z). - 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/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-26T19:07:40Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-03-26T22:05:34Z to the end date of dvl.log. - Set the content length of dvl.log to 1126809. - UpdateBot DataProducer persisted and has ID 30287. - Deployment dvl was changed and persisted to the database with ID 30260. Going to try to convert any outputs of deployment hydroscatlog to NetCDF files: - Working on output hydroscatlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/hydroscatlog.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/auvctd/missionlogs/2009/2009085/2009.085.02/hydroscatlog.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-03-27T03:12:34Z - NetCDF creation finished at 2009-03-27T03:12:37Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/hydroscatlog.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-03-27T03:12:34Z(start date = 2009-03-27T03:12:34Z, end date = 2009-03-27T03:12:37Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be hydroscatlog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/hydroscatlog.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/auvctd/missionlogs/2009/2009085/2009.085.02/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-26T19:07:46Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2009-03-26T22:05:34Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 3584218. - UpdateBot DataProducer persisted and has ID 30288. - Deployment hydroscatlog was changed and persisted to the database with ID 30261. Going to try to convert any outputs of deployment biolume to NetCDF files: - Working on output biolume.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/biolume.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF already exists and is up to date so no NetCDF will be created. Going to try to convert any outputs of deployment gps to NetCDF files: - Working on output gps.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/gps.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-03-27T03:12:40Z - NetCDF creation finished at 2009-03-27T03:12:40Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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-03-27T03:12:40Z(start date = 2009-03-27T03:12:40Z, end date = 2009-03-27T03:12:40Z). - 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/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-26T19:07:35Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-03-26T22:05:34Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.82346133333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.839519166666676 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.90086500000001 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.90514116666668 to the max longitude of gps.log. - Set the content length of gps.log to 40388. - UpdateBot DataProducer persisted and has ID 30290. - Deployment gps was changed and persisted to the database with ID 30263. Going to try to convert any outputs of deployment ctdDriver to NetCDF files: - Working on output ctdDriver.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/ctdDriver.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF already exists and is up to date so no NetCDF will be created. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_1290945370 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_1632379168 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_2020531855 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_989983582 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_452790880 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment bluefinBattlog to NetCDF files: - Working on output bluefinBattlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/bluefinBattlog.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF already exists and is up to date so no NetCDF will be created. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_1717288064 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_874867901 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_1369332132 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment lisstlog to NetCDF files: - Working on output lisstlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/lisstlog.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF already exists and is up to date so no NetCDF will be created. Going to try to convert any outputs of deployment parosci to NetCDF files: - Working on output parosci.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/parosci.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-03-27T03:12:43Z - NetCDF creation finished at 2009-03-27T03:12:46Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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-03-27T03:12:43Z(start date = 2009-03-27T03:12:43Z, end date = 2009-03-27T03:12:46Z). - 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/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-26T19:07:37Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-03-26T22:05:34Z 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 9542.196 to the max depth of parosci.log. - Set the content length of parosci.log to 4343606. - UpdateBot DataProducer persisted and has ID 30294. - Deployment parosci was changed and persisted to the database with ID 30275. Going to try to convert any outputs of deployment tailCone to NetCDF files: - Working on output tailCone.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/tailCone.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-03-27T03:12:49Z - NetCDF creation finished at 2009-03-27T03:12:50Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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-03-27T03:12:49Z(start date = 2009-03-27T03:12:49Z, end date = 2009-03-27T03:12:50Z). - 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/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-26T19:07:41Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-03-26T22:05:33Z to the end date of tailCone.log. - Set the content length of tailCone.log to 522187. - UpdateBot DataProducer persisted and has ID 30295. - Deployment tailCone was changed and persisted to the database with ID 30276. Going to try to convert any outputs of deployment navigation to NetCDF files: - Working on output navigation.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/navigation.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-03-27T03:12:53Z - NetCDF creation finished at 2009-03-27T03:12:58Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.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-03-27T03:12:53Z(start date = 2009-03-27T03:12:53Z, end date = 2009-03-27T03:12:58Z). - 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/auvctd/missionlogs/2009/2009085/2009.085.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/auvctd/missionlogs/2009/2009085/2009.085.02/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-26T19:08:09Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-03-26T22:05:34Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.8234647362058 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.84055642590234 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.91216059355379 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.89450259611604 to the max longitude of navigation.log. - Set the content length of navigation.log to 12556034. - UpdateBot DataProducer persisted and has ID 30296. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_1107303700 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_762934650 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:56Z_286060284 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 30277. Going to try to convert any outputs of deployment isuslog to NetCDF files: - Working on output isuslog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/isuslog.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF already exists and is up to date so no NetCDF will be created. Going to try to convert any outputs of deployment dynamicControl to NetCDF files: - Working on output dynamicControl.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/dynamicControl.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF already exists and is up to date so no NetCDF will be created. Going to try to convert any outputs of deployment ctdDriver2 to NetCDF files: - Working on output ctdDriver2.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2009/2009085/2009.085.02/ctdDriver2.log) - The RecordDescription and NoNetCDF flag show the output can be converted. - The NetCDF already exists and is up to date so no NetCDF will be created. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:57Z_2049913611 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:57Z_1520148288 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-26T23:22:57Z_723068850 to NetCDF files: - There were no direct outputs for that deployment. - Deployment 2009.085.02 was changed and persisted to the database with ID 30259. Processing for deployment 2009.085.02 ended at 2009-03-27T03:13:05Z