After a while, let me announce our paper based on the Asteroids@home project. It was published last year in the Frontiers in Astronomy and Space Sciences: https://ui.adsabs.harvard.edu/link_gateway/2022FrASS...909771D/PUB_HTML. We used ATLAS photometry and its bootstrap samples to derive rotation periods (no shape) for about 5000 asteroids.

The A@H project is currently processing data from ATLAS and Gaia together - that's what you are computing now.

Thank you all for your contribution!

P.S. Please ignore the previous news about the paper published in Astronomy and Astrophysics - its results were not based on A@H because, at that time, the server was down due to COVID and hardware issues. Sorry for the confusion.

Hi everyone,

We are proud to announce our new OpenCL applications for AMD GPUs!
Development process took some time but we finally managed to build it.
There are still many rough edges to be polished but thanks to you guys and to your feedback we'll continue to improve the code.

Linux application requires 64 bit OS with GLIBC v2.31 or higher and will run on most AMD Radeon GPU cards and some AMD Integrated Graphics with support of OpenCL 1.1 or higher.

Windows application requres 64bit Windows 10 or 11 and will run on most AMD Radeon cards and some AMD Integrated Graphics with support of OpenCL 1.2 or higher.

Happy crunching and thank you for your support!

Asteroids@home team

Hi everyone,

A new, 64bit, version of the Period search application for the Raspberry Pi was released today supporting aarch64 (armv8) architecture!

It will be interesting to get some feedback from you about how it performs as there still could be some issues to be solved.

Happy crunching and don't forget to use active cooling on your boards as the app can be very aggressive to the cores on times.

Cheers!
Georgi

We are happy to present you another set of applications that will utilize those CPUs, which possess the FMA instruction set!

It was built to support both Linux and Windows OS with 64bit architecture.
What must be taken into account with these applications is that depending on the CPU architecture, generation, model, version, speed and number of utilized cores, in some cases the FMA applications may run slower than the corresponding AVX ones because of how those instructions are handled on different architectures, details that I'll not going further here as there is a lot of information on Internet. Also, there could be another case using even the same FMA application. For instance, there could be a situation where on the same particular system, having your preferences restrict the use of just a single core of, let's say, an Intel(R) Xeon(R) W Processor Xeon W-2195 of the Skylake-W Architecture, that single core will run much faster, close to processors' Turbo frequency of 4.3GHz, than if your configuration allows the client to utilize let's say 12 or more cores. In the second case those cores will run close to the processors' base frequency of 2.3GHz, depending on their actual number, which will result drastically in lowering of the application performance. Take a look at this article where under the "Per Core Turbo Data" chapter you will find explanation about how the Turbo ratio limits works.

Still, while the Boinc server is capable of finding the best performed application for every particular system, taking into account multiple factors, and after a while it will start sending the right one for every particular system. Which means that even if your CPU is equipped with the FMA engine it still might receive an AVX tasks and there is nothing to be concerned.

So happy crunching and thank you for your support!

Radim Vančo (FoxKyong)

We are happy to present you our latest CUDA application v102.16!

It was built on top of CUDA's v11.8 SDK and thus it will be able to utilize the vast majority of cards with Compute Capabilities (CC) between 5.0 till 8.9 adding support for the Ampere & Ada Lovelace micro architecture, and all the Tegra & Jetson modules.
Of course, it comes with its own requirements for the driver's versions, depending on your architecture, as those before it.
In order your client to be able to receive it your computer must have one of the following Nvidia driver versions installed:

• For Linux x86_64 and Linux AArch64 >= 450.80.02
  
• For Windows x86_64 >= 452.39
  

(https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html)

Here is the list of supported by the v102.16 application GPUs by their CC provided by Nvidia.

So happy crunching and thank you for your support!

Radim Vančo (FoxKyong)