Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SXFWRITE does not save cavity property frequency #421

Closed
coldfix opened this issue Apr 7, 2017 · 2 comments
Closed

SXFWRITE does not save cavity property frequency #421

coldfix opened this issue Apr 7, 2017 · 2 comments

Comments

@coldfix
Copy link
Collaborator

coldfix commented Apr 7, 2017

Issue migrated from trac ticket # 421

component: _build | priority: major


2017-04-07 10:52:39: ttydecks commented

Hi,
when using SXFWRITE to save a sequence, it does not include all parameters specified in the rfcavity command. Amongst others, the left out parameters are f.i. frequency, no_cavity_totalpath.
When loading the sequence later on with SXFREAD, this information is therefore not at hand and subsequent commands like PTC will not detect the cavities as the frequency is missing.

In the attached example "run.madx", please compare the original sequence with the one saved after running "run.madx" ("CAV.seq") and observe that the frequency is not saved.

Here is the header of my current MADX version:
++++++++++++++++++++++++++++++++++++++++++++

  • MAD-X 5.02.13  (64 bit, Linux)       +
    
  • Support: mad@cern.ch, http://cern.ch/mad +
  • Release date: 2016.12.20 +
  • Execution date: 2017.04.07 10:43:10 +
    ++++++++++++++++++++++++++++++++++++++++++++

Thank you very much for your support,
Tobias Tydecks


2017-04-07 10:52:57: ttydecks uploaded file run.madx (0.3 KiB)

@ldeniau
Copy link
Contributor

ldeniau commented Oct 2, 2017

Wrong question, this issue comes from previous issue Trac system.

@tpersson
Copy link
Contributor

This is fixed in #734

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants