computer-go: [Question] Nullmove

["Xu, Mousheng (SEA)" <moushengxu@xxxxxxxxxxxxxxxx>]

I have been trying to understand the lengthy discussions about nullmove
for a few days, but still have no clue why you guys are interested in
it. So here comes my question.

In a game tree, because of the limitation of computer power, usually you
decide to stop while the width or the depth of the tree reaches a
certain number (say, 3 nodes wide, 4 nodes deep). Since the depth of the
terminal nodes are the same in 99% cases, the terminal evaluation can be
assumed to be equally fair to each node. If I understand correctly, you
guys are talking about to take nullmove into consideration while
evaluating the terminal node so that the evaluation is closer to
reality. But why do you care about the absolute values of your
evaluation? You only care about the relative order of the evaluations,
right? 

I am sure I am missing something.

Thanks.

-- Mousheng Xu