strange behaviour of variableFilter

[cbrinkrolf@…]

My model contains variables p1.pc_t and p1.t.
Matching only second variable does not work with filter p1\.t
In runtime, this variable filter is extended to following regex: ^(p1\.t)$
However, both variables are matched. Is it just me or is there something wrong?

[Lennart Ochel]

I cannot reproduce the issue. I tested it on Linux and Windows using the following script:

loadString("
model test
  block foo
    Real t = cos(time);
    Real pc_t = sin(time);
  end foo;

  foo p1;
end test;
"); getErrorString();

simulate(test, simflags="-override=outputFormat=csv,variableFilter=p1.t"); getErrorString();

The result file does only contain time and p1.t as intended.

[Lennart Ochel]

I should mention that I get the same result for both p1.t and p1\.t.

[Lennart Ochel]

There is an issue with Q-idents. The following script produces different results on Linux and Windows:

loadString("
model test
  block foo
    Real t = cos(time);
    Real pc_t = sin(time);
  end foo;

  foo 'p1';
end test;
"); getErrorString();

simulate(test, simflags="-override=outputFormat=csv,variableFilter=\\'p1\\'.t"); getErrorString();

On Linux there is time and 'p1'.t in the result file, but on Windows there is only time in the result file.

[Lennart Ochel]

Running the executable directly from the command prompt produces the same results on Linux and Windows again.
./test -override=outputFormat=csv,variableFilter=\'p1\'.t

[Adrian Pop]

Could be an issue on how OMEdit sends these flags to the simulation executable.

[Lennart Ochel]

Replying to adrpo:

Could be an issue on how OMEdit sends these flags to the simulation executable.

OMEdit was not used for any of the tests.

[Adrian Pop]

Replying to lochel:

Replying to adrpo:

Could be an issue on how OMEdit sends these flags to the simulation executable.

OMEdit was not used for any of the tests.

You didn't use it, but maybe the ticket poster did.

[Lennart Ochel]

Replying to adrpo:

You didn't use it, but maybe the ticket poster did.

Sorry, maybe I should have said that Christoph - the ticket poster - is my colleague and has also not used OMEdit. He run the executable from command line and used only used override flag to specify the output format and variable filter as in my example from above.

[Lennart Ochel]

I am not sure what we actually did wrong, but it seems that it is working just fine. It's just about doing the escape sequence right. The following filter matches 'p1'.t and 'p2'.t_[1] and works for Windows and Linux:
./test -override=variableFilter=\(\'p1\'\.t\|\'p2\'\.t_\\[1\\]\)

[Dietmar Winkler]

Sorting away the closed as invalid, won't fix and duplicate tickets from Future.