mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Aliquot Sequences (https://www.mersenneforum.org/forumdisplay.php?f=90)
-   -   Subproject #1: 210k-250k sequences to 100 digits (https://www.mersenneforum.org/showthread.php?t=12132)

henryzz 2009-07-08 17:40

Subproject #1: 210k-250k sequences to 100 digits
 
This range was reserved by Wolfgang Creyaufmuller, but he unreserved it due to high energy prices. He had reached about 220k. We have now taken it!

This thread is for reserving 210k-250k sequences to take them up to 100 digits. Once they get past 100 digits, they will either be moved into the main reservation thread, or unreserved based on the user's choice.

Here's a current snapshot on the reservations and status:*
[code][B]Current reservations[/B]

[B]Sequence Who Index Size Driver/Guide[/B]
[/code][B]Sequences below 250k at 80 digits (take as many as you like!):[/B]
None left, have a look in the 500k-600k subproject!

I (henryzz) will usually† do a complete update at the weekend¶, and I will also try to check for reservations and add them to the table every day I read the forum.

[B]Nitpicker's corner[/B]
==============

* "Snapshot" means that I download the current status** of a sequence from Syd's database and check it against the last status. If it's changed it gets updated.

** "Current status" means current as of the instant I hit enter to query the database. Obviously, someone could upload a continuation of a sequence the instant after I query the DB. If that happens, I won't see the continuation unless I look at that one again during that update.

† "Usually" means I will try to do this every week, but if other considerations in Real Life take precedence, it might not happen for a particular week.

¶ "The weekend" means Saturday or Sunday, British time.

Mini-Geek 2009-07-08 18:04

Subproject #1 archive
 
I'm taking 237060 a little. Acquired downdriver at line 489, sz 70, let's see if this piggy will come home. I don't intend to take it farther than 80 or so. Edit: And, just as quickly, it lost the downdriver (bottomed out at sz 67) and is now under the control of a perfect number (2^2*7). I suppose this shouldn't surprise me, since it was on the list at all, and hadn't reached 80 digits in the DB yet, but still :sad: . Unreserving once it hits sz 80. Edit 2: Unreserved at sz 78 with a c76 that started QS. Status in DB.

mataje 2009-07-08 18:37

I reserve 229512, 229752, 229848, 229950 and 234900 sequences to take them up to 100 digits.
edit: added

unconnected 2009-07-08 20:14

Reserve 234768

unconnected 2009-07-08 21:41

[quote=unconnected;180250]Reserve 234768[/quote]
Also reserving 234210.

mataje 2009-07-08 21:51

[quote=unconnected;180256]Also reserving 234210+234900[/quote]234900 is reserved. See my message.

mdettweiler 2009-07-08 22:29

Reserving 238062.

gd_barnes 2009-07-09 00:47

That's confusing. Why limit the >200K reservation thread to just 100 digits? Then it's in 2 places and confuses the issue even more. Just my 2 cents.

Anyway, I still have former reservations from the usual reservations thread:
233324 (now > 100 digits but started at < 100 digits)
280686 (still < 100 digits)

New reservations:
210048
210280
(both > 100 digits)


You see why this will get confusing real fast? I'll go ahead and post the new reservations in the regular reservations thread. I personally always take them to a hard C100 or higher, which means I'll frequently reserve them at sz < 100 digits and take them to sz > 100 digits.

IMHO, we need a one-stop shop of all reservations, just like Karsten's pages. Let's get them all in one place.


Gary

10metreh 2009-07-09 06:59

[quote=gd_barnes;180264]That's confusing. Why limit the >200K reservation thread to just 100 digits? Then it's in 2 places and confuses the issue even more. Just my 2 cents.

Anyway, I still have former reservations from the usual reservations thread:
233324 (now > 100 digits but started at < 100 digits)
280686 (still < 100 digits)

New reservations:
210048
210280
(both > 100 digits)


You see why this will get confusing real fast? I'll go ahead and post the new reservations in the regular reservations thread. I personally always take them to a hard C100 or higher, which means I'll frequently reserve them at sz < 100 digits and take them to sz > 100 digits.

IMHO, we need a one-stop shop of all reservations, just like Karsten's pages. Let's get them all in one place.


Gary[/quote]

If your only intention is to take them to 100 digits and stop when they encounter a large composite, they should go in here. To decide which group you are in, I'll give you a question:

Suppose you reserved a sequence with 2 * 3, only trying to take it to 100 and a big composite, and it escaped the driver at 101 digits. It then lost the 3, leaving it with only 2^2, but it encounters a C102. Do you factor the C102 or stop?

gd_barnes 2009-07-09 08:34

But that's my whole point. Why I have 2 separate listings? If I'm an average searcher, I may not know ahead of time whether I want to take them beyond 100 digits.

Personally, I will always take them higher to a factor that is a hard C>=100 hence the size will always be > 100 but others may not know ahead of time. So does that mean that none of my >200K reservations go here?

So my question again is: What is the reasoning behind 2 listings for the same sequence range? Why not a one-stop shop? I'm curious more than anything how this was decided upon. Did I miss a posting somewhere?

kar_bon 2009-07-09 08:44

as i remember right, this thread was intended to continue the work in the range 100000<n<200000 mostly.
why put all seqs with 200000<n<300000 in here and rename this thread to only "200k Sequences"?

no misunderstanding will occur to where i reserve a seq then!

10metreh 2009-07-09 08:56

[quote=gd_barnes;180300]But that's my whole point. Why I have 2 separate listings? If I'm an average searcher, I may not know ahead of time whether I want to take them beyond 100 digits.

Personally, I will always take them higher to a factor that is a hard C>=100 hence the size will always be > 100 but others may not know ahead of time. So does that mean that none of my >200K reservations go here?

So my question again is: What is the reasoning behind 2 listings for the same sequence range? Why not a one-stop shop? I'm curious more than anything how this was decided upon. Did I miss a posting somewhere?[/quote]

henryzz and I had a discussion via PMs about what we were going to do about the 200k range. We decided that we should have one thread for the sequences that will only go to 100 digits. Wolfgang was working on the 210k-250k range, but he gave up for various reasons, so we've taken the range instead. This means we need to get all the sequences up to 250k to 100 digits. This thread is for the sequences that are part of this project. (Maybe I should make the title clearer.) The main reservations thread is for the sequences that have already reached 100 and are being taken further. Henryzz will keep track of this range.

[B]I am counting this range as high priority, so my advice is: only take sequences beyond 100 if they look good. We need to get more sequences to 100, not get the existing ones to 110.[/B]

So, basically: this thread is for the "210k-250k to 100 digits" subproject of the main project.

kar_bon 2009-07-09 09:07

i've taken some seqs from the upper bound (248k<n<250k) upto about 100 digits but not reserved somewhere, because they don't take so long.
i will continue some more downwards the n-range.

BTW: after checking all new posts here, i'll update the summary with more new data.

gd_barnes 2009-07-09 09:12

Ah, thank you 10metreh. Now I understand the background behind all of this. The name of the thread explains things better now.

It's really a mess...trying to bring together so many other's disparate efforts, several of which it sounds like they are not easily coming off of the files that would have been produced from them. It's a great work that you guys are doing here.

This effort reminds me a little of the "No prime left behind" prime search project that I'm an admin for. We try to fill in the 'holes' of Riesel primes that others have left behind from numerous wide-ranging efforts; hence the name. Besides the mathematical curiosity behind the sequences, the filling in of holes, i.e. sequences that are a little lower searched than their neighbors, kind of drew my attention here.

I didn't realize that I was doing the "low priority" stuff. :-) With the limit I use, I end up testing most to an average size of around 108-112 somewhere. I guess I want to see some of the lower sequences get cracked since there are so many of them, as hopeless as many of them are. I was SO close on 233324. :-)

10metreh 2009-07-09 09:34

As you will see, I have added a list of the unreserved sequences below 230k which have not yet reached 100 digits ("unworked" sequences). There are also four sequences below 230k which have reached 100 but have no files available. If anyone is willing to redo those, I'd be grateful.

Edit: someone's filled them in in the database (I don't know when). Thanks!

