Rosetta mini beta and/or android 3.61-3.83

Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83

To post messages, you must log in.

Previous · 1 . . . 7 · 8 · 9 · 10 · 11 · 12 · Next

AuthorMessage
zioriga

Send message
Joined: 16 Feb 06
Posts: 7
Credit: 290,247
RAC: 0
Message 6159 - Posted: 5 Apr 2017, 11:30:13 UTC

Now I'm at 99.5 after 31,5h
On my S3
ID: 6159 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6160 - Posted: 5 Apr 2017, 13:53:00 UTC - in response to Message 6159.  

Now I'm at 99.5 after 31,5h
On my S3


These are wus for I7 or Ryzen, not for my little arm... :-(
ID: 6160 · Report as offensive    Reply Quote
Profile dekim
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 20 Jan 06
Posts: 250
Credit: 543,579
RAC: 0
Message 6162 - Posted: 5 Apr 2017, 18:00:08 UTC

I agree. I'll talk to the researcher. The long run time is due to filtering logic. Even on one of our local machines it takes about an hour to generate a model (after quite a few filtered attempts).
ID: 6162 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6163 - Posted: 6 Apr 2017, 5:37:47 UTC - in response to Message 6158.  

I've another one. 99,1% after 18h.


99,6 after 37h....a small agony
Now, i think 1000 points is earned!!! :-P
ID: 6163 · Report as offensive    Reply Quote
Vikram K. Mulligan

Send message
Joined: 6 Jan 16
Posts: 2
Credit: 0
RAC: 0
Message 6164 - Posted: 6 Apr 2017, 6:26:44 UTC - in response to Message 6162.  

Although these slow jobs take longer to find a solution, they are heavily biased to sampling regions of conformation space that these peptides can actually access and which are relevant to our interests. That is, we might make the sampling rate slower by a factor of 100, but we're perhaps 1,000 or 10,000 times more likely for any given sample to be "useful". We're crunching numbers more intensively to produce better results instead of just relying on more sampling. I can say that the jobs that we're running now are successfully sampling the native state with fewer samples in cases in which incredible amounts of the old, naïve sampling produced nothing near the native state.

I'm not sure that we can make the sampling faster (i.e. produce more samples per CPU-hour), but the credit earned per sample should be proportional to the CPU-hours spent per sample, no?
ID: 6164 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6165 - Posted: 6 Apr 2017, 9:08:22 UTC - in response to Message 6164.  
Last modified: 6 Apr 2017, 9:08:51 UTC

We're crunching numbers more intensively to produce better results instead of just relying on more sampling.


This is not a problem, i like the science you do!!

the credit earned per sample should be proportional to the CPU-hours spent per sample, no?


I'm not sure. If i crunch a decoy in 2h with, for example, a Ryzen 1800x and the same decoy with my Huawei in 30h, i take the same points?
ID: 6165 · Report as offensive    Reply Quote
Profile dekim
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 20 Jan 06
Posts: 250
Credit: 543,579
RAC: 0
Message 6166 - Posted: 6 Apr 2017, 18:33:53 UTC - in response to Message 6165.  

Since the android app is a separate application, the credit per decoy running average will only use results from android jobs. But there is the issue of possibly adding a correction factor to try to normalize the credits coming from the standard app vs the arm app given the same protocol. I'll have to look into this and it would require running some benchmarks and updating the standard app. The arm app is running the latest Rosetta version.
ID: 6166 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6167 - Posted: 7 Apr 2017, 5:32:42 UTC - in response to Message 6163.  

99,6 after 37h....a small agony


Now 99,7% after 57h.
Strange behaviour, it continues to slow down.
I don't think i'll finish before deadline (tomorrow morning).
ID: 6167 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6168 - Posted: 9 Apr 2017, 13:09:30 UTC - in response to Message 6164.  

Although these slow jobs take longer to find a solution, they are heavily biased to sampling regions of conformation space that these peptides can actually access and which are relevant to our interests.


i'm afraid, but it's 99,8% after 105h. I've killed this wus.
ID: 6168 · Report as offensive    Reply Quote
Admpicard999

Send message
Joined: 4 Sep 16
Posts: 2
Credit: 1,257
RAC: 0
Message 6169 - Posted: 9 Apr 2017, 23:53:40 UTC - in response to Message 6168.  

Hi:

I see there are many here who have tasks that have been running for quite some time. I have three that have gone well past their reply by time: one running for 74 hours at 99.2%, a second 29 hours at 98.1% and a third at 30 hors at 98.2%. This is using a Pixel on Android 7.1.2 (newest). Do I let them keep going or do I stop them?
ID: 6169 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6170 - Posted: 10 Apr 2017, 8:22:37 UTC - in response to Message 6169.  
Last modified: 10 Apr 2017, 8:23:56 UTC

Do I let them keep going or do I stop them?


I know these working units are important for admins/developers, but i kill all "ralphtest_c." wus

All with these warnings:
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x2828
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x2828
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x2828
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x2828
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x2828
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
WARNING: linker: ../../projects/ralph.bakerlab.org/minirosetta_android_3.83_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x2828
ID: 6170 · Report as offensive    Reply Quote
Profile dekim
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 20 Jan 06
Posts: 250
Credit: 543,579
RAC: 0
Message 6171 - Posted: 11 Apr 2017, 19:14:40 UTC - in response to Message 6169.  

please keep those going.
ID: 6171 · Report as offensive    Reply Quote
Profile dekim
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 20 Jan 06
Posts: 250
Credit: 543,579
RAC: 0
Message 6172 - Posted: 11 Apr 2017, 19:15:25 UTC - in response to Message 6170.  
Last modified: 11 Apr 2017, 19:16:04 UTC

You can ignore those warnings. They are harmless. I will hopefully have those warnings removed in the next release soon.
ID: 6172 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6173 - Posted: 12 Apr 2017, 6:46:43 UTC - in response to Message 6171.  

please keep those going.


50h to crunch 0,1% i think 2 options:
- a bug in "ralph_test_c." wus
- my smartphone is too little to crunch these wus and i need an S8

I'll try another wu
ID: 6173 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6174 - Posted: 12 Apr 2017, 13:16:43 UTC

I just finished correctly a "ralp_test_c." wu after 20k seconds.
But these wus are different from problematic "ralphtest_c."??
ID: 6174 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6175 - Posted: 12 Apr 2017, 13:18:16 UTC - in response to Message 6173.  

- a bug in "ralph_test_c." wus

"ralphtest_c.", i mean
ID: 6175 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6177 - Posted: 19 Apr 2017, 8:22:33 UTC
Last modified: 19 Apr 2017, 8:26:46 UTC

Here again.
99,9% after 111h of crunching.
The deadline was 3 days ago.....
4044862
ID: 6177 · Report as offensive    Reply Quote
zioriga

Send message
Joined: 16 Feb 06
Posts: 7
Credit: 290,247
RAC: 0
Message 6178 - Posted: 20 Apr 2017, 5:05:33 UTC

I have this problem:

In my "Tasks for user" page I have 4 WU in progress, but ....... on my smartphone I have 5 WUs. :-)

I don't know if this is a problem specific to android app or is a general problem
ID: 6178 · Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 9 Apr 08
Posts: 840
Credit: 1,888,960
RAC: 0
Message 6179 - Posted: 21 Apr 2017, 6:59:19 UTC - in response to Message 6177.  

99,9% after 111h of crunching.


Still 99,9% after 145 hours.
What should i do?

ID: 6179 · Report as offensive    Reply Quote
mmonnin

Send message
Joined: 6 Dec 16
Posts: 8
Credit: 391,628
RAC: 0
Message 6180 - Posted: 21 Apr 2017, 9:12:08 UTC - in response to Message 6179.  

I aborted those that I had at 99%. The others just timed out while the server was down.
ID: 6180 · Report as offensive    Reply Quote
Previous · 1 . . . 7 · 8 · 9 · 10 · 11 · 12 · Next

Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83



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