Minecraft@Home studies questions related to Minecraft, such as the properties of worlds that can be generated from different random seeds.

---

It didn't import BOINC Wide Teams, so any team founders will have to make their own account again.
GPU only project. And as far as I can find, no checkpointing. So watch out.

---

And all tasks thus far end in error on my AMD GPU.

GPU-only for now, BOINC-wide teams is configured now, AMD was recently added so there are some teething issues

My AMD just finished its first task, in reasonable time as well (2,436.47 seconds, or 40m 32sec)

BOINC-wide teams is configured now

I noticed that, but didn't get the confirmation email about that. Normally this would send out an email to team founders saying "Team created on XXX", where XXX is your project name.

BOINC-wide teams is configured now

I noticed that, but didn't get the confirmation email about that. Normally this would send out an email to team founders saying "Team created on XXX", where XXX is your project name.

It turns out our SMTP service ratelimited us. We’re likely going to use a new provider.
I’m sure it’ll be acceptable if we find the messages which were unsent and artificially push them through.

It turns out our SMTP service ratelimited us.

That's what I suspected. You wouldn't be the first BOINC project marked as a spammer. Heck, I even get Apache emails in from things I do on these boards (moderation) that end up in my spam box because enough people have marked it as spam that Gmail thinks it is. Resending unsent emails will be polite towards your user base. :)

Looks like I solved it. We moved to SendGrid for SMTP and I wrote some code to resend those BOINC-wide teams messages. Let me know if you got one.

Checkpointing is coming in the next few days :)

Checkpointing is useless if the application isn't doing anything useful, only running to end in validate errors as it does on my AMD RX 5700 XT. Don't you read your own forums, well news thread?

Acknowledging your volunteers problems on your project would be nice. I've stepped out for now seeing how I don't get any answers there anyway. Not spending more energy on it when there's no feedback.

So set up complete forums instead of just news and answer people over there. Unless you expect everyone to report to you via Twitter and Discord, which I won't do.

Checkpointing is useless if the application isn't doing anything useful, only running to end in validate errors as it does on my AMD RX 5700 XT. Don't you read your own forums, well news thread?

Acknowledging your volunteers problems on your project would be nice. I've stepped out for now seeing how I don't get any answers there anyway. Not spending more energy on it when there's no feedback.

So set up complete forums instead of just news and answer people over there. Unless you expect everyone to report to you via Twitter and Discord, which I won't do.

Hi Jord, I've had a read through the discussions on the news posts and have been implementing changes over the course of today. There's some working changes to the app to implement multi-gpu support and checkpointing. It looks like these validation issues you experienced are caused by a limited number of AMD GPUs, we'll likely just need to add some compatibility support for them.

The remaining forums are live now to facilitate on-platform discussion, I've encouraged others behind the project to get involved with those discussions.

It looks like these validation issues you experienced are caused by a limited number of AMD GPUs, we'll likely just need to add some compatibility support for them.

No, a validate error happens when the contents of the result differ wildly from those of others. Like I said, all others I have seen use the CPU quite heavily, mine doesn't. I was paired against an AMD RX 580 and even there my result didn't validate. So something is off with my type of video card. And it isn't drivers, as I updated from 20.3.1 to 20.5.1 between tasks, on either side I didn't validate.

(And sorry I sounded so gruff in my previous post, bad night...)

It looks like these validation issues you experienced are caused by a limited number of AMD GPUs, we'll likely just need to add some compatibility support for them.

No, a validate error happens when the contents of the result differ wildly from those of others. Like I said, all others I have seen use the CPU quite heavily, mine doesn't. I was paired against an AMD RX 580 and even there my result didn't validate. So something is off with my type of video card. And it isn't drivers, as I updated from 20.3.1 to 20.5.1 between tasks, on either side I didn't validate.

(And sorry I sounded so gruff in my previous post, bad night...)

We think it’s something to do with the way fprintf is handled differently.
We’re rolling potential fixes over the next couple of days.

Our validator is looking for a keyword in the stderr which is missing, presumably because of this issue.

The strangest behaviour is; we see hosts which have been with us for a long time with similar cards, but half of their results are processed as expected (we see the expected output), however the others fail in exactly the same mode you experienced with no other discernible changes.

(no probs, we all have one of those sometimes)

@David Anderson
I can't register. Despite solving the Captcha and getting a green check mark, I'm getting an error message that the Captcha was not solved correctly.

Tried it with the most recent versions of
- Chrome
- Chrome Incognito Tab
- Firefox
- MS Edge

That's not for David to solve but for the project admin. Meanwhile you can register via BOINC Manager Add Project.

---

reCaptcha is disabled for now.

Good news for those of you without a compliant GPU but who want to contribute anyway, the project will at one time in the future have a multi-threaded CPU application, that they're testing now.
Hy, MAH developer wrote:

Now, even if you don't have a compatible graphics card:

For those with a multi-core, relatively modern (Bulldozer/Phenom and Intel Nehalem) and newer CPU, a version of kaktwoos is being made to run on CPU only systems or those with incompatible GPUs. It will serve the same purpose as kaktwoos-cl that all of us are running atm, but it's actually a decently fast alternative.

On my Ryzen 1700 (8c/16t, 3.75GHz all cores) I get a speed of ~20mseed/s if nothing is running and I set it to use all of the processor. This is comparable to a RX 580 on our latest kaktwoos-cl version!

A Intel 8600K runs at 12-13mseed/s, and I expect a Ryzen 2600 to perform similarly

On a Ryzen 3950x or older 16 core Threadripper, we can expect 40 million seeds a second, at 150W; comparable to my desktop's overclocked Vega 56.

Sadly, a Raspberry Pi 4 at 1.95Ghz, 4 cores (32bit OS) runs this at... 1.2mseed/s

If you would like, progress of our CPU kaktwoos application can be tracked here:
https://github.com/DutChen18/kaktwoos-rs (Orig)
https://github.com/Hyenadae/kaktwoos-rs/commits/master (BOINC native mods + auto build for linux and soon Windows)