SSDS Processing Report for data sets from Deployment 2019.351.00 Processing began at 2019-12-18T20:39:44Z Going to try to convert any outputs of deployment 2019.351.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/2019351/2019.351.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/2019351/2019.351.00/biolume.nc - Starting the NetCDF creation at 2019-12-18T20:39:45Z - NetCDF creation finished at 2019-12-18T20:39: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/2019351/2019.351.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-12-18T20:39:45Z(start date = 2019-12-18T20:39:45Z, end date = 2019-12-18T20:39:49Z). - 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/2019351/2019.351.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/2019351/2019.351.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:34:55Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of biolume.log. - Set the content length of biolume.log to 21636394. - UpdateBot DataProducer persisted and has ID 50561. - Deployment biolume was changed and persisted to the database with ID 50551. 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/2019351/2019.351.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/2019351/2019.351.00/ctdDriver.nc - Starting the NetCDF creation at 2019-12-18T20:39:52Z - NetCDF creation finished at 2019-12-18T20:39: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/2019351/2019.351.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-12-18T20:39:52Z(start date = 2019-12-18T20:39:52Z, end date = 2019-12-18T20:39:56Z). - 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/2019351/2019.351.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/2019351/2019.351.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:38Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 29736774. - UpdateBot DataProducer persisted and has ID 50562. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:37Z_1506465395 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:37Z_1978100354 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:37Z_705734632 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:37Z_781335888 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:37Z_816356126 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 50552. 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/2019351/2019.351.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/2019351/2019.351.00/ctdDriver2.nc - Starting the NetCDF creation at 2019-12-18T20:39:57Z - NetCDF creation finished at 2019-12-18T20:40: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/2019351/2019.351.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-12-18T20:39:57Z(start date = 2019-12-18T20:39:57Z, end date = 2019-12-18T20:40:01Z). - 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/2019351/2019.351.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/2019351/2019.351.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:21Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 29743007. - UpdateBot DataProducer persisted and has ID 50563. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:36Z_178025889 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:36Z_722855084 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:36Z_840270961 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 50545. 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/2019351/2019.351.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/2019351/2019.351.00/dvl.nc - Starting the NetCDF creation at 2019-12-18T20:40:03Z - NetCDF creation finished at 2019-12-18T20:40:04Z - 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/2019351/2019.351.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-12-18T20:40:03Z(start date = 2019-12-18T20:40:03Z, end date = 2019-12-18T20:40:04Z). - 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/2019351/2019.351.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/2019351/2019.351.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:00Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:13Z to the end date of dvl.log. - Set the content length of dvl.log to 7847289. - UpdateBot DataProducer persisted and has ID 50564. - Deployment dvl was changed and persisted to the database with ID 50550. 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/2019351/2019.351.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/2019351/2019.351.00/dynamicControl.nc - Starting the NetCDF creation at 2019-12-18T20:40:05Z - NetCDF creation finished at 2019-12-18T20:40: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/2019351/2019.351.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-12-18T20:40:05Z(start date = 2019-12-18T20:40:05Z, end date = 2019-12-18T20:40:24Z). - 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/2019351/2019.351.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/2019351/2019.351.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:34Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 113845890. - UpdateBot DataProducer persisted and has ID 50565. - Deployment dynamicControl was changed and persisted to the database with ID 50558. 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/2019351/2019.351.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/2019351/2019.351.00/gps.nc - Starting the NetCDF creation at 2019-12-18T20:40:25Z - NetCDF creation finished at 2019-12-18T20:40:26Z - 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/2019351/2019.351.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-12-18T20:40:25Z(start date = 2019-12-18T20:40:25Z, end date = 2019-12-18T20:40:26Z). - 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/2019351/2019.351.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/2019351/2019.351.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:34:55Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.65490483333334 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.902962666666674 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.84731633333337 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.04140583333337 to the max longitude of gps.log. - Set the content length of gps.log to 492980. - UpdateBot DataProducer persisted and has ID 50566. - Deployment gps was changed and persisted to the database with ID 50538. 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/2019351/2019.351.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/2019351/2019.351.00/hydroscatlog.nc - Starting the NetCDF creation at 2019-12-18T20:40:29Z - NetCDF creation finished at 2019-12-18T20:40:34Z - 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/2019351/2019.351.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-12-18T20:40:29Z(start date = 2019-12-18T20:40:29Z, end date = 2019-12-18T20:40:34Z). - 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/2019351/2019.351.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/2019351/2019.351.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:00Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 26019694. - UpdateBot DataProducer persisted and has ID 50567. - Deployment hydroscatlog was changed and persisted to the database with ID 50544. 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/2019351/2019.351.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/2019351/2019.351.00/isuslog.nc - Starting the NetCDF creation at 2019-12-18T20:40:35Z - NetCDF creation finished at 2019-12-18T20:40:35Z - 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/2019351/2019.351.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-12-18T20:40:35Z(start date = 2019-12-18T20:40:35Z, end date = 2019-12-18T20:40:35Z). - 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/2019351/2019.351.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/2019351/2019.351.00/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:36:11Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:13Z to the end date of isuslog.log. - Set the content length of isuslog.log to 1922549. - UpdateBot DataProducer persisted and has ID 50568. - Deployment isuslog was changed and persisted to the database with ID 50560. 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/2019351/2019.351.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/2019351/2019.351.00/lisstlog.nc - Starting the NetCDF creation at 2019-12-18T20:40:36Z - NetCDF creation finished at 2019-12-18T20:40:38Z - 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/2019351/2019.351.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-12-18T20:40:36Z(start date = 2019-12-18T20:40:36Z, end date = 2019-12-18T20:40:38Z). - 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/2019351/2019.351.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/2019351/2019.351.00/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:00Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 9784447. - UpdateBot DataProducer persisted and has ID 50569. - Deployment lisstlog was changed and persisted to the database with ID 50543. 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/2019351/2019.351.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/2019351/2019.351.00/navigation.nc - Starting the NetCDF creation at 2019-12-18T20:40:38Z - NetCDF creation finished at 2019-12-18T20:40: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/2019351/2019.351.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-12-18T20:40:38Z(start date = 2019-12-18T20:40:38Z, end date = 2019-12-18T20:40:58Z). - 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/2019351/2019.351.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/2019351/2019.351.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:34Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.65490589586614 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.902963856703 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.04140617098948 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.84488816374177 to the max longitude of navigation.log. - Set the content length of navigation.log to 114621478. - UpdateBot DataProducer persisted and has ID 50570. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:36Z_1586237575 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:36Z_1713419918 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2019-12-18T20:39:36Z_644281341 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 50539. 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/2019351/2019.351.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/2019351/2019.351.00/parosci.nc - Starting the NetCDF creation at 2019-12-18T20:41:00Z - NetCDF creation finished at 2019-12-18T20:41:07Z - 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/2019351/2019.351.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-12-18T20:41:00Z(start date = 2019-12-18T20:41:00Z, end date = 2019-12-18T20:41:07Z). - 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/2019351/2019.351.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/2019351/2019.351.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:34:59Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z 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.00867 to the max depth of parosci.log. - Set the content length of parosci.log to 37012454. - UpdateBot DataProducer persisted and has ID 50571. - Deployment parosci was changed and persisted to the database with ID 50549. 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/2019351/2019.351.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/2019351/2019.351.00/tailCone.nc - Starting the NetCDF creation at 2019-12-18T20:41:10Z - NetCDF creation finished at 2019-12-18T20:41: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/2019351/2019.351.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-12-18T20:41:10Z(start date = 2019-12-18T20:41:10Z, end date = 2019-12-18T20:41:14Z). - 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/2019351/2019.351.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/2019351/2019.351.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2019-12-17T20:35:00Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2019-12-18T18:06:14Z to the end date of tailCone.log. - Set the content length of tailCone.log to 18595435. - UpdateBot DataProducer persisted and has ID 50572. - Deployment tailCone was changed and persisted to the database with ID 50559. - Deployment 2019.351.00 was changed and persisted to the database with ID 50537. Processing for deployment 2019.351.00 ended at 2019-12-18T20:41:14Z