Formula Boinc 2019 - interested ?

PDW

PDW

Associate
Joined
21 Feb 2014
Posts
1,867
Just checking to see who is interested in contributing to the Formula Boinc 2019 season for OcUK ?

We came second at the end of 2017 in League 2, this thread contains the fun https://forums.overclockers.co.uk/threads/formula-boinc-2017.18763633/

After a rest during 2018 we are currently 15th in League 1 in the 2019 season
qKkd.jpg


FB site is here showing our project contributions http://formula-boinc.org/index.py?lang=en&team=399&year=2019

The FB Sprints are about to start, ties in with Formula 1 races, when extra points towards the team total can be attained if you finish within the top 10.

The first sprint runs from 14/03/2019 13:00 (UTC) to 17/03/2019 12:59 (UTC) but the project chosen is announced 24 hours before the start at 13/03/2019 13:00 (UTC). That is tomorrow lunch time !

To contribute you need to be signed up at that project and a member of team OcUK, all credit awarded between the race start and finish times counts.
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
Good :)

The first one has just been announced and it is NumberFields@home so you can download and bunker now.
Only results returned after the start time tomorrow will count though.
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
We are down to 10th now !

I thought @hanluc might have been around, I saw he'd run down what he had been doing, so either he's going to drop a big bunker in the next couple of days or he's gone away on holiday :p
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
Neither I'm afraid :) I'll fire some up tomorrow so we don't win the wooden spoon:D


Good stuff, the only way is up :)

We are currently in 14th but now starting to climb towards those above us and a points position :D

Are you ok Texas ? You haven't posted any points today and I have heard there have been a few weather problems your side of the pond.
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
This morning we are in 12th place and moving up :D

Still no news from @Texas_Connectio :confused:

@Matzo have you changed your preferences as you didn't appear in the Free-DC stats update today, see post 4 in the thread.

Less than 4 hours to go...
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
No worries, you'll appear tomorrow on Free-DC.
If you hadn't appeared on the team list at NF I would have chased you :)

Less than a couple of hours to go and we have moved up to 10th and a point on the board :D
Not too far behind 9th place either....
iIld.jpg
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
Final results are in and we stayed in 10th, just under 19k behind 9th spot...

JIld.jpg


Not bad for a rusty start after a year out.

Next sprint is less than 2 weeks away and a later start, project will be announced on Wednesday 27th March 9pm.
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
Next Sprint is from 28/03/2019 21:00 (UTC) to 31/03/2019 20:59 (UTC)
Project will be known on Wednesday 27/03/2019 21:00 (UTC)

In case it is either Acoustics or RakeSearch you should have installed the optimised apps (courtesy of [B@P]Daniel), download links and forum threads...

https://github.com/sirzooro/Acoustics-at-home/releases
http://www.acousticsathome.ru/boinc/forum_thread.php?id=66#313

https://github.com/sirzooro/RakeSearch/releases
https://rake.boincfast.ru/rakesearch/forum_thread.php?id=39

A newer version (v1.1) of RakeSearch was released February this year.

You need to find and download the appropriate release for your CPU/OS.
You need to restart Boinc after you've copied the necessary files into the project directory in order for them to be recognised by Boinc.

Other news, there is a GPU app for NumberFields now, only for linux at the moment, more news here...

https://numberfields.asu.edu/NumberFields/forum_thread.php?id=362
 

PDW

PDW

Associate
OP
Joined
21 Feb 2014
Posts
1,867
NumberFields is now fixed credit by the looks of it, had been getting abused on its original setting.
 
Associate
Joined
16 Apr 2014
Posts
85
The "abuse" was the project erroneously crediting based on wall clock run time instead of CPU run time... It happened on CPU as well. Just people weren't paying very close attention until now.
 
Back
Top Bottom