Posts by BarryAZ

1) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 87361)
Posted 24 Sep 2017 by BarryAZ
Post:
And they remain offline -- I suspect when folks show up for the project after the weekend they will take notice and restart the validators. Until then..... meh
2) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 87348)
Posted 23 Sep 2017 by BarryAZ
Post:
I have noticed this as well --- starting on Friday. (Sept. 22)
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81494)
Posted 18 Apr 2017 by BarryAZ
Post:
It seems to me that the upload problem has been solved. At least, all my stuck WU's have been uploaded now.



Yes, same here. Glad whatever the problem was has been resolved.
4) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81478)
Posted 17 Apr 2017 by BarryAZ
Post:
Pretty similar here -- realizing that the issue is back at the Rosetta site, since iis not happening with other projects on the same systems, I've elected to suspend processing on Rosetta units, which pushes my processing over to WorldGrid.

I periodically try to push the uploads but so far (since last week) no joy here.

Ideally the folks on the project side will figure out the problem they have at there end and resolve it.



I've got 12 queued that are now past the due date.
And another 14 waiting that haven't gone past the due date yet, but
more are dropping off all the time.

These are spread out on 15 different clients.

5) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81123)
Posted 2 Feb 2017 by BarryAZ
Post:
David, thanks much for jumping in here -- the air had been getting rather thin.

My sense is that the 24 hour backoff is a server specific function -- as in the multiple other projects I work with their is a progressive backoff typically starting at either 5 minutes or 1 hour and progressing with multiple non-responsiveness up to as much as 3 to 5 hours and then recycling to a 1 hour back off. It is only with Rosetta I have seen that.

As to the android no work report -- again that is likely a project specific configuration. Other projects provide a 'no work for your applications' message but with Rosetta it seems specific to android work -- I would think that could be configured out.

I don't do code though... so its all speculative.

The other issue -- for which your post is seriously appreciated, is the sense of the active user community being a bit 'unloved' by a lack of periodic responses from folks such as yourself.

I'm sure you have more work than time, but even a weekly "we're here and watching" message might reduce that sense.

Thanks again for you message.


In response to Mod.Sense's feedback/recommendations, I increased the short 2 day deadline to 3 days. I don't think I can increase the deadline longer for these high priority jobs. The deadlines are short for an important reason since there are time constraints for these jobs (weekly CAMEO benchmarks for Robetta). I also increased the standard deadline from 5-7 days to 2 weeks which should help.

If anyone knows how to change the 24 hour backoff, please chime in. I'm not sure if it's server or client logic and configurable.

Also, if anyone knows how to fix the "Android" alert, please let us know. I'll of course look into this also.

The last issue point I think can be coded into our application and I'll put it on the list of things to do for the next update.

Also, if you are not getting work, it is most likely because there isn't any to issue at the time. Our demand comes in waves as projects progress. However, our public structure prediction server, Robetta, usually provides continual work. It was down for a few days last week for updates though.

6) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81112)
Posted 1 Feb 2017 by BarryAZ
Post:
That raises an interesting question. Maybe a driving reason for the project to be essentially NO attention to the care and feeding of its most active participants reflects an internal decision that they already have too much work to process internally.

That, by actively ignoring the user community they are hoping to reduce the number of work units processed.

I can confirm that approach has worked just fine for me....



But I don't quite understand why our moderator can't just email someone at UW when exceptional problems arise. Aren't they on speaking terms?

If they don't need more work done, so be it. But they should tell us I believe.

7) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81105)
Posted 30 Jan 2017 by BarryAZ
Post:
As should be quite apparent to the truly active participants of this project, communicating with active participants by the project is a VERY low priority in the Rosetta scheme of things.

That means that issues perhaps viewed as insignificant by the project folks (or perhaps issues that they are simply not aware of) only get passing response.

I believe it is an informed choice made by the project to not allocate time and resources to the 'care and feeding' of the active user community.

Users get to prioritize as well, as a long time participant (going back over ten years) there have been times when maintained a daily completed work traffic generating 30 to 40 thousand credits. These days, it is more like 5 thousand credits as I shifted MY priorities to the WorldGrid project.

We all make choices.

And another blank day for stats

8) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81094)
Posted 27 Jan 2017 by BarryAZ
Post:
And of course for three weeks around the winter break as well.

