\documentclass[letterpaper,12pt]{report} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \usepackage{amsmath,amsfonts,amssymb,graphicx} \usepackage{enumitem} \usepackage{float,empheq} \usepackage{color} %\usepackage{hyperref} %\usepackage{wrapfig,picinpar} \usepackage[letterpaper,margin=1in]{geometry} \usepackage{wallpaper} \newcommand{\gap}{\vspace{0.05in}\noindent} \newcommand{\R}{\mathbb{R}} \newcommand{\Z}{\mathbb{Z}} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \begin{document} \section*{Principles of Optimization -- Spring 2018 \\ Collaborative Project Details} This document clarifies the expectations and requirements for the collaborative project portion of Principles of Optimization. The course is listed as MATH364 at Washington State University and MATH490 at Lewis-Clark State College. All correspondence should be directed to \textit{both} Dr. Heather Moon (hamoon@lcsc.edu) and Dr. Tom Asaki (tasaki@wsu.edu). \paragraph{Project Concept.} Optimization projects are intended to give students the opportunity to apply their accummulated skills and knowledge to a non-trivial optimization task, build collaborative skills, research and explore a realistic (or real) optimization scenario, demonstrate proficiency in mathematical writing. The project will give you an opportunity to accomplish an optimization task beyond (in size, depth of exploration, time commitment and experience) that of the standard textbook problem. \paragraph{Tasks.} Students are expected to complete three joint tasks a Project Design Proposal, a Draft Project Report and a Final Project Report. \paragraph{Grade Basis.} The Project Design Proposal, effectiveness of collaboration, Draft Project Report and Final Project Report will be worth 10\%, 10\%, 10\% and 20\% of your course grade, respectively. Note that this breakdown is different than stated in the original course syllabi. We have made this change in order to better assess your work. \newpage \subsection*{\center Project Design Proposal} \paragraph{Due Date:} March 15, 10:00PM, by email to both professors. Please feel free to submit at any earlier day or time. Late submissions may incur \textit{significant} score reduction at the discretion of the instructors. \paragraph{Format:} Typeset using \LaTeX~report document class -- no exceptions. \paragraph{Requirements:} The proposal should be a concise semi-technical discussion of your team project plan. It is expected that a good proposal might be written in one page. However, submissions up to three pages are acceptable. There is considerable freedom in the formatting, content and discussion. It is expected that the proposal will include the following. \begin{enumerate}\itemsep-4pt \item Team members and project title. \item Project synopsis. \item Discussion on the history and/or motivation of the project. \item Expected subtasks, estimated timeline and team member roles. \item Clear and measureable goal statements. \item Expected outcomes. \end{enumerate} \paragraph{Score Basis:} Your score will be based on how well the proposal meets the following criteria. \begin{enumerate}\itemsep-4pt \item Adherence to the Project Concept. \item Inclusion of required elements (see above). \item Proper use of both English and mathematical language. \item Clarity in document formatting. \item Clarity of exposition. \end{enumerate} \paragraph{Response:} By Monday, March 19, you will receive a response consisting of \begin{enumerate}\itemsep-4pt \item Assignment score. \item List of required modifications to your proposal (if any). The intent of any modifications is to help make your project both manageable and challenging. \item List of additional questions and areas of interest to us. \end{enumerate} \noindent\textbf{A well thought out and well written proposal is not likely to need modifications.} \newpage \subsection*{Effectiveness of Collaboration} Your collaboration score will be determined after the submission of the final project report. Each team member will receive an individual score. It will be based on effective teamwork skills and practices such as: \begin{enumerate}\itemsep-4pt \item Active participation in completing assigned project tasks. \item Encouraging and allowing others to complete their assigned tasks. \item Regular communication among team members and with both professors. \item Collaborative problem solving. \item Team time management. \end{enumerate} \noindent The main assessment tool will be your regular communication with both professors. \vspace{1cm} \noindent To assist in collaboration, you may wish to consider using Overleaf (overleaf.com) for writing tasks. \newpage \subsection*{Draft Project Report} \paragraph{Due Date:} April 23, 10:00PM, by email to both professors. Please feel free to submit at any earlier day or time. Late submissions may incur \textit{significant} score reduction at the discretion of the instructors. \paragraph{Format:} Typset using \LaTeX\; report document class--no exceptions. \paragraph{Requirements:} The draft project report should be a completed project report that includes: \begin{enumerate}\itemsep0pt \item Introduction \item Model Description \item Solution Path \item Analysis \item Summary \item Appendices \end{enumerate} \paragraph{Introduction:} Your introduction should include a clear description of the problem you are solving. This will contain your goals for this project and other relevant elements from your project proposal. Any changes from your proposal should be clear here as well. \paragraph{Model Description:} Your model description includes all assumptions made, how you formulated your decision variables, objective function, and constraints. A clear model in standard form should be present in this section. Wherever possible, use patterns in constraints to write your constraints in a compact way. For example, your model can be written (possibly more complex) as \begin{empheq}[box=\fbox]{align*} \min_{x}~~~&z=c^Tx\\ \text{s.t.~~~}&Ax\leq b\\ &\bar{A}x=\bar{b}\\ & \ell\leq x\leq u \\ &x\in\R^n \end{empheq} with the various matrices defined in the appendix. Note: This is a very simplified version that may not fit your model at all. Do not aim for this particular boxed model, rather make a concise model that fits your problem. Look at the \LaTeX\; code to see how to do this. \paragraph{Solution Path:} This section should discuss all the details about what happened in determining your solution. A discussion of tests on your problem, concept checks, difficulties and adjustments to resolve these difficulties, and other oddities that may arise for your particular problem. This is the troubleshooting and problem solving part of your process. We want to read about what really happened. This section in \underline{\bf no way} should say, I put the model into Matlab/Octave and got...'' This is \underline{\bf not} a place where you discuss any collaboration difficulties or successes. \paragraph{Analysis:} This section of your report should include your final solution to the problem. You should also give an analysis of your solution. Why do you believe your solution is optimum? How do your assumptions show themselves in your solution? Consider active and inactive constraints. How does the optimal solution help you understand the bigger problem better? Was your solution (totally) unexpected? Why or why not? Are their model improvements beyond the scope of this project that sound interesting? Your problems are vastly different, do not adhere only to the above. These examples are only meant to give you the flavor of your solution analysis. \paragraph{Summary:} Here you should revisit your goals, your problem, and/or the process. If you were submitting this to your employer, what would you like them to know? Write your summary so that you give all information you want to tell your employer in case s/he will only read the summary and does not want to spend a lot of time reading it. If you know your employer might want you to continue in this process, what would you tell him/her to describe how you could improve your results? Again, do not limit yourself to what we have given you here. Your project may be better with different summarizing information. Do what makes sense for your project. \paragraph{Appendix:} Put all detailed definitions (large matrices, data,...) in your appendix. Be sure to label these so that we can reference them if needed. No lengthy word descriptions are required in the Appendix. The purpose of the appendix is to make the report easier and more pleasant to read. Items in the appendix are the large tables and nitty gritty'' details that do not add clarity in your project report. \paragraph{Score Basis:} Your score will be based on how well the project draft meets the following criteria. \begin{enumerate}\itemsep0pt \item Adherence to the Project Concept. \item Inclusion of required elements. \item Project report should be based on a complete study. \item Presentation appearance. \item Clarity in document formatting. \item Clarity of exposition. \item Proper use of both English and mathematical language. \end{enumerate} Note: Be sure to consider possible experimentation prior to submitting your draft project. We may ask you to experiment more if we feel like you have not included enough information about this in your draft. \paragraph{Response:} By Thursday, April 26, you will receive a response consisting of \begin{enumerate}\itemsep0pt \item Assignment score. \item List of required report modifications (if any). If proofreading is necessary, we will only say as much. We will not proofread your report for you. \item List of required additional experimentation (if any). \end{enumerate} All feedback that requires additional work is meant to be included in your final report. You will not be given an option to resubmit your draft report. {\bf We encourage early submissions of draft reports. If you feel your draft is complete, an early submission could give you more time to make any required adjustments.} \subsection*{Final Project Report} \paragraph{Due Date:} May 3, 10:00PM, by email to both professors. Please feel free to submit at any earlier day or time. \textbf{Late submissions will not be accepted.} Your final project has the same expectations and same grading strategies as the draft project report. The only differences are that you include all additional required elements from the draft project report response. \end{document}