Bug in macro replacement in display
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
Research direction
Start by reproducing the nested-display case: a parent display passes P=QE1:FX4:, R=Current1:, and a child passes RN=$(R)TSTotal in the same macro list as R. Find where the Phoebus display runtime expands macros for child displays and check whether parameters are substituted in order, so later values see earlier replacements. Done when the plot title resolves to QE1:FX4:Current1:TSTotal and the ADL-converted and native .bob cases behave the same.
Written by the indexing model from the issue text.
Description
I think I have found a bug in macro replacement in display files. In my case these are files that are converted from medm .adl files, but I think the problem is more general.
I originally saw the problem using the adl converter from Phoebus 4.6.10 and Phoebus display 4.7.3. But I have reproduced it using both the converter and display in Phoebus 6.0.0.
This is an example of the problem.
quadEM.bob loads the related display file NDStats, and passes the macro parameters P=QE1:FX4:, R=Current1:
NDStats.bob loads the related display file NDStatsTimeSeriesPlot, and passes the parameters P=$(P), R=$(R)TS:, RN=$(R)TSTotal
The title of this plot is $(P)$(RN)
After substitution the plot title should thus be QE1:FX4:Current1:TSTotal.
However, it is not. As seen below it is QE1:FX4:Current1:TS:TSTotal.
The reason is clear. This is the screen for the Actions of the menu that calls NDStatsTimeSeriesPlot:
What is happening is that it is not using the original value of R when it builds RN, it is using the modified version from the first line.
I can work around the problem by swapping these 2 lines in the .adl file, so that RN is built before R. But it seems that this should be fixed in the translation or runtime engine.
- Dominant language
- Java
- Stars
- 130
- Forks
- 132
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ControlSystemStudio/phoebus
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ControlSystemStudio/phoebus#3983 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ControlSystemStudio/phoebus#3979 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ControlSystemStudio/phoebus#3962 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ControlSystemStudio/phoebus#3865 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ControlSystemStudio/phoebus#3995 ·
Maintainers usually reply within 1 day
All issues in ControlSystemStudio/phoebus
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
snowflakedb/snowflake-kafka-connector#1610 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
swagger-api/swagger-petstore#245 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
liquid-java/liquidjava#443 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
quarkiverse/quarkus-google-cloud-services#1188 ·
Maintainers usually reply within 1 day