CHAPTER 13
Multiple Chart Trading: Using Kase StatWare, and KaseX

ANSWER 13.1   CMCSA Daily with Kase StatWare and KPO, Wide Stops

  1. You would have entered on the first L, shown in green.
  2. You would have entered on the second L, shown in blue.
  3. All the orange Ss are first signals.
  4. Prices peaked on July 29, but KPO divergence didn't confirm until July 31. This is the down bar marked with the orange S. Dev3 would have been hit intraday, so in actuality, the exit would have been on Dev3, not the momentum divergence per se.
  5. The magenta S prior to the price peak is a second sell, so the short reversal would have taken place upon that signal.
  6. The short signal reversal was better because it was at a higher price.
  7. Two bars before the July 8 mark on the X-axis.

ANSWER 13.2   CMCSA Weekly with Kase StatWare and KCD, Wide Stops, Tolerance 3

  1. The bar following the price high, with the orange S, confirmed the bearish divergence and closed below Dev1. So one would have fully exited the long trade on that bar.
  2. Following the exit, one would have shorted on the second S, magenta. This was the second short signal, so it was valid for a short entry.
  3. The bullish divergence was confirmed the week of April 25, and also hit Dev1 at the same time, so one would have exited fully on that bar.
  4. The second L, cyan, would have been the second long signal, valid for a long entry.
  5. Since the weekly signal is dated May 23, and the daily signal took place on May 29, one could have scaled up immediately.
  6. The bearish momentum divergence confirmed on an up bar, as denoted by the dashed line. (This is an upgrade that was discussed in the Q&A for Section 12.) Thus an exit would have been optional. Given that Dev1 was hit, a strategy ranging from not taking an exit at all, perhaps pulling the stop into a close below Dev1, to a full exit could have been justified.

ANSWER 13.3   GBPUSD 33 Percent of Daily Range Kase Bar, KaseX

images
  1. After two triangles, there's a Dash1 hit. The reentry takes place upon the next purple down triangle. If one wanted to be more conservative, one might have waited for the following down triangle.
  2. Long entries are shown by green up block arrows.
  3. The trade taken following the Dash1 hit would have been exited upon momentum divergence as shown by the small light purple down arrow.
  4. Short, on the entry discussed in answer 1.

ANSWER 13.4   X Daily with KaseX

  1. It would have been about even either way. On the left one would have gotten into the successful short trade earlier, but would have gotten whipsawed during the uptrend, on the right. On balance, I would have preferred to get in slightly later, and avoid the later whipsaw.
  2. In this case, if entering long aggressively, one would have gotten whipsawed twice in exchange for entering one bar after the low on the run-up that began in early June. On balance, I would have preferred to get in a bit later than to deal with the whipsaws.
  3. There were three instances of up green arrows, but only the one in early June resulted in a stop hit, and thus an exit. Dash1 level stops were hit before the normal buy signal, so it wasn't a reversal.
  4. The down purple arrow in mid-July signaled a bearish divergence. This was followed by a Dash1 stop hit, so that's where one would have gotten out.
  5. Long as I would have reentered on the sequential green triangle, and after that there have been no exit signals of any kind.

ANSWER 13.5   M Daily with Kase StatWare

images

M Weekly with Kase StatWare

images
  1. The initial long entry is marked by the blue arrow on the daily chart.
  2. The scale-up point is marked by the blue arrow on the weekly chart.
  3. Whipsaw areas are circled on the daily chart.
  4. The first red arrow on the weekly chart marks the 80 percent exit point due to the KaseCD divergence. The remaining 20 percent would be exited upon the Dev1 hit marked by the second red arrow.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset