Differences

This shows you the differences between two versions of the page.

--- exp_get_results [2014/06/17 17:42] – created bguillon
+++ exp_get_results [2017/08/22 14:34] (current) – mimbert
@@ Line 1: / Line 1: @@
 ===== Gathering experiment results =====
-By default, the standard output and error channels will be retrieved on each node in dedicated txt files: `stdout.txt` and `stderr.txt`. Any other file produced by your scripts and code will be also retrieved if they exist. All these files will be zipped into a tar.gz archive file, one for each node involved. These archive files will then be put into a `results` NFS share located at the root of your home directory on the airlock. However it is mounted in read-only and should thus be handled as such.
+By default, the standard output and error channels will be retrieved on each node in dedicated txt files: `stdout.txt` and `stderr.txt`. Any other file produced by your scripts and code will be also retrieved if they exist. All these files will be zipped into a tar.gz archive file, one for each node involved. These archive files will then be put into a `results` NFS share located at the root of your home directory on the airlock. Each task will be into its own subdirectory and each node results as well.
-To ease the retrieval of the results from this NFS share, a little program can be called:
-<code>
-you@srvairlock:~$ unzip_task_results <task_id>
-</code>
-All results will be retrieved and unzipped in a `my_results` folder at the root of your home directory. Each task will be into its own subdirectory and each node results as well.
 <code>
@@ Line 17: / Line 10: @@
         ├── benchmark_tx.py
         ├── receive_path.py
-        ├── scenario.desc
+        ├── scenario.yaml
         ├── stderr.txt
         ├── stdout.txt
@@ Line 24: / Line 17: @@
         ├── uhd_interface.py
         └── uhd_interface.pyc
+...
+</code>
-</code>
+=> [Downloading the results from the airlock](exp_download)