It might have been.
I do run my own PID tunings for this altitude. I've also spent a lot of time trying to get a single tune that will work at both sea level and at altitude. Re-scaling the WGDC base table to go up to 3.0 boost setpoint factor and 500 MAF is very important, because even with TMAP scaling 24 PSI is only seen as about 2.5 boost setpoint factor at sea level, but its 2.9 boost setpoint factor at altitude. Thus by setting your WGDC base values to the right things based on boost setpoint factor and requested MAF, you can then tune a tight PID without it oscillating, and it works at both sea level and altitude.
I've spent many many hours taking logs and adjusting things for sea level and altitude when I drive between the two. One major problem is fuel multiplier. Because the absolute boost pressure is different between the two for the same boost pressure, the PI mappings in the AIC6 need different values for the two altitudes, but you can't do that, so you have to set your fuel scalar to be close and let the short term fuel trims do their work. This means you'll never be able to keep it close to 0 STFT at both locations. I prefer to run 0 at sea level and run negative at altitude as to be safe and run rich rather than lean if you run out of STFT.
Yes it was definitely you that I talked to, probably on another forum. Because of your advice and using V8bait's very informative spreadsheet, I was able to dial in my boost way better than any OTS map I had used. Came in like 3-400 rpm sooner and held much better to my intended target by rescaling and playing with those PID settings. And yes, many hours of logging, making changes, repeat I'd love to pick your brain on some other aspects too one of these days.