JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CCP4BB Archives


CCP4BB Archives

CCP4BB Archives


CCP4BB@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CCP4BB Home

CCP4BB Home

CCP4BB  October 2011

CCP4BB October 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

To archive or not to archive, that's the question!

From:

Gerard DVD Kleywegt <[log in to unmask]>

Reply-To:

Gerard DVD Kleywegt <[log in to unmask]>

Date:

Fri, 28 Oct 2011 23:02:46 +0200

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (205 lines)

Hi all,

It appears that during my time here at Cold Spring Harbor, I have missed a 
small debate on CCP4BB (in which my name has been used in vain to boot).

I have not yet had time to read all the contributions, but would like to make 
a few points that hopefully contribute to the discussion and keep it with two 
feet on Earth (as opposed to La La Land where the people live who think that 
image archiving can be done on a shoestring budget... more about this in a 
bit).

Note: all of this is on personal title, i.e. not official wwPDB gospel. Oh, 
and sorry for the new subject line, but this way I can track the replies more 
easily.

It seems to me that there are a number of issues that need to be separated:

(1) the case for/against storing raw data
(2) implementation and resources
(3) funding
(4) location

I will say a few things about each of these issues in turn:

-----------

(1) Arguments in favour and against the concept of storing raw image data, as 
well as possible alternative solutions that could address some of the issues 
at lower cost or complexity.

I realise that my views carry a weight=1.0 just like everybody else's, and 
many of the arguments and counter-arguments have already been made, so I will 
not add to these at this stage.

-----------

(2) Implementation details and required resources.

If the community should decide that archiving raw data would be scientifically 
useful, then it has to decide how best to do it. This will determine the level 
of resources required to do it. Questions include:

