Closed lfarv closed 7 months ago
As described in https://github.com/atcollab/at/wiki
1/ Contents can be generated using atupdateContents 2/ html documentation can once again be generated using atm2html (part of MML) or to be installed from https://github.com/gllmflndn/m2html graph dependence using https://graphviz.org/
Dear @lfarv,
All Contents are generated using atupdateContents. Do you want to include them in the release or should they be added during the installation of AT following the wiki page?
In the release not, could add the CorrectorPass bug fix.
@lnadolski
In the release not, could add the CorrectorPass bug fix.
You are right. I'll do that manually. Most of release notes is generated automatically, using the title of each pull request. Unfortunately, the CorrectorPass bug fix was not mentioned in the title… This shows how the PR titles must be very carefully chosen, and why mixing several things in a single PR may lead to problems.
@lnadolski: I ignored the existence of the wiki (my fault, it's indeed referred in the README), and the instructions are somewhat different from the "official" ones. This raises a few problems:
atupdateContents
breaks the version number by rewriting the 1st two lines of atmat/Contents.m
. According to the developer notes this file (its 1st 2 lines, in fact) is handled by the setversion
command. atupdateContents
should be modified to preserve these 1st 2 lines.atroot='/Users/laurent/Library/Application Support/MathWorks/MATLAB Add-Ons/Toolboxes/Accelerator Toolbox/atmat'
. Shall we make a new python release at the same time?
Shall we make a new python release at the same time?
PyAT 0.4.0 is almost 5 months old. Why not… But exact synchro is not necessary.
Added the CorrectorPass bug fix in the release notes.
@lnadolski : I ran atupdateContents
and committed the created Contents.m
files, so that a user does not need to run it. But I see some changes to be done in the future:
I think this should be part of another dedicated PR for documentation. For the moment, all contents files are there, that should be enough for a release. Do you agree with the present state?
PyAT 0.4.0 is almost 5 months old. Why not… But exact synchro is not necessary.
Since there has been quite a lot a new features added this would probably be a good idea, or at least before Christmas
I'd like to wait for the upgrade of the C constants (#691 ) before releasing the version. Otherwise, any comment on this release?
This release is ready. Please comment or approve.
cavpts missing from atSetRingParameters atGetRingParameters
Can you give more details on your problem: which platform, lattice example ? I can't reproduce the problem, for me atGetRingProperties(ring, 'cavpts') returns the cavities with the lowest frequency, as expected.
@simoneliuzzo : Sorry. I missed your message, but I have now all the info, thanks.
cavpts missing from atSetRingParameters atGetRingParameters
Fixed in #701
Hello @simoneliuzzo. The bug you reported in now corrected. Unless you have other remarks, can you approve again the release?
A new Matlab release including more that 1 year of updates.
There is no code change in this PR, only documentation and configuration changes.
A new tag and release will be published as soon as this PR is approved. The distribution on Matlab Central will follow immediately.