Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anzahlbedingungen in ConfigChecker brauchen vielleicht Anpassung #19

Open
jvoigtlaender opened this issue Dec 16, 2024 · 0 comments
Open

Comments

@jvoigtlaender
Copy link
Member

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."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant