I'm experiencing a very strange issue when inserting and/or pasting lines into IDeA. I've held off reporting this problem until I was sure it wasn't an isolated incident. I've seen it happen in multiple projects and in multiple trees.
To summarize what's happening all I can say is that some moves are being added to the tree and others aren't and the net result is that lines that are inserted or pasted are not being added to the tree correctly which leads to a very broken tree. After clicking All Positions there are usually far too many tasks created for the number of new moves and after minimax completes, the lines that were inserted or pasted are "broken". Attached is sequence of screenshots compiled into a single image that demonstrates what I'm talking about. (I apologize, the picture is rather large)
To summarize what's happening all I can say is that some moves are being added to the tree and others aren't and the net result is that lines that are inserted or pasted are not being added to the tree correctly which leads to a very broken tree. After clicking All Positions there are usually far too many tasks created for the number of new moves and after minimax completes, the lines that were inserted or pasted are "broken". Attached is sequence of screenshots compiled into a single image that demonstrates what I'm talking about. (I apologize, the picture is rather large)
![[gr]](/mwf/v12/flags/gr.png "Greece")
some thoughts
i have noticed, that if you press all positions add a move and press all positions again, then you will have double the positions in the queue. Probably IDEA checks the new tasks only against the tree, and not for duplicates in the task queue.
Sometimes, when you press allpositions, or current position, and IDEA is busy writing to the tree, it ignores it, and does not schedule the positions. So i guess this is what happened
>far too many tasks created for the number of new moves
i have noticed, that if you press all positions add a move and press all positions again, then you will have double the positions in the queue. Probably IDEA checks the new tasks only against the tree, and not for duplicates in the task queue.
> the lines that were inserted or pasted are "broken". Attached is sequence of screenshots compiled into a single image that demonstrates what I'm talking about. (I apologize, the picture is rather large)
Sometimes, when you press allpositions, or current position, and IDEA is busy writing to the tree, it ignores it, and does not schedule the positions. So i guess this is what happened
> Sometimes, when you press allpositions, or current position, and IDEA is busy writing to the tree, it ignores it, and does not schedule the positions. So i guess this is what happened
If this is what is causing the problem is it fair to assume that the more engines you have running (and writing to the tree) the more likely it is to happen? Hopefully this is something that can addressed with a patch?
Oddly enough, it seems like color marking and unmarking might be an inconvenient work around. For whatever reason, marking the "missing" moves seems to let minimax know the moves are there....
> If this is what is causing the problem is it fair to assume that the more engines you have running (and writing to the tree) the more likely it is to happen?
probably, this is why i set a minimum time for each task 2-3 secs. This way it does not happen often (rarely i would say)
![[gb]](/mwf/v12/flags/gb.png "United Kingdom")
If the notation pane has subvariations, I can press All Positions, a number in red is added to the tasks, then after a while - without my doing anything else - when I press All Positions again, it finds some more tasks. In some cases I can press All Positions again and again (sometimes with minutes in between), and more tasks are added. I'm not sure whether to trust the Auto-play button either.
as i said above
This means if you press 2 times Allpositions, before the positions are calculated and inserted into the tree, then they will be added to the queue again. At least this is what i found out.
I guess it should check the queue list too, but it doesn't
>Probably IDEA checks the new tasks only against the tree, and not for duplicates in the task queue.
This means if you press 2 times Allpositions, before the positions are calculated and inserted into the tree, then they will be added to the queue again. At least this is what i found out.
I guess it should check the queue list too, but it doesn't
I noticed that IDeA writes to a log file for each task and I can't help wondering if it might help to disable this logging since the information isn't very useful. Is it possible that this logging might be competing with the Tree writes for I/O and perhaps contributing to the problem?
My idea.log file is 16mb w/ 278k lines that mostly look like this:
[12/17/2009 4:26:33 PM] Task sent: project 27, task 466552
P.S.
I looked through the various config files to see if I could find a way to disable the logging but couldn't find it. Is it possible to disable this on the client side?
My idea.log file is 16mb w/ 278k lines that mostly look like this:
[12/17/2009 4:26:33 PM] Task sent: project 27, task 466552
P.S.
I looked through the various config files to see if I could find a way to disable the logging but couldn't find it. Is it possible to disable this on the client side?
you are right. i dont see any reason to keep that log for a normal user.
> I'm not sure whether to trust the Auto-play button either.
I hadn't gotten around to testing Auto-play yet but after reading your message I gave it a try and can confirm that it doesn't seem to be working. Adding Alternative moves is also spotty -- sometimes it works, sometimes it refuses to generate a new task no matter what I do. There are still some bugs here that need to be worked out.
![[fi]](/mwf/v12/flags/fi.png "Finland")
> Adding Alternative moves is also spotty -- sometimes it works, sometimes it refuses to generate a new task no matter what I do.
Note if there's already an Alternative task in the queue, a new task would be a no-op.
![[us]](/mwf/v12/flags/us.png "United States")
I experience the same problem when pasting lines into IDEA.
![[ph]](/mwf/v12/flags/ph.png "Philippines")
I usually merge several games into one game and insert it into the notation window of IDeA.
In Ver. 4.02, sometimes, this works, sometimes it does not. When the game is big, I have to break it up into smaller chunks so I can insert. It is too cumbersome.
Ver. 3.1.1 does not have this problem. Ver 4.02 has this problem.
In Ver. 4.02, sometimes, this works, sometimes it does not. When the game is big, I have to break it up into smaller chunks so I can insert. It is too cumbersome.
Ver. 3.1.1 does not have this problem. Ver 4.02 has this problem.
its known, basically the send games to IDEA feature , does not work for large amount of games (i know.... i really like that procedure :) )
Is there a workaround?
What I do is I maintain an old 3.1.1 version and use it to analyze all the moves in the inserted "big" game. After creating the .elm, .hsh files, I then use the Ver. 4.02 to continue the IDeA analysis.
The problem is I can no longer see which strong grandmaster played which move.
What I do is I maintain an old 3.1.1 version and use it to analyze all the moves in the inserted "big" game. After creating the .elm, .hsh files, I then use the Ver. 4.02 to continue the IDeA analysis.
The problem is I can no longer see which strong grandmaster played which move.
If you are merging many games into one and pasting into IDEA, another workaround is to click 'all positions' again, and again. Eventually all the positions are added to tasks but you have to keep hitting all positions after the original tasks created are analyzed. It's weird.
I was wondering why I would often click "all positions" after pasting "again and again" and would often get much more added positions with Aquarium 4 than the most I knew that I could have added; I guess it isn't just me, then...
Is this something that can be fixed or something we have to live with?
![[ru]](/mwf/v12/flags/ru.png "Russian Federation")
Thanks, we read this.
I agree that something should be changed. And this has the high priority. I am not sure what will be the exact solution but some change will be done in the future release.
I agree that something should be changed. And this has the high priority. I am not sure what will be the exact solution but some change will be done in the future release.
> Thanks, we read this.
>
> I agree that something should be changed. And this has the high priority. I am not sure what will be the exact solution but some change will be done in the future release.
Thank you for the prompt reply and the great product!
Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill