SSDS Processing Report for data sets from Deployment 2019.219.00 Processing began at 2019-08-08T18:17:13Z Going to try to convert any outputs of deployment 2019.219.00 to NetCDF files: - There were no direct outputs for that deployment. - Will loop through child deployments now (there are 12 of them) Going to try to convert any outputs of deployment biolume to NetCDF files: - Working on output biolume.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/biolume.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/auvctd/missionlogs/2019/2019219/2019.219.00/biolume.nc - Starting the NetCDF creation at 2019-08-08T18:17:14Z - NetCDF creation finished at 2019-08-08T18:17:19Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/biolume.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-08-08T18:17:14Z(start date = 2019-08-08T18:17:14Z, end date = 2019-08-08T18:17:19Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be biolume.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/biolume.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/auvctd/missionlogs/2019/2019219/2019.219.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:21:19Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of biolume.log. - Set the content length of biolume.log to 21407490. - UpdateBot DataProducer persisted and has ID 50381. - Deployment biolume was changed and persisted to the database with ID 50380. Going to try to convert any outputs of deployment ctdDriver to NetCDF files: - Working on output ctdDriver.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver.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/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver.nc - Starting the NetCDF creation at 2019-08-08T18:17:20Z - NetCDF creation finished at 2019-08-08T18:17:24Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-08-08T18:17:20Z(start date = 2019-08-08T18:17:20Z, end date = 2019-08-08T18:17:24Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be ctdDriver.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver.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/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:22:03Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 29420934. - UpdateBot DataProducer persisted and has ID 50382. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:07Z_12047786 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:07Z_1350080853 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:07Z_1695326033 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:07Z_1834128390 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:07Z_399240734 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50359. Going to try to convert any outputs of deployment ctdDriver2 to NetCDF files: - Working on output ctdDriver2.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver2.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/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver2.nc - Starting the NetCDF creation at 2019-08-08T18:17:25Z - NetCDF creation finished at 2019-08-08T18:17:29Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver2.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-08-08T18:17:25Z(start date = 2019-08-08T18:17:25Z, end date = 2019-08-08T18:17:29Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be ctdDriver2.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver2.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/auvctd/missionlogs/2019/2019219/2019.219.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:21:46Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 29427263. - UpdateBot DataProducer persisted and has ID 50383. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:08Z_1114337720 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:08Z_620543732 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:08Z_813555426 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50373. Going to try to convert any outputs of deployment dvl to NetCDF files: - Working on output dvl.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/dvl.nc - Starting the NetCDF creation at 2019-08-08T18:17:30Z - NetCDF creation finished at 2019-08-08T18:17:31Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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 2019-08-08T18:17:30Z(start date = 2019-08-08T18:17:30Z, end date = 2019-08-08T18:17:31Z). - 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/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:21:25Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of dvl.log. - Set the content length of dvl.log to 7700025. - UpdateBot DataProducer persisted and has ID 50384. - Deployment dvl was changed and persisted to the database with ID 50379. Going to try to convert any outputs of deployment dynamicControl to NetCDF files: - Working on output dynamicControl.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/dynamicControl.nc - Starting the NetCDF creation at 2019-08-08T18:17:31Z - NetCDF creation finished at 2019-08-08T18:17:46Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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 2019-08-08T18:17:31Z(start date = 2019-08-08T18:17:31Z, end date = 2019-08-08T18:17:46Z). - 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/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:22:00Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 112633728. - UpdateBot DataProducer persisted and has ID 50385. - Deployment dynamicControl was changed and persisted to the database with ID 50370. Going to try to convert any outputs of deployment gps to NetCDF files: - Working on output gps.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/gps.nc - Starting the NetCDF creation at 2019-08-08T18:17:48Z - NetCDF creation finished at 2019-08-08T18:17:48Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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 2019-08-08T18:17:48Z(start date = 2019-08-08T18:17:48Z, end date = 2019-08-08T18:17:48Z). - 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/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:21:19Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65985966666668 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.90391766666667 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.84650083333337 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.0332591666667 to the max longitude of gps.log. - Set the content length of gps.log to 681332. - UpdateBot DataProducer persisted and has ID 50386. - Deployment gps was changed and persisted to the database with ID 50369. Going to try to convert any outputs of deployment hydroscatlog to NetCDF files: - Working on output hydroscatlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/hydroscatlog.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/auvctd/missionlogs/2019/2019219/2019.219.00/hydroscatlog.nc - Starting the NetCDF creation at 2019-08-08T18:17:49Z - NetCDF creation finished at 2019-08-08T18:17:54Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/hydroscatlog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-08-08T18:17:49Z(start date = 2019-08-08T18:17:49Z, end date = 2019-08-08T18:17:54Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be hydroscatlog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/hydroscatlog.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/auvctd/missionlogs/2019/2019219/2019.219.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:21:25Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 25742494. - UpdateBot DataProducer persisted and has ID 50387. - Deployment hydroscatlog was changed and persisted to the database with ID 50358. Going to try to convert any outputs of deployment isuslog to NetCDF files: - Working on output isuslog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/isuslog.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/auvctd/missionlogs/2019/2019219/2019.219.00/isuslog.nc - Starting the NetCDF creation at 2019-08-08T18:17:55Z - NetCDF creation finished at 2019-08-08T18:17:56Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/isuslog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-08-08T18:17:55Z(start date = 2019-08-08T18:17:55Z, end date = 2019-08-08T18:17:56Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be isuslog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/isuslog.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/auvctd/missionlogs/2019/2019219/2019.219.00/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:22:43Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:55Z to the end date of isuslog.log. - Set the content length of isuslog.log to 1915189. - UpdateBot DataProducer persisted and has ID 50388. - Deployment isuslog was changed and persisted to the database with ID 50378. Going to try to convert any outputs of deployment lisstlog to NetCDF files: - Working on output lisstlog.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/lisstlog.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/auvctd/missionlogs/2019/2019219/2019.219.00/lisstlog.nc - Starting the NetCDF creation at 2019-08-08T18:17:56Z - NetCDF creation finished at 2019-08-08T18:17:56Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/lisstlog.nc.log - Now will create the SSDS Metadata objects to track the processing and NetCDF file. - The UpdateBot DataProducer will be named NetCDFConverter on 2019-08-08T18:17:56Z(start date = 2019-08-08T18:17:56Z, end date = 2019-08-08T18:17:56Z). - Created DataProducerGroup with name SSDS NetCDF Creators - Created DataContainerGroup with name SSDS Generated NetCDFs - The NetCDF DataContainer will be lisstlog.nc at http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.00/lisstlog.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/auvctd/missionlogs/2019/2019219/2019.219.00/lisstlog.nc.log. - UpdateBot DataProducer persisted and has ID 50389. - Deployment lisstlog was changed and persisted to the database with ID 50371. Going to try to convert any outputs of deployment navigation to NetCDF files: - Working on output navigation.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/navigation.nc - Starting the NetCDF creation at 2019-08-08T18:17:57Z - NetCDF creation finished at 2019-08-08T18:18:14Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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 2019-08-08T18:17:57Z(start date = 2019-08-08T18:17:57Z, end date = 2019-08-08T18:18:14Z). - 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/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:22:00Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.658555110239675 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.9039173857141 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.03326219868586 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.84417995026993 to the max longitude of navigation.log. - Set the content length of navigation.log to 113401070. - UpdateBot DataProducer persisted and has ID 50390. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:08Z_102113372 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:08Z_178404208 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-08-08T18:17:08Z_745705238 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50365. Going to try to convert any outputs of deployment parosci to NetCDF files: - Working on output parosci.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/parosci.nc - Starting the NetCDF creation at 2019-08-08T18:18:16Z - NetCDF creation finished at 2019-08-08T18:18:23Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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 2019-08-08T18:18:16Z(start date = 2019-08-08T18:18:16Z, end date = 2019-08-08T18:18:23Z). - 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/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:21:24Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z 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 203.46936 to the max depth of parosci.log. - Set the content length of parosci.log to 36621158. - UpdateBot DataProducer persisted and has ID 50391. - Deployment parosci was changed and persisted to the database with ID 50372. Going to try to convert any outputs of deployment tailCone to NetCDF files: - Working on output tailCone.log (http://ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/tailCone.nc - Starting the NetCDF creation at 2019-08-08T18:18:24Z - NetCDF creation finished at 2019-08-08T18:18:28Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2019/2019219/2019.219.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 2019-08-08T18:18:24Z(start date = 2019-08-08T18:18:24Z, end date = 2019-08-08T18:18:28Z). - 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/auvctd/missionlogs/2019/2019219/2019.219.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/auvctd/missionlogs/2019/2019219/2019.219.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-08-07T19:21:24Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-08-08T16:38:56Z to the end date of tailCone.log. - Set the content length of tailCone.log to 18398251. - UpdateBot DataProducer persisted and has ID 50392. - Deployment tailCone was changed and persisted to the database with ID 50377. - Deployment 2019.219.00 was changed and persisted to the database with ID 50357. Processing for deployment 2019.219.00 ended at 2019-08-08T18:18:28Z