Hi Team:

For your consideration:

I believe the Manual is using the term "Signal" instead of the more accurate term "Input" in some spots. In both text and code, we refer to an indicator we just created as a "Signal" instead of just calling it an Indicator. At the same time, the manual also refers to the final trade decision as a "Trade Signal". This should be streamlined.

We use signal in both of these two senses in this statement from Workshop 5,

"For generating trade signals, it is normalized and Fisher transformed, and the resulting Signal series is finally compared with an upper and lower Threshold for generating trade signals."

Can we reserve "Signal" for the context of a Trade Signal.. ie. a Buy ,Sell, Exit, or Hold signal ? An indicator crossing a threshold is an event. It is that crossing event that we would call a signal. Ex, it is commonly stated that 'Neural Networks accept inputs in order to output trade signals'.

Likewise, it is easier to say that we feed inputs to adviseLong() or adviseShort() in order to generate a Buy or Sell "Signal".

Here are some restatements of parts of the Manual:

"To create our final indicator, it is normalized and Fisher transformed, and the resulting Indicator series is finally compared with an upper and lower Threshold for generating trade signals."

"In training mode, Zorro learns rules that predict the success of a trade from the Inputs". "Inputs should be normalized roughly to the 100.. -100 range. "

vars Fisher_BandPass_Indicator = series(FisherN(Filtered,500)); // instead of
//vars Signal =


Thanks so much,

OptimusPrime