SSDS Processing Report for data sets from Deployment 2009.080.00 Processing began at 2009-04-01T00:59:36Z Going to try to convert any outputs of deployment 2009.080.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 navigation to NetCDF files: - Working on output navigation.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2009/2009080/2009.080.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/2009080/2009.080.00/navigation.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-01T00:59:36Z - NetCDF creation finished at 2009-04-01T00:59: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/2009080/2009.080.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-04-01T00:59:36Z(start date = 2009-04-01T00:59:36Z, end date = 2009-04-01T00:59:36Z). - 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/2009080/2009.080.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/2009080/2009.080.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-21T00:15:20Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2009-03-21T00:16:13Z 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.737873233691424 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.88042685648058 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 64554. - UpdateBot DataProducer persisted and has ID 30573. - Will loop through child deployments now (there are 9 of them) Going to try to convert any outputs of deployment Deployment_2009-03-31T20:26:03Z_1531188875 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T20:26:03Z_671956289 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T20:26:03Z_691745313 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T20:45:21Z_1667681751 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T20:45:21Z_582206425 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T20:45:21Z_672227967 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T22:58:17Z_1625940018 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T22:58:17Z_1519502739 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-03-31T22:58:17Z_2113209652 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 30556. 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/2009080/2009.080.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/2009080/2009.080.00/dvl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-01T00:59:39Z - NetCDF creation finished at 2009-04-01T00:59:39Z - 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/2009080/2009.080.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-04-01T00:59:39Z(start date = 2009-04-01T00:59:39Z, end date = 2009-04-01T00:59:39Z). - 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/2009080/2009.080.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/2009080/2009.080.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-21T00:14:59Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2009-03-21T00:16:13Z to the end date of dvl.log. - Set the content length of dvl.log to 19521. - UpdateBot DataProducer persisted and has ID 30574. - Deployment dvl was changed and persisted to the database with ID 30560. 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/2009080/2009.080.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/2009080/2009.080.00/dynamicControl.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-01T00:59:41Z - NetCDF creation finished at 2009-04-01T00:59:41Z - 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/2009080/2009.080.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-04-01T00:59:41Z(start date = 2009-04-01T00:59:41Z, end date = 2009-04-01T00:59:41Z). - 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/2009080/2009.080.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/2009080/2009.080.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-21T00:15:20Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2009-03-21T00:16:13Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 67436. - UpdateBot DataProducer persisted and has ID 30575. - Deployment dynamicControl was changed and persisted to the database with ID 30561. 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/2009080/2009.080.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/2009080/2009.080.00/tailCone.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-01T00:59:42Z - NetCDF creation finished at 2009-04-01T00:59:43Z - 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/2009080/2009.080.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-04-01T00:59:42Z(start date = 2009-04-01T00:59:42Z, end date = 2009-04-01T00:59:43Z). - 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/2009080/2009.080.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/2009080/2009.080.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-21T00:15:03Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2009-03-21T00:16:13Z to the end date of tailCone.log. - Set the content length of tailCone.log to 4747. - UpdateBot DataProducer persisted and has ID 30576. - Deployment tailCone was changed and persisted to the database with ID 30562. 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/2009080/2009.080.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/2009080/2009.080.00/parosci.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-01T00:59:45Z - NetCDF creation finished at 2009-04-01T00:59:45Z - 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/2009080/2009.080.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-04-01T00:59:45Z(start date = 2009-04-01T00:59:45Z, end date = 2009-04-01T00:59:45Z). - 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/2009080/2009.080.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/2009080/2009.080.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2009-03-21T00:15:06Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2009-03-21T00:16:13Z 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.07906355 to the max depth of parosci.log. - Set the content length of parosci.log to 26678. - UpdateBot DataProducer persisted and has ID 30577. - Deployment parosci was changed and persisted to the database with ID 30563. 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/2009080/2009.080.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/2009080/2009.080.00/gps.nc - The NetCDF file already exists, so will delete it. - Starting the NetCDF creation at 2009-04-01T00:59:47Z - NetCDF creation finished at 2009-04-01T00:59:47Z - 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/2009080/2009.080.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-04-01T00:59:47Z(start date = 2009-04-01T00:59:47Z, end date = 2009-04-01T00:59:47Z). - 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/2009080/2009.080.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/2009080/2009.080.00/gps.nc.log. - UpdateBot DataProducer persisted and has ID 30578. - Deployment gps was changed and persisted to the database with ID 30564. - Deployment 2009.080.00 was changed and persisted to the database with ID 30569. Processing for deployment 2009.080.00 ended at 2009-04-01T00:59:51Z