SSDS Processing Report for data sets from Deployment 2019.176.00 Processing began at 2019-06-26T17:57:38Z Going to try to convert any outputs of deployment 2019.176.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/2019176/2019.176.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/2019176/2019.176.00/biolume.nc - Starting the NetCDF creation at 2019-06-26T17:57:39Z - NetCDF creation finished at 2019-06-26T17:57:44Z - 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/2019176/2019.176.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-06-26T17:57:39Z(start date = 2019-06-26T17:57:39Z, end date = 2019-06-26T17:57:44Z). - 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/2019176/2019.176.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/2019176/2019.176.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:23Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:00Z to the end date of biolume.log. - Set the content length of biolume.log to 21391018. - UpdateBot DataProducer persisted and has ID 50244. - Deployment biolume was changed and persisted to the database with ID 50235. 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/2019176/2019.176.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/2019176/2019.176.00/ctdDriver.nc - Starting the NetCDF creation at 2019-06-26T17:57:45Z - NetCDF creation finished at 2019-06-26T17:57: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/2019176/2019.176.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-06-26T17:57:45Z(start date = 2019-06-26T17:57:45Z, end date = 2019-06-26T17:57:49Z). - 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/2019176/2019.176.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/2019176/2019.176.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:58:06Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 29398278. - UpdateBot DataProducer persisted and has ID 50245. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_1006611265 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_1808592302 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_67661592 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_871220825 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_959538887 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50228. 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/2019176/2019.176.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/2019176/2019.176.00/ctdDriver2.nc - Starting the NetCDF creation at 2019-06-26T17:57:50Z - NetCDF creation finished at 2019-06-26T17:57: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/2019176/2019.176.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-06-26T17:57:50Z(start date = 2019-06-26T17:57:50Z, end date = 2019-06-26T17:57:54Z). - 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/2019176/2019.176.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/2019176/2019.176.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:49Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 29404799. - UpdateBot DataProducer persisted and has ID 50246. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_1379325999 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_1395499697 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_2131615600 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50238. 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/2019176/2019.176.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/2019176/2019.176.00/dvl.nc - Starting the NetCDF creation at 2019-06-26T17:57:54Z - NetCDF creation finished at 2019-06-26T17:57: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/2019176/2019.176.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-06-26T17:57:54Z(start date = 2019-06-26T17:57:54Z, end date = 2019-06-26T17:57:55Z). - 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/2019176/2019.176.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/2019176/2019.176.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:28Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:13:59Z to the end date of dvl.log. - Set the content length of dvl.log to 7753377. - UpdateBot DataProducer persisted and has ID 50247. - Deployment dvl was changed and persisted to the database with ID 50222. 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/2019176/2019.176.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/2019176/2019.176.00/dynamicControl.nc - Starting the NetCDF creation at 2019-06-26T17:57:57Z - NetCDF creation finished at 2019-06-26T17:58:13Z - 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/2019176/2019.176.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-06-26T17:57:57Z(start date = 2019-06-26T17:57:57Z, end date = 2019-06-26T17:58:13Z). - 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/2019176/2019.176.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/2019176/2019.176.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:58:02Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 112550526. - UpdateBot DataProducer persisted and has ID 50248. - Deployment dynamicControl was changed and persisted to the database with ID 50236. 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/2019176/2019.176.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/2019176/2019.176.00/gps.nc - Starting the NetCDF creation at 2019-06-26T17:58:15Z - NetCDF creation finished at 2019-06-26T17:58:15Z - 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/2019176/2019.176.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-06-26T17:58:15Z(start date = 2019-06-26T17:58:15Z, end date = 2019-06-26T17:58:15Z). - 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/2019176/2019.176.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/2019176/2019.176.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:22Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65850316666668 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.90332783333334 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.81355083333337 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.03232100000002 to the max longitude of gps.log. - Set the content length of gps.log to 1043924. - UpdateBot DataProducer persisted and has ID 50249. - Deployment gps was changed and persisted to the database with ID 50237. 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/2019176/2019.176.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/2019176/2019.176.00/hydroscatlog.nc - Starting the NetCDF creation at 2019-06-26T17:58:16Z - NetCDF creation finished at 2019-06-26T17:58:20Z - 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/2019176/2019.176.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-06-26T17:58:16Z(start date = 2019-06-26T17:58:16Z, end date = 2019-06-26T17:58:20Z). - 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/2019176/2019.176.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/2019176/2019.176.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:28Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 25723090. - UpdateBot DataProducer persisted and has ID 50250. - Deployment hydroscatlog was changed and persisted to the database with ID 50242. 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/2019176/2019.176.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/2019176/2019.176.00/isuslog.nc - Starting the NetCDF creation at 2019-06-26T17:58:21Z - NetCDF creation finished at 2019-06-26T17:58:22Z - 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/2019176/2019.176.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-06-26T17:58:21Z(start date = 2019-06-26T17:58:21Z, end date = 2019-06-26T17:58:22Z). - 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/2019176/2019.176.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/2019176/2019.176.00/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:58:45Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of isuslog.log. - Set the content length of isuslog.log to 1914261. - UpdateBot DataProducer persisted and has ID 50251. - Deployment isuslog was changed and persisted to the database with ID 50221. 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/2019176/2019.176.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/2019176/2019.176.00/lisstlog.nc - Starting the NetCDF creation at 2019-06-26T17:58:23Z - NetCDF creation finished at 2019-06-26T17:58: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/2019176/2019.176.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-06-26T17:58:23Z(start date = 2019-06-26T17:58:23Z, end date = 2019-06-26T17:58:24Z). - 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/2019176/2019.176.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/2019176/2019.176.00/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:28Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 9514807. - UpdateBot DataProducer persisted and has ID 50252. - Deployment lisstlog was changed and persisted to the database with ID 50234. 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/2019176/2019.176.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/2019176/2019.176.00/navigation.nc - Starting the NetCDF creation at 2019-06-26T17:58:25Z - NetCDF creation finished at 2019-06-26T17:58:44Z - 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/2019176/2019.176.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-06-26T17:58:25Z(start date = 2019-06-26T17:58:25Z, end date = 2019-06-26T17:58:44Z). - 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/2019176/2019.176.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/2019176/2019.176.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:58:02Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.658504472029215 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.903326622032786 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.03231866374517 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.81323154284874 to the max longitude of navigation.log. - Set the content length of navigation.log to 113317302. - UpdateBot DataProducer persisted and has ID 50253. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:33Z_948121965 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_288802095 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-06-26T17:57:34Z_780531830 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50223. 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/2019176/2019.176.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/2019176/2019.176.00/parosci.nc - Starting the NetCDF creation at 2019-06-26T17:58:46Z - NetCDF creation finished at 2019-06-26T17:58:53Z - 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/2019176/2019.176.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-06-26T17:58:46Z(start date = 2019-06-26T17:58:46Z, end date = 2019-06-26T17:58:53Z). - 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/2019176/2019.176.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/2019176/2019.176.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:27Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z 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.11674 to the max depth of parosci.log. - Set the content length of parosci.log to 36592550. - UpdateBot DataProducer persisted and has ID 50254. - Deployment parosci was changed and persisted to the database with ID 50243. 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/2019176/2019.176.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/2019176/2019.176.00/tailCone.nc - Starting the NetCDF creation at 2019-06-26T17:58:54Z - NetCDF creation finished at 2019-06-26T17:58: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/2019176/2019.176.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-06-26T17:58:54Z(start date = 2019-06-26T17:58:54Z, end date = 2019-06-26T17:58:58Z). - 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/2019176/2019.176.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/2019176/2019.176.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-06-25T18:57:27Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-06-26T16:14:01Z to the end date of tailCone.log. - Set the content length of tailCone.log to 18384139. - UpdateBot DataProducer persisted and has ID 50255. - Deployment tailCone was changed and persisted to the database with ID 50227. - Deployment 2019.176.00 was changed and persisted to the database with ID 50220. Processing for deployment 2019.176.00 ended at 2019-06-26T17:58:59Z