SSDS Processing Report for data sets from Deployment 2009.099.06

Processing began at 2009-06-26T17:22:23Z

  Going to try to convert any outputs of deployment 2009.099.06 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 parosci to NetCDF files:
       - Working on output parosci.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009099/2009.099.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/2009/2009099/2009.099.06/parosci.nc
         - Starting the NetCDF creation at 2009-06-26T17:22:24Z
         - NetCDF creation finished at 2009-06-26T17:22: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/2009099/2009.099.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-26T17:22:24Z(start date = 2009-06-26T17:22:24Z, end date = 2009-06-26T17:22:24Z).
         - 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/2009099/2009.099.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/2009/2009099/2009.099.06/parosci.nc.log.
       - UpdateBot DataProducer persisted and has ID 33990.
       - Deployment parosci was changed and persisted to the database with ID 33431.
      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/2009099/2009.099.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/2009/2009099/2009.099.06/gps.nc
         - Starting the NetCDF creation at 2009-06-26T17:22:25Z
         - NetCDF creation finished at 2009-06-26T17:22:25Z
         - 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/2009099/2009.099.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-26T17:22:25Z(start date = 2009-06-26T17:22:25Z, end date = 2009-06-26T17:22:25Z).
         - 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/2009099/2009.099.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/2009/2009099/2009.099.06/gps.nc.log.
       - UpdateBot DataProducer persisted and has ID 33991.
       - Deployment gps was changed and persisted to the database with ID 33432.
      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/2009099/2009.099.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/2009/2009099/2009.099.06/tailCone.nc
         - Starting the NetCDF creation at 2009-06-26T17:22:26Z
         - NetCDF creation finished at 2009-06-26T17:22: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/2009/2009099/2009.099.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-26T17:22:26Z(start date = 2009-06-26T17:22:26Z, end date = 2009-06-26T17:22:26Z).
         - 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/2009099/2009.099.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/2009/2009099/2009.099.06/tailCone.nc.log.
       - UpdateBot DataProducer persisted and has ID 33992.
       - Deployment tailCone was changed and persisted to the database with ID 33433.
      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/2009099/2009.099.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/2009/2009099/2009.099.06/dvl.nc
         - Starting the NetCDF creation at 2009-06-26T17:22:28Z
         - NetCDF creation finished at 2009-06-26T17:22: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/2009/2009099/2009.099.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-26T17:22:28Z(start date = 2009-06-26T17:22:28Z, end date = 2009-06-26T17:22:28Z).
         - 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/2009099/2009.099.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/2009/2009099/2009.099.06/dvl.nc.log.
       - UpdateBot DataProducer persisted and has ID 33993.
       - Deployment dvl was changed and persisted to the database with ID 33434.
      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/2009099/2009.099.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/2009/2009099/2009.099.06/navigation.nc
         - Starting the NetCDF creation at 2009-06-26T17:22:29Z
         - NetCDF creation finished at 2009-06-26T17:22:29Z
         - 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/2009099/2009.099.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-26T17:22:29Z(start date = 2009-06-26T17:22:29Z, end date = 2009-06-26T17:22:29Z).
         - 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/2009099/2009.099.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/2009/2009099/2009.099.06/navigation.nc.log.
       - UpdateBot DataProducer persisted and has ID 33994.
        - Will loop through child deployments now (there are 3 of them)
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:01:16Z_1722055761 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:01:16Z_941140693 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:01:16Z_1417677760 to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment navigation was changed and persisted to the database with ID 33435.
      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/2009099/2009.099.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/2009/2009099/2009.099.06/dynamicControl.nc
         - Starting the NetCDF creation at 2009-06-26T17:22:30Z
         - NetCDF creation finished at 2009-06-26T17:22: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/2009099/2009.099.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-26T17:22:30Z(start date = 2009-06-26T17:22:30Z, end date = 2009-06-26T17:22: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/2009/2009099/2009.099.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/2009/2009099/2009.099.06/dynamicControl.nc.log.
       - UpdateBot DataProducer persisted and has ID 33995.
       - Deployment dynamicControl was changed and persisted to the database with ID 33439.
   - Deployment 2009.099.06 was changed and persisted to the database with ID 33430.
Processing for deployment 2009.099.06 ended at 2009-06-26T17:22:32Z