@@ -10,62 +10,62 @@ The next section is [Section 3: Compile](TutorialsGeneralUsageCodeletManagementC
# Introduction #
<divalign='justify'>
The following section explains how to add applications, run Codelet Finder, and automatically create codelets. Please be sure to have read [Adding a codelet](TutorialsGeneralUsageCodeletManagementAddingACodelet) as it contains important information on file management. Codelet management is the first step in characterizing and optimizing code segments in CTI.
</div>
<br/>
<divalign='justify'>
The rest of the documentation uses the following application example: <ahref='http://wiki.codelet-tuning-infrastructure.googlecode.com/git/Test_cti_codelet_manager.tar.gz'>Test_cti_codelet_manager.tar.gz</a>.
</div>
<br/>
The user first has to create an application entry. The name and directory are provided.
# Adding an Application #
<divalign='justify'>
Codelets are created from a given application. CTI must have an entry describing the application in order to create the codelets.
</div>
</br/>
<divalign='justify'>
Before adding an application, it is recommended to build a [local repository](TutorialsGeneralUsageRepositories). The user should always perform grouped experiments inside a separate local repository.
</div>
## CTS ##
<divalign='justify'>
To import an application, click on the "Codelet management" link from the top-menu. Then, from the sub-list of the "Application" item in the left menu, select "Add an application".
The form can be completed, among other fields, by [choosing the repository](TutorialsGeneralUsageRepositories), the displayed name, the name of the application, and the full path to the directory. The path to the application is the path from the computer running CTI or CTS and not automatically the user's local machine.
</div>
<br/>
<divalign='justify'>
Once completed, the user can click on Add to finally add the application. This will make a link to the newly-created entry appear.
</div>
<br/>
<divalign='justify'>
Clicking this link will display a view, providing information about the application.
At creation, there are no codelets associated to the application. The following section presents how to create the codelets for the application using CAPS' tool called Codelet Finder(CF).
</div>
## Command-Line ##
<divalign='justify'>
Using the command-line, a user can add an application to a local repository.
The command is performed in a CTI directory, ie a cti repository init command has previously been performed in the directory. To import an application, the user must do the following:
</div>
```
$ cti repository init my_rep
The local repository is created (UID = 2f4bfcd0-7dbd-49b8-963e-8852859618ff)!
...
...
@@ -80,9 +80,9 @@ In the previous case, the application /home/users/ftalbart/test is added to the
# Creating Codelets from the Application #
<divalign='justify'>
Creating codelets automatically from the application can be done via CTS or command line. The application is compressed and sent to the target machine (supported protocols: SSH and Slurm), or the local machine. Then, CF is launched on the machine specified by the user. Finally, the codelets generated by CF are sent back to machine's user and imported into CTI.
</div>
Before the first creation, the user needs to send its SSH public key to the target machine (if the experiment is not run locally):
...
...
@@ -100,35 +100,35 @@ Then, the user can run the experiment and never has to perform the ssh-key step
Via CTS, the user must go to the created application entry and click on the "Create new codelets" button:
A new "codelet_group" entry is created each time the user invokes the "create codelets" button. By clicking on one, information about the set of codelets is retrieved:
