SSDS Processing Report for data sets from Deployment 2009.168.05 Processing began at 2009-06-26T17:42:53Z Going to try to convert any outputs of deployment 2009.168.05 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 dvl to NetCDF files: - Working on output dvl.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.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/2009168/2009.168.05/dvl.nc - Starting the NetCDF creation at 2009-06-26T17:42:53Z - NetCDF creation finished at 2009-06-26T17:42: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/2009168/2009.168.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-06-26T17:42:53Z(start date = 2009-06-26T17:42:53Z, end date = 2009-06-26T17:42:53Z). - 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/2009168/2009.168.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/2009168/2009.168.05/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T19:09:32Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T19:25:28Z to the end date of dvl.log. - Set the content length of dvl.log to 216705. - UpdateBot DataProducer persisted and has ID 34171. - Deployment dvl was changed and persisted to the database with ID 33868. 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/2009168/2009.168.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/2009168/2009.168.05/tailCone.nc - Starting the NetCDF creation at 2009-06-26T17:42:56Z - NetCDF creation finished at 2009-06-26T17:42: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/2009168/2009.168.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-06-26T17:42:56Z(start date = 2009-06-26T17:42:56Z, end date = 2009-06-26T17:42:56Z). - 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/2009168/2009.168.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/2009168/2009.168.05/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T19:09:31Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T19:25:29Z to the end date of tailCone.log. - Set the content length of tailCone.log to 230347. - UpdateBot DataProducer persisted and has ID 34172. - Deployment tailCone was changed and persisted to the database with ID 33869. 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/2009/2009168/2009.168.05/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/2009/2009168/2009.168.05/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T17:42:58Z - NetCDF creation finished at 2009-06-26T17:42: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/2009168/2009.168.05/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-26T17:42:58Z(start date = 2009-06-26T17:42:58Z, end date = 2009-06-26T17:42:58Z). - 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/2009/2009168/2009.168.05/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/2009/2009168/2009.168.05/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T19:09:57Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T19:25:27Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 6991. - UpdateBot DataProducer persisted and has ID 34173. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:09:01Z_1833941011 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:09:01Z_1216193412 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:09:01Z_379021498 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 33870. 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/2009168/2009.168.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/2009168/2009.168.05/navigation.nc - Starting the NetCDF creation at 2009-06-26T17:43:01Z - NetCDF creation finished at 2009-06-26T17:43:02Z - 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/2009168/2009.168.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-06-26T17:43:01Z(start date = 2009-06-26T17:43:01Z, end date = 2009-06-26T17:43:02Z). - 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/2009168/2009.168.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/2009168/2009.168.05/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T19:09:52Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T19:25:29Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.80934540245447 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.814829185545726 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.97803447798188 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.97130905229672 to the max longitude of navigation.log. - Set the content length of navigation.log to 1107438. - UpdateBot DataProducer persisted and has ID 34174. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:09:01Z_740529830 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:09:01Z_1599398815 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:09:01Z_552757776 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 33874. 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/2009168/2009.168.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/2009168/2009.168.05/gps.nc - Starting the NetCDF creation at 2009-06-26T17:43:04Z - NetCDF creation finished at 2009-06-26T17:43:04Z - 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/2009168/2009.168.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-06-26T17:43:04Z(start date = 2009-06-26T17:43:04Z, end date = 2009-06-26T17:43:04Z). - 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/2009168/2009.168.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/2009168/2009.168.05/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T19:09:31Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T19:10:39Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.80934533333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80955933333334 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.9713091666667 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.97147033333336 to the max longitude of gps.log. - Set the content length of gps.log to 5756. - UpdateBot DataProducer persisted and has ID 34175. - Deployment gps was changed and persisted to the database with ID 33878. 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/2009168/2009.168.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/2009168/2009.168.05/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T17:43:08Z - NetCDF creation finished at 2009-06-26T17:43:08Z - 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/2009168/2009.168.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-06-26T17:43:08Z(start date = 2009-06-26T17:43:08Z, end date = 2009-06-26T17:43:08Z). - 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/2009168/2009.168.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/2009168/2009.168.05/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T19:09:52Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T19:25:29Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 1172186. - UpdateBot DataProducer persisted and has ID 34176. - Deployment dynamicControl was changed and persisted to the database with ID 33879. 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/2009168/2009.168.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/2009168/2009.168.05/parosci.nc - Starting the NetCDF creation at 2009-06-26T17:43:10Z - NetCDF creation finished at 2009-06-26T17:43:10Z - 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/2009168/2009.168.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-06-26T17:43:10Z(start date = 2009-06-26T17:43:10Z, end date = 2009-06-26T17:43:10Z). - 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/2009168/2009.168.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/2009168/2009.168.05/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T19:09:37Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T19:25: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 96.09739 to the max depth of parosci.log. - Set the content length of parosci.log to 369878. - UpdateBot DataProducer persisted and has ID 34177. - Deployment parosci was changed and persisted to the database with ID 33880. - Deployment 2009.168.05 was changed and persisted to the database with ID 33867. Processing for deployment 2009.168.05 ended at 2009-06-26T17:43:13Z