Welcome to MilkyWay@home

Posts by Cameron

1) Message boards : News : Migrating MilkyWay@home to a New Server (Message 76621)
Posted 17 Nov 2023 by Cameron

It appears Kevin needs to let Willy @ BAM! know what the correct URL is because it's not pointing to it.

I posted to the thread in the number crunching but apparently that info hasn't been relayed over...

BAM (BOINCStats) has been getting Milkyway updates again since 14 - Nov.

Kevin posted https://milkyway-new.cs.rpi.edu/milkyway/forum_thread.php?id=5051&postid=76610 saying as much in the Number Crunching Server Migration Thread.
2) Message boards : News : Migrating MilkyWay@home to a New Server (Message 76541)
Posted 4 Nov 2023 by Cameron
Did you put http://milkyway-new.cs.rpi.edu/milkyway/

into the Project URL for Milkyway in the Add Project Wizard.
And give your correct login credentials.
3) Message boards : News : Server Maintenance 6/28/2023 12 PM EDT (4 PM UTC) (Message 76071)
Posted 28 Jun 2023 by Cameron
looks like mine (330) got marked as invalid on the first pass through.
4) Message boards : News : Server Maintenance 6/28/2023 12 PM EDT (4 PM UTC) (Message 76011)
Posted 28 Jun 2023 by Cameron
19-Jun-2023 17:08:24 [Milkyway@Home] Scheduler request completed: got 71 new tasks
20-Jun-2023 22:08:15 [Milkyway@Home] Scheduler request completed: got 89 new tasks
20-Jun-2023 22:15:56 [Milkyway@Home] Scheduler request completed: got 232 new tasks

These logged times are UTC + 10:00 so the server may have decided to give these out before you got around to shutting the processes down.
They have been returned and are probably the majority of the 405 I have pending. You wanted what was out to be returned that has been done.

regardless of if they are of scientific value to you or not Just going well it's easiest if it's consider null and void because we don't need it for the project. It was sent out to a volunteer and it was returned.
5) Message boards : News : Server Trouble (Message 72134)
Posted 21 Mar 2022 by Cameron
You only not gain credit for any returned results that either error or are inconclusive from my experience.
If they're returned they can probably be counted.

I've got 600 results waiting a quorum partner, 700 valid 100 inconclusive.and 11 errored.

so those 600 could go either way but I could have another 500 results to add to the tally
6) Message boards : News : Server Trouble (Message 71956)
Posted 15 Mar 2022 by Cameron
Just got a Single MW Seperation task when I reurned all my completed work.
I'll try again later when the backlog has had a chance to clear and the gererator some time to create WUs
7) Message boards : News : Server Trouble (Message 71797)
Posted 23 Feb 2022 by Cameron
Thanks for the hard work Tom.
One of the benefits of the 14 day deadlines is the results can have a few days till they're returned if something unexpected happens.
8) Message boards : News : New Separation Runs (Message 71739)
Posted 11 Feb 2022 by Cameron
I've cancelled all of the bad workunits from the job pool. Hopefully you should see them disappear from your machines shortly.

Just had the last few on my machine cancel, so that worked.
9) Message boards : News : Introducing Myself (Message 71653)
Posted 29 Jan 2022 by Cameron
10) Message boards : News : New Separation Runs 6/9/2021 (Message 70913)
Posted 25 Jun 2021 by Cameron
Had one Error on me

Workunit 119867095
name de_modfit_84_bundle4_4s_south4s_gapfix_bgset2_1621277702_21732796

Task in Question 229042440
11) Message boards : Number crunching : Nbody 1.80 errors (Message 70832)
Posted 24 May 2021 by Cameron
I know not too worry about them cause we're not wasting CPU time. But after noticing a few errors yesterday checking the thread and then examining the n-body work queued up on the machine. You do have workunits for 1.76 being run on 1.80.

I thought Boinc could support two versions of the same science app anyway so that you could have n-body 1.76 and n-body 1.80.
As you migrated the app towards more robust output, but still had earlier work that had been previously generated.

I like finishing resends and it seems a waste of that earlier modelled run if you're going to let them error out on the server,
Even if you're discarding a trivial fraction of the run.
12) Message boards : News : New Milkyway Badges Online (Message 70441)
Posted 26 Jan 2021 by Cameron
More badges... Thanks.
13) Message boards : News : Nbody 1.70 release (Message 67644)
Posted 2 Jul 2018 by Cameron
Just restarted accepting Nbody work

Application is version 1.70 although the workunits indicate *_v168_20k*.

This is alright?
14) Message boards : News : Nbody 1.68 release (Message 67538)
Posted 26 May 2018 by Cameron
I think the N-body Simulations are a multi-threaded task and will use many cores if available.

After you log in edit your Milkyway@home preferences

Run only the selected Applications: Milkyway@home: yes
Milkyway@home N-Body Simulation: no

Save your preference changes

send an update request from your BOINC client.
15) Message boards : News : New Separation Runs 7 May (Message 67454)
Posted 14 May 2018 by Cameron
Any particular reason these runs are bundled in 4s rather than 5s?

They appear to have 26 parameters instead of 20 in the previous tasks. And, judging by the elapsed time for these new tasks on my GPU it looks as if 4*26 parameters takes about the same time as 5*20 (!)

Obviously, this consistency of run time would be more significant for folks running CPU tasks - an increase of about 25% CPU time (likely with 5 per batch) might not go down quite so well there!...

I've always been a CPU only contributer to Milkyway.

but if it's a workunit flop size for the generator to handle that makes sense.
16) Message boards : News : New Separation Runs 7 May (Message 67450)
Posted 11 May 2018 by Cameron
Any particular reason these runs are bundled in 4s rather than 5s?
17) Message boards : News : Validation Inconclusive Errors (Message 66965)
Posted 15 Jan 2018 by Cameron
Anything going to happen to the inconclusive.... Cancelled Results?

some of the 35 I have

workunit 1551469684
workunit 1555077585
workunit 1555224430
workunit 1555253384
workunit 1555405588
18) Message boards : News : New Badges for Membership Time (Message 66871)
Posted 19 Dec 2017 by Cameron
saw the new badge passing by one of the stat sites.
They look good.
While I'm here time to get the 500K badge.
19) Message boards : News : Update on This Weeks Errors (Message 66755)
Posted 29 Oct 2017 by Cameron

Our project has been running for upwards of 10 years now and we have been crunching literally billions of workunits over those years. As a result of all of your hard work and dedication, we have actually calculated enough results that we have run out of room to store the IDs of all of these results in a normal unsigned integer value (the default data type used for storing IDs in BOINC databases). As a result, on Tuesday night, I updated our database to be able to store IDs in a much larger data type to prevent this issue from happening again during the remaining life of the project. As a result, I also had to quickly patch the BOINC code we run on the server to allow it to use this newly available data type in the database.

Just wondering If you know how much longer the project plans to run?
20) Message boards : Number crunching : cpu is desapear ? (Message 66126)
Posted 20 Jan 2017 by Cameron
Computing Preferences are common across all your BOINC Projects so changing it elsewhere may have affected how many CPUs MilkyWay will use.

What are your Computing Preferences set at for

On multiprocessors, use at most: n processors


On multiprocessors, use at most: % of the Processors

I'd suggest either explicitly stating the number of proccessors (eg 4 and 100%) or setting the numbers to 0 which will let the projects use all processors.

Next 20

©2024 Astroinformatics Group