CCP4 web logo CCP4i: Graphical User Interface
Tutorial 1

next button top button

Setting up and getting organised

Before you start

For this first tutorial, which is most useful for first-time users of the Interface, you only need what is described in the Introduction:
a directory called "ccp4itut".

It is also advisable to
start a Netscape session by typing netscape (you may have to specify a version, e.g. netscape30 or netscape4.05)
before entering the Interface.

Directory selection

CCP4i expects users to keep all the files relating to one project in one directory called 'the Project directory'. The Interface will create a sub-directory of the project directory, called "CCP4_DATABASE", in which it keeps its own files. You are free to decide what exactly is one project, but it should probably be one structure solution, and you may have more than one project in progress at one time.
The Interface also has the concept of directory aliases, which work similarly to Unix environment variables: you provide a short one-word alias for the long pathnames of project directories and also, optionally, for other directories you use regularly.

Hints on using Interface windows:
The "Directories&ProjectDir" window may look a little confusing at first. Here are some hints to features seen throughout the Interface -
try them out
while going through the actual tutorial.

If you are using the Interface for the first time If this is not the first time you are using the Interface
1 Upon typing ccp4i the Interface will
bring up the Main Window automatically
or (if your shell setup is such)
bring up the shape of the Main Window which you can place on your screen where you want it.
2 A window called "Directories and Project Directory" will come up in the same way. The Interface has created a file "directories.def" in the directory .CCP4/unix/ (or .CCP4/windows/, where .CCP4/ is a subdirectory of the user's home directory), where it will store your directory choices/aliases. There already is a file "directories.def" in your .CCP4/unix/ and/or .CCP4/windows/ directory.
Click on the Directories&ProjectDir button
near the top right of the Main Window to bring up the "Directories and Project Directory" window.
3 Click in the field "Project",
type ccp4itut

as your first alias,
and make it point to ~/ccp4itut
in the field "uses directory:".
See above for hints on how to do this.
Click on Add project, type
ccp4itut and make it point to
~/ccp4itut
4 The Interface has entered this directory in the
'Project for this session of CCP4Interface' pop-up menu.
5 Since there is only one possible Project directory, this is automatically installed for this session. Click on the pop-up menu button
for the 'Project for this session' and select ccp4itut
6 Click on Apply
7 The Interface brings up another window, called "Create". Read this carefully. The Interface is installing "ccp4itut" as your Project Directory, and wants to create a database directory for this, where it will keep track of all the things you do while working on your current project.
Click on Create Directory
The Interface has created a subdirectory of "ccp4itut", called "CCP4_DATABASE".
Since you have used the Interface before, you have probably created a database before.
If not, proceed following the left-hand-side of this table.
8 Click on the Add directory alias button.
In the field "Alias:",
type rnase_exam
and make it point to
$CEXAM/rnase/

Please note that the aliases must be one word, with only alphanumeric characters and underscores. Any other character will be converted to an underscore, and you will be warned of this.
9 Click on Apply&Exit

N.B. In cases where the process the Interface is trying to perform takes a fair amount of time, a small message window will come up (either automatically, or just the shape of one you can place yourself, as before). This window tells you what the Interface is trying to do.

More information

The Interface documentation on features from this tutorial can be found at:

Viewing HTML Help Text
Directories and Project Directory
File and Directory Selection
next button top button