Rev...
That is a good start to your AT. You have to look at your AT session a bit different than your riding style. Look at how a tune is performed on a dyno.... full rollons and full decel in various gears and much more. This gives the ecm optimum data for ANY style. Say you tune it to how you ride it... NOW... then you start getting a bit more aggressive for whatever reason... you will not have sufficient data in those areas that the bike has NEVER learned. Maybe you have to get aggressive to move out of a potentially dangerous situation so you don't get hit... as an example. If you NEVER pinned the throttle to get those blocks to populate in that particular rpm/TP range, you can't predict if your bike with stumble, hit a flat spot or how it will react, you can't know.... it NEVER learned those areas you just put it into.
I stated in the very beginning of this thread... Do WHAT YOU FEEL COMFORTABLE WITH... and do it SAFELY. The reason you push outside your comfort zone for the tune is for those situations that may deem it necessary for YOU to be pushed into that zone for whatever reason.
If the data has never been collected in those areas, you cannot predict if the bike will run properly in those areas. Some of us have experienced a 'flat spot' or hesitation within a certain tune within a certain rpm range or TP.... I want to make sure that doesn't happen when I need it.... so when I tune... I try to get as much of the table populated to ensure an efficient tune will make my scoot run at its best... whatever rpm range and throttle position I have to be in.
Sure... I may not run wide open throttle in 4th, 5th and 6th gear all the time ( well... lol!) but if and when I do, I want to know that my bike has the proper data to keep it running at its optimum with proper timing and air/fuel ratios etc.....
I run a Power Vision now on my 15RGS120ST.... I started with a canned map from Fuel Moto. The AT process is much the same as I explained in this thread, however, you have the ability to datalog and WATCH the table populate and it COUNTS the number of hits in each cell. The 'magic number' on the PV to learn is 7 hits to lock in data. As you ride from city to freeway, you can visually watch to various areas of the table populate and learn due to the change in speed and throttle usage. It'ss pretty cool