A few tests show that these are the only lines that need be included in the account_ file for it to work:

- <account>
<master_url>https://boinc.bakerlab.org/rosetta/</master_url>
<authenticator>fakefakefakefakefkaefakefakefake</authenticator>
<project_name>rosetta@home</project_name>
</account>

If you create this file in an empty c:/"program files"/boinc folder, and then install boinc, when the program starts it connects to rosetta and then expands the file appropriately.

My suggestions:

a) simple startup - this small file could be sent as a zipped attachemnt to the mail message you get to confirm registration. The zip would auo-un-zip to c:/"program files"/boinc by default (or possibly pick up one of the filenames stored in the registry?). People would be told, click this zip file then click on the boinc install

b) mass roll out - copy the zip and the boinc install onto each box, etc

c) even simpler startup - make a website that would create you a personalized download file. You'd register with rosetta first, then go to the custom downloads page on the rosetta website (hopefully still logged in from registration, if not then you'd log in again). The custom download page would build you a personalised install by using the log in cookie to generate the account_ file, and add that file to the normal download.

d) that custom download can also be copied across as many boxes as you like for mass roll out

e) a cd burning website could do the same, but burn a custom cd and then post it to the new user. Like most cds containing free software I'd expect a small charge to cover cost & postage.

Just a thought + sorry if it has been thunk before

River~~

---

Good idea!
Mass roll-out is always good to have =)

Do you think something similar could be done with the host ID? I know this one is a bit tricky, but I've been thinking about burning Knoppix liveCDs... then of course, I'd like to be able to reboot the machine if need be, and "only" loose the workunits... It would be a pretty good way to easily make dedicated crunshers...

- trib'

---

A few tests show that these are the only lines that need be included in the account_ file for it to work:

- <account>
<master_url>https://boinc.bakerlab.org/rosetta/</master_url>
<authenticator>fakefakefakefakefkaefakefakefake</authenticator>
<project_name>rosetta@home</project_name>
</account>

If you create this file in an empty c:/"program files"/boinc folder, and then install boinc, when the program starts it connects to rosetta and then expands the file appropriately.

My suggestions:

a) simple startup - this small file could be sent as a zipped attachemnt to the mail message you get to confirm registration. The zip would auo-un-zip to c:/"program files"/boinc by default (or possibly pick up one of the filenames stored in the registry?). People would be told, click this zip file then click on the boinc install

b) mass roll out - copy the zip and the boinc install onto each box, etc

c) even simpler startup - make a website that would create you a personalized download file. You'd register with rosetta first, then go to the custom downloads page on the rosetta website (hopefully still logged in from registration, if not then you'd log in again). The custom download page would build you a personalised install by using the log in cookie to generate the account_ file, and add that file to the normal download.

d) that custom download can also be copied across as many boxes as you like for mass roll out

e) a cd burning website could do the same, but burn a custom cd and then post it to the new user. Like most cds containing free software I'd expect a small charge to cover cost & postage.

Just a thought + sorry if it has been thunk before

River~~

If you look in the boinc source files you'll notice the BBC-CCE and a gridrepublic coding there as well.

You could build you client modifying the BBC-CCE, OR gridrepublic.
BBC-CEE is an example of dedicating and branding it to one project.
Gridrepublic is or will be an example of using branding and account managment.

*This maybe of use for the people at looking for Rosetta recruitment.

But if you're doing it for yourself using microsoft ORCA to include the file you mention (and any other you would like) into Windows installation files.
For linux and MAC ??. (mass roll out)

---

Team mauisun.org

Good idea!
Mass roll-out is always good to have =)

Do you think something similar could be done with the host ID? I know this one is a bit tricky, but I've been thinking about burning Knoppix liveCDs... then of course, I'd like to be able to reboot the machine if need be, and "only" loose the workunits... It would be a pretty good way to easily make dedicated crunshers...

- trib'

Why not use one of the distro's that writes back to the CDRW/DVDRW you boot from? That way you'll not loose anything other than in a crash (they write back on shut down all changes afaik)

---

Team mauisun.org

Yes, this tiny little file is a key part of making an easy to install CD. As you point out, it's the fact that it's unique to each user that makes it tricky. I like the idea of driving it's creation from the website. Perhaps it could be incorporated in to the account information page, so it would have choices for "Change email address", "Change password", "Download Rosetta startup file".

