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.
-
Content Count
4075 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Calendar
Articles
Everything posted by Tams
-
calm down... what SIUYA said was the DOM that's patterned. Programming language cannot be patterned. However, programming code can be patterned.
-
Yes... reading the manual is a must. EasyLanguage has been around for ~20 years; their manuals and tutorials are the result of years of refinement, no other trading programming language can rival its breadth and depth in coverage and code samples. I would dare to say, practically anything that you can imagine, has been done. It is only a matter of time to search out the fragment of code that is floating around in the ether space.
-
yup... for now, this is the only trick to do background color. I hope MultiCharts will come up with a new keyword soon. see this post for detail instructions http://www.traderslaboratory.com/forums/f46/paint-town-red-5721.html 96
-
can you post a chart to illustrate?
-
but... when the sequence is completed, there can be no mercy...
- 4385 replies
-
.......... try a bollinger band.
-
don't know what exactly do you mean... what is your interpretation of "pivot"? can you draw a picture to illustrate your point?
-
more housekeeping before we get into the nitty-gritty.. organize your thoughts/logics, separate the "global" requirement from the detail logics so that the code does not look crowded. i.e. make it easy to read and debug. e.g. you can separate this requirement from the detail logics time>0930 and time<1630 var: trading.hour(false); trading.hour = time>0930 and time<1630; if trading.hour = true then begin {--- write your codes here---} end;
-
approach to coding... your logic description (1st quote) should mirror the code (2nd quote), so that you can go through the required tasks line-by-line.
-
some house keeping first: 1. avoid using generic variables... ie value1, value2, etc., always create a meaningful variable names, because you will come back to the code 3 months from now and you have to scratch your head wondering what value101 is about. you have mention HH, why are you not using it in your code? 2. tag your codes, so that it is easy for everybody to read tagged codes look like this: // This is tagged code if time=0930 then value1=open; if entriestoday(date)<1 and time>0930 and time<1630 and h>(value1+100) then value2=h; if entriestoday(date)<1 and time>0930 and time<1630 and h>(value1+100) then sell short next bar at (value2-50) stop; if time>1630 then buy to cover next bar at market;
-
this is a public forum... buy your own site (or start a private thread) if you don't want people to post on your "turf".
-
This thread might help... The Price / Volume Relationship http://www.traderslaboratory.com/forums/f34/price-volume-relationship-6320.html
-
oooh you want to do quant... brilliant C# is powerful and flexible, it can do many things EasyLanguage cannot, (and vise versa) I am sure C# is good for you. Take a picture of your hair before you start.
-
if you would just add volume to the chart, you could confirm a lot sooner. don't mean to dis your effort to be a PA purist, but money don't know and don't care if you are unpure.
-
just a few notes on backtesting: 1. Backtesting is not real. Don't treat it as gospel. 2. Understanding the mechanics (spells: L-I-M-I-T-A-T-I-O-N) of backtesting will save you lots of headache. 3. different software handle backtesting differently... don't assume. 4. backtesting is to test a trading hypothesis, not validating trading codes. for code validation, you need live testing. (or forward testing at the minimal) 5. ideally you should test your "system' on at least 3 "business" cycles of data. ie: 3 up moves and 3 down moves. for some systems, that means 3 bull runs and 3 bear runs, for other systems, it might mean 3 years of data. for scalping, that means 3 intraday oscillations. Backtest is fun ! Enjoy it to the fullest.
-
let me get this straight... you want to have accurate backtesting... so you got yourself some tick data, good boy. now you are complaining that it is taking you toooooo frick'n loooong to run your 5 years of tick data? LOL Maybe I can loan you my Cray? I bet you are going to complain about the trouble it takes to count the millions of dollars when your backtest became successful. keep your chin up... you might get there, eventually. ;-)
-
I thought it beeps when price is higher than previous bar's high... try it with a small size CVB chart (say, 2000 crt)... you will see/hear it.
-
you've confused that with TradeStation Securities, Inc.
-
.......... .......... what is TT?
-
if you don't post your work-in-progress, are you expecting someone to do all the work for you?
-
write out your thoughts step by step, line by line. write them out one action at a time, one action per line... one action per line... one action per line... one action per line... eventually you will get there.
-
still awaiting your contribution..... .....
-
Please Share Your #1 Trading Rule You Adhere to with Discipline
Tams replied to rxs0005's topic in General Trading
yup... there is a lesson in every trade, especially the losing trades. you've got to embrace them to learn them. Those Who Do Not Learn From Their Lessons Are Doomed to Repeat Them. -
Today's Action by Intelligent/Predictive Agents
Tams replied to UrmaBlume's topic in General Trading
you sound frustrated that Urma is not handing you a freebie. well, neither are you giving a freebie... LOL -
Jabbing in a software thread with a coding problem is not going to lead to an answer you are looking for. If you want specific help, you should start a new thread, with your "problem" clearly and logically laid out. Blaming your inability on MultiCharts will not motivate anybody to enlighten you. note: EasyLanguage has been around a lot longer than you.