Oh well

Stats are being picked up by the stats sites (eg Boincstats) but there's been no updates to the data. This has happened a few times since the site came back up a few weeks ago.

9) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81065)
Posted 19 Jan 2017 by BarryAZ
Post:
Indeed, with the non-response from the project folks, at this juncture, I will process all work units I have on hand and set to no new work.

Sadly, it is not clear to me that the people running the project are even aware of the "Problems and technical issues with Rosetta@home" as they for whatever reasons have elected to isolate themselves almost completely from the reporting in the message boards.

So the lack of resolution of issues is significantly exacerbated by the project *choice* to not participate in any meaningful way with the user community, including those end users who take the extra time to participate on the message boards in the hope (not fulfilled) to get information to the project and in the hope (not fulfilled) to receive timely information from the project.

So I will monitor traffic here, but absent a change, the World Grid project which does good works is going to get my "CPU processing" vote with the available cycles.

I have participated in the Rosetta project for over ten years, so I do not make this choice lightly.

10) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81059)
Posted 18 Jan 2017 by BarryAZ
Post:
Jim -- the project itself has run for over ten years with pretty solid reliability.

However, in terms of communications and responsiveness to end user reports and issues, they have been historically weak. It is an unfortunate aspect of the project.

It seems they really don't have anyone tasked to monitor the message boards including reports of problems. Further, no one is tasked to respond to end user reports including obvious reports which point to typically minor project configuration issues which could be corrected with just a bit of attention to the data provided by end users.

That, of course is exacerbated by the absolute lack of feedback to user community which provides those reports.

Now the reporting using community is but a VERY small number of the actual user population, so perhaps our efforts and feedback don't matter to the power that be, or at least don't matter enough to allocate a small amount of existing project resources to address the care and feeding of the most involved members of the Rosetta user community.

This is rather unfortunate.

As I noted before, I've now decided to pair WorldGrid with any workstation that has Rosetta. I've set World Grid with the same priority as Rosetta. So when Rosetta doesn't have work, or responds with its infamous automatic 24 hour back off, it amounts to the Rosetta project itself having a lower priority on my workstations -- and the WorldGrid folks who are also doing good research thus get a higher proportion of my processing time.

About a month ago, I had a Rosetta credit of 27 million. Today it is 27.7M

About a month ago, I had a Worldgrid credit of 17.5 million. Today it is 18.7 million. At this rate I figure WorldGrid will overtake Rosetta for me by the end of the year even though I have both projects at the same priority. I figure that's a project choice and am good with it.

Each project has their own internal priorities and it is apparent for Rosetta, that the care and feeding of their most interactive users is pretty low on their priority list.





I get the sinking feeling that no one at the top is aware of the problem. But after they see the work falling off, they will call a committee meeting on what to do. Someone will suggest better PR, and they will implement a better "User of the Day" award.



11) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81044)
Posted 16 Jan 2017 by BarryAZ
Post:
As to the work not available -- that should is likely a case of loading up new work for non-android devices and resolve itself.

As to correcting the error message there and making it like other BOINC projects -- that is, 'no work is available for your device' instead -- that would take some actual change at the project level, which in turn would require this ongoing report (I encounter this message as well), to get received by the project admins and then acted on.

As to the 24 hour delay, that is the same issue. That report (I run into it as well), requires not only that the message be received by the project admins and operators, but also that it be understood by them as a *project specific* issue and not a user issue nor one that is a function of the BOINC software. The 24 hour back-off is very much a project specific setting -- other projects have a progressive process when connects don't succeed start with a one hour back off. This is pretty clearly project specific and fixing it is up to the Rosetta project folks.

As to your computer being bored, well my approach has been to make sure that every computer I have which is connected to Rosetta, is also set up with WorldGrid. They are doing good work and very rarely run out of work, do not have Rosetta's 24 hour back off bug, and tend on their home site to provide good and updated status information for the user community.


Problem with 24-hour delay and "Rosetta Mini for Android is not available for your type of computer" still occuring. My machines is bored. When we can expect repair?

12) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 81016)
Posted 13 Jan 2017 by BarryAZ
Post:
I haven't received new tasks for quite a while. Not so big a deal, WorldGrid is picking up the slack for now.

