Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I am working on my first (complex) indicator and making good progress. The drawing functions of MC are a little bit limited (only lines, no rectangulars etc.) but I get used to it.
BTW: MC's approach of defining functions with more than one result value is really strange (declare inputs as "pseudo-outputs") - at this point I really miss C# or a similar OO language...
aknip
Can you help answer these questions from other members on NexusFi?
There is a good trick for drawing rectangles on the MC forum. I am heading to bed or I would link for you, but try searching for rectangle. Their drawing tools are fine for my needs, there are trade offs vs Ninja, both good and bad. Since you prefer to deal with non-time based charts, remember to use the _s versions of most the drawing tools so you get more granular control (the _s means seconds).
To be honest, I actually prefer MultiChart's method for functions. Yes, it took me an hour to figure out how the hell to return a value, or multiple values. But once I did, I was fine with it. It's not that particular "feature" I prefer, it's the whole design structure that I prefer. It is so much cleaner now to re-use frequent functions within different strategies.
But the issues for accurate backtesting aren't limited to the exotic data series. ANYTHING ofther than time is subject to inconsistencies, including Range, Renko, Volume, and Tick .
It's particularly galling when the vendors offer these chart types natively, knowing that backtesting and of course optimizing with them is an exercise in futility.
This really is not the right thread for this. With aknip's approval, this entire exchange on renko issues can be moved to the MultiCharts thread.
I don't agree with that statement. Please tell me more about your MultiCharts testing with volume, range, and tick and the inconsistencies you discovered in backtesting and optimizing.
The last 14 posts came from the HugoHurley automated strategy thread. Since they described a problem with MultiCharts it was better to move them to this thread than clutter up the strategy thread.
I guess you are saying you'd make a new object or struct every time you want to return multiple things. Ok, but I thought I should point out that C#'s approach to multiple return values is pretty much exactly the same as Easylanguage's approach. Same with C's approach, and most other c-style languages. So, it's really not strange at all. In fact, languages like Lisp and Scheme with native support for multiple return values are in the minority, language-wise.
I just started using MC and am getting my data from IQfeed. One thing I noticed is that unlike NT, MC doesn't
seem to have a way to "filter out" bad prints? nothing exotic, just plain 5min or 30 min bar charts. Curious to see if there is a workaround in MC?
Don't know what instrument you are tracking, but how do you know there are bad prints? I have never had issues with IQ, but I only follow pretty standard instruments. Never had issues with Zen for that matter either.
