![]() |
[QUOTE=lorgix;278544]I still don't know how flags work. I can't restart a nfs-job, because I don't know how to supply the "-R".[/QUOTE]
How do you normally start yafu? |
[QUOTE=bsquared;278547]How do you normally start yafu?[/QUOTE]
I generally double-click the exe. I use cmd for batchfiles. |
[QUOTE=lorgix;278550]I generally double-click the exe.
[/QUOTE] There's the issue. Use cmd to open a console window, navigate to your yafu directory, then you'll be able to type something like: [CODE]yafu-32k-x64.exe "nfs(<num>)" -R[/CODE] |
[QUOTE=bsquared;278551]There's the issue.
Use cmd to open a console window, navigate to your yafu directory, then you'll be able to type something like: [CODE]yafu-32k-x64.exe "nfs(<num>)" -R[/CODE][/QUOTE] Aha, working now. Do I have to type [B]"nfs()"[/B]? [B]nfs() [/B]wont do? |
[QUOTE=lorgix;278553]Aha, working now.
Do I have to type [B]"nfs()"[/B]? [B]nfs() [/B]wont do?[/QUOTE] Good. On windows, either quotes or no quotes will work. On linux you need the quotes, so I'm in the habit of including them. |
Edit yafu.ini and add a line "R=1" (no quotes, just R=1) to it, wherever you like. It is good to have it and it makes no harm when you don't need it. If there aren't any file to resume from, and the line exists, then the line is ignored anyhow. If there are files to resume from, and you do not have the line, then you get the error "use -R to resume a partial job" or something like that, and the task is aborted. So, the best is always to have the line there. Then you can start yafu in the usual way, he will know when to resume without using the explicit switch -R in the command line. I use this for aliqueit, which is difficult to control what parameters it passes to yafu, and the idea proved to be very useful for interrupted jobs: they continue smooth regardless of what parameters aliqueit program uses when he calls yafu. If there is some aliquot term partially factored and resume files exist, then the factorization will always continue from where it was interrupted (except for poly selection phase on nfs, which is not yet able to resume in yafu).
edit: on windows quotes are optional, but you have to include them to eliminate ambiguities. For example when one of the parameters contain a space, it has to be put in quotes, otherwise the command interpreter will take it as two different parameters. Semantically, windows completely ignores the quotes, they have no meaning for him. For example, if you have a file called "my file.num" (with space) containing the numbers to factor, then you have to write: >yafu factor(@) -batchfile "my file" If you type >yafu factor(@) -batchfile my file then the command interpreter will look for a file called "my", which can not be found, and the line will get an error because the word "file" is interpreted as an additional parameter which is unwanted |
[QUOTE=LaurV;278612] Edit yafu.ini and add a line "R=1" (no quotes, just R=1) to it, wherever you like.
[/QUOTE] Yep, that will work too. [QUOTE=LaurV;278612] (except for poly selection phase on nfs, which is not yet able to resume in yafu). [/QUOTE] This is coming soon... :smile: |
What's the flag to use yafu at idle priority? I can't find it on the docfile.txt. Thank you in advance.
|
[QUOTE=pinhodecarlos;279378]What's the flag to use yafu at idle priority? I can't find it on the docfile.txt. Thank you in advance.[/QUOTE]
It doesn't have one. In windows you can use task manager and in linux you can use nice. |
[QUOTE=bsquared;279379]It doesn't have one. In windows you can use task manager and in linux you can use nice.[/QUOTE]
What a pity, I was running this [url=http://www.mersenneforum.org/showpost.php?p=270964&postcount=1225]script[/url] but everytime a new integer is processed yafu starts it at normal priority. |
[QUOTE=pinhodecarlos;279380]What a pity, I was running this [URL="http://www.mersenneforum.org/showpost.php?p=270964&postcount=1225"]script[/URL] but everytime a new integer is processed yafu starts it at normal priority.[/QUOTE]
Couldn't the script be modified to invoke yafu at low priority then? |
| All times are UTC. The time now is 22:56. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.