User Tools

Site Tools


mtl

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mtl [2011/03/03 12:02] franckmtl [2015/12/14 18:57] (current) malsabbagh
Line 12: Line 12:
 === How to connect to MTL === === How to connect to MTL ===
  
-MTL has registered one of York's IP addresses to their system, so we can connect through //"Direct IP."// The IP address registered is indigo.cse.yorku.ca, so to connect to MTL, we need to connect to indigo first. If you're using the computer on campus, open terminal and type **''ssh indigo''** (doesn't need username and password). If you connect from home, use an ssh client to connect to **''indigo.cse.yorku.ca''**, then login with your cse account and password.+MTL has registered one of York's IP addresses to their system, so we can connect through //"Direct IP."// The IP address registered is indigo.cs.yorku.ca, so to connect to MTL, we need to connect to indigo first. If you're using the computer on campus, open terminal and type **''ssh indigo''** (doesn't need username and password). If you connect from home, use an ssh client to connect to **''indigo.cs.yorku.ca''**, then login with your EECS account and password.
  
 From indigo, we can connect to MTL using this command: From indigo, we can connect to MTL using this command:
-  ssh -l username 192.55.51.81+  ssh -l username 207.108.8.131
  
 The username and password will be provided by email.  The username and password will be provided by email. 
Line 26: Line 26:
  
 Copying from MTL to indigo: Copying from MTL to indigo:
-  scp username@192.55.51.81:<file_path_on_MTL> <file_path_on_indigo>+  scp username@207.108.8.131:<file_path_on_MTL> <file_path_on_indigo>
 Copying from indigo to MTL: Copying from indigo to MTL:
-  scp <file_path_on_indigo> username@192.55.51.81:<file_path_on_MTL>+  scp <file_path_on_indigo> username@207.108.8.131:<file_path_on_MTL>
  
 If we want to transfer a file to our current active directory, we can just type a single dot (.) If we want to transfer a file to our current active directory, we can just type a single dot (.)
Line 35: Line 35:
  
 Copy 1 file from MTL to indigo Copy 1 file from MTL to indigo
-  scp username@192.55.51.81:/home/username/myfolder/myfile.java .+  scp username@207.108.8.131:/home/username/myfolder/myfile.java .
 Copy the whole folder + subfolder from MTL to indigo Copy the whole folder + subfolder from MTL to indigo
-  scp -r username@192.55.51.81:/home/username/myfolder/ .+  scp -r username@207.108.8.131:/home/username/myfolder/ .
 Copy several files from MTL to indigo Copy several files from MTL to indigo
-  scp username@192.55.51.81:/home/username/myfolder/\{myfile_1.java,myfile_2.java\} .+  scp username@207.108.8.131:/home/username/myfolder/\{myfile_1.java,myfile_2.java\} .
 Copy all files in current active directory (local) to MTL Copy all files in current active directory (local) to MTL
-  scp * username@192.55.51.81:/home/username/myfolder/+  scp * username@207.108.8.131:/home/username/myfolder/
  
 [[http://winscp.net/eng/index.php|WinSCP]] is a very nice freeware SCP/FTP/SFTP package for Windows.  (It also has it's own embedded SSH terminal, but it's not terribly useful.)  With WinSCP, you can connect to MTL from your home computer and drag and drop to upload/download files. [[http://winscp.net/eng/index.php|WinSCP]] is a very nice freeware SCP/FTP/SFTP package for Windows.  (It also has it's own embedded SSH terminal, but it's not terribly useful.)  With WinSCP, you can connect to MTL from your home computer and drag and drop to upload/download files.
  
-To connect to MTL with WinSCP, set up a session with MTL's IP as the host, and your MTL username/password.  Then, before you save/connect to the session and close the window, set it up to tunnel through Indigo to MTL by clicking the "Tunnel" item in the tree-pane on the left, and checking "Connect through SSH tunnel," entering "indigo.cs.yorku.ca" as host, and your CSE username/password.  After this, you can interact with the file structure on MTL as if it were a part of your local file-system.+To connect to MTL with WinSCP, set up a session with MTL's IP as the host, and your MTL username/password.  Then, before you save/connect to the session and close the window, set it up to tunnel through indigo to MTL by clicking the "Tunnel" item in the tree-pane on the left, and checking "Connect through SSH tunnel," entering "indigo.cs.yorku.ca" as host, and your EECS username/password.  After this, you can interact with the file structure on MTL as if it were a part of your local file-system.
  
 === How to run an experiment === === How to run an experiment ===
  
 +<html>
 +<!--
 MTL consist of one login machine, and two experiment machines. To run a program on the experiment machine, we should submit a script to the batch system using this command: MTL consist of one login machine, and two experiment machines. To run a program on the experiment machine, we should submit a script to the batch system using this command:
   qsub <script_name>   qsub <script_name>
Line 70: Line 72:
  
 The latest version of Java is not the default JVM, so we should specify the full path **''/opt/java/latest/bin/java''**. Wall time is the maximum time that your experiment may run. Setting this value can help terminate your job in case it deadlocks or gets into an infinite loop. The latest version of Java is not the default JVM, so we should specify the full path **''/opt/java/latest/bin/java''**. Wall time is the maximum time that your experiment may run. Setting this value can help terminate your job in case it deadlocks or gets into an infinite loop.
 +-->
 +</html>
  
-More information can be found in {{private:guide.pdf|this}} guide.+More information can be found in {{private:guide.pdf|this}} guide and 
 +{{:mtl_tutorial.pdf|this}} guide.
  
 === Maximum number of CPUs and threads === === Maximum number of CPUs and threads ===
Line 79: Line 84:
 === Questions === === Questions ===
  
-The forum {{http://software.intel.com/en-us/forums/intel-manycore-testing-lab/|Intel® Manycore Testing Lab}} provides answers to many questions.  If you cannot find an answer to your question there, post your question at the {{https://forum.cse.yorku.ca/viewforum.php?f=142|forum}} for this course.+The forum {{http://software.intel.com/en-us/forums/intel-manycore-testing-lab/|Intel® Manycore Testing Lab}} provides answers to many questions.
  
 +=== Determine some CPU-Specs ===
 +
 +Since the job is executed in somewhat like a black-box after assigning it to the queue, one may ask what is the underlying system. The following Java snippets provide some system information: {{:csystem.txt|}}. Another possibility is to use bash commands. The following file shows an example to get detailed cpu information and current cpu clock-frequency: {{:cpu.txt|}}. The current cpu clock-frequency may vary over execution time due to energy-saving features of the cpu. So, one may check the current cpu clock-frequency several times during the experiment. 
 +
 +=== Acknowledging the Intel Manycore Testing Lab in your publications ===
 +{{https://software.intel.com/en-us/forums/intel-manycore-testing-lab/topic/285877|Forum post about acknowledging MTL labs}}
mtl.1299153754.txt.gz · Last modified: 2011/03/03 12:02 by franck

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki