SSDS Processing Report for data sets from Deployment 2004.296.03

Processing began at 2006-10-20T19:57:28Z

  Going to try to convert any outputs of deployment 2004.296.03 to NetCDF files:
    - There were no direct outputs for that deployment.
    - Will loop through child deployments now (there are 12 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/auvctd/missionlogs/2004/2004296/2004.296.03/navigation.log)
         - This output could not be converted to NetCDF because 
        - Will loop through child deployments now (there are 3 of them)
          Going to try to convert any outputs of deployment Device (id=1220) deployed on navigation(id=1236) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1221) deployed on navigation(id=1236) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1226) deployed on navigation(id=1236) to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment navigation was changed and persisted to the database with ID 16198.
      Going to try to convert any outputs of deployment tailCone to NetCDF files:
       - Working on output tailCone.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/tailCone.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment gps to NetCDF files:
       - Working on output gps.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/gps.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment crossbow to NetCDF files:
       - Working on output crossbow.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/crossbow.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment parosci to NetCDF files:
       - Working on output parosci.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/parosci.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment isuslog to NetCDF files:
       - Working on output isuslog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/isuslog.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment hydroscatlog to NetCDF files:
       - Working on output hydroscatlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/hydroscatlog.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment lisstlog to NetCDF files:
       - Working on output lisstlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/lisstlog.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment ctdDriver to NetCDF files:
       - Working on output ctdDriver.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/ctdDriver.log)
         - This output could not be converted to NetCDF because 
        - Will loop through child deployments now (there are 5 of them)
          Going to try to convert any outputs of deployment Device (id=1257) deployed on ctdDriver(id=1225) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1259) deployed on ctdDriver(id=1225) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1265) deployed on ctdDriver(id=1225) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1232) deployed on ctdDriver(id=1225) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1254) deployed on ctdDriver(id=1225) to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment ctdDriver was changed and persisted to the database with ID 16210.
      Going to try to convert any outputs of deployment biolume to NetCDF files:
       - Working on output biolume.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/biolume.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment dvl to NetCDF files:
       - Working on output dvl.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/dvl.log)
         - This output could not be converted to NetCDF because 
      Going to try to convert any outputs of deployment bluefinBattlog to NetCDF files:
       - Working on output bluefinBattlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2004/2004296/2004.296.03/bluefinBattlog.log)
         - This output could not be converted to NetCDF because 
        - Will loop through child deployments now (there are 3 of them)
          Going to try to convert any outputs of deployment Device (id=1262) deployed on bluefinBattlog(id=1237) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1263) deployed on bluefinBattlog(id=1237) to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Device (id=1264) deployed on bluefinBattlog(id=1237) to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment bluefinBattlog was changed and persisted to the database with ID 16218.
   - Deployment 2004.296.03 was changed and persisted to the database with ID 16202.
Processing for deployment 2004.296.03 ended at 2006-10-20T19:57:32Z