SSDS Processing Report for data sets from Deployment 2008.338.04 Processing began at 2009-06-26T15:37:51Z Going to try to convert any outputs of deployment 2008.338.04 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 parosci to NetCDF files: - Working on output parosci.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008338/2008.338.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/2008/2008338/2008.338.04/parosci.nc - Starting the NetCDF creation at 2009-06-26T15:37:52Z - NetCDF creation finished at 2009-06-26T15:37:52Z - 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.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-26T15:37:52Z(start date = 2009-06-26T15:37:52Z, end date = 2009-06-26T15:37:52Z). - 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.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/2008/2008338/2008.338.04/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:03:06Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:04:31Z 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.04239133 to the max depth of parosci.log. - Set the content length of parosci.log to 33686. - UpdateBot DataProducer persisted and has ID 32551. - Deployment parosci was changed and persisted to the database with ID 32426. 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.04/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.04/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T15:37:54Z - NetCDF creation finished at 2009-06-26T15:37: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.04/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:37:54Z(start date = 2009-06-26T15:37:54Z, end date = 2009-06-26T15:37:54Z). - 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.04/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.04/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:03:27Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:04:27Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 2127. - UpdateBot DataProducer persisted and has ID 32552. - 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:30Z_995105488 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:30Z_1164542708 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:30Z_1246415496 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32427. 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.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/2008/2008338/2008.338.04/dvl.nc - Starting the NetCDF creation at 2009-06-26T15:37:57Z - NetCDF creation finished at 2009-06-26T15:37:57Z - 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.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-26T15:37:57Z(start date = 2009-06-26T15:37:57Z, end date = 2009-06-26T15:37:57Z). - 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.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/2008/2008338/2008.338.04/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:02:58Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:04:31Z to the end date of dvl.log. - Set the content length of dvl.log to 23889. - UpdateBot DataProducer persisted and has ID 32553. - Deployment dvl was changed and persisted to the database with ID 32431. 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.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/2008/2008338/2008.338.04/gps.nc - Starting the NetCDF creation at 2009-06-26T15:37:59Z - NetCDF creation finished at 2009-06-26T15: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/2008/2008338/2008.338.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-26T15:37:59Z(start date = 2009-06-26T15:37:59Z, end date = 2009-06-26T15:38:00Z). - 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.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/2008/2008338/2008.338.04/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:03:00Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:04:31Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.80232933333333 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.80233900000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.78788266666668 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.78789183333336 to the max longitude of gps.log. - Set the content length of gps.log to 7412. - UpdateBot DataProducer persisted and has ID 32554. - Deployment gps was changed and persisted to the database with ID 32432. 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.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/2008/2008338/2008.338.04/tailCone.nc - Starting the NetCDF creation at 2009-06-26T15:38:02Z - NetCDF creation finished at 2009-06-26T15:38: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/2008/2008338/2008.338.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-26T15:38:02Z(start date = 2009-06-26T15:38:02Z, end date = 2009-06-26T15:38:02Z). - 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.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/2008/2008338/2008.338.04/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:03:03Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:04:30Z to the end date of tailCone.log. - Set the content length of tailCone.log to 5803. - UpdateBot DataProducer persisted and has ID 32555. - Deployment tailCone was changed and persisted to the database with ID 32433. 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.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/2008/2008338/2008.338.04/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T15:38:05Z - NetCDF creation finished at 2009-06-26T15: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/2008/2008338/2008.338.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-26T15:38:05Z(start date = 2009-06-26T15:38:05Z, end date = 2009-06-26T15: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/2008/2008338/2008.338.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/2008/2008338/2008.338.04/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:03:30Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:04:31Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 77186. - UpdateBot DataProducer persisted and has ID 32556. - Deployment dynamicControl was changed and persisted to the database with ID 32434. 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.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/2008/2008338/2008.338.04/navigation.nc - Starting the NetCDF creation at 2009-06-26T15:38:07Z - NetCDF creation finished at 2009-06-26T15: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/2008/2008338/2008.338.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-26T15:38:07Z(start date = 2009-06-26T15:38:07Z, end date = 2009-06-26T15:38:07Z). - 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.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/2008/2008338/2008.338.04/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-03T20:03:30Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-03T20:04:31Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.80232933333153 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.80233899999819 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.78789183332663 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.78788333332665 to the max longitude of navigation.log. - Set the content length of navigation.log to 73758. - UpdateBot DataProducer persisted and has ID 32557. - 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:31Z_1119146998 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:31Z_1519370247 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:31Z_1004297303 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32435. - Deployment 2008.338.04 was changed and persisted to the database with ID 32425. Processing for deployment 2008.338.04 ended at 2009-06-26T15:38:09Z