Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ecmfactor should take as optional argument the sigma value #10951

Closed
zimmermann6 opened this issue Mar 17, 2011 · 27 comments
Closed

ecmfactor should take as optional argument the sigma value #10951

zimmermann6 opened this issue Mar 17, 2011 · 27 comments

Comments

@zimmermann6
Copy link

I suggest the ecmfactor function takes as optional argument a sigma
value, which would be passed to GMP-ECM. In case of a successful
factorization, this would allow to know the lucky curve, for
example to report it on some tables of records.

For example I found a 61-digit prime factor using ecmfactor,
but was unable to know the lucky sigma
(http://www.loria.fr/~zimmerma/records/ecmnet.html).

Alternatively, one could store the (random) sigma value chosen by
GMP-ECM if not sigma was given, but that might be more difficult to
implement.

CC: @aghitza @JohnCremona @rlmill @jpflori

Component: factorization

Keywords: sd32, sd40.5

Author: Paul Zimmermann

Branch: 4a59cea

Reviewer: Mike Hansen, Frédéric Chapoton, Jean-Pierre Flori

Issue created by migration from https://trac.sagemath.org/ticket/10951

@zimmermann6
Copy link
Author

comment:1

Attachment: trac_10951.patch.gz

the attached file does two things:

(1) if an optional sigma=nnn input is given to ecmfactor, it uses that value (nnn) to choose the elliptic curve, instead of a random one. This allows to get a deterministic behaviour;

(2) if a non-trivial factor was found (with a random or user-given sigma) it is returned by
ecmfactor, which now returns (True, N, sigma)

Paul

@sagetrac-mariah
Copy link
Mannequin

sagetrac-mariah mannequin commented May 24, 2011

comment:3

This function seems to lack documentation. I do not see anything about it at http://sagemath.org/doc/reference/libs.html.

@sagetrac-mariah sagetrac-mariah mannequin modified the milestones: sage-4.7, sage-4.7.1 May 24, 2011
@zimmermann6
Copy link
Author

comment:4

Replying to @sagetrac-mariah:

This function seems to lack documentation. I do not see anything about it at http://sagemath.org/doc/reference/libs.html.

you are right. However this was already the case before my patch. The best would be to open a
separate ticket to add documentation for this function.

Paul

@williamstein
Copy link
Contributor

Changed keywords from none to sd32

@mwhansen
Copy link
Contributor

Author: Paul Zimmerman

@mwhansen
Copy link
Contributor

Reviewer: Mike Hansen

@mwhansen
Copy link
Contributor

comment:7

Looks good to me. I've made #13042 to add the module to the reference manual.

@mwhansen
Copy link
Contributor

Changed keywords from sd32 to sd32, sd40.5

@jdemeyer
Copy link

Work Issues: rebase, documentation

@jdemeyer
Copy link

comment:8

This patch should still be rebased to #12777 and the new option should be documented.

@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin removed this from the sage-6.3 milestone Aug 10, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin added this to the sage-6.4 milestone Aug 10, 2014
@zimmermann6
Copy link
Author

comment:13

any progress on this? I just found a 59-digit factor with ecmfactor, but I'm unable to know which sigma value was used. If I was able to give the sigma value, I would know.

Paul

@zimmermann6
Copy link
Author

comment:14

rebased with the help of Marc Mezzarobba. Remains to do:

  • check tests
  • add documentation

@zimmermann6
Copy link
Author

Changed work issues from rebase, documentation to documentation

@zimmermann6
Copy link
Author

Branch: u/zimmerma/10951

@zimmermann6
Copy link
Author

Commit: 5c6c5a2

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 2, 2015

Branch pushed to git repo; I updated commit sha1. New commits:

d6487b0Merge remote-tracking branch 'origin/u/vbraun/fix_python_tarball_names' into 10951
27c99e1fixes and improved documentation

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 2, 2015

Changed commit from 5c6c5a2 to 27c99e1

@zimmermann6
Copy link
Author

comment:16

I've added documentation in the new patch 27c99e1.
Ready for review again.
Paul


New commits:

d6487b0Merge remote-tracking branch 'origin/u/vbraun/fix_python_tarball_names' into 10951
27c99e1fixes and improved documentation

@zimmermann6
Copy link
Author

Changed work issues from documentation to none

@fchapoton
Copy link
Contributor

comment:18

this looks good to me.

I have removed some of the newly introduced random keywords.

If somebody else agrees, this can be put into positive review.


New commits:

173f5b0patch for #10951 (added optional input of sigma, and return lucky sigma)
45a5de7fixes and improved documentation
4a59ceatrac #10951 not so many random

@fchapoton
Copy link
Contributor

Changed branch from u/zimmerma/10951 to public/ticket/10951

@fchapoton
Copy link
Contributor

Changed commit from 27c99e1 to 4a59cea

@fchapoton fchapoton modified the milestones: sage-6.4, sage-6.9 Aug 9, 2015
@jpflori
Copy link

jpflori commented Aug 10, 2015

Changed reviewer from Mike Hansen to Mike Hansen, Frédéric Chapoton, Jean-Pierre Flori

@vbraun
Copy link
Member

vbraun commented Aug 11, 2015

Changed branch from public/ticket/10951 to 4a59cea

@zimmermann6
Copy link
Author

Changed commit from 4a59cea to none

@zimmermann6
Copy link
Author

comment:22

thank you Frederic for your review. For ecmfactor(2^167-1, 2e5) the 7-digit factor is always found by ECM since the curve has order divisible by 12 at least. However the 44-digit factor might be found in some (very) rare cases, which was the reason for the "random" keyword. The other cases are fine.

Paul

@fchapoton
Copy link
Contributor

Changed author from Paul Zimmerman to Paul Zimmermann

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants