Cohu $COHU Technical Update
The Cohu (NASDAQ: COHU) update and the technical summary table below can help you manage risk and optimize returns. We have day, swing, and longer-term trading plans for COHU, and 1300 other stocks too, updated in real time for our trial subscribers. The data below is a snapshot, but updates are available now.
Review the Trading Plans:
Long Term Trading Plans for COHU
September 14, 2018, 9:30 am ET
The Technical Summary and Trading Plans for COHU help you determine where to buy, sell, and set risk controls. The data is best used in conjunction with our Market Analysis and Stock Correlation Filters too, because those help us go with the flow of the market as well. Going with the flow is extremely important, so review our Market Analysis with this COHU Report.
COHU – (Long) Support Plan
There is no current Support Plan to trigger a buy of this stock at this time. This usually means that there are no clear support levels at this time, so buying the stock as it falls could be considered catching a falling knife. Buy signals only exist if resistance breask higher.
This often is a signal that the stock you are watching is weak. Waiting for a turn higher may be more intelligent than trying to catch a falling knife. In any case, new support levels are usually revised to the database at the beginning of the next trading session.
COHU – (Short) Resistance Plan
Short under 22.92, target n/a, stop loss @ 23.18.
The technical summary data is suggesting a short of COHU as it gets near 22.92, but the downside target is not available from the current data. This tells us to hold that position if it is triggered until a new downside target has been established (updates occur at the beginning of every trading session) or until the position has been stopped. The summary data tells us to have a stop loss in place at 23.18. 22.92 is the first level of resistance above 22.71, and by rule, any test of resistance is a short signal. In this case, if resistance 22.92 is being tested, so a short signal would exist.
This post was originally published on *this site*