SSDS Processing Report for data sets from Deployment 2008.339.06 Processing began at 2009-06-26T16:50:32Z Going to try to convert any outputs of deployment 2008.339.06 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 navigation to NetCDF files: - Working on output navigation.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008339/2008.339.06/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/2008339/2008.339.06/navigation.nc - Starting the NetCDF creation at 2009-06-26T16:50:33Z - NetCDF creation finished at 2009-06-26T16:50:33Z - 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/2008339/2008.339.06/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-26T16:50:33Z(start date = 2009-06-26T16:50:33Z, end date = 2009-06-26T16:50:33Z). - 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/2008339/2008.339.06/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/2008339/2008.339.06/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:17:33Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:24:28Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.83006290976252 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.83099188333948 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.8802693549772 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.87373071111443 to the max longitude of navigation.log. - Set the content length of navigation.log to 491242. - UpdateBot DataProducer persisted and has ID 32928. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:00Z_1400153792 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:00Z_344027243 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:00Z_856560210 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32681. 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/2008339/2008.339.06/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/2008339/2008.339.06/parosci.nc - Starting the NetCDF creation at 2009-06-26T16:50:35Z - NetCDF creation finished at 2009-06-26T16:50:35Z - 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/2008339/2008.339.06/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-26T16:50:35Z(start date = 2009-06-26T16:50:35Z, end date = 2009-06-26T16:50:35Z). - 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/2008339/2008.339.06/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/2008339/2008.339.06/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:17:09Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:24:28Z 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 6.12066 to the max depth of parosci.log. - Set the content length of parosci.log to 172070. - UpdateBot DataProducer persisted and has ID 32929. - Deployment parosci was changed and persisted to the database with ID 32685. 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/2008339/2008.339.06/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/2008339/2008.339.06/gps.nc - Starting the NetCDF creation at 2009-06-26T16:50:37Z - NetCDF creation finished at 2009-06-26T16:50:37Z - 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/2008339/2008.339.06/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-26T16:50:37Z(start date = 2009-06-26T16:50:37Z, end date = 2009-06-26T16:50:37Z). - 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/2008339/2008.339.06/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/2008339/2008.339.06/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:17:03Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:24:27Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.83006300000002 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.83076566666667 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.87370483333336 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.88026816666671 to the max longitude of gps.log. - Set the content length of gps.log to 8132. - UpdateBot DataProducer persisted and has ID 32930. - Deployment gps was changed and persisted to the database with ID 32686. 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/2008339/2008.339.06/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/2008339/2008.339.06/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T16:50:38Z - NetCDF creation finished at 2009-06-26T16:50:39Z - 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/2008339/2008.339.06/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-26T16:50:38Z(start date = 2009-06-26T16:50:38Z, end date = 2009-06-26T16:50:39Z). - 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/2008339/2008.339.06/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/2008339/2008.339.06/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:17:33Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:24:28Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 519436. - UpdateBot DataProducer persisted and has ID 32931. - Deployment dynamicControl was changed and persisted to the database with ID 32687. 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/2008/2008339/2008.339.06/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/2008/2008339/2008.339.06/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T16:50:41Z - NetCDF creation finished at 2009-06-26T16:50:41Z - 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/2008339/2008.339.06/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-26T16:50:41Z(start date = 2009-06-26T16:50:41Z, end date = 2009-06-26T16:50:41Z). - 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/2008/2008339/2008.339.06/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/2008/2008339/2008.339.06/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:17:29Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:24:19Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 3151. - UpdateBot DataProducer persisted and has ID 32932. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:00Z_306944728 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:00Z_1226171229 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:46:00Z_1942549477 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32688. 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/2008339/2008.339.06/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/2008339/2008.339.06/tailCone.nc - Starting the NetCDF creation at 2009-06-26T16:50:43Z - NetCDF creation finished at 2009-06-26T16:50:43Z - 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/2008339/2008.339.06/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-26T16:50:43Z(start date = 2009-06-26T16:50:43Z, end date = 2009-06-26T16:50:43Z). - 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/2008339/2008.339.06/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/2008339/2008.339.06/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:17:07Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:24:27Z to the end date of tailCone.log. - Set the content length of tailCone.log to 22315. - UpdateBot DataProducer persisted and has ID 32933. - Deployment tailCone was changed and persisted to the database with ID 32692. 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/2008339/2008.339.06/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/2008339/2008.339.06/dvl.nc - Starting the NetCDF creation at 2009-06-26T16:50:44Z - NetCDF creation finished at 2009-06-26T16:50:45Z - 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/2008339/2008.339.06/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-26T16:50:44Z(start date = 2009-06-26T16:50:44Z, end date = 2009-06-26T16:50:45Z). - 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/2008339/2008.339.06/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/2008339/2008.339.06/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:17:03Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:24:27Z to the end date of dvl.log. - Set the content length of dvl.log to 99705. - UpdateBot DataProducer persisted and has ID 32934. - Deployment dvl was changed and persisted to the database with ID 32693. - Deployment 2008.339.06 was changed and persisted to the database with ID 32680. Processing for deployment 2008.339.06 ended at 2009-06-26T16:50:46Z