-
Notifications
You must be signed in to change notification settings - Fork 4
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
Thoughts for future improvements #111
Labels
Comments
Thx for the suggestion, I know abt this one. It could theoretically be used instead of There are actually many small IPC libraries out there that one could try However not sure how much benefit it would bring in CoSimulation, since even when using Files the transfer times are usually much smaller than the solver (with my implementations ofc :D) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ModelPart
should be iterable withauto
like in Kratos =>for (auto& node : model_part.Nodes()) { ... }
=> [ModelPart] support for range based loops #266ModelPart
connection_name
(otherwise we have to keep theInfo
coming fromConnect
the entire time) => using strcpy #124, didn't go in in the endconnection_name
in C-Interface, see using strcpy #124ModelPart
to vtk directly for debugging purposes (maybe even with Data (like we do for vtu?))FileCommunication
configureable (?):Connect
=> see File comm/check version #140Testing
MPIDataCommunicator
CoSimIO.Vector
(see [Python] adding Vector #118) by ref (in python and C++) => make sure the opaque types workThe text was updated successfully, but these errors were encountered: