And I'm still puzzled because the last conversation I had with Andy was that only trickles (for OpenIFS) are awarded credit, not completion. But I see what you mean. Richard's offered to take a closer look. Next time there's a tech meeting I'm in I'll bring it up, it will be more effective that way than myself or the moderators sending emails.

STATS FOR ALL TASKS
 NUM ROUTINE                                     CALLS  MEAN(ms)   MAX(ms)   FRAC(%)  UNBAL(%)
   0 CNT0     - COMPLETE EXECUTION                   1 ********* *********    100.00      0.00
   1 CNT4     - FORWARD INTEGRATION                  1 ********* *********     99.98      0.00
   8 SCAN2M - GRID-POINT DYNAMICS                 3200   14521.4   14521.4     43.02      0.00
   9 SPCM     - SPECTRAL COMP.                    2952    1842.4    1842.4      5.03      0.00
  10 SCAN2M - PHYSICS                             2953    9882.9    9882.9     27.02      0.00
  11 IOPACK   - OUTPUT P.P. RESULTS                247    6811.2    6811.2      1.56      0.00
  12 SPNORM   - SPECTRAL NORM COMP.                126      82.3      82.3      0.01      0.00
  13 SCAN2M - RADIATION CALC.                      985   82359.3   82359.3     75.10      0.00
  14 SUINIF                                          1   14351.2   14351.2      0.01      0.00
  17 GRIDFPOS IN CNT4                              247     362.0     362.0      0.08      0.00
  18 SUSPECG                                         1    3399.0    3399.0      0.00      0.00
  19 SUSPEC                                          1    3468.4    3468.4      0.00      0.00
  24 SUGRIDU                                         1    7905.6    7905.6      0.01      0.00
  25 SPECRT                                          1    1461.0    1461.0      0.00      0.00
  26 SUGRIDF                                         1    1516.0    1516.0      0.00      0.00
  27 RESTART FILES - WRITING                       123   13675.8   13675.8      1.56      0.00
  28 RESTART FILES - READING                         1       0.0       0.0      0.00      0.00
  29 SU4FPOS IN CNT4                               247       1.4       1.4      0.00      0.00
  30 DYNFPOS IN CNT4                               247   17375.5   17375.5      3.97      0.00
  31 POSDDH IN STEPO                                13      36.4      36.4      0.00      0.00
  37 CPGLAG   - SL COMPUTATIONS                   2953  -53919.1       0.0      0.00    147.40
  38 WAM      - TOTAL COST OF WAVE MODEL          2952   23517.5   23517.5     64.27      0.00
  39 SU0YOMB                                         1    1564.1    1564.1      0.00      0.00
  51 SCAN2M   - SL COMM. PART 1                   2953      59.5      59.5      0.16      0.00
  54 SPCM     - M TO S/S TO M TRANSP.             2952     367.6     367.6      1.00      0.00
  55 SPCIMPF  - S TO M/M TO S TRANSP.             2952      82.1      82.1      0.22      0.00
  56 SPNORM   - SPECTRAL NORM COMM.                126       1.3       1.3      0.00      0.00
 102 LTINV_CTL   - INVERSE LEGENDRE TRANSFORM    10094    1333.5    1333.5     12.46      0.00
 103 LTDIR_CTL   - DIRECT LEGENDRE TRANSFORM      6152    1427.9    1427.9      8.13      0.00
 106 FTDIR_CTL   - DIRECT FOURIER TRANSFORM       6152     228.6     228.6      1.30      0.00
 107 FTINV_CTL   - INVERSE FOURIER TRANSFORM     10094     233.5     233.5      2.18      0.00
 140 SULEG       - COMP. OF LEGENDRE POL.            2     127.7     127.7      0.00      0.00
 152 LTINV_CTL   - M TO L TRANSPOSITION          10094      59.8      59.8      0.56      0.00
 153 LTDIR_CTL   - L TO M TRANSPOSITION           6152      64.6      64.6      0.37      0.00
 157 FTINV_CTL   - L TO G TRANSPOSITION          10094      78.6      78.6      0.73      0.00
 158 FTDIR_CTL   - G TO L TRANSPOSITION           6152      65.8      65.8      0.37      0.00
 400 GSTATS                                     589499       0.0       0.0      0.00      0.00
 401 GSTATS HOOK                                564603       0.0       0.0      0.00      0.00
