3.1.3DC vs 3.1.3

Jump to navigation Jump to search

Could someone explain why averaging the results from many random trees is stronger than using a single well-tuned tree?

MN (talk)13:13, 16 January 2014

I would suspect it might make your nearest-neighbours come from multiple perspectives, giving you areas of concavity in your nearest-neighbour function instead of just a pure convex search area. I also suspect using some fancy pre-processing on tree attributes (perhaps dimension reduction/PCA) before adding could give equivalent search patterns.

Skilgannon (talk)13:56, 16 January 2014
 

I'd answer this in 3 parts.

  1. There are some high level movement classes that are worth segmenting. Against simple targeters, time since velocity change is just noise. Against most bots, a flattener would be noise. But for a bot where a flattener helps, those lower levels of stats don't hurt. I think they even add "harmless noise" - they are still bullet dodging, so they won't make horrible decisions. So I have a few tiers (simple, normal / decaying, light flattener, flattener) in my movement stats, enabled at different enemy hit percentages.
  2. I found VCS to be easier to tune than DC. Similarly, I think layering a few trees is easier than trying to add features to your KNN system to create the exact "shapes" (or however you imagine it) that you want. "5 of last 150 + 5 of last 500 + 5 of last 1500" is easy to understand. Adjusting the weights and distancing to produce the same results from one KNN call seems hard.
  3. I can't prove that it is.
Voidious (talk)16:50, 16 January 2014
 

I believe that the trees tend to cancel each others errors and over fitting. That is why Random Forest works. In addition,like Voidious said, simpler trees may be better vs simple enemies.

Straw (talk)19:37, 16 January 2014
 

But then each tree should be specifically tuned against a specific kind of gun. Then each tree outputs a spike at a different GF, which shouldn't be a problem since you can dodge many GFs at once.

But generating dimensions at random to mimic DrussGT 100 buffers is another matter entirely. A combination of dimensions which don't relate to any gun is supposed to hurt classification. Although I can't prove it either.

MN (talk)01:33, 17 January 2014

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:DrussGT/Version History/3.1.3DC vs 3.1.3/reply (22).

No proofs and only conjectures, but convincing enough.

I´ll try using multiple classifications generated at random in my next version and see what happens.

MN (talk)13:46, 17 January 2014