Sonic R. System

Are you guys still using the chat room that was started? If yes, can I have the latest link. It seems I cant get in with the link posted in feb 2009.

Nice work, Domas. And what is particularly good about your work is that you kept it brief and straightforwared.

The Shimodax core Tz code has been worked on, and over the past year or so has resulted in two separate and detailed works. They are called the SDX-TzPivots and the SDX-TzSweetSpots, two separate indys because the pivots became quite loaded with features and complex, and the sweetspots was not time zone dependent, and thus broken away into a separate indy. Both have been recoded to apply to both "4 point" and "5 point" platforms, which makes them universal now. Much of this effort coincided with the THV development, but I have continued to work on the pivots indy, which is now at v5. One important thing of note....I have not found any time zone shift code that does not fail when over the Christmas holidays/New Year, when we have a day that closes early followed by (weekend or not) a day that opens late.....it is the only short coming of the time zone shift coded indys that I know of. And so far, I have not see a solution. I am continuing work on the pivots indy to refine and make what has become a complex code, remain flexible yet easier to use.

For those interested, I am posting the current versions of SDX-TzPivots and SDX-SweetSpots. There is a LOT of good info on the features embedded in the notes at the top of the compile for these two indys, which I encourage users to read.

Domas4, a much needed accomplishment is for somebody to dig into the Shimodax Tz core code and figure a way to pinpoint the stop of one day (a short day ending earlier than normal) and to pinpoint the start of the next day (that has a delayed start). This combination is what causes apparently all of the time zone shift codes to fail, since they all assume days of normal trading duration in order to find the stop/start candles on which to base the pivot calculations. If you can come up with revised time zone shift core code that pinpoints the stop/start candles regardless of irregular hours trading days, especially when back to back, it could then be applied to a variety of tz shift pivot indys, that are out there. And you would receive the gratitude of many.

EJ M15: This zoomed out chart shows something interesting. The Monthly main pivot and the Weekly main pivot are close together and recent PA has failed twice above the higher of the two. At the time of the second failure, relative volume was very high, a possible pump 'n dump situation and maybe a Double Top. If PA falls thru the Daily S1 (134.54, say the half number of 134.50) on good volume, then we may have an exceptional short setup. Just a possiblility worth noting, imho.

When I have time I'll try to make the indicator count the days and hours. I'll make every fifth day shorter to see if it fixes Sundays and Christma's false calculations.

The question is in how to know when a candle is the last candle of one trading day. I don't know of any special candle "marker" that flags such a candle differently than all other surrounding candles. Without such a "marker", maybe a way to zero in on EOD (End of Day) candles, especially important when a trading day ends early, is to provide a user EOD time input (permitting half hours, not just whole hours). Then the tz code would look for any change from the default number, and if finding a user input different from the default, it would use that input to pinpoint the EOD candle.....and the next candle would be the candle for the beginning of the current day. The default number (time of the EOD candle) would, of course, be based on the Tz the server is in, with the EOD being midnight time in that time zone. The code would keep track of two things: 1)how many hours, and in what direction, the user shifts the time zone, and 2) the fact that a trading day within the shifted 24 hour period may not have all the candle count that is normal, based upon a short trading day (even two back to back), which would be triggered by the user changing the EOD time input from the normal default to some earlier time that the market actually closed. Such coding is possible, and is one way I have been thinking that the only remaining problem with TZ coding can be resolved.

The Sunday issue would not necessarily require a user input, as this is a pretty regular occurrence. The code would recognize, by dates/times of candles, when Friday ended and Sunday began simply due to the long breach in the sequence of time on the candles. When the code looks for and sees a breach, it denotes the fact of a weekend and takes the last candle in sequence before the breach as the EOD. Or, it could go back to the previous EOD candle and count forward a whole days worth of candles, less one hours worth, since Friday closes an hour earlier than all the other normal days. The next candle would be the start of the next day of trading (Sunday afternoon), beginning the sequence of 4 days (M, T, W, Th) where normally there is a full candle count for each day (unless the user inputs an EOD time to denote a short day, marking the EOD candle and the candle for the beginning of the next day becomes the next candle....whenever that may be in time, even if the next day opens late).

In other words, just counting candles (24hrs worth for M, T, W, Th and 23 hrs worth for F) does not resolve the problem....it causes the problem. The code needs a user input to tell the code that the previous day ended earlier than the 24hrs/23hrs worth of candles. So, while the code is also shifting the stop/start of the 24 hour (midnight to midnight) periods, it also is told that there may not be a full complement of candles for any day within that 24 hour period....and exactly where to end one day (and next candle starts the next day which may also turn out to be short of candles up to the next 24 hour mark). So, I am thinking a user EOD time input that will override the default time for the EOD is an exacting way to resolve this issue.

