Making JH' SCT and all his material alive

That's what I have :

Ag VEBO

No typo.

You are tooling along.

You get to P2 one way or another (carte blanche).....

Check out that P2 is > P1.

So after P2 consider seeing a P1 or a T2P.

IF a P1 then designate the bar as Ag VEBO.

This could be a bar where a UL is "on the row". Just saying.....

Af HVBO

This is the old A2 of long ago.

You are in a lat. You are getting the job done.

Suddenly a HVBO occurs in the lat after you have the P1 to T1 to P2 in the lat.

What you see is what you get; designate it as Af HVBO.



DD and dissection time.

Ag VEBO
- VEBO stands for Volatility Expansion Break Out
- You get to P2 one way or another (carte blanche)..... : easy for me cause for once, carte blanche is in my native language ! So I get to P2 one way or another...so Wait and UL along the line does NOT kill Ag. I can also have several P1's and T1's unless it triggers another A-band EE. So far good.
- Check out that P2 is > P1 : Crystal clear, we need P2 above leftmost P1 level. And, according to the handwritten version of A-band EE's sheet, Ag is killed in Lat only
- So after P2 consider seeing a P1 or a T2P : effectively, after P2 according to the VERS, one can either (if the volume element is only a volume element and not also a EE), P1 is gated if superior to prior P1 (=last measured) and T2P is gated if bar.0 is under P2 and above T1.

NB : I have to remind that lastly, you IDd a T2P after a P2 on a bar (subsequent to P2 that was below it and that was above T1 leftmost) AND while the given P2 was above P1 AND while the bar.0 was both in between P2 and T1 and above P1. I said that in this case, I'd see an Ag VEBO due to the fact that : P2 > P1 AND the bar.0 is just after P2 AND this bar.0, although it satisfies T2P condition, is above last measured P1, which was P1 leftmost in this case. Being as I know P1 can follow a P2 if it exceeds prior P1 AND being as in this case the prior P1 is the first and only one, THEN I see this bar as a bar just after P2, which is a new P1 by being above prior one, with P2>P1, so I see everything lining up with Ag VEBO definition.


- IF a P1 then designate the bar as Ag VEBO. How can one have a P1 after P2 ? according to the litterature and the VERS, P1 can follow a P2 if it exceeds prior P1. Then what if there are several P1's initiating the sequence ? we use the leftmost, the first one so to speak. And what if there is only one P1 ? even more easy, it is the reference. The reference for what ? for ID a new P1 after P2. According to the VERS, for a P1 revchron, what do we need compared to last P1 IDd ? It's is revchron column, new new, it says >=. So a bar after P2 exceeding prior P1 is (P1revchron) OR (it is P1revchron AND a given EE"). In the case we discuss, it's question of a bar being another P1 after P2, so it can only be a P1 revchron cause P2 happens after P1 AND we have P2 > P1 AND we're not in a Lat cause we know from A-band sheet Ag is killed in Lat only.

- This could be a bar where a UL is "on the row". Just saying..... : this means a UL can be on the line. In addition to that, we can add : this could be a bar where a UL and/or a wait is on the line, thanks to the A-band sheet.


Af HVBO

- This is the old A2 of long ago : we know JH changed some of the names of the EE's along time. Fine.
- You are in a lat. : So Af can only appear in a Lat.
- You are getting the job done : we hope so ^^
- Suddenly a HVBO occurs in the lat after you have the P1 to T1 to P2 in the lat : fortunately, confusion is avoided here as it is clearly said that (BOTH P1-T1-P2 must appear IN THE LAT) AND (the HVBO must occur IN THE LAT).
- What you see is what you get; designate it as Af HVBO : ok ^^^
- additional : on the handwritten version of the A-band sheet, the AddReq cell is empty. BUT I have noted, in my old binder where I had handwritten all the EE's texts, that Af needs P2 > P1. I can't find back why I put this. BUt I know there must be a reason why. With that said, even though this annotated info on my personal notes, I don't see in the present text anything preventing in fact.... P2 to be anywhere compared to P1. If you say P2 must be below P1 for Af, there must be a reason why too, but I don't find it in THIS text, netiher in the text, nor between the lines. There must be another text you have used for this DD AND/OR this must come from a DD from another EE which makes Af in need of P2 < P1 in order to be.


My DD is then :

- to have Ag VEBO
a) we need the trend to have progressed until P2
b) we need this P2 to be above P1
c) the IDd bar as Ag VEBO can't be in a Lat although P1-carte blanche-P2 can be in a Lat. That's what is contained into "carte blanche" AND what is explicitely defined in the A-band sheet with "Kill in Lat only". The "carte blanche" precision contains the possibility of having the pre-sequence before Ag (so until P2 in a way or another), and when coupled with "Kill in lat only", then any possibility of having THE Ag VEBO bar in Lat is impossible.
d) we can have a wait (info from the sheet) and we an have a UL (info from the litteratureà) along the line and we can have the Ag bar on a UL

