Custom Scoring Setups
Overview
FS Manager is designed with hosting ISU competitions in mind, and thus only includes ISU standard scoring parameters and verification rules. However, it is possible to customise both of these through the configuration of XML files.
Custom Scoring Setups
Custom scoring parameters (i.e., factors and deduction multipliers) can be programmed into FS Manager and recalled for any competition that is not set as an “International Competition”. The general configuration can be seen below.
Example scoring setup
<Setups xmlns="http://tempuri.org/SetupDefinition.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Title="BIS Custom Scoring" Version="1.1.0" xsi:schemaLocation="http://tempuri.org/SetupDefinition.xsd SetupDefinition.xsd">
<Year Value="2425">
<CustomDifficulties>
<CustomDifficulty>
<!-- Defines category name -->
<Name>Beginner</Name>
<ShortName>B</ShortName>
<!-- Defines code used in ODF messages and when generating documents. Must be unique. -->
<RscCode>NATBEG</RscCode>
<!-- Determines sort order in FS Manager. Must be unique. -->
<MapIndex>a</MapIndex>
<CalculateFallDeduction>true</CalculateFallDeduction>
</CustomDifficulty>
</CustomDifficulties>
<Competition>
<!-- Determines the nature of the category and the difficulty it is associated with. -->
<Category Type="Men" Difficulty="Custom" CustomDifficulty="Beginner">
<Name>Beginner Boys</Name>
<Segment Type="Free">
<!-- This determines the name of the segment when it is created. For custom scoring, this cannot be overwritten. -->
<Name>Free Skating</Name>
<ShortName>FS</ShortName>
<AdditionalTime>Add10Sec</AdditionalTime>
<CreditForHighlight>1</CreditForHighlight>
<GeneralComponentFactor>1</GeneralComponentFactor>
<GeneralSegmentFactor>1</GeneralSegmentFactor>
<Priority>ProgramComponentScoreDecides</Priority>
<PerformanceTime>PT1M30S</PerformanceTime>
<StartSecondHalf>PT0S</StartSecondHalf>
<WarmupGroup>PT2M30S</WarmupGroup>
<ComponentFactors>
<!-- A component factor block is necessary for each factor, but is ommitted here for brevity. -->
<ComponentFactor>
<Factor>1.67</Factor>
<MapIndex>0</MapIndex>
<Name>Composition</Name>
<ShortName>CO</ShortName>
<Type>0</Type>
</ComponentFactor>
<!-- Other factors defined in this space... -->
</ComponentFactors>
<DeductionFactors>
<!-- As with components, a DeductionFactor node is needed to define each deduction. -->
<DeductionFactor>
<Factor>0.5</Factor>
<IsMajorityDeduction>false</IsMajorityDeduction>
<MapIndex>4</MapIndex>
<Name>Falls</Name>
<Responsible>TechnicalPanel</Responsible>
<Type>10</Type>
<Value>-0.5 per Fall</Value>
</DeductionFactor>
<!-- Other deductions defined in this space... -->
</DeductionFactors>
<!-- VerificationRule determines whether to use ISU rules for redefined stock categories, whether to disable verification or to search for custom verification. -->
<VerificationRule>None</VerificationRule>
</Segment>
</Category>
</Competition>
</Year>
</Setups>
Download custom scoring setup
The following file is considered to be in an alpha state, and any event organisers who choose to use it do so at their own risk! This file is provided with no warranty, stated or implied.
To download the scoring setups used at BIS events, click here.
Custom verification rules
Custom verification rules allow custom elements to be considered valid or invalid by FS Manager, and for custom program content requirements to be automatically assigned valid or invalid by the computer. However, documentation for this process is very scarce, and, as such, no advice is provided here for the majority of the functionality possible with these files.
An additional application of the custom verification is to enable custom pattern dances to be automatically loaded into a properly configured FS Score system, and validated by FS Manager. An example of this follows below.
Example pattern dance verifications
<?xml version="1.0" encoding="utf-8"?>
<!-- Here we can denote version and name to be displayed within FS Manager -->
<Validations xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://tempuri.org/RuleDefinition.xsd RuleDefinition.xsd" Title="BIS Solo Dance" Version="1.0.0"
xmlns="http://tempuri.org/RuleDefinition.xsd">
<Year Value="2425">
<!-- This is where more complex verification rules would live -->
</Year>
<PatternDances>
<!-- Define the dance name within FS Manager and whether it has keypoints or not -->
<Dance Name="Golden Skaters Waltz" KeyPoints="No" Type="1" Id="1">
<Or>
<!-- The sequences and sections of the dance are defined here. Keypoints should not be included here. -->
<Case>GSW1Sq</Case>
<Case>GSW2Sq</Case>
</Or>
</Dance>
<Dance Name="Riverside Rhumba" KeyPoints="No" Type="2" Id="3">
<Or>
<Case>RR1Sq</Case>
<Case>RR2Sq</Case>
</Or>
</Dance>
<Dance Name="Novice Foxtrot" KeyPoints="No" Type="4" Id="9">
<Or>
<Case>NFN1Sq</Case>
<Case>NFN2Sq</Case>
</Or>
</Dance>
</PatternDances>
</Validations>
Download pattern dance validation
The following file has been used successfully at previous events, but any event organisers who choose to use it do so at their own risk! This file is provided with no warranty, stated or implied.
To download the scoring setups used at BIS events, click here.
Custom Elements
When configuring custom elements, there are two main methods to use: manual entry through the FS Manager GUI, or bulk upload from an XML file. Both are discussed below.
Custom Elements through the FS Manager GUI
Custom elements can be entered through the Elements tab of FS Manager. To do this, click New (Fig. 1).
Figure 1. New element button within FS Manager.
This opens the element entry interface, where you can fill out the details of your elements. For each element, you must select the category, group and type. Only once all three of these are selected will the element be registered as Custom (Fig. 2).
Figure 2. Element configuration interface, with dropdown menus displayed.
Once you have selected all of the categories and entered your element name, click Save (see Fig. 1). It is important that you always have a “No Value” variant of any element you create, unless you have an explicit reason to exclude this.
In the example, we are creating the SOV for the Extremely Cool Spin, the SOV table for which is below:
Extremely Cool Spin
| -5 | -4 | -3 | -2 | -1 | Base | 1 | 2 | 3 | 4 | 5 |
|---|
| XeSpB | -0.85 | -0.68 | -0.51 | -0.34 | -0.17 | 1.70 | 0.17 | 0.34 | 0.51 | 0.68 | 0.85 |
| XeSp1 | -0.95 | -0.76 | -0.57 | -0.38 | -0.19 | 1.90 | 0.19 | 0.38 | 0.57 | 0.76 | 0.95 |
| XeSp2 | -1.05 | -0.84 | -0.63 | -0.42 | -0.21 | 2.10 | 0.21 | 0.42 | 0.63 | 0.84 | 1.05 |
To do this, we first create the No Value variant (XeSp), then XeSpB, XeSp1 and XeSp2. For each element, fill out the Base Value and for Calc (Fig. 3, right hand side). For elements where the grade of execution bonuses increase as the element level increases (as is typical for spins), this will be the same value in each box. After entering the Base Value and for Calc values, click Save, then click Calculate SOV, followed by clicking Save again. This will fill out the SOV boxes according to standard SOV scaling. If your element uses atypical SOV scaling, you must enter each value manually.
Figure 3. Examples of XeSp Scale Of Values entered into FS Manager.
If you are creating an element where SOV bonuses remain constant with changing levels of element (e.g., twizzles in Ice Dance), Base Value represents the base value of the element level (i.e., GOE +0), and for Calc represents the base value that is used to calculate the GOE bonuses (which is commonly equal to the base value of the level 1 version of the element). An example of this is in Figure 4.
Figure 4. Examples of elements with different Base Value and for Calc values. Note that the GOE scales for ATwW1 and ATwW2 are the same as the for Calc value is 3.12 in both cases.
Important notes
Some important points to note:
- Once an element’s category is set, it cannot be changed.
- Elements will only be valid for the category which they are created. For example, an element created for Rhythm Dance will not be valid in Free Dance. This also applies to pattern dances, where a pattern dance created for Ice Dance will not be valid for Solo Dance.
- If the elements are planned to appear on the FS Score judging interface, additional configuration of the interface must be performed separately. This procedure will only affect the validity of the element within FS Manager.
- Custom elements can interact strangely with verification rules. Always double check results before they are signed off when using custom elements.
Custom Elements in XML Documents
This section is currently being updated. Check back soon!
For a more portable solution, XML files can be written to define custom elements. These should be loaded after the master elements list that ships with FS Manager is loaded, and will not affect the element checksums unless a custom element redefines an existing element. The below procedure will load custom elements in addition to the stock elements:
- Load the stock elements XML into FS Manager. This is found in the
MasterData folder of the FS Manager install (default: C:\SwissTiming\OVR\FSManager\MasterData) - Load the custom elements XML into FS Manager by the same method. Once loaded, this should produce a popup showing how many new elements have been added and how many have been modified. Any modifications will affect the element list checksum, while additions do not.
Custom element annotated example
<!-- This element version is ignored for custom elements -->
<ISUCalcFS elm_version="2425.4">
<!-- Custom elements must be enclosed within a Custom_Element_List node, or they will delete the standard elements from the database -->
<Custom_Element_List>
<!-- ELM_ID must be unique -->
<!-- ELM_NAME defines the long name printed in FS Manager -->
<!-- ELM_SNAME defines the element code that is used to assign a value to the element -->
<!-- ELM_SNAMWL defines the element name without a level, applicable to elements like spins (i.e., if ELM_SNAME was SSp4, ELM_SNAMWL would be SSp) -->
<!-- ELM Group defines the category types which the element can be performed in -->
<!-- ELM_SORT is an ID that is used to sort the elements in the SOV printout. It should be unique for clarity -->
<!-- ELM_CALCGR determines the grouping for pattern dances -->
<!-- ELM_VAL4 determines the element's calculation base value -->
<!-- ELM_CALCBV determines the calculation base value for GOE calculations (e.g., for Solo Dance edge elements where GOE bonuses are the same for levels 1-4) -->
<!-- ELM_TYPE determines the element type within FS Manager, though this does not seem to affect the way the element behaves when used in competition -->
<Element ELM_ID="4000" ELM_NAME="Single Axel (Half Bonus)" ELM_SNAME="1Ah" ELM_SNAMWL="1Ah" ELM_SORT="BISF001" ELM_GROUP="S" ELM_CALCGR=" " ELM_VAL4="1.6" ELM_CALCBV="1.1" ELM_TYPE="Jump"/>
</Custom_Element_List>
</ISUCalcFS>
BIS Custom Elements
Download BIS custom elements for 25/26 season
The following file has been prepared with the greatest care and attention to detail, but any event organisers who choose to use it do so at their own risk! This file is provided with no warranty, stated or implied.
To download the custom elements XML, click here.