Message boards :
Number crunching :
nm_test16 and nm_test17
Message board moderation
| Author | Message |
|---|---|
TravisSend message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
i've tried dynamically calculating the fpops estimates (nm_test14 wasnt correct i don't think), so let me know if these seem about right, and if these WUs work correctly.
|
|
Send message Joined: 18 Nov 07 Posts: 280 Credit: 2,442,757 RAC: 0 |
Slightly off-topic, but isn't the term 'flops'? (it stands for 'floating point operations', of course, so fpops sort of makes more sense) |
|
Send message Joined: 7 Jun 08 Posts: 464 Credit: 56,639,936 RAC: 0 |
FLOPS is a unit of power, FLoating point Operations Per Second. FPOPS is a unit of work, Floating Point OPerationS. <edit> Now that I got that first part straightened out! ;-) In the BOINC context, you need the FPOPS estimate (the amount of work in the task) in order to calculate the estimated runtime using the host Benchmarks. This also comes into play when the Core Client (CC) goes to make a work request from a project. HTH, Alinator |
©2026 Astroinformatics Group