I think the fact that the project heard & responded to the suggestion that writing things to the slot directories that didn't need to be there was un-necessary, both here in the forums & by deploying a new application, shows that they do take notice & respond.

"All tasks are verified by a wingman for safety"

Actually, after a host delivers a certain number of valid results, it becomes quorum 1.
All the AutoDock/AutoDock Vina projects have been that way.
Periodically however, quorum 2 will be re-enabled to make sure the host is doing fine.

The AutoDock software currently in use at OpenPandemics is in a way, a new version, as it includes a new "reactive docking" protocol.

Clear and transparent, dedicated section to this specific project with all news posted in one place: https://www.worldcommunitygrid.org/research/opn1/news.do
Promise of frequent updates
Longer deadlines (~1 week)
Lower completion times (~2 hours)
Lower memory footprint (~200MB)
All tasks are verified by a wingman for safety
AVX support
GPU support nearly done
The ability to choose to work on only COVID-19
Badges specifically for COVID-19
Based on the free and open source AutoDock software instead of the closed source proprietary Rosetta software.
According to Wikipedia "AutoDock is one of the most cited docking software applications in the research community"

The fact that it's used so much is probably why it's so much more stable.
Although I admit this is from very little testing of the few machines I've swapped over.

I'll give it a week to see how things go, then I'll discuss with my colleagues about moving the work fleet over.

<10k tasks left, previously there was over 2million and was actively being kept above 1 million
No news/updates in regards to project progress - Folding@Home gives update almost daily
No way to know what you've contributed to (Folding@Home puts their publications front and center. GPUGRID gives you badges according to each publication you contributed to).
Continuing the above point: Rosetta does nothing to make you feel involved. e.g. Folding@Home now has a community Discord to keep contributors engaged to try and reduce the decline in users over time.
Still no AVX support - Folding@Home has this
Still no GPU support - Folding@Home has this
Memory errors posted on forums is going unaddressed (See signal 11 for Linux/Max and ACCESS_VIOLATION for Windows.)
In some cases, BSOD's are occurring when running these tasks at the same time as other heavy applications.
Direct PMs unanswered, direct emails ignored, forum posts not replied to.

The lack of communication, especially in regards to the memory errors, is what annoys me the most. Work feels wasted.

I'm not sure how one can update that global preference via the web site. I just edited the xml but that isn't convenient. If anyone knows, please post instructions here. I suppose I can modify the database records but I'm not completely sure that would cause problems or not and don't want to take that risk.

> Log into the Rosetta@Home website and go to your account.
> Click on "Computing preferences".
> Click "Edit Preferences" at the bottom.
> Change anything you want. e.g. "Store at least X days of work". If you don't want to change anything just change it back straight after.
> Click "Update preferences" at the bottom.
---
> At this point you can either edit your preferences again to undo your change, or you can proceed with the next step.
> Open up your BOINC manager, select the Rosetta@Home project and click the "Update" button.

That's it. Your preferences are now encrypted with HTTPS instead of using HTTP.

While this works, it is a really convoluted method that next to no one is going to bother following.

There were indeed some remaining http references in some xmls and I think I traced the issue. This is hopefully fixed now but will only be active with new jobs submitted by our group. Currently queued and running jobs will still have some URLs with http. I'll check again after new jobs get submitted.

<source_scheduler>http://bwsrv1.bakerlab.org/rosetta_cgi/cgi</source_scheduler>

<source_scheduler>http://bwsrv1.bakerlab.org/rosetta_cgi/cgi</source_scheduler>

Those URLs should be https. I'm not sure what is going on with your host.

I'd like to attract attention

As for the captcha, I can add it to the registration / email forms to replace the internal spam filtering when I get a chance but that's definitely low priority.

All it does is confirm there is no man in the middle. Useful for financial stuff, passwords and so on, not so for downloads of data files.

<upload_url>http ://boinc.bakerlab.org/rosetta_cgi/file_upload_handler</upload_url>

<source_scheduler>http ://bwsrv1.bakerlab.org/rosetta_cgi/cgi</source_scheduler>

<url>http ://boinc.bakerlab.org/rosetta_cgi/file_upload_handler</url>

<source_scheduler>http ://bwsrv1.bakerlab.org/rosetta_cgi/cgi</source_scheduler>

Completely agree. If there's a way, we can do it. I can look into this and test on our ralph project. But this will take some time since it will require an application update.

Indeed this is not efficient but there currently is no easy workaround that we know of since Rosetta is dependent on the database directory structure. If anyone knows of an easy workaround, I'm all ears. The Rosetta application depends on the database directory structure. This database holds all the required score, chemical, sampling, rotamer, etc. parameters and libraries that are the backbone of all the computations and a result of many years of research and development. These parameters may or may not change with application updates. For example, for the COVID-19 specific jobs, we had to significantly increase the size of the database to include an improved local protein structure fragment library in addition to side chain motif libraries to enable the interface design protocol. These are parameters/libraries that have been developed and continue to be developed in the lab through careful analysis and research of native protein structures and molecular structures in general.

3. We almost have the new update out, but not yet.

http://game.amd.com/us-en/unlock_radeon4800.aspx?p=2


Yes, It can run crysis.

On the first machine, NOD32 Antivirus thinks the Minirosetta .exe either contains a viral signature or looks bad heuristically (their UI doesn't say which). I have to add an exclusion to get the thing out of quarantine, every time a new version is released.

Hi David.

Did that it worked on the second try, thanks.

pete.