jupepis
commented
1 year ago In any of the cases above, the processed time variable will be increased by the new first waiting time. However, the interevent time between events will remain unaltered by such increase.
What written above is not necessary. Interevent time and time variable are two separate objects in the reh object and the time variable will bet the same as the input one.
- 1 time unit long (second/miute/hour/day/...)
- equal to the minimum waiting time observed in the sequence
- equal to the median waiting time observed in the sequence
- [ other ideas here ]
The waiting time to the first event at t[1] is now and will remain set to 1-time unit earlier, meaning that t[0] = t[1]-1 where 1 can be 1 second, minute, and so forth, depending on the time input.
Generally we expect that t[1] is not 0. When this happens, it means that the waiting time for the first event will be calculated as 0, and it would be seen as an artifact of the data because actually some time has elapsed after one starts annotating/recording events.
In the current commit of the repository
remify, if time[1] is 0, its waiting time is set to 0.Possible solutions could be about making the waiting time of the event occurred at time[1] be:
In any of the cases above, the processed time variable will be increased by the new first waiting time. However, the interevent time between events will remain unaltered by such increase.