Respected Seniors, I am finding mis match value of the indicator parked on my chart & in exploration reports.Even in inspection of exploration combo box for each security the value actually shown in the final list varies than that within the inspection box of that scrip. Initially i thought as Trough uses Zig whose last leg being dynamic this was happening.But even if i use DX() the same problem.Can u suggest how to get the value showing in the chart to get in exploration also in the same Day otherwise BarsSince also delays by another day. Regards Asish

Uasish Using "Minimum Records" for an exploration is the most common cause of explorations returning the "wrong" value. The many functions that use a form of exponential moving average require about 5 times the nominal "periods" parameter to return an accurate value. These functions include (but are not limited to) ADX, RSI and Wilders Smoothing. Functions with an "Nth" parameter also suffer when insufficient bars are loaded. There is no way to estimate how much data is required but "more" is better. ValueWhen() falls into this category. BarsSince() may need 2 bars or it may need 2000. If the event it triggers from does not occur within the nominated number of bars then N/A is the certain result. A "periods" parameter in any function ensures that at least "periods" bars are loaded, but many times this is not sufficient and the user must stipulate a larger number. Using the same number of bars as is loaded with each chart is sometimes suggested. This is usually overkill, but 100 to 500 can be quite appropriate, particularly with longer EMAs. Hope this helps. Roy MetaStock Tips & Tools

It sounds like you changed the chart "Load Options" not the Explorer load options. Click Tools>The Explorer and click the Options button at the bottom of the Explorer main menu. This is where you can "match" the load options in the Explorer with the Load Options of your charts.

