1 / 9

Mad-X Status

Mad-X Status. Purpose of the Second MAD-X Day Program of the Workshop MAD-X Code Facts MAD-X History and Future Services MAD-X Collaborators Manpower Needs Recent Developments Future Plans. Purpose of the Second MAD-X Day. MAD-X status: It is the design tool of the LHC

lapis
Download Presentation

Mad-X Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mad-X Status Purpose of the Second MAD-X Day Program of the Workshop MAD-X Code Facts MAD-X History and Future Services MAD-X Collaborators Manpower Needs Recent Developments Future Plans

  2. Purpose of the Second MAD-X Day • MAD-X status: It is the design tool of the LHC • MAD-X - PTC Integration: What is still needed? • What is MAD-X lacking compared to MAD8? Who will do the job? • Phase out MAD8 • The Non-LHC community: How to best serve them with MAD-X? Second MAD-X Day

  3. MAD-X Code Facts • Programming Language: C, Fortran77/90 • Core in C: Memory Management, Input Parser & Interfaces • Custodian and Team of Module Keepers • Truly Independent Modules: Module Keeper takes control (Restrictions apply) • CVS version control Second MAD-X Day

  4. MAD-X History and Future • MAD-X was an emergency solution in view of the needs of the LHC and the failure of MAD9. • Therefore MAD-X could NOT be a “Grand New Approach” but rather a collection of old MAD8 routines connected with a solid C core written by Hans Grote. • Code maintenance NOT by one or two experts, • Instead a custodian and a team of half-time module keepers. • Problems have to be fixed by the users in an open-source spirit . • No new development is planned for the Core itself (see later). • Emphasis is on Upgrading old modules and Adding new ones. • PTC is the GeneralUpgradePath of MAD-X for new physics and serving smaller machines. • Important: Allowing new features unknown to MAD-X proper but transferred through MAD-X input to PTC. Second MAD-X Day

  5. Services • MAD-X Web page: http://cern.ch/Frank.Schmidt/Xdoc/mad-X.html • Documentation in HTML format derived from that source PS & PDF manual files Comment: Please report deficiencies in the documentation!! • Reports and Manuals for MAD-X • News Section describing changes for each Version • Minutes of MAD-X Meetings • Latest Executables (LINUX, Windows, MAC OS-X) • Directory with Source Code, Makefile & Project History • Link to the Examples • Module Writer’s Guide • MAD8 to MAD-X Conversion • Bug Report Form • MAD-X Mailing List + Newsgroup Second MAD-X Day

  6. MAD-X Collaborators • Alex Koschik (André Verdier) – Thintrack • Catia Milardi (INFN/LNF) + Frank Zimmermann – Touschek • Eric McIntosh + Frank Schmidt –Memory Leaks & Buffer Flushing • Etienne Forest (KEK) – PTC proper • Frank Schmidt –Custodian,C6T, Twiss, PTC_Twiss • Frank Schmidt (Eric d’Amico) –SODD, PTC_Normal • Frank Tecker (André Verdier) – Survey • Frank Zimmermann – Dynap • Frank Zimmermann (Daniel Brandt) – IBS • Hans Grote –Core Maintenance & Debug • Helmut Burkhardt (Mark Hayes) – Makethin, MAC System 10 • J.B. Jeanneret(I.K. Waarum) – Aperture • John Jowett –Windows Version • Nikolay Malitsky (BNL) – SXF • Oliver Brüning –Match • Ralph Aßmann –Emit • Thys Risselada –Threader &MMK secretary • Riccardo de Maria (Eric d’Amico) –Plot • Valery Kapin (ITEP) + Frank Schmidt–PTC_track • Werner Herr –Error, Cororbit Second MAD-X Day

  7. Manpower Needs • Core Maintenance and Debugging The MAD-X team is very grateful about Hans Grote’s steady support!! • With the retirement of Eric d’Amico we lost our C developer of the Core  we need a half-time person to make progress in this field. • Presently the MAD-X proper modules are taken care of, with the essential exception of matching (near future)! • We are looking for developers of PTC related modules and long-term keepers of those PTC modules. • There will be a CERN fellow who is scheduled to make use of MAD-X PTC for CLIC. • It would essential that the small machine community gets involved in using MAD-X PTC for their machines. Active participation is required! • We are very happy about module keepers outside of CERN and we welcome more of those collaborations! Second MAD-X Day

  8. Recent Developments • Lots of bug fixes! • Upgrades: • Plot: Proper Interpolate, track table (gnuplot), ptc_twiss table • Makethin: better select • Error: Complete Machine Description in 2 files: sequence file & error file • Orbit: correction from external files; simultaneous 2 beam c.o. correction including common elements • Match: Nonlinear matching prepared with PTC • IBS: Horizontal growth rate corrected; effect of vertical dispersion added • Core: Parser separated from the rest of the Core • New Modules: • SODD: Second Order Detuning and Driving Term • Touschek  see talk • PTC modules  see talk • PTC integral Part of MAD-X • AML (Accelerator Mock-up Language) is being developed by Cornell. Both a MAD8 and a MAD-X parser to that language is being prepared by them. FS is in contact. Second MAD-X Day

  9. Future Plans • MAD-X proper Code • Bug fixes but no real Core development • Add modules when the need arises • PTC • Concentrate on making better use of PTC in MAD-X, presently only a small fraction is being used • Nonlinear Matching with PTC • Completing present PTC modules including Documentation • Applications for CLIC & Small Machines • General Issues • Investigate if AML is of use to us • UAL/SXF • Solve Memory Leaks & Flushing Problem Second MAD-X Day

More Related