New CSRosetta toolbox

[Anonymous]

Hi,

I am working for one of the labs, I have been making changes to CSRosetta toolbox like making it compatible with latest versions of Rosetta and would like our lab dir be added into the commons repo. I did not know who to contact. I can give more details about the lab, changes and so on.

Thanks.

[Anonymous]

If you’re talking about adjustments to the separate CSRosetta scripts, the ones downloaded from http://csrosetta.chemistry.ucsc.edu/  (or the old csrosetta.org site) – versus software downloaded through the rosettacommons.org site – those scripts are currently being maintained by Nik Sgourakis a UC Santa Cruz (http://niksgourakis.chemistry.ucsc.edu/).  He would be the one to contact about contributions.

[Anonymous]

If you’re talking about adjustments to the separate CSRosetta scripts, the ones downloaded from http://csrosetta.chemistry.ucsc.edu/  (or the old csrosetta.org site) – versus software downloaded through the rosettacommons.org site – those scripts are currently being maintained by Nik Sgourakis a UC Santa Cruz (http://niksgourakis.chemistry.ucsc.edu/).  He would be the one to contact about contributions.

[Anonymous]

If you’re talking about adjustments to the separate CSRosetta scripts, the ones downloaded from http://csrosetta.chemistry.ucsc.edu/  (or the old csrosetta.org site) – versus software downloaded through the rosettacommons.org site – those scripts are currently being maintained by Nik Sgourakis a UC Santa Cruz (http://niksgourakis.chemistry.ucsc.edu/).  He would be the one to contact about contributions.

[Anonymous]

Hi,

I work at his lab. The idea is to make one universal copy of CSRosetta toolbox available. Now there is one copy here: https://github.com/RosettaCommons/demos/tree/master/public/replica_docking/csrosetta3. I am not sure of the purpose of this. There is another one on the site you mention, the UCSC site (which is of course the one I have been working on.). So, to avoid confusions among all these various copies, we want to have one repo that contains the toolbox and everyone points to that. Which will be maintained/updated going further.

[Anonymous]

Hi,

I work at his lab. The idea is to make one universal copy of CSRosetta toolbox available. Now there is one copy here: https://github.com/RosettaCommons/demos/tree/master/public/replica_docking/csrosetta3. I am not sure of the purpose of this. There is another one on the site you mention, the UCSC site (which is of course the one I have been working on.). So, to avoid confusions among all these various copies, we want to have one repo that contains the toolbox and everyone points to that. Which will be maintained/updated going further.

[Anonymous]

Hi,

I work at his lab. The idea is to make one universal copy of CSRosetta toolbox available. Now there is one copy here: https://github.com/RosettaCommons/demos/tree/master/public/replica_docking/csrosetta3. I am not sure of the purpose of this. There is another one on the site you mention, the UCSC site (which is of course the one I have been working on.). So, to avoid confusions among all these various copies, we want to have one repo that contains the toolbox and everyone points to that. Which will be maintained/updated going further.

[Anonymous]

If you’re in a RosettaCommons lab, these sorts of internal organization questions are better asked on the Rosetta developer’s email list. (Only a subset of the people who are active there are active on the forums here.)

That said, the version in the demos repository is there just to support that particular demo (replica docking), it’s not intended as a general use resource. One of the reasons for the duplication is that the CSRosetta toolbox scripts are currently hosted outside the main Rosetta repositories, and hence are not otherwise availible with a standard Rosetta download. If you’re looking to centralize the scripts into a single, canonical location, then you might want to consider adding it to the tools/ repository that gets maintained and distributed with the rest of Rosetta. — Though I don’t know the full history of the CSRosetta toolbox, so there might be an argument for keeping it separate. That’s something Nik will have to decide on.

[Anonymous]

If you’re in a RosettaCommons lab, these sorts of internal organization questions are better asked on the Rosetta developer’s email list. (Only a subset of the people who are active there are active on the forums here.)

That said, the version in the demos repository is there just to support that particular demo (replica docking), it’s not intended as a general use resource. One of the reasons for the duplication is that the CSRosetta toolbox scripts are currently hosted outside the main Rosetta repositories, and hence are not otherwise availible with a standard Rosetta download. If you’re looking to centralize the scripts into a single, canonical location, then you might want to consider adding it to the tools/ repository that gets maintained and distributed with the rest of Rosetta. — Though I don’t know the full history of the CSRosetta toolbox, so there might be an argument for keeping it separate. That’s something Nik will have to decide on.

[Anonymous]

If you’re in a RosettaCommons lab, these sorts of internal organization questions are better asked on the Rosetta developer’s email list. (Only a subset of the people who are active there are active on the forums here.)

That said, the version in the demos repository is there just to support that particular demo (replica docking), it’s not intended as a general use resource. One of the reasons for the duplication is that the CSRosetta toolbox scripts are currently hosted outside the main Rosetta repositories, and hence are not otherwise availible with a standard Rosetta download. If you’re looking to centralize the scripts into a single, canonical location, then you might want to consider adding it to the tools/ repository that gets maintained and distributed with the rest of Rosetta. — Though I don’t know the full history of the CSRosetta toolbox, so there might be an argument for keeping it separate. That’s something Nik will have to decide on.

[Author]

Posts