Skip to content

slds-lmu/lecture_optimization

Repository files navigation

Optimization in Machine Learning

Course Website Slide Check

How to create a new website repository?

  1. Create a new repository with the name lecture_xyz and select slds-lmu/lecture_template as template repository.
  2. Start editing everything to suite your needs. For important (editing) workflows see the README files in the directories slides, exercises, and code-demos.
  3. Note: When creating new subchapters, it is important to copy the Makefile from one of the existing subchapters into the new one! Otherwise, the automatic rendering will not work.

How to get started with your new lecture repository?

  1. The very basic structure of the template contains
    1. slides: Raw .tex files of your lecture. PDFs are rendered automatically and moved to slides-pdf.
    2. exercises: Raw .tex exercise files. PDFs are rendered automatically and moved to exercises-pdf.
    3. code-demos: Raw .tex files for code demos. PDFs are rendered automatically and moved to code-demos-pdf.
    4. quizzes: Raw .csv files for quizzes.
    5. cheatsheets: Material for cheatsheets (images, source, etc.).
    6. latex-math: Submodule included from github.com/slds-lmu/latex-math.
    7. style: All relevant style files.
  2. Each folder contains a README.md with more details.

General editing workflow

  1. We have two branches, the main and release branch.
  2. Work is exclusively done in a subbranch of the main branch!
  3. When you have finished a task, write a short understandable commit message, the smaller and more precise your commit is the better. PLEASE DO NOT FORCE PUSH PDF FILES! PDFs are rendered automatically via an actions workflow. If you want to skip CI add a tag [skip ci] to your commit (details see here).
  4. Create a PR to the main branch and describe what you have done, reference issues, etc. Also assign a reviewer if necessary.
  5. The responsible person for the lecture then merges the PRs.
  6. A release is done once a while when enough new content was added. Therefore, the main branch is merged into the release branch.

More workflows are described in this gdoc (in German). If you don't have permission, ask one of the responsible pearsons.

Contents, License, Team and Further Info

Please see the main course site.

Help is appreciated and welcome!

We hope to continously improve and expand this course over the coming years. We strongly believe in open source and collaborative work. Please contact us if you think likewise and would like to contribute. See also our contributing guidelines

  • Are you an ML expert and like the course, but have some feedback or consider extending it? Write an email to Bernd and Fabian (see Team page) or Open an issue.
  • Are you a student taking the lecture - either at the LMU or online - and you spotted a typo, think we should rephrase something be or even would like to provide a new quiz question or coding example? Please consider providing a pull request. To do so, please check out the devel branch of the repo and add your fixes there. Writing an e-mail or opening an issue with suggested improvements is obviously very welcome as well!
  • You are none of the above but would like to contribute, get in touch / open issues / create pull requests! We are happy about any help.

License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

We would appreciate if you contact us in case you are re-using our course. Knowing this helps us to keep the project alive. Thank you!