Skip to content

Determine if sampling rate needs to be adjusted in Titta #14

@anna-stacey

Description

@anna-stacey

So I had previously gone into our Titta fork and changed the settings.SAMPLING_RATE = 60 for Tobii Pro Fusion.
Then I wondered if this was necessary, bc some quick research suggested the original 120 was a permissible value.
However, when it is set to 120, I get the following crash/error message:

Traceback (most recent call last):
6.4052     WARNING     Monitor specification not found. Creating a temporary one...
  File "C:\Users\Anna\Documents\Wiigwaas\wiigwaas.py", line 250, in <module>
    main()
  File "C:\Users\Anna\Documents\Wiigwaas\wiigwaas.py", line 46, in main
    recorder = set_up_recorder(main_window, mouse, str(subjID))
  File "C:\Users\Anna\Documents\Wiigwaas\eye_tracking_resources.py", line 110, in set_up_recorder
    tracker.init()
  File "C:\Users\Anna\Documents\Wiigwaas\Titta\titta\Tobii.py", line 168, in init
    self.set_sample_rate(self.settings.SAMPLING_RATE)
  File "C:\Users\Anna\Documents\Wiigwaas\Titta\titta\Tobii.py", line 1748, in set_sample_rate
    assert np.any([int(i) == Fs for i in self.buffer.supported_frequencies]), "Supported frequencies are: {}".format(self.buffer.supported_frequencies)
AssertionError: Supported frequencies are: [30.0, 60.0]

I'm not sure exactly where these self.buffer.supported_frequencies are determined, but if 120 isn't among them, should it be the default for TPF (while we just change it to 60 locally)? Or should I make a PR changing it to 60?

Metadata

Metadata

Assignees

Labels

in-labNeeds to be done at Stores i.e., requires the eye tracker.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions