Posts by dekim

1) Message boards : Feedback : New server (Message 6251)
Posted 8 Dec 2017 by Profile dekim
Post:
Looks like next week and unless something else comes up, it SHOULD HAPPEN :)

It will be just like the R@h server, hardware and software upgrades.
2) Message boards : Feedback : New server (Message 6250)
Posted 7 Dec 2017 by Profile dekim
Post:
Sorry, things keep coming up. I'll hopefully get a chance to work on it soon.
3) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6238)
Posted 21 Nov 2017 by Profile dekim
Post:
Not sure why but this error is from a very old app version.
4) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6231)
Posted 21 Nov 2017 by Profile dekim
Post:
Finally finished the builds. It took some time because we updated the source again to include additional bug fixes. I also updated the android version. We'll submit some tests soon.
5) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6226)
Posted 3 Nov 2017 by Profile dekim
Post:
Sorry! I've canceled this test batch. Looks like a database issue I'll have to troubleshoot.
6) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6214)
Posted 2 Oct 2017 by Profile dekim
Post:
We are still actively using 3.73 for forward folding and for Robetta structure prediction.
7) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6212)
Posted 2 Oct 2017 by Profile dekim
Post:
The latest boinc client release, 7.8.2 is buggy. The BOINC developers are working on a fix but not knowing how long it may take, I will be testing application side fixes for the minirosetta app. The main issue is that work may run in dirty slot directories and when this happens our application crashes. It's causing a 10-20% increase in failures.
8) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6207)
Posted 29 Aug 2017 by Profile dekim
Post:
Aside from this issue, are the graphics ok?
9) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6203)
Posted 22 Aug 2017 by Profile dekim
Post:
Yes, I just updated the app to 4.02 to address this.

The issue was that we are using the new BOINC graphics api which uses a new to us font rendering framework. The BOINC ttfont.cpp code necessary for the fonts to work does not resolve the filename (using the boinc_resolve_filename api function) of the ttf font file so the graphics app would crash under the boinc client but not with a local test. This is because we passed the current run directory to the ttf_load_fonts function and not the project directory. Luckily it didn't take me that long to find the cause of this bug and hopefully I fixed it.
10) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6201)
Posted 21 Aug 2017 by Profile dekim
Post:
Sorry, I was busy during the weekend and only added a small batch just in case there were issues. I also noticed the assimilator and validator wasn't turned on for the new app.

The latest app update will be named "rosetta". This is mainly because it is not backwards compatible with the current app for "rosetta scripts XML" protocols.
11) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6198)
Posted 18 Aug 2017 by Profile dekim
Post:
Please post issues/bugs regarding the 'rosetta_beta_4.0+' application versions here.
12) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6172)
Posted 11 Apr 2017 by Profile dekim
Post:
You can ignore those warnings. They are harmless. I will hopefully have those warnings removed in the next release soon.
13) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6171)
Posted 11 Apr 2017 by Profile dekim
Post:
please keep those going.
14) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6166)
Posted 6 Apr 2017 by Profile dekim
Post:
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.
15) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6162)
Posted 5 Apr 2017 by Profile dekim
Post:
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).
16) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6157)
Posted 4 Apr 2017 by Profile dekim
Post:
These work units should eventually finish. I suggest not killing them. We'll see if we can reduce the run times for future batches.
17) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6155)
Posted 1 Apr 2017 by Profile dekim
Post:
Yes, I've noticed these warnings on some devices but can't reproduce them on mine. I'll have to figure out what libraries aren't being used but linked against. Thanks!
18) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6152)
Posted 29 Mar 2017 by Profile dekim
Post:
I updated the android app to 3.82. I think I managed to work out the major issues.
19) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6150)
Posted 28 Mar 2017 by Profile dekim
Post:
I'm seeing a lot of early errors from the 3.80 android app so I'll probably revert to the previous version after letting it run through the night.

edit: I reverted back to 3.79 as 3.81.
20) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6147)
Posted 17 Mar 2017 by Profile dekim
Post:
Eventually when it's necessary, but I'm focusing on android for the moment. The XML changes are not backwards compatible so the next update will likely be under a new app name. However, there hasn't been a significant research related need to update the pc platforms yet.

There are a lot of android users joining our project and there's potential for significantly more in the near future.



Next 20



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