You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if ignition_type == 'max':
# Get indices of peaks
peak_inds = detect_peaks(target, edge=None, mph=1.e-9*np.max(target))
# Get index of largest peak (overall ignition delay)
max_ind = peak_inds[np.argmax(target[peak_inds])]
#ign_delays = time[peak_inds[np.where((time[peak_inds[peak_inds <= max_ind]]) > 0.0)]]
ign_delays = time[peak_inds[peak_inds <= max_ind]]
I'm not sure if ign_delays is meant to include all of the peaks up to and including the max peak?
Later on in:
The first value in ignition_delays is always used, so the delay for the max peak doesn't actually end up being selected unless it happens to also be the first peak. From looking at the code, it seems like the same issue may be occurring for the 'd/dt max' ignition type as well, but this hasn't yet come up in testing.
The text was updated successfully, but these errors were encountered:
It seems like the 'max' ignition-type case is not working as intended.
PyTeCK/pyteck/simulation.py
Line 96 in bba7984
I'm not sure if
ign_delays
is meant to include all of the peaks up to and including the max peak?Later on in:
PyTeCK/pyteck/simulation.py
Line 496 in bba7984
The first value in
ignition_delays
is always used, so the delay for the max peak doesn't actually end up being selected unless it happens to also be the first peak. From looking at the code, it seems like the same issue may be occurring for the 'd/dt max' ignition type as well, but this hasn't yet come up in testing.The text was updated successfully, but these errors were encountered: