Mav-jp — Aujourd’hui à 15:12
that’s because of several things :
[15:12]
you need to understand how the HPRF work (modifié)
[15:13]
the missile turns on HPRF when it estimates that the distance between the virtual target is less than X NM ; and that this vvirtual target has a positive closing treshold passed
[15:14]
the radar has an errror not only on position, but also on velocity vector
[15:14]
so many things can happen, but for instance, if the real target is actually in a beam when the missile turns HPRF, the the HPRF will chose ANY target within his cone with a positive closure, and will totally disregard the real target which is basically invisible
[15:15]
from there you are screwed as the missile will start guiding to a total other target
[15:15]
a first issue here is that we made a data mistake , the AIM120 cone beam for now in BMS is 60 deg whereas it should be 30 deg
[15:16]
that of course increase the probability to find an alternate target in dense environment
[15:17]
so we need to fix this
Batman — Aujourd’hui à 15:17
Do you centre the cone around the virtual target or is centred around the missile axis?
Mav-jp — Aujourd’hui à 15:17
which of course changes entirely the probabilistic stuff that we need to adjust again
around the virtual target
the cone beam can be moved from -/+ 55 deg each side
be careful when you look at ACMI because with the huge LEAD guidance, you can have surprises between misisle axis and radar center
as i said , there are no mistake in implementations, we know what we are doing here, we have still some bugs
the one of MPRF target switching makes absolutly no sense at all
And if the missile doesn’t find any targets after switching to active, will it fly a ballistic arc or will it fly towards the last known point of intercept?
it will fly toard last known point and continue seeking within the cone beam
it is not last know point
it is predicted point based on last DL info received , position + speed vectors