- About Us
- For Students
Users of the Senior Design Center (SDC) Laboratory are expected to abide by the following policies. These policies are intended to preserve the integrity, utility, and flexibility of the equipment in the lab. They are also designed to protect the privacy of work done by students and faculty and to preserve our access to networks to which the lab is connected. You will also find useful and important information in the FAQs section.
The computers that are in your workspace are not related to your unity accounts. An account for your team has been set up. The initial login/password for your team is 'adminuser/adminuser' (for Windows machines). Please change the password immediately.
Please change the password associated with the team login to something more secure. Be sure to change the password to one that the team decides upon. All student team accounts have administrator privileges. Be advised, if you also create additional logins, the Sys Admin will not support any problems with these accounts. Please create passwords for any additional accounts as well.
There are several applications that are freely available on the Internet and each team has administrator privileges on their machine. You are encouraged to install and configure these free applications in an effort to better understand the technology that you will be using to develop your project. If the application you need is not freely available for download, use the Resource Request Form. In your request be sure to specify your computer name(s) found on a sticker on the front of each computer. Also be sure give the following information about the software: cost, where it can be found (ie website) what the software does, and why you need it.
Yes. Yes. All default student accounts on Senior Design Center computers will belong to the 'administrator' group. With this comes the responsibility to ensure that your computer remains viable and stable.
Yes, you may access your AFS space with your unity login through WinSCP. You may download and install the latest version of WinSCP at http://www.eos.ncsu.edu/remoteaccess/windows/ras-win-sftp.html.
In an effort to increase security in our labs, machines will be made remotely accessible only through VPN and NCSU wireless (not guest). You must put in a resource request to be allowed remote access to your machines.
Virtual Machines are available upon request. CSC IT maintains multiple virtualization clusters on Centennial Campus which which are available to SDC students. The recommended method for attaching to these VMs is via a remote protocol such as SSH & RDP (Remote Desktop; Windows) but console access is also permitted via https://vcenter.csc.ncsu.edu. vCenter access is also limited to on-campus & VPN only access.
Default configuration for these VMs are:
Windows Server 2012 R2; 1vCPU, 3GB RAM, 40GB HDD
Red Hat Enterprise Linux (RHEL) 6; 1vCPU, 1GB RAM, 10GB HDD
Additional/alternate OSes can be installed yourself or we can import a prebuilt VM for you. The above configurations are default. Addtional resources can be allocated upon request.
Remote access is available by default on all Windows machines deployed by CSC IT Staff. You must first connect via campus VPN if you are not on campus. (https://vpn.ncsu.edu). And then use RDP to access the machines on port 4040. Linux machines may require additional configuration from the local machine.
Please do not store or host your project on any external services (AWS, Azure, etc.) without checking with both your sponsor and the CSC IT team. Your sponsor might not want their data stored in a particular place. And if you’re doing a university-based project, there are strict limitations about what data can be hosted and where. The only exception to this is DropBox. If you are working for a company (not an NCSU entity), they can approve use of Dropbox without CSC IT approval.
Additional equipment such as iPads and Android phones may be required for your project. These items can be checked out from CSC IT Staff. Please send in a resource request for these items.
Teams will have access to GIT repositories for version control of source code and other text-based documents. All repositories have been created in advance for your team. Please note that your team is required to use the GIT repository provided by the Senior Design Center.
If you have not done so yet, visit NC State's GitHub Enterprise at https://github.ncsu.edu/ and log in with your Unity account. This is needed to initialize your account on GitHub before it can be added to your team's repository. To give your account access to your GIT repository, visit the Document Submission System, open the 'GIT Instructions' page, and follow the instructions.
If you don't have a GIT client installed already, you can visit http://git-scm.com/downloads and download the GIT client there.
This operation needs to be done only once by one of the members of your team. After your GIT repository is initialized, other team members should follow the instructions on Cloning your GIT Repository below.
git add README.md (or the name of the file you created in step 2)
git commit -m "first commit"
git remote add origin https://github.ncsu.edu/engr-csc-sdc/<REPO_NAME>.git
git push -u origin master
git clone https://github.ncsu.edu/engr-csc-sdc/<REPO_NAME>.git
<REPO_NAME>is the name of your team's repository (e.g. spring2013Team03).
git add <file>, where
<file>is the name of the file or folder you want to include in the commit. You can also include everything by running the command
git add .
NOTE: Committing files into your repository is a local operation. It does not affect the files on the server. If you want the changes to be visible somewhere else (like to the instructors for grading, or to update the code on other computers) you must push it to the server.
git push origin master
git pushto push your commits to the server.
You can find more information on the available GIT commands, and details about how a GIT repository works on http://git-scm.com/docs. Details about how to use GitHub can be found at https://help.github.com/.
Please let your TAs know if you have a problem using GIT, or let us know immediately if you have any other problems.
Note: Resource Requests should be completed by the Team Lead.