Posts by forretrio

1) Message boards : Number crunching : Task reruns after finishing (Message 995)
Posted 13 May 2017 by forretrio
Post:
https://yafu.myfirewall.org/yafu/result.php?resultid=1016278

Recently one of my 8t task kind of hanged my machine and forced me for restart the manager. However I waited the the task to complete (but it failed to submit it). Here are the last few lines of the factor file:

05/13/17 12:33:13 v1.34.5 @ REMI-N, nfs: raising min_rels by 5.00 percent to 11320758
05/13/17 12:33:13 v1.34.5 @ REMI-N, nfs: commencing lattice sieving with 8 threads
05/13/17 12:43:57 v1.34.5 @ REMI-N, nfs: commencing lattice sieving with 8 threads
05/13/17 12:52:23 v1.34.5 @ REMI-N, nfs: commencing lattice sieving with 8 threads
05/13/17 13:00:43 v1.34.5 @ REMI-N, nfs: commencing lattice sieving with 8 threads
05/13/17 13:09:37 v1.34.5 @ REMI-N, nfs: commencing msieve filtering
05/13/17 13:13:23 v1.34.5 @ REMI-N, nfs: commencing msieve linear algebra
05/13/17 13:44:18 v1.34.5 @ REMI-N, nfs: commencing msieve sqrt
05/13/17 14:01:32 v1.34.5 @ REMI-N, prp76 = 1089166811196532289855261540103998746537161103288818992879418747458942383217
05/13/17 14:01:32 v1.34.5 @ REMI-N, prp50 = 56776958843214016172259292138564062174520464953027
05/13/17 14:01:32 v1.34.5 @ REMI-N, NFS elapsed time = 55884.8434 seconds.
05/13/17 14:01:32 v1.34.5 @ REMI-N,
05/13/17 14:01:32 v1.34.5 @ REMI-N,
05/13/17 14:01:32 v1.34.5 @ REMI-N, Total factoring time = 61170.5279 seconds


That indicates that the number concerned can be factorized as

1051328063
*56776958843214016172259292138564062174520464953027
*1089166811196532289855261540103998746537161103288818992879418747458942383217

which is indeed true by checking it manually.

When I restarted the manager, the task restarted halfway (which always happens to me), but I do not want to rerun the task as this is a waste of resources as the factorization is all we want and we have it already.

I know this is a bit suspicious because it is impossible to determine whether the CPU time is true for the above log (I swear it to be true), but can I simply abort the task but still get credit for it?

I have the complete stderr and factor log, and hopefully the other files are not destroyed by restarting the calculation.
2) Message boards : Number crunching : Workunit 835151 (Message 958)
Posted 20 Mar 2017 by forretrio
Post:
Given how the apps are coded as described, you may not want to run the longer tasks if your computer crashes often or in general unstable.

The progress bar is useless here. To check progress you may want to open the slot and check the files inside. During the NFS factorization when it's still generating relations there is no way that you can tell the time it takes, but once it goes into the linear algebra phase the estimated time of completion should be manageable.
3) Message boards : Number crunching : Elapsed time going back (Message 920)
Posted 15 Dec 2016 by forretrio
Post:
https://yafu.myfirewall.org/yafu/result.php?resultid=914592

The task is completed today and I am granted credits for ~1 day of computation but I actually crunched for ~2.5 days. Not that I am complaining about the credits, I just want to know what's wrong with my computer...
4) Message boards : Number crunching : Elapsed time going back (Message 919)
Posted 14 Dec 2016 by forretrio
Post:
I am currently crunching a task (30+ hours and counting...)

Suddenly the elapsed time went from ~30 hours back to 17 hours or so, and the progress bar dropped from 99% back to 92%.

I checked the flies in the corresponding slot but it does not seemed to lose any data:

stderr: the q keeps increasing with no significant gap
out:

nfs: commencing algebraic side lattice sieving over range: 5400000 - 5410000
nfs: commencing algebraic side lattice sieving over range: 5410000 - 5420000
nfs: commencing algebraic side lattice sieving over range: 5420000 - 5430000
nfs: commencing algebraic side lattice sieving over range: 5450000 - 5460000
nfs: commencing algebraic side lattice sieving over range: 5460000 - 5470000
nfs: commencing algebraic side lattice sieving over range: 5440000 - 5450000
nfs: commencing algebraic side lattice sieving over range: 5470000 - 5480000
nfs: commencing msieve filtering
883936859999360254883432506262500707615680332140753100657327354146703810893802990399354335419931349685352405298202636957369
read 10M relations
nfs: commencing algebraic side lattice sieving over range: 5510000 - 5520000
nfs: commencing algebraic side lattice sieving over range: 5500000 - 5510000
nfs: commencing algebraic side lattice sieving over range: 5490000 - 5500000
nfs: commencing algebraic side lattice sieving over range: 5480 Warning: lowering FB_bound to 5479999.
Warning: lowering FB_bound to 5499999.
Warning: lowering FB_bound to 5509999.
Warning: lowering FB_bound to 5489999.
missing variable indicator (@) in input expression
ignoring any input expression: interpreting batchfile lines as input expressions


