rf_setup is broken in 2025.1

Moderators: michael_borland, soliday

Post Reply
Skamarokha
Posts: 32
Joined: 14 Apr 2021, 09:42

rf_setup is broken in 2025.1

Post by Skamarokha » 05 May 2025, 00:59

Hello

Updated today elegant from 2024.1 to 2025.1 on Windows and discovered different behavior of rf_setup. Pelegant exits without warnings and errors after printing out all data from script at the tracking step. In Elegant I see message

Code: Select all

Updating floor coordinates
tracking step 1
Tracking fiducial particle (runFiducialParticle)
5 May 25 12:52:02: This step establishes energy profile vs s (fiducial beam).
5 May 25 12:52:02: Rf phases/references reset.
Fiducial particle lost. Don't know what to do.
Also in the terminal output

Code: Select all

&rf_setup
    filename = %s.rf,
    name = RES1,
    start_occurence = -1,
    end_occurence = -1,
    s_start = -1.000000000000000e+00,
    s_end = -1.000000000000000e+00,
    set_for_each_step = 0,
    near_frequency = 0.000000000000000e+00,
    fractional_frequency_change = 0.000000000000000e+00,
    harmonic = 222,
    bucket_half_height = 1.000000000000000e-02,
    over_voltage = 0.000000000000000e+00,
    total_voltage = 0.000000000000000e+00,
    disable = 0,
    output_only = 0,
    track_for_frequency = 0,
    phase_offset = 0.000000000000000e+00,
&end

Rf setup: frequency is 1.817292866824004e+08 Hz (h=222)
Changing definition (mode absolute) RES1.FREQ from 1.817292866824030e+08 to 1.817292866824004e+08
Changing value (mode absolute) RES1.FREQ from 1.817292866824004e+08 to 1.817292866824004e+08
Voltage per cavity is             -nan(ind) V, overvoltage is             -nan(ind), phase is             -nan(ind) deg

Changing value (mode absolute) RES1.VOLT from             -nan(ind) to             -nan(ind)
Changing value (mode absolute) RES1.PHASE from             -nan(ind) to             -nan(ind)
Set phase of RES1 to             -nan(ind) deg
For some reason rf_setup does not see my values for voltage and phase and can't setup it's own.

Reinstalled 2025.1 - same problem. Returned to 2024.1 - no problem, everything works as it should.
Respectfully,
Mikhail A. Skamarokha.

michael_borland
Posts: 2006
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: rf_setup is broken in 2025.1

Post by michael_borland » 05 May 2025, 16:32

Mikhail,

I'm not able to confirm this problem on linux or windows. Can you upload files that cause the problem?

Thanks--Michael

Skamarokha
Posts: 32
Joined: 14 Apr 2021, 09:42

Re: rf_setup is broken in 2025.1

Post by Skamarokha » 06 May 2025, 23:26

Michael,

Made an example for you. Also checked this for different lattice. It looks like rf_setup behavior is lattice dependent. The lattice in question is a result of DA optimization, but energy aperture is bad. rf_setup from 2024.1 however managed to find RFCA parameters, but the one from 2025.1 couldn't - logs are in the archive. Has the fiducialization process or the behavior of elements changed in 2025.1?
Attachments
example.zip
(189.68 KiB) Downloaded 36 times
Respectfully,
Mikhail A. Skamarokha.

michael_borland
Posts: 2006
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: rf_setup is broken in 2025.1

Post by michael_borland » 06 May 2025, 23:46

Mikhail,

The problem is caused by dipole magnet called R.MB12, which has ANGLE=0. I'm not sure why it is a problem now and not in the previous version, but I'll find a solution now that I can see it.

--Michael

michael_borland
Posts: 2006
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: rf_setup is broken in 2025.1

Post by michael_borland » 07 May 2025, 14:46

Mikhail,

This bug was introduced when I refined the calculation of radiation integrals to better include orbit effects. The fix was pretty simple, see attached.

Thanks for the bug report.

--Michael

Post Reply