Share
Tweet
4Nina POVEYDedTotal
105.46
ElementBase
Value
GOE
Total
GOE
Mark
Score
1.3.300.003.30
2.6.400.006.40
3.1.300.001.30
4.0.000.000.00
5.3.000.003.00
6.2.000.002.00
7.5.61x0.005.61
8.3.63x0.003.63
9.3.500.003.50
10.2.600.002.60
11.4.62x0.004.62
12.1.500.001.50
Total Base Value22
37.46
Total Technical Element Score17
37.46
ComponentPCS Mark
1
1
1
1
1
Total Program Component Score (factored by 1.60)1
68.00
18Nina POVEYGBRStartDedTotal
90.0075.10
HUN
🇭🇺
SVK
🇸🇰
CAN
🇨🇦
RUS
🇷🇺
AUT
🇦🇹
USA
🇺🇸
GER
🇩🇪
Judge TSS Tally (+ Ded)17
77.46
18
75.56
16
76.96
20
73.36
19
72.06
14
73.36
15
78.76
ElementBase
Value
GOEHUN
🇭🇺
SVK
🇸🇰
CAN
🇨🇦
RUS
🇷🇺
AUT
🇦🇹
USA
🇺🇸
GER
🇩🇪
Score
1.2A3.300.2011100003.50
2.3Lo+2T6.400.0000000016.40
3.2T1.30-0.1200-10-1-1-11.18
4.2T**0.000.00-------0.00
5.FSSp43.000.0000000003.00
6.ChSq12.000.4211000112.42
7.3Lo5.61x0.0000000005.61
8.2A3.63x-0.60-1-1-1-1-2-2-13.03
9.CCoSp43.500.0000000103.50
10.StSq22.600.1000000112.70
11.2F+2Lo+1Lo4.62x-0.060-1000-104.56
12.LSp11.50-0.30-1-1-10-2-1-11.20
Judge Total TES Tally17
37.86
18
37.56
19
36.96
19
36.96
19
35.66
16
37.36
17
38.36
Total Base Value22
37.46
Total Technical Element Score17
37.10
ComponentHUN
🇭🇺
SVK
🇸🇰
CAN
🇨🇦
RUS
🇷🇺
AUT
🇦🇹
USA
🇺🇸
GER
🇩🇪
Score
Skating Skills18
4.75
21
4.75
14
5.25
21
4.75
18
4.75
15
5.00
15
5.25
18
4.90
Transitions17
4.75
16
4.50
16
4.75
21
4.25
17
4.50
14
4.00
16
4.75
18
4.55
Performance16
5.00
18
5.00
16
5.00
21
4.50
19
4.50
17
4.25
13
5.50
17
4.80
Composition16
5.00
20
4.50
15
5.25
21
4.75
19
4.50
13
4.50
16
4.75
19
4.70
Interpretation13
5.25
17
5.00
17
4.75
21
4.50
19
4.50
13
4.75
16
5.00
17
4.80
Judge Total PCS Tally18
39.60
19
38.00
16
40.00
21
36.40
19
36.40
15
36.00
16
40.40
Total Program Component Score (factored by 1.60)18
38.00

This Calculator is powered by my custom element-score-calculation algorithm, called EVVIE. EVVIE is an acronym for "Element Verification and Validation Interface: EVVIE" (it's a recursive acronym).

The EVVIE algorithm consists of about 3,000 lines of object-oriented Python code. 1

EVVIE's parser is strict. That is, it only accepts valid element codes exactly as they would appear on an official ISU protocol. This is a feature, not a bug.

For example, EVVIE is case-sensitive. If you enter4Finto an Element Name text input box above and click Submit, you will get the score for a quadruple Flip. However, if you enter4f, you will get a syntax error. This is not a bug. One of the goals of EVVIE is to discover any potential errors made by the ISU in their published protocols. Any leniency in the parsing of user input would compromise EVVIE's ability to detect potential future errors by the ISU.

Another example of EVVIE's strictness is the requirement of adjoining+s in combination elements.3A+3Tis a combination jump.3A3Tis a syntax error. Again, this is a desirable feature of EVVIE.

EVVIE is accompanied by an extensive suite of tests which help ensure that EVVIE produces the correct results. That test suite is based on my database of historical ISU scores.

My database of historical ISU scores includes all scores from the Grand Prix Series, ISU Championships, and Olympic Winter Games since the 2010-2011 season. Also included in my database are all Junior Grand Prix Series and Challenger Series scores since the 2016-2017 season. This database of scores contains over 160,000 elements across 9 seasons, from all four disciplines (Men, Ladies, Pairs and Ice Dance). The ISU changes the scoring rules and the Scale of Values nearly every season. EVVIE encodes the distinct rules for each season, and can produce the correct results for the selected season.

After any addition of new scores to my database of historical scores, my test suite is automatically run against the database to confirm that EVVIE produces the same Base Value, GOE Total, and Total Score for each element as were officially awarded by the ISU. This ensures that EVVIE is in agreement with the ISU's own internal element-score-calculation algorithm. EVVIE's element score results match the scores officially awarded by the ISU for 100% of the elements in my database. There are no known errors.

If you discover an error in any aspect of EVVIE's results, I would LOVE to hear about it so I can fix it. Thank you!


  1. EVVIE is built using traditional compiler techniques. It works like this: the user input is first tokenized by a Tokenizer class to produce Tokens. From those tokens, a Parser class builds a Node tree representation of the given element. Simple elements like, say, aFCSp4are represented by a single node, but combination elements like3Lo+1Eu+3Sare represented by a node tree – a parent node with children (3 in this case). That node tree is then traversed by a Visitor class which calculates the corresponding Base Value, GOE Total and Total Score while also building a Base Value Description along the way.

Follow us on TwitterTools

See a problem with the scores on this page?
Help us fix it by reporting it.