10.7/10.9 INDI SOLUTIONS

Post by **slowkey** » Wed Apr 30, 2014 2:39 am

Tommaso,

You really made it easy to change these setting so I changed the htf to 240 and htf2 to 1440 and will start testing these for the 15 minutes. Also the 5 minute.

new indicator.png

Doug

James Roscoe · Post by **James Roscoe** » Wed Apr 30, 2014 5:15 am

spider x, what are the diamonds next to the trend mean? I looked around but did not find an answer to this. You r dashboard is a great time saver, so thanks for your efforts!

Post by **SpiderX** » Wed Apr 30, 2014 5:21 am

James Roscoe » Wed Apr 30, 2014 1:15 pm wrote:spider x, what are the diamonds next to the trend mean? I looked around but did not find an answer to this. You r dashboard is a great time saver, so thanks for your efforts!

Hi,

That is legacy stuff from 10.6 dashboard....will need to dig the code to see what the diamond does.

Cheers

James Roscoe · Post by **James Roscoe** » Wed Apr 30, 2014 5:50 am

SpiderX » Tue Apr 29, 2014 11:21 pm wrote:
James Roscoe » Wed Apr 30, 2014 1:15 pm wrote:spider x, what are the diamonds next to the trend mean? I looked around but did not find an answer to this. You r dashboard is a great time saver, so thanks for your efforts!

Hi,

That is legacy stuff from 10.6 dashboard....will need to dig the code to see what the diamond does.

Cheers

You don't have to do that. If that is 10.6 stuff that diamond means that both dummy lights from that system are lined up. So what you have done is made a dashboard that helps with 10.6-10.9.

Thanks for the quick reply!

Post by **dclayw** » Wed Apr 30, 2014 2:30 pm

alorente » Wed Apr 30, 2014 12:42 am wrote: First and foremost, I would only pick one TF Sto. I am using H1 Sto right now for a quicker exit and more trades per day. Exit the trade as soon as the Sto arrow changes direction. For example in my case in a Buy, as soon as the H1 Sto arrow turns white. Once you settle on your TF, remove the other TFs from the dashboard. When you have only one TF showing, you can leave the white numbers on. They help you see how close you are to a pair color change.

All good points. I've been trading mostly the H1, sometimes the M15 and keeping tabs on the H4, just for screen time to see how this thing works. I'll take your advice and concentrate on single TF, certainly reduces the clutter.

I would not implement CSS in the dashboard. It is way too complicated and it takes 3 seconds to check the 3 TFs on the CSS to make sure they align. What I do is, as long as they point in the correct direction OR are more or less parallel in all 3, I pull the trigger.

I think I would find a simplistic implementation of the CSS into the dashboard useful. By simplistic I mean just the relative levels on the CSS, (the relative levels being the most basic and probably most important information provided by the CSS, and the easiest to automate I expect) e.g. if AUD is higher then EUR than AUD is stronger and bias is to buy it. While it doesn't take long to check that on the CSS, if there are several signals all firing at once I tend to get a bit lost (signal pairs turn back to yellow), so I think I'd find the automation of that CSS level check useful.

Post by **SpiderX** » Wed Apr 30, 2014 2:36 pm

dclayw » Wed Apr 30, 2014 10:30 pm wrote: I think I would find a simplistic implementation of the CSS into the dashboard useful. By simplistic I mean just the relative levels on the CSS, (the relative levels being the most basic and probably most important information provided by the CSS, and the easiest to automate I expect) e.g. if AUD is higher then EUR than AUD is stronger and bias is to buy it. While it doesn't take long to check that on the CSS, if there are several signals all firing at once I tend to get a bit lost (signal pairs turn back to yellow), so I think I'd find the automation of that CSS level check useful.

imo, for those who think CSS reading can be automated...
Try running the CSS indicator on a few pairs with the option of showOnlySymbol on chart.
Try to backtest your CSS reading logic a few months back and see if it can be automated with simple rules.
Backtesting is one thing, the other thing is you have to see how much the CSS indicator varies in live situation.

If after testing out all the above stuff, and you have found reliable rules to automate the reading of CSS...
please share with us here.

Cheers

Dovilo · Post by **Dovilo** » Wed Apr 30, 2014 4:24 pm

AutoCSS
New version v1.1 features:
- Strong Parametr that separates additionaly weak moves from strong ones.
- User can now choose colours of moves.
- Bullets indicating oversold/overbought currencies on selected timeframes.

Next edition will feature alerts.

What do you guys think? Any ideas or spotted bugs? Let me know.

Post by **slowkey** » Wed Apr 30, 2014 6:12 pm

imo, for those who think CSS reading can be automated...
Try running the CSS indicator on a few pairs with the option of showOnlySymbol on chart.
Try to backtest your CSS reading logic a few months back and see if it can be automated with simple rules.
Backtesting is one thing, the other thing is you have to see how much the CSS indicator varies in live situation.

If after testing out all the above stuff, and you have found reliable rules to automate the reading of CSS...
please share with us here.

Cheers

Totally agree with that thought SpiderX ...

I tried two times in my systems to use CSS on a pair as part of a manual entry and exit tool. Exits were impossible and entries made difficult by a lack of being able to determine a threshold that would work consistently in every time period. I gave up on entries switching to a stochastic when I realized that the only time periods I could get consistent entries on was the four hour. Than Bobs 10.7 indicator came out and it was an easy move from the stochastic to his super stochastic. CSS is fabulous as an analysis tool just not as a market timing indicator.

Cheers,
Doug

Dovilo · Post by **Dovilo** » Wed Apr 30, 2014 6:28 pm

SpiderX » Wed Apr 30, 2014 2:36 pm wrote:
imo, for those who think CSS reading can be automated...
Try running the CSS indicator on a few pairs with the option of showOnlySymbol on chart.
Try to backtest your CSS reading logic a few months back and see if it can be automated with simple rules.
Backtesting is one thing, the other thing is you have to see how much the CSS indicator varies in live situation.

If after testing out all the above stuff, and you have found reliable rules to automate the reading of CSS...
please share with us here.

Cheers

I don't actually see a problem, automatic CSS reading can tell what currency is doing now on different tfs almost as well as human. We don't know what price will do next either for example if changing direction of slope is only a quick retracment or is it a direction changing move. Of course I would not reliable on CSS only (even if this is a great indicator) or dare to make EA using only this (though I think it is possible, just too difficult for me, at least for now

).

Post by **padnoter** » Wed Apr 30, 2014 8:21 pm

Nice work Dovilo.

It's an interesting idea... look forward to seeing where this takes us as it develops.

At the moment I find it a bit confusing with the array of colours & meanings. Maybe some arrows might help?
or some indicators as to when different timeframes line up (if that could be important?).

I can see when you've fixed the currency names in order (for comparison across tf), but then we lose easy sight of strongest/weakest currencies we had when they were ordered by value. Tricky.

You could certainly remove the redundant currency names if they stay in that fixed order. Don't need four "USD" literals.

Maybe some other indicator to show value strength for easy eyeballing. A range of diff' sized red/green circles?

Not sure how to use it in live trading yet, but I'm sure there is something in strong css values/slopes on H4 & D1, and weak on H1/M15 i.e. pullback in trend.

But I like it. Thanks.

Cheers
Padnoter