SSDS Processing Report for data sets from Deployment 2008.358.04 Processing began at 2009-06-26T17:08:19Z Going to try to convert any outputs of deployment 2008.358.04 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 dvl to NetCDF files: - Working on output dvl.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008358/2008.358.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/2008/2008358/2008.358.04/dvl.nc - Starting the NetCDF creation at 2009-06-26T17:08:20Z - NetCDF creation finished at 2009-06-26T17:08: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/2008/2008358/2008.358.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:08:20Z(start date = 2009-06-26T17:08:20Z, end date = 2009-06-26T17:08:21Z). - 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-23T17:54:51Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-23T18:13:58Z to the end date of dvl.log. - Set the content length of dvl.log to 284409. - UpdateBot DataProducer persisted and has ID 33802. - Deployment dvl was changed and persisted to the database with ID 33136. 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/navigation.nc - Starting the NetCDF creation at 2009-06-26T17:08:23Z - NetCDF creation finished at 2009-06-26T17:08: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/2008/2008358/2008.358.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:08:23Z(start date = 2009-06-26T17:08:23Z, end date = 2009-06-26T17:08:23Z). - 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-23T17:55:12Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-23T18:13:59Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.63573592661189 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.64356798762833 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.87622275321067 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.87506788010764 to the max longitude of navigation.log. - Set the content length of navigation.log to 1331874. - UpdateBot DataProducer persisted and has ID 33803. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:54:22Z_928173766 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:54:22Z_1573573085 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:54:22Z_217172141 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 33137. 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/gps.nc - Starting the NetCDF creation at 2009-06-26T17:08:25Z - NetCDF creation finished at 2009-06-26T17:08:26Z - 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/2008/2008358/2008.358.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:08:25Z(start date = 2009-06-26T17:08:25Z, end date = 2009-06-26T17:08:26Z). - 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-23T17:54:52Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-23T18:13:59Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.63573633333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.64356783333335 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.87506816666668 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.87531666666668 to the max longitude of gps.log. - Set the content length of gps.log to 31316. - UpdateBot DataProducer persisted and has ID 33804. - Deployment gps was changed and persisted to the database with ID 33141. 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/parosci.nc - Starting the NetCDF creation at 2009-06-26T17:08:27Z - NetCDF creation finished at 2009-06-26T17:08:28Z - 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/2008/2008358/2008.358.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:08:27Z(start date = 2009-06-26T17:08:27Z, end date = 2009-06-26T17:08:28Z). - 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-23T17:54:57Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-23T18:13:59Z 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 10.790436 to the max depth of parosci.log. - Set the content length of parosci.log to 446774. - UpdateBot DataProducer persisted and has ID 33805. - Deployment parosci was changed and persisted to the database with ID 33142. 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T17:08:29Z - NetCDF creation finished at 2009-06-26T17:08: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/2008/2008358/2008.358.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:08:29Z(start date = 2009-06-26T17:08:29Z, end date = 2009-06-26T17:08:30Z). - 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-23T17:55:12Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-23T18:13:59Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 1409936. - UpdateBot DataProducer persisted and has ID 33806. - Deployment dynamicControl was changed and persisted to the database with ID 33143. 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/tailCone.nc - Starting the NetCDF creation at 2009-06-26T17:08:32Z - NetCDF creation finished at 2009-06-26T17:08: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/2008/2008358/2008.358.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:08:32Z(start date = 2009-06-26T17:08:32Z, end date = 2009-06-26T17:08:32Z). - 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/2008/2008358/2008.358.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/2008/2008358/2008.358.04/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-23T17:54:55Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-23T18:13:59Z to the end date of tailCone.log. - Set the content length of tailCone.log to 59755. - UpdateBot DataProducer persisted and has ID 33807. - Deployment tailCone was changed and persisted to the database with ID 33144. - Deployment 2008.358.04 was changed and persisted to the database with ID 33135. Processing for deployment 2008.358.04 ended at 2009-06-26T17:08:33Z