Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add screen capture video frame times as events in the iohub hdf5 file.

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by locating the video post-processing script that converts frame times and the code writing the separate NPZ mapping. Review existing iohub event tables and processing queries before deciding whether the proposed videocapture device and ScreenShotEvent schema fit. Done means the mapping is represented in the HDF5 events and the requested frame/time filters are supported without the extra NPZ file.

Written by the indexing model from the issue text.

Description

idea Low Priority

During post processing of the video files, a script is available which converts video frame times to the same time base as iohub events during the session.

Instead of saving out a separate file that has the video frame - iohub event mapping table in it, should we just treat video frames as another event type. The processing script could add a 'videocapture' device within the events section of the hdf5 file, and this device could have a ScreenShotEvent table in it. The script could add one event per video frame per file for each session processed. The ScreenShotEvent type could have the following fields (the important ones are listed here):

session_id
recording_period_id
device_time: in this case would be the original frame time provided from opencv
time: the converted device time to the iohub event time base.
frame_number: the opencv frame number returned for the frame

This could replace the extra npz file being created, and the processing module could be changed to support returning other iohub events selected based on any of:

session_id,
video_id,
starting_frame_number
end_frame_number (optional)
start_video_time : in event time base, so the time from some other event could be used as the start of the search time.
end_video_time: (optional) in event time base, so the time from some other event could be used as the end of the search time period.

I'll let you decide if this would be a good way of doing things based on how you will want to slice and dice data. If you want it this way, please assign priority 1 to this issue and assign back to me.

Thanks!

Dominant language
Python
Stars
9
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EducationalTestingService/Confero

All issues in EducationalTestingService/Confero

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.