mklasson 2009-07-09 12:15

Ooh, fun! I'll take 4: 228504, 229224, 229266, 229516.

mklasson 2009-07-09 14:15

That went well. Pass me two more: 228060, 228366.

bsquared 2009-07-09 14:26

Sheesz, this seems like the place to be!

I'll try 227220.

Mini-Geek 2009-07-09 14:26

Taking 220932 and 221130.

jrk 2009-07-09 17:28

Taking 223632

10metreh 2009-07-09 17:56

One thing: please make it clear when sequences reach 100. Henryzz and I don't spend hours every day looking through Syd's database.

henryzz 2009-07-09 18:12

[quote=10metreh;180363]One thing: please make it clear when sequences reach 100. Henryzz and I don't spend hours every day looking through Syd's database.[/quote]
agreed although i will probably keep an eye on the sequences near 100 digits

also something that need clearing up:
when i add a reservation i check its status in the database i have often found in this thread that there is only 50 iterations there or maybe the sequence starter has been run in the database
what should i do?
there seems little point in adding status when it doesn't even go to 10 digits
when should i start adding status for a sequence?
please bear in mind that it takes time to add the status for a sequence and 10metreh and i don't want to spend all day adding useless statuses when you reserve several sequences
i would feel inclined to say not to bother before 80 digits since it doesnt take me long to get up to there

