Fractal Theory: Redux

[frenchfry]

Volume test procedure (by JH)

a three part OOE is used to test volume to obtain the bar volume name.

This has to be done precisely and exactly as stated here.

when permission is given and suppression is lifted (this is a comment to coders), then the following tests are preformed.

1. test for a repeat is performed,

2. if there is NO repeat, then a Rev Chron test is performed,

3. If there is NO rev chron, then the NEXT is assigned.
………………………..
Testing has two answers:

True or False. Fortunately, each is unique and each never overlaps the other. As answers, they are mutually exclusive. So that is that.

If you are getting true of false, you have made the progress required to be a winner. If not, then you are still a whinner. Whinners look for things that they invent as going wrong.

So now you have learned what to fill in all the cells of the volume testing part of the log.

The purpose and process of testing is to get all FALSES because that states that you have finished a trend no matter what type.

Since this is so simple, you will need more help to be able to do it correctly.

1. To begin the test procedure, go to the starting point and make a dot in the upper right corner of the appropriate cell.

2. Find the appropriate cell by using the last T in the row above and drop straight down one cell (you change rows but you DO NOT change elements. this is where the "repeat" test is done.

3. Draw your cellular pathway as you get FALSES and put an arrow on the pthway line when you get to TRUE.
…………………………..
Now for some reminders.

For reverse chron you keep going until you reach a TRUE. you may use all the cells before you get a true. All this means is that you are making money. And as said, you now have permission to draw to the NEXT By going under all your work in the row in the direction to the right. At a blank cell go to the middle and place a T and write the column name in the EVENT.
…………………………………………

the price "permission and suppression process.

This tool feeds the volume test procedure.

the volume test procedure defines every turn of the market.

the turns of the market define the End Effects that occur and, also define upcoming future profit taking opportunities in trend analysis and monitoring.
………………………………………………………..

There are 7 answers plus WAIT. the TEST PROCEDURE VOLUME ELEMENTS RANGES is how the test answers are detrmined.

Three columns on that sheet tell you which column to use. First is the first time in a trend. New is the time when the element appears again. New New is the additional time it appears.

Kills are time of suppression. these times are classified as either "after" or "out of range" for a prior element.

 

[frenchfry]

6 Steps to name volume bars

you are using the 6 steps illustration (past post) to wrap up gaining facility on taking the full offer of the market. Write a text for using the 6 steps.

a. You assign P1.

b. You compare forming bar to prior elligible bar. (see MADA Flow Sheet and the Mathemtics on " Test Procedure Volume Elements RANGES. the forming bar gets it name from meeting the range requirement while doing the 4 part test procedure.

c. Having completed the b. repeatedly, you look at the flow sheet entitled "Change routine". this involves figuring out turn type if any, trend type (one is always in effect), and doing look up on the four band sheets which contain all EE's. you find a "true by using the math expression related to the EE.

d. By knowing c., you figure out where the trend is in terms of its later portions. You find IF the c. is an n -1. When it is you then look for n.

If you see an n arriving, you go the the folw sheet entitled "reversal routine".

e. At "reversal" you reset and start over with a above.

 

[frenchfry]

P1

For band A, P1 is coincident with the trend ending bar. for all failsafe (two contexts) a P1 is coincident with the trend ending bar.

For all other contexts, P1 is assigned to the first non suppressed bar available.
……………………….
The P1 begins all trends (all four types).
……………………..
P1 is assigned so it can be a value that is "independent of the past. A window opens when P1 appears. Nothing is able to be seen before P1 in a beginning trend.
………………………
For P1 to repeat the forming bar must be larger.

I have added PRV as a shadow behind the forming volume, so that you know you know the value of the end of the forming bar right from its beginning.

There is some dynamic, however. But you are always in the ballpark and playing ball.

I have seen adjacent volume bars be equal in any context. P1 is the most common. If equal, then make the call that a repeat has occurred. Adjust your mind to define repeat in a way that includes equal for all sorts of things. Make it a precise way of life.

Lets do repeat for all bar names. peaks means larger; troughs mean smaller. In volume the names are names for peaks or for troughs.
…………………………………….
P1's are assigned based upon the EE that finished the prior profit segment.

An EE is assigned On the EE or AFTER the EE.

If the failsafe context gives an EE,, then, the P1 is assigned ON the EE bar. See many of the logs I have posted.

On the other hand, IF the band A is in effect, then, the P1 is assigned ON the EE bar. See many of the logs I have posted.

If neither failsafe nor band A is the context, then the P1 is assigned on the first opportunity AFTER the EE bar.

 

[frenchfry]

Ok. Let's say we have a three bar lateral. 1st and 2nd bar are a FTP Both bar Incr Price. 2nd and 3rd bar are Stitch Red. 2nd bar Incr Price, 3rd bar Decr Price. The 2nd and 3rd bar get "squished" into what form? If we add a 4th bar say FBP AND 4th bar is Incr Price, what is the "squished" result?

When I do it, I leave the first bar alone. The 2nd and 3rd bar get squished into a two-legged bar. If I squish the 2nd, 3rd and 4th, I get a third leg on a composite single bar. If this is correct then the 3rd bar of this 4bar lateral is the dominant leg of the 2nd, 3rd and 4th bar. Which has me anticipate a return to dominance on the next bar.

These are the thoughts that have me go,...."hmmm"

The lateral is maybe not a good example for a Squish. If you have a two bar combination then those two bars can be "squished" into one synthetic bar which in your FTP example gets the open, high and low from the first bar and the close from the second bar. The volume will be taken from which ever bar had the larger volume.

Theoretically you can do that with a lateral, too but we are talking here about JHM 2.0 (I hope). Therefore here are the rules how to log the lateral correctly...

Laterals

they were defined and they are known when the third bar forms with the other cases. I color the three bars in their box. after that I just put the lateral bar number above the following bars.

I put a 3 in volume to wake me up on the third bar. In the log I write lat 3 in the form column. I draw an arrow to the written UL in the row or two above. I draw a line through the volume colums and then place a W in the event column.

So more of the day is eaten up by laterals. they can last as long as they wish.

On lateral 4, a caveat occurs.

caveat 2.

write retro in the column to the right of the event column. Fill in the names of the volume bars in that column.
…………………..
Laterals have BO's. This means the boundary of the lateral (degapped) is penetrated AND the close is OUTSIDE the boundary.

If it closes back inside then the lateral continues.
……………………..

We do NOT rename "forms" while doing retro.

Retro is used to REPLACE "WAIT" in a lateral that is 4 or more bares in length.

So "RETRO" is written on a log column that is just the the "right" of the EVENT column.

At lat 4, you write "retro in the row where the LAT 1 began

Lat 2 is named as an EVENT in the retro column. And so on.

 

[llIHeroic]

@Sprout

re: Your question about failsafe OB's. The fact is that a prior P1 isn't required for PP4. tiddlywinks and I both tried to illustrate what is required for PP4 already. We worked with jack directly when he was first presenting this system. There are still old discussions and charts he posted and if you dig through those you will see your view of how PP4's work isn't correct. Any P1 over T1 OB is a PP4.

Furthermore, certain EE's assign P1 directly on the bar of the End Effect, and certain EE's assign P1 on next measurable bar. If you have an OB that triggers the former type; it's going to have a P1 auto-assigned to the top of the OB. The NEXT condition will give T1 on the bottom; triggering another End Effect. OB's give pretty consistent read-outs. Any IV OB will have at least one EE of some sort because it will be Peak over Trough. Any OB creating an A Band EE or Failsafe EE will have a double sentiment change. I'm not sure how else to phrase this. Should become apparent with enough logging.

It's nice that FF seems to be willing to help bring you up to speed on some RDBMS specifics. I'd refer questions about details to him for the time being. I want to be polite and refrain from leaving questions directed at me unanswered. But as I said I don't really have much energy / initiative toward going through the guts of this stuff again. There's a few threads worth of slogging through RDBMS details over dozens of pages already that I was a part of.

If you get to the point of trying to develop parameters to convert P/V annotations or RDBMS outputs to consistent execution please bring that to my attention. I think I will have better capacity to engage in a mutually beneficial dialogue on that subject. Best of luck on your continued progress!

 

[Sprout]

@Sprout

re: Your question about failsafe OB's. The fact is that a prior P1 isn't required for PP4. tiddlywinks and I both tried to illustrate what is required for PP4 already. We worked with jack directly when he was first presenting this system. There are still old discussions and charts he posted and if you dig through those you will see your view of how PP4's work isn't correct. Any P1 over T1 OB is a PP4.

Furthermore, certain EE's assign P1 directly on the bar of the End Effect, and certain EE's assign P1 on next measurable bar. If you have an OB that triggers the former type; it's going to have a P1 auto-assigned to the top of the OB. The NEXT condition will give T1 on the bottom; triggering another End Effect. OB's give pretty consistent read-outs. Any IV OB will have at least one EE of some sort because it will be Peak over Trough. Any OB creating an A Band EE or Failsafe EE will have a double sentiment change. I'm not sure how else to phrase this. Should become apparent with enough logging.

It's nice that FF seems to be willing to help bring you up to speed on some RDBMS specifics. I'd refer questions about details to him for the time being. I want to be polite and refrain from leaving questions directed at me unanswered. But as I said I don't really have much energy / initiative toward going through the guts of this stuff again. There's a few threads worth of slogging through RDBMS details over dozens of pages already that I was a part of.

If you get to the point of trying to develop parameters to convert P/V annotations or RDBMS outputs to consistent execution please bring that to my attention. I think I will have better capacity to engage in a mutually beneficial dialogue on that subject. Best of luck on your continued progress!

Heroic, thank you so much for the warm tone and kind assistance !

My intention is to clarify my thinking not to be argumentative.

I have though gotten sidetracked in logic traps from my unrecognized blind spots and biases.

 

[Sprout]

The lateral is maybe not a good example for a Squish. If you have a two bar combination then those two bars can be "squished" into one synthetic bar which in your FTP example gets the open, high and low from the first bar and the close from the second bar. The volume will be taken from which ever bar had the larger volume.

Theoretically you can do that with a lateral, too but we are talking here about JHM 2.0 (I hope). Therefore here are the rules how to log the lateral correctly...

Laterals

they were defined and they are known when the third bar forms with the other cases. I color the three bars in their box. after that I just put the lateral bar number above the following bars.

I put a 3 in volume to wake me up on the third bar. In the log I write lat 3 in the form column. I draw an arrow to the written UL in the row or two above. I draw a line through the volume colums and then place a W in the event column.

So more of the day is eaten up by laterals. they can last as long as they wish.

On lateral 4, a caveat occurs.

caveat 2.

write retro in the column to the right of the event column. Fill in the names of the volume bars in that column.
…………………..
Laterals have BO's. This means the boundary of the lateral (degapped) is penetrated AND the close is OUTSIDE the boundary.

If it closes back inside then the lateral continues.
……………………..

We do NOT rename "forms" while doing retro.

Retro is used to REPLACE "WAIT" in a lateral that is 4 or more bares in length.

So "RETRO" is written on a log column that is just the the "right" of the EVENT column.

At lat 4, you write "retro in the row where the LAT 1 began

Lat 2 is named as an EVENT in the retro column. And so on.

Thanks a bunch Frenchfry !!

The historical context is very helpful and supports a more targeted effort.

The text snips are great as well, thank you!
Would you by chance remember the name of some threads that go into more detail or walk throughs?

My current referential reading list includes;
SCTlearning from scratch
I am getting my butt handed to me on a daily basis
Exact Science
Volume
Math with Ram...

Yes, RDBMS! JHM 2.0!

 

[frenchfry]

Sure.

I think the first time I noticed his "new approach" after "Exact Science" was in the thread "Why is the obvious not so obvious". However I don't remember anymore why I didn't put it in my attached list.

The challenge could be that some attachments are no longer accessible. Maybe the admins can help to find them or some other member saved them and are willing to share them.

If you read through the threads what will also help is, if you do what the member "Vienna" did: create a VERY long "Ignore list" (at least temporarily). This way you can focus on only reading what Jack posted.

 

[stepan7]

Thanks a bunch Frenchfry !!

The historical context is very helpful and supports a more targeted effort.

The text snips are great as well, thank you!
Would you by chance remember the name of some threads that go into more detail or walk throughs?

My current referential reading list includes;
SCTlearning from scratch
I am getting my butt handed to me on a daily basis
Exact Science
Volume
Math with Ram...

Yes, RDBMS! JHM 2.0!

Hi Sprout,

Did you make any progress in your endeavor?

Stepan

 

[Sprout]

Hi Sprout,

Did you make any progress in your endeavor?

Stepan

Hey hey,

Yes, here's some of the current stuff I've been working on. Mainly, taking the prior helpful posts and Heroic's suggestion of the successful transference he's observed by folks making Jack Hershey's materials their own. As I worked through the logic of the Volume Test Procedure, some clarity presented itself in what Jack was hinting to about the displays of the future being something other (or addition) to the current method of depicting a price/volume chart.
That and the fact that he called the final iterative refinement of his Market System of Operation view a RDBMS.

These diagrams deconstruct the program flow of the VTP. The square boxes represent persistent data, diamonds are decisions and circles are displays. It helps to print, lay them out and connect them. They are also in a landscape format, so it can be supportive tools in the RDBMS binder.

This is a budding framework and a first draft at this, there might be inconsistencies or errors. Overall it was a great drill to obtain a deeper understanding of JHM 2.0 and an exercise to develop LTM.

I currently see the Price/Volume relationship as a revolving 4d cube-octohedron on a diagonal axis in my mind's eye. The HDHPPC comes to mind, hence the repeating 2d pattern on the diagrams.

HTH