Differences

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

--- other:newppl:starting [2019/04/24 16:45] – [Which programs should you use?] Improved section jypeter
+++ other:newppl:starting [2020/03/05 11:29] – [Miscellaneous information] jypeter
@@ Line 8: / Line 8: @@
 A few useful links that have nothing to do with science and software resources!
+  * [[other:newppl:pub_transport|LSCE-related public transport]]
   * [[other:newppl:riealgo|Adding money online to your restaurant account]]
   * [[https://intranet.lsce.ipsl.fr/Phocea/Page/index.php?id=97|Survival kit and other information for CDD and interns]] (LSCE intranet)
@@ Line 14: / Line 15: @@
   * [[https://logement.campus-paris-saclay.fr/| Trouver un logement dans une résidence universitaire]] (in French... //Finding a room in a student dorm//)
   * [[https://www.science-accueil.org/en/|Science Accueil]]
+  * {{:other:newppl:uvsq-guide-du-personnel-nov2019.pdf|Guide du Personnel UVSQ}}
 ===== Phone directory, and map of the building =====
@@ Line 169: / Line 171: @@
 ===== Which Linux servers should you use? =====
-There are lots of things you can do directly on your **local** Win7 or Linux desktop (displaying pdf, images, using a text editor, ...), rather than on the remote servers. Never forget that **your local desktop has access to the remote disks on the Linux servers**.
+There are lots of things you can do directly on your **local** Win7/Win10 or Linux desktop (displaying pdf, images, using a text editor, ...), rather than on the remote servers. Never forget that **your local desktop has access to the remote disks on the Linux servers**.
 Otherwise, **use the appropriate Linux servers**. The //load balancing// system will send you to the server that has currently the smallest load
-  * obelixN (''ssh obelix'', or ''ssh obelix.lb''): never forget that you are sharing these servers with other users! Do not use too much CPU and memory for a long time. Heavy computation should be done on the obelix cluster
+  * **obelix**//NN// (type ''ssh obelix'' to get there): never forget that you are sharing these servers with other users! Do not use too much CPU and memory for a long time. Heavy computation should be done on the obelix cluster
-  * [[https://intranet.lsce.ipsl.fr/informatique/en/calcul/batch.php|the batch system]] (aka //obelix cluster//) for really heavy duty programs
+    * <code> $ ssh obelix
+Last login: Mon Jun  3 08:49:53 2019 from somewhere
+# You can use one of the following commands if you want to know on which obelix you are
+ >echo $HOST
+obelix5
+ >hostname
+obelix5</code>
+  * [[https://intranet.lsce.ipsl.fr/informatique/en/calcul/batch.php|the batch system]] (aka //obelix **cluster**//) for really heavy duty programs
   * in some cases, you may need an account to use the [[http://mesocentre.ipsl.fr/|IPSL/ESPRI clusters]] (aka //ciclad// and //climserv//), especially if you need to use data that is already available/mirrored there, rather than copying the data to LSCE
-  * asterixN: some people may mention these servers, but they don't exist any more!
+  * //asterixN//: some people may mention these servers, but they don't exist any more!
 ==== Which shell are you using? ====
@@ Line 238: / Line 247: @@
 <note warning>
   * It is very important to use the correct directories and make it easy for your advisor to find things after you have left
-    * **Put the source codes, scripts and papers you are writing on a backed up disk**
+    * <wrap em>**Put the source codes, scripts and papers you are writing on a backed up disk**</wrap>
-    * Put temporary files on a scratch disk
+      * The <wrap em>backed up disk at LSCE</wrap> is [[#the_home_directory|/home/users/your_login]]. You should have a few Gb available on //home// (use the ''quota -s'' command to find out the exact amount)
-    * Do NOT put (big) data files on a backed up disk
+    * Put **temporary files** on a scratch disk (''scratch01'' at LSCE)
+    * Do **NOT** put (big) data files on a backed up disk
   *  Do not forget to clean your directories before you leave (ask your advisor what should be kept or cleaned)
@@ Line 250: / Line 260: @@
   * Example path on the LSCE Linux server: ''/home/scratch01/your_lsce_login''
-  * Accessing the same path from a local desktop:
+  * Accessing the path above from a local desktop:
     * Linux desktop: ''/home/scratch01/your_lsce_login''
     * Windows desktop: ''\\dfshost\dfs\scratch01\your_lsce_login''\\ {{ :other:newppl:dfs_on_win.png?nolink |}}
@@ Line 266: / Line 276: @@
       * bash shell users: ''.profile'' and ''.bashrc''
       * emacs text editor: ''.emacs''
+    * You can go to your home directory by typing ''cd'' (no arguments), and to the home directory of somebody else with ''cd ~login_name''
+    * At LSCE, you can't read the content of somebody else's //home// directory
   * **Backup of the home directory on the LSCE servers**: YES! Every night
-    * More details on the [[https://intranet.lsce.ipsl.fr/informatique/en/nsr/index.php|backup system]] page
+    * More details on the [[https://intranet.lsce.ipsl.fr/informatique/en/nsr/index.php|LSCE backup system]] page
-    * Put the most important sources/scripts/data/papers in this directory
+    * <wrap em>Put the most important sources/scripts/data/papers in this directory</wrap>
-    * Do not put temporary files, or big data files that are available somewhere else in this directory!
+    * **Do not** use the //home// directory to store:
-    * Your home directory will also be archived when your account is closed
+      * temporary files (use ''scratch01'')
+      * big (or many) data files (use ''scratch01'' or a project specific disk)
+    * Your home directory will be archived when your account is closed, so that you or your advisor can access it later, if required
   * **Backup of the TGCC home directory**: YES!
@@ Line 284: / Line 298: @@
 ==== The scratch directory ====
+<note warning>Do not put anything in the scratch directory that you can't recreate with a program, or copy/download from somewhere else!</note>
   * **Location**: ''/home/scratch01/your_lsce_login''
@@ Line 296: / Line 312: @@
 ==== Project specific directories ====
+<note warning>The data on these disks is <wrap em>probably not backed up</wrap>... You are not protected against file deletion by mistake, or a disk crash (a major disk crash is not likely, but can happen)
+\\ You should <wrap em>store your source codes, scripts, notebooks, manuscripts, reports, figures, on a backed up directory</wrap>, and only store on the project disks data downloaded from outside, or that you can regenerate with the backed up scripts</note>
   * **Location**: ''/home/some_project_name/your_lsce_login''
     * Ask your advisor if you should use a specific project directory and the technical details about it
-    * Use this directory for storing the (big) data files that you can't store safely in the //scratch// directory, and should not store in the //scratch// directory
+    * Use this directory for storing the (big) data files that you can't store safely in the //scratch// directory, and should not store in the //home// directory
   * **Backup**: ask your advisor
@@ Line 464: / Line 485: @@
   - Send a mail to //help-lsce//, and request an access to the //ssh1// server
   - Use ''ssh'' to **connect** to //ssh1//
-    * From a Linux/mac desktop: ''ssh -A -X your_lsce_login@ssh1.lsce.ipsl.fr''
+    * From a terminal on a Linux/Windows10/Mac computer: ''ssh -A -X your_lsce_login@ssh1.lsce.ipsl.fr''
-    * From a Windows desktop:
+    * From a Windows computer:
-      * Text only: use [[other:win7apps#putty|Putty]]
+      * Text only: use [[other:win10apps#putty_pageant|Putty]]. Putty allows you to open text terminals on remote computers
-      * Text & graphics. This is more complex to set up, and you need to use one of the options below:
+      * Text **and graphics**: you need to [[https://wiki.lsce.ipsl.fr/pmip3/doku.php/other:win10wsl#using_an_x_server|install an X server]] on your computer in order to display the graphics
-        * use [[other:win7apps#vcxsrv_windows_x_server|VcXsrv]]
+  - You can access all LSCE disks from //ssh1//, but there is only a limited number of programs that you can run, so you have to go from //ssh1// to //obelix// or //irene// with one of the ''ssh'' commands below:
-        * use [[other:win7apps#cygwin-x|cygwin/X]]
-        * use [[other:index#virtualbox_notes|VirtualBox]]
-  - You can access all LSCE disks from //ssh1//, but there is only a limited number of programs that you can run, so you have to go from //ssh1// to //obelix// or //curie// with one of the ''ssh'' commands below:
     * ''ssh obelix''
     * ''ssh your_tgcc_login@curie-ccrt.ccc.cea.fr''
@@ Line 487: / Line 505: @@
 ==== Copying files to/from LSCE ====
-If you need to **transfer** files to/from LSCE, use ''scp'' (on Linux), or an scp client such as [[other:win7apps#winscp|WinSCP]] (on Windows) between your computer and ''ssh1.lsce.ipsl.fr''
+If you need to **transfer** files to/from LSCE, use ''scp'' (on Linux and Windows 10), or a graphical scp client such as [[other:win10apps#winscp|WinSCP]] (on Windows) between your computer and ''ssh1.lsce.ipsl.fr''
-  * Example from a Linux/mac desktop: ''scp -p file_outside_lsce your_lsce_login@ssh1.lsce.ipsl.fr:/home/scratch01/your_lsce_login/''
+  * Example:
+    * Sending **one file** from a Linux/Windows10/Mac computer to your //scratch// directory at LSCE:\\ ''scp -p file_on_your_computer_outside_lsce your_lsce_login@ssh1.lsce.ipsl.fr:/home/scratch01/your_lsce_login/''
+    * Sending recursively **a full directory**:\\ ''scp -pr directory_on_your_computer_outside_lsce your_lsce_login@ssh1.lsce.ipsl.fr:/home/scratch01/your_lsce_login/''
 ===== What next? =====