But of course what would be seriously nice is to get some explanation of the status of things from project folks....

My interpretation of the statement used, is that it thinks that our client is asking for Android units while being a PC, so it will not send us units. :-)

I'm pretty sure it doesn't mean that, but we can all agree it's a dreadful line whatever they're trying to tell us.

Are people getting tasks through ok yet? I can see some of my unattended PCs haven't polled for a long while and it always bugs me whether it's because the PC has crashed or it's been forced into a 24-hour backoff again.

13) Message boards : Number crunching : "Rosetta Mini for Android is not available for your type of computer" (Message 81014)
Posted 12 Jan 2017 by BarryAZ
Post:
Indeed, it is as if at the moment, the only work units being created are for the android phones and not for workstations.

For now, worldgrid is very happy <smile>

I'm seeing the same thing on Ubuntu 16.04: a project backoff of 24 hours accompanied by the message "Rosetta Mini for Android is not available for your type of computer." when attempting to get new tasks via Update.

Before the recent hiccups this machine crunched Rosetta without any problems.
14) Message boards : Number crunching : No more work (Message 81012)
Posted 12 Jan 2017 by BarryAZ
Post:
Hmm -- I have not been able to get non Android work at this point. I hope that is only a function of the extended winter break at UW.

Aaaaand we're back, crunching is underway again.

15) Message boards : Number crunching : Rosetta no longer generating XML statistics files? (Message 81008)
Posted 12 Jan 2017 by BarryAZ
Post:
Thanks Sid -- yes, I see the update came through.

It is possible that the reboot they had to do as a result of the power outage cleared things up and it simply took a day to wash through to the stats sites.



Did I miss something or is there no commentary from the project regarding the XML statistics issue which has existed now for closing on three weeks??

No, I've not seen anything. I'll shoot an EMail to DK. Possible they disabled this to relieve strain on DB server.

Check out Boincstats now. Stats coming through.

I just picked up 139k in credits from Rosetta alone... #Yikes

16) Message boards : Number crunching : No more work (Message 81000)
Posted 11 Jan 2017 by BarryAZ
Post:
It might be difficult to tell -- it seems that UW has an extended break between terms and that applies to support staff including those involved with Rosetta.

It is why there has been no response from the project regarding the stats update XML data not having been updated for three weeks --- with no response from the project regarding it.

It may also be why a two or three hour power outage at UW resulted in a 36 hour totally offline period for the project.

You might post to the 'problems' thread --- eventually that might get a response.

Over the ten years I have processed for Rosetta, I have
17) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 80997)
Posted 11 Jan 2017 by BarryAZ
Post:
As noted in a separate thread.

Rosetta no longer generating XML statistics files.

Last XML stats update was three weeks ago.
18) Message boards : Number crunching : Rosetta no longer generating XML statistics files? (Message 80995)
Posted 10 Jan 2017 by BarryAZ
Post:
OK -- thanks for that.

That explains the 36 hour offline condition.

Did I miss something or is there no commentary from the project regarding the XML statistics issue which has existed now for closing on three weeks??

See project homepage which details on power outage in Seattle area.

19) Message boards : Number crunching : Rosetta no longer generating XML statistics files? (Message 80992)
Posted 10 Jan 2017 by BarryAZ
Post:
Well, I see someone did something since Saturday night when the project went totally offline.

I also see the XML statistics have yet to update.

And of course, I also see there has been nothing from the project admins. That is to be expected I suppose....
20) Message boards : Number crunching : Rosetta no longer generating XML statistics files? (Message 80981)
Posted 5 Jan 2017 by BarryAZ
Post:
Over the ten years or so that I have processed Rosetta work units, the project has been very reliable. Even now when the XML piece has been flat out broken for two weeks, the rest of the site appears to be mostly working, if very much unattended.

The one thing over the years that has been troublesome almost from the start, is that the project has never allocated any resources for a 'user keeper' -- someone who could communicate to users via the message boards or the home page when things are amiss. This is clearly one of those times.

For now, what I have done is partially reallocate CPU resources over to the World Grid project. I haven't shut down Rosetta, I'm just running less work for it.




This project is associated with the U of Washington. Students are out on break for another week or two, so probably our guys too.



Next 20



©2021 University of Washington
https://www.bakerlab.org