When will WU's be ready?

Will the WUs be part of ClimatePrediction, or will it be an entirely separate project?

---

Discussion thread for this new project.
The first 2 posts have been moved here from the News section.

Even the moderators don't know about this yet.
The early news post was probably to test the new "changed and improved" News section.

When there IS some info, it'll get posted.

There's a link on the project's front page about this new project, although not much more than has already been extracted and posted in the News thread.

Just to give some more details on AFLAME. This is a belated announcement of the project, which actually started in April this year. This will be run under CPDN with the weather@home2 application using the South America region. Some of the initial WU have already been sent out (batches 813, 814, 815 and 822) with more planned when we have the appropriate land use forcing files available.

That explains it.
I missed those batches, as I was running test site stuff at the time.

This will be run under CPDN with the weather@home2 application

This means not for Linux users, right?

---

Right. :(

But there are other fish being fried. :)

This seems a really cool project. Its a shame I cant be involved as there are no work units for Linux. All my BOINC clients are Linux or Android which has scuppered most of my participation with CPDN. Heres hoping that will change soon!

Androids are never going to be used on this project, and for Linux it's best to have about 2-3 Gigs of ram per core for the Met Office models.

For the new OpenIFS models, you'll need between 3 and 6 Gigs of ram per core.
And there's been no sign of them since we ran the big event a few months ago during the the introductory conference.

The place to watch for new work is the New work thread in Number crunching, (which can be a bit late by the time you hear about them), and the Project status thread.

how can we download work units for AFLAME

---

There hasn't been any BOINC work for months.
The researchers are only running their usual mainframe programs at present.

When there is BOINC work, computers that ask for work are sent whatever is available for that OS, with no choice as to what research work it's for.

This seems a really cool project. Its a shame I cant be involved as there are no work units for Linux. All my BOINC clients are Linux or Android which has scuppered most of my participation with CPDN. Heres hoping that will change soon!

Windows tasks run perfectly well using WINE. My only issue is that the manager always crashes in advanced view if I install the 64 bit version. 32bit one works fine.

Edit: What I would really like to see though is all Linux tasks moving to openIFS and an end to tasks being trashed by users who don't read the forums and don't install the required 32bit libs.

It's a pity that CPDN cant check for the libraries before downloading the task files or when LINUX boxes add CPDN as a project.

It's a pity that CPDN cant check for the libraries before downloading the task files or when LINUX boxes add CPDN as a project.

I agree. I asked about this over on the BOINC forums and no one there came up with ideas about how to do it. I also asked about including the libraries in the downloaded applications but it seems there would be problems with different Linux flavours and version numbers causing compatibility problems.

What I would really like to see though is all Linux tasks moving to openIFS and an end to tasks being trashed by users who don't read the forums and don't install the required 32bit libs.

I wonder if openIFS is merely dead, or dead as a door knob?

What I would really like to see though is all Linux tasks moving to openIFS and an end to tasks being trashed by users who don't read the forums and don't install the required 32bit libs.

I wonder if openIFS is merely dead, or dead as a door knob?

More likely the scientists at the universities are used to the current applications or openIFS is suited to a particular type of climate problem and is waiting for a PhD student who needs it.

Edit: I remember how long the HADAM4 tasks took between first testing and appearing on the main site.

Looking at what CPDN reports on my Linux box I get "Linux Ubuntu, Ubuntu 18.04.4 LTS [5.3.0-62-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1.2)]" for the operating system. Presumably this is "collected" when the computer registers with CPDN when the project is initially joined. Could this be used to notify participants that their computer does not have the required libraries and therefore will not get any tasks downloaded until this is corrected? I suppose the question is "how to do it".

Linux Ubuntu
Ubuntu 20.04 LTS [5.4.0-39-generic|libc 2.31 (Ubuntu GLIBC 2.31-0ubuntu9)] Is what is reported for the computer I am using at the moment. Unfortunately that information collected by BOINC doesn't include any information about the 32bit libraries.

I assume it would be possible to write a batch file to identify and stop tasks going to computers failing with the missing libs message. This would then require new participants who having seen the message install the missing libraries to have their computers reinstated as there is no mechanism to tell when they have been installed. Potentially off putting for new participants. I will take a look on the BOINC forums as CPDN is not the only project that has this issue and see if there are any more clues as to solutions there. This has over the years been discussed ad nauseam here and with the project people without any solutions that everyone likes. These tasks now get up to five tries rather than three which has greatly reduced the number of real, "hard fails." (Where moderators and project people can look to get information about batch statistics still shows them as hard fails after three attempts meaning hard fails + successful tasks>100%.