Oh well, I suck! Trader slang, I suppose. I am though interested in exploring your ideas a bit more when I'm venture into building more automation into my methodology.
K,... I don't suck that bad! The cliff notes: Current Read Short BTC in intermediate trend, looking for advanced profit-taking in a retrace. The retrace would become a reversal long when the current short trend line is broken. We are in any area where support entered during the beginning of August. This change event is anticipated within the next two bars. The fake-out would be a penetration of the line slope but a bar close below the line and price declining with decreased pace. Bar-by-bar trading is informationally dense and requires a notational language.
Funny how you would by 1 Bitcoin for say $4875 with real cash, real fiat to use to buy other goods and services...now why would anyone buy a virtual currency that could be worth $4875 one day $5189 the next and a week later worth $3475??? Again it's a virtual currency that some dude or dudes invented only some years ago....it was created out of thin air...
No, still nothing. However if you can write down the precise algo for this stuff I'm happy to code it up for you and test if it actually works Grateful, but happy to remain ignorant, GAT
Great! The first algo that is easy to test and see results is for Pro-Rated Volume. In a 5min bar (or any timeframe), having a tool that measures the current transactional pace within that timeframe. This would show a graphical representation of a bar's forecasted end of bar volume if it were to continue at it's current volume pace. Here's a pic of a tool with a specialized library that I don't have access to modify nor extend. I have the algo for it. My goal is to utilize existing python frameworks or platforms. Simply to make it web-based. Specifically, if in the first 5sec of the bar if the transactional volume was 2k, then the forecasted EOB volume histogram height would be 10k. If by the 4min, no other transactions occurred during the bar, the bar's PRV (yellow highlight) would be 2500 (2k/4min current pace = 500contract/min). This pace is a reduction of the 1st min bar pace which was 2k/min. Why would this tool be useful? If volume is the leading indicator of price, then the PRV tool would demonstrate the change in price direction from intrabar changes in volume pace which results in the resulting End of Bar volume histogram height. The next would be to code the Ten Price Cases by which to determine when to measure the volume parameter. Why not just use the software above? I could, but Trade Navigator isn't supported by my current broker Why not just diy? Definitely happening so if you're not inspired, helpful support while I learn python would be great! If the methodology works why not just hire someone to write it? Good point, at the appropriate time, I'd prolly write it before shopping it out just to learn something new. I'm more a get-my-hands-dirty kinda of guy vs taking it to the dealership kinda guy. But the idea of open-sourcing software is something I could get into.
Me neither but looks like this to me: : When everyone says something should go up and it's not going up, ... chances are it'll go down. (and vice versa too)
We have a C-turn. Dominant Shift. Moment of go/no-go early long, next bar inside bar or XB unless volume pace keeps increasing. If so then short trend still not complete and XR.