Dear Users,
0. The changes related to CALC6D should correspond to the new version number 1.1 according to the original roadmap of 30 years ago.
1. A wrong usage of mkstemp creating unnecessary files has been corrected.
2. The flag RADTAPER no longer needs CODPLOT.
3. Closed orbit finding with RADTAPER has been revised.
4. Accessing keys of elements with an internal table kytbl has been changed to use parameters if possible.
5. Fitting value specification with two locations treats the value as the ratio for BX, BY, BZ, and as the difference for other functions:
FIT P1 P2; BX 1.5 : BX(P2) / BX(P1) == 1.5
FIT P1 P2; EX 0.2 : EX(P2) - EX(P1) == 0.2
6. A bug was created in around Sept. 2016, and fixed in temit.f. It might have affected the value of emittances.
Dear Users,
1. A bug was found in THIN elements SEXT, OCT, DECA, DODECA since V1.1. K value was not accepted.
Dear Users,
1. A bug was found in an optics calculation with CAVI in Linac. The parameter HARM was used for PHI. This was since V1.1k64.
Dear Users,
1. A bug was found that the keyword SIGMAZ in LINE, forMARK, did not work.
Dear Users,
1. The next version 1.1.0.3k64 brings a few new options in Graphics: FrameFontScale, LegendFontScale. These specify a relative sizes of FrameLabel and Legend. FrameFontScale (also TickFontScale) accepts a real number or a list of real numbers. If it is a real number, it is applied to all frames. If it is a list, it is applied in the order of bottom, left, top, right in the same way as FrameLabel. If its length is shorter than 4, 1's are supplemented to the right.
2. OpticsPlot accepts an option RemoveOverlap. If it is not "L$NAME", the overlapping of the labels of the lattice is unsolved.
Dear Users,
1. A new keyword DVOLT will be added to CAVI and MULT in the next version, 1.1.0.3k64. DVOLT is to be added to VOLT without affecting the design momentum p0(s).
2. A bug was there in CALC/GO with CALC6D with acceleration and TRPT. The normalization of orbit according to p0(s) has been applied twice.
Dear Users,
1. A bug was found in the optics/emittance for MULT with acceleration. The rf phase was wrongly handled since V1.0.10.9k64.
Dear Users,
1. A bug was found in qfraccomp (qtwiss.f) to determine the orientation of an element in a wrong way. It has been there since V1.1k64.
Dear Users,
1. There has been an issue in TrackParticles if it starts at an element with nonzero OFFSET and the ends at a location earlier than the effective start point. It is corrected to return {start, coords} without tracking in such a case.
Dear Users,
1. Due to the previous change in TrackParticles, a bug was created in V1.1.0.3k64, to prevent tracking for one element-by-element case.
2. Unnecessary print-out was generated during tracking.
Dear Users,
1. Another bug was found for Emittance[Matrix->True], not returning the transfer matrix for the end of line. By the way, TransferMatrix function is more recommended for this purpose, usable issuing CALC/GO with CALC6D.