GETTING ERROR WHILE USING DYMOL INDICATOR

I'm at a loss what this is: a question or assertion? If a question, what's our next step?

Please read this carefully: How to Report Bugs Effectively > "It doesn't work", then follow author's suggestions and summary. Having finished with that, please provide the information necessary for troubleshooting using this convenient bullet point list:

* Describe the problem in detail. What error are you getting, precisely?
* Wealth-Lab tool in use (Chart, Strategy Window, Strategy Monitor, Strategy Ranking etc.)
* Strategy or sample code used. Again, we ask that you provide an "as-small-as-possible" script that demonstrates the anomaly.
* Single symbol or Multi-symbol mode, Position Sizing, Bar Scale and Data Loading settings
* Symbol(s) and Data provider

In a duplicate thread that doesn't exist, Darrell__ asked:

The Dynamic Momentum Index (DyMoI) Community Indicator is generating an "Unhandled Exception" error when I place it on an intraday chart.

Looks like that "an intraday chart" won't do: I just applied DyMoI to an intraday chart and nothing terrible happened. Please follow the troubleshooting instructions in my post #2 above. Also, copy/paste the complete exception message. Thanks.

Eugene,

Hope this helps:

1) Describe the problem in detail. What error are you getting, precisely?

Wealth-Lab will generate an error message (attached) when displaying the attached "ascii" data file. If another chart is already opened with the "DYMOI (Dynamic Momentum Index)" indicator already selected, then Wealth-Lab will crash when you select the attached data set (file).

2) Wealth-Lab tool in use (Chart, Strategy Window, Strategy Monitor, Strategy Ranking etc.)

New Chart Window with no strategies selected.

3) Strategy or sample code used. Again, we ask that you provide an "as-small-as-possible" script that demonstrates the anomaly.

N/A. No strategies or other code is being used.

4) Single symbol or Multi-symbol mode, Position Sizing, Bar Scale and Data Loading settings.

Single symbol mode; 5 minute scale; All Data; Position Size $100,000 (RP).

5) Symbol(s) and Data provider

"@AD-5-Min.txt"; ASCII file. Although this is an "ascii" text file and not a Fidelity Data file, I have been using this same data file to test many other indicators.

This isn't a big issue, but I find it odd that this is the only indicator I've used/tested thus far which causes any significant problems.

Thanks,

Darrell

Hi Darrell,

Thanks for the detailed walkthrough and especially the ASCII data which helped me reproduce the issue and understand the cause. Since fixing it was trivial, I've decided to distribute it w/o having to wait for the monthly release cycle.

You can update the extension now.

Wow... that was an incredibly quick fix. I hope everyone realizes what an asset you are to this forum and especially to this product. I can't think of any program I've ever used before that has better support! I will upload the update now.

Thanks again...

Thank you for the kind words. Always glad to help.

Eugene,

I was curious if you set a minimum and maximum limit value for the periods value in your fix, i.e. "int per = (int)(14 / VIX[bar]);" And if so, what values did you use?

regards

The period value may take negative values so the fix is to set its value to zero.

Eugene,

I don't think the period value should ever be negative; however, it can be zero (i.e. when the stdev of the 5 bar close is equal to 0)--this can often happen in intraday trading. In which case, the "DyMoI" value with your fix returns a zero value. (For example, refer to the "DyMoI" values for 23 Aug 18:45 - 19:00 using the sample data that I provided earlier.) That's a abrupt change when the prior values were all around 50. Maybe a better fix would be to set the "DyMoI" return value to 50 when the period value is equal to 0. Anyway, I like this indicator, but I think it needs a little tweak to make it better/more stable.

QUOTE:
I don't think the period value should ever be negative;

Darrell, yet it did with your data - when the VIX value reaches negative infinity (e.g. 21 Aug 13:25 - 13:30). Thanks for your tip re: setting the value to 50. I will change indicator's behavior as you suggested.

Version 2017.11 is out with the following change: the DyMoI crash fix would take 50 on negative values (previously 0).