![]() The appropriate light sensor threshold level for the monitor being tested was set by the test script itself. The MilliKey DeLux was configured to generate a USB Serial event after the DeLux light sensor detected the monitor brightness crossed a digital threshold level. The same script was connected to a MilliKey with the DeLux light sensor via USB Serial. The stated response time of the SyncMaster P2770 is 1 msec, which probably means it is closer to 2 msec peak to peak.Ī Python 3 test script used the open source PsychoPå experiment package to make 1000 dark -> light display changes, recording the flip() time of each dark->light change. In this test we used was a Dell G5 15 laptop running Windows 10 with NVIDIA graphics connected to a SyncMaster P2770 LCD monitor. Using the MilliKey DeLux light sensor upgrade and PsychoPå we compared the display update time reported by () to the time the experiment received a 1000 Hz USB serial event triggered by the MilliKey DeLux light sensor in response to each screen brightness change. Windows 10 Monitor Scale Setting 125% results in extra 1 frame (monitor retrace) delay. Windows 10 Monitor Scale Setting 100% results in expected display change timing. When using a 70 Hz monitor for example, this adds an extra 14.3 msec delay, causing the reported display update time to be off by one retrace as well. We have found that if the Windows 10 Display -> Scale (and layout) setting is not set to 100%, the Windows 10 operating system adds an extra frame delay to the actual monitor update time. Self.caliTargetPos, self.It looks like you need to be careful with your display settings in Windows 10, otherwise Windows 10 could be adding an extra frame delay to the display update times reported by your experiment software. That is, if the target is staying on the 5th position in Positions listed in self.calTargetPos or self.valTargetPos. This attlibute holds the order in which calibration target visits This list is internally generated from self.calTaretPos everytime This attribute holds a list of validation target positions. This attribute is set by setCalibrationTargetPositions(). This attribute holds a list of calibration target positions. This attribute is set by setCalibrationTargetStimulus(). This attribute holds stimulus object(s) for drawing calibration target. If you have to access the entire list of calibration target positions, you can refer following data attributes of (). See Sample 05: Custmizing calibration target motion, Configure GazeParser, setCalTargetMotionParams() and setCalSampleAcquisitionParams() for detail. The range of t can be customized in version 0.6.0 by using following parameters. This parameter is equal to targetPosition The position indicated by this parameter.Ī tuple of two values that represents current calibration If the target is moving to or stays on 5th position,Ī tuple of two values. This value is 0 before calibration is initiated by space key This value represents the order of current target position. When 1.0<=t<2.0, the calibration target stays onĬalibration data is sampled when 1.4callback function receives four parameters shown in Table 1. updateCalibrationTargetStimulusCallBack = callback Def callback ( self, t, index, targetPos, currentPos ): if index = 0 : return else : if t < 1.0 : self.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |