The strategy, ETF-Eager Bever 2w PeekChecker, interests me. After translated by WSTL, the code can not be compiled on WLD. Want to get help from you guys for the followed errors.

1, The name 'Gaussian' does not exist in the current context
2, The name 'StartPeekCheck' does not exist in the current context
3, The name 'InstallTimeBasedExitR' does not exist in the current context
4, The name 'ApplyAutoStopsR' does not exist in the current context
5, The name 'PriceCloseR' does not exist in the current context
6, The name 'CoverLimitR' does not exist in the current context
7, The name 'BuyAtLimitR' does not exist in the current context
8, The name 'ShortAtMarketR' does not exist in the current context
Besides, the warning indicates "The predefined type 'System.Threading.Tasks.Task' is defined in multiple assemblies in the global alias; using definition from 'C:\\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll'"

Thanks

The PeekChecker library was not translated to C#. I doubt that WSTL can have any success in its automatic translation. Consequently, you have to:

1. Get rid of StartPeekCheck
2. Replace PriceCloseR, CoverLimitR, BuyAtLimitR and ShortAtMarketR with their native analogues without the 'R' postfix
3. Same for ApplyAutoStopsR and InstallTimeBasedExitR

Additionally:

4. For ApplyAutoStopsR and InstallTimeBasedExitR, there are 3 alternatives:

4.1. Rename them as suggested in #3 which is equivalent to...
4.2. ...Drop them altogether. (Recommended)
4.3. Not recommended: Use the AutoStops set of functions to manually translate them into pure WealthScript. This is the most complicated option and I'm sure it won't work. Mixing WSTL code with native WealthScript inserts is always a bad idea.

5. Finally, the additional Gaussian filter (click) used by the code. I'm sure there's a way in WSTL to include a library from external .WS file. Check its Help as the tool is no longer supported.

QUOTE:
Besides, the warning indicates "The predefined type 'System.Threading.Tasks.Task' is defined in multiple assemblies in the global alias; using definition from 'C:\\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll'"

Hmm, this is something new. If this error only bugs your WSTL-generated strategies, then I think that WSTL authors could have defined a Task class somewhere back in 2006/7 that has become redundant since the introduction of .NET 4.0. I think you can disregard this message.