i have found the 5 following terms of my sequence and subminetted them to the factorDB. i think i got that right (although my 'credits' didn't move, need to be checked?). after that, for the 846 th term, i assigned myself an ECM [URL="http://factordb.com/search.php?id=165916830&adv165916830=%3E+%3E"]here[/URL] how do I 'do' this assignement?
sorry to bother you with those question, i'm a noob in that field

Ignore the "ECM work". Other than "Quick ECM", it doesn't work. (Don't ask why - it's complicated.) The database isn't for doing work, it's for storing results. Aliqueit should be used for doing work. Have you installed it and the programs it uses for factorization (GMP-ECM, YAFU, msieve, GGNFS)?

yup, i have installed all the software, and its running... not as fast as i hoped for but still good

Forgot to mention this, but the credits don't work either. The DB is currently just a DB except for "Quick ECM".

Done with 36512

reserving 40500

ok... factordb is acting strange... for 36684, at the 870 iteration there is a small problem...
[URL="http://factordb.com/search.php?id=165919062"][COLOR=#002099]4468722781...[/COLOR][/URL]<102> = [URL="http://factordb.com/search.php?id=16882"][COLOR=#000000]2[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=107"][COLOR=#000000]53[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=10144"][COLOR=#002099]57[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=788"][COLOR=#000000]1093[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=165919063"][COLOR=#550000]70843169[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=165919065"][COLOR=#550000]49685824598826035240380565051[/COLOR][/URL]<29> · [URL="http://factordb.com/search.php?id=165919066"][COLOR=#550000]19224367016503764005279927748469360887002331412508236569883[/COLOR][/URL]<59>
even if i put 2*3*19*53*1093....etc it come back as 2*53*57... and even if i try to do a quick ecm with 57, it does not work. what should I do?

(and trying to repair 57 does not work)

[quote=firejuggler;216207]ok... factordb is acting strange... for 36684, at the 870 iteration there is a small problem...
[URL="http://factordb.com/search.php?id=165919062"][COLOR=#002099]4468722781...[/COLOR][/URL]<102> = [URL="http://factordb.com/search.php?id=16882"][COLOR=#000000]2[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=107"][COLOR=#000000]53[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=10144"][COLOR=#002099]57[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=788"][COLOR=#000000]1093[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=165919063"][COLOR=#550000]70843169[/COLOR][/URL] · [URL="http://factordb.com/search.php?id=165919065"][COLOR=#550000]49685824598826035240380565051[/COLOR][/URL]<29> · [URL="http://factordb.com/search.php?id=165919066"][COLOR=#550000]19224367016503764005279927748469360887002331412508236569883[/COLOR][/URL]<59>
even if i put 2*3*19*53*1093....etc it come back as 2*53*57... and even if i try to do a quick ecm with 57, it does not work. what should I do?[/quote]
This is a known bug. A few numbers, such as 57, (3*19) are marked like they're composites with no known factors when they're really (often trivially, as in this case) fully factored. Since the DB thinks not all numbers in the line are fully factored, it doesn't let the sequence continue.

I suggest you ignore the DB for now, keep running the sequence locally, and when you're done with it post the .elf to the forum. A .elf file contains the factorizations of an aliquot sequence's numbers in plain text. It should be in aliqueit's folder and named alq_36684.elf.

Or if that sounds like too much trouble, you can just unreserve it and pick a new sequence to run. I'll put it back in the list of available sequences and someone else will do it.

I am at c104, i'll get it to 110 before releasing it, with the elf file

Correct me if I'm wrong, Mini-Geek, but doesn't submitting the full elf to the db via aliqueit, or submitting the correct lines manually, store the correct factored lines within the db? Then, when the 57, 159, etc. bugs are eradicated, the stored info will populate the db's sequences properly.

In this specific case, 512539091200423605342377877270021978828257857114084791961422307443426141684267634625913356380869010638 is the composite for iteration 871** of 36684 and the db has the next several lines up through a c105. So, firejuggler's input is apparently in the db, just not visible from the base 36684, until the 57 bug is chased away.

If the above is correct, there should be no need to post elfs, unless there is a reason for complete elfs elsewhere. Yes/No?

Additional thought: Someone who is taking a "buggy" sequence, should probably check their first new iteration against the db, to make sure it hasn't been added and is just not showing up due to the bug.

** iteration number fixed based on subsequent post by firejuggler

[quote=EdH;216215]
<snip>
In this specific case, 512539091200423605342377877270021978828257857114084791961422307443426141684267634625913356380869010638 is the composite for iteration 571 of 36684 and the db has the next several lines up through a c105. So, firejuggler's input is apparently in the db, just not visible from the base 36684, until the 57 bug is chased away.

</snip>
[/quote]
hm, iteration 871, for the sake of accuracy

[quote=firejuggler;216222]hm, iteration 871, for the sake of accuracy[/quote]
Indeed! Thanks! I must have had "57" stuck in my head. Oh, No! Perhaps I've contracted the bug from the db.:sad:

I was still able to edit the previous post, so I have done so, but added a note. . .