[zbmethod] Re: Search codes to be put in a .txt file
Yes I agree. Well in addition to the desired masks, it is probably best to also do a general (no mask) search. I can run an entire COLL category for you guys, just prepare the input lines, so I don't have to think about it. E-mail them to me at d_funny007 [at] yahoo. 1 COLL times 12 edge possibilites (though usually less) times 4 maskings times 3 metrics is 144 (though typically half due to symmetries) ACube runs per COLL... this is rediculous (although I can do one in one night if need be). We need to take out STM and one of the masks, you see we don't really lose much, it usualy happens that the nice RUF or URD algs come through in the general search. (RUL algs are genereal too far away from optimal to catch in the general serach) If we just do RULM and a general search, each in FTM only then it's only 24 outputs to sort through per COLL case (and thare are not too many COLLs). Only if there is some serious problems with finding a good one there should we go farther. But this is my opinion only, and I acknowledge that being part of a group means that I will have to do what ever task is assigned to me. Thus I await school to be over so that someone from self- selected "group A" gives me concrete instructions. Until then I will continue posting my "no CP" algs, which have been in my notes and gone through a few years of evolution. Also, if no one wants to do this task, I guess I can spend time coding something that will generate a lot of input lines. But that will take up a lot of my time. Ok perhaps someone here has time, and wants to take up a chunk of the ZBLL and type out the input lines for them. And before you run them, e-mail them to me and if I'm not terribly busy I bet I will beat your computer to it. (don't take my enthusiasm the wrong way) Also, just to get started with things (as we wait for further direction from our fearless leader), could some one go through T1 timings for Chris's page, look at his T5 algs, and also my L1 algs that I posted earlier, as well as the ones someone else posted earlier at http://www.belgiancubes.be/zbll/ for diagonal CP H- Orientaion cases. -Doug --- In zbmethod@yahoogroups.com, Gilles van den Peereboom <[EMAIL PROTECTED]> wrote: > > I think that searching with too many masks will just take forever. > We need to balance the qualitity of our work and the progress (after all, > there are still quite a lot of cases). > > I'm kind of happy with these masks ( RULM, RUF, URD). > I don't know how to use ACube very well, I don't even know how to put a > mask. WHat I do is I just ask him a solution and then I work on it to be > able to do it a bit faster but this might not be the best approach. > > Gilles. > > 2005/12/13, Doug Lee <[EMAIL PROTECTED]>: > > > > Who here wants STM optimized algs? We aren't Corners First people > > here, I used to search only in STM on principle, but I no longer > > feel it holds much potential. I use it a lot for my ELL though, but > > that's totally different. > > > > I think it's better to look at the output of a QTM or HTM set, and > > look for those that then lowest in STM. > > > > This times 3 factor is a bit daunting for the timespan I imagine. It > > would be great if we could get all the Acube outputs generated very > > early on and then have everybody filter through it. > > > > I think > > RULM = 431, > > RUF = 510, > > URD = 610, > > and general search > > would be enough. I have a thing for URD type ones. > > > > > > -Doug > > > > > > > > --- In zbmethod@yahoogroups.com, "cmhardw" <[EMAIL PROTECTED]> wrote: > > > > > > Yeah I agree, using each turn mask all the time would make this > > take > > > forever. > > > > > > For cases that are really bad I try a lot of those different turn > > > masks though too to try to find something. > > > > > > I wouldn't throw out RULM, or maybe I can do all the RULM searches, > > > since some of my best ZBLL algs use M turns in an otherwise RUL > > type > > > alg too. > > > > > > This is where we need to find out what type of turns we all like > > the > > > most, and try to accomodate everyone. > > > > > > Actualyl it will take longer for just RUL searches, but will > > include > > > RULM moves too, maybe Doug we could condense the RUL into RULM and > > be > > > left with > > > > > > RULM = 431 > > > RUF = 510 > > > URD = 610 > > > > > > The problem is I also like RULD = 630 moves and already 4 is > > getting > > > to be too much to do for every case. > > > > > > Perhaps we can restrict to the "all" general searches, and only do > > the > > > other side searches in case one of the cases we try just does not > > have > > > anything good at all. The problem is that if we do these side > > > searches for everything, Doug you may run too many searches. Say > > the > > > RUL algs for one case stink, but the general includes an optimal > > alg > > > that is awesome? We have then wasted that search time. > > > > > > I think getting just the QTM
Re: [zbmethod] Re: Search codes to be put in a .txt file
I think that searching with too many masks will just take forever.We need to balance the qualitity of our work and the progress (after all, there are still quite a lot of cases).I'm kind of happy with these masks ( RULM, RUF, URD).I don't know how to use ACube very well, I don't even know how to put a mask. WHat I do is I just ask him a solution and then I work on it to be able to do it a bit faster but this might not be the best approach. Gilles.2005/12/13, Doug Lee <[EMAIL PROTECTED]>: Who here wants STM optimized algs? We aren't Corners First people here, I used to search only in STM on principle, but I no longer feel it holds much potential. I use it a lot for my ELL though, but that's totally different. I think it's better to look at the output of a QTM or HTM set, and look for those that then lowest in STM. This times 3 factor is a bit daunting for the timespan I imagine. It would be great if we could get all the Acube outputs generated very early on and then have everybody filter through it. I think RULM = 431, RUF = 510, URD = 610, and general search would be enough. I have a thing for URD type ones. -Doug --- In zbmethod@yahoogroups.com, "cmhardw" <[EMAIL PROTECTED]> wrote: > > Yeah I agree, using each turn mask all the time would make this take > forever. > > For cases that are really bad I try a lot of those different turn > masks though too to try to find something. > > I wouldn't throw out RULM, or maybe I can do all the RULM searches, > since some of my best ZBLL algs use M turns in an otherwise RUL type > alg too. > > This is where we need to find out what type of turns we all like the > most, and try to accomodate everyone. > > Actualyl it will take longer for just RUL searches, but will include > RULM moves too, maybe Doug we could condense the RUL into RULM and be > left with > > RULM = 431 > RUF = 510 > URD = 610 > > The problem is I also like RULD = 630 moves and already 4 is getting > to be too much to do for every case. > > Perhaps we can restrict to the "all" general searches, and only do the > other side searches in case one of the cases we try just does not have > anything good at all. The problem is that if we do these side > searches for everything, Doug you may run too many searches. Say the > RUL algs for one case stink, but the general includes an optimal alg > that is awesome? We have then wasted that search time. > > I think getting just the QTM/HTM/STM searches for each case would be > an ok starting point. From there STM solvers, HTM solvers, etc. can > search for the ones they like and if the algs stink, then individualyl > we can go through and search for lots of different metrics to find a > good alg. > > Chris > > > > Chris > > --- In zbmethod@yahoogroups.com, "Doug Lee" <[EMAIL PROTECTED]> wrote: > > > > That is way too many turnface mask codes. > > We need just 2 or 3. Especially if we are searious about searching > > all 3 metrics (although I sugguest not doing slice metric). > > > > What I tend to do myself is search inf FTM/HTM all the time, and > > then look at the subset of solutions that are lowest in QTM within > > those results. > > > > RUL = 430 > > RULM = 431 > > RUF = 510 > > URD = 610 > > > > Are ones I like, in fact I think RUL is enough, so take out the RULM. > > > > Actually how about just RUL and a general search? Both only in HTM. > > And then we go back thorugh the especially slow cases. > > > > Cuz right now, it looks to me like every little thing you add adds a > > factor into the equation. And this really adds up > > > > > > -Doug > > > > > > > > --- In zbmethod@yahoogroups.com, "cmhardw" <[EMAIL PROTECTED]> wrote: > > > > > > Hey Doug and all searchers, > > > > > > Start ACube with these > > > java -cp ACube3.jar ACube a > > > java -cp ACube3.jar ACube qa > > > java -cp ACube3.jar ACube sa > > > > > > And preface the positions with whichever of these you like. These > > are > > > all the search faces I've ever used. > > > > > > RUL = 430 > > > RULM = 431 > > > RU = 410 > > > LU = 420 > > > RUF = 510 > > > LUF = 520 > > > RUFM = 511 > > > LUFM = 521 > > > RULD = 630 > > > RUFD = 710 > > > LUFD = 720 > > > URD = 610 > > > ULD = 620 > > > MU = 401 (only for EPLL only) > > > MUD = 601 > > > MUR = 411 > > > MUL = 421 > > > > > > My style is heavily RULM influenced, so will be these face > > groupings. > > > Please add any that I have left out that you all use. > > > > > > Everyone searching a case please put in the ACube codes for the > > > position and preface it with the face groupings you like most. > > > > > > Now we need to know exactly who is searching which cases? I can do > > > the T cases, since I already have a lot of my output files still > > from > > > those. For some reason my command window (where I run ACube) won't > > > let me copy text, so I'll make .jpgs of my screen captures for the > > > search data I still have. > > > > > > Nobo
[zbmethod] Re: Search codes to be put in a .txt file
Who here wants STM optimized algs? We aren't Corners First people here, I used to search only in STM on principle, but I no longer feel it holds much potential. I use it a lot for my ELL though, but that's totally different. I think it's better to look at the output of a QTM or HTM set, and look for those that then lowest in STM. This times 3 factor is a bit daunting for the timespan I imagine. It would be great if we could get all the Acube outputs generated very early on and then have everybody filter through it. I think RULM = 431, RUF = 510, URD = 610, and general search would be enough. I have a thing for URD type ones. -Doug --- In zbmethod@yahoogroups.com, "cmhardw" <[EMAIL PROTECTED]> wrote: > > Yeah I agree, using each turn mask all the time would make this take > forever. > > For cases that are really bad I try a lot of those different turn > masks though too to try to find something. > > I wouldn't throw out RULM, or maybe I can do all the RULM searches, > since some of my best ZBLL algs use M turns in an otherwise RUL type > alg too. > > This is where we need to find out what type of turns we all like the > most, and try to accomodate everyone. > > Actualyl it will take longer for just RUL searches, but will include > RULM moves too, maybe Doug we could condense the RUL into RULM and be > left with > > RULM = 431 > RUF = 510 > URD = 610 > > The problem is I also like RULD = 630 moves and already 4 is getting > to be too much to do for every case. > > Perhaps we can restrict to the "all" general searches, and only do the > other side searches in case one of the cases we try just does not have > anything good at all. The problem is that if we do these side > searches for everything, Doug you may run too many searches. Say the > RUL algs for one case stink, but the general includes an optimal alg > that is awesome? We have then wasted that search time. > > I think getting just the QTM/HTM/STM searches for each case would be > an ok starting point. From there STM solvers, HTM solvers, etc. can > search for the ones they like and if the algs stink, then individualyl > we can go through and search for lots of different metrics to find a > good alg. > > Chris > > > > Chris > > --- In zbmethod@yahoogroups.com, "Doug Lee" <[EMAIL PROTECTED]> wrote: > > > > That is way too many turnface mask codes. > > We need just 2 or 3. Especially if we are searious about searching > > all 3 metrics (although I sugguest not doing slice metric). > > > > What I tend to do myself is search inf FTM/HTM all the time, and > > then look at the subset of solutions that are lowest in QTM within > > those results. > > > > RUL = 430 > > RULM = 431 > > RUF = 510 > > URD = 610 > > > > Are ones I like, in fact I think RUL is enough, so take out the RULM. > > > > Actually how about just RUL and a general search? Both only in HTM. > > And then we go back thorugh the especially slow cases. > > > > Cuz right now, it looks to me like every little thing you add adds a > > factor into the equation. And this really adds up > > > > > > -Doug > > > > > > > > --- In zbmethod@yahoogroups.com, "cmhardw" <[EMAIL PROTECTED]> wrote: > > > > > > Hey Doug and all searchers, > > > > > > Start ACube with these > > > java -cp ACube3.jar ACube a > > > java -cp ACube3.jar ACube qa > > > java -cp ACube3.jar ACube sa > > > > > > And preface the positions with whichever of these you like. These > > are > > > all the search faces I've ever used. > > > > > > RUL = 430 > > > RULM = 431 > > > RU = 410 > > > LU = 420 > > > RUF = 510 > > > LUF = 520 > > > RUFM = 511 > > > LUFM = 521 > > > RULD = 630 > > > RUFD = 710 > > > LUFD = 720 > > > URD = 610 > > > ULD = 620 > > > MU = 401 (only for EPLL only) > > > MUD = 601 > > > MUR = 411 > > > MUL = 421 > > > > > > My style is heavily RULM influenced, so will be these face > > groupings. > > > Please add any that I have left out that you all use. > > > > > > Everyone searching a case please put in the ACube codes for the > > > position and preface it with the face groupings you like most. > > > > > > Now we need to know exactly who is searching which cases? I can do > > > the T cases, since I already have a lot of my output files still > > from > > > those. For some reason my command window (where I run ACube) won't > > > let me copy text, so I'll make .jpgs of my screen captures for the > > > search data I still have. > > > > > > Nobody go too crazy on T cases until I can put up my T searches > > that > > > are already completed (that will save of search time that I've > > already > > > done). > > > > > > Also every who is familiar with ACube put up the codes for your > > > favorite face groupings. If you are not familiar with ACube, > > simply > > > request some face groupings here and one of us will convert it. > > > > > > Chris > > > > > > --- In zbmethod@yahoogroups.com, "Doug Lee" <[EMAIL PROTECTED]> > > wrote: >
[zbmethod] Re: Search codes to be put in a .txt file
Yeah I agree, using each turn mask all the time would make this take forever. For cases that are really bad I try a lot of those different turn masks though too to try to find something. I wouldn't throw out RULM, or maybe I can do all the RULM searches, since some of my best ZBLL algs use M turns in an otherwise RUL type alg too. This is where we need to find out what type of turns we all like the most, and try to accomodate everyone. Actualyl it will take longer for just RUL searches, but will include RULM moves too, maybe Doug we could condense the RUL into RULM and be left with RULM = 431 RUF = 510 URD = 610 The problem is I also like RULD = 630 moves and already 4 is getting to be too much to do for every case. Perhaps we can restrict to the "all" general searches, and only do the other side searches in case one of the cases we try just does not have anything good at all. The problem is that if we do these side searches for everything, Doug you may run too many searches. Say the RUL algs for one case stink, but the general includes an optimal alg that is awesome? We have then wasted that search time. I think getting just the QTM/HTM/STM searches for each case would be an ok starting point. From there STM solvers, HTM solvers, etc. can search for the ones they like and if the algs stink, then individualyl we can go through and search for lots of different metrics to find a good alg. Chris Chris --- In zbmethod@yahoogroups.com, "Doug Lee" <[EMAIL PROTECTED]> wrote: > > That is way too many turnface mask codes. > We need just 2 or 3. Especially if we are searious about searching > all 3 metrics (although I sugguest not doing slice metric). > > What I tend to do myself is search inf FTM/HTM all the time, and > then look at the subset of solutions that are lowest in QTM within > those results. > > RUL = 430 > RULM = 431 > RUF = 510 > URD = 610 > > Are ones I like, in fact I think RUL is enough, so take out the RULM. > > Actually how about just RUL and a general search? Both only in HTM. > And then we go back thorugh the especially slow cases. > > Cuz right now, it looks to me like every little thing you add adds a > factor into the equation. And this really adds up > > > -Doug > > > > --- In zbmethod@yahoogroups.com, "cmhardw" <[EMAIL PROTECTED]> wrote: > > > > Hey Doug and all searchers, > > > > Start ACube with these > > java -cp ACube3.jar ACube a > > java -cp ACube3.jar ACube qa > > java -cp ACube3.jar ACube sa > > > > And preface the positions with whichever of these you like. These > are > > all the search faces I've ever used. > > > > RUL = 430 > > RULM = 431 > > RU = 410 > > LU = 420 > > RUF = 510 > > LUF = 520 > > RUFM = 511 > > LUFM = 521 > > RULD = 630 > > RUFD = 710 > > LUFD = 720 > > URD = 610 > > ULD = 620 > > MU = 401 (only for EPLL only) > > MUD = 601 > > MUR = 411 > > MUL = 421 > > > > My style is heavily RULM influenced, so will be these face > groupings. > > Please add any that I have left out that you all use. > > > > Everyone searching a case please put in the ACube codes for the > > position and preface it with the face groupings you like most. > > > > Now we need to know exactly who is searching which cases? I can do > > the T cases, since I already have a lot of my output files still > from > > those. For some reason my command window (where I run ACube) won't > > let me copy text, so I'll make .jpgs of my screen captures for the > > search data I still have. > > > > Nobody go too crazy on T cases until I can put up my T searches > that > > are already completed (that will save of search time that I've > already > > done). > > > > Also every who is familiar with ACube put up the codes for your > > favorite face groupings. If you are not familiar with ACube, > simply > > request some face groupings here and one of us will convert it. > > > > Chris > > > > --- In zbmethod@yahoogroups.com, "Doug Lee" <[EMAIL PROTECTED]> > wrote: > > > > > > Sounds very good. > > > I know that I use the "~U" command too so that it doens't count > the > > > U turn as part of the length when searching. > > > I am very strong when it comes to parsing data, writting > parsers, > > > writting scripts that will turn the ACube output directly into a > > > webpage layout, stuff like that. > > > So you guys don't have to worry about filtering through data > besides > > > making them all triggerific! > > > > > > We need someone to write up a bunch of txt files with all the > input > > > strings. Perhaps even separated into q,h,s metrics. But > organized in > > > a really nice way. > > > > > > It looks like it's something that I could run next weekend. > > > > > > Just a lucky coincidence I'm doing a bit of computer lab admin > this > > > weeka and setting up 20 brand new workstations (multi-processor) > > > that should help out big time. > > > > > > I've been running ACube for over 6 years now, so I know how it's > > > done. > > > > > >
[zbmethod] Re: Search codes to be put in a .txt file
That is way too many turnface mask codes. We need just 2 or 3. Especially if we are searious about searching all 3 metrics (although I sugguest not doing slice metric). What I tend to do myself is search inf FTM/HTM all the time, and then look at the subset of solutions that are lowest in QTM within those results. RUL = 430 RULM = 431 RUF = 510 URD = 610 Are ones I like, in fact I think RUL is enough, so take out the RULM. Actually how about just RUL and a general search? Both only in HTM. And then we go back thorugh the especially slow cases. Cuz right now, it looks to me like every little thing you add adds a factor into the equation. And this really adds up -Doug --- In zbmethod@yahoogroups.com, "cmhardw" <[EMAIL PROTECTED]> wrote: > > Hey Doug and all searchers, > > Start ACube with these > java -cp ACube3.jar ACube a > java -cp ACube3.jar ACube qa > java -cp ACube3.jar ACube sa > > And preface the positions with whichever of these you like. These are > all the search faces I've ever used. > > RUL = 430 > RULM = 431 > RU = 410 > LU = 420 > RUF = 510 > LUF = 520 > RUFM = 511 > LUFM = 521 > RULD = 630 > RUFD = 710 > LUFD = 720 > URD = 610 > ULD = 620 > MU = 401 (only for EPLL only) > MUD = 601 > MUR = 411 > MUL = 421 > > My style is heavily RULM influenced, so will be these face groupings. > Please add any that I have left out that you all use. > > Everyone searching a case please put in the ACube codes for the > position and preface it with the face groupings you like most. > > Now we need to know exactly who is searching which cases? I can do > the T cases, since I already have a lot of my output files still from > those. For some reason my command window (where I run ACube) won't > let me copy text, so I'll make .jpgs of my screen captures for the > search data I still have. > > Nobody go too crazy on T cases until I can put up my T searches that > are already completed (that will save of search time that I've already > done). > > Also every who is familiar with ACube put up the codes for your > favorite face groupings. If you are not familiar with ACube, simply > request some face groupings here and one of us will convert it. > > Chris > > --- In zbmethod@yahoogroups.com, "Doug Lee" <[EMAIL PROTECTED]> wrote: > > > > Sounds very good. > > I know that I use the "~U" command too so that it doens't count the > > U turn as part of the length when searching. > > I am very strong when it comes to parsing data, writting parsers, > > writting scripts that will turn the ACube output directly into a > > webpage layout, stuff like that. > > So you guys don't have to worry about filtering through data besides > > making them all triggerific! > > > > We need someone to write up a bunch of txt files with all the input > > strings. Perhaps even separated into q,h,s metrics. But organized in > > a really nice way. > > > > It looks like it's something that I could run next weekend. > > > > Just a lucky coincidence I'm doing a bit of computer lab admin this > > weeka and setting up 20 brand new workstations (multi-processor) > > that should help out big time. > > > > I've been running ACube for over 6 years now, so I know how it's > > done. > > > > > > -Doug Li > Yahoo! Groups Sponsor ~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/MXMplB/TM ~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/zbmethod/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
