For more detailed tasks see each team's meeting minutes.

Gantt Chart

*If you don't have the working algorithm, assign order of magnitude values to variables. For instance orifice diameters could all be specified as 2 cm until later in the semester when you get to the code.

Definition of Tasks

0. Adding Pages to Watch

• ASAP 
• Adding a page to watch on the wiki sends you an email whenever a page is updated. To add a page on the wiki as one you are watching click on the envelope next to the star on the top right of the page.
• Add this page to watch.
• You should also consider adding to watch: the assignments page under Team Organization, your team pages, and the integration page corresponding to your program.

1. Working Program and Sub-Program Skeletons:

•  Due February 22.
•  The Master Program handles input from the engineer and references and calls the MathCAD Programs named Unit Processes, Hydraulic Design, AutoCAD, and Report Compiler. The subteams are responsible for the Program corresponding to their team name. This means that your entire program will actually be a function, so the MathCAD files you have now may need to be modified so that a single driver function called YourSubteamName(Input1,Input2,...,InputN) will return the necessary information to the master program so that it can be entered as an input to the next function called.
• The inputs that will be given to each program are listed on the corresponding inputs wiki page under integration and the program details.
• The values that need to be returned to the program are listed in the output page. The outputs should be returned in an array. Since the outputs will likely have different units you will need to normalize each by it's unit. For example if dim.tank has units of meters it should be divided by meters. It shouldn't matter that some variables are arrays and some are scalar. It is necessary to make sure that the units that are used to nomalize the outputs are the same as those used to convert back.
• You will likely have other functions that you need to call in your main driver function for your program. If it represents a major component of the design like flocculator design for unit processes or launderer design for hydraulic design, it would be good to make it a separate mathCAD file to hold that function. Functions that play smaller roles can simply be defined within the program after the driver function. 
• In addition to the skeletons for the driver functions like UnitProcessses(Q.plant, width.baffles) you need to have the skeletons formed for your sub-programs like flocculatordesign(inputs). It is important to know which variables will be input and output to/from your sub-programs.
• It is okay if the parameters for your sub-programs change.
• All that is due, at first, is the skeleton of the programs, but if you have the algorithms already and have the time, do not hesitate to include them.
• So basically all this is is creating mathcad files, writing basic driver functions that will recieve inputs, return reasonable outputs (but with made up values), and subprograms with the same. The goal is to put it together to make sure that everything connects right, before we worry about how it is actually defined.

2. Teach-In:

• Scheduled for Wednesday February 27th.
• Will define at next integration meeting.

3. Finish All Programs with Correct Algorithms

• Due February 29. 
• Now that all the skeletons are made, They just need to be filled in. I trust you know best what needs to go on here.

4. Putting it all Together, Testing, Tweaking, and Peer Review

• The Month of March 
• As integration team leader I will take charge of compiling the programs you have written. If I run across any problems I will call on you to help.
• In the mean time we will be subjecting all of our designs to peer review. We haven't concreted the procedure we will use to do this, but just imagine in-depth teach-in like meetings and an official signer who okays the algorithm. You will need to explain your algorithms line by line to a group/and or a single person. You will also need to be on the flip side and critically analyze other algorithms.
• More Details TBA.

5. Trying Out New Designs

• April 1 and on.
• During this time we will be making new designs. The Tamara plant should be about finished and we will need new designs for APP to start making budgets.

6. Improving the Report and Its Content.

• April 1 and on. 
• I envision the Report for the engineers will be a beast. It should contain all sorts of information about how the plant works, how it needs to be kept up, and the design parameters we came up with. Considering each part of the plant warrents a report in itself it could be fairly long.
• I put a rough outline of what could be included in the report on the wiki page for the Report Generator.
• Each team should contribute to this report. You can anticipate that you will be responsible for the parts most relevant to the parts of the plant you design.
• We can assign parts of the report to work at a later meeting.
• If you would like to help with the Materials List too, that would be helpful.

7. Adding Content to Wiki

• Throughout the semester
• While making the MathCAD functions and files you need to be documenting their content on the wiki.
• It might be a good idea to add this information and any new pages under the integration pages already set up describing inputs and outputs.
• You need to include thorough descriptions of the algorithms, the functions you've created and their purpose, inputs, outputs, and any other significant information.
• The layout of the wiki pages should mimic how the MathCAD files are referenced. For instance U.P., H.D, A.CAD, and R.G are all children of the Master Program wiki page since they are referenced by the Master Program. Exceptions to this rule are for the Pipe Database and the Fluids Function File since they are referenced by multiple programs under the Master Program they are children of the Master Program. I think.
• Remember that the content you add to the wiki is considered in your final grade.

8. Surveys

• I am going to put together surveys that I will e-mail to you once a week.
• The purpose of these surveys is for me to assess the progress that is being made, to make sure that everyone understands what they are doing and supposed to be doing, to give you an opportunity to offer comments on what you think is going well, what you think might work better, variables or functions that you might need changed somehow, if you have enought to do, and if you need anything additional of me. I'll try to keep them fairly short.
• I would appreciate quick and honest responses.