50 digits is what i have been doing so far

Batalov 2009-07-09 18:15

228042 sounds like fun.

10metreh 2009-07-09 18:27

[quote=henryzz;180364]agreed although i will probably keep an eye on the sequences near 100 digits

also something that need clearing up:
when i add a reservation i check its status in the database i have often found in this thread that there is only 50 iterations there or maybe the sequence starter has been run in the database
what should i do?
there seems little point in adding status when it doesn't even go to 10 digits
when should i start adding status for a sequence?
please bear in mind that it takes time to add the status for a sequence and 10metreh and i don't want to spend all day adding useless statuses when you reserve several sequences
i would feel inclined to say not to bother before 80 digits since it doesnt take me long to get up to there

50 digits is what i have been doing so far[/quote]

I would only update statuses if they have reached 70 digits, but I wouldn't update as soon as somebody reserves a sequence. IMO it takes up too much time.

henryzz 2009-07-09 18:28

[quote=bsquared;180344]Sheesz, this seems like the place to be!

I'll try 227220.[/quote]
not for a mod:smile:
for the opposite reason
its more work for us:smile:

10metreh 2009-07-09 18:32

Henryzz, a couple of notes on the colours: 2 * 3^2 is red not blue: it is a variant of 2 * 3. 2^2 * 3 * 5 is blue not red.

henryzz 2009-07-09 18:33

[quote=10metreh;180366]I would only update statuses if they have reached 70 digits, but I wouldn't update as soon as somebody reserves a sequence. IMO it takes up too much time.[/quote]
good idea
should we only do it at the major updates?
i am now realizing that doing statusing takes up quite a bit of time

10metreh 2009-07-09 18:40

[quote=henryzz;180371]good idea
should we only do it at the major updates?
i am now realizing that doing statusing takes up quite a bit of time[/quote]

Fine, just at the weekend if you like it that way.

bsquared 2009-07-09 18:41

[quote=henryzz;180371]good idea
should we only do it at the major updates?
i am now realizing that doing statusing takes up quite a bit of time[/quote]

It would be super if reservations could be handled thusly:
[URL]http://www.chiark.greenend.org.uk/ucgi/~twomack/homcun.pl[/URL]

I imagine that would help your workload a bit.

As for statuses (statusi? stati? whatever), in theory there is a query for anything with a database. A stored procedure which crawled a list of the currently reserved sequences could be run once a day, returning you a block of text which you could paste into the forum, and this whole business could be automated. But where's the fun in that, once the scripts are written?

- ben.

Batalov 2009-07-09 18:59

Will play with 224560, too.

Greebley 2009-07-09 21:23

I will start working on the 240xxx which is:
240030, 240096, 240120, 240378, 240432, 2240480, 240792, 240810

unconnected 2009-07-09 21:32

234768 i=728 size 106 C104
234210 i=902 size 106 C103

Both seqs uploaded to DB, but for 234768 something strange happens at i=602 and rest is not loaded yet. How to fix this?

Taking 227010 and 227200 next.

KriZp 2009-07-09 21:45

I'll take 223398

Batalov 2009-07-09 22:03

I'll play with 221472, 222558, 222834, 223000, 223632, 223692, 224508

mklasson 2009-07-09 22:13

229224, 229516, 228060, 228366 all made it to 100 digits unharmed and 228504 will be there within the hour most likely.

Taking 224520, 225570, 226764, 227160.

kar_bon 2009-07-09 22:14

[QUOTE=unconnected;180394]Both seqs uploaded to DB, but for 234768 something strange happens at i=602 and rest is not loaded yet. How to fix this?
[/QUOTE]

you can't do anything, the error is known by Syd (Database guru), he has to fix it manually!
you could only PM him!

[QUOTE=Batalov;180396]I'll play with 221472, 222558, 222834, 223000, 223632, 223692, 224508[/QUOTE]

223632 res. by jrk!

[b]@mklasson: for 228060 there're only up to index 645 (size 75) in the database. please update![/b]

BTW:
i've decided to let the reserved for this thread in the place they are on the summary page and not to show them on top of the page.
too much copy/paste for so much seqs and not so long reservation timings!

Batalov 2009-07-09 22:50

[quote=kar_bon;180401]223632 res. by jrk![/quote]
Yes, indeed. We need a better reservation system, quite apparently.
Anyway, in case jrk is reading - it is at index 1034 already.

PM me for the last line.
(FactorDB is stuck on an error in this sequence as well.)

mataje 2009-07-09 22:51

I´ll take 237096, 237384, 237600, 237888, 238212 and 238476.

gd_barnes 2009-07-10 00:41

Henry,

Ah, I see by your comment about doing statuses taking up a lot of time that you must be somewhat new to moderating here. :smile: Therefore, I'll pass along a little of my own experience: Moderating will take FAR more of your time than you ever originally imagined. Especially if the project becomes even remotely popular, which this one has. Having Max and Karsten help at first at NPLB was great but within about a year, I found we needed more. So I turned to one of our regulars, Ian (MyDogBuster), who is online frequently and was helpful to see if he would like to do some moderation. Fortunately he agreed. He has been almost the biggest help of all. Since he's online so much, I rarely have to worry about updating primes listings or statuses of k's, etc. I can focus more on getting drives started, sending off files to the servers, processing results, following up with people as needed, and determing future direction of the project.

As yet another compliment to Karsten: His organizing of entire listings of Riesel primes and Aliquot sequences, their statuses, and their reservations I believe has been instrumental in RPS, aliquot sequences, and to a lesser extent NPLB taking off as projects.

I think that is one thing that does not get the credit that it deserves: If you have an extremely organized listing of what is being worked on, statusus of the various efforts, who has what reserved, when it was last worked on, etc., as well as open results or files available (in this case .ELF files) for such efforts, I believe that encourages large #'s of people to become much more interested in the projects.

Personally, I really like being able to see my effort "up in lights" so to speak on the internet and see those "holes" getting filled in on a web page somewhere. If I can't see the holes being filled in, I don't really feel like I'm filling them in and become less interested.

One final thing as a suggestion to the moderators here: On your very most main thread, whatever you decide that is (perhaps the main reservations thread), in the very 1st post in very big bold letters, provide a link to Karsten's status/reservations pages. As it is now, I have a hard time finding a link to it. I put it in my favorites when I first found it but I can tell there are several people here that are not aware of it.

Edit: lol. Oops, I see the link is in the 1st post of the stickied summary page thread. I was looking the reservations and statuses pages. Regardless, would it be good to have a link to that page in the reservations and statuses pages? As a newb, that is where I would first look for such a thing.


Gary

Mini-Geek 2009-07-10 01:56

Unreserving [URL="http://factordb.com/search.php?aq=221130"]221130[/URL]. Hit size 100 fairly quickly (with its 2^3*3) and hit a hard c90 4 lines into sz 100. Not the biggest I've cracked for this seq, but big enough to stop now that the size is 100. :smile:
Still working on [URL="http://factordb.com/search.php?aq=220932"]220932[/URL]. This one might take a bit longer to hit sz 100 since it's just got a perfect number driver. (2*3) Those are so stubborn to break, but don't drive the sequence up quickly. It's a bit frustrating to only grow and yet have such poor chances for getting the downdriver. :squash: :yucky: I suppose it's better than something that's stubborn [I]and[/I] grows quickly...actually, no, perfect numbers are more annoying because you have to waste more time instead of just setting it aside for future computers to work on.
Currently i=920, sz 95, just started SIQS on a c89.

bsquared 2009-07-10 03:55

I'm taking 233634 for a bit. It has 2^5 * 3 * 7 and has already grown a handful of digits since I started typing... :smile:

kar_bon 2009-07-10 05:39

[QUOTE=Mini-Geek;180416]It's a bit frustrating to only grow and yet have such poor chances for getting the downdriver. :squash: :yucky: I suppose it's better than something that's stubborn [I]and[/I] grows quickly...actually, no, perfect numbers are more annoying because you have to waste more time instead of just setting it aside for future computers to work on.[/QUOTE]

it's just the same annoying to have a downdriver with 2 or 2*5 at a size of 115 or 120 digits!
you see this downdriver but crunching the remaining part of 113 to 119 digits takes soooo long you can't stand it, and the next index perhaps the same, before ECM finishes his job! :grin:

mataje 2009-07-10 12:04

[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=229512&action=last&fr=&to="]229512[/URL]: line 836, size 100, 2^2*3 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=229848&action=last&fr=&to="]229848[/URL]: line 2442, size 104, 2^2*3*7 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=229950&action=last&fr=&to="]229950[/URL]: line 771, size 100, 2*3*7 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=237096&action=last&fr=&to="]237096[/URL]: line 793, size 102, 2*3^3 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=237384&action=last&fr=&to="]237384[/URL]: line 934, size 101, 2^3*3*5 UNRESERVED

Greebley 2009-07-10 14:06

[quote=kar_bon;180433]it's just the same annoying to have a downdriver with 2 or 2*5 at a size of 115 or 120 digits!
you see this downdriver but crunching the remaining part of 113 to 119 digits takes soooo long you can't stand it, and the next index perhaps the same, before ECM finishes his job! :grin:[/quote]
Ya, I am suffering this with 232956. Went to 120 digits and after 11 days is down to 112 - I suspect it will take more than a 2 weeks to reach 110 digits. OTOH, if it has a big cofactor, you know you aren't going to lose the driver, so working away isn't all bad.
Worse though would be trying to run a sequence until you hit a driver and it never does. Wasn't there one that was taken to 145(140?) digits with a C137 and still didn't have a driver before it was retired? That sounds like it would have been frustrating.

bsquared 2009-07-10 15:49

[quote=bsquared;180344]
I'll try 227220.[/quote]

Unreserved. size 106, C104.

[quote=bsquared;180427]I'm taking 233634 for a bit. It has 2^5 * 3 * 7 and has already grown a handful of digits since I started typing... :smile:[/quote]

I'm keeping this one for a while longer... it now has the downdriver! size 107, C102.

henryzz 2009-07-10 16:04

[quote=bsquared;180475]I'm keeping this one for a while longer... it now has the downdriver! size 107, C102.[/quote]
i am going to move it to the main reservation thread as it is getting a bit big for this thread

bsquared 2009-07-10 16:13

[quote=henryzz;180478]i am going to move it to the main reservation thread as it is getting a bit big for this thread[/quote]

Fair enough.

I'll reserve 239940, 239964, and 239976.

henryzz 2009-07-10 16:19

[quote=bsquared;180480]Fair enough.

I'll reserve 239940, 239964, and 239976.[/quote]
first reservations since this morning
today has been quiet:smile:

unconnected 2009-07-10 17:14

227010 i=779 size 110 C107
Reserving 238710.

henryzz 2009-07-10 17:29

[quote=unconnected;180490]227010 i=779 size 110 C107
Reserving 238710.[/quote]
could you specifically say unreserving next time?
i presume this time and last time you wanted to unreserve

10metreh 2009-07-10 17:33

Just a notice:

[B]Please could you submit the current status of your sequence to the DB once you unreserve it. Thank you.[/B]

henryzz 2009-07-10 17:33

[quote=unconnected;180490]227010 i=779 size 110 C107
Reserving 238710.[/quote]
you haven't put the data into the database

[B]10metreh:[/B] Guess why I posted what I just posted?

[B]henryzz: [/B]Yes, it is pretty obvious from my next post:smile:

