[Cs5500] Avoiding Sad Avatars

[Karl Lieberherr]

Somewhere in a far away land of an HSR playground there lives a lonely
avatar who would love to play with others. But each time she tries,
she gets kicked by the admin. The avatar thinks this is highly unfair
because she thinks she is very good and deserves to play with the
others and win frequently.

The sad avatar then went to the doctor to find out what is wrong with
her. The doctor ordered a test of the solve function by calling the
valid function immediately after the solve. It turned out
that many of the solutions the solve function produced were illegal
which is why the avatar got kicked.

Now the avatar feels much better; at least she knows what is wrong with her.
She is negotiating with her care giver about how to change her circuitry.

To avoid sad avatars and trips to the doctor, test them following the
outline below.
It is easy because the functions that check are already in the playground.

-- Karl

public SolutionI solve(SolveRequest solveRequest);
solve tested by
InstanceI SolveRequest.getInstance()
Instance.valid(SolutionI solution, Config config)

public List<Claim> propose(List<Claim> forbiddenClaims);
propose tested by
InstanceSetI.valid(Config config)
InstanceSetI Claim getInstanceSet()
Also test quality and confidence in [0,1].

public InstanceI provide(Claim claimToBeProvided);
provide tested by
InstanceSetI.belongsTo(InstanceI instance)

public List<OpposeAction> oppose(List<Claim> claimsToBeOpposed);
oppose tested by
This method will be tested by a tournament.
Make sure that the outgoing list has the same length
as the incoming list.