PDA

View Full Version : Autocrew - TMA



wranger
09-02-2006, 11:52 AM
Hi


How can you tell when the autocrew has a good solution ? I'm just getting started and was tailing a ssn, but the Nav map contact seemed to jump around.

Many thanks

Molon Labe
09-02-2006, 02:38 PM
Hi


How can you tell when the autocrew has a good solution ? I'm just getting started and was tailing a ssn, but the Nav map contact seemed to jump around.

Many thanks

aTMA can be a bit funny sometimes. In general, the solution tends to start good when it is first made, and then it will jump around a bit and then settle again. I'd say if your leg is at least 4 lines long you're probably pretty well settled down again, provided the contact hasn't changed course or speed. Also, the settling process will start again after you manuever ownship...and yes, that is a bit unrealistic, but the way they've programed error into the aTMA is a bit crude (and thus, interpreting it can be a bit "gamey" at times). Think of the solution as the oscilations of a dampened spring. The high points and low points are the error range; the true solution is the steady state.

I think, or at least hope, then when the solution for the second leg settles, it will be better than it was after the first leg.

Always check the DDI for an aTMA solution to see its "Age." In high-contact environments, the aTMA gets lagged up and lets solutions get very old. If you see this happening, switch to manual and update the oldest ones yourself.

Probably the best way to see if aTMA is getting it right is to get the solution yourself, especially if you have DEMON info. :wink:

wranger
09-03-2006, 06:10 AM
Hi


Thanks for that one. On the stack there seems to be numbers that change and vary from 1 - 5, do you know what they mean ?


Thanks

Molon Labe
09-03-2006, 11:10 AM
Hi


Thanks for that one. On the stack there seems to be numbers that change and vary from 1 - 5, do you know what they mean ?


Thanks

Are those the labels on the horizontal axis? If so, it's probably a measure of deviation for the data points. It's also rather unnecessary, because you can tell if the stack is aligned or not just by looking at it.