Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Badges

New Members: Be sure to confirm your email address by clicking on the link that was sent to your email inbox. You will not be able to post messages until you click that link.

markd ✭✭✭

About

Username
markd
Joined
Visits
2,267
Last Active
Roles
Full Member
Points
117
Badges
15

Comments

  • I don't get that result. To verify the actual values you are getting for rsi(3), add this line to your scan: rank by rsi(3) You will see the rsi(3) values in the last column on the results page. When you verify on the charts, make sure your cha…
  • Thanks for the kind words.
  • Well, in general, in an uptrend, a higher volume bar should advance the trend - with a new close or a new high, and it should close in at least the upper half of the bar and its range should expand more or less commensurately with the degree of high…
  • Dreamweaver hasn't re-surfaced, so I'll take a shot at your question. You would have to do a study to know for sure, but anecdotally, I do take it as sign of possible trouble ahead, although not necessarily right away. It's probably more meaningf…
  • You can download the default data shown in the results lists. To do this, select the "Download in CSV format" option from the "Available Actions" drop down on the results page. If your scan includes a "rank by" statement, the results list will inc…
  • I'd send the question to support. Include the scan itself so they can run it if necessary.
  • You would think they would be the same, but maybe there is a difference in "Stockcharts speak" between last (most recent) update and final (last close) update. Support might know. I am surprised there is such a big difference in results, but I sup…
  • There is no need to translate. The scan code is the same for running a scan during market hours and after market hours. The difference is, if you want to run the scan intraday (while the market is open), you have to set the "start" to 0 days befo…
  • @Andyt Your could try something like this (play with the parameters) and test it over some random dates from the past: [group is sp500] and [rsi(14) > 60] and [1 days ago max(21, RSI(14)) < 60] and [min(21, RSI(14)) < 40]
    in RSI scan Comment by markd August 14
  • Usually, patterns vary enough that they are very hard to capture in code, which has to be pretty specific. No matter what you write, you may capture some instances, but you will miss others that your eye tells you fit the pattern. For a (fairly) si…
    in RSI scan Comment by markd August 13
  • I've re-arranged things a little bit. Things that describe the stock in general are first, then things that describe what its doing now. Not necessary to running the scan, but makes it easier to think about what you want and where to make edits. Al…
  • To your second question: and [close < ema(10, close) - ATR(14)] This gets hits with the close below, not at, 1 ATR below the ema.
  • When you save a scan, it saves whatever you have at that moment in the "Starting 0 days.. " window - either Last Intraday Update or Last Close. If you save the scan as Last Intraday update, and run it during market hours, it should give you result…
  • TRIN is the ratio of net ticks and net volume. It goes above 1 if declining stocks are attracting more volume and below 1 if advancing stocks are attracting more volume. Volume represents conviction. If the TRIN is moving up while TICK is moving do…
    in TRIN vrs TICK Comment by markd August 10
  • I can't find an explanation in the documentation of how they programmed "long body". However, here is an explanation of possible methods for programming "long body" by Greg Morris, who is a contributor to the site. http://stockcharts.com/articles…
  • The sell strength on PKI is not good news for the up side, but it doesn't prove a long term down trend is in place. By long term, I assume you mean several months. The up trend will often find support around the 63 LPC (lower price channel), or the …
  • I have since learned that the rank by statement is intended to be used with existing indicators and does not (intentionally) accommodate conditions that include operators.
    in Payout Ratio Comment by markd August 7
  • On the Advanced Scan Workbench, in the Scan Builder section, is a drop down called "Candlestick Building Blocks". Open the drop down, select Marabozu and click "Insert". To limit hits, you may want to add some other conditions from the Ticker Prope…
  • I think you mean Feb 15 - yes, that is a good example. In that case, price tested the low of the HV (high volume) bar. Sometimes the test is the the high of the HV bar, sometimes the body. Another example on that chart - Jun 1 tested June 12. Anothe…
  • 10 LPC (lower price channel) in March (blue channel) Notice when Fast K 10 (blue line) dips below 20, it is often a good set up. 21 LPC in April (light red channel) - note there is also a 10 LPC entry before the 21. Concentrations of buying (up vo…
  • I go down to the bar level to plan entries. Ideally, in an up trend I want to see that selling has dried up or lost its effectiveness so the trend can re-assert itself. A couple of indications are bars on low volume with tails below support but clos…
  • The chart list does have a comment window but it appears in 10 per page view, which does not have refresh. Refresh appears in Chart Workbench view, but the chart comments do not show up there. However, you can use the annotate tool to mark each cha…
    in Scan Summary Comment by markd August 5
  • If you have determined that this is a pattern that works well, then don't touch it. I think it should be written this way, with additional "weekly" modifiers and using a weekly sma so you can verify results on one chart: and [weekly slow stoch %K(…
  • On the daily, Force 251 represents a year of trading days, and 63 about three months, or a quarter of a year. So the assumption is that annual and quarterly cycles somehow correspond to different groups of investors, and when Force and its MA inters…
  • Look at TEVA today (Aug 3) for an "accumulation trap". Force looks like it is showing increasing buying - and that may have been what was happening - but a bad earnings report - apparently unanticipated - killed it.
  • Sometimes you get Force 63 MA falling and Force rising to meet it while price is still in an uptrend - in other words, there has not been a serious sell off, so it is unlikely accumulation is happening. Those hits are a distraction. To eliminate th…
  • Pretty good, but it has a long wall of resistance to climb assuming it gets above the 2016 and 2017 highs. FNV on the other hand is approaching all times highs, so there would be no resistance if it breaks above its 2016 high.
  • // MA 63 of Force is falling and [sma(63, Force(251)) < 10 days ago sma(63, Force(251))] // Force is below its MA 63 and [Force(251) < sma(63, Force(251))] // MA 21 of Force also below MA 63 and [sma(21, Force(251)) < sma(63, Force(251))]…
  • Here's another one where it doesn't work as well, but the stock doesn't have a good long term trend in place: