moorepants / eng122

Website for my UCD ENG 122 Mechanical Vibrations course

The course website for Jason K. Moore's University of California, Davis Introduction to Mechanical Vibrations course (ENG 122). The rendered version can be viewed at:

http://moorepants.github.io/eng122

This site is generated with Pelican.

Editing Guide

• The website is built using Pelican. Review the Pelican documentation to get familar with how to create pages and articles.
• The source files are in the git branch called master. This is the default branch of the repository. The HTML files are generated via doctr and pushed to the gh-pages branch, which is automatically seved to https://moorepants.github.io/eng122. You should not have to ever manually edit files in the gh-pages branch.
• All articles, pages, and similar content should be written in reStructuredText. See the Sphinx reStructuredText primer to learn the syntax.
• All changes, in general, should be submitted as Github pull requests. Don't commit directly to the master branch. Wait until the build finishes with a green checkmark before merging the pull request.
• Binary Assets such as images, videos, etc should be served from an external hosting site. Ask Jason about using his Dreamhost DreamObject bucket. He'll set it up for multi-user access when needed. Do not commit binary assets to this repository.
• You can edit and add rst files directly in the contents directory using the Github interface. The small pencil on files lets you edit and submit pull requests. Just above the directory view has buttons for adding files. See these instructions: https://help.github.com/en/articles/editing-files-in-your-repository

Building Locally

It is good practice to build the documentation locally so that you can review change before submitting a pull request.

Install pelican with conda (or pip if you prefer):

$ conda install pelican

Clone the theme repository:

$ git clone --branch mechmotum [email protected]:mechmotum/pelican-alchemy.git

Note the path to the theme, e.g.:

/home/my_username/pelican-alchemy

Clone the pelican-plugins repository:

$ git clone [email protected]:getpelican/pelican-plugins.git

Note the path to the plugins directory, e.g.:

/home/my_username/pelican-plugins

Clone this repository and change into the new directory:

$ git clone [email protected]:moorepants/eng122.git
$ cd eng122/

Create a configuration file called local-config.yml and add the full path to where you installed the theme:

$ echo "THEME_PATH: /home/my_username/pelican-alchemy" > local-config.yml
$ echo "PLUGIN_PATHS: /home/my_username/pelican-plugins" >> local-config.yml

Now you can build and serve the documentation with:

$ make devserver

If this succeeds you can open the website in your web browser at http://localhost:8000.

While the server is running you can change the website source files and they will be build automatically. Refresh your web browser to view the changes.

To stop the web server press <CTRL + C> or type make stopserver.

LICENSE

This repository is licensed under the CC-BY 4.0 license.

eng122's Issues

Build fails with newly created environment

Ran into this because I didn't keep the website build environment around and re-created it: getpelican/pelican-plugins#928

Design problem idea: spoon with vibration damping

http://www.liftware.com/steady/

Instructor Recap

Homework

• Book questions are pretty good
• Book questions don't go into as much depth as the midterm
• Most are "go look up formula and use that"
• Homework may not apply to the derivation in lecture
• Some questions hid the concept it wanted to get across
• The problem that you had to dtermein if coloumb or viscous from time tract but not much difference
• Wheel rolling on grond didn't quite connect to base excitation
• Some of the book solutions didn't have detailed answers
• homework length was pretty consistent
• first problem in the last homework was (partianl fraction expansion) was a pain
• make sure that it is required to computation on the howework if you want them to
• most did everything by hand on the last homework
• the electronic grading was ok but not great
• the pdf's just don't come out well
• at the beginning make sure to know what to submit
• have a policy for the ta to know what to do if they don't follow
• canvas was ok, not many comments (speedgrader ended up being pretty nice)
• kenny used the comments: comment tool specifically (a lot easier)
• the comment: would show some text and the loss of points

Notebooks

• thought the in class notebooks were fun

• would groups be better than pairs

• make sure to deal direclty th epeople without laptops so we don't loose them

• make pairs switch

• check into better classrooms for group work

• hard for instructor ot get into isle

• live coding or prepared notebook: liked living coding

• an our a week with a little bit extra is reasoble

• did they learn the vibrations concepts in the computatoin/?

• the indecing the eigenvector bogged them down

• think they got the intergrating eoms numerically

• got lost on the "what is a function?"

• the fillin gthe 3d array was tough

• we should turn more office hours into python sessions (make this happen more explicitly)

• if they have the prebuilt notebook they leass liley to ask questions in calssl (conceptula bakgourN) ... if this was the case it may be less need for the office hour python session

• more time at the beginnin gto get every at the same programming level (maybe two lectures)

• it was a good idea to do it in python: relevant experience to have for the students, more modern that is a real proramming language that can be used in other contexts

• have more time and be prepared ahead of time

• as soon as i posted the homework, kenny would try to do the homework before his office hours

• if i posted homework late then that screwed up kenny's schedule

• it would be helpful to know more about the exam eariier

• having more stuff done ahead of time

check eng 122 hw 7 solutions

Project idea

Saw this presented at a conference:

https://figshare.com/articles/On_coupling_of_vertical_and_longitudinal_dynamics_of_unsuspended_bicycles/5404942

Bicycle ABS over cobblestone.

Use sticky notes for mini quizzes

If the quizzes are multiple choice, we could collect the answers on sticky notes instead of full pieces of paper.

Create a notebook on designing a record player needle

A fun project could be to do some analysis on a record player's needle. This is likely similar to a base excitation problem. I think that they try to keep a constant force on the needle tip given a "wavy" record.

Some technical info:

http://shure.custhelp.com/app/answers/detail/a_id/4072/~/high-fidelity-phonograph-cartridge---technical-seminar

Brainstorming for multiple project ideas for the 2020 course

From #4:

A fun project could be to do some analysis on a record player's needle. This is likely similar to a base excitation problem. I think that they try to keep a constant force on the needle tip given a "wavy" record.

Some technical info:

http://shure.custhelp.com/app/answers/detail/a_id/4072/~/high-fidelity-phonograph-cartridge---technical-seminar

From #5

http://www.liftware.com/steady/

Saw this presented at a conference:

https://figshare.com/articles/On_coupling_of_vertical_and_longitudinal_dynamics_of_unsuspended_bicycles/5404942

Bicycle ABS over cobblestone.

Another thing:
https://www.reddit.com/r/engineering/comments/a4d4wq/seems_like_a_good_example_to_highlight_in_a/

Shows a speed limit that avoids a certain speed range to avoid ice vibration.

Problem 4.22 seems to have a typo

P.T @ M @ P = I is not true.

and

P.T @ K @ P = Lambda is not true. (should be K tilde)

Notebooks as pages

Opening an issue just to keep track of things.

I haven't found a particularly nice way to take a notebook and make a page out of it.

There's liquid_tags, which is bundled with the main pelican-plugins repo. I gave it a quick test and there are some issues with the CSS that I'm not equipped to handle. No activity in the notebook module in 7 months.

There is also pelican-ipynb, which seems a bit more up to date and mentions the CSS situation. I haven't really tried it out yet but will do soon.

fab gh_pages rejects updates

fab gh_pages should handle to people pushing to the gh_pages branch seamlessly, but it seems like it doesn't. It should just force commit on top of that branch and not worry about merging.