Possible bug in ASRDecoderTimeStamps - math.ceil on fractional tokens_per_chunk leads to timestamps displacements on long files
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. @tango4j , could you look at this? maybe at least change default values and add comment?
**Describe the bug**

I used the class `ASRDecoderTimeStamps` with fastconformer model and observed incorrect timestamps on long (1 hour) audio. The timestamps near the end of file were offset by several seconds, bigger than the actual filesize.
I think the problem is in this expression when the result of division is fractional:

https://github.com/NVIDIA/NeMo/blob/186a05ef7a0ec702f4ab56b3eb6ec3c21d096b36/nemo/collections/asr/parts/utils/decoder_timestamps_utils.py#L633

For example, default values for fastconformer `self.chunk_len_in_sec = 15` and `self.model_stride_in_secs = 0.08` lead to fractional 187.5 being rounded to 188. It seems that the rounding error somehow accumulates on long audios.
When I set `self.chunk_len_in_sec = 14`, `14/0.08=175` (whole number), all timestamps are exact. 
