Some of the early individual evaluation reports had more visual details and later tests are more short hand saving the writer and us readers the redundancy of how this “standard evaluation” is being conducted.
Nobody wants to see a very long post with a swfa 6x drop test in every scope test post. It would make it way too complex to follow.
Well, that explains it.
Too much information?!
I get your points. But you may want to take a moment to realize that negative results are being publicly posted about another organization's product(s). Their scopes, correct?
And the reporting would benefit from details to support the conclusions. That's all part of competitive testing, and best practice.
Or is this just for the Rokslide fanboys?
Or just page clicks?
I thought it was to eventually improve scopes, and the industry as a whole, which is highly commendable.
If so, that audience expects details. Technical details. Especially with negative results being claimed.
The original question, by another member, was in regards to whether a proof scope was going to be used. Which is stated in the original method.
Mr. Avery then confirmed that there's always a control.
Well, where are the proof results then?
Those details strengthen the reporting, even if it's too much of an inconvenience for you to read.
I don't know what your backgrounds are, but I spent 20+ years as an engineer in research and product development.
I am now very fortunate to have clients in various industries across the globe where I evaluate their processes, testing, reporting, and manufacturing. And I make them fix issues like what is being discussed here. I approve the fixes before implementation.
In case you are wondering, I don't work with any companies that make sporting optics. I do have clients that make optics for astro, surveillance, comms, and energy.