Edit detail for KnownBugs revision 1 of 1

changed:
-
Use the Cara Issue Tracker to get a listing of reported bugs:

http://www.cara.ethz.ch/CARA/Tracker

Another useful source of help is CARAcrashes

Here is a summary of well known bugs and their work-arounds:

* User changed a parameter but the change is not reflected in the Cara-Explorer Pane.
  This is a display update problem. Switch to another Pane  e.g. *!ResidueTypes* and then back to the Pane in question e.g. *Spectra*. The correct value should now be displayed.

* CARA crashes when reading a spectrum

  Look "here":XeasySpectraProblems for some hints and suggestions.

* CARA cannot read repository:

  <pre>unexpected character (line 1599 colume 1) error while parsing attribute</pre>

  CARA cannot open a repository if it was stored with unusual characters used in the name of a project or other objects (spectra, peaklists etc).::

   %"*ç/*![]|{}

  Just stick to alphanumerics, whitespaces, -, and _ to avoid problems

  The easy way to recover: copy the *!MyRepository.cara.bak* backup file to *!MyRepositoryBackup.cara* and open that file. If you somehow erased the backup file or if it is also corrupted, you will need to edit the repository file directly (it is xml format which makes this pretty straightforward - see EditingRepositories for more info). Note down the line number where the first error is reported in the repository. Open the repository with an editor and navigate to this line number.

  E.g. your project name was::

   Funnychars"%&&&ç*"&&"

  The line of the repository with an error reported in it (line 1599 for example) looks like::

   <project name='Funnychars*&quot;%

  Edit the line to look like::

   <project name='Funnychars'>

  save the repository to a new name and reopen it.

* CARA does not accept external calibrations

  If you change a .param file using a text editor or XEASY while CARA is running, CARA will not be aware of this change, since it stores the calibration upon loading. You will need to *replace spectrum* with itself in the Cara-explorer. Click on Spectrum, right-click *Replace Spectrum* and reselect the spectrum.

* When overwriting a spectrum with an external program, CARA may crash

  A typical situation: you retransform a spectrum with PROSA and overwrite it. Then you open MonoScope. This may lead to a crash. Since CARA uses a "map" of the spectrum for fast navigation, retransforming and overwriting the spectrum may change this map. The solution is to use the *replace spectrum* function to replace the spectrum with itself (reloading it).


* *Show folded* doesn't do anything.

  Your .param file is bad. This may happen with .param files generated using uxnmr2xeasy. Edit the .param file to set <pre>Folding in w1 ................. NO</pre> to the correct value, e.g. <pre>Folding in w1 ................. RSH</pre> and then *replace spectrum* with itself to update the spectral data in Cara. You should see the correct value for Folding in the Cara-Spectrum Explorer.

  Note that it is now possible to store the folding states for a spectrum directly in the repository. Click on the spectrum in Spectra-Explorer to expand it. Then right-click on the dimension and select "Set Folding" and select the appropriate folding mode (NONE, RSH, TPPI). Don't forget to save the repository afterwards. This Folding information is stored in the repository, NOT in the spectrum file.

* Integrator produces negative peak volumes even though the intensity is positive.

  This occurs when peaks are very close to eachother. Try to separate them, or reduce the defined peak models width. Another option is to use the "LUA":CALUA script *!CopyPeakAmpToVol.lua* to copy intensities into the volume. Store the repository afterwards and then export the peaklist. Or you can try using the Integration Method "Base Rectangle Intensity Sum" which uses a different algorithm to determine the volume.

NEXT GettingStarted

Return to FrontPage

Return to DownloadOverview