Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
futures.io (formerly BMT) also makes available it's GoToWebinar professional webinar system with 500 room capacity to any Elite member who has a good use for it, and it can also be recorded and shared.
CJ,
On the chart below I noted the higher low with an arrow and also the higher high. At what point on the 1508
chart would you start looking for a long trade on the 377 chart?
Thanks
The moment PRICE not the ZigZag or any other indicator touches the top of the MA or cloud you begin to evaluate the 377 for a POTENTIAL trade. Then right before you pull the trigger look at the 1508 real quick to make sure the support is holding -.
Hi Charles, i would like to know since we have time, if you make a difference when we have a HH on the 1508 preceded by a LL versus a HH preceeded by a HL. I know your rule is to wait for a HH on the 1508 nothing more but i was wondering if it makes a difference in your evaluation of the context. In my mind, consecutive HL, HH is more strong than consecutive LL, HH.
Here is an example of what i am talking about using one of your screen capture. This is a trade that failed. Here we have a LL preceding a HH.
What was the reason why you did not enter on the first red bar that closed below the cloud on the 377 ticks chart between points #2-3. Was it only a question of risk too big ?
I think I remember this day, you reference that LL just before the HH that then gave a failed HL trade. Look at the LL you mention - it sure looks like an ABCD retrace and if it was then that is a powerful trade. If i remember this day correctly indeed it was an ABCD
ABCD will have you trading a LL in an uptrend or HH in a downtrend but the calculation of it would need to be correct
I do believe the post itself answers your question - point 2 made a HH and Stochastic did as well - there was a standard divergence between points 1 & 3
Yes i understand the ABCD but this is not what i am talking about. If you look at the three green arrows, where you entered, the HH was preceded by a Lower Low. Whether or not it was a valid ABCD or not is not important as i am talking about the pullback that occured after the HH. For one thing, this HH was preceded by a LL but also the pullback on the 1508 never hit the MA or cloud which is one of your condition. Anyway, my point was that i think a series of consecutive LL, HH, pullback to MA seems less strong than a series of consecutive HL HH, pullback to MA since by definition a healthy uptrend should show HL HHHL and not LL HH HL. Maybe i am thinking too hard
Iono bout all that, but I'm doing some SIM replays, and I swear, everyone of the losses I'm trading are the ones where price actually pulls back INTO the cloud. The better ones stop short of it, or barely kiss the cloud.
The rules do say that the zigzag should be above/below, but I didn't know how literal to be with that.
If you can post a chart where you have a losing trade after the retrace comes inside the cloud. This would make it easier to respond to your comment
There are some good trades that occur from inside the cloud, on the other hand when price comes inside the cloud from above it means price has broken support and the top of the cloud becomes resistance so if you take a trade then you need price to break that resistance or close the trade at any sign of rejection at it
Keep in mind also that when price has broken support by coming inside it from above that the bottom of the cloud is also support.
