Elegant users forum

I got the same behavior with unknown tokens - traced it back to having only a single instance of a marker. Is there another syntax without '#<num>' for accessing these? I tried rpn trace mode, but it doesn't list what exactly is stored by optimizer, and 'smem' doesn't output anything from inside elegant.

As a workaround, doubling up the markers as worked

Nikita

Nikita,

The syntax for referring to quantities at markers must always be of the form <elementName>#<occurrenceNumber>.quantity, even if the marker only occurs once.

--Michael

Thank, Michael.

In case anyone else finds this thread, I figured out that the problem was my assumption about <occurenceNumber> indexing. It is [0,...] and not [1,...] - that is why double markers resolved the issue, since then 2nd one of the pair matched.

Occurence numbers actually start with 1, not 0. So if you have
The first M1 is M1#1 and the second is M1#2, etc. Referring to M1#0 should return an error.

--Michael

Thank you Michael - I must have mixed up my recollection.

Here is the real reason: optimization terms were generated automatically in Python code that was 0-indexed, but used last instance of the marker by default. So, adding two markers meant '<marker>#1' was generated and matched first of two actual instances in the lattice. I have since then just hardcoded '#1' and enforced unique element names during lattice export to avoid possible bugs.