Good morning{image}
Can you please upload this template ?
Regards
Sarju
csDash (currency strength meter)
- #222
- Jun 14, 2015 9:53am Jun 14, 2015 9:53am
- Joined Nov 2014 | Status: Trader | 1,300 Posts
Just to clarify - is the current forming bar included in the eg. 24?
Does the circled pairs with incomplet B/R means it is still forming/not enough data yet? (I have H4 + 6 in example) Pls advise
Hope that helps
- #223
- Jun 14, 2015 9:54am Jun 14, 2015 9:54am
- Joined Nov 2014 | Status: Trader | 1,300 Posts
{quote}
- #225
- Jun 15, 2015 12:43am Jun 15, 2015 12:43am
- Joined Jul 2010 | Status: Great hopes make great men | 2,042 Posts
Low Risk Low Stress High Reward High Probability Trades
- #228
- Jun 18, 2015 6:14am Jun 18, 2015 6:14am
- Joined Nov 2014 | Status: Trader | 1,300 Posts
Timeframt to calculation = Base of the DB for the strength calculation Chart timeframe = Timeframe of the chart for to open when you click on the pair name inside the DB
- #229
- Jun 18, 2015 6:31am Jun 18, 2015 6:31am
- Joined Nov 2014 | Status: Trader | 1,300 Posts
So, I've finally got around to implementing some experimental code to enhance the alerting process.
Why? The problem with alerts is that whenever a value hangs around an alert threshold (rather than moving clearly one way or the other) you get multiple triggers in close succession. These multiple alerts can create the impression that you are getting a really strong signal, but the reality is the opposite: you are getting a very marginal signal.
Consider the following example (differential threshold is 4.0):
csDash previously used a time delay of 1 minute between alerts. It is a crude mechanism based on the theory that things will move on and settle away from the threshold in the intervening minute. Doesn't always happen though.
I've now coded a new method to reduce the number of repeat alerts. The only user settings is Trigger Sensitivity:
At its highest setting, it works as per the example above. At its lowest setting, you will get very few repeat alerts (please note: sensitivity never affects the first alert).
If you want to play with this new feature, please feel free and report back any bugs
Why? The problem with alerts is that whenever a value hangs around an alert threshold (rather than moving clearly one way or the other) you get multiple triggers in close succession. These multiple alerts can create the impression that you are getting a really strong signal, but the reality is the opposite: you are getting a very marginal signal.
Consider the following example (differential threshold is 4.0):
3.8
3.9
4.0 ALERT!
4.1
4.0
3.9
4.0 ALERT!
3.9
4.0 ALERT!
3.9
3.9
4.0 ALERT!
csDash previously used a time delay of 1 minute between alerts. It is a crude mechanism based on the theory that things will move on and settle away from the threshold in the intervening minute. Doesn't always happen though.
I've now coded a new method to reduce the number of repeat alerts. The only user settings is Trigger Sensitivity:
At its highest setting, it works as per the example above. At its lowest setting, you will get very few repeat alerts (please note: sensitivity never affects the first alert).
If you want to play with this new feature, please feel free and report back any bugs
- #230
- Jun 18, 2015 6:36am Jun 18, 2015 6:36am
- Joined Jul 2010 | Status: Great hopes make great men | 2,042 Posts
Always thoughtful and outstanding additions Good job Captain 
Good job Captain Low Risk Low Stress High Reward High Probability Trades
- #232
- Jun 18, 2015 11:12am Jun 18, 2015 11:12am
- Joined Nov 2014 | Status: Trader | 1,300 Posts
Always thoughtful and outstanding additions
- #236
- Jun 18, 2015 3:46pm Jun 18, 2015 3:46pm
- Joined Nov 2014 | Status: Trader | 1,300 Posts
{quote} THANK YOU Dan
{quote} THANKS - Have to figure out all the uses with all the permutations!! Just a quick look. {image}
- #237
- Jun 18, 2015 3:47pm Jun 18, 2015 3:47pm
- Joined Nov 2014 | Status: Trader | 1,300 Posts
Hello, Thank you Honest for all of the improvements. You are doing wonderful work. I have been playing around with rolling time frames and would like to share my progress. The attempt is to calculate bars back based on time to account for missing bars and weekends. This is based on an existing CSM with alerts. All credit is due to the previous developers. I am a beginning coder so no guarantees are being extended. Any feedback, suggestion or improvements will be welcomed. I would like it if anyone can help me make multiple indies for different time...
- #240
- Jun 19, 2015 1:55am Jun 19, 2015 1:55am
- Joined Nov 2014 | Status: Trader | 1,300 Posts
Thank you Honestknave. Your csDash indicator is excellent. I like the latest change with the rolling time frame so the relative strength appears stable over a given time period.