This came up when feeding a run into spiceEV (thanks to @stefansc1 for spiceEV's sanity checks!).
With default_single scenario with changed config: simbev_config.txt (txt instead of cfg as github doesn't support this extension) there're some lines which show implausible numbers:
car_type
bat_cap
location
netto_charging_capacity
SoC_start
SoC_end
chargingdemand
charge_time
park_start
park_end
drive_start
drive_end
consumption
...
...
...
...
...
...
...
...
...
...
...
...
...
59
phev_luxury
40
driving
0.0
1.0
0.0
0.0
0
0
0
937
956
106.20382399999998
...
...
...
...
...
...
...
...
...
...
...
...
...
Even if it is somewhat realistic that the EV uses up the entire capacity (is this supposed?), the consumption is flawed and should be 40.
Sometimes, this also occurs with phev_medium and phev_mini but seems that only PHEVs are affected, BEV not.
This came up when feeding a run into spiceEV (thanks to @stefansc1 for spiceEV's sanity checks!).
With
default_single
scenario with changed config: simbev_config.txt (txt instead of cfg as github doesn't support this extension) there're some lines which show implausible numbers:Even if it is somewhat realistic that the EV uses up the entire capacity (is this supposed?), the consumption is flawed and should be 40.
Sometimes, this also occurs with
phev_medium
andphev_mini
but seems that only PHEVs are affected, BEV not.Ideas, @timroepcke ?