Skip to content

Anzahlbedingungen in ConfigChecker brauchen vielleicht Anpassung #19

@jvoigtlaender

Description

@jvoigtlaender

Insbesondere sind nach der Liberalisierung in #16 folgende Bedingungen nicht mehr unbedingt so klar korrekt/passend/optimal:

| flows < fst startNodes + snd triggerNames + if preventEmptyTriggersFromStates then fst joinNodes else 0
= Just "Your upper bound for trigger names is too high, relatively to the number of possibly named flows."
| distinctTriggerNames && enforceOutgoingEdgesFromNormalAndHierarchical &&
fst triggerNames < hierarchicalStates + if preventEmptyTriggersFromStates then normalStates - (if snd joinNodes > 0 then regions - regionsStates else 0) else 0
= Just "Your lower bound for trigger names is too low, relatively to the number of states to have distinctly named leaving flows according to your settings."
| distinctTriggerNames && preventEmptyTriggersFromStates &&
fst triggerNames < flows - snd startNodes - snd shallowHistoryNodes - snd deepHistoryNodes - snd joinNodes - (if snd joinNodes > 0 then regions - regionsStates else 0) - (regions - 2 * (regionsStates - 1)) * snd forkNodes
= Just "Your lower bound for trigger names is too low, relatively to the number of flows to be distinctly named according to your settings."

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions