This update includes bug fixes to the symmetric modeling protocol and also an update to the windows graphics application to accommodate large models. Please post bugs/issues here.

Not really a problem, but referring to the description that now large models are better supported by windows graphics application.
For me it's not working for
https://boinc.bakerlab.org/rosetta/result.php?resultid=722810814 and
https://boinc.bakerlab.org/rosetta/result.php?resultid=722775030

Application only goes to blank window. At least the application does not crash in full screen mode like the previous one.

Greetings, Michael

Update: From time to time the application window shows graphics. However, full screen mode still results in black screen.

Thanks for the heads up. I'll look into this. Anyone else seeing issues with the graphics?

Still no graphics for Linux / Ubuntu after many years I think! :(

---

Still no graphics for Linux / Ubuntu after many years I think! :(

The reason is clear: There is no graphics for command-line interface ;)
Just kidding, hope there'll be a fix, soon.

I'm finding that these 3.54 Tasks are generating a MASSIVE number of Small Files in the Slot directory - 3853 files in each of two current Slots running MR 3.54 WUs.
Not only is this Much higher than I've noticed for any older Tasks, but the Tasks when Checkpointing seem to work to Update most all of these Files. That means a HDD Queue Depth that THRASHES the HDD and KILLS the Win7 UI for any other App that happens to need a bit of Disk IO. (And my HDD is Cached to SSH using iRST...)

The vast majority of the Files in question are ".PDB" and ".PATCHDOCK" - the former each sized 170-188KB and the latter all 8-12KB.

I'm finding that these 3.54 Tasks are generating a MASSIVE number of Small Files in the Slot directory - 3853 files in each of two current Slots running MR 3.54 WUs.
Not only is this Much higher than I've noticed for any older Tasks, but the Tasks when Checkpointing seem to work to Update most all of these Files. That means a HDD Queue Depth that THRASHES the HDD and KILLS the Win7 UI for any other App that happens to need a bit of Disk IO. (And my HDD is Cached to SSH using iRST...)

The vast majority of the Files in question are ".PDB" and ".PATCHDOCK" - the former each sized 170-188KB and the latter all 8-12KB.

Thanks for the heads up, we are aware of this issue and the lab member is changer her job setup to fix it. We'll cancel the existing jobs.

I'm finding that these 3.54 Tasks are generating a MASSIVE number of Small Files in the Slot directory - 3853 files in each of two current Slots running MR 3.54 WUs.
Not only is this Much higher than I've noticed for any older Tasks, but the Tasks when Checkpointing seem to work to Update most all of these Files. That means a HDD Queue Depth that THRASHES the HDD and KILLS the Win7 UI for any other App that happens to need a bit of Disk IO. (And my HDD is Cached to SSH using iRST...)

The vast majority of the Files in question are ".PDB" and ".PATCHDOCK" - the former each sized 170-188KB and the latter all 8-12KB.

can you provide the name of this job?

can you provide the name of this job?

I had REAL DIFFICULTIES doing ANYTHING with my PC whilst the MiniRosetta Tasks were "Having their Way" with my PC, but I believe it was these two Tasks of which I finally was hit Bad Enough to Complain:
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770395
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770254

There were 2-3 other Active MR Tasks ongoing at the same time, but by watching which were reported Running at the Critical Times (couldn't really do Anything else), I believe that I identified the correct Suspects. (The Computer specifics are accurately listed...)

I've since gone No New Tasks and Aborted all which were Loaded but not yet Started. I let the Offenders run to Completion - both to see if they would Complete, and to not have Wasted so much of my HDD/SSD's life and also waste the CPU and Science Work...

Please review and confirm whether these are the proper Culprits...

I'm finding that these 3.54 Tasks are generating a MASSIVE number of Small Files in the Slot directory

Just curious, where is this slot directory you speak of? I checked all over the BOINC folders in 'ProgramData' but couldn't find anything called 'Slot' and I'd like to check this out on my end.

Well, there is total silence on the RALPH@Home site...

I got 4 WUs earlier today and all 4 are now stuck a various percentages, though running for more than 4 hours by now.
Are they still supposed to do something useful? Right now they just blocking everything else but I would hate to abort them just yet...

Ralf

Well, there is total silence on the RALPH@Home site...
I got 4 WUs earlier today and all 4 are now stuck a various percentages, though running for more than 4 hours by now.

They ask you the url of wus with problem, but you don't reply

---

I'm finding that these 3.54 Tasks are generating a MASSIVE number of Small Files in the Slot directory

Just curious, where is this slot directory you speak of? I checked all over the BOINC folders in 'ProgramData' but couldn't find anything called 'Slot' and I'd like to check this out on my end.

Yes:
C:ProgramDataBOINCslots ... C:ProgramDataBOINCslots1 ... thru C:ProgramDataBOINCslots4
One Slot for each Processor Thread plus one Slot for each GPU (4 and 1 in my case)...

Well, there is total silence on the RALPH@Home site...

I got 4 WUs earlier today and all 4 are now stuck a various percentages, though running for more than 4 hours by now.
Are they still supposed to do something useful? Right now they just blocking everything else but I would hate to abort them just yet...

Ralf

Are these Ralph jobs? Can you provide the task names?

can you provide the name of this job?

I had REAL DIFFICULTIES doing ANYTHING with my PC whilst the MiniRosetta Tasks were "Having their Way" with my PC, but I believe it was these two Tasks of which I finally was hit Bad Enough to Complain:
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770395
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770254

There were 2-3 other Active MR Tasks ongoing at the same time, but by watching which were reported Running at the Critical Times (couldn't really do Anything else), I believe that I identified the correct Suspects. (The Computer specifics are accurately listed...)

I've since gone No New Tasks and Aborted all which were Loaded but not yet Started. I let the Offenders run to Completion - both to see if they would Complete, and to not have Wasted so much of my HDD/SSD's life and also waste the CPU and Science Work...

Please review and confirm whether these are the proper Culprits...

I forwarded this post to the researcher who submitted the jobs. I'm pretty sure these are the bad jobs and they have been canceled.

[/quote] I had REAL DIFFICULTIES doing ANYTHING with my PC whilst the MiniRosetta Tasks were "Having their Way" with my PC, but I believe it was these two Tasks of which I finally was hit Bad Enough to Complain:
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770395
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770254

There were 2-3 other Active MR Tasks ongoing at the same time, but by watching which were reported Running at the Critical Times (couldn't really do Anything else), I believe that I identified the correct Suspects. (The Computer specifics are accurately listed...)

I've since gone No New Tasks and Aborted all which were Loaded but not yet Started. I let the Offenders run to Completion - both to see if they would Complete, and to not have Wasted so much of my HDD/SSD's life and also waste the CPU and Science Work...

Please review and confirm whether these are the proper Culprits...[/quote]

So sorry, these were both my jobs. We were aware of the issue (the protocol didn't like the naming convention of some of the input files and that was messing everything up) and thought we had deleted all of them. You must have gotten a couple stragglers that slipped through. I apologize. Thanks for letting me know. I have tracked all of the sub-batches down and made sure no more jobs were getting released for these. Thanks for donating computing time to our Rosetta@Home projects!

I had REAL DIFFICULTIES doing ANYTHING with my PC whilst the MiniRosetta Tasks were "Having their Way" with my PC, but I believe it was these two Tasks of which I finally was hit Bad Enough to Complain:
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770395
https://boinc.bakerlab.org/rosetta/result.php?resultid=722770254

There were 2-3 other Active MR Tasks ongoing at the same time, but by watching which were reported Running at the Critical Times (couldn't really do Anything else), I believe that I identified the correct Suspects. (The Computer specifics are accurately listed...)

I've since gone No New Tasks and Aborted all which were Loaded but not yet Started. I let the Offenders run to Completion - both to see if they would Complete, and to not have Wasted so much of my HDD/SSD's life and also waste the CPU and Science Work...

Please review and confirm whether these are the proper Culprits...[/quote]

So sorry, these were both my jobs. We were aware of the issue (the protocol didn't like the naming convention of some of the input files and that was messing everything up) and thought we had deleted all of them. You must have gotten a couple stragglers that slipped through. I apologize. Thanks for letting me know. I have tracked all of the sub-batches down and made sure no more jobs were getting released for these. Thanks for donating computing time to our Rosetta@Home projects![/quote]

No Problem...

Once I get the CPU/GPU done Chewing on the Hunk-O MilkyWay WUs that stepped up to fill the Void, I'll re-enable MiniRosetta...

Well, there is total silence on the RALPH@Home site...

I got 4 WUs earlier today and all 4 are now stuck a various percentages, though running for more than 4 hours by now.
Are they still supposed to do something useful? Right now they just blocking everything else but I would hate to abort them just yet...

Ralf

Are these Ralph jobs? Can you provide the task names?

Yes, they are RALPH jobs ;-)

I had suspended them for a while so some other project WUs could finish before their deadline and then resumed all 4 jobs. They seemed to have picked up on resume just fine and two of the already reported:

cb_mar11_dock_placestub_EEEH_1035_vegf_ProteinInterfaceDesign_20241_91_0_0
cb_mar11_dock_placestub_EEEH_1038_vegf_ProteinInterfaceDesign_20241_91_0_0

The other two are currently still crunching, named

cb_mar11_dock_placestub_EEEH_1037_vegf_ProteinInterfaceDesign_20241_91_0_0
cb_mar11_dock_placestub_EEEH_1036_vegf_ProteinInterfaceDesign_20241_91_0_0

and should finish within the next 15min or so...

Those got previously stuck for hours at 12% and 20% IIRC,

Ralf

Well, there is total silence on the RALPH@Home site...
I got 4 WUs earlier today and all 4 are now stuck a various percentages, though running for more than 4 hours by now.

They ask you the url of wus with problem, but you don't reply

Who asked me where?
I replied to the question of the WU names a bit earlier, after I got back to check in here. The main problem for me is that I don't necessarily have always the time to babysit. And there has been no post on the RALPH forum (if that is what you are referring to) for more than 30 days. And not that they ever have been very communicative in the first place...

Ralf

I replied to the question of the WU names a bit earlier, after I got back to check in here. The main problem for me is that I don't necessarily have always the time to babysit.

If you don't want to "babysit", don't partecipate to beta projects :-P

And there has been no post on the RALPH forum (if that is what you are referring to) for more than 30 days. And not that they ever have been very communicative in the first place...

Ok, they are not very comunicative (we know), but you post YOUR problem the 13 Mar 2015 3:47:36 UTC and Kripton reply you the 13 Mar 2015 4:33:20 UTC , 50 minutes later...

---