Welcome to Magan 3.12 for Windows XP & Windows 7

This README file contains important information about Magan
For technical information, please contact the software author by sending an
e-mail to:

antonio.schettino@unicam.it

If you use Magan for research, please cite the following paper:

Schettino, A., 2012. Magan: A new approach to the analysis and interpretation of marine magnetic anomalies, Computers & Geosciences, 39C, 135-144, doi:10.1016/j.cageo.2011.07.007.


1. Installation
   ------------

Magan does not need of an installation procedure. Simply run an instance of the program from its main folder.
However, for a correct operational environment you must meet the following minimum requirements:

- 2 GB RAM (4 GB recommended)
- An Intel Core 2 duo/quad processor or an Intel core i5/i7
- Windows XP, Windows 7, or Windows 8
- About 32 MB of free hard disk space
- A color display. It is recommended to set the resolution to 1280960 or higher;
- A color printer
- A mouse

Please do not delete any of the files included in the following distribution list, as this operation could prevent
the correct execution of the program.


2. File List
   ------------

- Magan_3.12.exe:	Magan binary
- License.txt:		License File
- Readme.txt:		This file
- Terrainbase.bmp:	256-color bitmap of world topography (5 min resolution)
- Terrainbase.hdr:	Header file for Terrainbase.bmp
- Magan Help 3.12.pdf:	Help of Magan
- Data:			Folder containing optional data (rotation model, Kp indices, time scale, etc.)
- Tests:		Folder containing some examples (requires data in the Data folder)


3. Examples
   ------------

Three examples are included in this distribution. They work only if the main Magan folder is c:\Magan. Otherwise,
you should open the project files: .\Tests\02020049\02020049.1.txt, .\Tests\09090002\09090002.1.txt, and
.\Tests\67010068\67010068.3.txt through a text editor (e.g., Notepad) and substitute all the occurrences of
strings "C:\Magan\" by the correct path (e.g., "E:\Marine Geophysics\Magan\"). All these examples are analyses of
data from the NGDC GEODAS data base in the central Atlantic.


4. What is new in version 1.3 (January 2011)
   -----------------------------------------

This version allows to select a group of consecutive blocks from one side only through the Alt-Gr + Tab keys. This is
useful to fit a given anomaly on one side only using a constant stage velocity. Version 1.3 also allows to import
MGD77T and MAG88T track files from the NGDC data base.


5. What is new in version 1.4 (April 2011)
   -------------------------------------

This version allows to:

	> Import projected XYZ data files. Therefore, in this case source data are considered as already projected,
	  and the flow line is built directly from the data;
	> Import a sequence of survey-time geomagnetic field directions for a set of control points. This allows
          Magan to calculate accurately the model anomalies in the case of large flow lines;
	> View plots of unsorted magnetic data. These plots are useful to detect inconsistencies of the projection
	  procedure, mainly associated with navigation errors, when data from more ship-track segments are averaged
	  along the flow line.

6. What is new in version 2.0 (May 2011)
   -------------------------------------

This new version allows to change the obliquity of spreading independently for each block in the model


7. What is new in version 2.1 (August 2011)
   -------------------------------------

This new version allows to set new global parameters, to reset a model, to remove ridge jumps, and removes a bug in the
calculation of model anomalies when the spreading obliquity is different from 90.


8. What is new in version 2.2 (September 2011)
   -------------------------------------

This new version allows to recalculate and assign the ship-track anomalies from an IGRF/DGRF total field data file.

9. What is new in version 2.2.1 (January 2012)
   -------------------------------------

In this new release, the horizontal range of model windows encompasses the entire flow line, not just the range of projected
anomalies. A serious bug in the calculation of model anomalies, when the obliquity angle is different from 90, has been fixed.

10. What is new in version 2.3 (March 2012)
   -------------------------------------

This release allows to assign a starting chron. This option is useful to remove from the magnetization model any block older
than a specified chron, for instance when you are modelling the oldest anomalies close to the COB. This version also allows
to rebuild the magnetization model when some global parameter has been changed in the main window.

11. What is new in version 3.0 (July 2012)
   -------------------------------------

This release includes the following new features:

- Capability of setting the starting chron independently for the left and right sides of a magnetic profile;
- Fixed a bug of time - distance plots in presence of ridge jumps;
- Automatic setting of IGRF parameters;
- Improved user interface in modelling windows;
- Capability of resetting the left or right side magnetization models independently;
- Block grouping mode in modelling windows. Now you can select a group of subchron blocks with a single mouse click;
- Fixed a bug in exiting modified modelling windows;
- Ridge location is now displayed taking into account of spreading obliquity parameter;
- Capability of displaying time - angular distance plots;
- Fixed a bug in the fitting procedure of stage analysis.

12. What is new in version 3.1 (July 2013)
   -------------------------------------

This release includes the following new features:

- An efficient algorithm of despiking;
- Capability to create theoretical magnetic anomaly profiles with specified parameters

12. What is new in release 3.11 (May 2014)
   -------------------------------------

This release includes the following new features:

- More efficient way to import IGRF geomagnetic field parameters for anomaly modelling

13. What is new in release 3.12 (August 2014)
   -------------------------------------

This release fixes a bug that prevented correct reading and projection of some background images (bmp files).