mdettweiler 2009-07-10 18:03

Unreserving 238062 at i=1978, C102 (C101 cofactor), 2*3 driver.
Reserving 220200.

unconnected 2009-07-10 18:20

[quote=henryzz;180495]you haven't put the data into the database
[/quote]
I loaded data before I post there.
[URL="http://factordb.com/search.php?query=&se=1&aq=227010&action=last&fr=&to="]227010[/URL]

jrk 2009-07-10 19:41

Unreserving 223632 at i=1189 size 101 digits, 2^2*7 driver. Factors are in database but line 530 is wrong.

I've uploaded the sequence also: [url=http://jaysonking.com/aliquot/223632.elf]223632.elf[/url].

KriZp 2009-07-10 22:28

reserving 239778

unreserving 223398 i=2060 size 108 2^4 *3

jrk 2009-07-11 03:50

reserving 233130

henryzz 2009-07-11 07:04

[quote=unconnected;180505]I loaded data before I post there.
[URL="http://factordb.com/search.php?query=&se=1&aq=227010&action=last&fr=&to="]227010[/URL][/quote]
i guess the database must have been behind

henryzz 2009-07-11 07:46

just noticed 238710 has the squared bug

jrk 2009-07-11 08:00

Unreserving 233130 at i=1946 size 102 digits. Factors are in Syd's database and also uploaded here: [url=http://jaysonking.com/aliquot/233130.elf]233130.elf[/url].

henryzz 2009-07-11 08:09

I have just done a full update.
We have made huge progress over the last few days.
Unfortunately we have no downdriver runs.

When updating i found that there is a huge number of sequences above 100 digits now.
I will now move these reservations to the main reservation [URL="http://mersenneforum.org/showthread.php?t=11588"]thread[/URL].

Greebley 2009-07-11 14:25

Finished:
240030 - Size 100, 2^3*5
240096 - Size 114, 2^4*31^2
240120 - Size 106, 2^2*7
240378 - Size 103, 2^2*7
240432 - Size 104, 2^3*3

I guess will grab the 241's and do them next when I finish the last 3 240's (two are close to done)
241116
241136
241236
241416
241506
241860
241884

mdettweiler 2009-07-11 16:10

Unreserving 220200 at i=1646, C110 (C102 cofactor). Guide: 2^4*3^3*5
Reserving 220724.

Batalov 2009-07-11 17:28

