After download you will have a disk image Maud.dmg in your download folder, double click it to mount the image and a Finder window will open showing the Maud folder that you can copy or drag where you want Maud installed.
The Maud folder has the following structure:
- Maud.app (the Maud application))
- plugins (folder)
Move the maud directory with all the content in the place you are more comfortable with. Be sure you have the rights to write in that directory.
Double click the Maud.app to start Maud.
If you get a message that the application is corrupted and cannot be run, than you need to enable applications not coming from the App store. To do it, open System Preferences, choose Security & Privacy and than change the option: Allow apps downloaded from: to Mac App Store and identified developers or Anywhere. Maud.app is signed by the author as developer and it should be recognised as from identified developers, but sometimes it does not work and you need the Anywhere option.
If this is the first java program you run on your OS X system, it will ask to download and install the Java VM. By default it will install the Java VM 1.6 from Apple. Another alternative is to download instead the Java VM 1.7 or higher from Oracle and install that one. Be aware that this is different from the Java embedded in the browser you may have already updated more than once. This is a Java server VM, the one embedded in the browser cannot run Maud or other desktop java applications.
Next version of Maud will be 1.7 only or higher, so it may be a good idea to already install the Oracle one as the one from Apple will not go higher than 1.6.
The first time Maud run, it will show the license agreement window and after you press the OK button it will show a dialog asking for a folder where to extract some files. These are files needed by Maud (databases, preferences etc. plus some examples) and to avoid to pollute your Maud folder it is advised to create another folder (it can be located inside the Maud one, we will call it the examples folder in the following). Be sure to enter inside the newly created example folder before pressing the Extract here button.
To check everything is ok, from the File menu, choose Open analysis… and choose the alzrc.par file inside the example folder. After loading it, press the calculator button in the toolbar to calculate the pattern. You should see a nice fit of the data with the residuals. You are set and ready to use Maud. If not check the troubleshooting section.
Tips (before or after installation)
- How to check if you the Oracle or the Apple java VM working by default:
Open a terminal window and type:
and check if the version of Java. If it is 1.7 or higher it’s the one from Oracle.
- If you have some troubles starting or running Maud and nothing you do can solve it, check first you have a startingLog file in the Maud folder. If there is not this file you don’t have a working java VM installed or something is wrong with the Maud.app, check the troubleshooting section. Otherwise you can send the startingLog file to the Maud author for help along with the content of the Maud console if you can reach the Maud main window.
- How to activate the Maud console and get more output, info and errors reported: when the Maud main window opens, select console visible from the Interface menu.
- How to use the same Maud installation for multiple users: install Maud in a folder accessible by all users and where all users have the rights to write in. Then each user has to start Maud using the Maud.app and on the first run extract all databases and examples in his own home folder (each user create a suitable folder somewhere and extract everything there). How it works: when Maud starts, it checks inside the Maud.app structured folder for a file named .maudpath_username where username is the User name. If the file does not exist, it will prompt for the license agreement and then ask for a folder where to extract the databases and example files. This folder is also used to store the preferences of Maud. The path to such folder is saved in the .maudpath_username file. This way each user will have his own folder with preferences etc. The unix environment should take care of running multiple instances of the program and each user keep separated files, analyses, preferences etc.
If something does not work, be sure your java virtual machine is properly installed and working and that you didn’t have a corrupted download of Maud. Re-downloading it sometimes solves the corrupted download problem. But be aware of proxy caching the downloads, it means that if the corrupted download is in the cache of the proxy server, you will download again the same corrupted archive. Changing network for the download or forcing a refresh and download 1-2 days after may solve the caching problem.
- Maud does not start using the Maud.app.
Open a terminal window and type:
if java is a recognised command, then the problem can be the aforementioned Security & Privacy setting preventing to run applications not downloaded from the App Store or the signature of the developer has not been recognised. Change the Security & Privacy setting. Otherwise you may have the wrong version of Maud. For OS X version > 10.6 and 64bit you need to download Maud for OS X > 10.6, the other will not work.
I have java but Maud does not start.This may be caused by a memory problem. You have a 32bit computer with a Java 32bit VM, but Maud is trying to allocate more than 2Gb of memory. You can change the memory settings of Maud, by right clicking over the Maud.app application and choose Show package folder. A folder will open, navigate inside the Contents folder and edit the Info.plist file. It is in xml format, go near the end of the file where you find:
in this case Maud is asking for 8Gb of memory with the -Xmx8192m string, change it to a value lower than 2 Gb, something like -Xmx1024m for 1Gb. Save the file, exit the folder and run Maud again. Otherwise see next point.
- Maud start, but you are not able to arrive to the Maud main window.
You may have either a Java VM not working properly or a corrupted Maud installation, in either case try to re-download one or the others or both and re-install them. Otherwise, check the startingLog file created inside the Maud folder when Maud starts and in case send it to the Maud author. Check the Tips section for more.