agen judi bola , sportbook, casino, togel, number game, singapore, tangkas, basket, slot, poker, dominoqq, agen bola
. Semua permainan bisa dimainkan hanya dengan 1 ID. minimal deposit 50.000 ,- bonus cashback hingga 10% , diskon togel hingga 66% bisa bermain di android dan IOS kapanpun dan dimana pun. poker , bandarq , aduq, domino qq , dominobet
. Semua permainan bisa dimainkan hanya dengan 1 ID. minimal deposit 10.000 ,- bonus turnover 0.5% dan bonus referral 20%. Bonus - bonus yang dihadirkan bisa terbilang cukup tinggi dan memuaskan, anda hanya perlu memasang pada situs yang memberikan bursa pasaran terbaik yaitu http://18.104.22.168/
Bola168. Situs penyedia segala jenis permainan poker online kini semakin banyak ditemukan di Internet, salah satunya TahunQQ merupakan situs Agen Judi Domino66 Dan BandarQ Terpercaya
yang mampu memberikan banyak provit bagi bettornya. Permainan Yang Di Sediakan Dewi365 Juga sangat banyak Dan menarik dan Peluang untuk memenangkan Taruhan Judi online ini juga sangat mudah . Mainkan Segera Taruhan Sportbook anda bersama Agen Judi Bola
Bersama Dewi365 Kemenangan Anda Berapa pun akan Terbayarkan. Tersedia 9 macam permainan seru yang bisa kamu mainkan hanya di dalam 1 ID saja. Permainan seru yang tersedia seperti Poker, Domino QQ Dan juga BandarQ Online
. Semuanya tersedia lengkap hanya di ABGQQ. Situs ABGQQ sangat mudah dimenangkan, kamu juga akan mendapatkan mega bonus dan setiap pemain berhak mendapatkan cashback mingguan. ABGQQ juga telah diakui sebagai Bandar Domino Online
yang menjamin sistem FAIR PLAY disetiap permainan yang bisa dimainkan dengan deposit minimal hanya Rp.25.000. DEWI365 adalah Bandar Judi Bola Terpercaya
& resmi dan terpercaya di indonesia. Situs judi bola ini menyediakan fasilitas bagi anda untuk dapat bermain memainkan permainan judi bola. Didalam situs ini memiliki berbagai permainan taruhan bola terlengkap seperti Sbobet, yang membuat DEWI365 menjadi situs judi bola terbaik dan terpercaya di Indonesia. Tentunya sebagai situs yang bertugas sebagai Bandar Poker Online
pastinya akan berusaha untuk menjaga semua informasi dan keamanan yang terdapat di POKERQQ13. Kotakqq adalah situs Judi Poker Online Terpercaya
yang menyediakan 9 jenis permainan sakong online, dominoqq, domino99, bandarq, bandar ceme, aduq, poker online, bandar poker, balak66, perang baccarat, dan capsa susun. Dengan minimal deposit withdraw 15.000 Anda sudah bisa memainkan semua permaina pkv games di situs kami. Jackpot besar,Win rate tinggi, Fair play, PKV Games
Could you upload your experiment and the datafile?
this are the files
You'll have to be a bit more specific. I can see in the experiment that you have a 3000 ms delay between calling
eyetracker.stop_recording(), at least if
display_offsetis 3000 and
post_viewis 0. So I get that point.
But what do you mean by this?
Can you illustrate exactly what you do here, and how you arrive at the values between 1500 and 2500? For example by uploading a datafile and describing what you do with that. And what makes you think that the sample duration is 16 ms?
When I look at the log file, I find that the time difference between star_recoding and end_recording is aproxx 1500 and 2500 ms, instead of 3000 ms,
The 16 ms are for the frequency of the tracker (60hz), within the log file appears sampletime: 16.67 ms.
I apologize I'm new to this, maybe my code is wrong.
What I need to do is for the log file to record 3000 ms of recordings, but for some reason I get different time trials in the log file.
This is puzzling indeed. There's threading involved, which always introduces some jitter. But this seems a bit much, even for Python threading.
Here's what I would try:
This will give you messages in the EyeTribe log file like this:
So the first two timestamps are given by the EyeTribe. The last one (
T1 = ...) is given by OpenSesame. What happens if you do this? Do all timestamps agree on how much time has passed? If not, then which of the following do you see:
- Less than 3000 ms (the EyeTribe thinks that time runs too fast)
- More than 3000 ms (the EyeTribe thinks that time runs too slow)
I have noticed a similar problem in my own experiments. At one point, I did essentially what Sebastian suggested above but I used a sleep time of 5000ms. I measured the time between my logged events, and took the difference between them to get the inter-event interval (IEI). For every experiment I ran, the beginning of each recording had shorter IEIs than what it was supposed to be. Below is a histogram of IEIs of the first 100 samples of my EyeTribe (30Hz sampling rate).
You can see that the majority of the samples are actually shorter than 5000ms, which is the same problem you were having. Here is the same data but plotted as a time series
As you can see, the first 24 samples are shorter than what they were supposed to be. This means the first 10seconds or so of recording will most likely be a little off. The good news is that the IEI gradually moves towards where it is supposed to be.
I have no idea why this happens. The only suggestion I can make is for you to make one long recording (only one start and stop). Start the recording early, have at least 10 seconds or so before you actually start presenting stimuli to avoid this weird effect, and log events to indicate trials.
We have similar timing issues as Guido. Basically, we are running pygaze on a python 2.7.3 on Windows 10 with an EyeTribe eyetracker. We observed a similar difference between the time measured with pygaze.clock (or pygame.time) and the eye tracker. When looking into the validation (of calibration) data we observed that the pattern of eye movements followed the correct timing but the messages (logs) showed to be faster or compressed, and consistently the recording also ends before the indicated time (stop_recording).
After running code similar to the one Sebastiaan suggested we obtained the following output:
Where we observed that the pygame timing is correct, but the eyetribe timing is not.
You can see the code here users.df.uba.ar/juank/eyetracker/experiment.rar
Any help or suggestion is welcome.
I just tested my own Eye Tribe, and (fortunately) I don't experience the problem. I attached the full data file and experiment. Basically, I let a fixation dot jump from left to right and back, three times with a 2000 ms delay. With every displacement I logged the X coordinate and timestamp. You see that OpenSesame and the Eye Tribe perfectly agree, both indicating 2000 ms between each message:
If I plot eye position, it's also clearly accurate, in the sense that my gaze shifts when you would expect it to shift after each displacement.
So that's good.
But this raises the question: Why is synchronization off for you, but not for me? What versions of the relevant software are you using exactly? My test was done with:
The Eye Tribe server reports the following:
@Edwin Do you know where the timestamps in the data file come from? Do they come from the Eye Tribe (along with the gaze data), or from PyGaze?
Thanks @sebastiaan ,
My system is:
Windows 10 Home 64bit
Pygaze 0.5.0 (Downloaded Dec-2016, not sure how to check version... I look into the init.py file)
PS: currently downloading opensesame for checking with your script, thanks