We10 in TF and PM1

eumayer · 2014-12-10, 13:24

Just got following result from TF

M117xxxxxx no factor from 2^66 to 2^67, We10: 697F0F20

What meaning has this hexadecimal value called We10 and how is it computed?

Is it comparable with such like a residue (Res64) in a LL-test?

Prime95 · 2014-12-10, 17:11

We10: The e indicates what version of prime95 you are running -- I think e is version 28, but I'd have to check the source code to be sure. The 10 indicates what OS you are running. The logic behind reporting this is in case a bug is later found that forces us to rerun some TF, we can rerun only the affected results.

The hexadecimal number is a simple checksum that lets the server validate the result as coming from a legitimate copy of prime95 and it was transmitted without error.

You should also know that using prime95 for TF is not the best use of your computer. GPUs can TF nearly 100x more efficiently than prime95 can.

2014-12-10, 13:24	#1
eumayer Dec 2014 Sydney, Australia 2 Posts	We10 in TF and PM1 Just got following result from TF M117xxxxxx no factor from 2^66 to 2^67, We10: 697F0F20 What meaning has this hexadecimal value called We10 and how is it computed? Is it comparable with such like a residue (Res64) in a LL-test?

2014-12-10, 17:11	#2
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 19·397 Posts	We10: The e indicates what version of prime95 you are running -- I think e is version 28, but I'd have to check the source code to be sure. The 10 indicates what OS you are running. The logic behind reporting this is in case a bug is later found that forces us to rerun some TF, we can rerun only the affected results. The hexadecimal number is a simple checksum that lets the server validate the result as coming from a legitimate copy of prime95 and it was transmitted without error. You should also know that using prime95 for TF is not the best use of your computer. GPUs can TF nearly 100x more efficiently than prime95 can.