Getting down and dirty is where the rubber meets the road ...

Discussion in 'Strategy Building' started by charts, Mar 31, 2010.

  1. charts

    charts

    You log the events, more than you propose to do. Look at one of the examples posted by Jack.
     
    #421     May 14, 2010
  2. Not sure I understand what you mean. Are you telling me: "Don't wast your time with that log and instead construct the three fractals on the chart?"

    Thanks for clarification.

     
    #422     May 14, 2010
  3. charts

    charts

    Au contraire ... I suggest you do what Jack recommended: log all intra-bar events, on the three fractals, following the examples he posted. Also, fully annotate on your chart both volume and price on the three fractals.
     
    #423     May 14, 2010
  4. dkm

    dkm

    Could you please elaborate. I still don't see the difference. Thanks
     
    #424     May 14, 2010
  5. I took the bars from your illustration. Here are the two internal pairs of bars from the 10 cases labeled A through J. The yellow box is a stitch; it has an H and an L which stand for high and low, respectively.

    [​IMG]

    Your log shows the progress of the left bar. The close is outside of the FF1. A new red bar forms and the log shows it as a SYM B/R. Successively, the new red bar becomes paired with the left bar as a FTP B/R, a Hitch B/B and finally a stitch B/B.

    You see that a WAIT is underway during a trading TF short Hold. The yellow container is automatically provided and lasts all the way from 300 seconds to 0 seconds of the countdown of the life of the new bar.

    The last bar in the illustration begins as a SYM B/B and time passes and the formation of the middle and last bar mutates into a SYM B/R and remains so.

    During this time you are doing M A D A. You hold on the TF short and you get nearer to point 3 of the TF.

    You are able to use the two cases to form two bars. I labeled them bar 1 and bar 2. I show how each bar relates to a case and I contain the case in a box. On a minimum level platform each box is formed and it is yellow by convention.

    As time passes I go through a process of taking a set of information that is too complex for a person to understand and I break it down into smaller parts so that the person can understand the smaller parts by reading. As is seen, all the these pieces are available and seen and have durations that appear in the bar and second column of the log.

    This makes the "order of events" a factor and a "known" in the ooperation of the market.

    Gradually an assimulation goes on with the earnest trader. He comes to understand the factors and the order in which the factors occur. You teach music. In music there are factors and they occur in an order of events. The group formed is known as a melody in some trends of factors where each factor relates to a prior factor.

    It is important to know how to combine bars to form the observable FF. So far I have suggested doing combos to get FF's and this cannot be understood up to this point. I have avoided a compare and contrast so far since I feel that adds too much drama to reading this mystery I am writing.

    All of the inventions that are present in your commentary greatly shadow the essence of the simplicity of combining two bars to make a FF. I can't really do a critiques since that only makes for very long posts about what is wrong and I am finding it difficult to make up simpler drills.

    Of course, we see here that three bars were used to make two pairs. If that is a possibility for readers, then you are taking a step forward. If you are able to use pairs of bars to ID the case represented then that is another step forward. finally, if you step , properly you may be able to combine the two bars you have into the observable FF.

    To comment on your post and illustration. I won't critique it because of the numerous errors and omissions (E&O in engineeringeze)

    It looks like you are stating the applications of stitches. Luckily all cases (cases means all 10 cases) have the same application as determined by where they occur.

    I will break my answer up into separate posts in order to minimize confusion.
     
    #425     May 14, 2010
  6. See the combination of events that occurred on the illustration. I made the last two bookmarks yellow so they would not draw immediate attention and defeat you from seeing the orde of events that occur.

    You have quite a few inventions in your illustration and I am not going to point out all these errors simply because it would be a distraction. Later I will make a suggestion on what is what in doing critical thinking.

    I want to pick up the pace a little as well. to take over a week to get through a portion of a day is a little demanding in terms of what is required vis avis the patience of others.

    Look at my annotations and see the order of events and how the order of events affects things and keeps M A D A relatively simple. the log is where the intrabar order of events unfolds in support of the EOB residue which is always observable.

    [​IMG]
     
    #426     May 14, 2010
  7. dkm

    dkm

    I am assuming that there is a “convention” that must be applied in order to connect a series of bars in accordance with the 10 cases and thereby create FF’s, TF’s and SF’s. It is apparent, due to the number of errors and inventions on my chart clip that I am not adopting the required convention, even at the most basic level of FF. If it is possible to describe the convention as a simple ruleset then perhaps it would be best to dispense with my poorly annotated chart and describe the convention, case by case. If we had a concise and clear description of when and how to connect which ends of each pair of bars, including when to fan and when to accelerate the rtl, I suspect that we would make significantly faster progress. I am most grateful for your patience and perseverance.
     
    #427     May 14, 2010
  8. As shown on the prior illustration, the FBP is in the resummed FF 3 of the short TF whereby the FF 2 of the long TF was ended by FF 1 being cancelled by exceeding the bookmark limitation AND a NEW FTT appeared in the resumed FF 3.

    So as the FF 3 continues we service it as required to be able to make money from TF FTT to FTT.

    In my first illustration of your query, I commented upon the stitch in that part of your illustration. By doing what you did with the FF rtl incorrectly you created problems for your awareness of what was going on. You did the FF 2 incorrectly too and the result was you were not aware on those bars what the order of events was either.

    Annotation is the application of parallelograms to build patterns move by move on the nesting of fractals.

    The appearance of cases where two actual bars are combined into a one bar equivalent for annotationg has an aspect of where the location of the close of the bar or FF or TF or SF determines a potential point 2. It has to do with the regions of the space. the importance of any region is determine once and for all by critical thinking in the iterative refinement of a deductive paradigm.

    A lot of your inventions come from creating convenience through induction.

    MADA is a pregmatic routine where a differnetiated mind has the opportunity to take the market's offer. Building the mind is a result of using the building blocks that were presented as a syllabus a while back. Elsewhere the syllabus is abstracted as a body of knowledge. For about 6 years, recently, we worked through streamlining the way to transfer this stuff from one person to another.

    Please begin to focus on the dominant and non dominant nature of FF's and how FF's may be used to construct TF's. Always be sure you have the SF in place so that you understand the context of what is going on.
     
    #428     May 14, 2010
  9. Right on.

    Bar 38 is part of the beginning of the long TF after the bar 37 FTT of the short TF.

    We know of the pattern which basically defines all of MADA and the paradigm as a consequence of going through the iterative refinement to complete the paradigm fully and without noise or anomalies.

    All FF 1's are unique in their P, V relationship where one price move incorporates two volume moves. The RTL on a TF level is the dividing line of the volume moves.

    David's illustration leaves out theRTL of the TF short. were it there, you would see the bar 38 go through the P to T and then the T to P of the FF 1 of the long FF 1.

    Why would I expect a PRV that shows both a P to T and a T to P to have increasing volume? for me it is simple, the sentiment change of the market is occuring and the herd is what isnow "pushing" SCT traders to make money. It is a thing that becomes second nature as a person knocks off the trades. the first FF of a pattern goes through decreasing volume to approach the RTL as the members of the herd go through the realization that a tend has ended. they do not see the period of overlap simply by ommission of reasoning. Pring is a classic example of this reticence.

    Because we deal in a space slightly ahead of the Present, we are focused on the future coming into the Present. Increasing volume is how dominance forst appears in a new trading pattern.

    By doing drills the mind gets built. I can't make that point as yet in this thread. We are still at the "give me the onepager" that explains everything and by the way write down the ATS that is how it works as a footnote.
     
    #429     May 14, 2010
  10. dkm

    dkm

    :confused:

    ...
    You did the FF 2 incorrectly too and the result was you were not aware on those bars what the order of events was either.
    ... A lot of your inventions come from creating convenience through induction.


    It is abundantly clear that I do not know wtf I am doing.

    Please begin to focus on the dominant and non dominant nature of FF's and how FF's may be used to construct TF's. Always be sure you have the SF in place so that you understand the context of what is going on.

    Jack, until I can construct an FF correctly I don't stand a chance in hell of getting correct TF's and SF's. :)
     
    #430     May 14, 2010