mailRe: [task #6438] To relax the BMRB.


Others Months | Index by Date | Thread Index
>>   [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Header


Content

Posted by Eldon Ulrich on November 04, 2009 - 18:07:
Hi,

Quick response regarding items 7 and 9. I just took your example file and replaced the '?' with the file name for this tag:

   _Chem_shift_anisotropy.Data_file_name OMP_NMR_STAR_2009_10_28

I then uploaded the file into ADIT-NMR and the field for the 'Deposited data file name' was populated and had a green check mark. This should resolve the problem of depositors needing to fill in this field and should work for the Het NOE saveframe, as well.

Cheers,
Eldon


Edward d'Auvergne wrote:
Hi,

Thank you for all the info.  My responses are also below.


2009/11/3 Eldon Ulrich <elu@xxxxxxxxxxxxx>:

For testing deposition against the new dictionary, is there a
non-production machine that could be used?  If I can submit and check
against your changes, this should speed up development.  I have made a
few improvements since the file at
https://gna.org/support/download.php?file_id=7140, and using the new
file, a few of the issues identified by ADIT-NMR include (I'll number
these for future reference):
ADIT-NMR is a relatively complex (several components and lots of legacy
code) system. Updating an instance of the system with a new dictionary
requires a bit of work that is carried out by Steve Mading in the group.
Other parts of the system also are under development to handle mandatory
chemical shift deposition with PDB depositions. Unfortunately, this all
makes it difficult to create a unique test system for this project that I
could keep up to date with changes.

Oh.  Hopefully we can work to get the new saveframes finalised and
then added to the production system without too many problems.  Maybe
I can develop these in relax first, and then once the NMR-STAR file
with this data is ready then it be added to ADIT-NMR?


1.  The author info is missing - this can probably be added by the
submitter afterwards.

That would be the normal procedure.

Ok, relax will leave this empty.


2.  The entity entry is not complete - relax needs to add a few
additional tags for this.

OK

I think this is now complete in the new file attached to the task at
https://gna.org/task/index.php?6438
(https://gna.org/support/download.php?file_id=7171).


3.  In the Molecular assembly saveframe supergroup 3, three saveframes
appear to be required - Molecular assembly, Natural source, and
Experimental source.  Should relax create these?

Natural source and experimental source would normally be filled in by the
depositor. For simple single polymer systems, the molecular assembly might
be filled in by relax. But if the system is more complex (ligands, multiple
polymer, etc.), it might be easier to have the depositor enter the
information.

For the entity saveframe, relax is simply depositing the data loaded
into relax as spin systems - i.e. not the entire information from the
PDB file.  Therefore sections and components not used in the
model-free analysis are excluded from the NMR-STAR file.  This is
because structural information could actually be absent in an
analysis.  If there are missing amino-acids or nucleic acids, how
should relax handle this in _Entity.Polymer_seq_one_letter_code?  For
completeness of the model-free data storage, this is all that is
really needed.  If you would like more, I can add it.  I might be able
to change this current behaviour by dumping all the PDB info - if
available - but would this be a useful aim?


4.  For the Experimental_descriptions saveframe supergroup, only the
software saveframe is being created by relax.  I have used $sample_1
and $conditions_1 in the other saveframes so these exist but are
empty.  Should relax do more with this?

This should be all you need to do. Sample and conditions information is
usually hidden in a lab book and the depositor has to dig it out and enter
it at the time of deposition.

Ok, that makes it easier.

Can I do something similar with the file name in point 7?  I.e. say
$file_1 and then have only one place where you specify that all the
data comes from the same file?  I would really like to remove this
step from the user, if possible, because it is so obvious.  The only
reason for having the user specify that the file that created the
saveframe plus contains the data is the file that created the
saveframe would be legacy code, so I'm looking for a workaround that
can be implemented in relax.


5.  _Software.Version is only allowed to be 31 characters.  For
non-released software (a number of users utilise the repository code
rather than released versions) I would like to have something like
"repository checkout r9832
svn+ssh://bugman@xxxxxxxxxxx/svn/relax/branches/bmrb".  Can this be
extended into VARCHAR(127)?

This has been changed to VARCHAR(127).

Thank you.  Does this take a while to reach the production server?
I'm still having the error message "*Invalid input: should be 31
characters or less".


6.  The citations section of the software saveframe appears to be
missing.  Is this not metadata?

I will need to do more investigating on this one. I do not know of anyone
who has provided this information and there is probably a flag set somewhere
that is causing the problem.

Ok.  I would like to use this tag category as it is a tiny investment
for relax to implement and it makes the file more complete.  It is
also automatic from a user's perspective so entails zero cost,
timewise.  It will also encourage users to add the relevant references
for the implementation of their analysis next to these standard
program references.


7.  The chemical shift anisotropy saveframe requires the deposited
data file name.  I've tried supplying '?', but nothing I do appears
remove this issue from the user.  Is there some way I can specify that
it all comes from the same file?

I uploaded your temp_bmrb file and then entered it as the deposited data
file name in both the CSA and the Het NOE fields and this was accepted and
the green check marks appeared.

As above, I would like to remove this step from the user if at all
possible.  I would like to have as many green check marks as possible
throughout the deposited data in the ADIT-NMR system with all tags
ticked (excluding those that the user needs to add additional
information).  My aim would be to have green check marks the following
saveframe categories, as the user shouldn't really change anything
there:

Citations.
Molecular_assembly (well most of this super group).
Software descriptions in Experimental_descriptions.
NMR_parameters.
Kinetic_data.

relax can supply 100% of the relevant information in these sections
(though Citations and Molecular assembly could be added to during
deposition).


8.  The chemical shift anisotropy saveframe is asking for the NMR
experiment used.  You usually set this to -160 or -172 ppm in
model-free analyses.  Can this be made non-compulsory or at least put
a tick in the ADIT-NMR system for it.

Data had to be collected from an experiment run on an NMR spectrometer. One
or more NMR experiments like a '1H-15N het NOE' experiment needs to be
entered by the depositor and linked to the sample, sample conditions, and
NMR spectrometer used. This is filled in in the 'NMR experiments and
samples' section after the Sample, Sample conditions, and NMR spectrometer
list have been completed. The deposition system is asking for the name of an
NMR experiment not for parameters.

I can probably add this for the het NOE, R1, and R2 but in the case of
the CSA values used, there may be no NMR experiment involved.  Almost
100% of model-free analyses (and SRLS and reduced spectral density
mapping) fix the CSA value of all similar spins to one value.  For
model-free analysis, this is now almost always -172 ppm.  Although
almost never used, the source of CSA values could be experimental,
from the literature, by direct calculation, or maybe even direct
fitting as a parameter of the model (relax allows for all of these
scenarios).  Therefore there could be a per spin CSA value utilised
that comes from no NMR experiment.  It can be experimental data, a
permanently fixed value, or a model parameter.


9.  Save as 6. for the heteronuclear NOE saveframes.

Not sure about this one.

Sorry, I meant "Same as 7. for the heteronuclear NOE saveframes."  The
file name needs to be specified, and I can't work out how relax can do
this automatically.


10.  _Heteronucl_NOE_list.Heteronuclear_NOE_val_type appears to be
compulsory in ADIT-NMR but not in the dictionary at

http://www.bmrb.wisc.edu/dictionary/3.1html_frame/frame_HeteronuclNOEList.html#_Heteronucl_NOE_list.Heteronuclear_NOE_val_type.

This information is not available from legacy data and so in the dictionary
the field is allowed to have a null value, however it was felt that the NOE
val type should be a mandatory item in the deposition system so that this
information would be collected for all future depositions.

Ok, I'll make sure that relax forces the user to input this information.


11.  I'm not sure what _Heteronucl_NOE_list.NOE_ref_val is or why it
is compulsory.

It is no longer compulsory. I think it was intended as an intensity value
that is used to normalize the data or as a reference to compare with other
values in the spectrum.

Should I set this to something like 1, or wait for the production
system to accept a null value.


Ok, I'll update the relax output
_Heteronucl_NOE_list.Heteronuclear_NOE_val_type.  I eagerly await to
read your notes from our meeting at the 2009 ENC, so I can add to
relax the new saveframes necessary to hold all information in a
model-free analysis.

Cheers,

Edward



Related Messages


Powered by MHonArc, Updated Thu Nov 05 11:40:11 2009