Search found 390 matches
- 12 Nov 2021, 13:02
- Forum: Installation
- Topic: Compile SDDS and ELEGANT on CentOS7
- Replies: 5
- Views: 13274
Re: Compile SDDS and ELEGANT on CentOS7
When running it as a normal user, you will not be able to install any required system development packages. This error is probably from some of the required packages being missing. The list of packages it looks for are: tcl wget subversion gzip tar make rpmdevtools rpm-build gcc gcc-c++ gcc-gfortran...
- 12 Nov 2021, 12:56
- Forum: Installation
- Topic: Compile SDDS and ELEGANT on CentOS7
- Replies: 5
- Views: 13274
Re: Compile SDDS and ELEGANT on CentOS7
What version of linux are you using?
- 12 Nov 2021, 10:28
- Forum: Installation
- Topic: Install on Ubuntu 21.10
- Replies: 6
- Views: 6372
Re: Install on Ubuntu 21.10
I have not tried building it with Ubuntu 21.10 yet. I will get back to you later today with a solution.
- 10 Nov 2021, 11:19
- Forum: Installation
- Topic: Tcl/Tk package installation
- Replies: 5
- Views: 8358
Re: Tcl/Tk package installation
OAGTclTk-1.26-1.x86_64 should have installed: /usr/local/oag/apps/lib/linux-x86_64/tclIndex and /usr/local/oag/apps/lib/linux-x86_64/APSStandardSetup.tcl Make sure that the environment variable HOST_ARCH is set to linux-x64_64 There can also be an issue if you have the environment variable OAG_TOP_D...
- 04 Nov 2021, 11:29
- Forum: Parallel Elegant
- Topic: testing Pelegant on elegantExamples
- Replies: 16
- Views: 28699
Re: testing Pelegant on elegantExamples
I have updated the RHEL7 mpich versions. I removed the FORTIFY_SOURCE flag. I also check the RHEL8 version of mpich. It looks like Redhat removed that flag on RHEL8.
You can download the new version from the software page. It has the same name and version but a new release date.
You can download the new version from the software page. It has the same name and version but a new release date.
- 28 Oct 2021, 17:59
- Forum: Ring Tracking
- Topic: &correct does not work
- Replies: 11
- Views: 8619
Re: &correct does not work
There is a new Windows version of Elegant that you can download and try. There was a problem with not including enough of the redistributable Intel MKL DLL libraries. The version released today should fix the problem you are seeing.
- 22 Sep 2021, 10:08
- Forum: Optimization and Matching
- Topic: beta beat optimization
- Replies: 14
- Views: 9448
Re: beta beat optimization
The HOST_ARCH and EPICS_HOST_ARCH are environment variables that should both be set to linux-x64_64
If you are using the bash shell you can put this into the ~/.bashrc file:
export HOST_ARCH=linux-x86_64
export EPICS_HOST_ARCH=linux-x86_64
If you are using the bash shell you can put this into the ~/.bashrc file:
export HOST_ARCH=linux-x86_64
export EPICS_HOST_ARCH=linux-x86_64
- 21 Sep 2021, 08:56
- Forum: Optimization and Matching
- Topic: beta beat optimization
- Replies: 14
- Views: 9448
Re: beta beat optimization
Your message says the problem occurs on line 4. However exec oagtclsh "$0" "$@" should be on line 3. It appears that you have an extra line in there somewhere. I will post the entire contents of computeBeats below. You should be able to copy and paste it: #!/bin/sh # \ exec oagtclsh "$0" "$@" set au...
- 24 Aug 2021, 13:13
- Forum: Optimization and Matching
- Topic: beta beat optimization
- Replies: 14
- Views: 9448
Re: beta beat optimization
Can you run "file computeBeats" Does it say: computeBeats: POSIX shell script, ASCII text executable I want to make sure it doesn't mention CRLF line terminators which you could get if unzipped on Windows Next, do the top three lines look like: #!/bin/sh # \ exec oagtclsh "$0" "$@" If I remove the s...
- 23 Jun 2021, 18:12
- Forum: General
- Topic: sddsxref functions differently in one specific script
- Replies: 2
- Views: 2899
Re: sddsxref functions differently in one specific script
Most likely you will have to put the -leave=* inside quotes "-leave=*"
It sounds like bash is expanding the * value before passing it to sddsxref. So it is actually passing a list of files in the directory instead of *
It sounds like bash is expanding the * value before passing it to sddsxref. So it is actually passing a list of files in the directory instead of *