- what should be archived? (See Jim H's list from (a) to (z) or so.) An 
initial plan would perhaps aim for the images associated with the data used in 
the final refinement of deposited structures.

- how much data are we talking about per dataset/structure/year?

- should it be stored close to the source (i.e., responsibility and costs for 
depositors or synchrotrons) or centrally (i.e., costs for some central 
resource)? If it is going to be stored centrally, the cost will be 
substantial. For example, at the EBI -the European Bioinformatics Institute- 
we have 15 PB of storage. We pay about 1500 GBP (~2300 USD) per TB of storage 
(not the kind you buy at Dixons or Radio Shack, obviously). For stored data, 
we have a data-duplication factor of ~8, i.e. every file is stored 8 times (at 
three data centres, plus back-ups, plus a data-duplication centre, plus 
unreleased versus public versions of the archive). (Note - this is only for 
the EBI/PDBe! RCSB and PDBj will have to acquire storage as well.) Moreover, 
disks have to be housed in a building (not free!), with cooling, security 
measures, security staff, maintenance staff, electricity (substantial cost!), 
rental of a 1-10 Gb/s connection, etc. All hardware has a life-cycle of three 
years (barring failures) and then needs to be replaced (at lower cost, but 
still not free).

- if the data is going to be stored centrally, how will it get there? Using 
ftp will probably not be feasible.

- if it is not stored centrally, how will long-term data availability be 
enforced? (Otherwise I could have my data on a public server until my paper 
comes out in print, and then remove it.)

- what level of annotation will be required? There is no point in having 
zillions of files lying around if you don't know which 
structure/crystal/sample they belong to, at what wavelength they were 
recorded, if they were used in refinement or not, etc.

- an issue that has not been raised yet, I think: who is going to validate 
that the images actually correspond to the structure factor amplitudes or 
intensities that were used in the refinement? This means that the data will 
have to be indexed, integrated, scaled, merged, etc. and finally compared to 
the deposited Fobs or Iobs. This will have to be done for *10,000 data sets a 
year*... And I can already imagine the arguments that will follow between 
depositors and "re-processors" about what software to use, what resolution 
cut-off, what outlier-rejection criteria, etc. How will conflicts and 
discrepancies be resolved? This could well end up taking a day of working time 
per data set, i.e. with 200 working days per year, one would need 50 *new* 
staff for this task alone. For comparison: worldwide, there is currently a 
*total* of ~25 annotators working for the wwPDB partners...

Not many of you know that (about 10 years ago) I spent probably an entire year 
of my life sorting out the mess that was the PDB structure factor files 
pre-EDS... We were apparently the first people to ever look at the tens of 
thousands of structure factor files and try to use all of them to calculate 
maps for the EDS server. (If there were others who attempted this before us, 
they had probably run away screaming.) This went well for many files, but 
there were many, many files that had problems. There were dozens of different 
kinds of issues: non-CIF files, CIF files with wrong headers, Is instead of 
Fs, Fcalc instead of Fobs, all "h" equal to 0, non-space-separated columns, 
etc. For a list, see: http://eds.bmc.uu.se/eds/eds_help.html#PROBLEMS

Anyway, my point is that simply having images without annotation and without 
reprocessing is like having a crystallographic kitchen sink (or bit bucket) 
which will turn out to be 50% useless when the day comes that somebody wants 
to do archive-wide analysis/reprocessing/rerefinement etc. And if the point is 
to "catch cheaters" (which in my opinion is one of the weakest, least-fundable 
arguments for storage), then the whole operation is in fact pointless without 
reprocessing by a "third party" at deposition time.

-----------

(3) Funding.

This is one issue we can't really debate - ultimately, it is the funding 
agencies who have to be convinced that the cost/benefit ratio is low enough. 
The community will somehow have to come up with a stable, long-term funding 
model. The outcome of (2) should enable one to estimate the initial investment 
cost plus the variable cost per year. Funding could be done in different ways:

- centrally - e.g., a big application for funding from NIH or EU

- by charging depositors (just like they are charged Open Access charges, 
which can often be reclaimed from the funding agencies) - would you be willing 
to pay, say, 5000 USD per dataset to secure "perpetual" storage?

- by charging users (i.e., Gerard Bricogne :-) - just kidding!

Of course, if the consensus is to go for decentralised storage and a DOI-like 
identifier system, there will be no need for a central archive, and the 
identifiers could be captured upon deposition in the PDB. (We could also check 
once a week if the files still exist where they are supposed to be.)

-----------

(4) Location.

If the consensus is to have decentralised storage, the solution is quite 
simple and very cheap in terms of "centralised" cost - wwPDB can capture 
DOI-like identifiers upon deposition and make them searchable.

If central storage is needed, then there has to be an institution willing and 
able to take on this task. The current wwPDB partners are looking at future 
funding that is at best flat, with increasing numbers of depositions that also 
get bigger and more complex. There is *no way on earth* that wwPDB can accept 
raw data (be it X-ray, NMR or EM! this is not an exclusive X-ray issue) 
without *at least* double the current level of funding (and not just in the US 
for RCSB, but also in Japan for PDBj and in Europe for PDBe)! I am pretty 
confident that this is simply *not* going to happen.

[Besides, in my own humble opinion, in order to remain relevant (and 
fundable!) in the biomedical world, the PDB will have to restyle itself as a 
biomedical resource instead of a crystallographic archive. We must take the 
structures to the biologists, and we must expand in breadth of coverage to 
include emerging hybrid methods that are relevant for structural cell (as 
opposed to molecular) biology. This mission will be much easier to fund on 
three continents than archiving TBs of raw data that have little or no 
tangible (i.e., fundable) impact on our quest to find a cure for various kinds 
of cancer (or hairloss) or to feed a growing population.]

However, there may be a more realistic solution. The role model could be NMR, 
which has its own global resource for data storage in the BMRB. BMRB is a 
wwPDB partner - if you deposit an NMR model with us, we take your ensemble 
coordinates, metadata, restraints and chemical shifts - any other NMR data 
(including spectra and FIDs) can subsequently be deposited with BMRB. These 
data will get their own BMRB ID which can be linked to the PDB ID.

A model like this has advantages - it could be housed in a single place, run 
by X-ray experts (just as BMRB is co-located with NMRFAM, the national NMR 
facility at Madison), and there would be only one place that would need to 
secure the funding (which would be substantially larger than the estimate of 
$1000 per year suggested by a previous poster from La La Land). This could for 
instance be a synchrotron (linked to INSTRUCT?), or perhaps one of the 
emerging nations could be enticed to take on this challenging task. I would 
expect that such a centre would be closely affiliated with the wwPDB 
organisation, or become a member just like BMRB. A similar model could also be 
employed for archiving raw EM image data.

-----------

I've said enough for today. It's almost time for the booze-up that kicks off 
the PDB40 symposium here at CSHL! Heck, some of you who read this might be 
here as well!

Btw - Colin Nave wrote:

"(in increasing order of influence/power do we have the Pope, US president, 
the Bond Market and finally Gerard K?)"

I'm a tad disappointed to be only in fourth place, Colin! What has the Pope 
ever done for crystallography?

--Gerard

******************************************************************
                            Gerard J. Kleywegt

       http://xray.bmc.uu.se/gerard   mailto:[log in to unmask]
******************************************************************
    The opinions in this message are fictional.  Any similarity
    to actual opinions, living or dead, is purely coincidental.
******************************************************************
    Little known gastromathematical curiosity: let "z" be the
    radius and "a" the thickness of a pizza. Then the volume
             of that pizza is equal to pi*z*z*a !
******************************************************************

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager