I use the users actual readings of kW to calculate how much the SoC was supposed to increase based on those. So I don't assume anything reagarding battery cells. But yes, I saw some fluctuations in the kW numbers as well. And one reason might be that the user systematically wrote the larger numbers. But in the 3-4 minutes with kW numbers close to 250 kW the SoC was supposed to increase far more, as you can see when comparing the two graphs.
An example: A kW number of 250 kW is supposed to increase SoC more than 5 percentage points/min. His actual readings in the first minutes don't match that.
You took the user's kw/kwh readings and integrated it to get time for each point, and it didn't quite match up to the user's time readings. That the integral ended up around same the final end point, 40 min for 90% SOC, rather than accumulating differences, suggests that the first and last data points are correct, but some of the intermediate values are suspect.
Putting on my best Sherlock Holmes, looking at the blank values in the tables, the computer tendency to display rounded down values (e.g. 13:59 min shows 13 min, the innate human nature to fill out spreadsheets from top to bottom, and the coffee ring stain on the bottom left, I deduce that some of the values are not actual observations but poor (generally linear) interpolations after the fact.
Basically the user filled out observations of kw vs SOC (kwh), and time vs SOC for the v3 supercharger first without gaps. then later observed a v2 supercharger, trying to match the SOC values in the first column - but the times are different, so he inserted additional rows into the time vs SOC data. That created gaps in SOC values for the v3 supercharger, which he then tried to compensate by interpolating values.
Which numbers are or are not actual observations?
-Generally a V3 SOC value in the last column that does not have the same value in the first V3 SOC column, correspond to time observations during the later V2 SOC test that didnt' have a true V3 SOC reading
-Generally V3 SOC values in the last column that have a blank V2 SOC value, correspond to time observations that didn't have a true V2 SOC reading
-V2 SOC values with a decimal point are probably also attempts to interpolate the gaps, before giving up around the 15 min mark
-But, in some V3 observations, by the time the user shifted from recording SOC to recording time, some time and SOC values incremented by 1 in the display.
-Also, the user walks with a limp due to a gruesome childhood injury, causing him to favor his weight to his left foot.
Elementary, my dear Watson...