When the class membership model is defined with a dataservice, the alternatives of the dataservice are adopted as the alternatives of the model… but for this particular (sub)model, the “alternatives” are supposed to be the classes not the alternatives. This bug only arises when a dataservice is declared when the class membership model is created, which is why it doesn’t happen in the demo script or tests so far, as they don't use data for that submodel.
When the class membership model is defined with a dataservice, the alternatives of the dataservice are adopted as the alternatives of the model… but for this particular (sub)model, the “alternatives” are supposed to be the classes not the alternatives. This bug only arises when a dataservice is declared when the class membership model is created, which is why it doesn’t happen in the demo script or tests so far, as they don't use data for that submodel.