Asish, The results of my explorations and my charts match exactly, BUT there is a catch! This is what I did... Exploration 1. {ColA} DX(14) {filter} {none} Options: Load 1300 records Time taken to scan 2202 stocks : about 30 seconds Results agree with charted values: YES -- Exploration 2. {ColA} DX(14) {filter} {none} Options: Load 32767 records (the maximum number for explorations) Time taken to scan 2202 stocks : about 1 minute Results agree with charted values: YES -- Exploration 3. {ColA} DX(14) {filter} {none} Options: Load MINIMUM records Time taken to scan 2202 stocks : about 15 seconds Results agree with charted values: NO HOWEVER.... to match the value, the chart must also have the appropriate number of records loaded. I normally have the maximum amount chart loaded (65500 bars) (although there are not many stocks old enough to have this much data). If I load 65500 bars, the value of DX(14) for one company is say, 22. If I load 1300 bars, the value of DX(14) for the same company is 22. If I load 30 bars, the value of DX(14) for the company 24. So the results of Exploration 1 and Exploration 2 match the the chart only if I have 1300 bars or more loaded. The results of Exploration 3 match the chart if I have only 30 bars loaded. I don't have the code for the DX indicator with me right now (I have it somewhere I am sure) but I am pretty sure it uses PREV type values in its computations, which means that the value today will contain a (small) amount of yesterdays value and the day before vale and the day before that... If you try to skimp on the data loading then you are going to skew the result of the exponential computation. -- This goes to show the importance of having the right number of bars loaded in both your charts and explorations. Some people like to skimp on the bars loaded during explorations because they think it might save them time, but if you trade based on the results of an exploration that was producing flawed results because the indicators did not have enough history, then your trades will be flawed and you risk losing money. If you think that you need to experiment to find the minumum number of bars to load without skewing the results then I think you are sailing too close to the wind and need to find another hobby. Take up skydiving, BASE jumping, wild-pig hunting or something else less dangerous to your health than computer programming. If your explorations/system tests/code are taking too long to run, then: 1. Look carefully at your code. How many PREV functions do you have? Are they really necessary in your code, or have you added them just to see the results in report column? How many calls to ExtFml(), FmlVar() and Fml() do you have? These all slow down the execution of the code and hence the exploration (and system tests too!) 2. Don't explore the entire universe of stocks, warrants, options, indexes, mining companies, retailers, manufacturers etc if you only trade, say oil stocks. Separate your data into folders (your data provider should show you how, or there are third party software products available cheaply) so that you are scanning the minimum number of stocks; stocks that you actually trade. According to my data provider there are 2202 stocks on the ASX; so I scan only these without looking at options, warrants or indexes. 3. Get a faster computer. The cheapest option is to add RAM. As much as you can afford, and as much as your motherboard can hold. It takes about 30 seconds to add a stick of RAM, and you do not need to be a professional nerd to do it. The next cheapest option, after you have filled your quota of RAM is to get a faster HD. Look for one with caching, they are slighly faster than non-cached disks. SCSI discs are back in fashion, with 10000 RPM becoming the norm. Size does not necessarily equate to speed. Get the fastest disc your pocket can afford. Again, you do not have to be nuclear physicist to add another HD to your machine. It will take about 10 minutes. The last resort is to completely replace your machine (but don't throw the old one out!) 4. Manage your time better. If you get stressed about an exploration that takes 2 minutes or five minutes to complete then I think you need to relax more and get out of the house! How much time could you save by managing your day better than trying to better manage a computer? If you have any more questions, please ask. I hope this helps. wabbit :D

:crylol: Hey Asish- The only egos here are those that want to help you suceed in using the Equis line of products. Don't read into it... Wabbit's a nice fellow and a great teacher! G

Asish, Exploration Problems: Am I correct that your explorer results are different from the charts again. Are you using Zig(), Peak(), Trough(), LastValue() functions in your explorations? If you are, then these are the most likely culprits causing the different results in an exploration from the plotted indicator. These functions are all dynamic and extremely dangerous for exactly this reason. If you are still having problems with the explorations and "mis-matching", then please post all of the code you are using in the Exporation. It is very hard to provide assistance, and explain why an event is happening on your computer when we cannot see any of your code. It would also be extremely valuable for you to add a small portion of the results and a small portion of the chart so we can compare the two ourselves. -- I strongly suggest you rethink your tradng strategy if you are going to use the Peak and Trough functions as a basis for your trades. These functions, along with ZigZag and LastValue are hindsight indicators; they change their values in the past based on new information received, or in other words, they always make the "right decisions" with the benefit of hindsight. Read up in the MS Users Manual on the dangers of these functions in trading systems. I do not fully understand what you are trying to achieve, because like a computer, I need to be given instructions in very SPECIFIC terms. The use of "ideally" and "few" do not give clear instructions to the programmer. You must use words like "shall" and "three days" etc When you are as tired as I am right now, you need clear instructions to be able to write the correct code. You need to be very specific here. If you want to bound the two values to a range, you can do something like: Abs(PDI(14)-MDI(14))<5; To have this condition over 'x' consecutive bars: z:=Sum(Abs(PDI(14)-MDI(14))<5),x)=x; To have the two lines breaking a part after being in the bounded values for the 'x' bars: z:=Sum(Abs(PDI(14)-MDI(14))<5),x)=x; z=0 and Ref(z,-1)=1 and pdi(14)>mdi(14); Do you need to count how many times the two lines have crossed in the last 'x' days? This is possible too. Can you see how specific you need to be? I have already mentioned the dangers of this indicator, so I strongly suggest you think of an alternative. One of the very few good things with the indicator is that it can cut down on some code, sometimes. ROC(Zig(ADXR(14),10,%),1,%)>0; The Zig() function only rises or falls. To be rising, it must be coming out of a trough, so there is no need to try and catch the order of peaks and troughs. -- Try writing down each individual step that is required for your code to return a value of TRUE (or 1). Once you have written this down, then code each line, checking as you go through that each line returns the value that you expect. Debug your code line by line. There is no point getting to the end of the exploration to have unexpected results because your code has a mistake in the first line which is destroying the rest of your function. I hope this helps. wabbit :D

Asish, if u wanna b taken seriously here, try cutting out the "u/r/ur/becoz" SMS jive. Use plain English whereva possible. jose '-)

Asish, with all respect, look up the meaning of "Irony". jose '-)

Respected Wabbit, Your formula :{ROC(Zig(ADXR(14),10,%),1,%)>0; } is excellent.Instead of Trough function ,I have seen somewhere ,cant remember now , he has used {Ref(LOW,-4)=LLV(LOW,9)}.What is your suggestion.Here though the excellent hind sight is compromised but atleast the exploration result mismatch can be overcomed.However your formula{z:=Sum(Abs(PDI(14)-MDI(14))<5),x)=x; z=0 and Ref(z,-1)=1 and pdi(14)>mdi(14); }beautifully catches the 1st Condition now for the 2nd Condition ,forgoing ADXR rising ,plz help me with this new 2nd condition:ADX(14) rising and PDI(14) MDI(14) ADX(14){all these 3's value} are in a difference of max 4,means lowest low value of any(3 indicator's individual values) difference to there highest high value of each other is max 4. Regards Asish

Respected Wabbit, Thks, excellent solution.I have learnt this nested function from you today.Using Mr Jose's :=)EMA - (BEMA), dll version is there any mismatch of values on the report page(not the inspection page) ? Regards Asish