yafu.pl Usage Currently

[EdH]

Are there many users working on the composites in the db currently? I'm just bringing some of my computers back on line and looking for a direction for the short term. I was thinking of running yafu.pl on some of them for a bit. Is there a thread dedicated to this area? Is there something I should do to avoid "stepping" on others' work? Is the randomness of the script enough to make that a rarity?

Would working on Primo certificates be of more use than composites?

[henryzz]

Originally Posted by EdH

Are there many users working on the composites in the db currently? I'm just bringing some of my computers back on line and looking for a direction for the short term. I was thinking of running yafu.pl on some of them for a bit. Is there a thread dedicated to this area? Is there something I should do to avoid "stepping" on others' work? Is the randomness of the script enough to make that a rarity?

Would working on Primo certificates be of more use than composites?

Does the database accept the latest Primo certificates yet?

[EdH]

Originally Posted by henryzz

Does the database accept the latest Primo certificates yet?

Well, since the published version of yafu.pl won't retrieve composites for me and Primo has updated past usefulness with the db, I guess I'll go play somewhere else...

[chris2be8]

I'm running scripts to the same effect as yafu.pl (they use my GPU for ecm and polynomial selection stage 1, which complicates them) on a couple of old PCs. But I'm barely keeping up with the rate numbers are added to factordb so would be very glad for some help.

There's enough randomness in yafu.pl to make collisions rare enough not to matter.

Chris

[henryzz]

Originally Posted by EdH

Well, since the published version of yafu.pl won't retrieve composites for me and Primo has updated past usefulness with the db, I guess I'll go play somewhere else...

You do need to switch the script to factordb.com rather than the old address.

[Puzzle-Peter]

Originally Posted by EdH

Well, since the published version of yafu.pl won't retrieve composites for me and Primo has updated past usefulness with the db, I guess I'll go play somewhere else...

What about using an older primo version? 4.1.1 and older are working fine and factordb can read the certificates.

[Antonio]

Originally Posted by EdH

Are there many users working on the composites in the db currently? I'm just bringing some of my computers back on line and looking for a direction for the short term. I was thinking of running yafu.pl on some of them for a bit. Is there a thread dedicated to this area? Is there something I should do to avoid "stepping" on others' work? Is the randomness of the script enough to make that a rarity?

Would working on Primo certificates be of more use than composites?

You could always try the perl script mentioned here http://mersenneforum.org/showpost.ph...9&postcount=38, it will give you some control over the composites you work on.

[EdH]

Originally Posted by chris2be8

I'm running scripts to the same effect as yafu.pl (they use my GPU for ecm and polynomial selection stage 1, which complicates them) on a couple of old PCs. But I'm barely keeping up with the rate numbers are added to factordb so would be very glad for some help.

There's enough randomness in yafu.pl to make collisions rare enough not to matter.

Chris

I will run yafu.pl for a while and see if I can help knock down some composites. My machines are not yet up fully and not on 24/7 for now, but they still should help some.

Originally Posted by henryzz

You do need to switch the script to factordb.com rather than the old address.

That was the first thing I did yesterday and it still wouldn't run. Oddly, though, tonight it worked flawlessly. I did have to remember to change both instances.

Originally Posted by Puzzle-Peter

What about using an older primo version? 4.1.1 and older are working fine and factordb can read the certificates.

I thought of that and some of my machines that aren't yet back on are all set with earlier versions. Maybe when I bring them back up. At least for now, I have yafu.pl running.

Originally Posted by Antonio

You could always try the perl script mentioned here http://mersenneforum.org/showpost.ph...9&postcount=38, it will give you some control over the composites you work on.

Thanks. For now I'll run yafu.pl, but look at yours and maybe swap when I have a chance.

Thanks everyone.

[EdH]

Hmmm, I turn several machines toward composite factoring via yafu.pl and the composite list increases by 100k! Am I running something backwards? Ok, let's bring some more on line and see if that causes an even larger increase...

[pinhodecarlos]

Could you post a step by step guide how to run the Yafu.pl with links to programs?
Thank you in advance.
Carlos

[EdH]

Originally Posted by pinhodecarlos

Could you post a step by step guide how to run the Yafu.pl with links to programs?
Thank you in advance.
Carlos

All of the following is based on an Ubuntu and a Debian system and uses a terminal:

First, do you currently have a working version of YAFU on your system?

If, yes, then what I have done is make a directory for the work, which I have called yafupl, and placed a copy of the yafu binary and the yafu.ini file in the yafupl directory. I then copied the perl code from here, and placed it in a file called yafu.pl in the same directory.

You might want to change the "-threads 8" to another value, or remove it altogether, as I have, to let your yafu.ini file "threads=" entry prevail. Make sure you leave the "|" character there. You may also want to change the "mindig=" from 10 to something higher than 69, since the db is taking care of <70d composites, if I understand correctly. Based on my next post, you may even want to work higher.

I then cd to the yafupl directory and issue the command:

perl yafu.pl

If you get an error about LWP missing from perl, you might want to look at this page, unless someone else chimes in with better info.

As an alternative, you can look at the script mentioned a few posts earlier by Antonio. I will be looking at the possibility of switching over to it later on.