Elegant users forum

Posted: **06 Sep 2017, 07:54**

Dear Michael et al.,

I have a problem running elegant on Mac OS - never had any problems with same input files on linux.

The output is the following:

Code: Select all

flashbkr4:Lattice libov$ elegant FLASHForward.ele 
Running elegant at Wed Sep  6 14:47:46 2017

This is elegant 33.1.1, Jul 25 2017, by M. Borland, J. Calvey,M. Carla', N. Carmignani, M. Ehrlichman, L. Emery, W. Guo, R. Lindberg, V. Sajaev, R. Soliday, Y.-P. Sun, C.-X. Wang, Y. Wang, Y. Wu, and A. Xiao.
=====================================================================================
Thanks for using elegant.  Please cite the following reference in your publications:
  M. Borland, "elegant: A Flexible SDDS-Compliant Code for Accelerator Simulation,"
  Advanced Photon Source LS-287, September 2000.
If you use a modified version, please indicate this in all publications.
=====================================================================================
Link date: Jul 25 2017 10:14:54, SVN revision: 24422M
statistics:    ET:     00:00:00 CP:    0.00 BIO:0 DIO:0 PF:0 MEM:0
&global_settings
    inhibit_fsync = 0,
    echo_namelists = 0,
    mpi_randomization_mode = 3,
    exact_normalized_emittance = 1,
    SR_gaussian_limit = 3.000000000000000e+00,
    inhibit_seed_permutation = 0,
    log_file = {NULL},
    error_log_file = {NULL},
&end
statistics:    ET:     00:00:00 CP:    0.00 BIO:0 DIO:0 PF:0 MEM:0
Seeding random number generators
computed value for D1FL2EXTR.DY is 0.000000000000000e+00
computed value for D1FL2EXTR.N_KICKS is 200
computed value for D1FL2EXTR.BINS is 200
computed value for D1FL2EXTR.ISR is 1
computed value for D1FL2EXTR.CSR is 1
computed value for D1FL2EXTR.OUTPUT_INTERVAL is 10
computed value for D1FL2EXTR.INTEGRATION_ORDER is 2

Terminated by SIGSEGVProgram trace-back:
flashbkr4:Lattice libov$

It appears to happen with the dipoles, after coming to 'computed value for D1FL2EXTR.INTEGRATION_ORDER is 2' (for the case of D1FL2EXTR dipole)

Attached are the .ele and .lte files.

Thanks in advance for any advise!

Cheers
Slava

Posted: **06 Sep 2017, 08:05**

Slava,

I'm not able to reproduce the crash. Please add echo_lattice=1 to your run_setup command, then run again. This might provide an additional clue about the source of the problem, which appears to be in the lattice definition.

--Michael

Posted: **06 Sep 2017, 09:35**

I see this problem on MacOS too. I am looking into it now.

Posted: **06 Sep 2017, 16:07**

I found the problem. I'll try to get an updated release out soon. In the mean time you can workaround the problem by changing the CSRCSBEN definitions so that ISR=1 and CSR=1 instead of ISR="with_ISR" and CSR="with_CSR". These are incorrectly being stored internally as long values instead of short values when you set them this way and results in this crash.

Posted: **07 Sep 2017, 11:46**

There is a new minor release now 33.1.2 posted to our software page. I updated the MacOS and Windows links to this new version.

Posted: **07 Sep 2017, 23:43**

The 33.1.2 release indeed solves the problem, thank you so much!
Slava

Elegant users forum

SIGSEGVProgram trace-back

SIGSEGVProgram trace-back

Re: SIGSEGVProgram trace-back

Re: SIGSEGVProgram trace-back

Re: SIGSEGVProgram trace-back

Re: SIGSEGVProgram trace-back

Re: SIGSEGVProgram trace-back