User Tools

Site Tools


Sidebar

projects

wcp1 (due 20240124)
pct0 (bonus; due 20240125)
pct1 (bonus; due 20240125)
abc0 (due 20240131)
btt0 (due 20240131)
pct2 (due 20240131)
wcp2 (due 20240131)
mpg0 (due 20240207)
pct3 (bonus; due 20240207)
wcp3 (due 20240207)
mpg1 (due 20240214)
pct4 (due 20240214)
wcp4 (due 20240214)
bwp1 (bonus; due 20240228)
mpg2 (due 20240228)
pct5 (bonus; due 20240228)
wcp5 (due 20240228)
cgf0 (due 20240306)
gfo0 (due 20240306)
pct6 (due 20240306)
wcp6 (due 20240306)
cgf1 (due 20240313)
pct7 (bonus; due 20240313)
wcp7 (due 20240313)
cgf2 (due 20240320)
pct8 (due 20240320)
wcp8 (due 20240320)
pct9 (bonus; due 20240327)
wcp9 (due 20240327)
bwp2 (bonus; due 20240410)
cgf3 (due 20240410)
gfo1 (due 20240410)
pctA (due 20240410)
wcpA (due 20240410)
pctB (bonus; due 20240417)
waq0 (due 20240417)
wcpB (due 20240417)
pctC (due 20240424)
waq1 (due 20240424)
wcpC (due 20240424)
pctD (bonus; due 20240501)
wcpD (bonus; due 20240501)
gfo2 (due 20240508)
pctE (bonus; due 20240508)
wcpE (bonus; due 20240508)
EoCE (due 20240516)
haas:spring2024:data:projects:dlq0:metrics

dlq0 Project Class Status Summary

Provided as a means of better understanding trends, the following charts and tables will visualize various indirect data points that, while not indicative of success (or deferrance thereof), may well correlate with such. Plus, being able to see trends on a large scale can aid in better decision making and planning.

dlq0 lifespan

Projects are typically released on Tuesday, and are due by the end of the following Wednesday. This allows for at least nine days to work on the project without penalty.

Following the due date, there is a period of three days (the late, or past due period), where 25% is docked each day, after which the project neither has nor can earn any value.

Here is a table with the pertinent dates for this project (the day number is the one that is also found on the x-axis of the graphs).

20171107 20171108 20171109 20171110 20171111 20171112 20171113 20171114 20171115 20171116 20171117 20171118
0 1 2 3 4 5 6 7 8 (TODAY) 9 10 11
start date due date late day 1 (25% off) late day 2 (50% off) late day 3 (75% off)

Typically, any and all activity taking place to the left of the due date is preferable; it tends to indicate less procrastination and has the likelihood of involving better time management.

Progress By Day (Individual)

<charter> title = dlq0 Individual Progress size = 600×400 align = center type = bar XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

45,4,1,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,170,0,0,13,2,49,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,46,68,0,0,0,0 0,0,97,64,52,0,1,50,0,0,0,0 0,0,0,0,0,0,46,104,15,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,42,0,0,0,0,0 0,0,0,0,0,0,0,64,114,0,0,0 0,0,11,8,0,0,0,0,0,0,0,0 0,105,8,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 10,30,0,0,0,0,0,0,0,0,0,0 0,0,39,0,0,0,32,158,4,0,0,0 </charter>

Each line represents an individual class member's progress on the project. The more active they are, the higher the bar will rise.

The busier the day looks, the more active a development day it is by more of the class. And the more left shifted the activity, the less procrastination (lefterer is betterer).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

Progress toward Completion (Individual)

<charter> title = dlq0 Individual Completion Progress size = 600×400 align = center type = line XAxisName = Day YAxisName = Correct Unit Test Results shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

77,77,77,77,77,77,77,77,77 0,0,0,0,0,0,0,0,0 0,0,0,41,41,41,42,42,42 0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,8,60,60 0,0,44,55,74,74,74,74,74 0,0,0,0,0,0,33,75,75 0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,77,77,77 0,0,0,0,0,0,0,23,67 0,0,45,77,77,77,77,77,77 0,0,77,77,77,77,77,77,77 0,0,0,0,0,0,0,0,0 0,77,77,77,77,77,77,77,77 0,0,34,34,34,34,36,65,65 </charter>

Each line represents the progress of a class member toward full implementation (as defined by the unit tests performed during a 'make check'). The higher the line, the more unit tests are being passed.

The busier the day looks, the more active a development day it is by more of the class. And the more left shifted upward activity starts, the better (as it shows work is well underway).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

Progress By Day and Quantity (Together)

<charter> title = dlq0 Class and Quantity Progress size = 600×400 align = center type = barStacked XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

45,4,1,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,170,0,0,13,2,49,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,46,68,0,0,0,0 0,0,97,64,52,0,1,50,0,0,0,0 0,0,0,0,0,0,46,104,15,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,42,0,0,0,0,0 0,0,0,0,0,0,0,64,114,0,0,0 0,0,11,8,0,0,0,0,0,0,0,0 0,105,8,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 10,30,0,0,0,0,0,0,0,0,0,0 0,0,39,0,0,0,32,158,4,0,0,0 </charter>

Each bar represents the total class activity on the project for the given day. The higher and more colorful the bar, the more activity by more people took place (upperer as well as lefterer is betterer).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

Class Member Activity Per Day

<charter> title = dlq0 Class Progress size = 600×400 align = center type = barStacked XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

10,10,10,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,10,0,0,10,10,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,10,10,0,0,0,0 0,0,10,10,10,0,10,10,0,0,0,0 0,0,0,0,0,0,10,10,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,10,0,0,0,0,0 0,0,0,0,0,0,0,10,10,0,0,0 0,0,10,10,0,0,0,0,0,0,0,0 0,10,10,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 10,10,0,0,0,0,0,0,0,0,0,0 0,0,10,0,0,0,10,10,10,0,0,0 </charter>

Each day shows the quantity of project builds per day of the project's lifespan.

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing. As such, the lefterer and upperer the betterer.

NOTE: Activity is measured in units of a user performing build activities on the project, and counted up to one time per user per day.

Project Lifecycle Stats (Individual)

<charter> title = dlq0 Individual Project Duration size = 600×400 align = center type = bar XAxisName = Person YAxisName = Minutes shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

202 0 6466 0 1630 7622 2139 0 83 913 1687 805 0 1918 8020 </charter>

Each bar represents the number of minutes taken from initial upgrade to project through project submission (final submission).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

Obtains/Upgrades/Updates/Submits By Day

<charter> title = dlq0 Lifecycle Progress size = 600×400 align = center type = barStacked legendEntries = obtain, upgrade, update, submit XAxisName = Day YAxisName = Activity shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,0,0,0,0,0,0,0,0,0,0 20,10,30,10,0,0,40,10,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 10,10,10,10,0,0,20,30,0,0,0,0 </charter>

Each day shows the quantity of project obtains, upgrades, revision updates, and submissions per day of the project's lifespan.

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing. As such, the lefterer and upperer the betterer.

NOTE: Activity is measured in units of specific actions taken (upgrading, submitting, etc.), and counted once per user per day.

Status Page last updated: Wed Nov 15 13:29:45 EST 2017

haas/spring2024/data/projects/dlq0/metrics.txt · Last modified: 2017/11/15 18:29 by 127.0.0.1