H2 Scoring Limitations

Owned by Rodolfo Melia
Last updated: Sept 07, 2022 by Shrab Sahota (Unlicensed)
2 min read

There are some important limitations to consider.

Combining Scores and Questions

Scores and questions cannot be grouped together. This means that if a score contains a sub-score, it cannot contain questions like this:

 

 

 

This cannot be handled by the PCA as of v1.4.0 and will prevent the Set Up Program functionality from completing the process. To fix the issue in this example, questions Q15, Q16 and Q17 must be stored in another score like this:

Leaving Gaps in the Feedback Order

Another important limitation is the consistency while using Feedback Orders. Feedback Order gaps are not allowed as those may present issues while using the Feedback Module in the Android App, so the PCA validates the Feedback Order of each question to ensure that those are continuous while also presenting recommended fixes.

 

Remember that Feedback Order is the same as Compositive Indicator.

 

In the current example, defining Score 6 would create a Feedback Order gap as all the scores would follow the sequence [ 1, 1.1, 1.2, 2, 2.1, 3, 4, 4.1, 4.2, 6 ], where Score 5 is missing.

Many other scores can generate gaps, but you may be asking why isn't the jump from a score of 1.2 to 2 considered a gap. Gaps at the end of a sub-sequence don't affect the Android App, but adding a score like 1.4 would generate a gap in the sub-sequence [ 1.1, 1.2, 1.4 ] as Score 1.3 would be missing.

 

Nested scores are considered sub-sequences, in this example the nested scores 1.1 and 1.2 are a sub-sequence of Score 1.

 

Below you'll find a table with many examples of correct and incorrect Feedback Order sequences, that may help clarify this concept.

Example

Validity

 

Example

Validity

 

  • 1

  • 2

  • 3

  • 4

  • 5

 

Integer sequences are valid.

 

  • 1

  • 3

  • 4

  • 5

Score 2 has been skipped, generating a gap.

  • 1

  • 2

  • 3

  • 4

  • 5

 

  • 1

  • 2

  • 2

  • 2

  • 3

  • 4

  • 5

  • 6

Scores cannot be duplicated, in this case Score 2 is

repeated several times.

  • 1

  • 2

  • 2

  • 2

  • 3

  • 4

 

  • 1

    • 1.1

    • 1.2

    • 1.3

    • 1.4

  • 2

  • 3

  • 4

  • 5

    • 5.1

    • 5.2

    • 5.3

Combining integer sequences with nested sequences is valid.

 

  • 1

    • 1.1

    • 1.2

    • 1.3

    • 1.4

    • 1.8

  • 2

  • 3

Scores 1.5, 1.6 and 1.7 have been skipped, generating a gap.

  • 1

    • 1.1

    • 1.2

    • 1.3

    • 1.4

    • 1.5

    • 1.6

    • 1.7

    • 1.8

  • 2

  • 3

 

  • 1

    • 1.1

      • 1.1.1

        • 1.1.1.1

        • 1.1.1.2

      • 1.1.2

        • 1.1.2.1

        • 1.1.2.2

    • 1.2

    • 1.3

    • 1.4

Nested sequences inside nested sequences are valid.

 

  • 1

    • 1.1

      • 1.1.1

        • 1.1.1.2

        • 1.1.1.3

    • 1.2

    • 1.3

    • 1.4

Score 1.1.1.1 has been skipped, generating a gap.

  • 1.1

    • 1.1.1

      • 1.1.1.1

      • 1.1.1.2

      • 1.1.1.3

 

  • 1

    • 1.1

      • 1.1.1.1

      • 1.1.1.2

      • 1.1.2

        • 1.1.2.1

        • 1.1.2.2

    • 1.2

    • 1.3

    • 1.4

Skipping a level in a nested sequence is invalid.

The Score 1.1.1 is missing.

  • 1.1

    • 1.1.1

      • 1.1.1.1

      • 1.1.1.2

      • 1.1.2

        • 1.1.2.1

        • 1.1.2.2

  • 12

 

  • 1

    • 1.1

      • 1.1.1

        • 1.1.1.1

          • 1.1.1.1.1

            • 1.1.1.1.1.1

            • 1.1.1.1.1.2

There's no limit to the amount of nested sequences

you can use. Just ensure the sequence is correct.

 

  • 1

    • 1.1

    • 1.2

  • 2

    • 2.1

    • 2.2

    • 1.3

    • 1.4

  • 3

    • 1.5

    • 3.1

Scores can be mixed with other scores as long as they

are entered subsequently.

 

  • 1

  • 4

  • 2

  • 5

  • 3

Scores are not bound to follow a specific order, those can

be defined in any order. Just ensure that there are no gaps

in the sequence. This also extends to nested scores.

 

Previous

Home

Next