Opened 6 years ago
Last modified 6 years ago
#5516 closed defect
tableOnFile parameter of a CombiTable2D appears modifiable when using NF — at Version 7
Reported by: | massimo ceraolo | Owned by: | Per Östlund |
---|---|---|---|
Priority: | normal | Milestone: | 1.14.0 |
Component: | New Instantiation | Version: | v1.14.0-dev-nightly |
Keywords: | Cc: |
Description (last modified by )
Consider the enclosed "Test.mo" along with "Test.TXT"
The table output should be 1 when tableOnFile is false, 0.5 when it is true.
This is what happens when we simulate.
If, instead, we change the tablsOnFile value from the Variables Browser and re-simulate, the table output stays unchanged.
To obtain this behaviour one has to set -d=newInst,nfAPI.
Tested from OMEdit Connected to OpenModelica v1.14.0-dev-26504 (64 bit, Win)
Change History (11)
by , 6 years ago
by , 6 years ago
comment:1 by , 6 years ago
Component: | *unknown* → OMEdit |
---|---|
Owner: | changed from | to
comment:2 by , 6 years ago
comment:3 by , 6 years ago
Unfortunately not: I've verified that "Evaluate all parameters" is unchecked
by , 6 years ago
Attachment: | Untitled.png added |
---|
by , 6 years ago
follow-up: 5 comment:4 by , 6 years ago
It is always a good idea to post the omeditcommunication.log
file so we know which flags are used for the simulation.
I tested a bit and for me tableOnFile
is not changeable. I also attached a sample script that simulates the model without any flags and then you can see the Test_init.xml
file and look for variable combiTable2D1.tableOnFile
and attribute isValueChangeable
. Note that it is false
.
comment:5 by , 6 years ago
Replying to adeas31:
It is always a good idea to post the
omeditcommunication.log
file so we know which flags are used for the simulation.
Sorry for this!
In fact, repeating the test here from my home PC I don't see tableOnfile as modifiable. Tomorrow I'll repeat from work and will send you also omeditcommunication.log.
So maybe we will understand what strange setting makes it look as modifiable.
comment:6 by , 6 years ago
I've checked.
tableOnFile (wrongly) appears to be modifiable if you set -d=newInst,nfAPI as Additional Translation Flags.
So it is a NF issue: I'm going to change ticket title and description
comment:7 by , 6 years ago
Component: | OMEdit → New Instantiation |
---|---|
Description: | modified (diff) |
Owner: | changed from | to
Priority: | high → normal |
Summary: | Re-simulate does not modify boolean tableOnFile → tableOnFile parameter of a CombiTable2D appears modifiable when using NF |
I haven't tested it yet but just guessing if this is the same issue as was reported in #5377.