SSDS Processing Report for data sets from Deployment 2008.339.07 Processing began at 2009-06-26T16:50:02Z Going to try to convert any outputs of deployment 2008.339.07 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 gps to NetCDF files: - Working on output gps.log (http://ssds.shore.mbari.org/auvbi/missionlogs/2008/2008339/2008.339.07/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/2008339/2008.339.07/gps.nc - Starting the NetCDF creation at 2009-06-26T16:50:03Z - NetCDF creation finished at 2009-06-26T16:50: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/2008339/2008.339.07/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-26T16:50:03Z(start date = 2009-06-26T16:50:03Z, end date = 2009-06-26T16:50:03Z). - 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/2008339/2008.339.07/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/2008339/2008.339.07/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:45:58Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:46:51Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.83114900000001 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.83119750000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.88200850000001 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 121.88207050000003 to the max longitude of gps.log. - Set the content length of gps.log to 4676. - UpdateBot DataProducer persisted and has ID 32911. - Deployment gps was changed and persisted to the database with ID 32667. 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/2008339/2008.339.07/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/2008339/2008.339.07/navigation.nc - Starting the NetCDF creation at 2009-06-26T16:50:05Z - NetCDF creation finished at 2009-06-26T16:50: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/2008339/2008.339.07/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-26T16:50:05Z(start date = 2009-06-26T16:50:05Z, end date = 2009-06-26T16:50: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/2008/2008339/2008.339.07/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/2008339/2008.339.07/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:46:29Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:46:52Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.83116061189645 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.831197876715166 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -121.88207151556293 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.88202396881982 to the max longitude of navigation.log. - Set the content length of navigation.log to 29390. - UpdateBot DataProducer persisted and has ID 32912. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:59Z_171659362 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:59Z_839052152 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:59Z_1894087235 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 32668. 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/2008339/2008.339.07/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/2008339/2008.339.07/bluefinBattlog.nc - Starting the NetCDF creation at 2009-06-26T16:50:06Z - NetCDF creation finished at 2009-06-26T16:50: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/2008339/2008.339.07/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-26T16:50:06Z(start date = 2009-06-26T16:50:06Z, end date = 2009-06-26T16:50:06Z). - 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/2008339/2008.339.07/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/2008339/2008.339.07/bluefinBattlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:46:25Z to the start date of bluefinBattlog.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:46:25Z to the end date of bluefinBattlog.log. - Set the content length of bluefinBattlog.log to 1359. - UpdateBot DataProducer persisted and has ID 32913. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:59Z_427535747 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:59Z_680897347 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2009-06-26T16:45:59Z_724013882 to NetCDF files: - There were no direct outputs for that deployment. - Deployment bluefinBattlog was changed and persisted to the database with ID 32672. 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/2008339/2008.339.07/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/2008339/2008.339.07/dynamicControl.nc - Starting the NetCDF creation at 2009-06-26T16:50:08Z - NetCDF creation finished at 2009-06-26T16:50:08Z - 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/2008339/2008.339.07/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-26T16:50:08Z(start date = 2009-06-26T16:50:08Z, end date = 2009-06-26T16:50:08Z). - 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/2008339/2008.339.07/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/2008339/2008.339.07/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:46:29Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:46:52Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 30186. - UpdateBot DataProducer persisted and has ID 32914. - Deployment dynamicControl was changed and persisted to the database with ID 32676. 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/2008339/2008.339.07/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/2008339/2008.339.07/dvl.nc - Starting the NetCDF creation at 2009-06-26T16:50:10Z - NetCDF creation finished at 2009-06-26T16:50: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/2008/2008339/2008.339.07/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-26T16:50:10Z(start date = 2009-06-26T16:50:10Z, end date = 2009-06-26T16:50:10Z). - 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/2008339/2008.339.07/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/2008339/2008.339.07/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:45:58Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:46:51Z to the end date of dvl.log. - Set the content length of dvl.log to 13125. - UpdateBot DataProducer persisted and has ID 32915. - Deployment dvl was changed and persisted to the database with ID 32677. 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/2008339/2008.339.07/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/2008339/2008.339.07/parosci.nc - Starting the NetCDF creation at 2009-06-26T16:50:12Z - NetCDF creation finished at 2009-06-26T16:50: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/2008/2008339/2008.339.07/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-26T16:50:12Z(start date = 2009-06-26T16:50:12Z, end date = 2009-06-26T16:50:12Z). - 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/2008339/2008.339.07/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/2008339/2008.339.07/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:46:04Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:46:52Z 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.14041476 to the max depth of parosci.log. - Set the content length of parosci.log to 18998. - UpdateBot DataProducer persisted and has ID 32916. - Deployment parosci was changed and persisted to the database with ID 32678. 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/2008339/2008.339.07/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/2008339/2008.339.07/tailCone.nc - Starting the NetCDF creation at 2009-06-26T16:50:13Z - NetCDF creation finished at 2009-06-26T16:50:13Z - 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/2008339/2008.339.07/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-26T16:50:13Z(start date = 2009-06-26T16:50:13Z, end date = 2009-06-26T16:50:13Z). - 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/2008339/2008.339.07/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/2008339/2008.339.07/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2008-12-04T18:46:01Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2008-12-04T18:46:52Z to the end date of tailCone.log. - Set the content length of tailCone.log to 3451. - UpdateBot DataProducer persisted and has ID 32917. - Deployment tailCone was changed and persisted to the database with ID 32679. - Deployment 2008.339.07 was changed and persisted to the database with ID 32666. Processing for deployment 2008.339.07 ended at 2009-06-26T16:50:14Z