![[in]](/mwf/v12/flags/in.png "India")
In Build 409, positions analyzed in the current stage are not immediately visible. I spent a lot of time searching all over my notation, and finally thought I had missed to add that position. Then I just did a minimax, and lo, that position appeared in the tree. Is this the intended behavior or a bug?
Consequence: one will always have to do a minimax before going through the tree!
Problem: One would like to see whether the positions added manually were significant or not, before it is minimaxed?
Consequence: one will always have to do a minimax before going through the tree!
Problem: One would like to see whether the positions added manually were significant or not, before it is minimaxed?
I reverted back to 4.06, but yes, I am following this thread with interest.
![[gb]](/mwf/v12/flags/gb.png "United Kingdom")
To put it another way...back to the drawing board.....again 
Yesterday, I had observed this problem a few times, but today I am not finding it! Perhaps it has something to do with a particular project or tree or some condition, I have not been able to identify.
![[ru]](/mwf/v12/flags/ru.png "Russian Federation")
1) Sometimes in the projects with short analysis time Aquarium is not able to read and display data in time as a tree is busy for writting.
2) Unlike 4.0.6 the current 4.0.7 release is free of the problem not showing just analyzed moves and evaluations before minimaxing. But in any case you can avoid the described problem by ticking off "Show main tree moves only" check box in IDeA tree configuration.
2) Unlike 4.0.6 the current 4.0.7 release is free of the problem not showing just analyzed moves and evaluations before minimaxing. But in any case you can avoid the described problem by ticking off "Show main tree moves only" check box in IDeA tree configuration.
> the current 4.0.7 release is free of the problem
Thank you for the reply. I thought I was using 4.0.7, but now I am not sure... I will report if I observe it again.
![[is]](/mwf/v12/flags/is.png "Iceland")
> I thought I was using 4.0.7, but now I am not sure...
How about finding out if you were using build 409 or not and letting us know?
> How about finding out if you were using build 409 or not and letting us know?
Sorry, I use 2 systems connected to a single monitor. The same position was being analyzed by 2 different engines and I was feeding the results from one system to another. I had loaded Build 409 in one system only. Since I had never observed the reported behavior in Build 385, I thought the problem must be in Build 409. Since I was not able to replicate the problem later, I am confused which system showed the problem! Now I have loaded Build 409 in both systems, so please wait till I get the problem again!.
This is to confirm that the problem is with Build 409, see screenshot below.
In this case, the analysis time was 180 s minimum, so there is no question of lack of time.
I checked my tree configuration, and "Show main tree moves only" is not ticked. I think the default option is not ticked, and I have never ticked it.
> 1) Sometimes in the projects with short analysis time Aquarium is not able to read and display data in time as a tree is busy for writting.
In this case, the analysis time was 180 s minimum, so there is no question of lack of time.
> in any case you can avoid the described problem by ticking off "Show main tree moves only"
I checked my tree configuration, and "Show main tree moves only" is not ticked. I think the default option is not ticked, and I have never ticked it.
![[gr]](/mwf/v12/flags/gr.png "Greece")
if you move forward or backwards from the position, does it re-appear?
> if you move forward or backwards from the position, does it re-appear?
That is the usual behavior. Here, that did not happen. Is there any way to reach that position, without clicking on the current task button, or the move in the notation?
what other way. I cannot imagine something else.
Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill