Make sure that time > 0

[mhliu0001]

In the current fuse framework, the time of the event is determined either from a csv file, or from source_rate. In the latter case, the time is determined by:

event_times = self.rng.uniform(
    low=start / self.event_rate, high=stop / self.event_rate, size=stop - start
).astype(np.int64)

This time is normally larger than 0. However, if the time is very close to 0 (it might happen), fuse will create a chunk with a start time smaller than 0 because the first_chunk_left(1e6) is subtracted from the event time.

This is potentially dangerous because people always assume time>0 when coding. I don't know whether this will create any real problems, but we should avoid this kind of situation that is very hard to debug. An easy solution is to add a constant shift to all times of the event simulated; maybe the user can configure it.

[mhliu0001]

Another motivation is for my sprinkling PR (#181). I need to include waveforms that extend ~0.01s to the left of the simulated events.

[HenningSE]

Hi @mhliu0001, thanks for bringing this up. We should fix this problem! I think we have to touch the event timing when making fuse ready for mc_chain use as there we want to combine multiple simulation runs into a single run. This can only work if the runs cover different times so we would need something like a time offset that can be set by the user. Maybe we can do this in one go then.