ok. please can you post here when the time comes? thanks

How long will the calculations take in general?

The ℚ(√-10) search is also known as sf7. This one is mostly being computed at Gerasim (no badges). Periodically, some cases are run here giving you the chance to earn some counts.

Any chance of having a few more of these please?

I suppose that NF is FP64-intense which is not friendly to NVIDIA cards. Am I right?

Yes. I see about 8x speedup on 4060 Laptop than the CPU when running 3 tasks in parallel, but with 60W power consumption. When on CPU, it only consumes 25W with 16 tasks in parallel. That's awkward because heterogeneous computing normally increases power efficiency by nearly a magnitude.

Besides, I don't see any energy efficiency increase when switching to GPU as expected. Is that normal?

Also I did a little Paint.net work using layers to make the Galois Field badges much easier to distinguish apart at as low as 10% scale of the original size.

If you wish to use these, and I hope you do - feel free!

As title. How can i earn septic count and ℚ(√-10) count?

I have had 3 tasks fail after between 12 and 14 hours with the following error:
Exit status 198 (0x000000C6) EXIT_MEM_LIMIT_EXCEEDED

The tasks are https://numberfields.asu.edu/NumberFields/result.php?resultid=204294692, https://numberfields.asu.edu/NumberFields/result.php?resultid=204294798 and https://numberfields.asu.edu/NumberFields/result.php?resultid=204294071

Part of Stderr Output gives:

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<message>
working set size > client RAM limit: 16385.39MB > 16309.76MB</message>
<stderr_txt>
GPU Summary String = [INTEL|Intel(R)HDGraphics4600|1|1629MB||102].
Loading GPU lookup table from file.
GPU was not found in the lookup table. Using default values:
numBlocks = 1024.
threadsPerBlock = 32.
polyBufferSize = 32768.


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x00007ffe3287b892

Engaging BOINC Windows Runtime Debugger...

From these messages I understand that the tasks are running out of GPU memory.
Is there any way to reduce the amount of memory being used?

Thanks, Ruud

Pardon me for the impertinence, but I may have a better solution for the GPU problems that this project is hampered by:

*Expand the number of GPUs in the file your project supplies! (gpuLookupTable_v402.txt)*

      GPU Name      |   numBlocks   |  threadsPerBlock
==========================================================
     GTX 1050       |      9600     |       32
     GTX 1050 Ti    |      9600     |       32
     GTX 1660       |      8192     |       32
      RX 570        |      2048     |       64
     GTX 1070       |      9600     |       32

is a bit meagre, don't you think?
There's whole generations of GPUs (and IGPs) that do not get mentioned, and the default values don't work for all those. Editing the file does not work, even when you have a line in the cc_config.xml preventing the check for changed files -at least not in my BOINC client version. It looks like the file gets overwritten at times too, because I have made the change several times -to no avail.

I tried the solution

If it is truly a resource problem, you could try adding the following line to the gpuLookupTable file in your projects directory:

UHD Graphics 605     |     256     |      8

but it had no effect whatsoever -it still can't find the GPU in a certain table, apparently not the one in my drictory. I made my hosts visible now, so you can see more yourself.

I noticed on the batch status page the sf6-DS-12x9 has been marked completed. However, I am still getting a few of these tasks from time to time. Do you still need these tasks? If not, I would rather abort them and work on tasks that are needed.

Thinking about this, there are only two options: Anonymous platform or removing signature and its requirement from gpuLookupTable.txt. Both require changing server-side settings. (I don't like downgrading BOINC for too many versions.)

<verify_files_on_app_start/>
    Before starting or restarting an app, check contents of input files and app version files by either MD5 or digital signature check. Detects user tampering with file (but doesn't really increase security, since user could also change MD5s or signatures in client state file). 

Have either of you considered using the configuration option

<dont_check_file_sizes>0|1</dont_check_file_sizes>
Normally, the size of application and input files are compared with the project-supplied values after the files are downloaded, and just before starting an application. If this flag is set, this check is skipped. Use it if you need to modify files locally for some reason.

(details in the User manual)

Sorry for the dumb question, but are we thinking this is a BOINC problem with the newer version or an error with the hardware producer itself?