mersenneforum.org GNFS
 Register FAQ Search Today's Posts Mark Forums Read

2022-08-13, 22:41   #23
chalsall
If I May

"Chris Halsall"
Sep 2002

13·821 Posts

Quote:
 Originally Posted by storm5510 Time will tell.
No insult intended towards anyone. But William S. Burroughs has often been someone worth listening to in my world.

Quite insane. And quite insightful.

2022-08-13, 22:50   #24
charybdis

Apr 2020

857 Posts

Quote:
 Originally Posted by storm5510 I could use this for each new job from the start, unless CADO insists on using /tmp. I take it the path from / would have to be fully resolved. if I could start it with "/home" it would make for a shorter command line.
Using shortcuts in the path is fine. CADO creates a directory in /tmp by default, but you can put the path anywhere you want, preferably not in /tmp.

Why do you care about the length of the command line?

2022-08-14, 00:01   #25
storm5510
Random Account

Aug 2009
Not U. + S.A.

44358 Posts

Quote:
 Originally Posted by charybdis Using shortcuts in the path is fine. CADO creates a directory in /tmp by default, but you can put the path anywhere you want, preferably not in /tmp. Why do you care about the length of the command line?
No particular reason.

I was considering putting a folder in /home. This is way I asked about the path.

2022-08-14, 00:28   #26
chalsall
If I May

"Chris Halsall"
Sep 2002

13×821 Posts

Quote:
 Originally Posted by storm5510 I was considering putting a folder in /home. This is way I asked about the path.
Please forgive me if I come across as a pedantic teacher, but...

I would suggest you go just a little bit further, and have a unique path into a /home/ sub-directory the running process will be able to write to. This presumes Linux of course. I don't do Windows...

This then lets you do all kinds of fun stuff in the many-to-many space.

Again... As my stepfather (John K.) always told me, "Please ignore me if I'm telling you how to chew gum.

 2022-08-14, 03:23 #27 storm5510 Random Account     Aug 2009 Not U. + S.A. 91D16 Posts Same assignment, totally different machine, again failed to complete. This time, it took the log files with it. It was the same error in the same place at the end of the LA. I still have the log files from the Xeon. "No tuned configuration" was one item. Code: can't find any F file, cannot infer the mksol max iteration at /home/storm5510/cado-nfs/build/1620XE/linalg/bwc/bwc.pl line 1499. Check for mksol, Please run lingen first. It seem there is more I need to do...
 2022-08-14, 05:15 #28 VBCurtis     "Curtis" Feb 2005 Riverside, CA 5,483 Posts Well, it's strange that you're getting the same error on two machines that none of us have seen before. Yet, you're letting CADO decide where to store the files, which reduces the chance this is some weird effect of folder read/write permissions. Are you running the job with ./cado-nfs.py {your number here}? Have you altered any of the params files from the defaults included with the package? Have you gotten a smaller number to factor with CADO (which suggests perhaps *this* number triggers a rare bug). In short, I don't think you're doing anything wrong *if* you've gotten some smaller number to factor completely (I use RSA-100 for a test, for instance).
2022-08-14, 15:43   #29
storm5510
Random Account

Aug 2009
Not U. + S.A.

44358 Posts

Quote:
 Originally Posted by VBCurtis Well, it's strange that you're getting the same error on two machines that none of us have seen before. Yet, you're letting CADO decide where to store the files, which reduces the chance this is some weird effect of folder read/write permissions. Are you running the job with ./cado-nfs.py {your number here}? Have you altered any of the params files from the defaults included with the package? Have you gotten a smaller number to factor with CADO (which suggests perhaps *this* number triggers a rare bug). In short, I don't think you're doing anything wrong *if* you've gotten some smaller number to factor completely (I use RSA-100 for a test, for instance).
I wrote a bash file:

Code:
./cado-nfs.py workdir=/home/temp <number here> -t 6
I ran this on the i7 dual-boot overnight with my previous assignment from Kamada's site. It failed, but it was different this time. I swear I saw something about "0 (zero) disk space" in a log file.

I tried to run RSA-100 as a test on the Xeon. It also failed. A screenshot of the error section is attached below. It has a 500 GB drive in it. One of the utilities says it has 473 GB available.

These text lines are always part of the last screen output, except for last night.

Code:
## Check for mksol: Lingen output files missing
## Check for mksol: cant find any F file...
## Check for mksol: Please run lingen first.
I set the work directory in the invocation line, but there is never any output since I started specifying it. It's almost like it's being block somehow.
Attached Thumbnails

 2022-08-14, 17:27 #30 EdH     "Ed Hall" Dec 2009 Adirondack Mtns 4,909 Posts You have to use tasks.workdir rather than just workdir. Check cado-nfs/parameters/factor/params.c90 for all the options and full variable names.
2022-08-14, 17:39   #31
charybdis

Apr 2020

857 Posts

Quote:
 Originally Posted by EdH You have to use tasks.workdir rather than just workdir.
Not true. The main CADO readme even has examples with just "workdir".

2022-08-14, 18:13   #32
EdH

"Ed Hall"
Dec 2009

4,909 Posts

Quote:
 Originally Posted by charybdis Not true. The main CADO readme even has examples with just "workdir".
Thank you for the correction!

2022-08-14, 18:29   #33
storm5510
Random Account

Aug 2009
Not U. + S.A.

2,333 Posts

I was successfully able to run the RSA-100 test to its conclusion. I ran it as it appears below. Nothing more added. The result was two large factors. If it wrote them into a file, I can't find it.

Code:
./cado-nfs.py 1522605027922533360535618378132637429718068114961380688657908494580122963258952897654000350692006139
The project I am working in is owned and operated by Makoto Kamada and is here. I was referred to this site by swellman after James' project was complete.

Kamada does not want just factors. He wants to see how the process was done from Point A to Point Z. A good example is Yafu's factor.log. This is what I've sent him so far and he is not opposed to it. I can't find a similar file created by CADO-NFS. If it's there, it's really buried deep. Yafu's caveat is that it takes a lot more time.

I find CADO-NFS very interesting, but most of what I see sails over my head. It's too complex for this old brain.

Quote:
 Originally Posted by charybds Not true. The main CADO readme even has examples with just "workdir".
I originally tried it this way. It didn't seem to write anything anywhere. Not in /tmp or /home/temp I created. On one instance, it refused to start, period.

Last fiddled with by storm5510 on 2022-08-14 at 18:33 Reason: Additional

 Similar Threads Thread Thread Starter Forum Replies Last Post pinhodecarlos NFS@Home 0 2014-12-24 19:13 pinhodecarlos NFS@Home 34 2014-04-01 21:27 fivemack Factoring 84 2011-04-26 10:22 10metreh Factoring 48 2009-04-08 01:54 Andi47 Msieve 5 2009-01-26 18:19

All times are UTC. The time now is 20:29.

Sun Oct 2 20:29:40 UTC 2022 up 45 days, 17:58, 0 users, load averages: 0.65, 0.91, 1.06