Matching with family
Posted: Sun 6 Feb 2022 20:45
Hi Colleagues,
I have two questions:
First question:
There are two pieces of related comments in the TraceWin user's manual, quoted below. It seems to me that if I want to use match_fam_grad, there must be a command "set_twiss fn" in the code. But I have tried, it is not true. I can use match_fam_grad and set_size successfully without set_twiss. Do these comments in the manual mean something else?
p.79
Write “SET_TWISS fn” corresponds to write “SET_TWISS fn 0 0 0 0 0 0 1 1 1 1 1 1”. That disables the SET_TWISS command and allows different other optimisations by inserting another commands like for example “SET_SIZE”.
p.80
The command SET_TWISS is always obligatory to allow the matching of the gradrupole. And the option “Matching with family & Twiss commands” of page “Matching” has to be checked.
Second question:
Among all the set_xxx commands, only set_twiss supports the family number. On the other hand, all the match_fam_xxx commands support family number. How can I, for example, use only one collection of parameters (fn=1) to optimize for one set_size command and use another collection of parameters (fn=2) to optimize for another set_size command?
Best regards,
Wai-Ming
I have two questions:
First question:
There are two pieces of related comments in the TraceWin user's manual, quoted below. It seems to me that if I want to use match_fam_grad, there must be a command "set_twiss fn" in the code. But I have tried, it is not true. I can use match_fam_grad and set_size successfully without set_twiss. Do these comments in the manual mean something else?
p.79
Write “SET_TWISS fn” corresponds to write “SET_TWISS fn 0 0 0 0 0 0 1 1 1 1 1 1”. That disables the SET_TWISS command and allows different other optimisations by inserting another commands like for example “SET_SIZE”.
p.80
The command SET_TWISS is always obligatory to allow the matching of the gradrupole. And the option “Matching with family & Twiss commands” of page “Matching” has to be checked.
Second question:
Among all the set_xxx commands, only set_twiss supports the family number. On the other hand, all the match_fam_xxx commands support family number. How can I, for example, use only one collection of parameters (fn=1) to optimize for one set_size command and use another collection of parameters (fn=2) to optimize for another set_size command?
Best regards,
Wai-Ming