Jump to content

Welcome to the new Traders Laboratory! Please bear with us as we finish the migration over the next few days. If you find any issues, want to leave feedback, get in touch with us, or offer suggestions please post to the Support forum here.

aaa

Members
  • Content Count

    466
  • Joined

  • Last visited

Everything posted by aaa

  1. I use 3 workspaces 1 = 1 chart dayly 700 bars back + 1 chart 168 mn 700 bars back detached on a 2nd screen 2 = 1 chart 60 mn 700 bars barck + 1 chart 15 mn 700 bars back detached on a 2nd screen The one I trade with 3 = ( 1 chart 5 mn 700 bars barck + 1 chart 1 mn 9 days back ) + 1 chart 1 mn 9 days back with 2 datas detached on a 2nd screen Total = 8 datas in RT And my CPU is over 50 oftenly 80% I think that it could be indicator(s) which is bad writen... PS I have a HMM with a 610 period this is why I use 700 bars back
  2. I'm Glad to collaborate with my few knoledge I 've traded from 9:00 to 15:30 (Zurich Time) with the pair EuroStoxx cash/EuroStoxx Future And at 15:30 I've swapped to the pair DJI cash/EuroStoxx without any problem I added this because it was quicker to add a symbol on an existed graph rather that starting from 0. It is very processing hard charge with 8 graphs for a quadriProcessor My compliments for this great indicator ; I really improve my trading
  3. ATTENTION :helloooo: This is A GREAT indicator, one the best one on my modest point of view. I will post charts and interpretations this weekend I added minor changes, if Tams agree // version 5.6b // Author: aa // Date: 20090505 // 1) The Threshold.Upper and Threshold.Lower are linked // 2) Choose between inserting the... // ... Insert.Cash.1rst = 1 // ... Future first = 0 // 3) Set a noPlot color for good color synchronisation STRSQZ_Stretch_and_Squeeze v5.6b.txt
  4. Of course QED or CQFD which was to be demonstrated English is not my mother tongue too
  5. You are right I must give more informations if I want to be understood I hope that this graph is clear enough The lookback period is usefull to clean the graph from pollution of all the H/L of the data range Let say on my graph that I estimated that the -4 day is an important top It could be also the -10 day ( the yellow arrow ) or any lookback (may be maxi 50 days ?) The Blue/red color for H/L is a way to immediatly see the confluences of the H/L
  6. I don't see any changes... I'm not a fan of multi colored lines too Blue for High and red for low I'm not complaining guys !!! Your help is a gift I think that my way is not the good way to do what I "want" The code is too heavy because if I want to have 50 days back... 2 millions exponentials codes lines may be ? Also it's better to have the beginning of the line with the real first day in a solid line to better interpretation and the choose of, let's say, 50 days of Xtended dotted lines on the right My 15 mn charts is exactly my goal 50 ThanX anyway, I really do appreciate your help.
  7. It's good to have friends all over the world The idea is simple and works like classicals pivots The goal is to have High Blue and low Red in a solid color And to extend in Dotted lines to the right during xDays The circles shows interesting S/R on the 15 mn graph They are a lot of pullback in 1 mn on these support
  8. I think that I understand TL_New but no way to extend extend lines on the right !!! I've coded :missy: something horrible and complicate , but it works Tams, If you have time to correct it I will appreciate it a lot // HL bar (MC) // version: beta 0.1 // author: TAMS // date: 20090426 // license: public use // description: this indicator draws a trendline // at the highest high and lowest low of X days back input: lookback( 1 ), Line.size ( 1 ), Line.style ( 1 ), color.tl.h( blue ), color.tl.l( red ); // 1 if date <> date[1] and lookback = 1 then begin value1 = tl_new_s(d , time_s , highd(1), d , time_s, highd(1 )); value2 = tl_new_s(d , time_s, lowd(1), d , time_s, lowd(1)); tl_setcolor( value1, color.tl.h ); TL_SetSize( value1, Line.size ); TL_SetStyle( value1, Line.style ); tl_setcolor( value2 , color.tl.l ); TL_SetSize( value2, Line.size ); TL_SetStyle( value2, Line.style ); end; if lookback = 1 then begin tl_setend_s(value1, d , time_s , highd(1) ); tl_setend_s(value2, d , time_s , lowd(1) ); end; // 2 if date <> date[1] and lookback = 2 then begin value1 = tl_new_s(d , time_s , highd(1), d , time_s, highd(1 )); value2 = tl_new_s(d , time_s, lowd(1), d , time_s, lowd(1)); value3 = tl_new_s(d , time_s , highd(2), d , time_s, highd(2 )); value4 = tl_new_s(d , time_s, lowd(2), d , time_s, lowd(2)); tl_setcolor( value1, color.tl.h ); TL_SetSize( value1, Line.size ); TL_SetStyle( value1, Line.style ); tl_setcolor( value2 , color.tl.l ); TL_SetSize( value2, Line.size ); TL_SetStyle( value2, Line.style ); tl_setcolor( value3, color.tl.h ); TL_SetSize( value3, Line.size ); TL_SetStyle( value3, Line.style ); tl_setcolor( value4 , color.tl.l ); TL_SetSize( value4, Line.size ); TL_SetStyle( value4, Line.style ); end; if lookback = 2 then begin tl_setend_s(value1, d , time_s , highd(1) ); tl_setend_s(value2, d , time_s , lowd(1) ); tl_setend_s(value3, d , time_s , highd(2) ); tl_setend_s(value4, d , time_s , lowd(2) ); end; // 3 if date <> date[1] and lookback = 3 then begin value1 = tl_new_s(d , time_s , highd(1), d , time_s, highd(1 )); value2 = tl_new_s(d , time_s, lowd(1), d , time_s, lowd(1)); value3 = tl_new_s(d , time_s , highd(2), d , time_s, highd(2 )); value4 = tl_new_s(d , time_s, lowd(2), d , time_s, lowd(2)); value5 = tl_new_s(d , time_s , highd(3), d , time_s, highd(3 )); value6 = tl_new_s(d , time_s, lowd(3), d , time_s, lowd(3 )); tl_setcolor( value1, color.tl.h ); TL_SetSize( value1, Line.size ); TL_SetStyle( value1, Line.style ); tl_setcolor( value2 , color.tl.l ); TL_SetSize( value2, Line.size ); TL_SetStyle( value2, Line.style ); tl_setcolor( value3, color.tl.h ); TL_SetSize( value3, Line.size ); TL_SetStyle( value3, Line.style ); tl_setcolor( value4 , color.tl.l ); TL_SetSize( value4, Line.size ); TL_SetStyle( value4, Line.style ); tl_setcolor( value5, color.tl.h ); TL_SetSize( value5, Line.size ); TL_SetStyle( value5, Line.style ); tl_setcolor( value6 , color.tl.l ); TL_SetSize( value6, Line.size ); TL_SetStyle( value6, Line.style ); end; if lookback = 3 then begin tl_setend_s(value1, d , time_s , highd(1) ); tl_setend_s(value2, d , time_s , lowd(1) ); tl_setend_s(value3, d , time_s , highd(2) ); tl_setend_s(value4, d , time_s , lowd(2) ); tl_setend_s(value5, d , time_s , highd(3) ); tl_setend_s(value6, d , time_s , lowd(3) ); end; // 4 if date <> date[1] and lookback = 4 then begin value1 = tl_new_s(d , time_s , highd(1), d , time_s, highd(1 )); value2 = tl_new_s(d , time_s, lowd(1), d , time_s, lowd(1)); value3 = tl_new_s(d , time_s , highd(2), d , time_s, highd(2 )); value4 = tl_new_s(d , time_s, lowd(2), d , time_s, lowd(2)); value5 = tl_new_s(d , time_s , highd(3), d , time_s, highd(3 )); value6 = tl_new_s(d , time_s, lowd(3), d , time_s, lowd(3 )); value7 = tl_new_s(d , time_s , highd(4), d , time_s, highd(4 )); value8 = tl_new_s(d , time_s, lowd(4), d , time_s, lowd(4 )); tl_setcolor( value1, color.tl.h ); TL_SetSize( value1, Line.size ); TL_SetStyle( value1, Line.style ); tl_setcolor( value2 , color.tl.l ); TL_SetSize( value2, Line.size ); TL_SetStyle( value2, Line.style ); tl_setcolor( value3, color.tl.h ); TL_SetSize( value3, Line.size ); TL_SetStyle( value3, Line.style ); tl_setcolor( value4 , color.tl.l ); TL_SetSize( value4, Line.size ); TL_SetStyle( value4, Line.style ); tl_setcolor( value5, color.tl.h ); TL_SetSize( value5, Line.size ); TL_SetStyle( value5, Line.style ); tl_setcolor( value6 , color.tl.l ); TL_SetSize( value6, Line.size ); TL_SetStyle( value6, Line.style ); tl_setcolor( value7, color.tl.h ); TL_SetSize( value7, Line.size ); TL_SetStyle( value7, Line.style ); tl_setcolor( value8 , color.tl.l ); TL_SetSize( value8, Line.size ); TL_SetStyle( value8, Line.style ); end; if lookback = 4 then begin tl_setend_s(value1, d , time_s , highd(1) ); tl_setend_s(value2, d , time_s , lowd(1) ); tl_setend_s(value3, d , time_s , highd(2) ); tl_setend_s(value4, d , time_s , lowd(2) ); tl_setend_s(value5, d , time_s , highd(3) ); tl_setend_s(value6, d , time_s , lowd(3) ); tl_setend_s(value7, d , time_s , highd(4) ); tl_setend_s(value8, d , time_s , lowd(4) ); end;
  9. I'm not sure that everybody read Japanese on this forum...
  10. An indicator of tendency suit, efficient but very little known of the investors. Ichimoku Kinko Hyo" has been developed by the Japanese journalist Goichi Hosoda, that wrote under the pseudonymous Ichimoku Sanjin, before World War II. It appeared a few years ago to Japan this indicator is excellent to predict the tendencies of the markets The documentation on" Ichimoku Kinko Hyo" remains limited
  11. For the 3 temporal variables, the indicator's author counsels to choose respectively the lengths of 9 days, 26 days 52 days. At the time of this indicator's creation, there were 6 days of trading in one week. These parameters corresponded therefore to one week and half for the short-term analysis, one month for the medium-term survey and two months for the long term. Today, the financial places are open 5 days per week. To adjust, you can choose therefore the periods of 7 days, 22 days 44 days As for other indicators, the parameters must be adjusted according to the periodicity of your diagram.
  12. Thank's for this interesting programm, programmer If I understand well, it takes the middle of x last High and low days And then the confluence of all that middles + x last High and low should give strong S/R ? Does it means that we can't use your code ? I am a beginner and sorry if my question looks stupid
  13. I always trade with the DJI cash 1 mn on my left screen and the EuroStoxx Future 1 mn on the right screen. (Europe market follows US markets as a sticker) The interpretation takes a long time and this indicator looks to be very interesting I will try it next week ThanX Tams
  14. Ichimoku Kinko Hyo Technical Indicator is predefined to characterize the market Trend, Support and Resistance Levels, and to generate signals of buying and selling. This indicator works best at weekly and daily charts. When defining the dimension of parameters, four time intervals of different length are used. The values of individual lines composing this indicator are based on these intervals: Tenkan-sen shows the average price value during the first time interval defined as the sum of maximum and minimum within this time, divided by two; Kijun-sen shows the average price value during the second time interval; Senkou Span A shows the middle of the distance between two previous lines shifted forwards by the value of the second time interval; Senkou Span B shows the average price value during the third time interval shifted forwards by the value of the second time interval. Chinkou Span shows the closing price of the current candle shifted backwards by the value of the second time interval. The distance between the Senkou lines is hatched with another color and called "cloud". If the price is between these lines, the market should be considered as non-trend, and then the cloud margins form the support and resistance levels. If the price is above the cloud, its upper line forms the first support level, and the second line forms the second support level; If the price is below cloud, the lower line forms the first resistance level, and the upper one forms the second level; If the Chinkou Span line traverses the price chart in the bottom-up direction it is signal to buy. If the Chinkou Span line traverses the price chart in the top-down direction it is signal to sell. Kijun-sen is used as an indicator of the market movement. If the price is higher than this indicator, the prices will probably continue to increase. When the price traverses this line the further trend changing is possible. Another kind of using the Kijun-sen is giving signals. Signal to buy is generated when the Tenkan-sen line traverses the Kijun-sen in the bottom-up direction. Top-down direction is the signal to sell. Tenkan-sen is used as an indicator of the market trend. If this line increases or decreases, the trend exists. When it goes horizontally, it means that the market has come into the channel.
  15. An other great Topic from Tams
  16. Eureka :doh: The code is clear, elegant. Have a nice week.
  17. Yes I reached my limits with arrays and I don't understand zigzag I tried "my" indicator with 10 days long It looks interesting especially scalping in 1 mn : the price stops always for a short break at highest last 1, 2 3 or more past days (cf picture below) If you have time Could you make a correct code ? Here is my terrible one It works but slows down dramatically the software Also the style is off Inputs: Days.Nbr( 2 ), Color.HL( blue ), Size.HL( 2 ), Style.HL( 1 ); Var: count( 0 ), count.end( Days.Nbr * 2 ); Arrays: Line.ID[20]( 0 ), level[20]( 0 ), DaysAfter[20](0 ), TimeAfter[20](0 ), DaysBefore[20](0 ), TimeBefore[20](0 ); level[1] = HighD(1); level[2] = LowD(1); level[3] = HighD(2); level[4] = LowD(2); level[5] = HighD(3); level[6] = LowD(3); level[7] = HighD(4); level[8] = LowD(4); level[9] = HighD(5); level[10] = LowD(5); level[11] = HighD(6); level[12] = LowD(6); level[13] = HighD(7); level[14] = LowD(7); level[15] = HighD(8); level[16] = LowD(8); level[17] = HighD(9); level[18] = LowD(9); level[19] = HighD(10); level[20] = LowD(10); DaysBefore[1] = d[1] ; DaysBefore[2] = d[1] ; DaysBefore[3] = d[2] ; DaysBefore[4] = d[2] ; DaysBefore[5] = d[3] ; DaysBefore[6] = d[3] ; DaysBefore[7] = d[4] ; DaysBefore[8] = d[4] ; DaysBefore[9] = d[5] ; DaysBefore[10] = d[5] ; DaysBefore[11] = d[6] ; DaysBefore[12] = d[6] ; DaysBefore[13] = d[7] ; DaysBefore[14] = d[7] ; DaysBefore[15] = d[8] ; DaysBefore[16] = d[8] ; DaysBefore[17] = d[9] ; DaysBefore[18] = d[9] ; DaysBefore[19] = d[10] ; DaysBefore[20] = d[10] ; TimeBefore[1] = t[1] ; TimeBefore[2] = t[1] ; TimeBefore[3] = t[2] ; TimeBefore[4] = t[2] ; TimeBefore[5] = t[3] ; TimeBefore[6] = t[3] ; TimeBefore[7] = t[4] ; TimeBefore[8] = t[4] ; TimeBefore[9] = t[5] ; TimeBefore[10] = t[5] ; TimeBefore[11] = t[6] ; TimeBefore[12] = t[6] ; TimeBefore[13] = t[7] ; TimeBefore[14] = t[7] ; TimeBefore[15] = t[8] ; TimeBefore[16] = t[8] ; TimeBefore[17] = t[9] ; TimeBefore[18] = t[9] ; TimeBefore[19] = t[10] ; TimeBefore[20] = t[10] ; DaysAfter[1] = d[1] ; DaysAfter[2] = d[1] ; DaysAfter[3] = d[2] ; DaysAfter[4] = d[2] ; DaysAfter[5] = d[3] ; DaysAfter[6] = d[3] ; DaysAfter[7] = d[4] ; DaysAfter[8] = d[4] ; DaysAfter[9] = d[5] ; DaysAfter[10] = d[5] ; DaysAfter[11] = d[6] ; DaysAfter[12] = d[6] ; DaysAfter[13] = d[7] ; DaysAfter[14] = d[7] ; DaysAfter[15] = d[8] ; DaysAfter[16] = d[8] ; DaysAfter[17] = d[9] ; DaysAfter[18] = d[9] ; DaysAfter[19] = d[10] ; DaysAfter[20] = d[10] ; TimeAfter[1] = t[1] ; TimeAfter[2] = t[1] ; TimeAfter[3] = t[2] ; TimeAfter[4] = t[2] ; TimeAfter[5] = t[3] ; TimeAfter[6] = t[3] ; TimeAfter[7] = t[4] ; TimeAfter[8] = t[4] ; TimeAfter[9] = t[5] ; TimeAfter[10] = t[5] ; TimeAfter[11] = t[6] ; TimeAfter[12] = t[6] ; TimeAfter[13] = t[7] ; TimeAfter[14] = t[7] ; TimeAfter[15] = t[8] ; TimeAfter[16] = t[8] ; TimeAfter[17] = t[9] ; TimeAfter[18] = t[9] ; TimeAfter[19] = t[10] ; TimeAfter[20] = t[10] ; for count = 1 to count.end begin Line.ID[count] = TL_New( DaysBefore[count] , TimeBefore[count] , level[count], DaysAfter[count] , TimeAfter[count] , level[count]); TL_SetColor( Line.ID[count] , Color.HL); TL_SetSize( Line.ID[count] , Size.HL ); // TL_SetStyle( Line.ID[count] , Style.HL ); end;
  18. Let's try the Tams Prize before !
  19. Tams, I think that I am in the wrong way I have now the yesterday HL during 2 days The code looks complicate and if I want lines during x days it should be very long The goal is to have the Yesterday HL during x days Are arrays the solution ? Is a counter a solution ? Inputs: Color.HL( blue ), Size.HL( 2 ), Style.HL( 1 ); Var: count( 0 ), count.end( 4 ); Arrays: Line.ID[4]( 0 ), level[4]( 0 ), DaysAfter[4]( 0 ), TimeAfter[4]( 0 ), DaysBefore[4](0 ), TimeBefore[4](0 ); level[1] = HighD(1); level[2] = LowD(1); level[3] = HighD(2); level[4] = LowD(2); DaysBefore[1] = d[1] ; DaysBefore[2] = d[1] ; DaysBefore[3] = d[2] ; DaysBefore[4] = d[2] ; TimeBefore[1] = t[1] ; TimeBefore[2] = t[1] ; TimeBefore[3] = t[2] ; TimeBefore[4] = t[2] ; DaysAfter[1] = d[1] ; DaysAfter[2] = d[1] ; DaysAfter[3] = d[2] ; DaysAfter[4] = d[2] ; TimeAfter[1] = t[1] ; TimeAfter[2] = t[1] ; TimeAfter[3] = t[2] ; TimeAfter[4] = t[2] ; for count = 1 to count.end begin Line.ID[count] = TL_New( DaysBefore[count] , TimeBefore[count] , level[count], DaysAfter[count] , TimeAfter[count] , level[count]); TL_SetColor( Line.ID[count] , Color.HL); TL_SetSize( Line.ID[count] , Size.HL ); TL_SetStyle( Line.ID[count] , Style.HL ); end;
  20. // Draw High and Low lines of the day before // version 1.01 // Author: aaa // Date: 20090425 Inputs: Color.High( blue ), Color.low( red ), Size.HL( 2 ), Style.HL( 1 ); Var: count( 0 ), count.end( 2 ); Arrays: Line.ID[2]( 0 ), level[2]( 0 ), Color[2]( 0 ), Size[2]( 0 ), Style[2]( 0 ); level[1] = HighD(1); level[2] = LowD(1); Color[1] = Color.High; Color[2] = Color.low; Size[1] = Size.HL ; Size[2] = Size.HL ; Style[1] = Style.HL ; Style[2] = Style.HL ; for count = 1 to count.end begin Line.ID[count] = TL_New( d[1] , t[1] , level[count], d , t , level[count]); TL_SetColor( Line.ID[count] , Color[count] ); TL_SetSize( Line.ID[count] , Size[count] ); TL_SetStyle( Line.ID[count] , Style[count] ); end;
  21. It's a Great idea to create topics like this Sorry, if it's not a really original indicator.... It is only an exercice with arrays
  22. ThanX for your notes Mister TAMS I like it hard ! Starting point = ending point = OK for a day H/L but Date + time must start the day before // Draw High and Low lines of the day before // version 1.0 // Author: aaa // Date: 20090425 Var: count( 0 ), count.end( 2 ); Arrays: Line.ID[2]( 0 ), level[2]( 0 ), Color[2]( 0 ), Size[2]( 0 ), Style[2]( 0 ); level[1] = HighD(1); level[2] = LowD(1); Color[1] = blue; Color[2] = red ; Size[1] = 2 ; Size[2] = 2 ; Style[1] = 1 ; Style[2] = 1 ; for count = 1 to count.end begin Line.ID[count] = TL_New( d[1] , t[1] , level[count], d , t , level[count]); TL_SetColor( Line.ID[count] , Color[count] ); TL_SetSize( Line.ID[count] , Size[count] ); TL_SetStyle( Line.ID[count] , Style[count] ); end;
  23. a little correction but the result has a lot of lines Var: count( 0 ), count.end( 2 ); Arrays: Line.ID[2]( 0 ), level[2]( 0 ), Color[2]( 0 ); Level[1] = HighD(1); Level[2] = LowD(1); Color[1] = blue; Color[2] = red; for count = 1 to count.end begin Line.ID[count] = TL_New( d , t , level[count], d, t , level[count]); TL_SetColor(Line.ID[count], Color[count]); TL_SetExtRight(Line.ID[count], true ); end;
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.