mfakto 0.12 available
 

I just released the Windows-version of mfakto 0.12 on
[URL]http://mersenneforum.org/mfakto/mfakto-0.12/[/URL]

These are the changes:
[LIST][*] IMPORTANT: bugfix for missing factors for certain exponent ranges. Thanks to dabaichi and Axelsson for bug report and help on [URL]http://mersenneforum.org/showthread.php?t=13977&page=16#383[/URL][*]handling of <worktodo>.add (worktodo file name as configured, with suffix replaced): will be appended to <worktodo> between 5 and ~10 minutes after the add file's creation, or when moving to the next assignment[*]new mfakto.ini key SieveCPUMask to set the siever thread's CPU affinity[*]auto-detection of the GPU-type, along with new GPUType key in mfakto.ini, removed PreferKernel key[*] optimization for GCN (Graphics Core Next: HD77xx, HD78xx, HD79xx)[*]improved estimation of the number of compute units[*]bugfix: occasional abort on very high SievePrimes (> 450,000)[*]progress line output format: percent complete now %5.1f (was %6.2f), exponent now %-10u (was %d)[*] bugfix: if a kernel file cannot be found, tell it's name instead of KERNEL_FILE (thanks to Axelsson)[*] approx. 30,000 new test cases (factors) for pre-release testing (thanks to James Heinrich)[/LIST]The Linux version will follow tomorrow (probably).

[SIZE=1]@kracker: I just found my first new factor with the release candidate, so it is still capable of finding factors ...[/SIZE]

Cool! Thanks!
Quick question regarding SieveCPUMask:
Value of 3 (0011) would allow running on CPU 0 and 1, while 12 (1100) would designate CPU 2 and 3?
(Obviously not a programmer here...)

[QUOTE=Bdot;306387]I just released the Windows-version of mfakto 0.12 on
[URL]http://mersenneforum.org/mfakto/mfakto-0.12/[/URL]

These are the changes:
[LIST][*] IMPORTANT: bugfix for missing factors for certain exponent ranges. Thanks to dabaichi and Axelsson for bug report and help on [URL]http://mersenneforum.org/showthread.php?t=13977&page=16#383[/URL][*]handling of <worktodo>.add (worktodo file name as configured, with suffix replaced): will be appended to <worktodo> between 5 and ~10 minutes after the add file's creation, or when moving to the next assignment[*]new mfakto.ini key SieveCPUMask to set the siever thread's CPU affinity[*]auto-detection of the GPU-type, along with new GPUType key in mfakto.ini, removed PreferKernel key[*] optimization for GCN (Graphics Core Next: HD77xx, HD78xx, HD79xx)[*]improved estimation of the number of compute units[*]bugfix: occasional abort on very high SievePrimes (> 450,000)[*]progress line output format: percent complete now %5.1f (was %6.2f), exponent now %-10u (was %d)[*] bugfix: if a kernel file cannot be found, tell it's name instead of KERNEL_FILE (thanks to Axelsson)[*] approx. 30,000 new test cases (factors) for pre-release testing (thanks to James Heinrich)[/LIST]The Linux version will follow tomorrow (probably).

[SIZE=1]@kracker: I just found my first new factor with the release candidate, so it is still capable of finding factors ...[/SIZE][/QUOTE]

Thanks! is this the same as pre2... ?

[QUOTE=kracker;306394]Thanks! is this the same as pre2... ?[/QUOTE]
yes, except for
progress line output format: percent complete now %5.1f (was %6.2f), exponent now %-10u (was %d)

This is the late change that probably breaks something :smile:

[QUOTE=sdbardwick;306391]Cool! Thanks!
Quick question regarding SieveCPUMask:
Value of 3 (0011) would allow running on CPU 0 and 1, while 12 (1100) would designate CPU 2 and 3?
(Obviously not a programmer here...)[/QUOTE]
Yet you got it right. Maybe I need to hire someone expressing my techno-speak more user-friendly ...

good work !

could it be possible to integrate p-1 testing in the gpu-app ?

[QUOTE=NormanRKN;306402]could it be possible to integrate p-1 testing in the gpu-app ?[/QUOTE]

That might be possible, if we extend CUDALucas. mfakt* use completely different routines from LL testing and P-1 (which are both relatively similar).

[QUOTE=Dubslow;306408]That might be possible, if we extend CUDALucas. mfakt* use completely different routines from LL testing and P-1 (which are both relatively similar).[/QUOTE]
+1
P-1 for gpu would rock...

[QUOTE=Dubslow;306408]That might be possible, if we extend CUDALucas. [/QUOTE]

Even there, stage 2 is not a trivial thing to extend because of memory issues.

[QUOTE=axn;306414]Even there, stage 2 is not a trivial thing to extend because of memory issues.[/QUOTE]

[OT]True, but it should theoretically be possible to write S1 save files in Prime95 format to do a proper stage 2.[/OT]