emoving the "\_" authored by franck.talbart@gmail.com's avatar franck.talbart@gmail.com
...@@ -220,19 +220,19 @@ When the process is finished, the codelets are automatically imported into CTI i ...@@ -220,19 +220,19 @@ When the process is finished, the codelets are automatically imported into CTI i
## CTS ## ## CTS ##
At the end of the process, Application DATA\_UID is displayed: At the end of the process, Application DATA_UID is displayed:
<p align='center'>[[img/CTS-daemon-output.png]]</p> <p align='center'>[[img/CTS-daemon-output.png]]</p>
<p align='center'><i>The daemon's output</i></p> <p align='center'><i>The daemon's output</i></p>
Then, the user can go back to the application entry by following the "produced\_by" link: Then, the user can go back to the application entry by following the "produced_by" link:
<p align='center'>[[img/CTS-codelets-list.png]]</p> <p align='center'>[[img/CTS-codelets-list.png]]</p>
<p align='center'><i>The application viewer</i></p> <p align='center'><i>The application viewer</i></p>
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: 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:
<p align='center'>[[img/CTS-codelet-list.png]]</p> <p align='center'>[[img/CTS-codelet-list.png]]</p>
... ...
......