[QUOTE=cmd;261862]so :

[code]

[B]???? ???? ???? ????[/B]

¿¿¿¿ ¿¿¿¿ ¿¿¿¿ ¿¿¿¿

[I]???? ???? ???? ????[/I]

¿¿¿¿ ¿¿¿¿ ¿¿¿¿ ¿¿¿¿

[B]???? ???? ???? ????[/B]

[/code][/QUOTE]

Can someone please stop this guy from spamming this thread!

He got his own thread to post such things.

Thanks.

[QUOTE=kar_bon;261894]Can someone please stop this guy from spamming this thread!

He got his own thread to post such things.

Thanks.[/QUOTE]I deleted many of his posts in this thread. Didn't check if any of them was useful (which i doubt).

I'll propose a ban if he continues.

Has something changed in the format expected by the DB when submitting factors? As of 3-4 days ago, I could submit a factorization from the command line using a command like this:
[CODE]
wget http://factordb.com/report.php --post-data="report=true&msub=13190789828154072917143593725962464892772345908077188923589296347603204686539531 = 51467689791946698239 * 256292634883683371484524861104319590830984670961919826205429"
[/CODE]But now that doesn't seem to work -- when I query the composite it still shows up as unfactored. If I report the factors manually through the web page, it does work, although I get a strange-looking message like:

[CODE]51467689791946698239: factor already known
51467689791946698239: new factor[/CODE]

Is anyone else having this problem? Am I using the wrong wget command to submit?

[QUOTE=bchaffin;261938]
Is anyone else having this problem? Am I using the wrong wget command to submit?[/QUOTE]

I did a few small changes to the submit form, i think only the variable name changed. But keep your script, I'll make both variables work. Easier this way.

[QUOTE]How can I check a few hundred numbers to learn if factordb has a full factorization?[/QUOTE]

At the moment there is no way to do this with one request.

[QUOTE=Syd;261946]I did a few small changes to the submit form, i think only the variable name changed. But keep your script, I'll make both variables work. Easier this way.[/QUOTE]

Thanks Syd, that was fast -- it's working now.

I changed a few more things, thats:
-the input parser. It may give some error messages, I'm working on it
-ecm/p+1/p-1-results are now also saved. Just copy the whole gmp-ecm output inside the results box
-someone used to flood and fill the database with random numbers, so I put some limits per IP in there. Tell me if they are too low!
-added a little tool to calculate ecm group orders
([url]http://factordb.com/groupcalc.php[/url])

I hope everything is working!

Now I'm going to prp-test all numbers up to at least 10k digits. This will take some time.

[QUOTE=Syd;261984]I changed a few more things, thats:
-the input parser. It may give some error messages, I'm working on it
-ecm/p+1/p-1-results are now also saved. Just copy the whole gmp-ecm output inside the results box
-someone used to flood and fill the database with random numbers, so I put some limits per IP in there. Tell me if they are too low!
-added a little tool to calculate ecm group orders
([URL]http://factordb.com/groupcalc.php[/URL])

I hope everything is working!

Now I'm going to prp-test all numbers up to at least 10k digits. This will take some time.[/QUOTE]

I reached the hourly limit on CPU-time in 58 minutes.

I used to be able to submit things like

[code]
271427466523206484847994068911650639605211252676780737908688140410714736524641091422630657735093035601853065255927575880416555215109540024045933346045786966=2*3^2*7*37*168148369*3203229620049913*1360431734531670131847561541955682301592960850611*79455513541390151139958754790541060250889700879428962184770179563141553469758579
418843675097827265722980539527791853106180383815497669797039425714247050685769210356616440350089340212315250921632616394203641575784352554580820377145329834=2*3^2*7*43*857*210643*908419*3039056421010273*155117263844215027452110925603234757817465496458519899734548941351870914781082539019827558204805397920484658160909905437649
643657055044722845453318200858189786179249238618662777304007190201623142612757306498360771216457869756045243113995195885302297974328444182051312004489742166=2*3^3*7*101*857*1193*1801*1692221*5410648256741139118184621944921333176675429270768776125309616588165637564050976395580889554876497334385323055655980821367054780283818207
[/code]

to the report-factors box, to report an extension of an aliquot sequence. This no longer works - I get an error message 'factor already known', but the sequence does not extend.

The "elf-file" format ("index . composite = factor*factor...") is not accepted anymore!?
So the command "aliqueit -s " does not work for me.
Index and composite merge to one number and so just reporting some (already known) factors and there is no extension of sequences!?

[QUOTE=RobertS;262005]The "elf-file" format ("index . composite = factor*factor...") is not accepted anymore!?
[/QUOTE]

*gulp*
If that's intended, this might make me (and probably others who don'tg want to enter factor by factor manually) quit the aliquot project.

[QUOTE=lorgix;261995]I reached the hourly limit on CPU-time in 58 minutes.[/QUOTE]

No problem, I increased this limit.

[QUOTE=fivemack;262001]I used to be able to submit things like
to the report-factors box, to report an extension of an aliquot sequence. This no longer works - I get an error message 'factor already known', but the sequence does not extend.[/QUOTE]

[QUOTE=RobertS;262005]The "elf-file" format ("index . composite = factor*factor...") is not accepted anymore!?
So the command "aliqueit -s " does not work for me.
Index and composite merge to one number and so just reporting some (already known) factors and there is no extension of sequences!?[/QUOTE]

This was a bug within the new parser. I think I found the bug now, just the output is still a little bit messy.

[QUOTE]*gulp*
If that's intended, this might make me (and probably others who don'tg want to enter factor by factor manually) quit the aliquot project. [/QUOTE]

No, it was not intended!!