Yes, this is supported, exactly for the purposes you mention (optimizing an algo).
When we implemented this, we assumed people would want to use this with jevois-daemon running on the host computer. Parameter cameradev selects the device for the camera, but that could also be a movie file:
--cameradev (string) default=[/dev/video0]
Camera device name (if starting with /dev/v...), or movie file name (e.g., movie.mpg) or image sequence (e.g., im%02d.jpg, to read frames im00.jpg, im01.jpg, etc).
from http://jevois.org/doc/UserCli.html
If running jevois-daemon on host (this requires that you install the jevois deb packages on an ubuntu computer), you would start it as follows:
jevois-daemon --cameradev=movie.mpg --videomapping=23 # select the mapping that corresponds to your module; use listmappings in the console to know that number.
If you are using JeVois Inventor and want to run the movie in your camera instead, put your movie in the JEVOIS partition of the SD card, and then, add this to JEVOIS:/config/params.cfg
cameradev=/jevois/movie.mpg
(note: this config file is for experts only and thus is not available in JeVois inventor. It is the system-global params.cfg as opposed to being each module's params.cfg, which is exposed in JeVois inventor. So you need to connect the SD card to your computer, or export it from a running jevois camera it using the button under the System tab of jevois inventor).
If you copy a file movie.mpg into the root of the JEVOIS partition, that is seen by the software running in the camera as /jevois/movie.mpg
Note: when we read a movie file, we automatically rescale it to whatever input resolution your module expects.
Note2: When the movie ends, we try to rewind it, but for some video formats this is not possible. In such case, your module may stall at the end of the movie with an error that it cannot read the next video frame.