Physics 434 Syllabus

• Course: PHYS434, B280
• Instructors: Toby Burnett, Durmus Karatay
• Text: Hands-On Introduction to LabVIEW for Scientists and Engineers, John Essick Amazon U Bookstore
• Software: Labview 2014
• Need help?
  • Look through and create issues
  • Email Durmus or Toby for 1-on-1 help, or to set up a time to meet

Course Description

Understand how to use computers for experimental control, data acquisition, and data analysis, and understand the principles involved in each. Review and consolidate electronics knowledge. Learn the standard tool LabVIEW.

Homework/Projects

All assignments are listed within the Course Outline.

These are usually two-person partnerships. It should be written and submitted as a joint effort. The same grade goes to each. Text corresponding to an introduction and conclusions must be written into the VI.

Workflow

1. Fork the repository for the exercise/project (found under github.com/uw-labview)
2. Clone the repository to your computer
3. Modify the files to complete your solution
4. Make sure all of your project is committed
5. Push/sync up to GitHub
6. Create a pull request on the original repository by the due time (generally the start of the following class)
7. You can continue to push fixes and improvements until the close date (listed in Classes) – just add a comment in the pull request to let me know it's been updated.

Feedback will be given in the pull request, so please respond with your thoughts and questions! You are welcome to open the pull request as the work is still in-progress if you are stuck and want to ask a question – just mention @ukaratay with the question.

Requirements

These apply to real life, as well.

• Must apply "good programming style"
  • See Rules to Wire By
  • Optimize for readability
  • Documentation
• Bonus points for:
  • Creativity (as long as requirements are fulfilled)

Course Outline

Week 1

Chapters 1 and 2, Problems 1.4 and 2.6 are due in class time.

Homework (Due by 10/7/14)

Chapter 2 Do-it-Yourself

Pairing Tips

• The person who's less experienced/comfortable should have more keyboard time
• Switch who's "driving" regularly
• Make sure to save the project and send it to both people

Grading

• Class Participation (10%)
• Homework (50%)
  • Functionality (25%)
  • Documentation (12.5%)
  • Readability (12.5%)
• Project (40%)

Statements on Plagiarism

UW

In computer programming classes, borrowing computer code from another student and presenting it as your own. When original computer code is a requirement for a class, it is a violation of the Universityʹs policy if students submit work they themselves did not create. 

Instructors

You are encouraged to learn from the work of your peers. This class is structured such that all solutions are public. We won't hunt down people who are simply copying-and-pasting solutions, because without challenging themselves, they are simply wasting their time and money taking this class.

License

This work and all other materials under https://github.com/uw-labview are licensed under a Creative Commons Attribution 4.0 International License. The Markdown boilerplate and some of the statements for the syllabus have been taken from advanced-js.