On My Way To The Top

Just read the fresh PDF; its all clear and I think it can produce very nice results when selecting such options you discribed.

Its just that I'm not thinking very clear today(some grapes still stuck somewhere in my brains) so I will put some comment on that later. I realy have to evaluate the story again and produce some more thougths on all and give some more meaningfull reply..

I'm sorry MJ, I realy feel horrible today..

Feeling very guilty as well..

hi despichtt,

No problem. Better you skip today - get a rest. No point to struggle through and not be productive anyway.

Still didnt open MT4 for today; decided to first evaluate all options in the latest PDF..

----------------------------------------------------------------------------
Set1_STO_BLongMinShortMaxLevels: (Set1_STO_BeyondLongMinShortMaxLevels)
(e.g.: this difference from the above that we want to make sure for Long to be true it is below the LONG MIN level – like Spud's 100,3,3 Elastic.)

TASK is: check that all included TF within Set1 are beyond each defined Levels.
For LONG to be true: Stoch below Long_Minimum
For SHORT to be true: Stoch above Short_Maximum



Set1_STO_BLongMaxShortMinLevels: (Set1_STO_BeyondLongMaxShortMinLevels)
(e.g.: this difference from the above that we want to make sure for Long to be true it is above the LONG MAX level and not at the opposite side.)

TASK is: check that all included TF within Set1 are beyond each defined Levels.
For LONG to be true: Stoch above Long_Maximum
For SHORT to be true: Stoch below Short_Minimum

----------------------------------------------------------------------------------


This is where I'm thinking about for long now..
Parts of this can also be achieved by setting Long_Minimum values between [0,20](It's just that one would loose many other scenario's to scan for if this option didnt exist). Its a different mattar if you take into acount direction as well. Do these settings also validate values if not all pointing to the same direction?

Next thing one would like to know for elastic trading is the position of the fastest TF(lets asume 1min TF) if you exlude this line from SET. To put it simple: you would like to scan for situations where lets say 15Min is oversold AND 1Min comming from overbought. Its very unlikely the directions are the same for this two lines as this situation appears so thats complicating things a bit.
Perhaps if you choose these conditions and than add one of the Extra Stochastic line and put conditions to this line as well you could work around this. The Alerter than should be able to first evaluate the Set1_STO_BLongMinShortMaxLevels situation and than the conditions for the Extra Stochastics line. Not sure if this is possible to implement. Its probably a hard nut to crack.
Very complicated..

In some of this scenarios Sets will not be the right thing to use.

But we will have enough options for thing similar with the Extra Stochs.

E.g elastic like Spud. something like this: 100,3,3 Stoch oversold , 14,3,3 coming from overbought down.

with similar options as the sets we can do that nearly already.

Using 3 EXTRA stochs SAME TF: 100,3,3|14,3,3 and a second 14,3,3

*100,3,3 BLongMaxShortMinLevels = SHORT: 100,3,3 in oversold
*14,3,3 BLongMinShortMaxLevels = SHORT: 14,3,3 in overbought

Now we want a couple of extras:
100,3,3 should point also down and not following up the Fast Stoch:


*100,3,3 Stoch_Direction: means for SHORT: pointing down
14,3,3 Should also already pointing down even though it is in overbought area(for instance MAXLevel not to 80 but to 65 set so we do not get stucket in oberbought)
*14,3,3 Stoch_Direction

Now we use the second 14,3,3 to limit that the Stoch is not at 90 for instance
*14,3,3 WithinMinMaxLevels MAX 72



Something along this line: maybe I made some mistake did not really check this through - just some fast thoughts.


I had in my customary system also option for Reverse-direction (or opposite direction pointer) meaning (For a long check the stoch must point down) but not sure if we would need that - I forgot for what I used it.

E.g elastic like Spud. something like this: 100,3,3 Stoch oversold , 14,3,3 coming from overbought down.

with similar options as the sets we can do that nearly already.

Using 3 EXTRA stochs SAME TF: 100,3,3|14,3,3 and a second 14,3,3

A)
*100,3,3 BLongMaxShortMinLevels = SHORT: 100,3,3 in oversold
*14,3,3 BLongMinShortMaxLevels = SHORT: 14,3,3 in overbought
B)
Now we want a couple of extras:
100,3,3 should point also down and not following up the Fast Stoch:
*100,3,3 Stoch_Direction: means for SHORT: pointing down
14,3,3 Should also already pointing down even though it is in overbought area(for instance MAXLevel not to 80 but to 65 set so we do not get stucket in oberbought)
*14,3,3 Stoch_Direction
C)
Now we use the second 14,3,3 to limit that the Stoch is not at 90 for instance
*14,3,3 WithinMinMaxLevels MAX 72

