Pulse peak time correction for unusable pixel (July 30, 2024, pixel 1739)

[SeiyaNozaki]

Pixel 1739 was tagged as an unusable_pixel due to highped_std (due to a bright star) on July 30, 2024. So time_correction value of this pixel was set to 0 ns in the calibration product.

This calibration produce was used to process the data taken on July 30, then this pixel showed ~3 ns delay in calibration pulse peak time. It means this pixel was not interpolated, but time correction was not applied ("0 ns" time_correction was applied).
https://www.lst1.iac.es/datacheck/dl1/v0.10/20240730/DL1_datacheck_20240730.html

Is it intended? Maybe it would be better to compute the average (median) peak time of the same module, and set this value to one of unusable pixels since this correction mainly comes from the BP delay calibration (module-wise).