If those machines were inactive for a while, they no longer show on the list of active hosts. If they were merged, one is removed as well.

---

Rosetta Moderator: Mod.Sense

They were there and they did show. It doesn't sound like anybody understands so let me illustrate:

Total Credit for 768175 before merge: 181,754.28
Total Credit for 965812 before merge: 6,008.17
Total Credit for 1003570 before merge: 0
Total Credit for 1026651 before merge: 0 <--- computer presumably being merged to

Total Credit for 768175 after merge: 0
Total Credit for 965812 after merge: 0
Total Credit for 1003570 after merge: 0
Total Credit for 1026651 after merge: 0 <--- notice no credit

So their credit was zeroed but it was never added to destination host. They were effectively just removed. This looks like a software bug. If it can't be fixed right now I understand, but the merge function should then be disabled until it can.

---

BBLounge - Broadband and Technology forum

The only strange thing was that there were 4 when I was only using 1 during that period so I assumed it was a side-effect from the restore.

Upgrading BOINC versions sometimes causes the system to think you are using a new computer. For example if you had run some tasks with BOINC 4.x and then upgraded to BOINC 5.x the system may count the same computer twice. 3 duplicates may have been caused by 4 installs.

People will now think I cheated having the credit but no computers that actually did it. :D Though I don't see how one could.

I wouldn't worry about your missing data at host level. Your BOINC Stats page clearly shows that you earned the credit steadily between July 2006 and January 2009, so there will be no suspicion of "faking" your credit. ^_~

Home page:
Total queued jobs: 0
In progress: 430,783
Successes last 24h: 233,825

Server status page:
Ready to send 5,820
In progress 704,522

I think we'll need some extra work shortly

---

We recently updated the web site with the latest BOINC code. Please post any issues with the web site in this thread. This update includes new features in the forum, spam filters, and a fix for merging hosts.

I have completed all tasks sent and the message on the upload is "communications deferred. I have not be able to download anymore tasks since then.

Any chance of getting the "results" links on the Home page and the Account page fixed - for the past few weeks all I have been getting is the message "Sorry, the data requested does not exist"

I had previously posted this issue in the thread "User results" but maybe that was not the right place to do so.

The results server should now be working, as indicated in this post.

Also, the list of articles and papers written by the Project Team has just been updated here.

---

Rosetta Moderator: Mod.Sense

The results server should now be working, as indicated in this post.

Also, the list of articles and papers written by the Project Team has just been updated here.

Thanks!!!

---

When I click on Results at https://boinc.bakerlab.org/rosetta/, I get this error message:

Request Error

Sorry, the data requested does not exist.


This happened within a few minutes of the time I clicked on Your Results under boincmgr.exe for the 64-bit Windows version of BOINC 6.10.58, and was able to actually see the list of results. I just tried that again - the list is still there.

This suggests that the results server is now working, but the Results link to it on the home page isn't.

The home page link you refer to provides a view of your results as compared to others for the same protein. It shows how your best score on the task compares to all of the other submitted results. The link from the BOINC Manager just displays the standard BOINC web pages listing your recent work in progress or completed for specific tasks.

---

Rosetta Moderator: Mod.Sense

I have 17 tasks which seem to have disappeared. They are listed in my website account Tasks List as having been sent on 24 May, with a deadline of 3 June. However they are not in the BOINC Manager tasks list. Obviously, I cannot now abort them. It would appear that all I can now do is simply leave them and allow them to expire.

It would appear that all I can now do is simply leave them and allow them to expire.

Yep. A scheduler reply must have been interrupted and so the server thinks the tasks were issued, but the BOINC Manager never received them. The BOINC world refers to these are "orphaned" tasks.

---

Rosetta Moderator: Mod.Sense

The home page link you refer to provides a view of your results as compared to others for the same protein. It shows how your best score on the task compares to all of the other submitted results. The link from the BOINC Manager just displays the standard BOINC web pages listing your recent work in progress or completed for specific tasks.

The home page Results link still gives only an error message. Does that imply that I've only tried it on workunits for proteins that no one else has returned outputs for yet? Or does it imply that the comparison process hasn't been working lately?

Is there any particular reason why the two methods of observing the server status give such extremely different numbers of workunits ready to send?

The Server Status near the top right corner of the Rosetta@Home home page currently reports Total queued jobs: 2,729,562.

The Server Status page for Returning participants currently reports results ready to send as 71,144.

As far as I know, they are different queues. Total queued jobs feeds the "ready to send"-queue.

---

As far as I know, they are different queues. Total queued jobs feeds the "ready to send"-queue.

That is my understanding as well.

If you look at the glossary at the bottom of the server status page, the Feeder sends tasks to the Scheduler. The queued jobs (on the home page) is the number available to the Feeder. The ready to send number on the server status page are those in the Scheduler which are immediately available for clients (our computers).

---

Warped

As far as I know, they are different queues. Total queued jobs feeds the "ready to send"-queue.

That is my understanding as well.

If you look at the glossary at the bottom of the server status page, the Feeder sends tasks to the Scheduler. The queued jobs (on the home page) is the number available to the Feeder. The ready to send number on the server status page are those in the Scheduler which are immediately available for clients (our computers).

Could easily be correct, but definitely confusing. One of those server status lists should show both in that case.

Wow

Results comes up again.

---

Wow

Results comes up again.

And down. It was only transient sparkling.

---

As far as I know, they are different queues. Total queued jobs feeds the "ready to send"-queue.

That is my understanding as well.

If you look at the glossary at the bottom of the server status page, the Feeder sends tasks to the Scheduler. The queued jobs (on the home page) is the number available to the Feeder. The ready to send number on the server status page are those in the Scheduler which are immediately available for clients (our computers).

Could easily be correct, but definitely confusing. One of those server status lists should show both in that case.

It gets even more confusing. ;) There's another queue of about 100 tasks, I understand. You actually get a task from that queue not from the ready to send queue directly. Undoubtedly there's a good reason. Maybe it facilitates the throughput on the server-end

---