Hi Rosetta researchers,

I was curious about what the DRH_Curve jobs are modeling? There seems to be an endless stream of them for the past month or two.

Do these jobs all belong to one person? Are they all looking at a particular protein / family of proteins, or a particular type of situation or..? Just curious.

---

**38 cores crunching for R@H on behalf of cancercomputer.org - a non-profit supporting High Performance Computing in Cancer Research

Do these jobs all belong to one person? Are they all looking at a particular protein / family of proteins, or a particular type of situation or..? Just curious.

We seem to get very little information about what we are doing. Folding, for example, gives a description of each type of work unit. I would hope that they answer your question.

---

I would hope that they answer your question.

+1

---

I was curious about what the DRH_Curve jobs are modeling? There seems to be an endless stream of them for the past month or two.

Are months that, on android devices, we are crunching "cispro_backbone_".
What is it?

---

And, as usual, no answer....

---

Thanks. That is a really excellent explanation, from theory to application. It means a lot for what we are doing.

---

Thank you. It's very interesting. My smartphone is crunching...

---

Hi Timo,

The DRH_Curve jobs all belong to me. I am a graduate student in the Baker lab working to design new proteins that can be used as molecular switches. These switches could be used as tools in other labs around the world to control and study the interactions between natural proteins. There are also potential applications of these protein switches to control cell therapeutics such as Car-T cells which are being developed in other labs to teat cancer.

The number of possible protein structures that can be generated on a computer is extremely large and for each of these possible structures, there can be a very large number of possible sequences that we expect to fold to that particular structure. This is where Rosett@home comes in. After we design a particular protein structure with a particular amino acid sequence, we use Rosett@home to check whether that sequence is likely to fold to the desired structure. This allows us to eliminate "bad" designs and do further work with the "good" designs. These good designs are then encoded in a DNA sequence, which is put into a bacterium or yeast to produce the protein in our wet lab, allowing us to characterize the true structure of the protein and see how that matches with our computational models.

Sorry for the high level description of my work which glosses over a lot of background and details. If you have any questions or want more detail, please let me know.

Best,
Derrick

After we design a particular protein structure with a particular amino acid sequence, we use Rosett@home to check whether that sequence is likely to fold to the desired structure. This allows us to eliminate "bad" designs and do further work with the "good" designs. These good designs are then encoded in a DNA sequence, which is put into a bacterium or yeast to produce the protein in our wet lab, allowing us to characterize the true structure of the protein and see how that matches with our computational models.

That is the key point that allows us to see what good Rosetta does. A high-level description is good enough for most of us. We can carry on from there.

---