Broken aliquot sequences
 

[code]
228504 - next element is 115002363456781951116353025432393722069665825524716257351967573745719336629908761109140183558732708396906923367555454

706104 - next element is 41056247340555352160404327938385124070914568373289825909365899066462655085280970624745514385381813768355098498287234724
[/code]

This is the list of broken sequences in my current script. Format is {seq: (next-good-term, said-term's-index)}.

[code]broken = {319860: (2825523558447041736665230216235917892232717165769067317116537
832686621082273062400083298623866666431871912457614030538, 1072),
270870: (1291110518948762980086184521745721113860843218383951061593525
26283699001422613851356969918762669577402931599473069044, 1552),
337344: (1718418747094677774071372105197247457771552131180506064111375
96612474196944001558441112921996396264019339265486232710, 867),
706104: (4105624734055535216040432793838512407091456837328982590936589
9066462655085280970624745514385381813768355098498287234724, 938),
228504: (1150023634567819511163530254323937220696658255247162573519675
73745719336629908761109140183558732708396906923367555454, 1601)}
[/code]

In fact, 337344 is broken a bit earlier, at 844, the continuation is:
[CODE]843 . 13800710012818721686377176836950658029521999323673558068277408603214085787406348518457980786865144935482284469457238 = 2 * 3 * 17 * 2791 * 96448058774965644508235918713 * 502629450036802409831645837403502556245707353065795279268876677110360723970834343
844 . 15434794124606939665049526605837437264723911427275235389652798604877119402557306555686183210411478357525058173971114 = 2 * 3 * 14153673515319725928119989 * 181752510021521360083467530953812952249675148335119350446690716024589031293302626961653771
845 . 15434794124606939665049528786867557522980232428885606835408225600978899423989511915974775675323936060993292851256246 = 2 * 3 * 523 * 4918672442513365094024706433036187865831814030874954377121805481510165527083974479278131190351796067875491667067
846 . 15493818193917100046177825264063991777370214197256106287933687266757021410314519609726113249608157613807798751267338 = 2 * 3 * 47 * 59 * 2957 * 480760091966766385693 * 655054752029921267545111452991317127234487207332879489777737319576139870792897264338451
[/CODE]

(edit, just for the sake of having all the terms :P)

305460 also broken.
+327852
+322686

[QUOTE=LaurV;384473]In fact, 337344 is broken a bit earlier, at 844, the continuation is:

(edit, just for the sake of having all the terms :P)[/QUOTE]

I mean... my script doesn't really care about any intermediate terms :P

[QUOTE=unconnected;384476]305460 also broken.
+327852
+322686[/QUOTE]

I don't suppose you'd be willing to post correct indices for these? :razz:

[QUOTE=Dubslow;384500]
I don't suppose you'd be willing to post correct indices for these? :razz:[/QUOTE]

I have them in full, let me get back home (just arrived at work :D)

In your format:
[CODE]305460: (153930603295623579438311517767087301544108450139577880157761944822979334442803898050679690506918213552493053494172082, 1278)
322686: (302926126903899986879677895288088736941245823142759900740695496639749231035725570564906453951622576176253465079992650, 688)
327852: (686850216844208461856962371309231689049988200182761949020962964975366230549349069889648461306631311470409163996946786, 1251)[/CODE]

[QUOTE=LaurV;384577]In your format:
[CODE]305460: (153930603295623579438311517767087301544108450139577880157761944822979334442803898050679690506918213552493053494172082, 1278)
322686: (302926126903899986879677895288088736941245823142759900740695496639749231035725570564906453951622576176253465079992650, 688)
327852: (686850216844208461856962371309231689049988200182761949020962964975366230549349069889648461306631311470409163996946786, 1251)[/CODE][/QUOTE]

Thanks, though out of frustration I changed the format to reverse the new term and index. :smile:


[code]{319860: (1072, 2825523558447041736665230216235917892232717165769067317116537832686621082273062400083298623866666431871912457614030538),
270870: (1552, 129111051894876298008618452174572111386084321838395106159352526283699001422613851356969918762669577402931599473069044),
337344: (867, 171841874709467777407137210519724745777155213118050606411137596612474196944001558441112921996396264019339265486232710),
706104: (938, 41056247340555352160404327938385124070914568373289825909365899066462655085280970624745514385381813768355098498287234724),
228504: (1601, 115002363456781951116353025432393722069665825524716257351967573745719336629908761109140183558732708396906923367555454),
305460: (1278, 153930603295623579438311517767087301544108450139577880157761944822979334442803898050679690506918213552493053494172082),
322686: (688, 302926126903899986879677895288088736941245823142759900740695496639749231035725570564906453951622576176253465079992650),
327852: (1251, 686850216844208461856962371309231689049988200182761949020962964975366230549349069889648461306631311470409163996946786)
}[/code]

296886 also broken: i1307 should be

[code]
929613060469964142613395787623511040369650794668964528799792248592927016853533671095941458486258918363963289280347604
[/code]

Something wrong happened with the sequence [URL="http://factordb.com/sequences.php?se=1&aq=12012&action=last20&fr=0&to=100"]12012[/URL]

[QUOTE=Drdmitry;435705]Something wrong happened with the sequence [URL="http://factordb.com/sequences.php?se=1&aq=12012&action=last20&fr=0&to=100"]12012[/URL][/QUOTE]

The database has moved server today. This may be a result of that.

None of my assigned sequences will display.

Some of mine are fine and some are not displayed. I contacted Syd.

Out of the sequences that I'm working on, 4198862272 works fine (I'm currently working on the C122 on i429), but I've found out that a lot of [URL="https://sites.google.com/site/mynumbersandfactors/aliquot-sequences"]my sequences[/URL] won't work:

[CODE]271647324
4197560040
14195265656
18003824142
103184416668541535456159045977640995350285539764323079287562416[/CODE]And many others that I've tried in the past. Also, Look at the [URL="http://www.factordb.com/aliquot.php?type=1&aq=1100000000204695877&big=1"]graph for 09 F9[/URL]. All the index values at the bottom say "0g", and the digits axis is all "0f".

The following sequences are still not displaying (since 7 June):

230916
434040
829332

and I cannot download their elf files either.

Sequence 6552 is now not displaying at all

Sequence

12012

is not displaying

[QUOTE=richs;436033]The following sequences are still not displaying (since 7 June):

230916
434040
829332

and I cannot download their elf files either.[/QUOTE]

Fixed now. Thanks!

Thanks to Syd, these broken sequences seems to be fixed now:

228504 270870 296886 305460 319860 322686 327852 337344 706104

yoyo

[QUOTE=yoyo;442329]Thanks to Syd, these broken sequences seems to be fixed now:

228504 270870 296886 305460 319860 322686 327852 337344 706104

yoyo[/QUOTE]

Nice. I removed them from the AllSeq page.

Sequence 3270 is broken

This one was not listed on the AllSeq page and was unknown to me. So I couldn't discuss it with Syd :(

That was intended as a report rather than a complaint; I suspect 3270 broke this morning when I tried to upload a new factor.

[QUOTE=fivemack;442394]Sequence 3270 is broken[/QUOTE]

For me, the aliquot sequence 3270 in FactorDB is not being broken apart at all!
By the way, what causes the aliquot sequences in FactorDB to be getting having been broken apart? Do by that?
Erroneous computations / linkage of aliquot sequences in FactorDB is being the cause?

Is break apart being the appropriate word to use up - could be able to - consider it up - up over - not - not!

[QUOTE=Raman;442554]
Any way that you would need 2.3[sup]2k[/sup], k ≥ 1 to escape from the 2.3 driver, and then
that you would need 2[sup]6[/sup].127[sup]2k[/sup], k ≥ 1 to escape from the 2[sup]6[/sup].127 driver, and then
that you would need 2[sup]12[/sup].8191[sup]2k[/sup], k ≥ 1 to escape from the 2[sup]12[/sup].8191 driver, and then
that.
[/QUOTE]

Rather than = instead of?
Size = length? In MATLAB programming code / GNU Octave language - size returns with in a two dimensional matrix always exactly only certainly, but not only, let not alone, length returns with in a one dimensional vector always exactly only certainly, namely - not - not!
Cause = effect?

[QUOTE=Raman;442554]
Texas State HPC has reserved that 2,2158M c193 for over six years of time without having it as being getting completed off.
May be that some one else or may be that NFS@Home or @ Ryan Propper could be able to - consider it up - up over!
Good work by @ Paul Zimmermann to finish off that Texas State HPC reserved 7,347+ c188 by using ECM curves running immediately, executing out, finishing off with in that composite number, which would have otherwise got no progress at all - during having been a prime number cofactor!
[/QUOTE]

After 5,805L c160 and 10,366+ c172 and 6,370+ c161.

[QUOTE=Raman;442554]
The stable guide 2[sup]12[/sup] cannot pick up a 8191.
[/QUOTE]

There are many different drivers (perfect numbers - all only known to be even). But there is only one downdriver!
But in each same / other case, the power of 2 must / should either be of one or of higher! Similarly for other prime number factors - numbers!
How about for the power of 0 - not - not !?

[QUOTE=Raman;442554]
My latest posts length are always appearing to being long enough - not - not!
Occuping majority of the page size!
Lengthy posts are being liked by me up!
Other people do make mostly small posts!
I have been observing / watching it up!
A good exercise for analysis!
Statistics of posts characters count do made by other people!
By using be being!

Should have been - or
Must have been - or

Any way, by that do
By the way, by that do
On the other hand, by that do

My latest posts length are always seeming to being exceed 10000 characters - if the compressible limit is being 16384 characters right now.
Reviewed by using Microsoft Word - Windows Operating System - Review Word Count - MS DOS Operating System (Microsoft Disk Operating System - Operating System).
[/QUOTE]

Always need to wait for some time between two consecutive / continuous / successive posts or search results for the [spoiler]/ an /[/spoiler]
a given fixed time limit.
This effect is being always enhanced for non-members / guests.

Mersenne Forum does not quote quoted text even if it were do as like a part of / piece of new text / fresh text - not - not part of / piece of old text / ancient text / obsolete text - not - not!

Please,

Can anyone correct an error for the aliquot sequence that starts with the number 3^108 ?
There is an error at index 1575.

Is :

[CODE]1574 . 10536346489696420770680 = 2^3 * 5 * 19 * 23 * 919 * 3067 * 423931 * 504457
1575 . 15539970862145288285320 = 2^3 * 5 * 11 * 23 * 1753 * 15733 * 55677051589
1576 . 24287246194437618095480 = 2^3 * 5 * 7 * 31 * 2861 * 7489 * 130592086759[/CODE]

Should be :

[CODE]1574 . 10536346489696420770680 = 2^3 * 5 * 19 * 23 * 919 * 3067 * 423931 * 504457
1575 . 15540084064757285981320 = 2^3 * 5 * 23 * 181 * 593 * 594161 * 264867167
1576 . 21208836326841958327160 = 2^3 * 5 * 47 * 11281295918532956557[/CODE]

Thank you very much.

I think I found a new aliquot sequence with error on FactorDB. It's a sequence that starts with a number < 3,000,000 which is on the blue page.


This is the sequence that starts with 1142360, error at index 199.

Can anyone confirm ?

[CODE]197 . 18491352962151584 = 2^5 * 19 * 3359 * 13751 * 658447
198 . 19843797224754016 = 2^5 * 29 * 953^2 * 1669 * 14107
199 . 20613286913078864 = 2^4 * 1291691 * 997398319
200 . 19324987440401776 = 2^4 * 7 * 172544530717873
201 . 23466056177630976 = 2^8 * 3 * 7 * 13 * 23 * 14598547849 [/CODE]


should be :

[CODE]197 : 18491352962151584 = 2^5 * 19 * 3359 * 13751 * 658447
198 : 19843797224754016 = 2^5 * 29 * 953^2 * 1669 * 14107
199 : 20640395098951184 = 2^4 * 1290024693684449
200 : 19350370405266766 = 2 * 487 * 19866910067009
201 : 9734785932835874 = 2 * 11273 * 37783 * 11427743[/CODE]

[QUOTE=garambois;514933]I think I found a new aliquot sequence with error on FactorDB. It's a sequence that starts with a number < 3,000,000 which is on the blue page.


This is the sequence that starts with 1142360, error at index 199.

Can anyone confirm ?[/QUOTE]

Yes, I confirmed and fixed it on the blue page.

[QUOTE=ChristianB;514979]Yes, I confirmed and fixed it on the blue page.[/QUOTE]

Thank you very much !

Home Prime 3036 is broken

[url]http://www.factordb.com/sequences.php?se=2&aq=3036&action=all&fr=0&to=100[/url]

3036 => 22391 but should go to 2231123

[QUOTE=SethTro;520013]Home Prime 3036 is broken[/QUOTE]

This is base 2, so everything ok here.

3036[SUB]10[/SUB] = 101111011100[SUB]2[/SUB] = 2^2*3*11*23
-> 10 10 11 1011 10111 = 22391[SUB]10[/SUB]

Unless I'm mistaken, there's a problem on the blue page with the 2 sequences called "These sequences are currently broken" : the link no longer works !
In addition, the problem is solved for sequence 1142360.
I haven't checked to see if sequence 1465290 is repaired.

It seems that both sequences are fixed in factordb now.

BTW, 933564 is broken.

I think I found a new aliquot sequence with error on FactorDB. It's a sequence that starts with a number < 3,000,000 which is on the blue page.


This is the sequence that starts with 1475172, error at index 255.

Can anyone confirm ?


[CODE]253 . 152340387197383120612 = 2^2 * 113 * 337036254861467081
254 . 116614544182067610824 = 2^3 * 17 * 2371 * 4211 * 140297 * 612137
255 . 115052270138377872376 = 2^3 * 457 * 80233 * 278219 * 1409773
256 . 101146402985461010024 = 2^3 * 3727 * 3392353199136739
257 . 88553987910265490776 = 2^3 * 11069248488783186347[/CODE]should be :


[CODE]253 : 152340387197383120612 = 2^2 * 113 * 337036254861467081
254 : 116614544182067610824 = 2^3 * 17 * 2371 * 4211 * 140297 * 612137
255 : 115054299854133875896 = 2^3 * 14381787481766734487
256 : 100672512372367141424 = 2^4 * 2503 * 2513796253804613
257 : 94458408032962215712 = 2^5 * 442571 * 6669721357771[/CODE]

Both the Python mfaliquot library and WolframAlpha support the second version, so it appears the sequence is indeed broken in FactorDB.

I probably found yet another mistake :

A new aliquot sequence with error on FactorDB.
It's a sequence that starts with a number < 3,000,000 which is on the blue page.


This is the sequence that starts with 1866192, error at index 3835.

Can anyone confirm ?


[CODE]3833 . 1857136161022787663609287672 = 2^3 * 19 * 53 * 1072637 * 214917368946554501
3834 . 1877426135009140448634383528 = 2^3 * 947 * 977 * 394747 * 2138897 * 300413621
3835 . 1650071913384946652798107672 = 2^3 * 19 * 6163 * 49009 * 35941092589041083
3836 . 1607243861666293749034420328 = 2^3 * 11 * 18264134791662428966300231
3837 . 1680300400832943464899621432 = 2^3 * 71 * 2958275353579125818485249[/CODE]
should be :


[CODE]3833 : 1857136161022787663609287672 = 2^3 * 19 * 53 * 1072637 * 214917368946554501
3834 : 1877426135009140448634383528 = 2^3 * 947 * 977 * 394747 * 2138897 * 300413621
3835 : 1650082498696992926527054552 = 2^3 * 631 * 1109 * 65089 * 33131089 * 136682041
3836 : 1451567367500391297153505448 = 2^3 * 137 * 24708664649 * 53601552304837
3837 : 1289987788382339502020263552 = 2^7 * 7 * 405382183 * 3551509104729389[/CODE]

Confirmed! This is what Aliqueit tells me:
[code]
Verifying index 3835...
ERROR: @index 3835: value != sigma - n
[/code]Corrected lines match yours:[code]
3835 . 1650082498696992926527054552 = 2^3 * 631 * 1109 * 65089 * 33131089 * 136682041
3836 . 1451567367500391297153505448 = 2^3 * 137 * 24708664649 * 53601552304837
3837 . 1289987788382339502020263552 = 2^7 * 7 * 405382183 * 3551509104729389
3838 . 1647037987054673586242766848 = 2^11 * 7 * 321403 * 52293193 * 6835661317
[/code]

OK, verification of all aliquot sequences starting with numbers less than 3,000,000 is complete.
Thanks to Happy5214 and EdH for confirming errors found on factorDB.

Can someone please give me the last 80-digit terms of the 3 broken aliquot sequences on FactorDB ?

933564
1475172
1866192

I need these 3 terms to complete my updated C80 database I was talking about here :
[URL]https://www.mersenneforum.org/showthread.php?t=24423[/URL]

I hope someone has those three 80 digits terms...
If not, I will have to delete these three aliquot sequences from my C80 database.


Excuse me, but may I also point out that the two errors reported recently were not reported on the blue page.

I think these are the correct last c80's for the unbroken three sequences:
[code]
933564 = 53910798253283852177545053052282940198337166755985147396297057839253859396629560
1475172 = 70632199920744621702989746940578378226575559519111823940659865966774451778707304
1866192 = 97488918894772105620549720764059516378747055783492651624463822352092076013025324
[/code]These are not from the broken elf's, but from what should have been the correct elf's later on.

Thank you very much EdH !
This is exactly what I needed.

:smile:

How did you get the data for these three aliquot sequences ?


I realize that an aliquot sequence merge is detected when entering data into the FactorDB database.
Any merge detected using one of the three broken aliquot sequence on FactorDB will be false...

[QUOTE=garambois;545378]Thank you very much EdH !
This is exactly what I needed.

:smile:

How did you get the data for these three aliquot sequences ?


I realize that an aliquot sequence merge is detected when entering data into the FactorDB database.
Any merge detected using one of the three broken aliquot sequence on FactorDB will be false...[/QUOTE]
Here are the steps I took for 933564 (which included writing a couple scripts to fix the numbering and search for the last c80):

1. - download 933564.elf
2. - rename to alq_933564.elf
3. - check 933564 with "./aliqueit 933564 -t"
4. - delete the lines after the last valid line
5. - run "./aliqueit 933564 -q"
6. - take last composite from alq_933564 (1150187197239087798)
7. - query factordb for sequence 1150187197239087798
8. - download its elf
9. - remove new last line from alq_933564.elf to prevent duplication
10. - splice* the 933564 and 1150187197239087798 elf's together
11. - replace the original alq_933564.elf with the new spliced file
12. - verify the new alq_933564.elf with "./aliqueit 933564 -t"
13. - grab the last c80 in alq_933564.elf

*I wrote a script to renumber the new spliced file as it joined them, because simply concatenating would leave the original indices for the second elf.

splice-elf.sh script:
[code]
#!/bin/bash

count=0
exec <"$1"
while read line
do
period=$(echo `expr index "$line" .`)
echo "${count} ${line:$period-1}" >>new.elf
let count=${count}+1
done

exec <"$2"
while read line
do
period=$(echo `expr index "$line" .`)
echo "${count} ${line:$period-1}" >>new.elf
let count=${count}+1
done
[/code]

Thank you very much EdH for this method, I hadn't thought of it !
I can reproduce it with my own means...


:tu:

You're quite welcome. Glad I was able to help.

[QUOTE=EdH;545387]
*I wrote a script to renumber the new spliced file as it joined them, because simply concatenating would leave the original indices for the second elf.
[/QUOTE]
Nice job. Used to do all this procedure with the editor, in both pn2 and notepad++ you can mark/delete rectangular blocks (using shift+alt) and auto-number text lines. It is only a couple of cut/paste and takes a minute.

[QUOTE=LaurV;545510]Nice job. Used to do all this procedure with the editor, in both pn2 and notepad++ you can mark/delete rectangular blocks (using shift+alt) and auto-number text lines. It is only a couple of cut/paste and takes a minute.[/QUOTE]
I'm not familiar with pn2, but Notepad++ needs Windows. (Wine has just notepad.) That would be a bigger effort for me. I wonder if gedit has this capability.

I'm thinking of expanding the script to do everything from just entering the broken sequence. Maybe I'll do that later, just for fun. Isn't really that big a call for it, is there? Are there more than three broken sequences?

[QUOTE=EdH;545517]I'm thinking of expanding the script to do everything from just entering the broken sequence. Maybe I'll do that later, just for fun. Isn't really that big a call for it, is there? Are there more than three broken sequences?[/QUOTE]Here's a larger script that will take a sequence number and generate a local "fixed" .elf file for it. This works for me, but I can't guarantee success elsewhere:
[code]
#!/bin/bash
# Script to locally fix a broken Aliquot sequence
# Access to factordb.com is necessary
# aliqueit is necessary
# No error checking is performed
# Use at own risk

# Acquire sequence number, if not provided on command line
if [ ${#1} -lt 3 ]
then printf "Aliquot sequence: "
read sequence in
else
sequence=$1
fi

# Retrieve sequence.elf
echo "Retrieving $sequence.elf. . ."
wget -q -U Mozilla/5.0 "http://factordb.com/elf.php?seq=$sequence&type=1" -O alq_$sequence.elf

# Test sequence with aliqueit
./aliqueit $sequence -t >temp

# Acquire index of first invalid line
exec <"temp"
while read line
do
case $line in
"ERROR"*) index=${line:14};;
esac
done
colon=$(echo `expr index "$index" :`)
index=${index:0:colon-1}

# Truncate sequence.elf into temporary file
count=0
rm ${sequence}T 2>/dev/null
exec <"alq_${sequence}.elf"
while read line
do
if [ $count -lt $index ]
then echo "$line" >> ${sequence}T
fi
let count=${count}+1
done
rm alq_$sequence.elf
cp ${sequence}T alq_$sequence.elf

# Run aliqueit to create next index
./aliqueit $sequence -q >/dev/null

# Find new sequence from new index
newseq=$(tail -1 alq_$sequence.elf)
period=$(echo `expr index "$newseq" .`)
equals=$(echo `expr index "$newseq" =`)
newseq=${newseq:${period}+2:${equals}-${period}-4}
echo "$newseq"

# Retrieve new sequence.elf
echo "Retrieving $newseq.elf."
wget -q -U Mozilla/5.0 "http://factordb.com/elf.php?seq=$newseq&type=1" -O alq_$newseq.elf

# Splice the two sequences and renumber sequence.elf
rm temp.elf 2>/dev/null
count=0
exec <"${sequence}T"
while read line
do
period=$(echo `expr index "$line" .`)
echo "${count} ${line:$period-1}" >>temp.elf
let count=${count}+1
done
exec <"alq_$newseq.elf"
while read line
do
period=$(echo `expr index "$line" .`)
echo "${count} ${line:$period-1}" >>temp.elf
let count=${count}+1
done
rm alq_$sequence.elf
mv temp.elf alq_$sequence.elf

# Verify sequence .elf
./aliqueit $sequence -t
[/code]All valid factordb .elf files generate a warning in Aliqueit:
[code]
WARNING: @index ####: partial last line.[/code]This signals success.

Aliquot sequence 1750944 has an error at index 1068.