![]() |
|
|
#1 |
|
Sep 2004
5×37 Posts |
Hi jasonp !
I'll quote the msieve faq : Q. Why did you stop at 125 digits? I want to factor much bigger numbers. Does this limit still holds for the nfs part of the code? I am currently sieving a 128 digits composite with ggnfs and would be interested in the msieve classical sieve... Thanks. Philippe. |
|
|
|
|
|
#2 | |
|
Tribal Bullet
Oct 2004
3,541 Posts |
Quote:
Note that when the postprocessing can actually work, similar instructions will allow a GGNFS factorization to be completed using msieve. It would be interesting to compare the matrices generated by the two packages. jasonp ------------------ Assuming you have a binary compiled with a larger limit on the input size (I can provide one if this is a problem), to run the line siever you just need to provide a factor base file. This is a text file with the following lines: N <the number you are factoring> R0 <low-order coefficient of rational polynomial> R1 <high-order coefficient of rational polynomial> A0 <low-order coefficient of algebraic polynomial> A1 ... A2 ... A3 ... A4 ... A5 <high-order coefficient of algebraic polynomial> Running msieve -i <file_with_number> -nf <factor_base_file> -ns X,Y (with X and Y the lower and upper limits of sieve lines) will then run the line siever. It will generate the rest of the factor base and sieving parameters, then dump any relations found to msieve.dat Note that the first line of msieve.dat does not contain a relation, so hopefully this won't give procrels any trouble. Last fiddled with by jasonp on 2006-08-24 at 12:28 |
|
|
|
|
|
|
#3 |
|
"Sander"
Oct 2002
52.345322,5.52471
22458 Posts |
|
|
|
|
|
|
#4 |
|
Jul 2003
So Cal
2·34·13 Posts |
Thanks Jason for all the work you're putting into this! I have two questions. Does msieve support 4th or 6th order algebraic polynomials as well, or only 5th order? And is the 155 digit limit a limit of the MP code or could it be used with larger SNFS factorizations?
Thanks! Greg |
|
|
|
|
|
#5 |
|
Tribal Bullet
Oct 2004
3,541 Posts |
smh,
I wouldn't use a range larger than [1,4000]. The line size will always be the same, but it should really be varied, so that smaller values get a larger line size George, I don't want to get to a lattice siever (or any other optimization) until the library can complete an end-to-end GNFS factorization. It's the first priority when I get to that point though frmky, Incrementing MAX_POLY_DEGREE should allow the code to handle 6th degree polynomials. It can only *generate* 5th degree, though; the whole poly generator is going to get overhauled someday, and I didn't see the point of bothering with 4th-degree polynomials until that has happened. Thanks for the support everybody; if experience is any guide, the first few factorizations done with the new library are going to be very dicey, so please be patient if you want to help out. jasonp |
|
|
|
|
|
#6 |
|
Aug 2006
Monza, Italy
73 Posts |
I assume you can use the 1.10 msieve.dat file: I tried that and got no errors. Is that correct?
|
|
|
|
|
|
#7 | |
|
Tribal Bullet
Oct 2004
3,541 Posts |
Quote:
jasonp |
|
|
|
|
|
|
#8 | |
|
Mar 2007
22 Posts |
Quote:
may thanks ! |
|
|
|
|
|
|
#9 | |
|
Tribal Bullet
Oct 2004
354110 Posts |
Quote:
msieve -v -i <file with input number> -nf <file with polynomial> -s <huge savefile> -nc If it still crashes, and takes a while to do so, then it's probably a bug somewhere (according to your post in the GGNFS mailing list, you're trying to boil down 40 million relations, or 5x more than anyone else has tried so far). If this is on a windows system, and the file is larger than 2GB or 4GB, there could be trouble (though the library only makes sequential passes through the file, on purpose). jasonp |
|
|
|
|
|
|
#10 |
|
Mar 2007
22 Posts |
hi jason, thanks for answering.
my first attempt was only the goal to use the polynomial i found with ggnfs and start sieving with msieve. a 2nd goal would be trying to use the old relations (this was not what i was trying atm) i will try in the evening as you pointed out . Thanks for the help ! greets Update: i tried it as you said but same segfault msieve -v -i <file with input number> -nf <file with polynomial> -s <huge savefile> -nc size score = 0.000000e+00, Murphy alpha = 0.000000, combined = 0.000000e+00 generating factor base Segmentation fault in the <file with polynomial> i put N 12345 (mynumber) R0 12345 R1 12345 A0 12345 A1 12345 .. A5 12345 with R0 == Y0 and R1 == Y1 from ggnfs and mapping Ax to cX from ggnfs is this ok ? Last fiddled with by bigmic on 2007-03-21 at 19:42 |
|
|
|
|
|
#11 | |
|
Tribal Bullet
Oct 2004
3,541 Posts |
Quote:
jasonp |
|
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| error when running msieve 1.53 with cuda | aein | Msieve | 9 | 2019-02-25 14:09 |
| Help need to running Msieve | appleseed | Msieve | 12 | 2016-04-10 02:31 |
| Problem in running msieve with CUDA | mohamed | Msieve | 20 | 2013-08-01 08:27 |
| CUDA_ERROR_LAUNCH_OUT_OF_RESOURCES when running msieve 1.5.0 with CUDA | ryanp | Msieve | 3 | 2012-06-12 03:27 |
| Trouble Running Msieve | Sab | Msieve | 4 | 2009-07-07 06:19 |