To make sure that you have installed Python successfully, type python on your
command line. You should see something like this:
Python 3.6.1 |Anaconda custom (x86_64)| (default, May 11 2017, 13:04:09)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
Navigate to the directory where you want to put the PmagPy folder,
git clone https://github.com/PmagPy/PmagPy.git
You should now have a full local copy of the PmagPy repository. Change
directories into PmagPy:
Next, you need to add PmagPy to your PATH so that the PmagPy
programs can be called from any directory. Try running:
python dev_setup.py install
If you see an error message, that means that you will also need to
specify the location of your Python installation. To get your full path
to python, you can run the following two commands (exactly as
dir python.exe /s /p
This can take a while, so be patient. You should get a result that looks
something like this:
Once you’ve done that, navigate back into your PmagPy directory and run
python dev_setup.py install -p path_to_python
where path_to_python is your specific Python result.
Note: dev_setup.py edits your $PATH and $PYTHONPATH variables. If
you need to set those variables by hand, see this section on editing your
PATH for PmagPy.
After completing the developer install, you will need to restart the
Command Prompt. After restarting, you should be able to use all PmagPy
functionality. You will be able to stay up-to-date with PmagPy
development and make edits in PmagPy code which will be immediately
available in your system.
On your command line, type “python” to start the interpreter. You will
import pmagpy and then run a simple calculation. Importing pmagpy
may take over a minute the first time, so be patient! It will be much
faster in subsequent runs.
>>> from pmagpy import pmag
Test the GUIs:
On the command line, open Pmag GUI by running:
If any of these commands don’t work, go back and carefully follow the install
instructions. If you still have a problem, try the Troubleshooting section. If you
don’t find an answer there, check out the existing Github issues and create a new
one if necessary.