Rosetta Mini for Android is not available for your type of computer.

Message boards : Number crunching : Rosetta Mini for Android is not available for your type of computer.

To post messages, you must log in.

AuthorMessage
googloo
Avatar

Send message
Joined: 15 Sep 06
Posts: 133
Credit: 21,587,974
RAC: 6,188
Message 80212 - Posted: 21 Jun 2016, 18:08:15 UTC

This Rosetta server problem causes a 24-hour delay in my computer connecting with Rosetta. I have now had to manually update Rosetta five times in the last two days in order to avoid running out of Rosetta tasks.

This is not the first time I have raised this problem. Please fix this.
ID: 80212 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Wiktor Jezioro | lakewik.pl

Send message
Joined: 22 Feb 15
Posts: 4
Credit: 24,056,394
RAC: 0
Message 80217 - Posted: 22 Jun 2016, 9:12:16 UTC

I have same problem
ID: 80217 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Luigi R.

Send message
Joined: 7 Feb 14
Posts: 39
Credit: 2,045,527
RAC: 0
Message 80218 - Posted: 22 Jun 2016, 17:00:22 UTC
Last modified: 22 Jun 2016, 17:01:52 UTC

Same problem here.

22-Jun-2016 14:51:23 [rosetta@home] Scheduler request completed: got 0 new tasks
22-Jun-2016 14:51:23 [rosetta@home] No work sent
22-Jun-2016 14:51:23 [rosetta@home] Rosetta Mini for Android is not available for your type of computer.
22-Jun-2016 14:51:23 [rosetta@home] (won't finish in time) BOINC runs 81.4% of time, computation enabled 72.7% of that


That's not true! Indeed, after manual update some minutes later...

22-Jun-2016 15:35:14 [rosetta@home] Scheduler request completed: got 25 new tasks


I need to use a small task queue.
Unfortunately this forces me to switch to another project.
ID: 80218 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 1 Dec 05
Posts: 1847
Credit: 7,991,844
RAC: 8,693
Message 80219 - Posted: 22 Jun 2016, 18:50:03 UTC - in response to Message 80212.  

This is not the first time I have raised this problem. Please fix this.


Admins seem to be NOT so interested to resolve this

ID: 80219 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Dr. Merkwürdigliebe
Avatar

Send message
Joined: 5 Dec 10
Posts: 81
Credit: 2,657,273
RAC: 0
Message 80220 - Posted: 22 Jun 2016, 19:07:12 UTC

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.
ID: 80220 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Luigi R.

Send message
Joined: 7 Feb 14
Posts: 39
Credit: 2,045,527
RAC: 0
Message 80221 - Posted: 22 Jun 2016, 20:07:46 UTC - in response to Message 80220.  

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.

Totally agree.


Anyway a temporary "solution":
-block work request of all project except Rosetta
-increase queue days (e.g. 7)
-flood rosetta server for 2 hours (a request every 4 minutes)


Now I have got more than 400 tasks and my host will not get dried.
ID: 80221 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Sid Celery

Send message
Joined: 11 Feb 08
Posts: 1965
Credit: 38,176,314
RAC: 10,027
Message 80224 - Posted: 23 Jun 2016, 3:38:32 UTC - in response to Message 80221.  

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.

Totally agree.

Anyway a temporary "solution":
-block work request of all project except Rosetta
-increase queue days (e.g. 7)
-flood rosetta server for 2 hours (a request every 4 minutes)

Now I have got more than 400 tasks and my host will not get dried.

But may be counter-productive if you can't meet the current shorter deadlines while leaving less tasks available for others to run.

With the number of active users doubling over the last two months, Rosetta's becoming a victim of its own success. The solution is to make some additional resource available to make work


ID: 80224 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Luigi R.

Send message
Joined: 7 Feb 14
Posts: 39
Credit: 2,045,527
RAC: 0
Message 80228 - Posted: 23 Jun 2016, 8:04:28 UTC - in response to Message 80221.  

I can meet the deadlines.
ID: 80228 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 1 Dec 05
Posts: 1847
Credit: 7,991,844
RAC: 8,693
Message 80229 - Posted: 23 Jun 2016, 9:43:57 UTC - in response to Message 80220.  

Solution: Drop the support for smartphones and tablets and concentrate on enabling AVX2. This should have a much higher priority.


+1

ID: 80229 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Sid Celery

Send message
Joined: 11 Feb 08
Posts: 1965
Credit: 38,176,314
RAC: 10,027
Message 80296 - Posted: 27 Jun 2016, 1:07:01 UTC - in response to Message 80228.  

I can meet the deadlines.

That's good, but a bit surprising if you hold a 7-day buffer but half the tasks have a deadline of 2 or 5 days rather than the more usual 14 days
ID: 80296 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Luigi R.

Send message
Joined: 7 Feb 14
Posts: 39
Credit: 2,045,527
RAC: 0
Message 80297 - Posted: 27 Jun 2016, 7:19:46 UTC - in response to Message 80296.  
Last modified: 27 Jun 2016, 7:34:38 UTC

I can meet the deadlines.

That's good, but a bit surprising if you hold a 7-day buffer but half the tasks have a deadline of 2 or 5 days rather than the more usual 14 days


Deadline of 2 is rare.
5 days is enough to complete 240 4-hour tasks.
If I set 7 days of work queue, it's not my mistake whether BOINC software downloads work that's expiring in 5 days. Indeed very few tasks were going to expire in 5 days.
As a last resort if I want to meet deadlines and I can't do it, I could switch to 1-hour configuration and update preferences. Then all the starting tasks will get cpu_run_time_pref=3600. In my case the required time to complete tasks would be divided by 4.

Finally I don't think my '24/7 effort' is comparable to server work to generate tasks and according to me a deadline of 5 days doesn't mean "hurry up!". Some administrators of other projects say "feel free to abort tasks if you need" too.
I don't know if a participation by this behaviour could damage Rosetta@home project, but I think not.
ID: 80297 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 80301 - Posted: 27 Jun 2016, 13:19:59 UTC - in response to Message 80297.  

Some administrators of other projects say "feel free to abort tasks if you need" too.
I don't know if a participation by this behaviour could damage Rosetta@home project, but I think not.


Certainly, abort 'em if you must. They will quickly be reassigned. As you say, reducing your preference for runtime can clear work quickly. Beware that the change pertains to tasks still running too. And if your new preference precedes the current CPU time on a task by 4 hours, this can lead to the task thinking it is hung up and closing out. To avoid this, I sometimes reduce runtime in notches over the course of an afternoon. Or, if timing works out better, I'll suspend a couple of tasks that have run a long time, clear through the work, and then bump the runtime preference back up (and doing an update to project) before releasing them again.
Rosetta Moderator: Mod.Sense
ID: 80301 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Sid Celery

Send message
Joined: 11 Feb 08
Posts: 1965
Credit: 38,176,314
RAC: 10,027
Message 80312 - Posted: 28 Jun 2016, 23:48:06 UTC - in response to Message 80297.  

I can meet the deadlines.

That's good, but a bit surprising if you hold a 7-day buffer but half the tasks have a deadline of 2 or 5 days rather than the more usual 14 days

Deadline of 2 is rare.
5 days is enough to complete 240 4-hour tasks.
If I set 7 days of work queue, it's not my mistake whether BOINC software downloads work that's expiring in 5 days. Indeed very few tasks were going to expire in 5 days.
As a last resort if I want to meet deadlines and I can't do it, I could switch to 1-hour configuration and update preferences. Then all the starting tasks will get cpu_run_time_pref=3600. In my case the required time to complete tasks would be divided by 4.

I'm getting around a third of tasks with a 2-day deadline - maybe why I thought differently. But if it's working out for you without manually intervening, that's great.
ID: 80312 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : Rosetta Mini for Android is not available for your type of computer.



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