The Indicator Window for inputs would have the GMT +/- hours the Server is at. It would have the GMT +/- hours of the time zone the midnight to midnight span is to be shifted to.
And it would have a user input for the number of hours (example: 2.5) that the market closed short the previous day....the default being "0". This should allow the suggested coding method to ID the EOD candle, for any TF chart, for the 24 hour span (shifted or not shifted). With the EOD candle ID, whether changed by user input or not, the code then can exactly calculate pivots for the next day. And with a changed ID from default, the very next candle becomes the beginning of the next day, instead of the BOD (Beginning of Day) default candle...which would allow the code to exactly calculate pivots from that day when ended (at the default time or with another user input changing the default), for the follow-on day. Anyway, this is how I see an exacting solution.

It miss my TP1 with a mere few pips...which is near Tuesday Pivot..
It went back down and hit my SL...

http://www.funnyjunkz.com/wp-content.../funny-ads.jpg
Sonic

UJ M15: PA is below both monthly and weekly central pivots and playing with a break down thru TL. I am thinking to wait for a pull back upwards and maybe fresh setup short. PA is at the whole number and FO/LO traders may pump it up before slamming it down....IF down is the direction it goes.

I think that pretty well explained what my goal for the trade was.

What I left unsaid (because it had nothing to do with trading SonicR) is that today I had to be out and I would not be able to check on this trade. I didn't want to come home to a loss. As it happened, the trade did move in my direction quickly, and I moved the stop to BE when the first candle closed up 20+ pips. I made +55 on 1/2 and +0 on the second half, for a total of +27.5 on the trade.

Before I quit my trading platform and shut down for the day, I had considered lowering my TP2 to +80, near R1 (as Muhammad was smart enough to do). I did not do so. Had I done so, then this trade would have been +55 + 80 = 135 for an average trade profit of +67.5 - keeping my TP2 at +100 cost me 40 pips. That's the breaks. If I had been here watching, I would have moved my SL to TP1 level once price printed at R1. But I was not here. That's the price I pay sometimes to be able to spend the day at an amusement park with my children.

You can trade any way you wish.

I have said in other posts in Sonic's thread that I tend to slide SL to BE once we have a 20-30 pip profit on the trade, especially on the Yen crosses - not always, but often. I believe Basber has said he trades similarly. Today, Sonic had a trade come within a few pips of TP1, and he said that price then reversed and hit his SL. He does not say that it was a BE stop, so I assume it came back and hit his initial stop loss. That is how Sonic trades, and that is how his MM is spelled out in this thread.

As for me, I am not completely comfortable with Sonic's MM. I would not let a trade get within a few pips of TP1 and then let it come all the way back for a full loss at my initial TP. Sonic does. That is fine, its his money, and he can manage his trades as he wishes. You can manage your trades as you wish. I can manage my trades as I wish.

From now on when I post a SonicR, I will show EP, SL, TP1, TP2, along with wave analysis.

I will never again answer for how I manage a trade.

Tis are Some example of Sonic TRades Den juSt HappEn to move against u.

i will post some positives trade incontrast


Feel free to comment.


Nv stop LEarning

cool DD, there is nuthing wrong with ya MM, i mean idividual depends on their Risk to Reward they wanna set for themself.

In fact , the way u manage ur trade is as similar as mine. once, PA moves in my favour for certain pips. i move my S/l to BE. Again, depends on How Strong the PA signal i am getting den i will decide.

Protect ur capital

ddaytrader, thank you for taking the time to write out such a post. I believe I am the recipient of some good insight into trading and money management.

Hey Relax DD. Thank you for the answer. I was just trying to figure out how do you exit as it is very imp parameter for a successful trade of SonicR. Dint mean to offend you or anything.it was just a feedback oriented question.

Thanks for all the help.

My take is that not all are valid trades. Some of them are against the major trend and caution is always warranted there. Sonic has mentioned this many times. Also, on some of the projected entries, the QQE and CCI do not agree with the entry. Those entries could have been easily saved. Also, Sonic has mentioned that he doesnt like trading during Asian times. IF you apply these factors, I am sure many of these wrong entries were put off.

AG

Long Set up On EJ.

Any comments please?

The EMAs are flattening out.
Wave Analysis is Ok.
Waiting for QQE and CCI to confirm.

Please comment.

A set up on EU.

We are on the side of trend here. Any comments please.

We may be looking at a double top. Big volume at the highs yesterday followed by no interest. FO/LO could bring another pump n' dump. We just have to wait and see how it sets up.

EU M15: Frankfurt opens in about 10 minutes and PA is being elevated on light relative volume. Weekly R1 level is at 1.4314 and may be a resistance area that holds. After that, Monthly R1 at 1.4330. Just have to wait and see if this is a light volume pump and the real move down comes later.

EU M15: PA made a 50% retrace from yesterday's move down, with volume surging at the highs of the retrace. So, it could be that it was just pumped to dump.....but still no setup either way.

AG, can you make that picture smaller, it is screwing up the display settings so anyone on a laptop, has to scroll sideways to view the text in all the messages.