How long does the \'trickleup message\' take to upload? I am on broadband so the connection is not a problem, but if i know the details or characteristics of the program, i can work with it to free up more memory/cpu. In otherwords, if i can unplug my modem and turn off my internet security and antivirus program, the Bonic manager can work harder and faster. All i need to know is how long to give the program to upload the info it needs to carry on. I am running the \'Sulphur\' project/program for the climate change study. Bonic version 5.3.19

---

Hi, Chris, Welcome to the Boards.

Sulphur? You show two machines (likey two copies of the same machine [they can be merged]), one with three Models, two of which crashed. (The other machine shows no work assigned.) All three work units are Coupled Models, not Sulphur Cycle.

To upload Coupled Model \'annual\' Trickles on Broadband? Seconds, except for the ten-year uploads. They\'re more like minutes because they\'re nearly 5 Meg in size.

You can set boinc Manager to \"Network activity suspended\" and allow Trickles to accumulate for a week or so if you like. Then, allow the connection long enough to send it all home. (Note that the big uploads go to different servers than the routine Trickles.) Being out of contact for a week is not a problem for the Project.

By the way, important though it is, boinc Manager does very little work overall; it\'s the shell that allows Project client programs to operate.


Edit: Interesting that your post shows credit but the two machines in your account show nil.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Edit: Interesting that your post shows credit but the two machines in your account show nil.

Please also note that the trickle server is currently lagging behind; My last trickle at my resultpage shows 13th of June, so I haven\'t received trickles and credits for almost one week now.
Since I know it happened before at CPDN some times I don\'t really care.

---

Hi, thanks for the welcome, the reason for the two machines showing and neither being \'sulphur\' is because i fell for the old \'upgrade to the new version of Bonic\' line. When i upgraded and wanted to continue, i had the same problems many others did and so followed their advice and went back to my old version. In between finding this out, the three new models were downloaded and started, but i stopped them as i\'m already overcommitted with the sulphur program.

This is now back up and running and has just finished the first phase. It says i have 1800 hours left to do, which is huge. (six months if left 24/7).

Because of this i\'m trying to talk my father in law into taking the program and completing it if this is possible. Do you know if it is?

Also, what are the credits for? Can i spend them somewhere? !!

Hi, Chris, Welcome to the Boards.

Sulphur? You show two machines (likey two copies of the same machine [they can be merged]), one with three Models, two of which crashed. (The other machine shows no work assigned.) All three work units are Coupled Models, not Sulphur Cycle.

To upload Coupled Model \'annual\' Trickles on Broadband? Seconds, except for the ten-year uploads. They\'re more like minutes because they\'re nearly 5 Meg in size.

You can set boinc Manager to \"Network activity suspended\" and allow Trickles to accumulate for a week or so if you like. Then, allow the connection long enough to send it all home. (Note that the big uploads go to different servers than the routine Trickles.) Being out of contact for a week is not a problem for the Project.

By the way, important though it is, boinc Manager does very little work overall; it\'s the shell that allows Project client programs to operate.


Edit: Interesting that your post shows credit but the two machines in your account show nil.

---

Sulpher units were a short time project. Finishing them is up to you, but they are really not a necessity, anymore.

The new project takes longer than the sulpher models, and NEEDS 5.2.6 or higher version.

Someone else is better at explaining how to move models between machines, but the simple answer is, stop processing on first machine, backup the whole directory. Install same version on new machine, but do not start any projects. Close down software on new machine. Copy backed up data to new machine. Start software.

Credits = bragging rights, only.

---

OK, i really like the idea of helping out with thewe projects, but my computer is an old AMD Athalon 1200 with 512 meg of ram, because of this i am concerned about taking on a new project, especially if it\'s bigger than the sulpur one. what project would you recommend that is both do-able and worthy?

ps. i like that answer, bragging rights ! And well done on your stats.

Chris

Sulpher units were a short time project. Finishing them is up to you, but they are really not a necessity, anymore.

The new project takes longer than the sulpher models, and NEEDS 5.2.6 or higher version.

Someone else is better at explaining how to move models between machines, but the simple answer is, stop processing on first machine, backup the whole directory. Install same version on new machine, but do not start any projects. Close down software on new machine. Copy backed up data to new machine. Start software.

Credits = bragging rights, only.

---

OK, i really like the idea of helping out with thewe projects, but my computer is an old AMD Athalon 1200 with 512 meg of ram, because of this i am concerned about taking on a new project, especially if it\'s bigger than the sulpur one. what project would you recommend that is both do-able and worthy?

ps. i like that answer, bragging rights ! And well done on your stats.
pps. Did the \'version change\' explanation make sense about my credits and is it possilble to delete the stopped units and bring back the unit i\'m working on?
Chris

Sulpher units were a short time project. Finishing them is up to you, but they are really not a necessity, anymore.

The new project takes longer than the sulpher models, and NEEDS 5.2.6 or higher version.

Someone else is better at explaining how to move models between machines, but the simple answer is, stop processing on first machine, backup the whole directory. Install same version on new machine, but do not start any projects. Close down software on new machine. Copy backed up data to new machine. Start software.

Credits = bragging rights, only.

---

Chris

There is a list of some of the dozens of projects here.
Each should have a FAQ or About file.

My \'non-climate\' favourite is Rosetta, but half the fun is in exploring all the projects and deciding which ones you like :-)

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

pps. Did the \'version change\' explanation make sense about my credits and is it possilble to delete the stopped units and bring back the unit i\'m working on?

Sorry chris, I missed this bit in your last message.

The version change will only mess things up for people who were running the special BBC version, which stores programs and data in a different location to all of the \'normal\' versions of BOINC.
So it depends on your \'before\' and \'after\' versions.

As for getting back the sulphur model, if you don\'t have a backup from before the version change, and it hasn\'t shown up again since you\'ve returned to your pervious version of BOINC, then it\'s gone.

And credits are credits. \'You can\'t kill them with an axe\', as they say.
What you had before, you\'ll still have now.
Unless you\'re talking about rac. Which stands for RECENT average credit, and flutuates hourly. Think of them like water in a leaking bucket; you have to keep putting more in, otherwise you\'ll soon end up with an empty bucket / zero rac.