Merge equals positions

Post Reply
mafutrct
Posts: 25
Joined: Sat Dec 13, 2008 6:38 am
Contact:

Merge equals positions

Post by mafutrct »

As far as I know, equal positions that arise by a different move order (or by passes) do not lead to the same database entry. That's an important feature that should by implemented to avoid doubled work.
User avatar
adum
Site Admin
Posts: 398
Joined: Tue Sep 30, 2008 5:09 pm

Re: Merge equals positions

Post by adum »

this is a good idea -- i have this for goproblems, and it would work well in josekipedia too. it's a bit tricky right now but someday i'd like to do it.
mafutrct
Posts: 25
Joined: Sat Dec 13, 2008 6:38 am
Contact:

Re: Merge equals positions

Post by mafutrct »

status?
User avatar
adum
Site Admin
Posts: 398
Joined: Tue Sep 30, 2008 5:09 pm

Re: Merge equals positions

Post by adum »

no progress yet...
dracula
Posts: 6
Joined: Tue Feb 11, 2014 8:10 pm

Re: Merge equals positions

Post by dracula »

The main advantage of this feature isn't even avoiding duplicated effort but in making sure there aren't duplicates of a position having different sets of follow up moves and being seen by different eyes. Also, someone who's an expert on a certain position shouldn't have to hunt around for every example where the position comes up.
k0n0
Posts: 2
Joined: Wed Sep 01, 2021 10:55 pm

Re: Merge equals positions

Post by k0n0 »

adum wrote:this is a good idea -- i have this for goproblems, and it would work well in josekipedia too. it's a bit tricky right now but someday i'd like to do it.


A user should be informed about all the variations that lead to the merged node. How do you want to achieve it?
Post Reply