mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Aliquot Sequences (https://www.mersenneforum.org/forumdisplay.php?f=90)
-   -   Too many merge attempts etc. (https://www.mersenneforum.org/showthread.php?t=11794)

henryzz 2009-05-08 06:17

the fact*.pl scripts by default sieve further i think
if for some reason it is sieving the same range again change factmsieve.pl to sieve on the rational side and try again

jasonp 2009-05-11 04:10

[QUOTE=schickel;172802]I wonder if he's in the same position as last time....just a tiny bit under the required number of realtions. My older c112 jobs, all done completely with GGNFS and the factlat.pl script, required between 7 and 8 million relations.[/QUOTE]
I suspect you're right, I was looking at the results from the merge and they are superficially similar to what you see when there's a lot of oversieving. But if you have almost enough relations I can see a threshold phenomenon where deleting a few relations during the merge causes a cascade of deletions that destroys most of the matrix.

hhh 2009-05-11 04:56

I have got yet another c99 with this problem, and will actively try to figure it out once I find the time. Won`t happen soon though, perhaps in a week or so. Until then, please don`t use too many brain cells on this problem. I am already grateful for all your support. Cheers, H.

hhh 2009-05-14 13:03

1 Attachment(s)
OK, I managed to finish both the stuck c99 and c112, and I have a theory about what was going wrong.

First, my girlfriend shut down the computer/closed the window/whatever [U]during some filtering run[/U]. As the process was killed in action, the files spairs.out, something.add and so on failed to get deleted, and the jobfiles remained untouched. I restarted aliqueit, and sieving was carried out [U]once again on the same spot[/U], resulting in loads of duplicates. For some reason, msieve didn't like to be fed with the same stuff over and over, and threw up by dint of the merge attempts error. After this, the perlscript [U]still [/U] didn't clean up all the mess, which I had to do manually. So, I deleted

-spairs.out which was huge
-*.add (forgot the name)
- the job.T1 and job.T2 files

and adjusted the job file to some higher range. From now, everything went fine. Yet, I don't know if the new, last sieving run was indeed necessary or if a minuscule chunk would have been enough to put things in order again.

Thanks for your help again, pals, I will just post the logfiles (with annotations inside), so you can confirm of reject my theory... I wonder if something can be easily implemented into the perlscript or aliqueit in order to go around this kind of annoying behaviour.


H.

hhh 2009-05-14 13:04

1 Attachment(s)
:juggle:

mklasson 2009-05-14 15:29

[QUOTE=hhh;173514]I wonder if something can be easily implemented into the perlscript or aliqueit in order to go around this kind of annoying behaviour.[/QUOTE]

I recall someone (you?) asking me to fix resuming partial ggnfs sieving in aliqueit earlier, and I must confess I've been annoyed by it as well. I think someone even posted the exact details of what needs to be done to fix it, so maybe I can include that in an upcoming release.

Andi47 2009-05-14 19:54

[QUOTE=mklasson;173528]I recall someone (you?) asking me to fix resuming partial ggnfs sieving in aliqueit earlier, and I must confess I've been annoyed by it as well. I think someone even posted the exact details of what needs to be done to fix it, so maybe I can include that in an upcoming release.[/QUOTE]

This might have been me, who has asked - and if I remember correctly, the answer has been posted to the aliqueit.exe discussion thread.


All times are UTC. The time now is 08:16.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.