Hi,


I would like to be able to run different type of calculation with the same model. i.e: according to the type of calculation some variables will "fixed = true" or "fixed=false".


So I have done that:




And, this is the pb: I would like to write a code like that:



However it doesn't run, because it is not possible to "fixed=false" in initial equation?


Is anybody have a solution?



Thank you in advance


See you...

Hi Jerome,

put the your modifiers in the declaration part, e.g.:



Onething else, the initial equation part means there are equations, which are only valid during initialization. So the code:


means the same as:



Hope that helps.

Regards
Carsten

Hi Carsten,


Your response solve 80% of my problem, thanks.

Then, do you know the syntax to declare a variable according to the value of Calculation_type?

In fact, according to the value of Calculation_type some variables exist for ==1 but do not exist for ==2.

In my case the parameter MyDiameter does not exist if Calculation_type==2, then I have 2 solutions:
---> I can declare MyDiameter if Calculation_type==2
----> Or I can make "editText=false" if Calculation_type==2

However I have not succed to do both, could you help me?


For example, a thing like that



Thanks for your help.



See you.

Hi,

one question: Does it matter (besides that it isn't really "clean" style) that there is an unused parameter in the model? The translator will remove it anyway before solving when it is used nowhere.

If it really does matter, what about a little OOP? What about making a base class, then generating the specific sub classes with different parameter sets and then making a template model which allows to choose the used sub class instead of just the calculation_type? (redeclare, etc.) Just a suggestion...

Best regards,
Jonathan

Hi jce,

Thank you for your response.

In fact, I am going to "customize" the interface to simplify the use to the inexperienced user, that is why I would like some parameters does not exist = does not appear on the interface.

I think your response can help me, however I do not understand it. Could you give me more details. What is OOP, and you speak about sub classes: could you explain me the advantages to use them. Sorry but I am novice in modelica langage.



Regards.

Hi Jerome,

no problem, I try to explain in short terms. First, OOP means just Object Oriented Programming, that means the use of classes, subclasses, inheritance, etc.

For your problem I would suggest something like this:

First, you need a base class for the calculation, e.g.:


Then you derive the different calculation subclasses through inheritance:


and:


and finally, you write a "wrapper" class that just consists of an replaceable CalcBase object:



In your models you just include the wrapper class "CalcChooser" which let's you choose the applicable calculation class in the parameter dialog. The drop down list is automatically populated with all models derived from the "CalcBase" class by the annotation "choicesAllMatching"). After selecting the desired calculation, just click on the little arrow button besides the drop down list and choose "Edit". Then you are presented with the specific paramter dialog for the class you chose before. That's it! :-)

Good Luck and best regards,

Jonathan

Hi Jonathan,


I like your solution, it is a very "elegant" manner to program.


Thank you.



See you soon


Regards.