The "Max WGDC" table is poorly named. It should be called "Baseline WGDC" table. When you are cruising, the car is at 0% WGDC (at least that's what EvoScan says), and when you stomp on the gas, the ECU looks at the engine RPM, then goes to the Baseline WGDC table, reads the WGDC number, and applies that value to the BCS. At that point, the ECU then starts comparing the actual load to the target load (BDEL + boost offset) about once every 0.4 seconds. If the actual load matches the target load, then the ECU continues to follow the WGDC value (vs RPM) in the baseline WGDC table. However, if the ECU sees a discrepancy between actual and target load, then it can/will apply a correction to the WGDC. The amount of correction depends on the values in the boost error correction table. The correction is simply to raise or lower the entire Baseline WGDC curve. So after the correction is applied, the ECU follows the raised/lowered curve. It checks again 0.4 seconds later, and if necessary, raises or lowers the curve again. This is why the correction table isn't a function of RPM. The graph shows the behavior well. The blue arrows show when corrections are made, and its apparent that the ECU is simply raising/lowering the baseline WGDC curve.
