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.
Tams
-
Content Count
4075 -
Joined
-
Last visited
-
Days Won
1
Everything posted by Tams
-
That's a sly remark. It is not accepted here. I am putting you on ignore. Have a nice day.
-
This is a derivative of Stochastic... As a trial run, I would suggest users to put the indicator side-by-side with Stochastic and observe the behavioral difference. As with any oscillator, it was not designed to work alone -- always use it in conjunction with a trend indicator.
-
-
gapless function: //**************** gapless day transitions - John McCormick May 2008******************** //***************** modified and made into function by Simon Kennedy 2009******************** Inputs: GapCoef(numeric), //1.0 to ignore gap -----> 0.5 half the gap -----> 0.0 to include gap Price(numeric); //open,high,low or close Vars: RelPrice(0), // Relative price gap(0), // the opening gap (modified by the gap coefficient) Accum(0); // The sum of all the daily gaps if date<>date[1] then begin gap = GapCoef*(O-C[1]); Accum = Accum+gap; end; if BarType<=1 then //Valid only for Tick or Intraday Gapless= Price - Accum else Gapless=Price; gapless_(function).txt
-
You want to rave about your QuoteTracker code, yet don't see the point of posting it, is the same reason why you can't find the eSignal code when you need it.
-
I don't see the promises... Both got stopped out at various inopportune times; if its not this one, its that one. :-(
-
this is not as difficult to do as it sounds... just draw a line... when the price hits the line, send in the order. QED
-
Nothing ..... ..... ..... however, if you also know the following information, it might help: 1. prev volume 2. prev prev volume 3. last trade price 4. prev price 5. prev prev price
-
I don't think it would make a whole lot of difference.... LOL Just mentally add "1" to each of the 4 levels, it would be about the same 99.99% of the time.
-
You can post the code and make the request here... Trading Indicators - Traders Laboratory
-
Backtesting Morning Range Breakout Using Excel VBA
Tams replied to pmsinc's topic in Automated Trading
yes pls do...... ...... -
can you post the link? I don't seem to be able to locate what you are talking about.
-
re: these loops can slow down calculations considerably this code was created 20 yrs ago for the computers of the day. it won't make a difference with today's computer. FC remembers the result from previous calculation, and makes a short cut for the current calculation. This technique works fine inside an indicator, but the memory gets lost when it is called from within a function. Try SUMMATION instead of SUMATIONFC, you will get the result you expect.
-
You have to match every BEGIN with an END. The best way to make sure they match is to indent all the codes within a BEGIN/END pair.
-
You cannot use a FC function inside a function. I have highlighted the error in your code. Inputs: Price( NumericSeries ), Period( NumericSimple ); Variables: var0( 0 ), var1( 0 ); if CurrentBar = 1 then begin for Value1 = 0 to Period - 1 begin var0 = var0 + ( Period - Value1 ) * Price[Value1] ; end ; end else var0 = var0[1] + Period * Price[0] - SummationFC(Price, Period) ; {<---- error here} var1 = ( Period + 1 ) * Period * .5 ; WMA = var0 / var1 ;
-
why are you using a custom code? if the anomaly is observed after the customization, then the error is in the customization.
-
I don't assume anything.
-
there are 2 reasons for a stop to be taken out: 1. the stop is bad 2. the entry is bad
-
there are 2 types of stops: 1. catastrophic stop -- a "wide" stop used to protect against black swan events. 2. operational stop -- a tight stop used to protect against: a) wrong analysis b) market direction changed after entry
-
which chart has this code applied? what are the differences between the charts? what are you looking for? with the limited information you are providing, you are not being helpful to yourself.
-
try this... I have highlighted the changes //Plot for shorts if High[1] < High[2] and Low[1] > Low[2] then begin //This Calcs the Fib Retracement Step1S = High - Low; Step2S = Step1S*.214; Step3S = Low + Step2S; if Close < Step3S then //If the bar closes below the 78.6% retracment, print a dot and alert. BEGIN {<---- add this} Plot5(Step3S, "IB FO S 78.6", IBShortColor ); Alert("IB FO S 78.6"); end else NoPlot( 5 ); END; {<---- add this}
-
why not post your chart, at least someone can review it and give you a hand.
-
I think that's over reacting. Mind you, I have not had much problem with MultiCharts... I have been using it since 2006, I have never experienced problems that cannot be resolved. ... and I don't consider myself a light user -- I regularly have 5~8 workspaces opened, with 4~10 charts in each window, and 10~15 heavy duty indicators in each chart. You can say, I pushed MultiCharts pretty hard.
-
Need a Desktop Alarm That Goes Off in Set Intervals
Tams replied to brownsfan019's topic in Tools of the Trade
TimeLeft, count up, count down, alarm, voice announcement, pop up window, etc., You can program this a million different ways... one of them will meet your need TimeLeft - Countdown, reminder, clock, alarm clock, tray clock, stopwatch, timer, sticker, auction watch and time synchronization utility. -
What are the context of those observations?