Storage of diffraction data: Difference between revisions

From CCP4 wiki
Jump to navigation Jump to search
B5foan (talk | contribs)
Created page with "Synchrotrons are very good at archiving all collected data. In contrast, there's no requirement for including diffraction data when submitting a structure to the PDB. Conseque..."
 
B5foan (talk | contribs)
Line 6: Line 6:


* myTardis - developed at the Australian synchrotron and [https://github.com/mytardis/mytardis downloadable as open source].
* myTardis - developed at the Australian synchrotron and [https://github.com/mytardis/mytardis downloadable as open source].
* [[iRods]] - an effort headed by the Irish Centre for High End Computing of turning iRods into a modular storage solution that can be deployed at the lab or institute level.
* [[CDR]] - an effort headed by the Irish Centre for High End Computing of turning [http://www.irods.org iRods] into a modular storage solution that can be deployed at the lab or institute level.

Revision as of 17:11, 14 March 2014

Synchrotrons are very good at archiving all collected data. In contrast, there's no requirement for including diffraction data when submitting a structure to the PDB. Consequently, the connection between structure and the underlying data is lost for all practical purposes. Some think this is a problem, but there aren't any good solutions yet.

Diffraction data storage solution

As the PDB isn't developing data storage and retrieval solution, community efforts are needed. Here are a few examples:

  • myTardis - developed at the Australian synchrotron and downloadable as open source.
  • CDR - an effort headed by the Irish Centre for High End Computing of turning iRods into a modular storage solution that can be deployed at the lab or institute level.