Worldwide ZINC: Difference between revisions
No edit summary |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
= Sites / Clusters = | = Sites / Clusters = | ||
* [[Cluster 0]] @ [[UCSF]] | * [[Cluster 0]] @ [[UCSF]] | ||
* [[Cluster 1]] @ | * [[Cluster 1]] @ UofT | ||
* [[Cluster 2]] @ [[UCSF]] | * [[Cluster 2]] @ [[UCSF]] | ||
* | * [[Cluster 3]] @ [[UCSF]] | ||
* your cluster could go here... | |||
= | {{TOCright}} | ||
Each site | |||
= Levels of affiliation = | |||
Coordination, affiliation and federation among nodes on the worldwide ZINC network are optional, and may operate at several levels | |||
== Make public cycles available == | |||
Each member of the worldwide ZINC network is asked to make a public DOCK Blaster server available, and to allow public jobs to be run. | |||
== Forked development code branches == | |||
Members and potential members of the worldwide ZINC network should participate in code and script development. Use [[github]] to fork a branch. Changes made at your site should be committed for potential re-integration into the trunk, the germ-line version of the code. | |||
== Integration of DOCK Blaster job queues == | |||
When submitting a docking job to a node on the worldwide ZINC network, the user may select a different cluster in order to get the job processed faster. | |||
== Integration of ZINC number == | |||
If you choose to host a mirror site of ZINC, we ask that you participate in the incremental updates of ZINC, and use a common numbering scheme. If you would like to participate at this level, please write us. | |||
[[Category:Sysadmin]] | [[Category:Sysadmin]] | ||
Latest revision as of 18:04, 22 September 2014
We want to foster a community of sites around the world that use our software. We would like to loosely affiliate these sites so that resources can be pooled, and improvements made at one site can be easily propagated to other sites. For this, we have started using git and github as a revision control and software distribution platform.
Sites / Clusters
Levels of affiliation
Coordination, affiliation and federation among nodes on the worldwide ZINC network are optional, and may operate at several levels
Make public cycles available
Each member of the worldwide ZINC network is asked to make a public DOCK Blaster server available, and to allow public jobs to be run.
Forked development code branches
Members and potential members of the worldwide ZINC network should participate in code and script development. Use github to fork a branch. Changes made at your site should be committed for potential re-integration into the trunk, the germ-line version of the code.
Integration of DOCK Blaster job queues
When submitting a docking job to a node on the worldwide ZINC network, the user may select a different cluster in order to get the job processed faster.
Integration of ZINC number
If you choose to host a mirror site of ZINC, we ask that you participate in the incremental updates of ZINC, and use a common numbering scheme. If you would like to participate at this level, please write us.