SSDS Processing Report for data sets from Deployment 2009.168.04 Processing began at 2009-06-26T17:42:07Z Going to try to convert any outputs of deployment 2009.168.04 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 gps to NetCDF files: - Working on output gps.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009168/2009.168.04/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.04/gps.nc - Starting the NetCDF creation at 2009-06-26T17:42:07Z - NetCDF creation finished at 2009-06-26T17:42: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.04/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:42:07Z(start date = 2009-06-26T17:42:07Z, end date = 2009-06-26T17:42:08Z). - 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.04/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.04/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T18:26:03Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T18:57:47Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.80860266666667 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.81162833333334 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.96782233333337 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.97481416666669 to the max longitude of gps.log. - Set the content length of gps.log to 35996. - UpdateBot DataProducer persisted and has ID 34164. - Deployment gps was changed and persisted to the database with ID 33849. 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.04/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.04/parosci.nc - Starting the NetCDF creation at 2009-06-26T17:42:09Z - NetCDF creation finished at 2009-06-26T17:42:11Z - 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.04/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:42:09Z(start date = 2009-06-26T17:42:09Z, end date = 2009-06-26T17:42:11Z). - 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.04/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.04/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T18:26:09Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T18:57:48Z 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.06512 to the max depth of parosci.log. - Set the content length of parosci.log to 737510. - UpdateBot DataProducer persisted and has ID 34165. - Deployment parosci was changed and persisted to the database with ID 33850. 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.04/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.04/tailCone.nc - Starting the NetCDF creation at 2009-06-26T17:42:12Z - NetCDF creation finished at 2009-06-26T17:42:13Z - 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.04/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:12Z(start date = 2009-06-26T17:42:12Z, end date = 2009-06-26T17:42:13Z). - 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.04/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.04/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T18:26:04Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T18:57:47Z to the end date of tailCone.log. - Set the content length of tailCone.log to 457483. - UpdateBot DataProducer persisted and has ID 34166. - Deployment tailCone was changed and persisted to the database with ID 33851. 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.04/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.04/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T17:42:15Z - NetCDF creation finished at 2009-06-26T17:42:15Z - 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.04/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:15Z(start date = 2009-06-26T17:42:15Z, end date = 2009-06-26T17:42:15Z). - 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.04/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.04/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T18:26:29Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T18:57:39Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 15823. - UpdateBot DataProducer persisted and has ID 34167. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:44Z_255843627 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:44Z_1604687596 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:44Z_214996892 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 33852. 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.04/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.04/dvl.nc - Starting the NetCDF creation at 2009-06-26T17:42:16Z - NetCDF creation finished at 2009-06-26T17:42:17Z - 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.04/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:16Z(start date = 2009-06-26T17:42:16Z, end date = 2009-06-26T17:42:17Z). - 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.04/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.04/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T18:26:04Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T18:57:47Z to the end date of dvl.log. - Set the content length of dvl.log to 420285. - UpdateBot DataProducer persisted and has ID 34168. - Deployment dvl was changed and persisted to the database with ID 33856. 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.04/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.04/navigation.nc - Starting the NetCDF creation at 2009-06-26T17:42:19Z - NetCDF creation finished at 2009-06-26T17:42:20Z - 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.04/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:42:19Z(start date = 2009-06-26T17:42:19Z, end date = 2009-06-26T17:42:20Z). - 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.04/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.04/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T18:26:25Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T18:57:48Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.80860275662862 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.8144824573212 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.97803624668455 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.96782195761226 to the max longitude of navigation.log. - Set the content length of navigation.log to 2223954. - UpdateBot DataProducer persisted and has ID 34169. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:45Z_1392066523 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:45Z_1187240767 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:08:45Z_1774275211 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 33857. 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.04/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.04/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T17:42:22Z - NetCDF creation finished at 2009-06-26T17:42:23Z - 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.04/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:42:22Z(start date = 2009-06-26T17:42:22Z, end date = 2009-06-26T17:42:23Z). - 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.04/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.04/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T18:26:25Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T18:57:48Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 2354936. - UpdateBot DataProducer persisted and has ID 34170. - Deployment dynamicControl was changed and persisted to the database with ID 33861. - Deployment 2009.168.04 was changed and persisted to the database with ID 33848. Processing for deployment 2009.168.04 ended at 2009-06-26T17:42:26Z