Community,

Including a symbol with very limited trading history, is there a line of code that I should include in my strategies to prevent WLP from crashing upon execution? I have referenced the WIKI and help files to no avail using search term "IPO".

TIA

rhino

rhino,

Including where - Strategy Monitor? or Streaming Strategy window? or backtesting? Where's the code that crashes? What's the exception message?

Eugene,

In an open strategy, non streaming, backtesting, selecting the symbol from a dataset of 60 min bars consistently produces an immediate crash, no message, except, do I want to send data to Microsoft? Since the symbol now appears in a dataset I Strategy Monitor real time, I thought I'd posit the question to you beforehand.

rhino

Does it happen with all strategies or just some? What about those that came with WLP? If unique, we need the code.
What about the symbol name?
Does the log contain a recent entry linked to this crash? (..\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Logs\wlp.txt)

Eugene,

QUOTE:
2009-10-17 06:19:07,359 [8] ERROR Fidelity.Components.RequestManager.FidelityWebService [(null)] - Failed to fire OnWatchListGet event: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at WealthLab.DataProviders.FidelityWatchlist.b(WatchListGetResponse A_0)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Delegate.DynamicInvoke(Object[] args)
at Fidelity.Components.RequestManager.WatchListGet.DoCallback()
2009-10-17 06:48:05,156 [21] ERROR Fidelity.Components.RequestManager.FidelityWebService [(null)] - Failed to fire OnWatchListGet event: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at WealthLab.DataProviders.FidelityWatchlist.b(WatchListGetResponse A_0)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Delegate.DynamicInvoke(Object[] args)
at Fidelity.Components.RequestManager.WatchListGet.DoCallback()
2009-10-17 11:39:01,515 [Runner3] ERROR Fidelity.Components.RequestManager.RequestManager [(null)] - Unhandled re-direct.

I think these are two crashes this AM. Symbol CRIC .

I will try other strategies after an extended optimization run completes. This was from CandleCode [IBD 100]rev 1 on Published Strategies page.

rhino

Thank you. Although these log file entries aren't connected to the WLP crash, the other information is enough to reproduce the crash. I'll keep you posted.

Eugene,

Roger, Wilco. I think I hear you saying belay further strategy launching

pending results from your end?

ever obedient

rhino

rhino,

I've localized the bug somewhere in your Strategy XML file. The crash is probably caused by one of your drag & drop indicators saved with the chart. Are there any? If yes, then please let us know which one.

Thus, this particular (uploaded XML) file is affected - not the strategy code itself. Hence, the workaround will be quite simple: copy the strategy code, create a new code-based strategy, paste the code and save the new strategy.

We're going to let Fidelity know about the bug. Thanks.

Eugene,

There were two drag & drop indicators: Linear Regression & Linear Regression Slope.

Thanks for all the work.

Trust that I learn Buckets from these excursions.

I successfully implemented your outline locally. Will my provision of the D & D Indicators result in a determination as to which, if either, is still usable?

In the upload, there are features stored which are invisible to the Administrators? Can you explain the quick and dirty on D&D storage?

never fully understanding

rhino

Just don't use a saved strategy/chart that has LinearReg indicators with symbols which Bars.Count is less than the indicator's period e.g. IPO, or when the chart's data range was artificially limited to a small amount of data displayed.

Wealth-Lab won't allow dropping an indicator of period 20 on a 30(60)-minute chart of CRIC that currently has only a dozen of bars. The problem is when you run such a chart/strategy with drag & drop indicators, on a symbol whose data range < indicator period.

Eugene,
In the interest of my personal closure, the Drag & Drop was included in the uploaded html of the strategy, was able to trigger a crash,
and was invisible to Eugene as you examined the problem. You determined that a D & D was the responsible code snippet, but its specific
nature (e.g. Linear Regression, //Slope) was a hidden attribute? Are the preferred values likewise included in the upload? Are they likewise
a hidden attribute?

You've been very patient

rhino

Well, saved D&D indicators are "invisible" to a technician examining the code and even the Strategy's XML file. They are what is called "serialized" to a non-human readable string. Eventually, this string will be erased for new Strategy uploads performed on the site.

Update:

This is a confirmed bug to be fixed in a later release: LinearReg and LinearRegSlope can crash Wealth-Lab if source series count < period.