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

Tool selection should be the function of not just the activity, but also the models #8

Open
david-istvan opened this issue Nov 6, 2020 · 0 comments
Labels
enhancement New feature or request modeler

Comments

@david-istvan
Copy link
Member

32745983-9f9b6fa8-c8b4-11e7-978e-1422701c5c7e
Example shown here: a1 and m1 implies t1 and f1, respectively, tau1 implements t1 and t2 <=> it's a good selection, but tau2 wouldn't be a good selection for a1, as it doesn't implement t1. (~Although the two tools support the same formalism, they support different types of transformations.) Tau2 is a good selection for (a2, m2) though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request modeler
Projects
None yet
Development

No branches or pull requests

1 participant