For the input of data into relax, the difference between spaces, tabs,
and other whitespace characters doesn't matter. relax will treat all
whitespace the same. And the number of whitespace characters in a row
is inconsequential as well. As long as the columns are clearly
separated by whitespace, everything should be read into relax without
problem.
As for relax scripts, then the rules of python apply. If tabs are
used in the script, then all parts of the script should be indented
using tabs. If 4 spaces are used, then everything should be 4 spaces.
The same with 8 spaces. In the sample scripts which are indented, 4
spaces are used for the indentation rather than a tab (a Python
convention). Therefore if a line is added which uses a tab, then you
are likely to run into problems. In reality, only the current
indented block needs to be consistent. To save headaches when using
the sample scripts, using 4 spaces would be best.
I hope that helps,
Edward
On 9/29/06, Alexandar Hansen <viochemist@xxxxxxxxx> wrote:
Hello,
From experience, a number of programs often have problems with tabs, and
spaces, and perfect columns. (ie reading in PDBs can be a disaster if there
are tabs or the column is one space off on occasion.) Using modelfree4, I
ran into a problem of giving a gamma value too much precision once. Is it
known if relax has these problems?
Alex Hansen
_______________________________________________
relax (http://nmr-relax.com)
This is the relax-users mailing list
relax-users@xxxxxxx
To unsubscribe from this list, get a password
reminder, or change your subscription options,
visit the list information page at
https://mail.gna.org/listinfo/relax-users
Re: Tabs and spaces in inputs