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
The end_time in a task dataframe is not counted as an event. I am not sure if this is a bug or if it's by design (if it's the latter, just a documentation update would do).
For example, in a task dataframe as listed below, for subject 1520408 let's assume two events before 2010-10-20 and one event on 2010-10-20, recording end_time as 2010-10-20 would be treated as a sequence of two events during the call to filter_to_min_seq_len in
If the endtime is not meant to be included (as it currently is), it would be helpful to have a note in the documentation stating this.
The text was updated successfully, but these errors were encountered:
juancq
changed the title
end_time in task dataframes is not counted as an event
end_time in task dataframes is not counted as an event (right open interval)
May 28, 2024
The end_time in a task dataframe is not counted as an event. I am not sure if this is a bug or if it's by design (if it's the latter, just a documentation update would do).
For example, in a task dataframe as listed below, for subject 1520408 let's assume two events before 2010-10-20 and one event on 2010-10-20, recording end_time as 2010-10-20 would be treated as a sequence of two events during the call to filter_to_min_seq_len in
EventStreamGPT/EventStream/data/pytorch_dataset.py
Line 322 in 2f433a6
If the endtime is not meant to be included (as it currently is), it would be helpful to have a note in the documentation stating this.
The text was updated successfully, but these errors were encountered: