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

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

• 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

6. Improving the Report and It's content.

7. Adding Content to Wiki