Here is a small piece form a ge.log, with radar logging operating.

 

104351 Search.c:860 - Radar Emitter=AF-18A/B Hornet Target=E-737 Wedgetail, TargetRange=124, Radar LOS = (BaseLOS x weather_mod + 128)/256

104351 Search.c:861 - Radar LOS of 327nm = (327nm x 256 + 128)/256 --> Radar LOS=107057/256

104351 Search.c:867 - A RCS=157 TName=E-737 Wedgetail AName=AF-18A/B Hornet Range=124 Die=31 aPD=65

104351 Search.c:940 - B RCS=157 ARng=130 Arng=160 SRng=130 Srng=160

104351 Search.c:944 - Target was previously tracked.

104351 Search.c:987 - Detected E-737 Wedgetail with Air-to-Air Radar of range 130 with PD 65, Roll=31

104351 Search.c:1024 - Type of target known

104351 Search.c:860 - Radar Emitter=E-737 Wedgetail Target=AF-18A/B Hornet, TargetRange=124, Radar LOS = (BaseLOS x weather_mod + 128)/256

104351 Search.c:861 - Radar LOS of 327nm = (327nm x 256 + 128)/256 --> Radar LOS=107057/256

104351 Search.c:867 - A RCS=136 TName=AF-18A/B Hornet AName=E-737 Wedgetail Range=124 Die=44 aPD=80

104351 Search.c:940 - B RCS=136 ARng=113 Arng=317 SRng=113 Srng=317

104351 Search.c:1017 - Not Detected AF-18A/B Hornet

 

I assume: Radar LOS = radar line of sight distance, ie from emitter to horizon, can't 'see' any further due to earth curvature, BUT, if so, is it taking into account height of emitter and target and if so is that shown?

 

Somewhere I expect a little bit stating a final probability of the emitter detecting the target and a dice throw to determine, ie throw less than prob and get a detection other wise not...something like

"Die=31 aPD=65" and bingo that works for one detection but in the second we have die=44 aPD=80 so my theory is bad, so what is this part?

 

