SSDS Processing Report for data sets from Deployment 2018.164.00 Processing began at 2018-06-15T18:48:04Z Going to try to convert any outputs of deployment 2018.164.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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/biolume.nc - Starting the NetCDF creation at 2018-06-15T18:48:04Z - NetCDF creation finished at 2018-06-15T18:48:12Z - 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/2018/2018164/2018.164.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 2018-06-15T18:48:04Z(start date = 2018-06-15T18:48:04Z, end date = 2018-06-15T18:48:12Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/biolume.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:04Z to the start date of biolume.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of biolume.log. - Set the content length of biolume.log to 27096862. - UpdateBot DataProducer persisted and has ID 49851. - Deployment biolume was changed and persisted to the database with ID 49829. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/ctdDriver.nc - Starting the NetCDF creation at 2018-06-15T18:48:13Z - NetCDF creation finished at 2018-06-15T18:48: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/2018/2018164/2018.164.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 2018-06-15T18:48:13Z(start date = 2018-06-15T18:48:13Z, end date = 2018-06-15T18:48:18Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/ctdDriver.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:40Z to the start date of ctdDriver.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of ctdDriver.log. - Set the content length of ctdDriver.log to 37332294. - UpdateBot DataProducer persisted and has ID 49852. - Will loop through child deployments now (there are 5 of them) Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:58Z_1436792695 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:58Z_1488174493 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:58Z_1755168445 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:58Z_295368317 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:58Z_953843748 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver was changed and persisted to the database with ID 49830. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/ctdDriver2.nc - Starting the NetCDF creation at 2018-06-15T18:48:18Z - NetCDF creation finished at 2018-06-15T18:48: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/2018/2018164/2018.164.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 2018-06-15T18:48:18Z(start date = 2018-06-15T18:48:18Z, end date = 2018-06-15T18:48:23Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/ctdDriver2.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:40Z to the start date of ctdDriver2.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of ctdDriver2.log. - Set the content length of ctdDriver2.log to 37333439. - UpdateBot DataProducer persisted and has ID 49853. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:59Z_1724415199 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:59Z_2065270458 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:59Z_401471077 to NetCDF files: - There were no direct outputs for that deployment. - Deployment ctdDriver2 was changed and persisted to the database with ID 49845. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/dvl.nc - Starting the NetCDF creation at 2018-06-15T18:48:23Z - NetCDF creation finished at 2018-06-15T18:48: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/2018/2018164/2018.164.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 2018-06-15T18:48:23Z(start date = 2018-06-15T18:48:23Z, end date = 2018-06-15T18:48:26Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/dvl.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:07Z to the start date of dvl.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:12Z to the end date of dvl.log. - Set the content length of dvl.log to 19203465. - UpdateBot DataProducer persisted and has ID 49854. - Deployment dvl was changed and persisted to the database with ID 49843. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/dynamicControl.nc - Starting the NetCDF creation at 2018-06-15T18:48:26Z - NetCDF creation finished at 2018-06-15T18:48:48Z - Now will write out the NetCDF creation log to http://new-ssds.mbari.org/ssdsdata/ssds/generated/netcdf/files/ssds.shore.mbari.org/auvctd/missionlogs/2018/2018164/2018.164.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 2018-06-15T18:48:26Z(start date = 2018-06-15T18:48:26Z, end date = 2018-06-15T18:48:48Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/dynamicControl.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:45Z to the start date of dynamicControl.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of dynamicControl.log. - Set the content length of dynamicControl.log to 142926312. - UpdateBot DataProducer persisted and has ID 49855. - Deployment dynamicControl was changed and persisted to the database with ID 49841. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/gps.nc - Starting the NetCDF creation at 2018-06-15T18:48:50Z - NetCDF creation finished at 2018-06-15T18:48:50Z - 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/2018/2018164/2018.164.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 2018-06-15T18:48:50Z(start date = 2018-06-15T18:48:50Z, end date = 2018-06-15T18:48:50Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/gps.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:04Z to the start date of gps.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of gps.log. - Since a min latitude was found in the NetCDF file, will assign 36.75986216666668 to the min latitude of gps.log. - Since a max latitude was found in the NetCDF file, will assign 36.839029000000004 to the max latitude of gps.log. - Since a min longitude was found in the NetCDF file, will assign 121.83610600000002 to the min longitude of gps.log. - Since a max longitude was found in the NetCDF file, will assign 122.02105350000002 to the max longitude of gps.log. - Set the content length of gps.log to 680324. - UpdateBot DataProducer persisted and has ID 49856. - Deployment gps was changed and persisted to the database with ID 49850. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/hydroscatlog.nc - Starting the NetCDF creation at 2018-06-15T18:48:51Z - NetCDF creation finished at 2018-06-15T18:48: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/2018/2018164/2018.164.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 2018-06-15T18:48:51Z(start date = 2018-06-15T18:48:51Z, end date = 2018-06-15T18:48:57Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/hydroscatlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:10Z to the start date of hydroscatlog.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of hydroscatlog.log. - Set the content length of hydroscatlog.log to 32664514. - UpdateBot DataProducer persisted and has ID 49857. - Deployment hydroscatlog was changed and persisted to the database with ID 49844. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/isuslog.nc - Starting the NetCDF creation at 2018-06-15T18:48:57Z - NetCDF creation finished at 2018-06-15T18:48: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/2018/2018164/2018.164.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 2018-06-15T18:48:57Z(start date = 2018-06-15T18:48:57Z, end date = 2018-06-15T18:48:58Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/isuslog.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:28:23Z to the start date of isuslog.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of isuslog.log. - Set the content length of isuslog.log to 2427797. - UpdateBot DataProducer persisted and has ID 49858. - Deployment isuslog was changed and persisted to the database with ID 49842. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/lisstlog.nc - Starting the NetCDF creation at 2018-06-15T18:48:58Z - NetCDF creation finished at 2018-06-15T18:48:59Z - 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/2018/2018164/2018.164.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 2018-06-15T18:48:58Z(start date = 2018-06-15T18:48:58Z, end date = 2018-06-15T18:48:59Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/lisstlog.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:12Z to the start date of lisstlog.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:10Z to the end date of lisstlog.log. - Set the content length of lisstlog.log to 3879247. - UpdateBot DataProducer persisted and has ID 49859. - Deployment lisstlog was changed and persisted to the database with ID 49849. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/navigation.nc - Starting the NetCDF creation at 2018-06-15T18:49:00Z - NetCDF creation finished at 2018-06-15T18:49: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/2018/2018164/2018.164.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 2018-06-15T18:49:00Z(start date = 2018-06-15T18:49:00Z, end date = 2018-06-15T18:49:22Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/navigation.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:45Z to the start date of navigation.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of navigation.log. - Since a min latitude was found in the NetCDF file, will assign 36.75961291725208 to the min latitude of navigation.log. - Since a max latitude was found in the NetCDF file, will assign 36.83920469797405 to the max latitude of navigation.log. - Since a min longitude was found in the NetCDF file, will assign -122.02515317382017 to the min longitude of navigation.log. - Since a max longitude was found in the NetCDF file, will assign -121.83610569966709 to the max longitude of navigation.log. - Set the content length of navigation.log to 143899726. - UpdateBot DataProducer persisted and has ID 49860. - Will loop through child deployments now (there are 3 of them) Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:59Z_1117677785 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:59Z_1395256924 to NetCDF files: - There were no direct outputs for that deployment. Going to try to convert any outputs of deployment Deployment_2018-06-15T18:47:59Z_1843035906 to NetCDF files: - There were no direct outputs for that deployment. - Deployment navigation was changed and persisted to the database with ID 49837. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/parosci.nc - Starting the NetCDF creation at 2018-06-15T18:49:23Z - NetCDF creation finished at 2018-06-15T18:49:32Z - 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/2018/2018164/2018.164.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 2018-06-15T18:49:23Z(start date = 2018-06-15T18:49:23Z, end date = 2018-06-15T18:49:32Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/parosci.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:09Z to the start date of parosci.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z 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 252.43085 to the max depth of parosci.log. - Set the content length of parosci.log to 46464518. - UpdateBot DataProducer persisted and has ID 49861. - Deployment parosci was changed and persisted to the database with ID 49836. 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/tailCone.nc - Starting the NetCDF creation at 2018-06-15T18:49:33Z - NetCDF creation finished at 2018-06-15T18:49: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/2018/2018164/2018.164.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 2018-06-15T18:49:33Z(start date = 2018-06-15T18:49:33Z, end date = 2018-06-15T18:49:37Z). - 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/2018/2018164/2018.164.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/2018/2018164/2018.164.00/tailCone.nc.log. - Since a start date was found in the NetCDF file, will assign 2018-06-13T16:27:09Z to the start date of tailCone.log. - Since a end date was found in the NetCDF file, will assign 2018-06-14T19:28:13Z to the end date of tailCone.log. - Set the content length of tailCone.log to 23343499. - UpdateBot DataProducer persisted and has ID 49862. - Deployment tailCone was changed and persisted to the database with ID 49828. - Deployment 2018.164.00 was changed and persisted to the database with ID 49827. Processing for deployment 2018.164.00 ended at 2018-06-15T18:49:38Z