Algorithm-Reasoning behind Writing Quality Lab Reports

High Level Algorithm- Writing Quality Lab Reports (Control Systems ViewPoint)
Inputs (How I Learn)
1.Raw Data/facts = acquired from google search
2.Information = filtered raw data based on mathematically constrained conditions
3.Knowledge = organized raw data acquired through (reading, google search &
observation)
4.Understanding = converting the knowledge into a documented algorithm/procedure
with reasoning.

Transfer function (Logic)

Note: Without documentation the algorithm/procedure looses repeatability (same
results + old algorithm)
Note: Without reasoning the algorithm/procedure looses reproducibility (same result +
new algorithm)

Output (Writing detailed documents)

..... documentation is my subconscious way of retaining understanding despite
variations caused by repeatability, reproducibility & short or long term memory
Algorithm-Reasoning behind Writing Quality Lab Reports
Appendix (Reasoning based thought process)
Analysis- Statistical applied to Code Review:
1. Measuring Variability aka precision
Variability is the amount of imprecision.
Variability has two parts: repeatability & reproducibility

1.1Repeatability (tool variability)

........here tool = IDE
Variation in Code Output due to same source code (setup), same users (operator) & varying
IDE’s (tool).
Repeatability (IDE variability)
........... out of scope for code review
……….Without documentation the Code Review Algorithm looses repeatability (same results
+ old algorithm); outsiders cant understand my work to know what I did aka looses
repeatability factor

1.2Reproducibility (user variability)

........ here user = developer
Variation in Code Output due to same source code (setup), same IDE (tool) & varying users
(operators)
Reproducibility (user variability)
.......... detailed documentation is a MUST because it provides traceability and understanding
needed to provide valuable feedback during code review 
……….Without reasoning  the Code Review Algorithm looses reproducibility (same result +
new algorithm); outsides cant understand my work well enough to improve it by giving a
new algorithm aka looses reproducibility factor

2.Measuring Bias aka accuracy

2.1Accuracy(setup variability)
.......here setup = source code output
Bias is the amount of inaccuracy given by the %error formula
% Error= (theory-actual)/(actual) where actual = code output based on the assignment
instruction sheet and theory = code output based on the created source code
Accuracy(code output variability)
.......... without comparing if the Report reflects alignment with the Instruction Sheet we
don’t know if what we wrote is going to give us a good grade. A good report reflects 80-100%
alignment with the Instruction Sheet while a bad report reflects 20-50% alignment with the
Instruction Sheet.