StrelokPro allows multiple bc input which is better right?
I think it might be. However I have only skimmed the surface of Strelok, so no real idea how it works. I am guessing that it pieces together a trajectory from a number of sections, each using a BC appropriate to the velocity range for each section. Would that be correct ?
I do most of my theorising, at home, not in the field, using a standard calculator, this one:
ShootersCalculator.com | Ballistic Trajectory Calculator a straightforward thing which can only accept either G1 or G7 BCs. There are many more G(x) models as well, maybe some of which might closer match a G(Yew Tree) bullet, but finding a calculator, or even a solver that knows these is I think outwith the realm of straightforward usage.
I do have some basic environmental measurement equipment, i.e. a Casio wristwatch for barometric pressure and temperature, as well as a windwatch more designed for nautical use. No humidity device. But, for UK conditions, no particular extremes of e.g. altitude or temperature, I think it is good enough, since I already have these. I do have a good but old set of LRF binoculars with a crude internal ballistics calculator which is surprisingly useful at hunting distances and much further. The calculator gives up predicting beyond 500m, but they range reliably to exactly one mile,1760 yards not a yard further (something to do with ITAR restriction at the time I bought them)
I am thinking of tinkering with the Hornady 4DOF app. to see how that works. Having read the White Paper about the theory (a deep read). Who knows, there might be a characterised bullet in their database already that is not dissimilar to a tipped Yew Tree. Might be interesting, but I have no pressing interest, or time, to try it out. It is "free" (at the moment).
https://press.hornady.com/assets/site/hornady/files/ballistic/hornady-4dof-technical-paper-v2.pdf
4DOF App - Hornady Manufacturing, Inc
They have "baked it in" to a Kestrel, in competition I suppose with Applied Ballistics, who own that space.
I am not clear about how wind drift measurements have been determined. It must be pretty difficult to be sure of the actual wind speed and direction along the bullet track, but perhaps measurements near the firing point are good enough ? Obviously having the electronic target is useful to see where the bullets are striking, at least in a relative manner unless a target face has been fitted and aligned. Both vertical and horizontal. If I have understood correctly the use of G1 wind drift predictions for these bullets closely matches the actual measurements of wind drift on the target, validating this method. And that the bullet has a BC matching closer to G1 than G7.
It is good that Yew Tree are testing and making available BCs, which seem to be absent from some others' information.
Measure the dimensions of the bullet and
determine your own drag function. Then press the 'ballistics' button and the program will go on to give you a drop chart based on the computed drag curve, not any ballistic coefficient....
This is fascinating. I must look up McDrag. Cut my teeth on Fortran BTW, mum taught it at the Computing Lab. at uni, along with other languages such as Algol-W and Ada so I was doing simple stuff even before I got my O-levels. Compiled stuff, not interpreted things like BASIC.
I am curious to know how you compute the drag curve, is that also part of the McDrag algorithms, or something more proprietary ? As you say, "The logical extension is to use McDrag as the front end of a complete external ballistics program, using the calculated drag curve to generate ballistic tables rather than use the usual Ballistic Coefficient with reference to a standard projectile as the starting point.
This is what has been done here."
Clearly what I’m after is a solution that people can use within the designed operating velocities of the bullet subject to the equipment I have. Given the distances you shoot I think you can corroborate that my solution works well 