[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=238650"]238650[/URL] reserving ...and terminating. :smile:

mataje 2009-07-11 18:20

[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=234900&action=last&fr=&to="]234900[/URL]: line 656, size 111, 2^2*3^2*7 UNRESERVING
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=237600&action=last&fr=&to="]237600[/URL]: line 2062, size 10, 2^4*3*31 UNRESERVING
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=237888&action=last&fr=&to="]237888[/URL]: line 2045, size 10, 2^3*3^2 UNRESERVING

Batalov 2009-07-11 19:02

246888 reserving...

Greebley 2009-07-11 23:28

Done with 240480 size 102, 2*3^3*5
Done with 240792 size 103, 2^3*3^2*5^2 (might be worth seeing if the 3^2*5^2 helps but has a potential current c97 (passed some ecm).
Done with 240810 size 101, 2^3*3*5

starting the 241's

Batalov 2009-07-12 05:54

Randomly picked 239772 and 238544 to mess with.

unconnected 2009-07-12 09:44

227200 i=781 size 113 C111 [B]unreserved
[/B]Taking 242424.

mataje 2009-07-12 10:35

I´ll take 246840 and 247560.

mataje 2009-07-12 16:41

[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=238212&action=last&fr=&to="]238212[/URL]: line 977, size 100, 2^2*3*7 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246840&action=last&fr=&to="]246840[/URL]: line 447, size 100, 2^6*5*127 UNRESERVED

I´ll take 246504, 246648, 246708, 246720, 246768, 246792.

Mini-Geek 2009-07-12 19:09

Unreserving [URL="http://factordb.com/search.php?aq=220932"]220932[/URL].
Status in DB.
i=998, sz 102, c94 with all the ECM aliqueit wanted (in DB, along with some extra, probably not too helpful, P-+1)
Taking 233304.

unconnected 2009-07-12 20:38

Taking 242190, 242370, 244140, 244440.
238710 now size 123 at i=1811, but not loaded into DB due to squared bug. I'll continue with it for some more iterations.

Mini-Geek 2009-07-12 23:01

Unreserving [URL="http://factordb.com/search.php?aq=233304"]233304[/URL]. i 769, sz 101, c92 (with all ECM wanted by aliqueit and the DB)

mdettweiler 2009-07-13 00:08

Unreserving [url=http://www.factordb.com/search.php?query=&se=1&aq=220724&action=last&fr=&to=]220724[/url] at i=1446. Initial composite: C105; cofactor: C100 (not much ECM). Driver: 2^4*3^2
Reserving 226092.

axn 2009-07-13 00:13

Could someone delete all posts that have been reflected in top post? Two pages of posts is too much to scan thru.

10metreh 2009-07-13 06:43

[quote=axn;180756]Could someone delete all posts that have been reflected in top post? Two pages of posts is too much to scan thru.[/quote]

Why do you need to scan through everything? We (henryzz and I) need to have a record of who did what.

Greebley 2009-07-13 07:17

Done 241116 - size 100, 2^2*3*7
Done 241136 - size 104, 2^2*7, half the ecm done on a C102

schickel 2009-07-13 07:57

[QUOTE=axn;180756]Could someone delete all posts that have been reflected in top post? Two pages of posts is too much to scan thru.[/QUOTE][QUOTE=10metreh;180786]Why do you need to scan through everything? We (henryzz and I) need to have a record of who did what.[/QUOTE]I also found it hard to just delete messages (well, after I deleted the original huge discussion thread, anyway....).

Maybe fork off a "discussion" thread where the reserves/unserverves could be moved after incorporation in the top post....

unconnected 2009-07-13 08:47

Reserving 243120, 243180, 243540.

10metreh 2009-07-13 08:50

[quote=schickel;180799]I also found it hard to just delete messages (well, after I deleted the original huge discussion thread, anyway....).

Maybe fork off a "discussion" thread where the reserves/unserverves could be moved after incorporation in the top post....[/quote]

I think what I'll do is keep a record of what's been done on my own system and then delete the stuff (after agreeing with henryzz; he's in charge of this subproject, not me).

mataje 2009-07-13 15:02

[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=238476&action=last&fr=&to="]238476[/URL]: line 1618, size 100, 2*3 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246768&action=last&fr=&to="]246768[/URL]: line 998, size 100, 2^2*7 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246792&action=last&fr=&to="]246792[/URL]: line 1220, size 100, 2*3^2*7 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=247560&action=last&fr=&to="]247560[/URL]: line 789, size 100, 2*3 UNRESERVED

henryzz 2009-07-13 16:18

[quote=10metreh;180806]I think what I'll do is keep a record of what's been done on my own system and then delete the stuff (after agreeing with henryzz; he's in charge of this subproject, not me).[/quote]
if we use that method i then wont be able to clear up myself
i personally vote for moving to a separate discussion thread
that will also keep it easily acessible to anyone

10metreh 2009-07-13 16:46

[quote=henryzz;180834]if we use that method i then wont be able to clear up myself
i personally vote for moving to a separate discussion thread
that will also keep it easily acessible to anyone[/quote]

Here we go...

henryzz 2009-07-13 16:51

[quote=10metreh;180840]Here we go...[/quote]
brilliant
shall we move stuff here as soon as it is reflected in the first post?
one disadvantage in that is the thread has dropped down the sticky list a lot
maybe we should always keep the most recent post in there

10metreh 2009-07-13 16:56

[quote=henryzz;180841]brilliant
shall we move stuff here as soon as it is reflected in the first post?
one disadvantage in that is the thread has dropped down the sticky list a lot
maybe we should always keep the most recent post in there[/quote]

OK, but the "most recent post" can't be dicussing the threads issue. Here we go again...

Edit: Done, and I'll close this thread after a couple of days when everyone's had the chance to reply to the posts they want to reply to.

mdettweiler 2009-07-13 19:11

Unreserving [URL="http://www.factordb.com/search.php?query=&se=1&aq=226092&action=last&fr=&to="]226092[/URL] at i=760, C103 (C99 cofactor), guide: 2^2*3*5
Reserving 239304.

Also, quick question: how come many of the "unworked sequences" are already at ~80 digits in the DB? I can understand why some others are at ~70 digits since the DB can do up to that with the workers, but why would some be higher? Is some mystery benefactor responsible for this?

Not that I'm saying this is a bad thing, mind you, just that it's rather curious. :smile:

unconnected 2009-07-13 20:12

[URL="http://factordb.com/search.php?query=&se=1&aq=243120&action=last&fr=&to="]243120[/URL] i=1521 size 106 C99 [B]unreserved
[/B]242190 terminates at i=1745 with P=1544509. I can't upload it to DB due to bug at i=1027 - already PM'ed to Syd about that.

Greebley 2009-07-14 01:41

[quote=mdettweiler;180854]Unreserving [URL="http://www.factordb.com/search.php?query=&se=1&aq=226092&action=last&fr=&to="]226092[/URL] at i=760, C103 (C99 cofactor), guide: 2^2*3*5
Reserving 239304.

Also, quick question: how come many of the "unworked sequences" are already at ~80 digits in the DB? I can understand why some others are at ~70 digits since the DB can do up to that with the workers, but why would some be higher? Is some mystery benefactor responsible for this?

Not that I'm saying this is a bad thing, mind you, just that it's rather curious. :smile:[/quote]

I know I have updated some sequences to 80 digits in the 200k range in the past. I wouldn't think it was 'many' though so I suspect others have done the same thing.

Greebley 2009-07-14 02:13

Done with [URL="http://factorization.ath.cx/search.php?se=1&aq=241236&action=last"]241236[/URL] - It hit the 2^3*3^2*5 driver (though the 3^2 makes it only a guide) with 106 digits. It will never lose the square on 3 since the 5 and 2 term both contribute a 3 so it doesn't have enough 2's to be a driver and is less persistent than the one with just plain 3 (though it does go up faster).

henryzz 2009-07-14 06:40

[quote=unconnected;180861][URL="http://factordb.com/search.php?query=&se=1&aq=243120&action=last&fr=&to="]243120[/URL] i=1521 size 106 C99 [B]unreserved
[/B]242190 terminates at i=1745 with P=1544509. I can't upload it to DB due to bug at i=1027 - already PM'ed to Syd about that.[/quote]
could you tell us what the highest size was for the terminations thread?

10metreh 2009-07-14 06:59

[quote=henryzz;180910]could you tell us what the highest size was for the terminations thread?[/quote]

Or post a zipped .elf or .alq file.

unconnected 2009-07-14 07:27

1 Attachment(s)
Max size was only 85. Zipped ELF-file attached.
It is my first terminated sequence!

10metreh 2009-07-14 07:35

[quote=unconnected;180917]Max size was only 85. Zipped ELF-file attached.
It is my first terminated sequence![/quote]

:party:

This subproject is going well!

(And there will be another one once this one's finished. And I have an idea what it'll be.)

Edit: When looking for the aliquot sequence of the correct number where the bug is, I get the squared bug :sad:

mataje 2009-07-14 12:43

[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246504&action=last&fr=&to="]246504[/URL]: line 1124, size 101, 2^3*3*5 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246648&action=last&fr=&to="]246648[/URL]: line 949, size 100, 2*3 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246708&action=last&fr=&to="]246708[/URL]: line 2001, size 105, 2^5*3^2*7 UNRESERVED

Now, I´ll take 244728, 244872, 245274, 245520, 245640, 246432.

mataje 2009-07-14 15:30

[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=245640&action=last&fr=&to="]245640[/URL]: line 589, size 100, 2^3 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246432&action=last&fr=&to="]246432[/URL]: line 364, size 100, 2^3*3*5 UNRESERVED
[URL="http://factorization.ath.cx/search.php?query=&se=1&aq=246720&action=last&fr=&to="]246720[/URL]: line 824, size 100, 2^2*7 UNRESERVED

mdettweiler 2009-07-14 16:20

Unreserving 239304 at i=1364, C103 (C96 cofactor). Guide is 2^6*5^2 (though there's a 127^2 immediately after the 5^2; not sure if that's part of the guide since it just showed up on this line.)

Reserving 234240.


All times are UTC. The time now is 09:09.

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