SSDS Processing Report for data sets from Deployment 2008.338.06 Processing began at 2009-06-26T15:40:49Z Going to try to convert any outputs of deployment 2008.338.06 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 7 of them) 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/dvl.nc - Starting the NetCDF creation at 2009-06-26T15:40:50Z - NetCDF creation finished at 2009-06-26T15:40:50Z - 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/2008/2008338/2008.338.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-26T15:40:50Z(start date = 2009-06-26T15:40:50Z, end date = 2009-06-26T15:40:50Z). - 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:26:32Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:28:05Z to the end date of dvl.log. - Set the content length of dvl.log to 23889. - UpdateBot DataProducer persisted and has ID 32573. - Deployment dvl was changed and persisted to the database with ID 32474. 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/navigation.nc - Starting the NetCDF creation at 2009-06-26T15:40:53Z - NetCDF creation finished at 2009-06-26T15:40:54Z - 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/2008/2008338/2008.338.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-26T15:40:53Z(start date = 2009-06-26T15:40:53Z, end date = 2009-06-26T15:40:54Z). - 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:27:04Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:28:05Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.802283666664856 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.80240366666485 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.78791666665997 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.78782666665997 to the max longitude of navigation.log. - Set the content length of navigation.log to 73994. - UpdateBot DataProducer persisted and has ID 32574. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:36Z_335267316 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:36Z_1159058170 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:36Z_2014860607 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32475. 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/parosci.nc - Starting the NetCDF creation at 2009-06-26T15:40:56Z - NetCDF creation finished at 2009-06-26T15:40:56Z - 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/2008/2008338/2008.338.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-26T15:40:56Z(start date = 2009-06-26T15:40:56Z, end date = 2009-06-26T15:40:56Z). - 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:26:39Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:28:05Z 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.05570687 to the max depth of parosci.log. - Set the content length of parosci.log to 33638. - UpdateBot DataProducer persisted and has ID 32575. - Deployment parosci was changed and persisted to the database with ID 32479. 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/tailCone.nc - Starting the NetCDF creation at 2009-06-26T15:40:58Z - NetCDF creation finished at 2009-06-26T15:40: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/2008/2008338/2008.338.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-26T15:40:58Z(start date = 2009-06-26T15:40:58Z, end date = 2009-06-26T15:40:58Z). - 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:26:37Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:28:04Z to the end date of tailCone.log. - Set the content length of tailCone.log to 5803. - UpdateBot DataProducer persisted and has ID 32576. - Deployment tailCone was changed and persisted to the database with ID 32480. Going to try to convert any outputs of deployment bluefinBattlog to NetCDF files: - Working on output bluefinBattlog.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008338/2008.338.06/bluefinBattlog.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/2008/2008338/2008.338.06/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T15:41:01Z - NetCDF creation finished at 2009-06-26T15:41: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/2008/2008338/2008.338.06/bluefinBattlog.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-26T15:41:01Z(start date = 2009-06-26T15:41:01Z, end date = 2009-06-26T15:41:01Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be bluefinBattlog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvbi/missionlogs/2008/2008338/2008.338.06/bluefinBattlog.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/2008/2008338/2008.338.06/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:27:00Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:28:00Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 2127. - UpdateBot DataProducer persisted and has ID 32577. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:36Z_818189916 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:36Z_401318158 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T15:27:36Z_678684167 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32481. 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T15:41:03Z - NetCDF creation finished at 2009-06-26T15:41: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/2008/2008338/2008.338.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-26T15:41:03Z(start date = 2009-06-26T15:41:03Z, end date = 2009-06-26T15:41:03Z). - 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:27:04Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:28:05Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 77436. - UpdateBot DataProducer persisted and has ID 32578. - Deployment dynamicControl was changed and persisted to the database with ID 32485. 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/gps.nc - Starting the NetCDF creation at 2009-06-26T15:41:06Z - NetCDF creation finished at 2009-06-26T15:41:06Z - 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/2008/2008338/2008.338.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-26T15:41:06Z(start date = 2009-06-26T15:41:06Z, end date = 2009-06-26T15:41:06Z). - 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/2008/2008338/2008.338.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/2008/2008338/2008.338.06/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:26:34Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:28:04Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.802283666666675 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80240366666667 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.78782666666669 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.7879166666667 to the max longitude of gps.log. - Set the content length of gps.log to 7340. - UpdateBot DataProducer persisted and has ID 32579. - Deployment gps was changed and persisted to the database with ID 32486. - Deployment 2008.338.06 was changed and persisted to the database with ID 32473. Processing for deployment 2008.338.06 ended at 2009-06-26T15:41:07Z