Just got one of these and noticed I've completed two in recent months (16275890 and 16291996).

Maybe Linux just rules, eh?

So the silence means moderators want me to continue with the one have?

You seem to have missed seeing several messages regarding these tasks.

>
Message 48807 - Posted 15 Apr 2014 20:00:23 UTC


NO RESUBMISSION tasks are in the mix again. See the second paragraph of mo.v's post here:
http://climateapps2.oerc.ox.ac.uk/cpdnboinc/forum_thread.php?id=7739&nowrap=true#48049

If the HadCM3N task is named 7??? and the Work Unit is marked 'No Resubmission' it should be aborted.

Sorry about that.<

Ed

No, I saw them. I wondered if it might pique the interest of a scientist or two to know some are completing. On the other hand, if I'm just wasting electricity I'd like to hear a moderator or admin say so.

The work units marked as 'no resubmission' should not have produced more models to process, so any models that have appeared should be aborted. I suppose that the reappearance of 'no resubmission' tasks is because some anniversary has now arrived of the original release (the task on your machine is a reissued timeout, with the BOINC server blithely ignoring the 'no resubmission' marking).

I take the deliberate marking of the work units by the project staff as a statement that the work units are no longer of interest to the science group. However, I did get a 7-series reissue from a work unit not marked as 'no resubmission' and ran it: whether it will ever be analysed I don't know.

See this post from Ian Inglis:

Message 47969 - Posted 14 Jan 2014 12:23:34 UTC in News and Announcements.

Task aborted--and now it's gone here. Well, at least it's on Linux.

Probably too late for this batch, but perhaps in the future the distribution script could have a few lines added that grep for the '7xxx' and nix them (in Python this can be done with a subprocess call.) The filename check would be more robust than querying the database for 'no resubmission' (which apparently is not working).

Apology in advance if this strategy has already been considered.

... I think the strategy is to upgrade the entire BOINC server software to a more recent, less tailored version - which presumably won't suffer from the same problem.