Difference between revisions of "EGR 103/Getting Started (very outdated)"

From PrattWiki
Jump to navigation Jump to search
(Created page with "In the example below, "N" is used to represent the lab number for that week. # Log into one of the PCs in the lab using your NetID. Be sure it is set to log on to WIN. # In W...")
 
m (DukeEgr93 moved page EGR 103/Getting Started to EGR 103/Getting Started (very outdated) without leaving a redirect: outdated page)
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
 
# Log into one of the PCs in the lab using your NetID. Be sure it is set to log on to WIN.
 
# Log into one of the PCs in the lab using your NetID. Be sure it is set to log on to WIN.
 
# In Windows:
 
# In Windows:
#* Mount your CIFS drive. For instructions, go to [[How To Get Work Done]] then click the link for File Access under Your Own Windows Computer. Note the comments on Pundit modifying what the OIT page instructions say.
+
#* Mount your CIFS drive. For general instructions, go to [[How To Get Work Done]] then click the link for File Access under Your Own Windows Computer. Note the comments on Pundit modifying what the OIT page instructions say. For the B209 lab, follow the instructions below:
#* Start a terminal with graphics. For instructions,  go to [[Lab:B209]] and check out the Using the PCs to Run Unix Programs Remotely section for how to get connected and make sure the connection is working.
+
#** Open File Explorer and click on This PC
 +
#** At the top of the window, left-click Computer and then Map Network Drive
 +
#*** Drive: Pick an unused letter (this example will use Z:)
 +
#*** Folder: \\homedir.oit.duke.edu\users\N\NetID
 +
#**** N is the first letter of your NetID; NetID is your NetID
 +
#**** If you logged in to the computer using your NetID, you can just Finish; if not (for instance, if you logged in from your own computer), select Connect Using Different Credentials.  For Different Credentials, use WIN\NetID for the user name and your OIT password
 +
#* Start a terminal with graphics. For general instructions,  go to [[Lab:B209]] and check out the Using the PCs to Run Unix Programs Remotely section for how to get connected and make sure the connection is working.  For the B209 lab, follow the instructions below:
 +
#** Start [[MobaXterm]]; you can double click the icon on the desktop or use the search option at lower left to find <code>moba</code>.
 +
#** Start a new terminal in MobaXterm.  There should be a button in the middle of the right panel for this.
 +
#** Type <source lang=bash> ssh -XY NETID@login.oit.duke.edu</source>
 +
#**:where NETID is your NET ID in lower case.
 +
#** Type your password when asked - if it gives a warning about a .Xauth file, that's probably fine...  Note that the cursor will not move as you type your password.
 +
#** At the <code>production</code> prompt, type <source lang=bash>
 +
xeyes & </source>to start the xeyes program.  You can minimize the program, but you should keep it running to keep your session from timing out.
 
#* Start Spyder. In the Windows menu, there is a group for Anaconda3; Spyder is in that group. If the PC asks for network permissions, click cancel. If the PC asks about updating, do not update.
 
#* Start Spyder. In the Windows menu, there is a group for Anaconda3; Spyder is in that group. If the PC asks for network permissions, click cancel. If the PC asks about updating, do not update.
 
# In the terminal window (i.e. in UNIX; note the ☒ represents a space):
 
# In the terminal window (i.e. in UNIX; note the ☒ represents a space):
Line 11: Line 24:
 
mkdir ☒ labN
 
mkdir ☒ labN
 
cd ☒ labN</syntaxhighlight>
 
cd ☒ labN</syntaxhighlight>
#* Copy the tar file from Dr. G’s space into your lab2 folder and expand the tar file: <syntaxhighlight>wget ☒ people.duke.edu/∼mrg/EGR103/LabNFiles.tar
+
#* Copy the tar file from Dr. G’s space into your <code>labN</code> folder and expand the tar file: <syntaxhighlight>wget ☒ people.duke.edu/∼mrg/EGR103/LabNFiles.tar
 
tar ☒ -kxvf ☒ LabNFiles.tar</syntaxhighlight>
 
tar ☒ -kxvf ☒ LabNFiles.tar</syntaxhighlight>
 
#* Make a personal copy of the lab report skeleton: <syntaxhighlight>
 
#* Make a personal copy of the lab report skeleton: <syntaxhighlight>
cp ☒ -i ☒ LabNSample S20.tex ☒ labN.tex</syntaxhighlight>
+
cp ☒ -i ☒ LabNSample_S20.tex ☒ labN.tex</syntaxhighlight>

Latest revision as of 18:31, 23 August 2023

In the example below, "N" is used to represent the lab number for that week.

  1. Log into one of the PCs in the lab using your NetID. Be sure it is set to log on to WIN.
  2. In Windows:
    • Mount your CIFS drive. For general instructions, go to How To Get Work Done then click the link for File Access under Your Own Windows Computer. Note the comments on Pundit modifying what the OIT page instructions say. For the B209 lab, follow the instructions below:
      • Open File Explorer and click on This PC
      • At the top of the window, left-click Computer and then Map Network Drive
        • Drive: Pick an unused letter (this example will use Z:)
        • Folder: \\homedir.oit.duke.edu\users\N\NetID
          • N is the first letter of your NetID; NetID is your NetID
          • If you logged in to the computer using your NetID, you can just Finish; if not (for instance, if you logged in from your own computer), select Connect Using Different Credentials. For Different Credentials, use WIN\NetID for the user name and your OIT password
    • Start a terminal with graphics. For general instructions, go to Lab:B209 and check out the Using the PCs to Run Unix Programs Remotely section for how to get connected and make sure the connection is working. For the B209 lab, follow the instructions below:
      • Start MobaXterm; you can double click the icon on the desktop or use the search option at lower left to find moba.
      • Start a new terminal in MobaXterm. There should be a button in the middle of the right panel for this.
      • Type
         ssh -XY NETID@login.oit.duke.edu
        
        where NETID is your NET ID in lower case.
      • Type your password when asked - if it gives a warning about a .Xauth file, that's probably fine... Note that the cursor will not move as you type your password.
      • At the production prompt, type
        xeyes &
        
        to start the xeyes program. You can minimize the program, but you should keep it running to keep your session from timing out.
    • Start Spyder. In the Windows menu, there is a group for Anaconda3; Spyder is in that group. If the PC asks for network permissions, click cancel. If the PC asks about updating, do not update.
  3. In the terminal window (i.e. in UNIX; note the ☒ represents a space):
    • Change into your folder for EGR 103L, create a labN folder inside it, then switch into that folder:
      cd ☒ ∼/EGR103
      mkdir ☒ labN
      cd ☒ labN
    • Copy the tar file from Dr. G’s space into your labN folder and expand the tar file:
      wget ☒ people.duke.edu/∼mrg/EGR103/LabNFiles.tar
      tar ☒ -kxvf ☒ LabNFiles.tar
    • Make a personal copy of the lab report skeleton:
      cp ☒ -i ☒ LabNSample_S20.tex ☒ labN.tex