Regarding drive cycle data

[manjunathnilugal]

Hi,
The drive cycle data for UDDS and US06, are for what capacity of the battery.
I have to simulate drive cycle for 1.65 Ah battery, is there any method to scale it down ?
https://github.com/Battery-Intelligence-Lab/SLIDE/tree/master/data/profiles/drive_cycles

Regards,

[mohammadrezwankhan]

The legacy UDDS and US06 files used by ProfileAgeing are documented as absolute cell current profiles. The source describes a peak of 8.1 A as 3C, so their reference capacity is 2.7 Ah. The sign convention is positive for discharge and negative for charge, with one-second samples for these drive cycles.

To preserve the same C-rate waveform for a 1.65 Ah cell, scale only the current values:

scale = C_target / C_reference = 1.65 / 2.7 = 0.611111
I_1.65Ah(t) = 0.611111 * I_original(t)

The 8.1 A peak therefore becomes 4.95 A. Keep the timestamps/sample duration and current signs unchanged. For a one-column/one-row current file, multiply every sample; for a two-column [current_A, duration_s] file, multiply only the current column.

Two related details matter:

1. Also configure the simulated cell itself as a 1.65 Ah cell, including its geometry/capacity and cell-specific OCV, resistance, kinetic, and thermal parameters. Scaling the input trace alone does not turn the supplied Kokam model into a calibrated 1.65 Ah cell.
2. Do not mix this legacy ampere convention with the newer drive_cycles.hpp example, which treats profile values as C-rates and calls setCurrent(c_rate * cap). For that workflow, convert the original trace once with c_rate = I_original / 2.7, set the model capacity to 1.65 Ah, and let the code produce amperes. Pre-scaling the file and then multiplying by capacity would scale twice.

The relevant profile comments and sign convention are in degradation.cpp. This capacity-ratio method preserves electrochemical C-rate stress; it does not preserve a full vehicle's demanded power unless the cell count and pack voltage are scaled consistently as well.