Therefore finally, if all these conditions are present, then after P2 :
- either the bar is above P1 leftmost : Ag VEBO
- either the bar is between P1 and T1 : T2P
- either the bar is under T1 : Ab LVBO

- to have Af HVBO
a) both the sequence leading to P2 MUST be in the Lat AND so must be the HVBO bar
b) UL/WAIT can happen, no kill
c) the relative position of P2 compared to P1 is :
- for my old notes, it must be P2 > P1
- for you, it must be P2 < P1
- for my current DD : I don't know. I can't find again why I put this condition some months ago.
Correction/additional : in c) of my DD for Ag VEBO : The "carte blanche" precision contains the possibility of having the pre-sequence before Ag in a LAT
 
I'll compare with what I've done and see if my comments are congruents with my own voew of the day.

I have not logged nor annotated the day prior to 10/22/19 so we do not have the same beginning. Fine.
After comparison, I see, except concerning the Lat I did not see as long a you did, we have the same IDs kind of 80-90% of the time.

Planning on do an hindsight log today and add a bit more of oil to my journey in 20min.

NB : I won't have the possibility to add the tri pane charts as I'm not home and the screen I have for working is kind of...very little compared to what I'm used to AND I only have one, whereas I normally have two ones. No big deal, next week I'll add the necessary.
 
Market is opening soon. In order to have a beginning of a path, I just IDd by some guess for the first OD, the end of prior day in order to do the carryover.
 

Attachments

  • for carryover.png
    for carryover.png
    33.9 KB · Views: 22
Market is opening soon. In order to have a beginning of a path, I just IDd by some guess for the first OD, the end of prior day in order to do the carryover.

How this looks so far

NB : some things appear on the chart as anticipation (for ex the BO,T1 coupled with next turn that will be b-turn no matter what)
 

Attachments

  • step1.png
    step1.png
    335.9 KB · Views: 21
Step3

Edit : of course, typo on last a-turn : Set is C and not A.
 

Attachments

  • step3.png
    step3.png
    171.3 KB · Views: 19
Last edited:
Have to go. Full view is there with associated log.

Doing this has been fantastic..
 

Attachments

  • better view step1.png
    better view step1.png
    80 KB · Views: 18
  • better view steps2-3-4.png
    better view steps2-3-4.png
    128.9 KB · Views: 18
  • Log1.jpg
    Log1.jpg
    895.6 KB · Views: 18
  • Log 2.jpg
    Log 2.jpg
    242.8 KB · Views: 18
Step5 (bar 25 to 36 had to be made in hindsight)

Again, have to go, see you tomorrow
 

Attachments

  • step5.png
    step5.png
    227.9 KB · Views: 16
38th session of MADA, almost half made in real-time, 10/22/19- 43 EE's
 

Attachments

  • ES1! 102419 EOB 1.png
    ES1! 102419 EOB 1.png
    168.5 KB · Views: 14
  • ES1! 102419 EOB 2.png
    ES1! 102419 EOB 2.png
    226.4 KB · Views: 13
  • ES1! 102419 EOB 3.png
    ES1! 102419 EOB 3.png
    212 KB · Views: 13
  • ES1! 102419 EOB 4.png
    ES1! 102419 EOB 4.png
    141.3 KB · Views: 13
Back
Top