So the option for Stoch_Direction B) would solve much of the problems!

The last Step: C) would than produce an Alert if all other conditions before have met and Stochastics realy coming down from overbought to give even more value to all evaluated before..

Good thinking!

MJ reply blue

So the option for Stoch_Direction B) would solve much of the problems!
The Stoch_Direction was always planned to be part (similar to the one of the whole set but for the individual Extra Stochs.
Just in the pdf I did not go so far - as I want you guys to think through some stuff you might need.


The last Step: C) would than produce an Alert if all other conditions before have met
Planned is for the simple version to check each enabled Task independently: when all agree to produce an Alert.


and Stochastics realy coming down from overbought to give even more value to all evaluated before..
Hopefully it really comes down: there is a small part missing (don't plan to add it at least not at this stage)
We do not know if the 14,3,3 ever when higher than 65-66 (as it must point down.)
In my old system I tracked such situations over time: Conditional task check if you like: First it must do that: after that it must do that..


Good thinking!

UPDATE

I did make some progress today but slow.

Anyway, you guys continue with your homework. Also test with extremes: e.g. Monthly with 200,50,50 or whatever - do really a thorough test: I don't want to run after crazy alerts not finding the solution because it lays on the base.

LAST VERSION of indi: http://www.forexfactory.com/showpost...&postcount=340

There are still 2 homework to finish: http://www.forexfactory.com/showpost...&postcount=326

UPDATE!

Still working - had to organise many things new as it becomes quite big.

Anyway if all goes well I hope in about 2 days to know more or less (At least basically) if what I plan might work out.

Still no task implemented.


BELOW some of what I thought incl. the Extra stoch: I plan to increase the number from 3 to 5.

Because it is anyway a lot of work: I'm trying with the config something I might want to use myself too. (Ignore them at the moment


//==== SET1 MTF-STOCHASTICS TASKs ==== (The leading S1 means SET1) e.g. SET1

S1_STO_Direction = "1N";
S1_STO_InMinMaxLevels = "2N";
S1_STO_OutMinMaxLevels = "0N";
S1_STO_OutLongMaxShortMinLevels = "0N";
S1_STO_OutLongMinShortMaxLevels = "0N";
S1_STO_AllInOrder = "0N";


//=== EXTRA-STOCHASTICS TASKs ====
e.g. Extra Stoch1

STO1_Direction = "0N";
STO1_InMinMaxLevels = "0N";
STO1_OutMinMaxLevels = "0N";
STO1_OutLongMaxShortMinLevels = "0N";
STO1_OutLongMinShortMaxLevels = "0N";
STO1_Leads_STO2 = "1N";
STO1_Leads_STO3 = "0N";
STO1_Leads_STO4 = "0N";
STO1_Leads_STO5 = "0N";
STO1_KMainAboveBelowDSignal = "0N";


Cheers


HOW does the testing go: no frozen PC? MTF STO/MA are plotting ok also with extreme data?

I've added all TF's Stochastics, some rope and also Colorbars on 5min chart. Not much of a moving average user but added some as well.

Note: I added 1min Colorbar on 5min chart. It didnt produce error but probably should!? At least some message probably like 'TF to short' like in the other Colorbars I used. Dont know what to think of it(same story for the 5min colorbar on the 15min TF). The color on the bar seems to be correct all the time though for the 5min colorbar on 15min TF!

Idid this for 6Futures for 5 and 15min charts. Something goes wrong on the H1 but probably my fault(used settings from 5min to integrate. I'm working to integrate the H1 as well.

No frozen PC yet for me..

I will give more feedback in a moment; also on the Action you wrote above..

MJ Blue response:

hi despichtt,

Thanks for checking this out.

I've added all TF's Stochastics, some rope and also Colorbars on 5min chart. Not much of a moving average user but added some as well.

Note: I added 1min Colorbar on 5min chart. It didnt produce error but probably should!?

YES. have to look at his.

At least some message probably like 'TF to short' like in the other Colorbars I used. Dont know what to think of it(same story for the 5min colorbar on the 15min TF).

By what you say I have probably forgot something by the ColorBar thanks.

The color on the bar seems to be correct all the time though for the 5min colorbar on 15min TF!

Not sure if I understand you: if you add a LOWER TF Color bar to a HIGH Period Chart the colors are still correct?

In general it should be - but because in extreme situation there isa problem I prefer to display it (what I might have forgotten when one switches to bars)



Idid this for 6Futures for 5 and 15min charts. Something goes wrong on the H1 but probably my fault(used settings from 5min to integrate. I'm working to integrate the H1 as well.

No frozen PC yet for me..

I will give more feedback in a moment; also on the Action you wrote above.

EXCELLENT.


BTW: the MA test are at least as important.

//=== EXTRA-STOCHASTICS TASKs ====
e.g. Extra Stoch1

STO1_Direction = "0N";
STO1_InMinMaxLevels = "0N";
STO1_OutMinMaxLevels = "0N";
STO1_OutLongMaxShortMinLevels = "0N";
STO1_OutLongMinShortMaxLevels = "0N";
STO1_Leads_STO2 = "1N";
STO1_Leads_STO3 = "0N";
STO1_Leads_STO4 = "0N";
STO1_Leads_STO5 = "0N";
STO1_KMainAboveBelowDSignal = "0N";

Dont know if possible but would be nice to also add:
STO2_Leads_STO3 = "0N";
STO2_Leads_STO4 = "0N";
STO3_Leads_STO4 = "0N";
STO2_Leads_STO5 = "0N";
STO3_Leads_STO5 = "0N";
STO4_Leads_STO5 = "0N";

I have written down many scenario's and try to imagine how to implement in the current version(like you wrote down in PDF and above); most of them already qualify!

Will report more on this as well..

Thanks: Found the problem.

I only checked for Lower TF when onAlerts where enabled.

I ATTACH TWO corrected STOCHS

(but leave the version number the same: in that way you do not have to do any template new. Just close MT4 delete the old indi and drop the corrected on into the folder.)

Keep me updated and Thanks - good work.

despichtt

Dont know if possible but would be nice to also add:
STO2_Leads_STO3 = "0N";
STO2_Leads_STO4 = "0N";
STO3_Leads_STO4 = "0N";
STO2_Leads_STO5 = "0N";
STO3_Leads_STO5 = "0N";
STO4_Leads_STO5 = "0N";

I have written down many scenario's and try to imagine how to implement in the current version(like you wrote down in PDF and above); most of them already qualify!

Will report more on this as well..

MJ:

THANKS for the thought:

I have did that already before (by the other stochs but did not post it here)

We are on the same page: because it's not finishing and might still change I did not attach the current pdf. (don't want to confuse you guys more than necessary

here it goes: Alerter_Tasks_proccess_20110329.pdf

Not sure if I understand you: if you add a LOWER TF Color bar to a HIGH Period Chart the colors are still correct?
Yes the color from 5min colorbar on the 15min chart is correct though. I think its better to give the alert: like TF to small(like in the other versions)..

BTW: the MA test are at least as important.

I will add MTF for this as well(not used to do this much).
Fixed also H1; also for all Futures. Still no freeze..

I'm going out for diner again and will add more futures for testing when she goes to bed!

Yes the color from 5min colorbar on the 15min chart is correct though. I think its better to give the alert: like TF to small(like in the other versions)..

MJ: YES: it will be even more important with the Alerter , as we don't plot any lines or Color bars representing a indi: but just alerts.
I will change that in the alerter immediately too. Thanks.

replace the existing indies with the two attached in the previous post: should work without you having to change any template.

hi despichtt,

Excellent exercise: even though some parts my still change a bit: but still slowly we are getting somewhere.

Maybe you could post some of those examples (Even simple ones and explain your thinking. that might trigger some ideas too.

If the Alerter should really work out (not sure yet) I thought it would be nice if the guys who use it write a couple of such scenarios/the thinking of how to configure the alerter... maybe we can in the end come up with a kind of 'Alerter for dummies pdf.

Also start then a simple template collection with such scenarios - in that way it may help others who come after us but is also helpful for ourself. Easier to change an existing base template with a pdf which explains what's all about.

Just some thoughts.

Had an idea:
so I will rewrite much of the code (already too big couple of thousand lines) to keep it cleaner and also for possible future addition more extensible.

So, not sure if I come today to a first task implementation.

Good day to you guys.


UNRELATED: when I first learned about forexfactory I mainly joined because I got interested in this thread: http://www.forexfactory.com/showthread.php?t=123284
but never really read it through as somehow I got stuck with Spud's.

Maybe you could post some of those examples (Even simple ones and explain your thinking. that might trigger some ideas too.

If the Alerter should really work out (not sure yet) I thought it would be nice if the guys who use it write a couple of such scenarios/the thinking of how to configure the alerter... maybe we can in the end come up with a kind of 'Alerter for dummies pdf.

Yes, I will do exactly that. I'm making screenshots with the situations I like to scan for! Than publish them in this thread..

Also start then a simple template collection with such scenarios - in that way it may help others who come after us but is also helpful for ourself. Easier to change an existing base template with a pdf which explains what's all about.

Thats a very good idea as well!

You adressed this issue from lower TF quite well in the latest Indicators! I should have known this replacement for indicators before.. Just delete the old one and give the same name to the new one; very clever!

I'm studying rigth now on this PDF.

I wont trade today anyway; do some more testing as well as its getting very advanced all together in these Indicators..

Good idea:

There will be slight changes you know: actually I have started from scratch: cleaning things up more nicely : got a bit messy.

Anyway the basic ideas will mostly stay - so it's worthy to look at it. Note: not not all tasks can used tracking.

But internally I have decided to go a different way of doing thing: for instance the whole set enable will be removed all internally - so Ihope the config will be less error prone.

I just add the info code for it I don't bother to remove the code part.:
extern string ________READ_INFO________ = "<<< READ INFO >>>";
extern string __read1__ = "BELOW: UserInputOption StartWith";
extern string __read1a__ = "a lower letter.";
extern string __read2__ = "-----------------------------";
extern string __read2a__ = "IMPORTEN Abbreviation:";
extern string __read2b__ = "STO=Stochastic,MA=MovingAverage";
extern string __read2c__ = "RealPrice=Bid Price";
extern string __read2d__ = "FRA=Fractials,ZIG=ZigZag";
extern string __read2e__ = "ATR=Average True Range";
extern string __read3__ = "-----------------------------";
extern string __read3a__ = "TASKS: ConfigString have 2 chars!";
extern string __read3b__ = "1. PriorityGrp:Number: 1-3";
extern string __read3c__ = " 0= Deactivates individual Task";
extern string __read3d__ = "2. TrackingOption: N or Y";
extern string __read3e__ = " ONLYSomeTasksCanUseTraking";
extern string __read3f__ = "e.g.TaskConf: sWhateverTask = 1N";
extern string __read4__ = "-----------------------------";
extern string __read4a__ = "ForATaskToWorkItMustBeActivated";
extern string __read4c__ = "1. Individual Task";
extern string __read4d__ = "2. Taks Related/Needed Resources";
extern string __read4e__ = " e.g. IndividualIndicators";
extern string __read4f__ = " (STO1,MTFSet1STO1, RealPrice etc.)";
extern string __read4g__ = " some Tasks need multiple Resources";


I guess I will make a demo version with only the 5 Extra Sto - so you guys can play a bit and see if the concept works.

Also the Tasks I posted in the lastpdf will stay (slightly renamed) so you can think about scenarios already.