This project has moved. For the latest updates, please go here.

Issue import raw data from Gazepoint GP3

Jul 1, 2014 at 4:17 PM
Hi Adrian,

I've an issue when I import the Gazepoint rawdata. Ogama wants GazeX and GazeY values, but in Gazepoint Raw file they aren't present.

I've noticed that the Ogama module "record" works fine and the value GazeX and GazeY as corrects.

Which values ​​do you use to get correct GazeX and GazeY data?

Thanks

Francesco
Coordinator
Jul 1, 2014 at 7:07 PM
Hi Francesco,

the gazepoint module uses BPOGX and BPOGY values from the gazepoint Interface
It is configured using
        this.memNetworkManager.SendMessage("<SET ID=\"ENABLE_SEND_POG_BEST\" STATE=\"1\"/> \r\n");
and received using
           // Calculate values between 0..1
            attribute = root.GetAttribute("BPOGX");
            newGazeData.GazePosX = float.Parse(attribute, CultureInfo.InvariantCulture);
            attribute = root.GetAttribute("BPOGY");
            newGazeData.GazePosY = float.Parse(attribute, CultureInfo.InvariantCulture);
Regards, Adrian
Jul 1, 2014 at 9:28 PM
Hi Adrian,

thank you for your answer.

I've tested your solution but unfortunatly it doesn't work. I have noticied that the data in POGX columns are numbers from 0 to 1, when I try plotting these values the circle gets blocked in the upper left corner.

I paste for you a part of the Gazepoint logfile I get.
BPOGX BPOGY BPOGV
0.5508 0.3369 1
0.5508 0.34529 1
0.55057 0.35675 1
0.51799 0.45137 1
0.58615 0.47098 1
0.58581 0.47997 1
0.54308 0.53961 1
0.54741 0.52949 1
0.54729 0.54326 1
0.53162 0.43798 1
0.54715 0.53389 1
0.54713 0.53535 1
0.51841 0.52959 1
0.53162 0.49198 1
0.53145 0.47929 1
0.52875 0.50731 1
0.53016 0.47573 1
0.53001 0.46537 1
0.41868 0.36464 1
0.43164 0.3331 1
0.43162 0.33296 1
0.41908 0.46652 1
0.40892 0.37243 1
0.40984 0.37987 1
0.41985 0.51952 1
0.41416 0.36935 1
0.41429 0.37028 1
0.42091 0.40502 1
Why do I get such output?

I thank you in advance if you would help me.

Francesco
Coordinator
Jul 1, 2014 at 9:42 PM
Hi Francesco,
yes sure, they are normalized, you have to scale them to Screen coordinates yourself. Ogama does this internally using the presentation Screen size:
    // The GazePos data is in values from 0 to 1
    // so scale it to SCREEN COORDINATES
    // and add optional scroll offset
    if (newRawData.GazePosX != null)
    {
        if (newRawData.GazePosX >= 0 && newRawData.GazePosX <= 1)
        {
            newRawData.GazePosX = newRawData.GazePosX * this.xResolution + this.xScrollOffset;
        }
    }

    if (newRawData.GazePosY != null)
    {
        if (newRawData.GazePosY >= 0 && newRawData.GazePosY <= 1)
        {
            newRawData.GazePosY = newRawData.GazePosY * this.yResolution + this.yScrollOffset;
        }
    }
    return newRawData;
Adrian