| 3 | | Prerequisites: Before GSAS-II can be used on your computer, you must have two software packages installed, python and subversion. With 10.5 and 10.6, OS X comes with both installed, but alas, the supplied python versions do not include all the required packages (see below). Note that at present GSAS-II is only distributed via subversion. If you work at an institution with a firewall that blocks downloading files from subversion (uncommon, but known), contact your computer support department or arrange to perform the download from another location. |
| | 3 | Prerequisites: Before GSAS-II can be used on your computer, you must have two software packages installed, python and subversion. With 10.5 and 10.6, OS X comes with both installed, but alas, the supplied python versions do not include all the [PythonPackages required packages]. Note that at present GSAS-II is only distributed via subversion. If you work at an institution with a firewall that blocks downloading files from subversion (uncommon, but known), contact your networking support department or arrange to perform the download from another location. |
| | 4 | If you can help expand any of these instructions, discover new mechanisms for installing Python, or have problems getting this to work, please let [mailto:Brian.Toby@ANL.gov me know]. |
| 9 | | There are at least two options for loading a complete Python implementation. The [http://www.enthought.com/products/epd.php EPD] package is what we use for code development. In theory, you might be able to load just the missing packages, but it is not clear how easy that is to do. Use of the Fink or !DarwinPorts versions of Python is probably not a good idea -- the GUI and graphics will be shown in X-windows; if this indeed works, the performance will be poor. |
| 10 | | Feedback on packages other than [http://www.enthought.com/products/epd.php EPD] is welcome. Note that at this time, GSAS-II does not support Python 3.0 or greater and Python 2.7 is recommended. |
| | 10 | We do not have a lot of experience with options for loading the needed Python interpreter and packages on the Mac. The [http://www.enthought.com/products/epd.php EPD] package is what we use for code development. In theory, you might be able to load just the missing packages, but it is not clear how easy that is to do. Use of the Fink or !DarwinPorts versions of Python is probably not a good idea -- the GUI and graphics will be shown in X-windows; if this indeed does work, the performance will be poor. Note that at this time, GSAS-II does not support Python 3.0 or greater and Python 2.7 is recommended. |
| 20 | | Subversion is a software version tracking system that allows you to download and update the GSAS-II software from the APS subversion server (https://subversion.xor.aps.anl.gov/pyGSAS/trunk/). It is already installed in 10.5 (Leopard) and 10.6 (Snow Leopard) but not 10.4 Subversion likely can be found and downloaded for 10.4, but the latest EPD releases require 10.5 or later. GSAS-II can probably be made to run on 10.4, but this is not recommended. |
| | 20 | Subversion is a software version tracking system that allows you to download and update the GSAS-II software from the APS subversion server (https://subversion.xor.aps.anl.gov/pyGSAS/trunk/). It is already installed in 10.5 (Leopard) and 10.6 (Snow Leopard) but not 10.4. Subversion likely can be found and downloaded for 10.4, but the latest EPD releases require 10.5 or later. While GSAS-II can probably be run on 10.4, this is probably a lot more work than one would like. |
| | 21 | |
| | 22 | === Compiling Fortran Code === |
| | 23 | |
| | 24 | GSAS-II requires a small number of Fortran routines that are incorporated as Python packages (.so files). GSAS-II is distributed with these files compiled for a number of python versions, but if you are using something that does not match what we distribute, you may need to compile the Fortran routines yourself using the !NumPy f2py routine and the compiler of your choice. Both G77 (32-bit Python only) and GFortran have been successful on the platforms we have tried. |
| | 25 | |
| | 26 | To help with compiling the programs, use the python scons routine inside the GSASII/fsource directory. If you are lucky, this routine will find the needed compiler and python program, set all options correctly for you and run all steps needed to prepare the .so files. This is done by |
| | 27 | (1) opening a Terminal or xterm window, |
| | 28 | |
| | 29 | (2) using the {{{cd}}} command to set your working directory to {{{.../GSASII/fsource}}} and |
| | 30 | |
| | 31 | (3) simply typing "{{{scons}}}" in the window. |
| | 32 | |
| | 33 | If you need to change any options, type "{{{scons help}}}" to see a list of the possible command-line arguments and the values for the options. For testing, help can be used with command-line options to see how they will change the variables. |
