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.
sevensa
Market Wizard-
Content Count
620 -
Joined
-
Last visited
Content Type
Profiles
Forums
Calendar
Articles
Everything posted by sevensa
-
A nerve? Hardly. I just find it amusing that someone with all these years of trading experience fell for buying systems which were clearly rip-offs and post about it just the other day and now guarantee profits if we follow your advice. Auto Forex FAP What does checking my trading account have to do with the guarantee you provide? Either way, I would be happy to try your advice since it is guaranteed by you. Please send a private message with your contact information where I can contact you in case things doesn't work out as guaranteed.
-
You guarantee it? Does this mean if I try it and don't make money, I can expect that you will reimburse me for the losses?
-
Nope, sorry. Looking into the future is not something I have figured out how to do yet.
-
Your issue are these two lines: fastosc>fastosc[-1] then begin fastosc<fastosc[-1] then begin The should be: fastosc>fastosc[1] then begin fastosc<fastosc[1] then begin You cannot use negative values to reference the past bars/values. Today's value is fastosc[0], yesterday's is fastosc[1], two days ago is fastosc[2], etc. Tomorrow's bar theoretically would be fastosc[-1] and that is why you get the error.
-
Have you thought about typing "ProShares UltraShort" in Google?
-
EasyLanguage - Extending the Order to More Thatn One Bar
sevensa replied to vanyok's topic in Automated Trading
You can use a counter along these lines... vars: counter(10), num_bars(5); condition = whatever; if condition then counter = 0; Counter = Counter + 1; If counter <= num_bars then buy next bar a low limit; -
This is like asking if blue or green is the better looking color. What is easy for one person, might not be easy for another person. You need to define your goal first in order to decide what you need. Just saying easy is not really a well defined goal. The only way to decide what you really need is to write down what your requirements are and what you are looking for and then look into the different options to see which will meet your requirements the closest.
- 8 replies
-
- easylanguage
- language
-
(and 4 more)
Tagged with:
-
Using different ID's are against site rules.
-
Why are you using two different ID's to post the same messages over and over on different threads?
-
Question About Daytrading Restrictions in an IRA
sevensa replied to ryanp37's topic in Beginners Forum
As far as I know, the rule is only relevant if you trade on margin. Since you are not allowed to trade on margin in an IRA account, the rule is not applicable. -
Didn't you ask what he is using?
-
Why do you say that? If you have a solid trading plan, why would it take more skill and composure to follow your plan with a small account instead of a large account? Based on what? Wouldn't that depend on your style of trading?
-
Multiple Profit Targets for Multiple Contracts
sevensa replied to palmcarl's topic in Automated Trading
Your short code has the following two lines: If ( CurrentContracts = -3) then exitshort ("ST 1") 1 contract next bar at EntryPrice-Target_1 limit else If ( CurrentContracts = 2 ) Then exitshort ("ST2") 1 contract next bar at EntryPrice-Target_2 limit The first if check for -3 contracts and the 2nd one for 2 contracts. You are missing the - sign in the 2nd if. -
This one works like a charm and much to my dismay for the hours I have spent on my version, is much simpler too. Maybe my version can be used as an example on how not to overcomplicate things...
-
Maybe if you change it to: If Globex and Time >= GLOBEX_END and Time[1] < GLOBEX_END then Globex = false; it will work for non time based charts as well?
-
You are such a show off.
-
Hi Blowfish This is certainly much simpler, but I don't think this will work. This line: If Globex and Time >= GLOBEX_END then Globex = false; will set Globex to false at 16:15 because 16:15 > 9:30 (globex_end). So at the first bar after 16:15 (globex_start), Globex is set to true with the first if statement and then immediately set to false with the next if statement.
-
After posting the code above, I have been thinking about how to prevent the "missing minute" and I think the code below does this. The code above also assumed that the overnight session ends at the same time the regular session starts since I have coded it for the e-mini's. I think the code below will work if there is a gap between the overnight session end and regular session start. I have not really tested this version other than briefly compared it to the previous one and there might be some logic errors in my thought process. Hopefully this will give you something to build on. inputs: StartTime (1530), EndTime (0830), PlotStartTime (0830), PlotEndtime (1515), TLSize (1), TLStyle (1), ONH_Color (red), ONL_Color (green); variables: ON_High(0), ON_Low(999999999), TL_ON_High(0), TL_ON_Low(0), ONH_Txt(0), ONL_Txt(0), TextStyleHoriz(1), TextStyleVert(1), Counter(0); If Time > EndTime and Time[1] <= EndTime then begin ON_High = 0; ON_Low = 999999999; Counter = 1; While Time[counter] > 0000 and date[counter] = Date begin if High[counter] > ON_High then ON_High = High[counter]; if Low[counter] < ON_Low then On_Low = Low[counter]; Counter = Counter + 1; end; While Time[counter] > StartTime begin if High[counter] > ON_High then ON_High = High[counter]; if Low[counter] < ON_Low then On_Low = Low[counter]; Counter = Counter + 1; end; end; if Time > PlotStartTime then begin TL_ON_High = TL_New(Date, PlotStartTime, ON_High, Date, PlotEndTime, ON_High); TL_SetColor(TL_ON_High, ONH_Color); TL_SetSize(TL_ON_High, TLSize); TL_SetStyle(TL_ON_High, TLStyle); TL_ON_Low = TL_New(Date, PlotStartTime, ON_Low, Date, PlotEndTime, ON_Low); TL_SetColor(TL_ON_Low, ONL_Color); TL_SetSize(TL_ON_Low, TLSize); TL_SetStyle(TL_ON_Low, TLStyle); ONH_Txt = Text_New(Date, PlotEndTime, ON_High, "ONH"); Text_SetStyle(ONH_Txt, TextStyleHoriz, TextStyleVert); Text_SetColor(ONH_Txt, ONH_Color); ONL_Txt = Text_New(Date, PlotEndTime, ON_Low, "ONL"); Text_SetStyle(ONL_Txt, TextStyleHoriz, TextStyleVert); Text_SetColor(ONL_Txt, ONL_Color); end;
-
This should do it... Create a new numeric function called RoundFraction and copy and paste the code below into it. inputs: Number(NumericSimple); vars: Fraction(0); Fraction = FracPortion(Number); If Fraction > 0 and Fraction < 0.24 then RoundFraction = 0; If Fraction >= 0.25 and Fraction < 0.74 then RoundFraction = 0.5; If Fraction > 0.75 then RoundFraction = 1; You can use it as follows: vars: val1(20.2), val2(20.4), val3(20.8), Result(0); {Result = 20.0)} Result = RoundFraction(val1) + IntPortion(val1); Print("Result = ", Result); {Result = 20.5)} Result = RoundFraction(val2) + IntPortion(val1); Print("Result = ", Result); {Result = 21)} Result = RoundFraction(val3) + IntPortion(val1); Print("Result = ", Result); The output of above code... Result = 20.00 Result = 20.50 Result = 21.00
-
Here is my version I am using. It is most likely not the best way of doing it as I am not a very efficient programmer and it is not 100% there. The minute between 23:59 and midnight is ignored, so you have a small chance of missing the high/low if it is made during that minute. I am only using it on time based charts, but I think it should work on tick and volume based charts too. inputs: StartTime1 (1530), EndTime1 (2359), StartTime2 (0000), EndTime2 (0830), PlotStartTime (0830), PlotEndtime (1515), TLSize (1), TLStyle (1), ONH_Color (red), ONL_Color (green); variables: ON_High(0), Plot_High(0), ON_Low(999999999), Plot_Low(0), TL_ON_High(0), TL_ON_Low(0), ONH_Txt(0), ONL_Txt(0), TextStyleHoriz(1), TextStyleVert(1); If Time > PlotStartTime and Time[1] <= PlotStartTime then begin Plot_High = ON_High; Plot_Low = ON_Low; ON_High = 0; ON_Low = 999999999; end; if (Time >= StartTime1 and Time <= Endtime1) or (Time >= StartTime2 and Time <= EndTime2) then begin if High > ON_High then ON_High = High; if Low < ON_Low then On_Low = Low; end ; if Time > PlotStartTime then begin TL_ON_High = TL_New(Date, PlotStartTime, Plot_High, Date, PlotEndTime, Plot_High); TL_SetColor(TL_ON_High, ONH_Color); TL_SetSize(TL_ON_High, TLSize); TL_SetStyle(TL_ON_High, TLStyle); TL_ON_Low = TL_New(Date, PlotStartTime, Plot_Low, Date, PlotEndTime, Plot_Low); TL_SetColor(TL_ON_Low, ONL_Color); TL_SetSize(TL_ON_Low, TLSize); TL_SetStyle(TL_ON_Low, TLStyle); ONH_Txt = Text_New(Date, PlotEndTime, Plot_High, "ONH"); Text_SetStyle(ONH_Txt, TextStyleHoriz, TextStyleVert); Text_SetColor(ONH_Txt, ONH_Color); ONL_Txt = Text_New(Date, PlotEndTime, Plot_Low, "ONL"); Text_SetStyle(ONL_Txt, TextStyleHoriz, TextStyleVert); Text_SetColor(ONL_Txt, ONL_Color); end;
-
I think this is one of the biggest misconceptions to think that you should adjust your stops based on your account size. The market doesn't care that you have a small or large account. If you determine that a good stop would be 20 pips away from your entry, there is no point placing it 10 pips away just because you have small account. You might think you are more conservative, but in reality this is much riskier and you have a higher probality to get stopped out of a good trade.
-
Try http://www.pinnacledata.com/. They have a pretty extensive collection of data and is very reasonably priced imo.
-
Yes, it can. I have Multicharts and NinjaTrader connected to it at the same time. I have recently started to experiment with Amibroker for realtime charting and had no issue having it connected as well.
-
In your "example" you are still buying low and selling high. Typing it in a different order doesn't change the concept. 2 + 1 is the same as 1 + 2. My earlier question still stands then. You have said earlier that looking for an approach to buy low and sell high is a search for the holy grail, so I am confused how you expect to be profitable if you are not buying low and selling high? Or if you prefer... if you are not selling high and buying low? Not really sure where this request is coming from, but I suspect you have misunderstood something somewhere. But I do have a system that catch every trend based on my definition of a trend. It also catches situations which turn out not to be trends based on my definition of a trend, but it still is profitable in the end.