Using GitHub and Visual Studio

 

Get a GITHUB account and create your own fork of the EN234_FEA repository

 

  1. Navigate to https://github.com Follow the instructions to create a new account. You can just create a free account (unless you want to create private repositories for your own research) - you will be signed in automatically once the account is complete. To sign out you can use the menu on the far top right of the screen. Don't sign out just now.
  2. In another browser window navigate to https://github.com/albower/EN234_FEA.git Press the 'Fork' button on the right of your screen near the top. Wait while the files are copied to your account. You now have your own copy of EN234_FEA, and will use this to track all the changes you make to the code.

Create a local repository of EN234_FEA on your Remote Desktop, build and run the code

  • Log into the Remote Desktop
  • Open Visual Studio by going to Intel Parallel Studio> Launch VS2013>
  • Click the Team Explorer tab on the right

  • Navigate to your Github fork and click 'Clone or Download'
  • Copy the link (IMPORTANT: USE YOUR FORK, NOT THE LINK TO THE ORIGINAL REPO!!)

  • In Visual Studio click 'Clone'
  • Paste the Github link into the space provided
  • Enter a directory to store the clone (the suggested directory is H:\Repos\EN234_FEA )
  • Press 'Clone'

  • Click the little house at the top of the Team Explorer window

  • Double click the EN234_Visual_Studio.sln, and wait for the solution file to be created
  • Click the 'Solution Explorer' tab, and expand the Source Files directory on the right
  • double click main.f90 to open it
  • Check that the VS_root_folder is set correctly in the code
  • Scroll down and uncomment the input and output file for the demo or homework problem you would like to run
  • Go to Build> and select Build EN234_Visual_Studio to compile and link
  • Press the Start arrow to start debugging
  • You can switch to Release mode to run the code faster, and switch to x64 to build a 64 bit version of the code (needed if you need a lot of memory)

Commit changes, and push to your Github fork

  • Click the 'Team Explorer' tab, and click the little house at the top
  • Click Changes
  • Enter a short description of the changes in the 'Enter a commit message' box (eg - solution to Homework 3)
  • Press Commit
  • Press the little house again
  • Press Unsynced Commits
  • Press Sync - this will push your changes to github

(c) A.F. Bower (2012)