openpupil / open-pupilext Goto Github PK

It seems that with large trigger runtime values (e.g., 50 min) the first parameter of the trigger command will be negative. The resulting FPS is wrong/weird. This seems to crash the STM and it needs to be rebooted. This state is a bit difficult to catch while running an experiment as superficially everything seems to work.

E.g., experimenting with different values (GUI) I got these:

Sending hardware trigger command:
Sending hardware trigger command:
Sending hardware trigger command:

Sending the command via a terminal (e.g., CoolTerm) works as expected. So I think that this issue is related to the GUI.

Hi,

Congratulations on a spectacular project, very inspiring.

What are your thoughts on supporting other camera platforms. There seem to be a few other solutions with similar spec to Basler for as little as one quarter the price.

I am very poor, but would like to be able to try out your amazing software. I am very willing to take on the work. just trying to get a sense of how much effort you think it would be.

I hope this is the right channel to reach you to discuss such things.

Thanks & regards,

James

When using two cameras (stereo camera mode), the label of the camera #1 jumps back to default after pressing connect. No functional impact, as only the GUI is affected.

Currently PupilEXT need to be build manually for macOS and Windows. With GitHub Actions PupilEXT can be build and tested automatically after pull requests. This has a high priority and needs to be implemented in the near future.

Edit: This issue is only for the project contributors. Users of PupilEXT simply need to download the compiled binaries for macOS or windows. Please read the documentation of PupilEXT in the main GitHub page for more information.

Download-Link: https://github.com/openPupil/Open-PupilEXT/releases/tag/v0.1.1-beta

PupilEXT crashed when choosing ExCuSe a pupil detection

Solution: Unknown, as this issue only happens on Mac.

Comment: Please do not use the ExCuSe algorithm if you are on a Mac.

Priority: Low

When using the hardware trigger, the maximum trigger duration is limited to 35 minutes. To solve this issue, another data type must be selected, as currently the duration is provided in seconds.

Discussed in #32

Quick-toolbar icons not visible in dark-mode of macOS.

Solution: Open PupilEXT in light-mode of MacOS.

Comment: Need to add positive-constrast icons and make it dependent on the light-mode or dark-mode state.

Priority: Low

When choosing a high fps (e.g. 120 Hz) in stereo mode, the timestamp seems to count backwards. Probably this is related to the way the frames are fetched from the camera's buffer, as the timestamp should be accurate. A current workaround is to re-order the data during pre-processing.

Further, in stereo mode, it is possible that some timestamps occur twice, which might be traced back to rounding issues in PupilEXT.

Attempting to run PupilEXT-macOS-Release-0.1.1-Beta on MacOS 12.6 (Monterey), immediately leads to the program dying with:

If the user name of the working system has a space, saving the log files does not work. A current workaround is to save the log file directly on the hard disk like 'c:/' or similar.

The source of the issue and workaround was mentioned in this post #6