Menu
▾
▴
Re: [Atcollab-general] update on AT2.0
|
From: NADOLSKI L. <lau...@sy...> - 2017-08-23 11:42:20
|
Dear Boaz, atsummary does not use lyap indeed (my mistake). I have gotten in trouble when I first used atx which is itself calling ohmienveloppe Now this is fine with moving the private directory. Compilation updated information : For information, I was able to recompile seamlessly AT under Matlab R2017a under MAC OS SIERRA 10.12.6 AT (mex) is not compatible on MAC OS SIERRA for R2016a as specified on Mathworks website. Error using mex No supported compiler or SDK was found. For options, visit http://www.mathworks.com/support/compilers/R2016a/maci64.html. Error in atmexall (line 34) eval(MEXCOMMAND); Best regards, Laurent. Dr Laurent S. NADOLSKI Coordinateur Exécutif des Accélérateurs Division Accélérateurs et Ingénierie, Synchrotron SOLEIL t: +33 (0)1 69 35 98 08 m: +33 (0)6 89 43 70 45 a: L'Orme des Merisiers Saint-Aubin BP 48, 91192 Gif-sur-Yvette CEDEX FRANCE w: www.synchrotron-soleil.fr<http://www.synchrotron-soleil.fr> e: nad...@sy...<mailto:nad...@sy...> Le 23 août 2017 à 11:46, Boaz Nash <boa...@es...<mailto:boa...@es...>> a écrit : Hello again, I should have written ‘addpath' instead of ‘setpath' in my email below. Boaz On Aug 23, 2017, at 11:39 AM, Boaz Nash <boa...@es...<mailto:boa...@es...>> wrote: Dear Laurent, Thanks for pointing out this issue with lyap. Indeed, it is needed by ohmienvelope which was moved. I moved private/lyap to the Radiation directory where ohmienvelope is now. It looks to me like atsummary does not use lyap, however. Could there be another reason why atsummary doesn’t work for you after the reorganization? Yes, re ohmienvelopedemo and in general, one needs to make sure machine_data and all the new directory structure is on the path. One can be sure of this by setting the path using a setpath(genpath(ATCOLLAB)) where ATCOLLAB is the top level directory. Best regards, Boaz On Aug 22, 2017, at 4:06 PM, NADOLSKI Laurent <lau...@sy...<mailto:lau...@sy...>> wrote: Dear Boaz, I have noticed that the reorganization of the file broke the function atsummary and ohmienvelope atcollab2017_branch/atmat/atphysics/ParameterSummaryFunctions/atsummary.m One solution could be to move also the private directory : private/lyap.m but ohmienvelope used it as well and is now located in another directory. So to avoid duplication, lyap should not be anymore a private function. ohmienvelopedemo does not work because spear2rad is not in the path anymore (now: machine_data/spear2rad.m) Undefined function or variable 'spear2rad'. Error in ohmienvelopedemo (line 3) A quick fix is to add machine_data to matlab the path Best regards, Laurent. Dr Laurent S. NADOLSKI Coordinateur Exécutif des Accélérateurs Division Accélérateurs et Ingénierie, Synchrotron SOLEIL t: +33 (0)1 69 35 98 08 m: +33 (0)6 89 43 70 45 a: L'Orme des Merisiers Saint-Aubin BP 48, 91192 Gif-sur-Yvette CEDEX FRANCE w: www.synchrotron-soleil.fr<http://www.synchrotron-soleil.fr> e: nad...@sy...<mailto:nad...@sy...> Le 28 juil. 2017 à 13:26, Boaz Nash <boa...@es...<mailto:boa...@es...>> a écrit : Dear all, After some discussion at ESRF, we decided to set August 25 as our date to finish AT2.0. There is always more to be done, but we will do what we can and call it finished at that time. The development is continuing in the at2devel branch in the subversion repository in SourceForge: https://sourceforge.net/p/atcollab/code-0/HEAD/tree/branches/at2devel/ As mentioned, following this release, we will look for a migration strategy to using git and hosting on github under the atcollab organization: https://github.com/atcollab At the moment, we are doing some cleaning and reorganization of some of the functions in the repository. In particular, some categories have been added to atphysics, and functions are being moved to relevant folders. https://sourceforge.net/p/atcollab/code-0/HEAD/tree/branches/at2devel/atmat/atphysics/ I may do something similar to the lattice directory https://sourceforge.net/p/atcollab/code-0/HEAD/tree/branches/at2devel/atmat/lattice/ I also created folders in the atdemos directory: https://sourceforge.net/p/atcollab/code-0/HEAD/tree/branches/at2devel/atmat/atdemos/ There were already some demos here originally by Andrei, but I’ve been adding some new ones. This is a big job, and I hope others will help test and improve these demos. One principle I am trying to follow is to only use lattice files in the machine_data directory: https://sourceforge.net/p/atcollab/code-0/HEAD/tree/branches/at2devel/machine_data/ These lattice files are still rather varied- some use AT 1.2 style with global variables for the lattice creation, some may include RF cavities and others not. I hope we can use this directory to standardize on what we consider best practice for lattice files. Then if we make sure that all the demos in the atdemos directory run properly, we can be confident that a good amount of AT works properly with these lattice files. Glad to hear comments and get input or help before we release AT2.0. Best regards, Boaz ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ Atcollab-general mailing list Atc...@li... https://lists.sourceforge.net/lists/listinfo/atcollab-general |
