Hello,
About those error messages, possibly there are some parameters that the parsing code does not understand (although I’m not sure that would be the only reason those error messages would be given).
If the referencing (etc.) looks good under the Experiment —> Spectra dialog then those error messages should be ok to ignore.
The code that parses Bruker data automatically sets the scaling based on what is in the the Bruker files. (Bruker have a scaling because they store the data as integers not floats.) The heights and volumes quoted should take that into account (I think!). I guess it’s possible to end up with different scales for different experiments, although others could possibly comment better on that.
If the heights are significantly different then that is likely correct (and significant). If it’s only the volumes which are significantly different then possibly the volume fitting has gone bad.
Wayne
On 7 Mar 2015, at 14:10, Andras Czajlik <[log in to unmask]> wrote:
> Hello,
>
> Nowadays I always get the following error message when I open a new Bruker processed spectrum in analysis:
>
> Error converting '<>' to float: set to 0.0
> ...
> Error converting '<>' to float: set to 0.0
>
>
> Although the spectra seem to be ok, I wonder what it does mean. Could it cause problems with any spectral parameter?
>
>
> I have two further questions:
>
> 1. in the Experiment:Spectra:Spectra menu there is an option: scale. The spectra are automatically scaled by CCPN. Can you tell me what the scaling depends on? Furthermore does it modify the peak intensity values (peak heights) calculated by CCPNMR or any other parameters? Finally is there any reason to get different scales for HSQC spectra of a protein recorded with the same parameters?
>
> 2. Is there any CCPNMR related error which could cause to get significantly (20-30%) different intensity values for HSQC spectra recorded with the same parameters?
>
> Thanks,
> Andras
|