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

More models converted from Modelica Standard Library #61

Open
HildingElmqvist opened this issue Oct 22, 2018 · 6 comments
Open

More models converted from Modelica Standard Library #61

HildingElmqvist opened this issue Oct 22, 2018 · 6 comments
Assignees

Comments

@HildingElmqvist
Copy link
Contributor

I am working on a recursive descent parser for Modelica written in Julia in order to automatically translate more Modelica models as test cases for Modia.

@o314
Copy link

o314 commented Oct 23, 2018

Hello Modia People, Mr Elmqvist,

Will this software be available publicly ?

@HildingElmqvist
Copy link
Contributor Author

Yes. I just need to get it a bit more complete and robust. I will then put it under ModiaSim. What's a good name? Modelica2Modia?

@MartinOtter
Copy link
Member

MartinOtter commented Oct 23, 2018

Yes. I just need to get it a bit more complete and robust. I will then put it under ModiaSim. What's a good name? Modelica2Modia?

ModelicaToModia (Modelica and Modia use correct English words and try to avoid abbreviations)

@MartinOtter
Copy link
Member

MartinOtter commented Oct 23, 2018

Sorry, clicked on the wrong button. Did not want to close this issue.

@MartinOtter MartinOtter reopened this Oct 23, 2018
@HildingElmqvist
Copy link
Contributor Author

I initially wanted to map the Modelica package structure onto the Julia module structure. However, this does not work because there are cyclic dependencies between some Modelica packages.

I did not find any trick to handle cyclic module dependencies in Julia. Any input on this?

This would mean that the Modelica libraries needs to be flattened, i.e. sub-pacages removed and model paths such as Modelica.Blocks.Continuous.Integrator would be replaced by a name such as Modelica_Blocks_Continuous_Integrator.

Any othersuggestion?

@o314
Copy link

o314 commented Oct 25, 2018

I don't know enough Julia already to specifically answer about Julia, but a generic good practice is to use the Inversion of Control pattern.

There is a good description there How to solve circular package dependencies

IMHO the flattening would lead to a double hierarchy, which could be very noisy and disturbing for users.

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

3 participants