Now --noglobal sets lambda_bg to 1e-9 instead of 0 to bypass infinite loop issue when there was a single read in the control at position 40k of rDNA and other than that none from 30k up. It works, but it is clear I need a real fix for --noglobal, not this bandaid. To help in the mean time, there is also --setglobal now. --setglobal allows you to choose any lambda_bg value you want - the goal being just shy of the minimum local value encountered. A real fix might entail ignoring regions where there is no local information to use -- if no local information and --noglobal, then ignore.