We're about to head out on a cruise from Florida to inland Canada, estimating about 6,000 statute miles or so.

We estimated the costs for removal of the current generator and installation of the new generator at $2,000. Altogether this brought the cost to $18,000 to $20,000. The decision to undergo an expensive repair rather than replace is always a risk.

Estimating distances, he saw my lights at 8 to 10 times the range I saw his. According to the "tonnage rule", he was on the wrong end of 40 to 60:1, his lucky day. LED's have come a long way since their first use as indicator lights on instrument panels in the 70's but for running/nav lights, I don't know if they're there yet.

It's OK to estimate to within 1/2 sq ft. The waterine number may be 11 sq ft, while the mast will be 1 sq ft or less; 11. Include things like flybridge enclosures, dinghies mounted on deck, radomes, etc. Anything the represents wind drag in your boat when it's anchored; 12.

For open source projects, I participated twice for Google Summer of Codes mentored by OpenCV on deep learning and 3D pose estimation tasks.

On this FAQ page, bandwidth estimates are listed for all devices except for E1xx. What are they?

I realized the offset when I was estimating the noise power using uhd_rx_cfile.py and afterwards processing the samples with octave. What I do is simply reading the complex binary data, performing fft and magnitude squaring. I found out that the data comming from the SBX seems to be corrupted by some sine or sine^2.

Nevertheless, when I precisely estimate the phase between the separate channels there are these 45 degrees jumps. The phase offset itself is not a problem, if it is constant, since it can be corrected. I would try this with the timed commands to see if it helps, but on Monday.

I am referring a section '*Parameter estimation and UHD > implementation*' from the website http://shannon.ece.ufl > .edu:6528/index.php/USRP_Transceiver_Tuning_and_Calibration.

To facilitate this, I make up estimates for the Event counter and Gate Counter and runs the calculation backwards: freq = Events / Time = Events / (GateCount * 90 MHz - Start + Stop) Events = freq * Time Time = Events / freq tau Events Gate Count -Start + Stop 1 s 5.000.000 90.000.000 -107,999 ps 100 ms 500.000 9.000.000 -119,999 ps 10