I guess RCS is radar cross section from the DB (I should check shouldn't I), my question though where is this put into the calculation of final detection prob?

 

ARng, Arng, SRng & Srng; these must be significant as they seem to be the biggest difference between the two data/calculations, but what are they, where do they go into the maths?

 

I'd like to get the hang of these logs (ECM is next) but I find I have a lot to learn.

One more question, I haven't found a logging that helps me (this does ?) with esm, where do I go?

Don Thomas

I assume: Radar LOS = radar line of sight distance, ie from emitter to horizon, can't 'see' any further due to earth curvature, BUT, if so, is it taking into account height of emitter and target and if so is that shown?

The two heights are taken into account but they are not shown since they were not an item in question when looking at radar (we know they are right and work right, the logging capability was made for debugging, not general interest but obviously it can be used for both).

 

The crazier thing is that no matter the die roll the Hornet would have maintained contact with the Wedgetail. The radar model says that if you are already tracking the target, detection is automatic if you are within range.

 

Somewhere I expect a little bit stating a final probability of the emitter detecting the target and a dice throw to determine, ie throw less than prob and get a detection other wise not...something like

"Die=31 aPD=65" and bingo that works for one detection but in the second we have die=44 aPD=80 so my theory is bad, so what is this part?

Your theory is correct, if die is less than PD and all other conditions are met, you should get a detect. The limitation in the case you list is that the target is at 124nm and the radar has a range of 113nm against the target so no detect due to range.

 

I guess RCS is radar cross section from the DB (I should check shouldn't I), my question though where is this put into the calculation of final detection prob?

 

ARng, Arng, SRng & Srng; these must be significant as they seem to be the biggest difference between the two data/calculations, but what are they, where do they go into the maths?

RCS does not affect probability but it is a major factor in the ARng vs ARng calculation. The bigger ARng being the raw radar range from the DB and the smaller being the range when RCS, weather, and whatnot are accounted for.

 

I'd like to get the hang of these logs (ECM is next) but I find I have a lot to learn.

One more question, I haven't found a logging that helps me (this does ?) with esm, where do I go?

Don Thomas

There is no logging for ESM. So I suppose you add it to your wishlist.

That all helped heaps Tony,

(I think it is starting to be useful to me)

Now:

another string of log-

105641 Search.c:860 - Radar Emitter=F-111C Aardvark Target=Amberley, TargetRange=178, Radar LOS = (BaseLOS x weather_mod + 128)/256

105641 Search.c:861 - Radar LOS of 246nm = (246nm x 256 + 128)/256 --> Radar LOS=60644/256

105641 Search.c:867 - A RCS=199 TName=Amberley AName=F-111C Aardvark Range=178 Die=38 aPD=0

105641 Search.c:940 - B RCS=199 ARng=0 Arng=0 SRng=364 Srng=160

105641 Search.c:958 - Detected Amberley with Surface Radar of range 364 with PD 65, Roll=38

105641 Search.c:1024 - Type of target known

 

I see a test for F 111C detecting Amberley base at a physical range of 178 nm.

Line of sight emitter to target is 246, check OK.

F 111C has no air search so ARng & Arng = 0, check OK

 

Database gives range of SS radar for Ardvark as 160 nm (= Srng as I expect from looking at other logs items)

BUT here the (I'll call it final surface range) SRng is more than double at 364 nm - this takes the case from one where the target is out of range to where it is in range.

QUESTION: how does that final ss range more than double?

 

QUESTION: what is difference between "A RCS" & "B RCS"?

 

I see a air detection prob ( aPD) = 0, check ok, but in the same area there is no print out of the sPD (see next log string), here I only know the sPD from the 'detected Amberley' line.

QUESTION: is than an omission from the logging printout?

 

next string:

 

105611 Search.c:860 - Radar Emitter=F-111C Aardvark Target=Amberley, TargetRange=178, Radar LOS = (BaseLOS x weather_mod + 128)/256

105611 Search.c:861 - Radar LOS of 246nm = (246nm x 256 + 128)/256 --> Radar LOS=60644/256

105611 Search.c:867 - A RCS=199 TName=Amberley AName=F-111C Aardvark Range=178 Die=77 aPD=0

105611 Search.c:940 - B RCS=199 ARng=0 Arng=0 SRng=364 Srng=160

105611 Search.c:1017 - Not Detected Amberley

 

I see from the numbers in the left columns this is 30 secs prior to the first string I showed (last previous radar detection tests).

Here Amberley isn't detected but it doesn't tell me why not, if I look at the other string I learn the sPD is probably 65 so the die throw was too big.

MY CONCLUSION, the printout omits to list the sPD value in the ' A RCS...' line but it should.

Don Thomas

True, it looks like surface PD isn't listed though you could look in the DB for that if you got really curious.

 

Range is indeed wrong there, that would be the range if Amberly were an aircraft target (I derived that from the Radar RCS worksheet). What version of the game are you using?

 

HCE - 2009.053 - 2011/03/10

===========================

- Chg:0000 GE Radar model was treating land installations like aircraft so

possible detection ranges were way too large. (thanks Brad)

True, it looks like surface PD isn't listed though you could look in the DB for that if you got really curious.

 

Range is indeed wrong there, that would be the range if Amberly were an aircraft target (I derived that from the Radar RCS worksheet). What version of the game are you using?

 

HCE - 2009.053 - 2011/03/10

===========================

- Chg:0000 GE Radar model was treating land installations like aircraft so

possible detection ranges were way too large. (thanks Brad)

OOps, slow me, I was using 2009.42, could I run the 2009.53 without the latest HCE patch while waiting for 'ultimate'?

Don.

OOps, slow me, I was using 2009.42, could I run the 2009.53 without the latest HCE patch while waiting for 'ultimate'?

Don.

 

You sure can