This is a volunteer computing project which allows anyone on the internet to contribute resources to research projects related to Minecraft.
[email protected] enables the study of the fundemental laws of Minecraft to answer unanswered questions regarding the features and true limits of the game.
Already joined? Log in
Kaktwoos version 2.13 released + reminders for Nvidia Linux OpenCL packages
We've released the latest version of Kaktwoos-cl, which is now 2.13!
In this update, we've added further checks for GPU model detection and printout for what GPU and its 'name' a given Kaktwoos-cl task is on. Please note that we highly suggest you run sudo apt-get install nvidia-opencl-dev if you are on Ubuntu or Debian (or a corresponding package + command on your distro) in order to install the missing OpenCL headers and allow Kaktwoos-cl to run. We would appreciate that all BOINC users thinking or currently running Nvidia GPUs on Linux to verify that BOINC tasks are not reporting computation errors accidentally, and leaving them running 'carelessly'. We have not truly resolved the very rare 'stuck at 100% / Infinite Task' post-crash issue, and we recommend for those tasks to be aborted manually if you encounter one at >99% for more than 10 minutes on a new GPU.
Nvidia GPUs will use one of two kernels depending on their age and model. For example, any RTX or 16xx (Turing) GPU shall continue to use optimizations introduced in Kaktwoos v2.10. Older or weaker GPU models shall use the previous kernel, which means we should see a 5% boost to any GPUs reported to have a regression, as some of you may reported on our BOINC threads.
AMD RDNA1/2 GPUs are now detected and matched to use another set of optimizations, increasing their speed to their original (pre 2.10) or further increasing it. Due to architectural differences, changes made that improved GCN (ie RX 480, Vega 56) performance by 25-40% reduced RDNA 1/2 performance by up to 2X, which is now mitigated.
All task outputs will include the seed range searched as well (s: and e: parameters) for general interest and debugging potential. Otherwise, there is not much left I (Hy) feel there is to code for Kaktwoos-cl, and CPU projects are now more of a focus for [email protected] than before, as you may have seen with our OneChunk pre-announcement.
6 Jun 2021, 18:39:47 UTC · Discuss
OneChunk CPU Pre-Announcement (X86_64 & ARM64)
Over on the [email protected] discord, Boysanic ("Boincboi"), Matt (Stronghold simulation coding), other developers and I have been discussing and planning a rollout of our first CPU application. This OneChunk project is "a BOINC project in the works. Our goal is to find all world seeds w/ at least an 11 eye portal in MC Java 1.7.10". So, if this all works out, "you'll finally be able to say you've found an 11 eye portal by yourself!"
Essentially, we are combining parts of the "SSG" (Seed-Speedrun) and 11-eye portal seed-filtering programs together to go through a large dataset. This input file is 9GB in size, but we plan to split it up into many small manageable tasks to be distributed through BOINC, which is where you come in! Going through a 320kb sample input takes a 4.8GHz Ryzen 5800 (the fastest single-core CPU) around 2 minutes, simulating and checking over 5,220 worldseeds a second. A 2GHz Raspberry Pi 4, with 64bit Raspbian manages to compute 1,370 worldseeds a second, making it around 3.8x slower but much more efficient. (45W vs 5W)
Thanks to work by other developers, I have tested and confirmed that both x86_64 ("64bit Windows and Linux") and ARM64 (64bit Linux ARMv8) configurations will work. The OneChunk 'Filter9000' BOINC application is single-threaded, but will likely have multiple tasks running concurrently on your computer to best utilize its resources and scale to your unique hardware configurations. For 'PC' requirements, we suggest Ubuntu 18.04/20.04 64bit or Windows 7 / 10 64bit, running on an CPU such as an AMD FX or Intel 1st Gen Core i5/i7 CPU or newer.
If anyone has a Raspberry Pi 3(B/B+) or 4, we would like to invite you to install the latest 64bit Raspbian on a spare SDcard in preparation. We also expect Nvidia Jetson Nano/TX1/Xavier devices with Ubuntu 18.04 64bit or newer to successfully run our Arm64 tasks, once we configure our BOINC server to provide and schedule tasks for this platform.
Please follow instructions on the Raspberry Pi website, but we suggest that more experienced Pi users join us for this experiment! OS image below:
Also, check out our Forums for upcoming updates, and to see the first 25-Tall Superflat cactus!
3 May 2021, 15:46:34 UTC · Discuss
23 tall blocks cactus found by PDW and edjotron
We've discovered the first naturally generated 23-Tall Cactus! Thanks to PDW and Edjotron, we can now confirm that the tallest is 23 blocks. To see this cacti in its natural habitat, right by a Mesa, please input the seed
184693195438010998on 1.14 and use
/tp 16274576 64 10230656to teleport to it, right next to the badlands!
The Grand BOINCale for Kaktwoos?
We apologize yet again for the lack of work over the past month and a half, since all of you had last BOINC'd to solve Minecraft’s tallest cactus mystery. Now, after improving Kaktwoos’ ease of use for our developers we are ready for one last, hopefully long round of cactus stacking and chunk smashing with our fellow cacti enthusiasts. Thanks to some changes behind the scenes, our developers no longer have to painfully modify many configuration files and verify multiple server adjustments (as mentioned in our previous post). At most now they will only have to change two numbers and send work out, as all of the preliminary seeds have been pre-loaded for BOINC to work off of! So, how much work do we expect to generate over the next few days?
Well for starters, an average run of ‘Kaktwoos’ per block layer (y-level) creates 120,000 tasks at a minimum, and each task takes a midrange gaming GPU at least an hour to complete. We have at least 10 layers planned to be checked for 23 and 24-block tall cacti, making this one of our most comprehensive searches yet. Even with 1000 users computing away 24/7, we can imagine this work, and reviewing all the data from it will take at least *60* days. This doesn’t even include that the seeds we are working on are only a fraction of the potential cacti to be stacked, though are the most likely to successfully merge into Tall Cacti at these unusual heights.
So, how high up in a desert do you think we can find tall cacti? Will ‘Superflat’ presets be the final destination for outrageously tall cacti searches? Join us now at [email protected] to find out, and bring back immense compute power to our BOINC network! We recommend anyone with a Windows 7/10 64bit and Ubuntu 18.04 or newer OS to join, and especially those with an AMD RX 460, GTX 750ti or newer/faster. Intel Graphics are supported as well, and multiple GPU systems are in high demand and very capable to assist us. If you’re in the Northern Hemisphere feeling cold and isolated this winter, why not BOINC with us and chat in our Discord server https://discord.gg/xArErFf , or pay a visit to our messaging board?
If you have already begun the penultimate search for ‘stacctus’ with us already, try to find your own tall cacti under ‘Your Tasks’ in the BOINC client’s ‘Advanced View’, then by clicking on the task number inside your browser. Inside those logs maybe there’s a chance you’ll find a 22 or taller ‘natural’ cactus of your own, that you can build by and share with us. We will be posting updates often to announce any interesting findings from your hard work, so stay tuned in the upcoming weeks for more.
27 Jan 2021, 21:18:34 UTC · Discuss
From sandy valleys, up to sand dune peaks. Kaktoos rises to the challenge!
After a somewhat long hiatus, Kaktoos is coming back for another round in the ring, and this time at higher and higher heights. Many of us who contribute to the project ([email protected]) got a little busy with school/work after the Pack project concluded, so I apologize on everyone’s behalf for the silence and uncertainty as of late.
As for where we left off, the y=62 search wasn’t as fruitful as we would have liked. No taller cacti had been found at this height than were found at the slightly higher height, y=63.
With the way things usually go, we would need to create an entirely new version of the program in order to run kaktoos for different heights. We started on y=63 for the original version of the program, and then changed this to y=62 for the second run of the program.
This time around, we’ve flipped the script, and different heights can now easily be run at the same time or in series, with 0 program changes. Effectively we’ll be able to get the final answers we’re looking for from the kaktoos project much easier and without as much “red tape” as there usually is with program changes due to security reasons.
What does this mean for you?
This means more kaktoos, more often, and with less breaks between runs for the foreseeable future.
There’s some limits to how many heights we can attempt since there comes a point where you simply will not find any cactus, however, we have a fair range to work with now with these new changes in play.
We’ll be launching a run of kaktoos very shortly. We’ve been testing this in beta with a height value of 64 for a short period of time to make sure that things are running as smoothly as we would like, but we’re happy to announce that we’re ready to go!
Some have offered far more support than we ever expected during this beta, which definitely surprised us! We’re grateful for everyone’s enthusiasm, even if it’s to our own disadvantage to have this run done so quickly.
For the curious, this new run will encapsulate heights of 65, 66, and 67.
That said, happy crunching! Kaktoos runs will begin soon outside of beta. Thank you all for the support and understanding over the last couple months as we work through things.
6 Dec 2020, 20:05:33 UTC · Discuss