We have captured a data of a person walking in front of the sensor up and down. The output of mrr parser is attached below.
Similary we have also run the mrr gui application for the same scenario and we have obtained the following output
On analyzing both the data xSize and ySize is found to be around >1.5m most of the time. For most of the frames xSize and ySize is found to be exactly the same
for example , please find below a sample from the mrr output file attached along with this thread
"data": [ { "x": 24, "y": 2344, "xd": -1, "yd": 0, "xSize": 261, "ySize": 261 }, { "x": 10098, "y": 5701, "xd": 94, "yd": -166, "xSize": 261, "ySize": 261 }, { "x": -19, "y": 2956, "xd": -4, "yd": 0, "xSize": 261, "ySize": 261 }, { "x": 334, "y": 3639, "xd": -7, "yd": 0, "xSize": 234, "ySize": 244 }, { "x": -203, "y": 1274, "xd": 0, "yd": 0, "xSize": 261, "ySize": 261 } ]
The only moving object in the scenario is a person which cannot have width >1.5 m .
We are getting wrong xSize and ySize. From the output of mrr parser we are not at all able to find the width and length of the person walking in the scenario. What is the reason for obtaining this wrong information?