1) If I understand right, the SETI CLI does the crunching and runs in the backgound. The SETI Driver does the DL/UL thing and monitors progress. If this is true, can I shut of the SETI Driver and keep cruching until I am through with the WUs in cache?
2) If #1 is true does the Driver use overhead and would you get better performance only turning it on when you need to UL/DL?
Thanks,
Ed
2) If #1 is true does the Driver use overhead and would you get better performance only turning it on when you need to UL/DL?
Thanks,
Ed