Francesco Casella
Francesco Casella
> My guess is that the debug log is to large to be handled. As a general remark, once a simulation tool has been refined enough to be actually usable...
> The message should be in `"messages"` of the Dict. With smaller debug flags this does work, for example `backenddaeinfo` worked. That's exactly what I meant as a questionable design...
> You are right that you might sometimes need to write to file, since in some cases available memory is not enough, and swapping might result in the simulation taking...
Same comment as in [OMMatlab #10](https://github.com/OpenModelica/OMMatlab/issues/10), isn't there a way to avoid code duplications and hence inconsistencies among different OpenModelica tools?
@JKRT can you please comment on that?
> Or we use GPL-3.0, but then nobody is allowed to change OMJulia. To the contrary, anybody can do that, _provided they make the changed code publicly available if they...
The OSMC-PL license is meant for the source code of _the tool_, not for the generated source code of _user's models_. That is to prevent non OSMC-members to change the...
> The first question to resolve is if the use of `omc` when communicating via sockets/pipes (like OMJulia/OMPython do) consists of [aggregation](https://www.gnu.org/licenses/gpl-faq#MereAggregation). It seems to me (**IANAL**) this should be...
Gosh, I wish somebody else could take care of these issues 😅
@bilderbuchi thanks for pointing this out. I missed the fact that the PR included OSMC-PL, not OSMC-PL-RT. I'll have to undo that.