SSDS Processing Report for data sets from Deployment 2009.084.00

Processing began at 2009-06-27T05:57:17Z

  Going to try to convert any outputs of deployment 2009.084.00 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 dynamicControl to NetCDF files:
       - Working on output dynamicControl.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009084/2009.084.00/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/2009084/2009.084.00/dynamicControl.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-27T05:57:18Z
         - NetCDF creation finished at 2009-06-27T05:57:18Z
         - 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/2009084/2009.084.00/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-27T05:57:18Z(start date = 2009-06-27T05:57:18Z, end date = 2009-06-27T05:57:18Z).
         - 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/2009084/2009.084.00/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/2009084/2009.084.00/dynamicControl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-03-25T22:54:59Z to the start date of dynamicControl.log.
         - Since a end date was found in the NetCDF file, will assign 2009-03-25T22:55:42Z to the end date of dynamicControl.log.
         - Set the content length of dynamicControl.log to 55936.
       - UpdateBot DataProducer persisted and has ID 34301.
       - Deployment dynamicControl was changed and persisted to the database with ID 34262.
      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/2009084/2009.084.00/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/2009084/2009.084.00/tailCone.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-27T05:57:22Z
         - NetCDF creation finished at 2009-06-27T05:57:22Z
         - 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/2009084/2009.084.00/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-27T05:57:22Z(start date = 2009-06-27T05:57:22Z, end date = 2009-06-27T05:57:22Z).
         - 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/2009084/2009.084.00/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/2009084/2009.084.00/tailCone.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-03-25T22:54:43Z to the start date of tailCone.log.
         - Since a end date was found in the NetCDF file, will assign 2009-03-25T22:55:42Z to the end date of tailCone.log.
         - Set the content length of tailCone.log to 4123.
       - UpdateBot DataProducer persisted and has ID 34302.
       - Deployment tailCone was changed and persisted to the database with ID 34263.
      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/2009084/2009.084.00/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/2009084/2009.084.00/gps.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-27T05:57:26Z
         - NetCDF creation finished at 2009-06-27T05:57: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/2009084/2009.084.00/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-27T05:57:26Z(start date = 2009-06-27T05:57:26Z, end date = 2009-06-27T05:57:26Z).
         - 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/2009084/2009.084.00/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/2009084/2009.084.00/gps.nc.log.
       - UpdateBot DataProducer persisted and has ID 34303.
       - Deployment gps was changed and persisted to the database with ID 34264.
      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/2009084/2009.084.00/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/2009084/2009.084.00/dvl.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-27T05:57:29Z
         - NetCDF creation finished at 2009-06-27T05:57: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/2009084/2009.084.00/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-27T05:57:29Z(start date = 2009-06-27T05:57:29Z, end date = 2009-06-27T05:57:29Z).
         - 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/2009084/2009.084.00/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/2009084/2009.084.00/dvl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-03-25T22:54:38Z to the start date of dvl.log.
         - Since a end date was found in the NetCDF file, will assign 2009-03-25T22:55:42Z to the end date of dvl.log.
         - Set the content length of dvl.log to 17025.
       - UpdateBot DataProducer persisted and has ID 34304.
       - Deployment dvl was changed and persisted to the database with ID 34265.
      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/2009084/2009.084.00/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/2009084/2009.084.00/navigation.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-27T05:57:32Z
         - NetCDF creation finished at 2009-06-27T05:57:32Z
         - 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/2009084/2009.084.00/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-27T05:57:32Z(start date = 2009-06-27T05:57:32Z, end date = 2009-06-27T05:57:32Z).
         - 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/2009084/2009.084.00/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/2009084/2009.084.00/navigation.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-03-25T22:54:59Z to the start date of navigation.log.
         - Since a end date was found in the NetCDF file, will assign 2009-03-25T22:55:42Z to the end date of navigation.log.
         - Since a min latitude was found in the NetCDF file, will assign 36.737844999998366 to the min latitude of navigation.log.
         - Since a max latitude was found in the NetCDF file, will assign 36.73784864196994 to the max latitude of navigation.log.
         - Since a min longitude was found in the NetCDF file, will assign -121.88042529681753 to the min longitude of navigation.log.
         - Since a max longitude was found in the NetCDF file, will assign -121.88042269999615 to the max longitude of navigation.log.
         - Set the content length of navigation.log to 53698.
       - UpdateBot DataProducer persisted and has ID 34305.
        - Will loop through child deployments now (there are 3 of them)
          Going to try to convert any outputs of deployment Deployment_2009-06-26T22:14:28Z_2028378726 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T22:14:28Z_551720403 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T22:14:28Z_1558293057 to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment navigation was changed and persisted to the database with ID 34266.
      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/2009084/2009.084.00/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/2009084/2009.084.00/parosci.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-27T05:57:36Z
         - NetCDF creation finished at 2009-06-27T05:57:36Z
         - 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/2009084/2009.084.00/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-27T05:57:36Z(start date = 2009-06-27T05:57:36Z, end date = 2009-06-27T05:57:36Z).
         - 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/2009084/2009.084.00/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/2009084/2009.084.00/parosci.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-03-25T22:54:44Z to the start date of parosci.log.
         - Since a end date was found in the NetCDF file, will assign 2009-03-25T22:55:42Z 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.07892982 to the max depth of parosci.log.
         - Set the content length of parosci.log to 22982.
       - UpdateBot DataProducer persisted and has ID 34306.
       - Deployment parosci was changed and persisted to the database with ID 34270.
   - Deployment 2009.084.00 was changed and persisted to the database with ID 34261.
Processing for deployment 2009.084.00 ended at 2009-06-27T05:57:38Z