# vCalc Competition on ddMMyyyy

Not Reviewed
Dataset / Last modified by Tim on 2015/07/13 11:33
vCalc Competition on ddMMyyyy
Type
Dataset
Category
vCommons
Contents
13 columns
Rating
ID
MichaelBartmess.vCalc Competition on ddMMyyyy
UUID
b6fa5020-c22b-11e4-a3bb-bc764e2038f2
Columns
DatatypeRequired
CompetitorStringYes
MarkupValid&AccurateEnumNo
InputLabelsExistEnumNo
InputInstructionsExistEnumNo
UsedEiCforConstantsEnumNo
BonusForEiEEnumNo
OriginalityOfContentConceptEnumNo
WikiCompletenessEnumNo
WikiQualityEnumNo
DerivationQualityEnumNo
BonusForGraphicEnumNo
OrganizationCalculatorEnumNo
CalculatorAestheticEnumNo
Current statistics
SumAvgMinMax

This data set contains the competition scores for a vCalc content creation competition held for students at the Africa Nazarene University and organized by Professor Edward Ombui.  Students were evaluated on the quality and completeness of vCalc tokens created during the competition.

This data set was also used in conjunction with an equation where each of this data set's evaluation criteria is separately weighted in defining a total score for a competitor.  The weights for that final scoring equation are in the equation inputs for the Competition Analysis equation.

# Usage

Basically, each competitor's name (or the name for a competitor team) will be listed in the data set and their name provides the look-up key for the scoring entry in this data set.

Each row of this data set then is a judge's scoring sheet for a competition entry.

The ranges for all evaluation criteria must be greater than zero.  A zero value would null out the entire equation results.  To not consider an individual evaluation criteria, instead make the weight zero -- which makes logical sense -- and the term will have a zero exponent and become a multiplicative factor of 1 in the competitor evaluation.

The initial set of evaluation criteria are defined as follows:

• MarkupValid&Accurate - [range: 1- low to 5 - high] The ASCIIMath markup should accurately convey the nature of each equation in appropriate math syntax.  Input variables should be included via the vCalc #var syntax.
• InputLabelsExist - [range: 1 - labels don't exist; 3 - labels partially completed or some difficult to interpret; 5 - all labels complete and discernible] Input labels should be succinct but convey to the user the nature of the data in that input field.
• InputInstructionsExist - [range: 1 - input instructions don't exist; 3 - input instructions partially completed or some difficult to interpret; 5 - all input instructions complete and understandable] Input instructions provide sufficient direction to ensure the user inputs appropriate data values.
• UsedEiCforConstants - [range: 1 - Constants manually entered in equations; 3 - Some but not all constants represented by CiEs; 5 - all constants represented by vCalc CiEs] Constants-in-Equations (CiEs) are more dependable than manually entered constants.  This does not apply to simple algebraic integer multipliers.  But for most constants either an existing vCalc constant should be used via drag-and-drop inclusion in an equation or a new vCalc constant should be constructed and likewise used.
• BonusForEiE - [range: 5] Using an equation in equation to leverage the power of vCalc is the best approach and a bonus will be added for use of one or more Equations-in-Equations.
• OriginalityOfContentConcept - [range: 1- low to 5 - high] This competition will value tokens created that show an original use of vCalc.  Topics or interests of student competitors are highly prized in vCalc.
• WikiCompleteness - [range: 1- low to 5 - high]  The wiki page provides the user all the information they need to know why they would use the equation or calculator and how best to use it.  The descriptive text explains what the purpose of the token is up front.  It uses important keywords so that the content can be found both by vCalc and Internet search engines.  It gives relevant background including historical information where appropriate.
Descriptive material may be quoted from other sources, including web sites but ONLY if the source provides an appropriate licensing scheme compatible with vCalc's use of the Creative Commons Attribution-Share Alike License.  The easiest way to ensure that the source provides an appropriate licensing scheme is to only copy source material that has noted it uses a Creative Commons Attribution-Share Alike License, which is known to be fully compatible with vCalc's own licensing scheme.  See the competition coordinator if you have any questions pertaining to licensing. All referenced source material must use vCalc footnote macros.

Note that all content from Wikipedia is fair game because all Wikipedia content is licensed under the Creative Commons Attribution-Share Alike License.

Note also that plagiarism, use of copyrighted material, cannot be tolerated and such content used in the competition will be disqualified.

• WikiQuality - [range: 1- low to 5 - high] The descriptive content of the wiki pages will be judged for clarity, general writing style and overall quality in context.
• DerivationQuality - [range: 1- low to 5 - high] Most mathematical formulas benefit from having a derivation provided, to show a user where the equation comes from and what it is based on.  The general quality of the derivation provided will be evaluated.  Many examples exist in vCalc of equations with full derivations and these should be used as examples.
• BonusForGraphic - [range: 3, some graphics provided; 5 - graphics provided for all tokens] Using a graphic is an extremely valuable addition to any equation and so a bonus can be earned for including a personally created custom graphic that contributes to the project.  Creating graphics for some of the project tokens earns partial credit, as does pasting-in graphics from external sources.  Remember, graphics CANNOT be copied unless they satisfy the same Creative Commons Attribution-Share Alike License as all other written content.  Again, see the competition coordinator if you have questions on how to identify graphic content that meets the vCalc licensing requirements.
• OrganizationCalculator - [range: 1- low to 5 - high] The calculator(s) included in the project will be evaluated on their logical organization and labeling to make them useful for all users.  Implications of mobile users and the size of buttons for instance will be considered.   See the competition coordinator for help with making calculators effective in their mobile view.
• CalculatorAesthetic - [range: 1- low to 5 - high] General aesthetic appeal -- uses of colors and other button attributes will be evaluated for calculator aesthetic appeal