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)
Over the long haul, not sure they would be much better, but there are some reasons they seem better to me. The first is the removal of the phantom bars inserted when range bars are built. The Kase bars use only real data, so if there is a gap outside the target range, the gapping tick is part of the next bar, while range bars would insert phantom bars until you get to the bar that would contain the gapping tick. The phantom bars have no volume.
This behavior is both good and bad depending what you are looking at. For backtesting, this is a very good thing because you do not want to get phantom fills in the middle of gap. For observing price, it is also a good thing because you can see that something happened, instead of seeing a nice smooth transition of price. For indicators that are gap sensitive (i.e. MA), this may not be as good, as it takes time for the indicator to settle out, and the phantom bars actually help them catch up faster.
It also depends what market and target range you are using. On the ES, they are range bars for the most part. On the CL/TF though, they tend to be different with smaller ranges as the price can really jump around. That might mean you don't have a large enough target range, but again, I can see the price action better with Kase vs range in those cases.
Are they better? I guess it depends what you care about, but I have been tending to use them over range bars even if they are only subtly different.
When listening to the interview, it just kind of bothers me that they are being presented as a new and innovative concept. I am thinking that there are more than a few people who use or who have experimented with an atr calculation to set their range bars, myself included, yet have you ever heard of the Foster Bar?
Yes, the bars are presented as wonderful thing (of course they are selling stuff), but I look at them as what they really are: a tweaked range bar. There are other bars out there (i.e. no gap range bars, alt range bars, etc), each trying to address some weakness of some bar type. It is possible that one of those is the same as Kase, but I have not gone looking at all possible bar types out there. I implemented these, as I was curious, and I already knew how to do custom bars in NT.
It all comes down to what is important to you as you are looking at price. Do you care about time? Are you looking for pivots? Do you care about volume? Lots of variables, and no bar type can do them all (that will be the AslanBarType )
A fix is coming, waiting for download file to get updated.
I really don't know what is going on in NT65, but I was able to reproduce the issue, though I did not originally understand what people were describing. In the process, I managed to trash my system as I broke a rule of mine to not install unneeded software on "the" system. After recovering from NT65, there is something about the V4 file that NT and .net do not like. Basically, the file is overriding the "tick" bar type for an unknown reason. Changing the way the id is set, back to the V3 method, fixes it.
Sorry for any inconvenience I have caused any NT65 users. I will post back when the file gets updated. If anyone needs the file pronto, just PM me.
I wasn't trying to say they can't be useful or demean your efforts. I am going to run some replays with them this weekend and if I don't see any bugs, then I plan to use them myself. I think it would be better to see the gaps and I appreciate the time you have spent to program them. Like I said, I was just a little bothered by her tact.
) 