Skip to content

Changes

Page history
img authored by Franck TALBART's avatar Franck TALBART
Show whitespace changes
Inline Side-by-side
TutorialsGeneralUsageCodeletManagementCodeletFinder.md
View page @ 99a0a144
...@@ -37,7 +37,7 @@ To import an application, click on the "Codelet management" link from the top-me ...@@ -37,7 +37,7 @@ To import an application, click on the "Codelet management" link from the top-me
The application creation form should appear: The application creation form should appear:
</div> </div>
<p align='center'>[[img/CTS-add_Application-Hot-Links.png]]</p> <p align='center'>![](img/CTS-add_Application-Hot-Links.png)</p>
<p align='center'><i>The application form</i></p> <p align='center'><i>The application form</i></p>
...@@ -53,7 +53,7 @@ Once completed, the user can click on Add to finally add the application. This w ...@@ -53,7 +53,7 @@ Once completed, the user can click on Add to finally add the application. This w
Clicking this link will display a view, providing information about the application. Clicking this link will display a view, providing information about the application.
</div> </div>
<p align='center'>[[img/CTS-Import-Application-Information.png]]</p> <p align='center'>![](img/CTS-Import-Application-Information.png)</p>
<p align='center'><i>The application viewer</i></p> <p align='center'><i>The application viewer</i></p>
...@@ -100,19 +100,19 @@ Then, the user can run the experiment and never has to perform the ssh-key step ...@@ -100,19 +100,19 @@ 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: Via CTS, the user must go to the created application entry and click on the "Create new codelets" button:
<p align='center'>[[img/CTS-Import-Application-Information.png]]</p> <p align='center'>![](img/CTS-Import-Application-Information.png)</p>
<p align='center'><i>The application viewer</i></p> <p align='center'><i>The application viewer</i></p>
Then, the user specifies on which machine CF should be run, by clicking on the "Find" button: Then, the user specifies on which machine CF should be run, by clicking on the "Find" button:
<p align='center'>[[img/CTS-create-codelet-platform.png]]</p> <p align='center'>![](img/CTS-create-codelet-platform.png)</p>
<p align='center'><i>The Codelet Finder form</i></p> <p align='center'><i>The Codelet Finder form</i></p>
If the machine is not registered in CTI, the user follows the "Add an entry" link, on the top of the pop-up. Then, he fills in the following form: If the machine is not registered in CTI, the user follows the "Add an entry" link, on the top of the pop-up. Then, he fills in the following form:
<p align='center'>[[img/CTS-add-platform-form.png]]</p> <p align='center'>![](img/CTS-add-platform-form.png)</p>
<p align='center'>The platform form_</p>_ <p align='center'>The platform form_</p>_
...@@ -120,13 +120,13 @@ If the machine is not registered in CTI, the user follows the "Add an entry" lin ...@@ -120,13 +120,13 @@ If the machine is not registered in CTI, the user follows the "Add an entry" lin
Finally, the user goes back to the previous form and select the platform. The user can also specify makefile/sbatch option: Finally, the user goes back to the previous form and select the platform. The user can also specify makefile/sbatch option:
<p align='center'>[[img/CTS-launch-CF-process.png]]</p> <p align='center'>![](img/CTS-launch-CF-process.png)</p>
<p align='center'><i>The Codelet Finder form</i></p> <p align='center'><i>The Codelet Finder form</i></p>
The CF daemon is launched and the daemon output is updated in an output file that is viewable: The CF daemon is launched and the daemon output is updated in an output file that is viewable:
<p align='center'>[[img/CTS-daemon-output.png]]</p> <p align='center'>![](img/CTS-daemon-output.png)</p>
<p align='center'><i>The daemon is running</i></p> <p align='center'><i>The daemon is running</i></p>
...@@ -222,31 +222,31 @@ When the process is finished, the codelets are automatically imported into CTI i ...@@ -222,31 +222,31 @@ When the process is finished, the codelets are automatically imported into CTI i
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>
<p align='center'><i>The list of codelets</i></p> <p align='center'><i>The list of codelets</i></p>
By choosing one of the codelets, the related file entry is displayed: By choosing one of the codelets, the related file entry is displayed:
<p align='center'>[[img/CTS-files-list.png]]</p> <p align='center'>![](img/CTS-files-list.png)</p>
<p align='center'><i>The list of files</i></p> <p align='center'><i>The list of files</i></p>
By clicking on the filenames, the file viewer displays the content: By clicking on the filenames, the file viewer displays the content:
<p align='center'>[[img/CTS-file-entry.png]]</p> <p align='center'>![](img/CTS-file-entry.png)</p>
<p align='center'><i>The file viewer</i></p> <p align='center'><i>The file viewer</i></p>
... ...
......