6 beeeellllion credits
6 beeeellllion credits
Just gone and cracked another beeeellllion. Go me. that one was a lot slower.
Re: 6 beeeellllion credits
Nice work! That’s a whole lot of credits!
Re: 6 beeeellllion credits
yep determined to get to that magical 11 digit club. thats a lot of collatz workunits
Re: 6 beeeellllion credits
Well done Neil, very impressive
-
- Active UBT Contributor 15+ yrs
- Posts: 1627
- Joined: Mon Jul 24, 2006 1:00 am
- Location: Halifax, West Yorks.
Re: 6 beeeellllion credits
I recently passed 2 billion, but at my current RAC it'll take about 5 years to add the extra digit.
So a big well done to Neil for getting a bit nearer so quickly.
So a big well done to Neil for getting a bit nearer so quickly.
-
- UBT Forum Admin
- Posts: 9684
- Joined: Mon Mar 13, 2006 12:00 am
- Location: NW Midlands
- Contact:
Re: 6 beeeellllion credits
if you can answer my post in the maths based section about my collatz WUs? either 4 seconds with a computational error or 20 minutes. its messing my collatz RAC up no end and i have people like Mark and Damien to over takeUBT - Timbo wrote: ↑Thu Dec 05, 2019 12:03 pmExcellent post.....very well done.
So, do you fancy sponsoring a sweep-stake on when you will crack the 7 beeeellion mark ??
regards
Tim
Re: 6 beeeellllion credits
Does it count if I do it?bigsinky wrote: ↑Fri Dec 06, 2019 9:02 amif you can answer my post in the maths based section about my collatz WUs?UBT - Timbo wrote: ↑Thu Dec 05, 2019 12:03 pmSo, do you fancy sponsoring a sweep-stake on when you will crack the 7 beeeellion mark ??
Surely that'll just make the sweep-stake predictions harder
Yeah, THAT'S going to happen
Mark
-
- UBT Forum Admin
- Posts: 9684
- Joined: Mon Mar 13, 2006 12:00 am
- Location: NW Midlands
- Contact:
Re: 6 beeeellllion credits
I wish I could answer - but I don't have an answer.
I could guess and suggest the following:
1) It could just be a work unit error - so nothing you can do about it. At least the 4 second errors aren't wasting a lot of time - just a pain.
2) The 20 minute error could be a hardware issue - on my GTX970s Collatz takes about 20-25 mins to complete so, it could simply be a local memory/hard drive issue, as Collatz gets near the end and starts writing it's output file, before uploading to the project servers.
Or it could be a config issue. Maybe try exiting BM, renaming your Collatz "app_config.xml" (to say "old_file.txt") and then restart BM and see if that stops it. (Certain commands within app_config file might not precisely suit your hardware, so going back to the default settings might be worth trying).
regards
Tim