Elegant users forum

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 actu...

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.

Hi Michael, I was playing around with adding new elements, and noticed that drift tracking results from MAD-X and elegant are different. I initially thought both codes had exact drifts. However, in csbend.c: void exactDrift(double **part, long np, double length) { long i; double *coord; for (i=0; i<...

Michael,

Please see attached. I have also realized the better fix is to add RECIRC after CHARGE, which is what default examples have. See the RC element at the end of the lattice file.

Nikita

I am also very interested in seeing Zen2 scaling in Pelegant, especially on the upcoming 3990X. If Pelegant is memory limited, things could go weird due to latency/asymmetry. There is also the NUMA settings, compile optimization (-march=znver2), and libraries (MKL hacking to enable AVX) to consider....

Hi all, I found an interesting crash - when lattice has CHARGE element, &frequency_map results in segfault. After (painfully) building elegant with debug symbols, I think the problem stems from the way do_tracking() is called from computeTunesFromTracking() with increasing pass offset, which for all...

Hi Michael and all, I seem to have a weird issue with IBSCATTER, WATCH elements and &insert_elements command. Namely, depending on where in task file I try to insert these, it either works normally, messes up other computations (like moments), or straight up segfaults. I suspect it has something to ...

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 ele...