EECS2030

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== How to submit from outside the Prism lab ======

This course uses an automated system that checks your submitted work for correctness and coding style. The system is not currently compatible with the [[https://webapp.eecs.yorku.ca/submit|EECS Web Submit]] system; thus, students must transfer their work to an EECS server and then remotely log in to the server to submit their work. This document describes the steps needed to submit work from outside the Prism lab.

==== Windows users ====

Windows does not provide an easy-to-use method for transferring files or for remotely logging in to a UNIX workstation. You will need to download and install software to provide these services.

== Step 1 ==
Download and install [[https://winscp.net/eng/download.php|WinSCP]]. **WinSCP** is an open source free program that supports secure file transfer between two Internet connected computers.

== Step 2 ==
Download and install [[https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html|putty]] (at the bottom of the linked page; it is easiest to use the PuTTY Installation package). **putty** is an open source free program that supports secure remote login to a host computer (among other things).

== Step 3 ==
Remote login to the EECS undergraduate server and create a directory for your submission files if you have not already done so in the past. Do this by running the **putty** program that you installed in Step 2. In the //Host Name (or IP address)// field enter the EECS undergraduate server name **red.cse.yorku.ca** and then click the //Open// button

{{ :putty1.png }}

== Step 4 ==
You may get a warning window stating //"The server's host key is not cached in the registry."// This is to be expected if this is the first time that you have logged into **red.cse.yorku.ca** using **putty**. Click the //Yes// button to continue.

== Step 5 ==
You should see a login terminal appear:

{{ :putty2.png }}

== Step 6 ==
Type your EECS user name and press //Enter//. Type your EECS password and press //Enter//; **your password will not appear as you type it**.

{{ :putty3.png }}

== Step 7 ==
To keep things organized, make a directory named submit and change to the newly created directory by typing the commands:

<code>
mkdir submit
cd submit
</code>

Do not close **putty**; you still need it to run the submit command.

{{ :putty4.png }}

== Step 8 ==
Transfer your files from your computer to the EECS undergraduate server. Do this by running the **WinSCP** program that you installed in Step 1. Enter the EECS undergraduate server name **red.cse.yorku.ca** as the //Host name//, type in your EECS user name and password, and press the //Login// button.

{{ :winscp1.png }} 

== Step 9 ==
You may get a warning window stating //"The server's host key was not found in the cache."// This is to be expected if this is the first time that you have logged into **red.cse.yorku.ca** using **WinSCP**. Click the //Yes// button to continue.

{{ :winscp2.png }} 

== Step 10 ==
When you successfully login, you should see the **WinSCP** program running as shown in the figure below. The left pane shows the file system of your computer, and the right pane shows the file system of the EECS undergraduate server.

{{ :winscp3.png }} 

== Step 11 ==
In the left pane, navigate to the folder containing your submission files using the //Open directory/bookmark// button. For eclipse users, you can find the folder holding your files using eclipse (in eclipse, open one of your submission files, click the //File// menu and select //Properties//). 

{{ :winscp4.png }} 

== Step 12 ==
In the figure below, you can see that I have successfully found the files that I want to submit in the left pane.

In the right pane, navigate to your **submit** directory that you created in Step 7.

{{ :winscp5.png }} 

== Step 13 ==
In the left pane, select the files that you want to submit. In the figure below, you can see that I have selected three files to submit. Click the //Upload// button (highlighted in red in the figure below) to upload your files.

{{ :winscp6.png }} 

== Step 14 ==
When the upload is finished, you will see your files appear in your account on the EECS server in the right pane. 

{{ :winscp7.png }} 


== Step 15 ==
In **putty** verify that your files have been successfully uploaded by listing the contents of the directory:

<code>
ls
</code>

{{ :putty5.png }}



== Step 16 ==
In **putty**, type in the submit command given to you by your instructor. For example, to submit lab1 for EECS2030 you might type:

<code>
submit 2030 lab1 Point2.java SpiroUtil.java group.txt
</code>

{{ :putty6.png }}

== Step 17 ==
Read the output of the submit command carefully. If there are errors with your submission you may be forced to re-submit your corrected work.

== Step 18 ==
You may re-submit your work as many times as you like. Every time you make changes to your work on your computer, you must re-transfer your work using **WinSCP** and re-submit by typing in the submit command in **putty**.

==== Mac users ====
Mac OS provides a terminal program much like the terminal program that you use in the Prism labs. You can transfer your files and submit using the Mac terminal.

== Step 1 ==
In **Launchpad**, search for the **terminal** program, and start the **terminal** program. You will use this terminal to access files on your EECS account by logging into the EECS undergraduate server computer.

{{ :term1.png }}

== Step 2 ==
**ssh** (short for //secure shell//) is a program for logging into a remote computer and for executing commands on a remote computer.

Remotely log in to your EECS account using **ssh** by typing the following command and pressing //enter//:

<code>
ssh your_eecs_username@red.eecs.yorku.ca
</code>

You should replace ''your_eecs_username'' with your actual EECS user name. For example, if I wanted to remotely log in to my account I would type:

<code>
ssh burton@red.eecs.yorku.ca
</code>

{{ :term2.png }}

== Step 3 ==
If this is the first time that you have remotely logged in to the server, you will receive a warning message. Type ''yes'' and press //enter// to continue:

{{ :term3.png }}

== Step 4 ==
Enter your password and press //enter// (your password will not appear as your type):

{{ :term4.png }}

== Step 5 ==
You are now logged in to your EECS account. Notice that the prompt in your terminal has changed to **red** which is the name of the EECS server computer that you are currently logged in to.

{{ :term4-2.png }}


== Step 5 ==
To keep things organized in your EECS account, you should create a directory for your submission files. Type in the following commands, pressing //enter// after each command (if you haven't already done this in the past):

<code>
mkdir submit
cd submit
</code>

This will create a directory named ''submit'' in your home directory of your EECS account, and then change to the newly created directory.

{{ :term5.png }}


== Step 6 ==
Open a second **terminal** window (click on the //Shell// menu and click on //New Window//). You will use this terminal to access files on your computer.

{{ :term6.png }}

== Step 7 ==
Find the directory where your submission files are located. For eclipse users, you can find the directory holding your files using eclipse (in eclipse, open one of your submission files, click the //File// menu and select //Properties//). 

== Step 8 ==
Change to the directory on your computer where your submission files are located. For example, my files are located in the directory ''workspace/EECS2030/src/eecs2030/lab1''. To change to that directory I would type the following command into the terminal and press //enter//:

<code>
cd workspace/EECS2030/src/eecs2030/lab1
</code>

{{ :term7.png }}

== Step 9 ==
List the contents of the directory by typing the following command into the terminal and press //enter//:

<code>
ls
</code>

In the figure below you can see that I have three files in the directory
(''Point2.java'', ''SpiroUtil.java'', and ''group.txt'').

{{ :term8.png }}


== Step 10 ==
Transfer your files to your ''submit'' directory on the EECS undergraduate server. If you want to transfer all of the files in the directory use the following command:

<code>
scp * your_eecs_username@red.eecs.yorku.ca:submit
</code>

Again, replace ''your_eecs_username'' with your actual EECS user name.

If you want to transfer specific files you can do so by transferring them one at a time; for example, I could transfer all three files individually by typing:

<code>
scp Point2.java burton@red.eecs.yorku.ca:submit
scp SpiroUtil.java burton@red.eecs.yorku.ca:submit
scp group.txt burton@red.eecs.yorku.ca:submit
</code>

{{ :term9.png }}


== Step 11 ==
**scp** will prompt you for your EECS password; type it in and press //enter//. 

{{ :term10.png }}


== Step 12 ==
**scp** will transfer a copy of your files from your computer to your EECS account.

{{ :term11.png }}
 

== Step 13 ==
Switch back to the first terminal window that you opened (the terminal where you are currently logged into **red**).

Make sure that your files have been transferred into your ''submit'' directory by typing the following command and press //enter//:

<code>
ls
</code>

In the figure below, you can see that the files ''group.txt'', ''Point2.java'', and ''SpiroUtil.java'' are now in the submit directory of my EECS account.

{{ :term12.png }}


== Step 14 ==
Submit your files using the command provided by your instructor.

For example, to submit lab1 for EECS2030 you might type:

<code>
submit 2030 lab1 Point2.java SpiroUtil.java group.txt
</code>

{{ :term13.png }}

== Step 15 ==
Read the output of the submit command carefully. If there are errors with your submission you may be forced to re-submit your corrected work.



== Step 18 ==
You may re-submit your work as many times as you like. Every time you make changes to your work on your computer, you must re-transfer your work using ''scp'' (using a terminal window on your computer) and re-submit by typing in the submit command (using a terminal window where you are logged into **red**).

Your remote login session ends automatically if you don't enter any commands for a certain period of time. If this happens, you will see a message that mentions a ''broken pipe'' and your terminal prompt will show the name of your computer (indicating that you are no longer remotely logged into **red**). If this happens,
run the **ssh** program again to log back into **red**.