0.18.1

This is a patch release, fixing a bug in the knob_extractor concerning the properties passed on to sparks.

Fixed:

• Setting sparkprops wrong in knob_extractor fixed.

What's Changed

• Knob extractor spark props by @JoschD in #470

Full Changelog: 0.18.0...0.18.1

Release 0.18.0

A minor release, introducing ORBIT_DPP as parameter for allowing calculations of an effective deltap/p offset caused by a change in orbit for the response matrix and global correction functions.

• Added:

  • Add the ability to calculate an effective deltap/p offset caused by a change in orbit.
  • Add the ability to use response_madx to calculate the updated response matrix for the global correction.
  • Tests for the calculation of the deltap/p and corresponding correction.
  • Tests for the calculation of the updated response matrix for the global correction.

• Fixed:

  • Fixed the response_twiss when updating the response matrix when calculating the global correction.

What's Changed

• Add Calculation of DPP in full response and global correction by @jgray-19 in #466

New Contributors

• @jgray-19 made their first contribution in #466

Full Changelog: 0.17.0...0.18.0

Release 0.17.0

A minor release, introducing analyse_dpp as parameter for choosing which files (with which dpp values) to take into account when running the optics analysis.

This also fixes a bug with the uncompensated phase-advances when using the equation compensation method, which might have caused some minor error in the coupling calculation when using this method.

• Added:

  • Optics Measurements: analyse_dpp parameter, to analyse only files with a specific DPP for tune, phase and (C)RDTs.

• Fixed:

  • Uncompensated Phase calculations with Equation compensation are now actually uncompensated when passed on to the coupling module.

What's Changed

• new parameter: analyse_dpp by @JoschD in #461

Full Changelog: 0.16.2...0.17.0

Release 0.16.2

Patch release to fix an issue with NXCALS in the CCC when using the knob-extractor.
This change should not impact anyone unless they also have a /mcr/bin/ at the beginning of their PATH.

• Fixed:
  • Temporary hack to fix knob_extractor in CCC.

Release 0.16.1

This is a patch release, that provides the following fixes.

• Fixed:

  • Fixed DepracationWarnings related datetime operations.
  • Fixed DeprecationWarning occuring due to the use of old numpy functions.
  • Fixed FutureWarning happening during edge-cases of dataframe concatenation by performing checks ahead of time.
  • Fixed FutureWarnings occuring due to deprecated pandas.Series accesses.
  • Fixed UserWarning occuring when wrongly setting ticks and labels for correction plots.

• Changed:

  • Masked NaturalNameWarnings happening during HDF5 tables operations, as the use of names such as kq4.r8b2 is not avoidable and pandas properly handles access operations for us.
  • Masked UserWarnings happening during plotting for operations that are explicitely demanded.
  • Intercept RankWarning which can happen during a polyfit of data and re-emit as log message.
  • Intercept OptimizeWarning happening when the covariance parameters could not be estimated in kmod analysis and re-emit as log message.
  • Intercept OptimizeWarning happening when the covariance parameters could not be estimated in rdt analysis and re-emit as log message.

What's Changed

• Fix Various Warnings by @fsoubelet in #460

Full Changelog: 0.16.0...0.16.1

Release 0.16.0

This is a minor release, with the following features:

• Added:

  • Global Correction for LHC:
    • The correction variables in the LHC accelerator class are now handled differently internally,
      allowing new variable classes to be added to each lhc-year and user-given files in the model-directory.
    • Variable categories MQM_ALL added to all LHC years.
    • Variable categories MQM_INJ_2024 and MQM_TOP_2024 added to LHC 2024.
    • Adding a "-" in front of a given correction variable name removes this variable from the correction. Does not work for whole variable categories.
  • Tests for running global_correction with omp and pinv correction methods.

• Fixed:

  • Orthogonal Matching Pursuit (omp) in global correction runs again (#448)
  • Corrections Check window stop-iteration issue: fixed. Single-plane files, i.e. normalized dispersion, now accepted (#447)
  • LHC Correction variables now logged, if not found in the variable categories (#446)

What's Changed

• Global Correction Fixes by @JoschD in #458

Full Changelog: 0.15.4...0.16.0

Release 0.15.4

This is a patch release, that provides the following fixes:

• Fixed:

  • Measure optics skips now using the ERRAMP column, when not present, i.e. when cleaning deactivated (#451)
  • hole_in_one now allows pathlib.Path objects in addition to str (#452)
  • Pandas to numpy dtype conversions bug (#453).
  • Special phases writing now skipped when accelerator has no special phases (#454).
  • RDT/CRDT calculation now not crashing when also giving off-momentum files; but only calculated from on on-momentum files (#456).

• Added:

  • Tests for full runs hole_in_one with on-momentum and off-momentum files.

What's Changed

• Bugfixes: numpy/pandas dtypes, erramp column, path read, special phases by @JoschD in #455

Full Changelog: 0.15.3...0.15.4

Release 0.15.3

This is a patch release with minor fixes:

Fixed:

• Add DOROS BPMs to twiss.dat.
• Some Pandas FutureWarnings, DeprecationWarnings and PerformanceWarnings

What's Changed

• madx pattern for doros BPMs by @JoschD in #445

Full Changelog: 0.15.2...0.15.3

Release 0.15.2

Release 0.15.2 is a patch version fixing compatibility with numpy 2.x by importing ComplexWarning differently.

Fixed

• Numpy's ComplexWarning was not part of main namespace in v2.0, so we import it directly

What's Changed

• Patch complexwarning by @JoschD in #443

Full Changelog: 0.15.1...0.15.2

Release 0.15.1

Release 0.15.1 is a patch version fixing compatibility with numpy 2.x. Please note there is a caveat (read below) on Python 3.9.

Important Changes:

• The minimum required numpy version is now numpy 1.24.

Fixes

• The package is now fully compatible with numpy 2.x on Python >= 3.10 thanks to a pytables compatibility release.
• The package still limits to numpy < 2 on Python 3.9 due to the lack of compatibility from pytables on this versions.

What's Changed

• Migrate to pyproject.toml and common workflows, update for numpy 2.0 by @fsoubelet in #442

Full Changelog: 0.15.0...0.15.1