Feromant_CUDA: worktodo file

feromant · 2016-12-05, 17:21

The program is not yet always properly can handle jobs from a file worktodo. This is due to the overlap with one range of multiple kernels. It will therefore require manual adjustment. The rule is simple: one line - one kernel.

The program includes the following kernels:
feromant96bit_n32_63
feromant128bit_n32_63
feromant128bit_n64_95
feromant160bit_n64_95
feromant160bit_n96_127
feromant192bit_n96_127
feromant192bit_n128_159
feromant224bit_n128_159
feromant224bit_n160_191
feromant256bit_n160_191
feromant256bit_n192_223
feromant288bit_n192_223
feromant288bit_n224_255
feromant320bit_n224_255
feromant320bit_n256_287
feromant352bit_n256_287
feromant352bit_n288_319
feromant384bit_n288_319
feromant384bit_n320_351
feromant416bit_n320_351
feromant416bit_n352_383
feromant448bit_n352_383
feromant448bit_n384_415
feromant480bit_n384_415
feromant480bit_n416_447
feromant512bit_n416_447
feromant512bit_n448_479
feromant544bit_n448_479
feromant544bit_n480_511
feromant576bit_n480_511
feromant576bit_n512_543
feromant608bit_n512_543
feromant608bit_n544_575
For example, kernel feromant320bit_n256_287 processes factors with exponents of n from 256 to 287 and up to 320 bits.

Example 1 (The job crosses the boundaries of the kernels in the exponent values n).
The string
FermatFactor=280,289,3000000000000,30000000000000
must be split into two:
FermatFactor=280,287,3000000000000,30000000000000 (handled by feromant352bit_n256_287)
FermatFactor=288,289,3000000000000,30000000000000 (handled by feromant352bit_n288_319)

Example 2 (The job crosses the boundaries of the kernels in the factor's bits).
The string
FermatFactor=300,309,30000000000000,80000000000000
must be split into following strings:
FermatFactor=300,305,30000000000000,80000000000000 (handled by feromant352bit_n288_319)
FermatFactor=306,306,30000000000000,70368744177663 (handled by feromant352bit_n288_319)
FermatFactor=306,306,70368744177665,80000000000000 (handled by feromant384bit_n288_319)
FermatFactor=307,307,30000000000000,35184372088831 (handled by feromant352bit_n288_319)
FermatFactor=307,307,35184372088833,80000000000000 (handled by feromant384bit_n288_319)
FermatFactor=308,309,30000000000000,80000000000000 (handled by feromant384bit_n288_319)

I'm sorry for the inconvenience. Automation of this process is included in the list of priority improvements of program and will be added in the next version v2.017.

feromant · 2017-07-13, 16:25

The problem is solved in the version 2.017, which can be downloaded here:
http://www.fermatsearch.org/prog/Fer...A%20v2.017.zip

2016-12-05, 17:21	#1
feromant "Roman" Dec 2016 Everywhere 2×13 Posts	Feromant_CUDA: worktodo file The program is not yet always properly can handle jobs from a file worktodo. This is due to the overlap with one range of multiple kernels. It will therefore require manual adjustment. The rule is simple: one line - one kernel. The program includes the following kernels: feromant96bit_n32_63 feromant128bit_n32_63 feromant128bit_n64_95 feromant160bit_n64_95 feromant160bit_n96_127 feromant192bit_n96_127 feromant192bit_n128_159 feromant224bit_n128_159 feromant224bit_n160_191 feromant256bit_n160_191 feromant256bit_n192_223 feromant288bit_n192_223 feromant288bit_n224_255 feromant320bit_n224_255 feromant320bit_n256_287 feromant352bit_n256_287 feromant352bit_n288_319 feromant384bit_n288_319 feromant384bit_n320_351 feromant416bit_n320_351 feromant416bit_n352_383 feromant448bit_n352_383 feromant448bit_n384_415 feromant480bit_n384_415 feromant480bit_n416_447 feromant512bit_n416_447 feromant512bit_n448_479 feromant544bit_n448_479 feromant544bit_n480_511 feromant576bit_n480_511 feromant576bit_n512_543 feromant608bit_n512_543 feromant608bit_n544_575 For example, kernel feromant320bit_n256_287 processes factors with exponents of n from 256 to 287 and up to 320 bits. Example 1 (The job crosses the boundaries of the kernels in the exponent values n). The string FermatFactor=280,289,3000000000000,30000000000000 must be split into two: FermatFactor=280,287,3000000000000,30000000000000 (handled by feromant352bit_n256_287) FermatFactor=288,289,3000000000000,30000000000000 (handled by feromant352bit_n288_319) Example 2 (The job crosses the boundaries of the kernels in the factor's bits). The string FermatFactor=300,309,30000000000000,80000000000000 must be split into following strings: FermatFactor=300,305,30000000000000,80000000000000 (handled by feromant352bit_n288_319) FermatFactor=306,306,30000000000000,70368744177663 (handled by feromant352bit_n288_319) FermatFactor=306,306,70368744177665,80000000000000 (handled by feromant384bit_n288_319) FermatFactor=307,307,30000000000000,35184372088831 (handled by feromant352bit_n288_319) FermatFactor=307,307,35184372088833,80000000000000 (handled by feromant384bit_n288_319) FermatFactor=308,309,30000000000000,80000000000000 (handled by feromant384bit_n288_319) I'm sorry for the inconvenience. Automation of this process is included in the list of priority improvements of program and will be added in the next version v2.017.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Error in Worktodo file	GARYP166	Information & Answers	34	2009-11-30 16:35
WorkToDo File	storm5510	Software	9	2009-08-18 00:18
N/A in my worktodo.txt file?	uigrad	PrimeNet	13	2008-11-10 13:12
Inclusion of worktodo.add file?	Graff	PrimeNet	17	2008-11-01 01:49
worktodo.ini	clowns789	Software	7	2003-10-21 03:57

2017-07-13, 16:25	#2
feromant "Roman" Dec 2016 Everywhere 2·13 Posts	The problem is solved in the version 2.017, which can be downloaded here: http://www.fermatsearch.org/prog/Fer...A%20v2.017.zip