Hello, are there any keypoints/advises when calibrating the HTC Vive eyetracking addon?

On how to get better results

Is there a way to reset the calibration data during Unity's play mode? I'm trying to recalibrate the eye tracker in between trials in case the validator I coded detects that the headset has slipped, but I'm noticing that when I call the calibration routine again, it stops after only 2 or so calibration points and succeeds immediately, but keeps the error. I think the problem would be solved if I could entirely clear the calibration data from the first round of calibration.

I'm tracing the code in hmd-eyes for the calibration. Via Calibration.cs and a few other calibration scripts, it gathers the timestamps associated with each calibration point and then uses the RequestControl script to send this information to something outside of unity I think. Am I right on this? Where's the data being sent? And where in the code is the calibration actually being calculated?

Oh so there's no reason it should ever remember the calibration between runs

@papr so…my PI is saying we have to validate that the eye tracker works binocularly, and the proposed way to do that is to do two calibrations, where each eye is blocked off, and the calibration routine is run per eye; afterwards, we take the calibration results per eye and combine them.

I was thinking of trying to do this for live calibrations in 3D-hmd, and I think we’ve talked about how to get and set the calibration parameters per eye via messages, but I’m having trouble doing so (I don’t think I have the right subject)

The other option was post-hoc calibration, but I’m unfamiliar with how post-hoc calibration works

Happy New Year to everyone. I have a few questions about how to use Pupil Labs in VR, but first of all, is there anyone that can tell me if by any chance the results of the pupil labs are time-variable? or it can only collectively tell you which points have caught more attention?!