I am sorry for server outages which was happening recently. There were several factors which often caused lack of free space and some services crashed and I had to do an emergency shutdown on Saturday in order to fix everything so I couldn't inform you about it except for Twitter. There is still a hardware problem with one of servers which I have to fix but the server is not being used now so project should be stable now. Radim Vančo (FoxKyong)

By asteroids@home at 2020-07-08

Hey all, The last set of N-body runs we set up started converging to compact progenitors due to an overly restrictive data histogram. We have fixed the data histogram and placed new runs up on the server: -de_nbody_07_07_2020_v176_40k__data__1 -de_nbody_07_07_2020_v176_40k__data__2 -de_nbody_07_07_2020_v176_40k__data__3 Please let us know if these runs cause any problems, and thank you all for your support. -Eric

By milkyway@home at 2020-07-07

We need to do some tests of a patch to fix a bug that's been plaguing us for some time. To this end, I am letting the job queues drain, so there will be an absence of CMS jobs -- perhaps as soon as tomorrow morning, depending on how we continue to recover from today's Oracle quota problem. So, be prepared to set No New Tasks as soon as you see any sign of lack of jobs -- or sooner if you prefer. I don't know how long the testing will take, there are many factors at work (if the BOINC server sees that there are no jobs available, it will stop sending tasks; that will mean it takes longer for each test batch to be recognised and start serving jobs).

By lhc@home_classic at 2020-07-01

Hello Everyone, I have put up the following separation runs: de_modfit_80_bundle4_4s_south4s_bgset_3 de_modfit_81_bundle4_4s_south4s_bgset_3 de_modfit_82_bundle4_4s_south4s_bgset_3 de_modfit_83_bundle4_4s_south4s_bgset_3 de_modfit_84_bundle4_4s_south4s_bgset_3 de_modfit_85_bundle4_4s_south4s_bgset_3 de_modfit_86_bundle4_4s_south4s_bgset_3 And I have taken down the following separation runs: de_modfit_80_bundle4_4s_south4s_bgset_2 de_modfit_81_bundle4_4s_south4s_bgset_2 de_modfit_82_bundle4_4s_south4s_bgset_2 de_modfit_83_bundle4_4s_south4s_bgset_2 de_modfit_86_bundle4_4s_south4s_bgset_2 de_modfit_14_bundle5_testing_4s3f_1 de_modfit_14_bundle5_testing_4s3f_2 de_modfit_14_bundle5_testing_4s3f_3 de_modfit_14_bundle5_testing_3s4f_1 de_modfit_14_bundle5_testing_3s4f_2 de_modfit_14_bundle5_testing_3s4f_3 The new runs are copies of the previous bgset_2 runs, in order to verify our results. Since the stripe 84 and 85 runs in the last set went a bit wonky after a couple weeks, I expect the same to happen here. I will keep a close watch on these forums, and when people begin to report errors from the runs on those stripes, I will promptly take them down. The errors that people are reporting on the bgset_2 runs should stop in the next couple days as the old runs all finish trickling in. All of the testing runs have come down (there may be more in the future). Thank you all for your continued support with this project. Stay safe (and sane) in these strange times. Best, Tom

By milkyway@home at 2020-06-29

The database underlying LHC@home will be down on Saturday 27th of June due to an upgrade of a DB storage rack. Hence LHC@home BOINC services will be unavailable for a good part of the day. (Est 5:30-12:30 UTC) So your BOINC client connections to our servers are likely to fail on Saturday. Thanks and happy crunching!

By lhc@home_classic at 2020-06-25

On 26th of May, CharityEngine1, a member of the team Gridcoin has found a Megaprime 166*443^432000+1 for base S443. The prime has 1.143.249 digits and entered the TOP5000 in Chris Caldwell's The Largest Known Primes Database.

By srbase at 2020-06-17

I have had a couple people mention that the fixed credits should be higher. I tried to set the credits to be in line with the cobblestone definition, but it's possible I missed the mark. I will wait for feedback before making any changes. Please share your credit opinions.

By numberfields@home at 2020-06-17

Hey everyone, We realized that the comparison histogram in the last set of runs contained incorrect data. As such we have replaced the last set of runs on 05/30/2020 with the following runs in their place: -de_nbody_06_08_2020_v176_40k__data__1 -de_nbody_06_08_2020_v176_40k__data__2 -de_nbody_06_08_2020_v176_40k__data__3 We apologize for any inconvenience, -Eric

By milkyway@home at 2020-06-08

This was discussed in another thread, and it just occurred to me I should post a news item with more explicit instructions. The issue is that the BOINC client comes bundled with SSL certificates and these expired earlier today. Here are the basic steps to fix the problem. (Note: this works on linux and I see no reason why it shouldn't work on Windows too.) 1. Download the new "ca-bundle.crt" file from here: [Link] https://1drv.ms/u/s!AsVDg7OAm7-whqEqBXKHuOie0UoBKA?e=VHwBAP 2. Replace the old ca-bundle.crt file with the new one (it should be in your BOINC root directory).

By numberfields@home at 2020-05-31

Hey everyone, We are really close to releasing a new version of NBody. Hopefully, after the next two sets of optimizations, we'll have all the bugs in the newer version fixed. So for the time being, here are the new runs: -de_nbody_05_30_2020_v176_40k__data__1 -de_nbody_05_30_2020_v176_40k__data__2 -de_nbody_05_30_2020_v176_40k__data__3 Thank you all for your continued support, -Eric

By milkyway@home at 2020-05-30

Due to a failure of a database storage system, a number of database services at CERN failed on Wednesday afternoon. The LHC@home servers were affected as well, as the BOINC database was unavailable and requests timed out. Sorry for the trouble and happy crunching!

By lhc@home_classic at 2020-05-27

I have replaced CreditNew (or CreditScrew as some like to call it) with a fixed credit system. The fixed value is based on the average runtime from many samples from a single machine in a well controlled environment (one of my own computers). Obviously, the fixed value will change with each batch, since each batch has a different average runtime. This should be a pretty fair system, especially after a host has processed enough WUs for the average to kick in. The main downside is the potential for cherry pickers - hopefully there won't be too many of them.

By numberfields@home at 2020-05-23