-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fix/inlet outlet connections #143
Conversation
AFAIK this is not explicitly caught, but inexplicitly via "CADETProcessError: Origin/Destination unit does not support ports." |
Thanks. Would you be up for adding some tests to this branch here? |
Will do 👍 |
I wrote a small test on #95 and we actually do not caugh the exception. It actually errors out by subscripting over non existant dict entrys, in the connections dict. So yeah we still have to catch this error.
|
We will sort it out. This week didn't work out unfortunately but next week @daklauss and I will do an intense cadet-process + ports session. |
Wrote some tests for checking errorraising of wrong inlet/outlet connections. Additionaly added tests for the other cases in which |
With this PR, an exception is raised whenever a user tries to connect an
Outlet
unit operation to another unit, or some unit to anInlet
unit operation.@hannahlanzrath @daklauss Do we already handle this in #95?
Fixes #139
Todo