SSDS Processing Report for data sets from Deployment 2019.196.04 Processing began at 2019-07-16T20:36:39Z Going to try to convert any outputs of deployment 2019.196.04 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/2019196/2019.196.04/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/2019196/2019.196.04/biolume.nc - Starting the NetCDF creation at 2019-07-16T20:36:39Z - NetCDF creation finished at 2019-07-16T20:36:45Z - 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/2019196/2019.196.04/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-07-16T20:36:39Z(start date = 2019-07-16T20:36:39Z, end date = 2019-07-16T20:36:45Z). - 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/2019196/2019.196.04/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/2019196/2019.196.04/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:24Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:26Z to the end date of biolume.log. - Set the content length of biolume.log to 23574410. - UpdateBot DataProducer persisted and has ID 50280. - Deployment biolume was changed and persisted to the database with ID 50279. 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/2019196/2019.196.04/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/2019196/2019.196.04/ctdDriver.nc - Starting the NetCDF creation at 2019-07-16T20:36:47Z - NetCDF creation finished at 2019-07-16T20:36: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/2019196/2019.196.04/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-07-16T20:36:47Z(start date = 2019-07-16T20:36:47Z, end date = 2019-07-16T20:36:51Z). - 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/2019196/2019.196.04/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/2019196/2019.196.04/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:52Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 32402982. - UpdateBot DataProducer persisted and has ID 50281. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:33Z_2081532365 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:34Z_1386430482 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:34Z_1607479739 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:34Z_1896409023 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:34Z_1946609158 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50270. 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/2019196/2019.196.04/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/2019196/2019.196.04/ctdDriver2.nc - Starting the NetCDF creation at 2019-07-16T20:36:52Z - NetCDF creation finished at 2019-07-16T20:36: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/2019196/2019.196.04/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-07-16T20:36:52Z(start date = 2019-07-16T20:36:52Z, end date = 2019-07-16T20:36:56Z). - 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/2019196/2019.196.04/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/2019196/2019.196.04/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:52Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 32403071. - UpdateBot DataProducer persisted and has ID 50282. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:33Z_1045055951 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:33Z_1675440721 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:33Z_2142705928 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50265. 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/dvl.nc - Starting the NetCDF creation at 2019-07-16T20:36:57Z - NetCDF creation finished at 2019-07-16T20:36:58Z - 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/2019196/2019.196.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 2019-07-16T20:36:57Z(start date = 2019-07-16T20:36:57Z, end date = 2019-07-16T20:36:58Z). - 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:30Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:25Z to the end date of dvl.log. - Set the content length of dvl.log to 8416533. - UpdateBot DataProducer persisted and has ID 50283. - Deployment dvl was changed and persisted to the database with ID 50258. 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/dynamicControl.nc - Starting the NetCDF creation at 2019-07-16T20:36:59Z - NetCDF creation finished at 2019-07-16T20:37:16Z - 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/2019196/2019.196.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 2019-07-16T20:36:59Z(start date = 2019-07-16T20:36:59Z, end date = 2019-07-16T20:37:16Z). - 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:25:04Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 124052688. - UpdateBot DataProducer persisted and has ID 50284. - Deployment dynamicControl was changed and persisted to the database with ID 50278. 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/gps.nc - Starting the NetCDF creation at 2019-07-16T20:37:18Z - NetCDF creation finished at 2019-07-16T20:37:18Z - 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/2019196/2019.196.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 2019-07-16T20:37:18Z(start date = 2019-07-16T20:37:18Z, end date = 2019-07-16T20:37:18Z). - 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:24Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65866916666668 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.90278150000001 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81076166666668 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.0292751666667 to the max longitude of gps.log. - Set the content length of gps.log to 1186916. - UpdateBot DataProducer persisted and has ID 50285. - Deployment gps was changed and persisted to the database with ID 50269. 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/2019196/2019.196.04/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/2019196/2019.196.04/hydroscatlog.nc - Starting the NetCDF creation at 2019-07-16T20:37:19Z - NetCDF creation finished at 2019-07-16T20:37: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/2019196/2019.196.04/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-07-16T20:37:19Z(start date = 2019-07-16T20:37:19Z, end date = 2019-07-16T20:37:24Z). - 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/2019196/2019.196.04/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/2019196/2019.196.04/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:30Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 28350778. - UpdateBot DataProducer persisted and has ID 50286. - Deployment hydroscatlog was changed and persisted to the database with ID 50276. 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/2019196/2019.196.04/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/2019196/2019.196.04/isuslog.nc - Starting the NetCDF creation at 2019-07-16T20:37:25Z - NetCDF creation finished at 2019-07-16T20:37:25Z - 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/2019196/2019.196.04/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-07-16T20:37:25Z(start date = 2019-07-16T20:37:25Z, end date = 2019-07-16T20:37:25Z). - 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/2019196/2019.196.04/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/2019196/2019.196.04/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:25:25Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:26Z to the end date of isuslog.log. - Set the content length of isuslog.log to 2109877. - UpdateBot DataProducer persisted and has ID 50287. - Deployment isuslog was changed and persisted to the database with ID 50257. 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/2019196/2019.196.04/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/2019196/2019.196.04/lisstlog.nc - Starting the NetCDF creation at 2019-07-16T20:37:26Z - NetCDF creation finished at 2019-07-16T20:37: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/2019196/2019.196.04/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-07-16T20:37:26Z(start date = 2019-07-16T20:37:26Z, end date = 2019-07-16T20:37:28Z). - 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/2019196/2019.196.04/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/2019196/2019.196.04/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:29Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 8775103. - UpdateBot DataProducer persisted and has ID 50288. - Deployment lisstlog was changed and persisted to the database with ID 50277. 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/navigation.nc - Starting the NetCDF creation at 2019-07-16T20:37:29Z - NetCDF creation finished at 2019-07-16T20:37: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/2019196/2019.196.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 2019-07-16T20:37:29Z(start date = 2019-07-16T20:37:29Z, end date = 2019-07-16T20:37:46Z). - 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:25:04Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.65857504156954 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.903021241726556 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.03062227447107 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.8107611783388 to the max longitude of navigation.log. - Set the content length of navigation.log to 124897710. - UpdateBot DataProducer persisted and has ID 50289. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:33Z_1408926057 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:33Z_454184908 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-07-16T20:36:33Z_794001175 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50259. 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/parosci.nc - Starting the NetCDF creation at 2019-07-16T20:37:48Z - NetCDF creation finished at 2019-07-16T20:37:55Z - 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/2019196/2019.196.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 2019-07-16T20:37:48Z(start date = 2019-07-16T20:37:48Z, end date = 2019-07-16T20:37:55Z). - 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:29Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z 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.52785 to the max depth of parosci.log. - Set the content length of parosci.log to 40331222. - UpdateBot DataProducer persisted and has ID 50290. - Deployment parosci was changed and persisted to the database with ID 50263. 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/tailCone.nc - Starting the NetCDF creation at 2019-07-16T20:37:57Z - NetCDF creation finished at 2019-07-16T20:38:01Z - 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/2019196/2019.196.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 2019-07-16T20:37:57Z(start date = 2019-07-16T20:37:57Z, end date = 2019-07-16T20:38:01Z). - 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/2019196/2019.196.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/auvctd/missionlogs/2019/2019196/2019.196.04/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-07-15T19:24:29Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-07-16T18:51:27Z to the end date of tailCone.log. - Set the content length of tailCone.log to 20262091. - UpdateBot DataProducer persisted and has ID 50291. - Deployment tailCone was changed and persisted to the database with ID 50264. - Deployment 2019.196.04 was changed and persisted to the database with ID 50256. Processing for deployment 2019.196.04 ended at 2019-07-16T20:38:02Z