Turbo Use Custom Levels

[quant...@gmail.com]

The Scalper Use Custom Levels feature in the FAP Turbo coding is
connected to a global function called a Noise Filter. Now normally a
Noise filter is something that would be used to screen out rapid
movements in the bid and ask prices in a high volatility bar which
would be for the purpose of preventing orders from being placed during
these times or exiting orders during these times. And in fact there is
a spread monitor in the coding that would normally be used to
accomplish this task. However, it is currently being used as the
Slippage level in an Order Close function. This is highly unusual as
most times you want the slippage level to be fixed. Perhaps the idea
here is to try to get orders to close if there is an extremely
volatile situation, but using a spread detection function that can be
volatile of its own accord in an order processing functions is NOT a
good idea.
This kind of coding will typically cause order processing delays at
the least and error messages and non execution at the worst.

What the Noise Filter actually does is to monitor the spread between
the Open Order Price and the Close Order Price and then compare this
spread against a measure of time. There are 5 different time to spread
relationships defined in the coding which appear to be designed to
close orders under these specific relationships. However, at the
present time the orders are closed when none of these relationships
apply.

As it appears as though there is a conflict between this feature and
other aspects of the order management portions of the program I
currently recommend that the Scalper_UseCustomLevels be set to FALSE.