SSDS Processing Report for data sets from Deployment 2009.167.02

Processing began at 2009-06-26T17:37:58Z

  Going to try to convert any outputs of deployment 2009.167.02 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 gps to NetCDF files:
       - Working on output gps.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009167/2009.167.02/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/2009167/2009.167.02/gps.nc
         - Starting the NetCDF creation at 2009-06-26T17:37:58Z
         - NetCDF creation finished at 2009-06-26T17:37: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/2009/2009167/2009.167.02/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:37:58Z(start date = 2009-06-26T17:37:58Z, end date = 2009-06-26T17:37:58Z).
         - 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/2009167/2009.167.02/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/2009167/2009.167.02/gps.nc.log.
       - UpdateBot DataProducer persisted and has ID 34116.
       - Deployment gps was changed and persisted to the database with ID 33737.
      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/2009167/2009.167.02/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/2009167/2009.167.02/dvl.nc
         - Starting the NetCDF creation at 2009-06-26T17:37:59Z
         - NetCDF creation finished at 2009-06-26T17:38:00Z
         - 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/2009167/2009.167.02/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:37:59Z(start date = 2009-06-26T17:37:59Z, end date = 2009-06-26T17:38:00Z).
         - 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/2009167/2009.167.02/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/2009167/2009.167.02/dvl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-06-16T22:45:08Z to the start date of dvl.log.
         - Since a end date was found in the NetCDF file, will assign 2009-06-16T22:47:20Z to the end date of dvl.log.
         - Set the content length of dvl.log to 33249.
       - UpdateBot DataProducer persisted and has ID 34117.
       - Deployment dvl was changed and persisted to the database with ID 33738.
      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/2009167/2009.167.02/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/2009167/2009.167.02/navigation.nc
         - Starting the NetCDF creation at 2009-06-26T17:38:01Z
         - NetCDF creation finished at 2009-06-26T17:38:01Z
         - 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/2009167/2009.167.02/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:38:01Z(start date = 2009-06-26T17:38:01Z, end date = 2009-06-26T17:38:01Z).
         - 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/2009167/2009.167.02/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/2009167/2009.167.02/navigation.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-06-16T22:45:29Z to the start date of navigation.log.
         - Since a end date was found in the NetCDF file, will assign 2009-06-16T22:47:20Z to the end date of navigation.log.
         - Since a min latitude was found in the NetCDF file, will assign 36.802444458006 to the min latitude of navigation.log.
         - Since a max latitude was found in the NetCDF file, will assign 36.80247633407722 to the max latitude of navigation.log.
         - Since a min longitude was found in the NetCDF file, will assign -121.78666172963457 to the min longitude of navigation.log.
         - Since a max longitude was found in the NetCDF file, will assign -121.78664944348361 to the max longitude of navigation.log.
         - Set the content length of navigation.log to 133230.
       - UpdateBot DataProducer persisted and has ID 34118.
        - Will loop through child deployments now (there are 3 of them)
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:06:36Z_938878111 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:06:36Z_692017798 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:06:36Z_1859564862 to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment navigation was changed and persisted to the database with ID 33739.
      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/2009167/2009.167.02/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/2009167/2009.167.02/tailCone.nc
         - Starting the NetCDF creation at 2009-06-26T17:38:03Z
         - NetCDF creation finished at 2009-06-26T17:38:03Z
         - 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/2009167/2009.167.02/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:38:03Z(start date = 2009-06-26T17:38:03Z, end date = 2009-06-26T17:38:03Z).
         - 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/2009167/2009.167.02/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/2009167/2009.167.02/tailCone.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-06-16T22:45:07Z to the start date of tailCone.log.
         - Since a end date was found in the NetCDF file, will assign 2009-06-16T22:47:20Z to the end date of tailCone.log.
         - Set the content length of tailCone.log to 32443.
       - UpdateBot DataProducer persisted and has ID 34119.
       - Deployment tailCone was changed and persisted to the database with ID 33743.
      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/2009167/2009.167.02/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/2009167/2009.167.02/dynamicControl.nc
         - Starting the NetCDF creation at 2009-06-26T17:38:05Z
         - NetCDF creation finished at 2009-06-26T17:38:05Z
         - 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/2009167/2009.167.02/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:38:05Z(start date = 2009-06-26T17:38:05Z, end date = 2009-06-26T17:38:05Z).
         - 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/2009167/2009.167.02/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/2009167/2009.167.02/dynamicControl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-06-16T22:45:29Z to the start date of dynamicControl.log.
         - Since a end date was found in the NetCDF file, will assign 2009-06-16T22:47:20Z to the end date of dynamicControl.log.
         - Set the content length of dynamicControl.log to 140186.
       - UpdateBot DataProducer persisted and has ID 34120.
       - Deployment dynamicControl was changed and persisted to the database with ID 33744.
      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/2009167/2009.167.02/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/2009167/2009.167.02/parosci.nc
         - Starting the NetCDF creation at 2009-06-26T17:38:07Z
         - NetCDF creation finished at 2009-06-26T17:38:07Z
         - 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/2009167/2009.167.02/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:38:07Z(start date = 2009-06-26T17:38:07Z, end date = 2009-06-26T17:38:07Z).
         - 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/2009167/2009.167.02/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/2009167/2009.167.02/parosci.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-06-16T22:45:14Z to the start date of parosci.log.
         - Since a end date was found in the NetCDF file, will assign 2009-06-16T22:47:20Z 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.06547263 to the max depth of parosci.log.
         - Set the content length of parosci.log to 49430.
       - UpdateBot DataProducer persisted and has ID 34121.
       - Deployment parosci was changed and persisted to the database with ID 33745.
   - Deployment 2009.167.02 was changed and persisted to the database with ID 33736.
Processing for deployment 2009.167.02 ended at 2009-06-26T17:38:08Z