Frederik Florentinus Van der Veken

Different scenarios summarised in https://www.overleaf.com/read/qnxfwwczzgbv#433390. Related issues: #413 #315

I was thinking to do something a la pandas (with a numeric index and `.loc` vs `.iloc`): print(line.element_names.index('ip3')) # 6459 line.loc[6459] # -> ip3 line.iloc[6459] # -> ip3 line.optimize_for_tracking() print(line.element_names.index('ip3'))...

I was also thinking to add the particles object as a parameter to the optimiser (`line.optimize_for_tracking(part)`) so that the method can shift the `at_element` in the particles. However, that puts...

- [ ] IT server setup in progress, succeeded in creating work and retrieving it on the client. - [ ] in git repo, need to create documentation on how...

A bit late to the discussion, but `xcoll` has such a monitor (`EmittanceMonitor`) since around the same time. It is currently implemented similarily to @eltos' suggestion, as a more general...

3) Rotations are not taken into account. 4) When the tracker is built with OpenMP, the result is just plain wrong.

You can have a look at `xcoll`'s `EmittanceMonitor`. It stores averages and squared averages, probably exactly what you need. There is a whole bunch of attributes (but the memory imprint...

If you do `pip install -e xpart/ xtrack/ xfields/ xplt/` only `xpart` will be installed as editable, the others won't. Better to install `xobjects` first (to get all necessary dependencies...

Did you plan for the LineTwisser to handle the versatility with (non)-collective elements as well? In that case, can we also provide the option to define this at the class...

Also, can you add the new implementation of ele_start and ele_stop to the list? It's been a while since we discussed this, so we should check that we still agree...