I have considered making a single "Welcome" user account, and burning CDs with that on them. If you want, you change it (actually, I guess you'd detach and attach with your own ID), if not, you're still crunching with a much simpler setup. Problem is support. You can't tell WHO this user with problems is. And they have no ID to post on the boards with.

I've considered having teams create their own "Welcome" user account which would already be a member of their team as well, but then you end up without control of the CD mastering that's going on. But, how much control is there now?

========= Caution: Windows-oriented statements ahead (ya gotta start somewhere)

But lately, I'm thinking that it would be best to create a very simple little installation program. This would be the install portion of the autorun program on an easy to install CD. It prompts you for the install directory, your EMail address, an optional team number you wish to join (perhaps written on front of CD jacket), it then uses the RPCs to the Rosetta site to create your account for you (which returns the key), it then builds the account_file in your install directory and installs both BOINC and Rosetta apps.

This would allow a single CD install image to be used (at least until new versions of BOINC and/or Rosetta are released, then a refresh would be required), and a single very simple prompt screen to fill out to get everything done. And, as I always point out, once this little installer program exists, it can be downloaded rather than installed via CD. It could also check your PC to warn (not prevent) you if it doesn't meet the project minimum requirements.

If the CD includes BOINC and Rosetta, then even with dial-up you are just 10 minutes away from crunching your first R@H WU.

===================
I note in the Rosetta license agreement it says:

Distribution

There is no charge for Rosetta.
Distribution of Rosetta is prohibited.

So, I believe this would have to be changed before an easy to install CD could be created.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Distribution

There is no charge for Rosetta.
Distribution of Rosetta is prohibited.

So, I believe this would have to be changed before an easy to install CD could be created.

This is an interesting one,
You may not use the data received or obtained by Rosetta in any way for any purpose.
It implies if you've run Rosetta@Home you'll not be able to access their findings (even though it's suppose to be free for all acedemics etc..)

;-)

---

Team mauisun.org

Why not use one of the distro's that writes back to the CDRW/DVDRW you boot from? That way you'll not loose anything other than in a crash (they write back on shut down all changes afaik)

That's correct, but then you restrict the possible user base to people having CD/DVD-rw drives. Theses are getting pretty common, I agree, but... We should probably target a userbase as large as possible... isn't it?

I believe it would be good to have a CD to hand out to people, so that they could just pop it in their CD drive, and the client would start crunshing for them...
Something dead simple (...for users ;) )

We could also "revert" the problem, by putting a unique ID per CD, and then have a web-managed database to map theses ID's to users? Like... we pre-setup a boinc client on a CD (windows oriented in the first place), that runs from it's folder (no access to registry keys or whatever) with autorun?

There is a "portable firefox" version that works just this way, I take it the overall concept could be applied to a BOINC client as well...

This would allow us to advertize Rosetta as being dead simple to set up: just put the CD in your drive, and let it do the rest. Once you're back to your computer, stop the program, take the CD out, and you're done.

Add to that that it would then be possible to mass print CDs with a nice packaging for a small fee: companies would easily buy them to give out to clients and stuff. My company would include a rosetta CD with PCs we sell, for example. Sort of like Ubuntu's shipIt service... It works very well!

- trib'

Edit: I just read about the distribution legal problems... wouldn't that be worked out if bakerlab itself hosted the "order a CD" system? They would be shipped (and burned) through some other company though, I don't know what the legal implication for that is... but I'm sure it could be worked out if this idea gets live.

---

You may not use the data received or obtained by Rosetta in any way for any purpose.

I believe the intent is that you don't use the information before the project has reviewed it and confirmed it's significance. I mean you might crunch a model with a great score, but if it's later determined that there was an error in the scoring mechanism, then you might be out running around boasting (to a big pharma company?) about something that is not what it appears to be.

In other words, the results of the project are to be delivered only by the project team.

If taken literally, I can't crunch a WU, because that is a "use" of data received.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

You may not use the data received or obtained by Rosetta in any way for any purpose.

I believe the intent is that you don't use the information before the project has reviewed it and confirmed it's significance. I mean you might crunch a model with a great score, but if it's later determined that there was an error in the scoring mechanism, then you might be out running around boasting (to a big pharma company?) about something that is not what it appears to be.

In other words, the results of the project are to be delivered only by the project team.

If taken literally, I can't crunch a WU, because that is a "use" of data received.

I think this relates to the Work Units, and the software that the project gives you. They do not want some corporate entity, capturing the Work Units and applications and using them for what ever other purpose. That statement gives them a way to stop it if it occurs. The actual folded protein results are freely available for use by other researchers, they are published and are made available to individuals like all of us.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact