The beta period has ended! We are happy with the progress so far, thanks to all who contributed during this phase of the project.

We have now pushed over 1.2 million work units for processing as part of the cactus finding project.
This is following the success of locating world seeds for cactuses up to 21 blocks tall, 2 blocks higher than the existing record.

You may notice a new application, panorama; this is attempting to locate the world seed which was used for the panorama screenshot used in the Minecraft main menu.

There are plenty more applications and work units to come. Thank you all once again for taking part in this adventure.

---

epic

I write here 'cause there is no other forum.
Some errors on my notebook

<message>
exceeded elapsed time limit 1973.44 (86400.00G/43.78G)</message>
<stderr_txt>
11:29:50 (6856): wrapper (7.7.26016): starting
11:29:50 (6856): wrapper: running ../../projects/minecraftathome.com_minecrafthome/kaktwoos_1.08_opencl.exe ( --start 4400000000000 --end 4500000000000 --chunkseed 135556446462079 --neighbor1 153 --neighbor2 649 --neighbor3 137 --diagonalindex 2 --cactusheight 12)

There is a time-limit for calculation?
And if yes, maybe there is a good solution to publish the minimum gpu version for the project

Yup, all tasks end in error for my Windows (AMD OpenCL) tasks as well. Running on an RX 5700 XT.

<core_client_version>7.16.7</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 1430.18 (86400.00G/60.41G)</message>
<stderr_txt>
11:51:41 (6872): wrapper (7.7.26016): starting
11:51:41 (6872): wrapper: running ../../projects/minecraftathome.com_minecrafthome/kaktwoos_1.08_opencl_amd.exe ( --start 4600000000000 --end 4700000000000 --chunkseed 161058896647288 --neighbor1 697 --neighbor2 185 --neighbor3 169 --diagonalindex 1 --cactusheight 12)

</stderr_txt>
]]>

Also, no checkpointing?

My tasks run for 23m, but come in with an estimate of 59s. All tasks run to 100% at around the 12 minute mark, then continue on until they time out at just before 24 minutes.

I see you haven't set rsc_fpops_est and rsc_fpops_bound in JobSubmission, but are using the default values of 36000000000 and 86400000000000
My RX 5700 XT has a peak flops output of 4646000000000, which is already more than the estimated default flops amount you think the tasks take.

And why run in a wrapper? If it's an OpenCL application, it can run natively on the GPU, can't it? Even if it's built for Nvidia, OpenCL should be the same between them.

Yup, all tasks end in error for my Windows (AMD OpenCL) tasks as well. Running on an RX 5700 XT.

I have an Nvidia mobile gpu and an RX550.
Not a top-level gpus, but i'm crunching on Einstein, Milkyway, Folding, etc without problems

My tasks run for 23m, but come in with an estimate of 59s. All tasks run to 100% at around the 12 minute mark, then continue on until they time out at just before 24 minutes.

Same here. Estimated time 2 minutes, 34 minuts of crunching, then errors

And why run in a wrapper? If it's an OpenCL application, it can run natively on the GPU, can't it? Even if it's built for Nvidia, OpenCL should be the same between them.

Great question!!

Same time limit error exceeded error for me also. 2080 with Ryzen 3950x.... estimates low, seems to reach 100%, sits for a few minutes, then computation error.

Xader seems to have a working computer on this project - https://minecraftathome.com/minecrafthome/hosts_user.php?userid=69 .. wonder what is different on his setup than ours erroring out.

You're lucky, I can't even get the tasks to start!

25/06/2020 11:06:46 | minecrafthome | Started download of version.xml.bak
25/06/2020 11:06:47 | minecrafthome | Giving up on download of version.xml.bak: permanent HTTP error

Same here, asymptotic ETA then time limit error.

Hi,
download and runnig was no problem, but after ~ 1 hour the wu was at 0,4%, remaining time : over 9 days.
But the deadline is only 24 hours, anybody else with this problem ?

Gpu is 1660 Ti, Windows 10, normal runtimes on all other projects.

You're lucky, I can't even get the tasks to start!

25/06/2020 11:06:46 | minecrafthome | Started download of version.xml.bak
25/06/2020 11:06:47 | minecrafthome | Giving up on download of version.xml.bak: permanent HTTP error

Same here, with new version 1.10.

Hello all, there's a few teething issues, we've resolved several issues over the course of today.
We're all learning here, the quality isn't what we hoped from the start, but things will be running smoothly soon.

Hi,
download and runnig was no problem, but after ~ 1 hour the wu was at 0,4%, remaining time : over 9 days.
But the deadline is only 24 hours, anybody else with this problem ?

Gpu is 1660 Ti, Windows 10, normal runtimes on all other projects.

Same here, 6 to 10 days on a 24 hour deadline.

Hi,
download and runnig was no problem, but after ~ 1 hour the wu was at 0,4%, remaining time : over 9 days.
But the deadline is only 24 hours, anybody else with this problem ?

Gpu is 1660 Ti, Windows 10, normal runtimes on all other projects.

Same here, 6 to 10 days on a 24 hour deadline.

Though the BM estimate is 6 - 10 days, mine completed in 4000 - 4600 seconds. Seems to be running fine here, you just need to ignore the estimated times.

I was pleased to discover Minecraft@home today.
However, it isn't clear whether this project applies to the Java or Bedrock editions of Minecraft. Although the Java edition is usually the first one out with new features, Bedrock has a larger installed user base (I'm a Bedrock user myself), so projects related to Bedrock seeds would likely benefit more people. So which edition is Minecraft@home supporting?

I think we're open to anything. Most of the effort is currently on Java edition due to pack.png, but I'm sure Bedrock projects will surface too, it's mostly the same arithmetic.

Hi,
download and runnig was no problem, but after ~ 1 hour the wu was at 0,4%, remaining time : over 9 days.
But the deadline is only 24 hours, anybody else with this problem ?

Gpu is 1660 Ti, Windows 10, normal runtimes on all other projects.

Same here, 6 to 10 days on a 24 hour deadline.

Though the BM estimate is 6 - 10 days, mine completed in 4000 - 4600 seconds. Seems to be running fine here, you just need to ignore the estimated times.

Should look better now, let me know what you see

    <rsc_fpops_est>60000000000000.000000</rsc_fpops_est>
    <rsc_fpops_bound>2000000000000000.000000</rsc_fpops_bound>

Slightly better, let's see if I can finish a task. Or cactii.

Edit: so far so good

Application
Multichunk population seed cactus stacking 1.12 (opencl_amd)
Name
kaktwoos_1.0.7_0111_233820593817128
State
Running
Received
25/06/2020 22:57:12
Report deadline
26/06/2020 22:57:12
Resources
0.99 CPUs + 1 AMD/ATI GPU
Estimated computation size
60,000 GFLOPs
CPU time
00:00:08
CPU time since checkpoint
00:00:08
Elapsed time
00:30:55
Estimated time remaining
00:05:38
Fraction done
84.563%
Virtual memory size
135.85 MB
Working set size
75.07 MB
Directory
slots/0
Process ID
5004
Progress rate
2.736% per minute
Executable
wrapper_26016_windows_x86_64.exe

One thing I see though, the kaktwoos application runs at Low priority in Windows Task Manager, even in the wrapper. The wrapper runs at Normal priority. Seeing how we run on the GPU, you should try to set the priority to below_normal (case 2, Low priority at the Wrapper App).

You now have it set to lowest, case 1. This may give problems for GPUs as anything else will take cycles away. On some systems this may even be recognized as idle and the computer will go to sleep while the GPU is doing work, resulting in crashed apps.