You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi
I didn't have any problems with testing under Ubuntu, but the following situations occurred when testing on windows. I use a graph with a height of 544 and a width of 960 for prediction. What happens is that the Y coordinate is correct, but the X coordinate is offset. The target is in the left half of the graph, and the box is offset to the left. The target is in the right half of the graph, and the box is offset to the right. I saw the result of *det output, x will be greater than 1 and less than 0. When I use a graph with a height of 960 and a width of 544 to predict, what happens is that the X coordinate is correct, the Y coordinate is offset. When the target is in the upper half of the graph, the box will move up. When the target is in the lower part of the graph, the box will be shifted downward.What is the most likely reason for this? Thank you very much.
The text was updated successfully, but these errors were encountered:
hi
I didn't have any problems with testing under Ubuntu, but the following situations occurred when testing on windows. I use a graph with a height of 544 and a width of 960 for prediction. What happens is that the Y coordinate is correct, but the X coordinate is offset. The target is in the left half of the graph, and the box is offset to the left. The target is in the right half of the graph, and the box is offset to the right. I saw the result of *det output, x will be greater than 1 and less than 0. When I use a graph with a height of 960 and a width of 544 to predict, what happens is that the X coordinate is correct, the Y coordinate is offset. When the target is in the upper half of the graph, the box will move up. When the target is in the lower part of the graph, the box will be shifted downward.What is the most likely reason for this? Thank you very much.
The text was updated successfully, but these errors were encountered: