Search found 7 matches
- 04 Oct 2010, 10:08
- Forum: Ring Tracking
- Topic: Compare the result of the frequency map with AT
- Replies: 17
- Views: 23682
Re: Compare the result of the frequency map with AT
Hi, In my opinion, it is very difficult to identify the right tune in every case, especially when there is coupling and lattice errors. The highest peak of spectrum does not mean it is the tune. In the attachment, is the spectrum of x and y coordinate, 2048 turns, and the initial amplitude of x is t...
- 15 Dec 2009, 22:40
- Forum: General
- Topic: tracking get slower when using multiple watch
- Replies: 4
- Views: 2352
Re: tracking get slower when using multiple watch
Michael,
I woulkd like this to be automatic, since it is a common job people tracking 200 turns, with 2-3 watching elements. 60sec verses 3 sec is too long for a impatient person like me.
But not so ctirical, since the recipe you gave works very well.
Lingyun
I woulkd like this to be automatic, since it is a common job people tracking 200 turns, with 2-3 watching elements. 60sec verses 3 sec is too long for a impatient person like me.
But not so ctirical, since the recipe you gave works very well.
Lingyun
- 15 Dec 2009, 19:37
- Forum: General
- Topic: tracking get slower when using multiple watch
- Replies: 4
- Views: 2352
Re: tracking get slower when using multiple watch
Sorry, I forgot to comment out the junk pieces. Thanks Michael: The inhibit_fsync=1 does help! lyyang@lyyang-desktop:~/devel$ time elegant track.ele > /dev/null real 0m2.749s user 0m2.730s sys 0m0.010s lyyang@lyyang-desktop:~/devel$ time elegant track.ele > /dev/null real 0m59.292s user 0m2.990s sys...
- 15 Dec 2009, 17:57
- Forum: General
- Topic: tracking get slower when using multiple watch
- Replies: 4
- Views: 2352
tracking get slower when using multiple watch
Hi All, When I use 2-3 watch to record the beam position, I found the tracking is significantly slower, the data is only for 200 turns, should not be a problem, I have set output_at_each_step=0. Is there any other options to control this I may not set it right ? Does anyone have similar experience ?...
- 11 Dec 2009, 16:55
- Forum: Dynamic Aperture
- Topic: All particle lost, but give DA area very large
- Replies: 4
- Views: 22850
Re: All particle lost, but give DA area very large
Michael,
Thanks for this quick fix, I didn't build from source code, so the post process would be a best solution for me now.
Lingyun
Thanks for this quick fix, I didn't build from source code, so the post process would be a best solution for me now.
Lingyun
- 11 Dec 2009, 15:06
- Forum: Dynamic Aperture
- Topic: All particle lost, but give DA area very large
- Replies: 4
- Views: 22850
Re: All particle lost, but give DA area very large
Hi Michael,
Thanks for looking at this problem.
Here are the lattice file and kickmap.
Lingyun
Thanks for looking at this problem.
Here are the lattice file and kickmap.
Lingyun
- 11 Dec 2009, 14:06
- Forum: Dynamic Aperture
- Topic: All particle lost, but give DA area very large
- Replies: 4
- Views: 22850
All particle lost, but give DA area very large
Hi, I got a large DA, with a set of sextupole, but found that during the tracking of "find_aperture" all particles are lost. Then the (x,y)=(+/-1, +/-1) are the default one ? the Area=2 m^2. are they supposed to be zero ? Thanks Here are the ouput: lyyang@debian:~/devel/nsls2/trunk/optim$ sddsprinto...