=== Starting work on batchfile expression ===
factor(883936859999360254883432506262500707615680332140753100657327354146703810893802990399354335419931349685352405298202636957369)
=============================================
Warning: lowering FB_bound to 5519988.
Warning: lowering FB_bound to 5549988.
missing variable indicator (@) in input expression
ignoring any input expression: interpreting batchfile lines as input expressions


=== Starting work on batchfile expression ===
factor(883936859999360254883432506262500707615680332140753100657327354146703810893802990399354335419931349685352405298202636957369)
=============================================


factor
12/15/16 00:55:51 v1.34.5 @ FLANDRE-SCO, nfs: previous data file found - commencing search for last special-q
12/15/16 00:56:50 v1.34.5 @ FLANDRE-SCO, nfs: parsing special-q from .dat file
12/15/16 00:56:50 v1.34.5 @ FLANDRE-SCO, nfs: commencing nfs on c123: 883936859999360254883432506262500707615680332140753100657327354146703810893802990399354335419931349685352405298202636957369
12/15/16 00:56:50 v1.34.5 @ FLANDRE-SCO, nfs: resuming with filtering
12/15/16 00:56:50 v1.34.5 @ FLANDRE-SCO, nfs: commencing msieve filtering
12/15/16 01:03:52 v1.34.5 @ FLANDRE-SCO, nfs: raising min_rels by 5.00 percent to 10848335
12/15/16 01:03:52 v1.34.5 @ FLANDRE-SCO, nfs: commencing lattice sieving with 4 threads
12/15/16 02:55:42 v1.34.5 @ FLANDRE-SCO,
12/15/16 02:55:42 v1.34.5 @ FLANDRE-SCO, ****************************
12/15/16 02:55:42 v1.34.5 @ FLANDRE-SCO, Starting factorization of 883936859999360254883432506262500707615680332140753100657327354146703810893802990399354335419931349685352405298202636957369
12/15/16 02:55:42 v1.34.5 @ FLANDRE-SCO, using pretesting plan: normal
12/15/16 02:55:42 v1.34.5 @ FLANDRE-SCO, no tune info: using qs/gnfs crossover of 95 digits
12/15/16 02:55:42 v1.34.5 @ FLANDRE-SCO, ****************************
12/15/16 02:55:42 v1.34.5 @ FLANDRE-SCO, nfs: previous data file found - commencing search for last special-q
12/15/16 02:56:37 v1.34.5 @ FLANDRE-SCO, nfs: parsing special-q from .dat file
12/15/16 02:56:37 v1.34.5 @ FLANDRE-SCO, nfs: commencing nfs on c123: 883936859999360254883432506262500707615680332140753100657327354146703810893802990399354335419931349685352405298202636957369
12/15/16 02:56:37 v1.34.5 @ FLANDRE-SCO, nfs: resuming with filtering
12/15/16 02:56:37 v1.34.5 @ FLANDRE-SCO, nfs: commencing msieve filtering
12/15/16 03:03:19 v1.34.5 @ FLANDRE-SCO, nfs: raising min_rels by 5.00 percent to 10848367
12/15/16 03:03:19 v1.34.5 @ FLANDRE-SCO, nfs: commencing lattice sieving with 4 threads
12/15/16 03:56:46 v1.34.5 @ FLANDRE-SCO, nfs: commencing lattice sieving with 4 threads


Two questions:

1) Is that normal? If not is it the problem of my computer or the app itself?
2) Will the cpu time/credits be probably calculated in the final result?
5) Questions and Answers : Windows : html screensaver (Message 918)
Posted 14 Dec 2016 by forretrio
Post:
I guess that solved my question then :) thanks
6) Questions and Answers : Windows : html screensaver (Message 916)
Posted 13 Dec 2016 by forretrio
Post:


I just had a quick screenshot in the hope that I didn't miss something. I had the task running and renamed graphics_app to graphics_app.exe then clicked show graphics, but I am still stuck at the initializing page. Do I need to modify yafu.html as you mentioned as well?
7) Questions and Answers : Windows : html screensaver (Message 914)
Posted 13 Dec 2016 by forretrio
Post:
Hi,

I just renamed graphics_app to graphics_app.exe but I am still stuck in the 'initializing' forever. Are there anything else I have to modify or it is just a problem of running javascripts on the browser?

Thanks :)







Datenschutz / Privacy Copyright © 2011-2024 Rechenkraft.net e.V. & yoyo