SSDS Processing Report for data sets from Deployment 2009.168.01 Processing began at 2009-06-26T17:40:19Z Going to try to convert any outputs of deployment 2009.168.01 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.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/2009168/2009.168.01/dvl.nc - Starting the NetCDF creation at 2009-06-26T17:40:19Z - NetCDF creation finished at 2009-06-26T17:40:19Z - 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.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-06-26T17:40:19Z(start date = 2009-06-26T17:40:19Z, end date = 2009-06-26T17:40:19Z). - 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.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/2009168/2009.168.01/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T15:59:21Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T16:29:10Z to the end date of dvl.log. - Set the content length of dvl.log to 380193. - UpdateBot DataProducer persisted and has ID 34143. - Deployment dvl was changed and persisted to the database with ID 33789. 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.01/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.01/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T17:40:21Z - NetCDF creation finished at 2009-06-26T17:40:21Z - 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.01/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:40:21Z(start date = 2009-06-26T17:40:21Z, end date = 2009-06-26T17:40:21Z). - 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.01/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.01/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T15:59:49Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T16:29:09Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 13135. - UpdateBot DataProducer persisted and has ID 34144. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:07:02Z_867792782 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:07:02Z_549495505 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:07:02Z_1588218873 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 33790. 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.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/2009168/2009.168.01/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T17:40:23Z - NetCDF creation finished at 2009-06-26T17:40:24Z - 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.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-06-26T17:40:23Z(start date = 2009-06-26T17:40:23Z, end date = 2009-06-26T17:40:24Z). - 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.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/2009168/2009.168.01/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T15:59:42Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T16:29:11Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 2211936. - UpdateBot DataProducer persisted and has ID 34145. - Deployment dynamicControl was changed and persisted to the database with ID 33794. 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.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/2009168/2009.168.01/navigation.nc - Starting the NetCDF creation at 2009-06-26T17:40:26Z - NetCDF creation finished at 2009-06-26T17:40: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/2009168/2009.168.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-06-26T17:40:26Z(start date = 2009-06-26T17:40:26Z, end date = 2009-06-26T17:40:27Z). - 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.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/2009168/2009.168.01/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T15:59:42Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T16:29:11Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.80787688795599 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.813830465941 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.97795073523247 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.96791094038761 to the max longitude of navigation.log. - Set the content length of navigation.log to 2088962. - UpdateBot DataProducer persisted and has ID 34146. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T17:07:02Z_1483671987 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:07:02Z_213670361 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T17:07:02Z_9386611 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 33795. 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.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/2009168/2009.168.01/tailCone.nc - Starting the NetCDF creation at 2009-06-26T17:40:29Z - NetCDF creation finished at 2009-06-26T17:40:30Z - 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.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-06-26T17:40:29Z(start date = 2009-06-26T17:40:29Z, end date = 2009-06-26T17:40:30Z). - 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.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/2009168/2009.168.01/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T15:59:21Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T16:29:11Z to the end date of tailCone.log. - Set the content length of tailCone.log to 429979. - UpdateBot DataProducer persisted and has ID 34147. - Deployment tailCone was changed and persisted to the database with ID 33799. 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.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/2009168/2009.168.01/parosci.nc - Starting the NetCDF creation at 2009-06-26T17:40:31Z - NetCDF creation finished at 2009-06-26T17:40: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/2009168/2009.168.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-06-26T17:40:31Z(start date = 2009-06-26T17:40:31Z, end date = 2009-06-26T17:40:32Z). - 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.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/2009168/2009.168.01/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T15:59:28Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T16:29:11Z 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 70.98906 to the max depth of parosci.log. - Set the content length of parosci.log to 692534. - UpdateBot DataProducer persisted and has ID 34148. - Deployment parosci was changed and persisted to the database with ID 33800. 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.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/2009168/2009.168.01/gps.nc - Starting the NetCDF creation at 2009-06-26T17:40:33Z - NetCDF creation finished at 2009-06-26T17:40:34Z - 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.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-06-26T17:40:33Z(start date = 2009-06-26T17:40:33Z, end date = 2009-06-26T17:40:34Z). - 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.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/2009168/2009.168.01/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-06-17T15:59:22Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2009-06-17T16:29:10Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.80787733333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.81233716666667 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.96813700000004 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.97786366666669 to the max longitude of gps.log. - Set the content length of gps.log to 30092. - UpdateBot DataProducer persisted and has ID 34149. - Deployment gps was changed and persisted to the database with ID 33801. - Deployment 2009.168.01 was changed and persisted to the database with ID 33788. Processing for deployment 2009.168.01 ended at 2009-06-26T17:40:35Z