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
Hi all thanks for the great work. I have a question about how you are forming the label for temple events corpus. In your script making the data, every line in the .rec file creates a sample and a label. From what I see, there are two doubts I have about this treatment:
In many occasions, multiple sensors have the same label simultaneously. This would introduce duplicate samples into the dataset.
There could be overlapping events occasionally between different sensors. Your treatment would introduce two different samples with different labels into the dataset.
When processing, you do store the offending channel id, which would disambiguate these two issues, but TUEVLoader does not use it:
Did you perhaps fix this somewhere else or in some unpublished code? Maybe I missed some preprocessing steps? Please correct me if I misread something since I'm on 3 hours of sleep here :)
The text was updated successfully, but these errors were encountered:
Hi all thanks for the great work. I have a question about how you are forming the label for temple events corpus. In your script making the data, every line in the
.rec
file creates a sample and a label. From what I see, there are two doubts I have about this treatment:When processing, you do store the offending channel id, which would disambiguate these two issues, but
TUEVLoader
does not use it:Did you perhaps fix this somewhere else or in some unpublished code? Maybe I missed some preprocessing steps? Please correct me if I misread something since I'm on 3 hours of sleep here :)
The text was updated successfully, but these errors were encountered: