SSDS Processing Report for data sets from Deployment 2008.338.03

Processing began at 2009-06-26T15:38:40Z

  Going to try to convert any outputs of deployment 2008.338.03 to NetCDF files:
    - There were no direct outputs for that deployment.
    - Will loop through child deployments now (there are 8 of them)
      Going to try to convert any outputs of deployment ctdDriver to NetCDF files:
       - Working on output ctdDriver.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008338/2008.338.03/ctdDriver.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/2008338/2008.338.03/ctdDriver.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:43Z
         - NetCDF creation finished at 2009-06-26T15:38: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/2008338/2008.338.03/ctdDriver.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-26T15:38:43Z(start date = 2009-06-26T15:38:43Z, end date = 2009-06-26T15:38:43Z).
         - Created DataProducerGroup with name SSDS NetCDF Creators
         - Created DataContainerGroup with name SSDS Generated NetCDFs
         - The NetCDF DataContainer will be ctdDriver.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008338/2008.338.03/ctdDriver.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/2008338/2008.338.03/ctdDriver.nc.log.
       - UpdateBot DataProducer persisted and has ID 32558.
        - Will loop through child deployments now (there are 5 of them)
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:32Z_2032084896 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:32Z_101557191 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:32Z_1374420936 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:32Z_2081266608 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:32Z_1988407710 to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment ctdDriver was changed and persisted to the database with ID 32440.
      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/2008338/2008.338.03/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/2008338/2008.338.03/dvl.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:45Z
         - NetCDF creation finished at 2009-06-26T15:38: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/2008338/2008.338.03/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-26T15:38:45Z(start date = 2009-06-26T15:38:45Z, end date = 2009-06-26T15:38: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/2008338/2008.338.03/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/2008338/2008.338.03/dvl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2008-12-03T19:57:29Z to the start date of dvl.log.
         - Since a end date was found in the NetCDF file, will assign 2008-12-03T19:58:50Z to the end date of dvl.log.
         - Set the content length of dvl.log to 21393.
       - UpdateBot DataProducer persisted and has ID 32559.
       - Deployment dvl was changed and persisted to the database with ID 32446.
      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/2008338/2008.338.03/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/2008338/2008.338.03/dynamicControl.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:47Z
         - NetCDF creation finished at 2009-06-26T15:38:48Z
         - 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/2008338/2008.338.03/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-26T15:38:47Z(start date = 2009-06-26T15:38:47Z, end date = 2009-06-26T15:38:48Z).
         - 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/2008338/2008.338.03/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/2008338/2008.338.03/dynamicControl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2008-12-03T19:58:00Z to the start date of dynamicControl.log.
         - Since a end date was found in the NetCDF file, will assign 2008-12-03T19:58:51Z to the end date of dynamicControl.log.
         - Set the content length of dynamicControl.log to 64936.
       - UpdateBot DataProducer persisted and has ID 32560.
       - Deployment dynamicControl was changed and persisted to the database with ID 32447.
      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/2008338/2008.338.03/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/2008338/2008.338.03/parosci.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:50Z
         - NetCDF creation finished at 2009-06-26T15:38:50Z
         - 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/2008338/2008.338.03/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-26T15:38:50Z(start date = 2009-06-26T15:38:50Z, end date = 2009-06-26T15:38:50Z).
         - 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/2008338/2008.338.03/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/2008338/2008.338.03/parosci.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2008-12-03T19:57:36Z to the start date of parosci.log.
         - Since a end date was found in the NetCDF file, will assign 2008-12-03T19:58:51Z 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 0.044436958 to the max depth of parosci.log.
         - Set the content length of parosci.log to 29846.
       - UpdateBot DataProducer persisted and has ID 32561.
       - Deployment parosci was changed and persisted to the database with ID 32448.
      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/2008338/2008.338.03/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/2008338/2008.338.03/tailCone.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:52Z
         - NetCDF creation finished at 2009-06-26T15:38:52Z
         - 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/2008338/2008.338.03/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-26T15:38:52Z(start date = 2009-06-26T15:38:52Z, end date = 2009-06-26T15:38:52Z).
         - 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/2008338/2008.338.03/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/2008338/2008.338.03/tailCone.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2008-12-03T19:57:34Z to the start date of tailCone.log.
         - Since a end date was found in the NetCDF file, will assign 2008-12-03T19:58:51Z to the end date of tailCone.log.
         - Set the content length of tailCone.log to 5179.
       - UpdateBot DataProducer persisted and has ID 32562.
       - Deployment tailCone was changed and persisted to the database with ID 32449.
      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/2008338/2008.338.03/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/2008338/2008.338.03/gps.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:54Z
         - NetCDF creation finished at 2009-06-26T15:38:54Z
         - 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/2008338/2008.338.03/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-26T15:38:54Z(start date = 2009-06-26T15:38:54Z, end date = 2009-06-26T15:38:54Z).
         - 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/2008338/2008.338.03/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/2008338/2008.338.03/gps.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2008-12-03T19:57:30Z to the start date of gps.log.
         - Since a end date was found in the NetCDF file, will assign 2008-12-03T19:58:51Z to the end date of gps.log.
         - Since a min latitude was found in the NetCDF file, will assign 36.80238433333334 to the min latitude of gps.log.
         - Since a max latitude was found in the NetCDF file, will assign 36.80239483333334 to the max latitude of gps.log.
         - Since a min longitude was found in the NetCDF file, will assign 121.78790050000003 to the min longitude of gps.log.
         - Since a max longitude was found in the NetCDF file, will assign 121.78791133333335 to the max longitude of gps.log.
         - Set the content length of gps.log to 6692.
       - UpdateBot DataProducer persisted and has ID 32563.
       - Deployment gps was changed and persisted to the database with ID 32450.
      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/2008338/2008.338.03/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/2008338/2008.338.03/navigation.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:56Z
         - NetCDF creation finished at 2009-06-26T15:38: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/2008/2008338/2008.338.03/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-26T15:38:56Z(start date = 2009-06-26T15:38:56Z, end date = 2009-06-26T15:38:56Z).
         - 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/2008338/2008.338.03/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/2008338/2008.338.03/navigation.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2008-12-03T19:58:00Z to the start date of navigation.log.
         - Since a end date was found in the NetCDF file, will assign 2008-12-03T19:58:51Z to the end date of navigation.log.
         - Since a min latitude was found in the NetCDF file, will assign 36.802384333331524 to the min latitude of navigation.log.
         - Since a max latitude was found in the NetCDF file, will assign 36.80238916666485 to the max latitude of navigation.log.
         - Since a min longitude was found in the NetCDF file, will assign -121.78791099999329 to the min longitude of navigation.log.
         - Since a max longitude was found in the NetCDF file, will assign -121.78790049999331 to the max longitude of navigation.log.
         - Set the content length of navigation.log to 62194.
       - UpdateBot DataProducer persisted and has ID 32564.
        - Will loop through child deployments now (there are 3 of them)
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:33Z_1772916704 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:33Z_405501202 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:33Z_847807362 to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment navigation was changed and persisted to the database with ID 32451.
      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/2008338/2008.338.03/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/2008338/2008.338.03/bluefinBattlog.nc
         - Starting the NetCDF creation at 2009-06-26T15:38:58Z
         - NetCDF creation finished at 2009-06-26T15:38: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/2008/2008338/2008.338.03/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-26T15:38:58Z(start date = 2009-06-26T15:38:58Z, end date = 2009-06-26T15:38: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/2008/2008338/2008.338.03/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/2008338/2008.338.03/bluefinBattlog.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2008-12-03T19:57:57Z to the start date of bluefinBattlog.log.
         - Since a end date was found in the NetCDF file, will assign 2008-12-03T19:58:47Z to the end date of bluefinBattlog.log.
         - Set the content length of bluefinBattlog.log to 1999.
       - UpdateBot DataProducer persisted and has ID 32565.
        - Will loop through child deployments now (there are 3 of them)
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:33Z_702229880 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:33Z_358752574 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:33Z_83473984 to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment bluefinBattlog was changed and persisted to the database with ID 32455.
   - Deployment 2008.338.03 was changed and persisted to the database with ID 32439.
Processing for deployment 2008.338.03 ended at 2009-06-26T15:39:00Z