find_aperture throws SIGSEG

Moderators: cyao, michael_borland

Post Reply
Julian
Posts: 17
Joined: 21 Mar 2013, 11:42

find_aperture throws SIGSEG

Post by Julian » 27 Mar 2013, 03:33

Hi,

i have not found any hint on how to get find_aperture working with Pelegant. Everytime i start my job, even this minimalistic attached one, the last line on the log is:

Code: Select all

Terminated by SIGSEGVProgram trace-back:
The process is still running on all cores, but there seems to be no progress. That's why i cancel that job.

Is there a work-around for this problem or is find_aperture not suitable for Pelegant or what am i doing wrong?


Thanks a lot

Julian
Attachments
parallel-error.log
Log of a run
(3.7 KiB) Downloaded 398 times
parallel-error.lte
Lattice file
(4.16 KiB) Downloaded 423 times
parallel-error.ele
Minimalistic Elegant file
(263 Bytes) Downloaded 401 times

michael_borland
Posts: 1772
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: find_aperture throws SIGSEG

Post by michael_borland » 27 Mar 2013, 07:54

Julian,

The recommended mode for parallel elegant is "n-line", which works fine for parallel and serial modes. The code is actual *supposed* to exit with an error message when other modes are used, since they have not been parallelized.

By the way, you need not define a beam (&bunched_beam) for &find_aperture. It isn't related.

--Michael

Julian
Posts: 17
Joined: 21 Mar 2013, 11:42

Re: find_aperture throws SIGSEG

Post by Julian » 27 Mar 2013, 10:14

Thank you.
Now this works with mode="n-lines". I'm sorry for taking your time.
Last edited by Julian on 16 Apr 2013, 06:41, edited 1 time in total.

michael_borland
Posts: 1772
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: find_aperture throws SIGSEG

Post by michael_borland » 27 Mar 2013, 10:19

No problem. Sorry for the bug and lack of clarity in the documentation.

Post Reply