SSDS Processing Report for data sets from Deployment 2009.103.04

Processing began at 2009-06-26T17:27:02Z

  Going to try to convert any outputs of deployment 2009.103.04 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/2009103/2009.103.04/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/2009103/2009.103.04/gps.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-26T17:27:02Z
         - NetCDF creation finished at 2009-06-26T17:27:02Z
         - 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/2009103/2009.103.04/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:27:02Z(start date = 2009-06-26T17:27:02Z, end date = 2009-06-26T17:27:02Z).
         - 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/2009103/2009.103.04/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/2009103/2009.103.04/gps.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-04-13T17:55:54Z to the start date of gps.log.
         - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:20:39Z to the end date of gps.log.
         - Since a min latitude was found in the NetCDF file, will assign 36.81202133333334 to the min latitude of gps.log.
         - Since a max latitude was found in the NetCDF file, will assign 36.812673666666676 to the max latitude of gps.log.
         - Since a min longitude was found in the NetCDF file, will assign 121.97270316666668 to the min longitude of gps.log.
         - Since a max longitude was found in the NetCDF file, will assign 121.97607033333337 to the max longitude of gps.log.
         - Set the content length of gps.log to 12956.
       - UpdateBot DataProducer persisted and has ID 31231.
       - Deployment gps was changed and persisted to the database with ID 31222.
      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/2009103/2009.103.04/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/2009103/2009.103.04/navigation.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-26T17:27:04Z
         - NetCDF creation finished at 2009-06-26T17:27: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/2009103/2009.103.04/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:27:04Z(start date = 2009-06-26T17:27:04Z, end date = 2009-06-26T17:27:05Z).
         - 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/2009103/2009.103.04/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/2009103/2009.103.04/navigation.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-04-13T17:56:14Z to the start date of navigation.log.
         - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:20:40Z to the end date of navigation.log.
         - Since a min latitude was found in the NetCDF file, will assign 36.81031990099631 to the min latitude of navigation.log.
         - Since a max latitude was found in the NetCDF file, will assign 36.81334513654004 to the max latitude of navigation.log.
         - Since a min longitude was found in the NetCDF file, will assign -121.97607119882743 to the min longitude of navigation.log.
         - Since a max longitude was found in the NetCDF file, will assign -121.97003152587607 to the max longitude of navigation.log.
         - Set the content length of navigation.log to 1732130.
       - UpdateBot DataProducer persisted and has ID 31232.
        - Will loop through child deployments now (there are 6 of them)
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:03:20Z_1303433509 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:03:20Z_334182373 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-06-26T17:03:20Z_1533501634 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-04-14T20:13:45Z_2020035701 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-04-14T20:13:45Z_1786690004 to NetCDF files:
            - There were no direct outputs for that deployment.
          Going to try to convert any outputs of deployment Deployment_2009-04-14T20:13:45Z_1497086471 to NetCDF files:
            - There were no direct outputs for that deployment.
       - Deployment navigation was changed and persisted to the database with ID 31223.
      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/2009103/2009.103.04/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/2009103/2009.103.04/parosci.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-26T17:27:09Z
         - NetCDF creation finished at 2009-06-26T17:27:10Z
         - 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/2009103/2009.103.04/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:27:09Z(start date = 2009-06-26T17:27:09Z, end date = 2009-06-26T17:27:10Z).
         - 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/2009103/2009.103.04/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/2009103/2009.103.04/parosci.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-04-13T17:56:00Z to the start date of parosci.log.
         - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:20:40Z 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 90.14822 to the max depth of parosci.log.
         - Set the content length of parosci.log to 582662.
       - UpdateBot DataProducer persisted and has ID 31233.
       - Deployment parosci was changed and persisted to the database with ID 31227.
      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/2009103/2009.103.04/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/2009103/2009.103.04/dvl.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-26T17:27:11Z
         - NetCDF creation finished at 2009-06-26T17:27:12Z
         - 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/2009103/2009.103.04/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:27:11Z(start date = 2009-06-26T17:27:11Z, end date = 2009-06-26T17:27:12Z).
         - 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/2009103/2009.103.04/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/2009103/2009.103.04/dvl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-04-13T17:55:55Z to the start date of dvl.log.
         - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:20:39Z to the end date of dvl.log.
         - Set the content length of dvl.log to 366153.
       - UpdateBot DataProducer persisted and has ID 31234.
       - Deployment dvl was changed and persisted to the database with ID 31228.
      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/2009103/2009.103.04/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/2009103/2009.103.04/tailCone.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-26T17:27:13Z
         - NetCDF creation finished at 2009-06-26T17:27:14Z
         - 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/2009103/2009.103.04/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:27:13Z(start date = 2009-06-26T17:27:13Z, end date = 2009-06-26T17:27:14Z).
         - 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/2009103/2009.103.04/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/2009103/2009.103.04/tailCone.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-04-13T17:55:58Z to the start date of tailCone.log.
         - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:20:40Z to the end date of tailCone.log.
         - Set the content length of tailCone.log to 73387.
       - UpdateBot DataProducer persisted and has ID 31235.
       - Deployment tailCone was changed and persisted to the database with ID 31229.
      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/2009103/2009.103.04/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/2009103/2009.103.04/dynamicControl.nc
         - The NetCDF file already exists, so will delete it.
         - Starting the NetCDF creation at 2009-06-26T17:27:15Z
         - NetCDF creation finished at 2009-06-26T17:27:16Z
         - 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/2009103/2009.103.04/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:27:15Z(start date = 2009-06-26T17:27:15Z, end date = 2009-06-26T17:27:16Z).
         - 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/2009103/2009.103.04/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/2009103/2009.103.04/dynamicControl.nc.log.
         - Since a start date was found in the NetCDF file, will assign 2009-04-13T17:56:14Z to the start date of dynamicControl.log.
         - Since a end date was found in the NetCDF file, will assign 2009-04-13T18:20:40Z to the end date of dynamicControl.log.
         - Set the content length of dynamicControl.log to 1833936.
       - UpdateBot DataProducer persisted and has ID 31236.
       - Deployment dynamicControl was changed and persisted to the database with ID 31230.
   - Deployment 2009.103.04 was changed and persisted to the database with ID 33515.
Processing for deployment 2009.103.04 ended at 2009-06-26T17:27:18Z