BRP4 crunching
9 Sep 2023 10:33:51 UTC
Topic 230061
(moderation:
Hallo!
I don't get tasks of BRP4 for my PC. Probably it's not suitable.
How much credit would I get for each validated task? I would like to know this for my statistics.
Many thanks in forehand,
kind regards and happy crunching
Martin
Tachchen,BRP4G (Arecibo,
)
Tachchen,
BRP4G (Arecibo, GBT) GPU: 62 credits example
BRP4X64 (Arecibo, GBT, long) CPU: 500 credits example
Happy crunching, Scrooge.
[EDIT:] task list displays: 62 credits, task details: 63. Some rounding issue maybe;
Scrooge McDuck wrote:task
)
Yes, actually you get 62.5 credits/WU. And since BRP4G are simply 8 bundled BRP4 WUs you get for them 8x62.5=500 credits.
@astro-marwil: you should be able to get BRP4G WUs, there are CPU applications for 32 and 64-bit Windows available, BRP4 is (on Windows) only for Intel-GPUs.
.
Hallo Scrooge! Many thanks
)
Hallo Scrooge!
Many thanks for your usefully answer. It's of help.
Kind regards and happy crunching
Martin
... and thanks to Link for
)
... and thanks to Link for explaning the dependance of CPU and GPU credits. Which raises the question: Why were the previously deployed (short) BRP4 CPU tasks that took 30 to 40 minutes (a long time ago) bundled into so-called "long" tasks bundling EIGHT of the original tasks (also 8 raw data files) into the currently deployed BRP4X64 CPU tasks to achieve longer runtimes per task. As a result, the Einstein servers are contacted less frequently for BRP4 CPU tasks. In contrast, the BRP4 GPU tasks weren't bundled into "long" tasks and still have runtimes of only a few minutes. On the other hand these short BRP4 tasks are the only available task type for all sorts of embedded ARM systems and classic Apple PowerPC G4/G5 Macs. Some low-end ARMs need long runtimes to complete a single "short" BRP4 task. I think these "short" tasks haven't been touched until now to involve the ARM enthusiasts with einstein.
I have a BRP4 task running on
)
I have a BRP4 task running on my Intel i5, Arecibo, GBT, long.But since my CPU is running also one Lateah GPU task and up to 11 other tasks I am not sure about the time it will take. Lateah tasks are the only GPU tasks, one at a time.Some GridPrime task use 11 threads,by putting all other tasks in waiting state.
Tullio
Scrooge McDuck wrote:In
)
BRP4G was originaly created for GPUs (that's why "G"), but they were moved back to BRP4.
Just a guess, but it might be due to the high inconclusive/invalid rate of the Intel GPU app, with 8 bundled WUs they probably needed too many results to get two that match, just compare the valid/invalid/inconclusive ratios for BRP4 and BRP4G on the server status page.
I reported it several times here in the forums, but currently the devs don't have the time to adress this issue. In the mean time I moved my Android to BRP4G with app_info.xml, where it validates against other CPU apps without any issues, when running BRP4 I had ~20% invalid rate because of the Intel GPU app (and IIRC also aarch64 app).
.
FYI, you can run BRP4G and
)
FYI, you can run BRP4G and BRP4 with the same app.
the BRP4G version of the app had some validation issues, but you can absolutely run BRP4G tasks on the BRP4 app and get the bigger tasks without the validation problems. I used to do this, but you need to use an app_info to force the BRP4 app to be used in this way.
_________________________________________________________________________
Ian&Steve C. wrote:the BRP4G
)
There are no BRP4/BRP4G versions of the app, for example the einsteinbinary_BRP4_1.33_windows_x86_64__BRP4X64.exe and einsteinbinary_BRP4G_1.33_windows_x86_64__BRP4X64.exe on my computer are identical. Just the tasks are different. Actually just the command line passed to the app is different/longer for BRP4G, the input and output files are the same, BRP4G has simply 8 of each. The Intel GPU app has some validation issues against CPU apps, they are now in BRP4 and there you can see insane amounts of inconclusive and invalid results on the server status page while BRP4G has nearly none.
.
incorrect.there was a 2.34
)
incorrect.
there was a 2.34 version of the app for intel GPU. this version was intended for BRP4G and the app you got if you had BRP4G enabled.
einsteinbinary_BRP4G_2.34_x86_64-pc-linux-gnu__opencl-intel_gpu
einsteinbinary_BRP4_1.34_x86_64-pc-linux-gnu__opencl-intel_gpu
this version is no longer listed on the applications page because the project removed it. but I have it on my host from my prior testing. the project has since changed how they distribute these tasks so this app is not being sent out anymore since they made BRP4G essentially CPU-only.
back to back testing on my own part showed MUCH more invalids when running BRP4G on the 2.34 app vs the 1.34 app.
the point was that you CAN run BRP4G if you wish using an app_info.xml file to force your host to ask for BRP4G tasks and run it with your own app (using the project's 1.34 BRP4 app) and it will run fine and validate reasonably well.
_________________________________________________________________________