Milestone 1

Due: Thursday, October 22nd at 11:59 PM

You will now begin your final project to develop a Python package for automatic differentiation. Please get together with your project group and complete the tasks below for Milestone 1.

Git Conventions

We expect all work from this point onwards do be done on feature branches and merged into master via Pull Requests.

Do not push anything directly to the master branch.

Please "approve" each other's branches and merge with a GitHub Pull Request.

The teaching staff will penalize teams that repeatedly push directly to master.

Steps to complete

1. Within your docs subdirectory, create a file called milestone1. The type of file is up to you and your group. Two good choices are markdown (milestone1.md) or a Jupyter notebook (milestone1.ipynb).
   1. Read the Milestone1 Document section below for what your milestone1 document should contain.
   2. Your milestone1 document submission should be in the following format:

cs107-FinalProject/
             README.md
             docs/  
                  milestone1
             ...

The teaching staff will only be able to give you a grade if you follow the exact structure just outlined!

Milestone1 Document

You must clearly outline your software design for the project. This is the main deliverable for this milestone. We are checking to make sure you have a realizable software design, that you understand the scope of the project, and that you understand the details of the project. Here are some sections your group should include in your document along with some prompts that you will want to address.

Introduction

Describe the problem the software solves and why it's important to solve that problem.

Background

Describe (briefly) the mathematical background and concepts as you see fit. You do not need to give a treatise on automatic differentation or dual numbers. Just give the essential ideas (e.g. the chain rule, the graph structure of calculations, elementary functions, etc). Do not copy and paste any of the lecture notes. We will easily be able to tell if you did this as it does not show that you truly understand the problem at hand.

How to Use PackageName

How do you envision that a user will interact with your package? What should they import? How can they instantiate AD objects?

Note: This section should be a mix of pseudo code and text. It should not include any actual operations yet. Remember, you have not yet written any code at this point.

Software Organization

Discuss how you plan on organizing your software package.

• What will the directory structure look like?
• What modules do you plan on including? What is their basic functionality?
• Where will your test suite live? Will you use TravisCI? CodeCov?
• How will you distribute your package (e.g. PyPI)?
• How will you package your software? Will you use a framework? If so, which one and why? If not, why not?
• Other considerations?

Implementation

Discuss how you plan on implementing the forward mode of automatic differentiation.

• What are the core data structures?
• What classes will you implement?
• What method and name attributes will your classes have?
• What external dependencies will you rely on?
• How will you deal with elementary functions like sin, sqrt, log, and exp (and all the others)?

Be sure to consider a variety of use cases. For example, don't limit your design to scalar functions of scalar values. Make sure you can handle the situations of vector functions of vectors and scalar functions of vectors. Don't forget that people will want to use your library in algorithms like Newton's method (among others).

Document Length

Try to keep your report to a reasonable length. It will form the core of your documentation, so you want it to be a length that someone will actually want to read. Since some of you will use Markdown while others will use Jupyter notebooks and still other group use Latex, we cannot standardize a page length. Use your best judgement. You will only lose points if your document is overly terse (e.g. you do not discuss aspects outlined above) or unbearably long (e.g. you provide so much information that it obscures the message).

Additional Comments

There is no need to have an implementation started for Milestone 1. You are currently in the planning phase of your project. This means that you should feel free to have a project_planning repo in your project organization for scratch work and code.
The actual implementation of your package will start after Milestone 1.

Final Deliverables

1. The docs/ directory should include a document called milestone1 (the extension is up to you, but .md or .ipynb are recommended. Details on how to create milestone1 are provided in the Milestone 1 Document section above.

Grading breakdown

Total: 15 points