for the anchor test, the anchor value should match across chunks or differ only by rounding. a bigger mismatch means the chunks sit on different scales. the anchor also has to be the top series in every request you run, not just the one you inspect
the five term cap on the classic endpoint is real, so calling it google’s cap is fair
Agreed on both. Matching anchors across chunks (within rounding) is the scale check, and the anchor has to be the top series in every request, not just the one you inspect. The classic endpoint's five-term cap is Google's, so naming it that way is fair.
OnlineProxy
for the anchor test, the anchor value should match across chunks or differ only by rounding. a bigger mismatch means the chunks sit on different scales. the anchor also has to be the top series in every request you run, not just the one you inspect
the five term cap on the classic endpoint is real, so calling it google’s cap is fair