source: trunk/HELP_SOURCE/source/bad_alignment.hlp

#Please insert up references in the next lines (line starts with keyword UP)
UP      arb.hlp
UP      glossary.hlp

#Please insert subtopic references  (line starts with keyword SUB)
#SUB    subtopic.hlp

# Hypertext links in helptext can be added like this: LINK{ref.hlp|http://add|bla@domain}

#************* Title of helpfile !! and start of real helpfile ********
TITLE           Detect bad helix alignment

OCCURRENCE      ARB_EDIT4/Edit/Detect bad helix alignment

DESCRIPTION     This functions help to find poor alignment in helical regions.

                Enter the helix number(s) to examine into the first input field.
                Numbers should be separated by ','.
                You may use helix ranges like '10-12' to specify multiple helices
                or use '*' to select all helices.

                    Use the 'Jump' button behind the input field to move the cursor
                    to the (next) helix position.

                Enter the symbol(s) you want to be reported into the second input field.

                    The used helix symbols are defined by LINK{helixsym.hlp}. Click the
                    button behind the input field to configure the helix symbols.

                Press 'Calculate' to examine all species loaded in ARB_EDIT4.
                For each species this functions calculates how often any of
                the 'Detected symbols' would display under those helices listed
                behind 'Helices to examine'.

                All species which have at least one symbol displayed will be shown in
                the list subwindow. The worst species is displayed at the top.

                If a target field is selected behind "Write to database field", the result
                of the calculation is written into the target field.
                For species with zero "bad symbols" a zero value is written.
                Species not loaded into the editor are not modified, i.e. if the target field
                already exists in any such species, it will remain unchanged.
                If that seems annoying, consider deleting the field via LINK{spaf_delete.hlp}.

NOTES           None

EXAMPLES        None

WARNINGS        None

BUGS            No bugs known