TOTAL MEASURED IMBALANCE =       0.0 SECONDS,  0.0 PERCENT
TOTAL WALLCLOCK TIME   108019.4 CPU TIME  503376.7 VECTOR TIME   503376.7

https://www.climateprediction.net should be back up and will hopefully resolve any problems connecting a computer to it.

2: That is a hadcm3s.
Up until recently, when the problem was found and fixed, that type of model had a fault in the trickle_up code, whereby the 1st trickle was generated with the correct info, but all subsequent trickles were identical.
So the server code would get the 2nd (and all others) trickle, compare it with what it already had, then discard it as a duplicate.
So people only got credit for one trickle for this type of model.
And, as you've already received that, you won't be getting more credit.

21710685	11381390	15 Jun 2019, 6:10:47 UTC	21 Nov 2019, 8:00:36 UTC	Completed	779,944.57	779,508.50	3,111.26	UK Met Office HadCM3 short v8.34 windows_intelx86

1: The so called deadline is just a number to keep BOINC happy. It's NOT when the task is required. Which is: ASAP
.

"even though it's set to additional 0.01 days of work (which should equate to every 14 minutes and appears to be the smallest increment BOINC accepts in that field)."

I thought that "set to additional days work" (actually "Store additional Days work" in my BOINC manager version), enabled you to download and store additional work units for your computer to crunch on future days.

Surely it has nothing to do with how frequently the requests for work are made - which is controlled by CPDN, not the BOINC Manager, to no more frequently that one hour as Les pointed out.

For Windows work, there's a "window of opportunity" which lasts for around 30 to 90 minutes, because of the huge numbers of Windows machines waiting for work.
Then it's back to waiting for a few weeks.

And personally, I think that this board looks a lot cleaner without them.

Credits are awarded each time data is received from a task (unlike other projects, which require completed tasks). Your task apparently failed to report the first reporting point. Sorry about that - we all lose some minutes of processing that way...

Ok, then I'll leave.

BYE BYE

Andy was working on an alternative script that wouldn't use so many resources but I have heard nothing of that since the big crash a few months ago.

.
.
.

A bit like Brexit, whatever happens, many will not be happy! Personally I think the current system is acceptable. When other important work is completed, it may be that Andy has time to return to work on the new script but until/unless that happens I doubt if there will be any change.

Model crashed: ATM_DYN : INVALID THETA DETECTED

They now know that the starting values used in that model run lead to an instability.

<![CDATA[
<message>
The device does not recognize the command.
(0x16) - exit code 22 (0x16)</message>
<stderr_txt>

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
The device does not recognize the command.
(0x16) - exit code 22 (0x16)</message>
<stderr_txt>

Model crashed: ATM_DYN : INVALID THETA DETECTED. tmp/pipe_dummy 2048

Model crashed: ATM_DYN : INVALID THETA DETECTED. tmp/pipe_dummy 2048

Model crashed: ATM_DYN : INVALID THETA DETECTED. tmp/pipe_dummy 2048

Model crashed: ATM_DYN : INVALID THETA DETECTED. tmp/pipe_dummy 2048

Model crashed: ATM_DYN : INVALID THETA DETECTED. tmp/pipe_dummy 2048

Model crashed: ATM_DYN : INVALID THETA DETECTED. tmp/pipe_dummy 2048
Sorry, too many model crashes! :-(
02:12:54 (1396): called boinc_finish(22)

</stderr_txt>
]]>

As I said a few posts earlier, Andy thinks it is the pre-22011 credit that has gone, as you have been crunching since well before that it has hit you. If it isn't fixed soon, because of the weekend and public holidays, not much is likely to change till Tuesday.

These WU are responsible for 70 to 95% of the power usage on any machine that they are run upon. It's not MARGINAL at all.

True enough, but in winter time you wont need to use the heaters so much, since the PC's heat your rooms :) And the research is valuable. I think it was marginal many years ago? Back when Athlon64's were the thing?

I read somewhere that a search on google uses as much electricity as a 60 watt light bulb does for 17 seconds.

Now back to topic :)

As an aside and not to divert the thread too greatly, the word "marginal" is sometimes used in marmot's sense of "small", but also means "at the margin" as in the expression "marginal cost". In addressing the question of 24/7 running, the word was used in the second sense and not the first: in effect, marmot argues that the marginal cost of running a CPDN model is "large" relative to the cost of the running an idle PC - that's actually a good thing, as it means the PC is efficient. However, it only produces a disagreement if "marginal" is allowed to have only one meaning, which it doesn't.