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
I have been encountering issues in the “Generate video snippets for interpretation” step of the B-SOiD Streamlit app where I cannot create an example video due to an error “list index out of range”. I’m currently using the same video I used in the earlier preprocessing stages to identify the features and clusters. I’ve also tried different syntax for specifying the sub-directory (ex. HL177\ instead of HL177) with no luck.
Some screenshots of the B-SOiD interface and error:
did you extract frames with the app? (toggle the "yes" to a "no" and extract first, sorry that part is confusing.)
the pngs/ folder in your screenshot should be populated with a subdirectory HL177_220118_OF... that contains frame1.png, frame2.png, etc.
Yes, it turned out that I didn't have the frames extracted prior to the making label predictions- hence my 'frames' directory was empty. I was able to generate the example videos as well.
I have been encountering issues in the “Generate video snippets for interpretation” step of the B-SOiD Streamlit app where I cannot create an example video due to an error “list index out of range”. I’m currently using the same video I used in the earlier preprocessing stages to identify the features and clusters. I’ve also tried different syntax for specifying the sub-directory (ex. HL177\ instead of HL177) with no luck.
Seems like the prediction went okay
Root project directory
Video and data directory I specified in B-SOiD interface:
It is mentioned here (https://stackoverflow.com/questions/65157867/indexerror-list-index-out-of-range-in-python-with-opencv-and-facerecognition) that this issue could be related with OpenCV (cv2.imread) but not familiar with to diagnose the root of the problem.
Model in use: SLEAP
Environment: Win10 Enterprise
CPU: Intel® Core™ i5-4590 CPU
RAM: 32GB
The text was updated successfully, but these errors were encountered: