Scalping

[superfly]

Chart Time Update Interval

Versus:
-frequency of trades in specific instrument
-personal comfortibale reactionspeed
-entry strat, (trail) stop strat
-available cpu

Thinking about it, I can live comfortly with 2 Chart updates every second.

How many:
-chart udates do you have in your timeframe?
-do you need?

 

[superfly]

Millisecond
http://www.thefreedictionary.com/millisecond

So I want to update my chart every 500 millisecond = 0.5 second.

 

[p-lab]

Whilst I entertained enough interest to open the thread, I swiftly lost interest with the content😕

 

[dcraig1]

Chart Time Update Interval

Versus:
-frequency of trades in specific instrument
-personal comfortibale reactionspeed
-entry strat, (trail) stop strat
-available cpu

Thinking about it, I can live comfortly with 2 Chart updates every second.

How many:
-chart udates do you have in your timeframe?
-do you need?

I wrote my own charting software. There is no provision for setting update frequency because charts are updated every tick. Even in fast markets, on four screens, modest graphics cards (NVS285), a quad core Q9550 is still 70% or more idle. Data feed is IB for futures and DTN IQ for stocks. Code is all Java.

Technically the trick is to repaint last bar only per tick and only update whole chart on the open of a new bar.

With modern CPUs and graphics hardware, there is no excuse for two updates per second etc etc. Vendors should fix their software. If they can't or won't, find another vendor.

Price ladder doms are likely to be more CPU intensive than charts.

 

[superfly]

reopend for pure accountability purpose. i may use this i may not, just in case.
my scalping system has a nonnegotiatable basis, and here i will only report on a daily in what degree i achieved that goal.

Goal​	Focus Area​	Action​	Criteria to Progress after Review with C​	Estimated Time​	End Day​
1	A. Foundation	Achieve 95% accuracy in Phase A (min. 200 trades).	95% accuracy with 200 trades	10-20 days	Day 10

 

[superfly]

The stat rates compliancy to risk , trading hours,, News timing, Phase patern and Pukelevel after noise.
To achieve the 95% acccuraty i cant make more then 10 errors, so as soon as i hit 10 errors under the 200 trades Ill start reviewing anew and set the numer of tdaes back to 0. ill report the following format(dummy numbers for now):
date | cummulativetrades | accuratetrade| %
jan-6| 50 | 49 | 98%

 

[ChelseaR]

The stat rates compliancy to risk , trading hours,, News timing, Phase patern and Pukelevel after noise.
To achieve the 95% acccuraty i cant make more then 10 errors, so as soon as i hit 10 errors under the 200 trades Ill start reviewing anew and set the numer of tdaes back to 0. ill report the following format(dummy numbers for now):
date | cummulativetrades | accuratetrade| %
jan-6| 50 | 49 | 98%

I like how you are tracking the number of errors and revisiting them. Have you found any specific pattern that tends to cause those errors?

 

[Simon54]

The stat rates compliancy to risk , trading hours,, News timing, Phase patern and Pukelevel after noise.
To achieve the 95% acccuraty i cant make more then 10 errors, so as soon as i hit 10 errors under the 200 trades Ill start reviewing anew and set the numer of tdaes back to 0. ill report the following format(dummy numbers for now):
date | cummulativetrades | accuratetrade| %
jan-6| 50 | 49 | 98%

nice! how do you fix those error or spot them while review?

 

[superfly]

to make the 200 realistic I now investigate the main and repeated errors, The biggest barrière is to detach enough to create space to make the review before entering, that is the biggest insight till now. I will report back when I have defined and fixed these issues so that I can reach 20 with max. of 1 error. what has to be true for every trade, but all those items have precedents, so I am busy diving into the market-related parts, to not only come up with an accuracy of 95%, but also improve the quality and efficiency of my process, and the probability and potential. yes a mouth full, but that is not the problem. The problem is what has to be true always and what are the precedents of that? A part I'm very graciously happy about is that I know exactly what part is rule-based and what part is discretionary/more fluid.

 

[ChelseaR]

to make the 200 realistic I now investigate the main and repeated errors, The biggest barrière is to detach enough to create space to make the review before entering, that is the biggest insight till now. I will report back when I have defined and fixed these issues so that I can reach 20 with max. of 1 error. what has to be true for every trade, but all those items have precedents, so I am busy diving into the market-related parts, to not only come up with an accuracy of 95%, but also improve the quality and efficiency of my process, and the probability and potential. yes a mouth full, but that is not the problem. The problem is what has to be true always and what are the precedents of that? A part I'm very graciously happy about is that I know exactly what part is rule-based and what part is discretionary/more fluid.

Understood, thanks

 

[Simon54]

to make the 200 realistic I now investigate the main and repeated errors, The biggest barrière is to detach enough to create space to make the review before entering, that is the biggest insight till now. I will report back when I have defined and fixed these issues so that I can reach 20 with max. of 1 error. what has to be true for every trade, but all those items have precedents, so I am busy diving into the market-related parts, to not only come up with an accuracy of 95%, but also improve the quality and efficiency of my process, and the probability and potential. yes a mouth full, but that is not the problem. The problem is what has to be true always and what are the precedents of that? A part I'm very graciously happy about is that I know exactly what part is rule-based and what part is discretionary/more fluid.

Sounds like a pro approach! How you balanced the rule based part with discretionary side?