SSDS Processing Report for data sets from Deployment 2019.276.02 Processing began at 2019-10-05T16:59:30Z Going to try to convert any outputs of deployment 2019.276.02 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/2019276/2019.276.02/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/2019276/2019.276.02/biolume.nc - Starting the NetCDF creation at 2019-10-05T16:59:31Z - NetCDF creation finished at 2019-10-05T16:59:37Z - 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/2019276/2019.276.02/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-10-05T16:59:31Z(start date = 2019-10-05T16:59:31Z, end date = 2019-10-05T16:59:37Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:26:33Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of biolume.log. - Set the content length of biolume.log to 27538766. - UpdateBot DataProducer persisted and has ID 50417. - Deployment biolume was changed and persisted to the database with ID 50408. 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/2019276/2019.276.02/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/2019276/2019.276.02/ctdDriver.nc - Starting the NetCDF creation at 2019-10-05T16:59:39Z - NetCDF creation finished at 2019-10-05T16: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/auvctd/missionlogs/2019/2019276/2019.276.02/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-10-05T16:59:39Z(start date = 2019-10-05T16:59:39Z, end date = 2019-10-05T16:59:43Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:27:10Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 37850790. - UpdateBot DataProducer persisted and has ID 50418. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:25Z_1668442813 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:25Z_2057981954 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:25Z_215919912 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:25Z_802909990 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:25Z_949472969 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50411. 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/2019276/2019.276.02/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/2019276/2019.276.02/ctdDriver2.nc - Starting the NetCDF creation at 2019-10-05T16:59:44Z - NetCDF creation finished at 2019-10-05T16:59:49Z - 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/2019276/2019.276.02/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-10-05T16:59:44Z(start date = 2019-10-05T16:59:44Z, end date = 2019-10-05T16:59:49Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:27:10Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 37850879. - UpdateBot DataProducer persisted and has ID 50419. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:24Z_114278735 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:24Z_1378145135 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:24Z_510866013 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50399. 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/2019276/2019.276.02/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/2019276/2019.276.02/dvl.nc - Starting the NetCDF creation at 2019-10-05T16:59:50Z - NetCDF creation finished at 2019-10-05T16:59:51Z - 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/2019276/2019.276.02/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-10-05T16:59:50Z(start date = 2019-10-05T16:59:50Z, end date = 2019-10-05T16:59:51Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:26:39Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:54Z to the end date of dvl.log. - Set the content length of dvl.log to 10293057. - UpdateBot DataProducer persisted and has ID 50420. - Deployment dvl was changed and persisted to the database with ID 50410. 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/2019276/2019.276.02/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/2019276/2019.276.02/dynamicControl.nc - Starting the NetCDF creation at 2019-10-05T16:59:52Z - NetCDF creation finished at 2019-10-05T17:00: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/2019276/2019.276.02/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-10-05T16:59:52Z(start date = 2019-10-05T16:59:52Z, end date = 2019-10-05T17:00:14Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:27:13Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 144898170. - UpdateBot DataProducer persisted and has ID 50421. - Deployment dynamicControl was changed and persisted to the database with ID 50394. 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/2019276/2019.276.02/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/2019276/2019.276.02/gps.nc - Starting the NetCDF creation at 2019-10-05T17:00:19Z - NetCDF creation finished at 2019-10-05T17:00: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/2019276/2019.276.02/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-10-05T17:00:19Z(start date = 2019-10-05T17:00:19Z, end date = 2019-10-05T17:00:19Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:26:33Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.694718666666674 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.79723200000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.84622900000004 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.21952016666671 to the max longitude of gps.log. - Set the content length of gps.log to 649364. - UpdateBot DataProducer persisted and has ID 50422. - Deployment gps was changed and persisted to the database with ID 50404. 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/2019276/2019.276.02/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/2019276/2019.276.02/hydroscatlog.nc - Starting the NetCDF creation at 2019-10-05T17:00:22Z - NetCDF creation finished at 2019-10-05T17:00: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/2019276/2019.276.02/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-10-05T17:00:22Z(start date = 2019-10-05T17:00:22Z, end date = 2019-10-05T17:00:28Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:26:39Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 33113578. - UpdateBot DataProducer persisted and has ID 50423. - Deployment hydroscatlog was changed and persisted to the database with ID 50409. 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/2019276/2019.276.02/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/2019276/2019.276.02/isuslog.nc - Starting the NetCDF creation at 2019-10-05T17:00:30Z - NetCDF creation finished at 2019-10-05T17:00: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/2019276/2019.276.02/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-10-05T17:00:30Z(start date = 2019-10-05T17:00:30Z, end date = 2019-10-05T17:00:31Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:27:57Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:54Z to the end date of isuslog.log. - Set the content length of isuslog.log to 2501461. - UpdateBot DataProducer persisted and has ID 50424. - Deployment isuslog was changed and persisted to the database with ID 50406. 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/2019276/2019.276.02/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/2019276/2019.276.02/lisstlog.nc - Starting the NetCDF creation at 2019-10-05T17:00:32Z - NetCDF creation finished at 2019-10-05T17:00:33Z - 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/2019276/2019.276.02/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-10-05T17:00:32Z(start date = 2019-10-05T17:00:32Z, end date = 2019-10-05T17:00:33Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:26:41Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:51Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 3925951. - UpdateBot DataProducer persisted and has ID 50425. - Deployment lisstlog was changed and persisted to the database with ID 50403. 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/2019276/2019.276.02/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/2019276/2019.276.02/navigation.nc - Starting the NetCDF creation at 2019-10-05T17:00:35Z - NetCDF creation finished at 2019-10-05T17:00:57Z - 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/2019276/2019.276.02/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-10-05T17:00:35Z(start date = 2019-10-05T17:00:35Z, end date = 2019-10-05T17:00:57Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:27:13Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.6921312718722 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.79723200898877 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.21951961827648 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.84622756935885 to the max longitude of navigation.log. - Set the content length of navigation.log to 145884998. - UpdateBot DataProducer persisted and has ID 50426. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:24Z_2113360114 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:24Z_289228627 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-10-05T16:59:24Z_894488209 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50395. 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/2019276/2019.276.02/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/2019276/2019.276.02/parosci.nc - Starting the NetCDF creation at 2019-10-05T17:01:00Z - NetCDF creation finished at 2019-10-05T17:01:10Z - 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/2019276/2019.276.02/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-10-05T17:01:00Z(start date = 2019-10-05T17:01:00Z, end date = 2019-10-05T17:01:10Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:26:38Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z 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.11728 to the max depth of parosci.log. - Set the content length of parosci.log to 47105222. - UpdateBot DataProducer persisted and has ID 50427. - Deployment parosci was changed and persisted to the database with ID 50405. 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/2019276/2019.276.02/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/2019276/2019.276.02/tailCone.nc - Starting the NetCDF creation at 2019-10-05T17:01:18Z - NetCDF creation finished at 2019-10-05T17:01: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/2019276/2019.276.02/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-10-05T17:01:18Z(start date = 2019-10-05T17:01:18Z, end date = 2019-10-05T17:01:23Z). - 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/2019276/2019.276.02/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/2019276/2019.276.02/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-10-03T19:26:38Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-10-04T22:49:55Z to the end date of tailCone.log. - Set the content length of tailCone.log to 23665147. - UpdateBot DataProducer persisted and has ID 50428. - Deployment tailCone was changed and persisted to the database with ID 50407. - Deployment 2019.276.02 was changed and persisted to the database with ID 50393. Processing for deployment 2019.276.02 ended at 2019-10-05T17:01:26Z