As of February 23, 2009, Firefly team is proud to announce the availability of the first official release of the Firefly package for Mac OS X/Intel platform.
List of some key features:
The Firefly for Mac project was initiated by Thomas Patko in a effort to bring the excellent Firefly ab-initio software to the Mac platform. It was made possible by extensive collaboration with the main Firefly project team and tireless beta testing and suggestions from Nick Greeves. Although Thomas is the major developer of Mac-specific code, as well as primary documentation contributor in the "Mac Port" at present in this initial release, the primary goal of the project is to develop the Mac edition continuously to make it more accessible and easy to use for chemists worldwide operating the Apple Macintosh platform.
The best method to accomplish this is to have an active collaborative environment where users are free to request features, report any bugs, and to have multiple contributors to the codebase for the "Mac Port".
The most recent official version of Firefly for Mac OS X is version 8.2.0
Quick Start Guide for Mac OS X version of Firefly v 8.1.0 Last updated: January 1, 2013.
Installation notes & usage guide for Mac OS X version of Firefly v. 8.1.0 Last updated: January 1, 2013.
Firefly version 8.2.0 build # 10203 Install image for Mac OS X Snow Leopard, Lion and newer versions of OS X Last updated: September 21, 2016. Note: this version is not compatible with Mac OS X Leopard and older versions of OS X.
The current source code and build instructions/documentation corresponding to the official 8.2.0 release of the Firefly for Mac job launch and run apps for developers is available upon request.
Download area: Windows/Linux Firefly, external basis set libraries, etc...
Running from a network drive is not currently supported. All of the file paths as well as the program itself need to run from a local drive.
If disk space is an issue for some calculations using just the internal drives (meaning that they would be out of space with this approach), we would suggest to use a large RAID array connected with a thunderbolt cable (it is very, very fast). This external raid array drive would still be a fully supported local drive from the WINE point of view (mounted under the /Volumes directory), but give ample additional space for temporary files which are probably the culprit for running out of local disk space. The path to the temporary files if fully configurable with all of drag and drop apps as well as the commandline script.
If a user wishes to modify any of the default variables for any drag and drop application (including where the temporary file reside), here is the easiest way to do it: Go to the "RUN-FIREFLY-JOBS" directory. Make a copy of the application that you wish to modify. As an example, let us suppose that I wish to modify the "Run-Firefly-Job-4-Cores.app" in the main "RUN-FIREFLY-JOBS" directory. Rename the app something reasonable that reflects the planned change. Do not leave an spaces or use any special characters. One example would be something like "Run-Firefly-Job-4-Cores-RAID-TEMP.app" Right-click on the copied and renamed application and choose the "Shown Package Contents" option. Double click on the "Contents" directory that opens in a new window after choosing this "Shown Package Contents" option. Double click on the "Resources" directory. Open the file with the extension *.config with a suitable text editor such as TextWrangler or BBEdit. Each of the *.config files are heavily commented to allow the user to modify all of the configuration variables that are loaded from this file at the start of the drag and drop application as may be desired. In our example of the "Run-Firefly-Job-4-Cores.app" drag and drop job launch application the path to the temporary files is found the fourth line and default is /tmp/FIREFLY/SCRATCH/ as shown. Any alternate local path may be selected (including RAID drives attached through a thunderbolt connector as recommended for large jobs with big temporary files and limited local internal hard drive space situations). The user should bear in mind that changing any of the default values for any of the variables may cause the application to cease working correctly if done improperly and so care should be taken with any modifications. In the case of the modification of the temporary file path directory it is recommended to select a path without spaces or special characters and to add the trailing "/" to the path designation to ensure proper job runs. Since we are working on just a copy of the original application if any problems are encountered that cannot be solved, we can always discard and restart from a new copy of a known working original.
Firefly team is grateful to all beta testers. Our special thanks to Nick Greeves and Lyndsey Vernon, University of Liverpool.
This Mac release of Firefly would not be ever possible without efforts and constant development made by Thomas Patko, who was the main
driving force behind Firefly for Mac project.
You are the th person, who visited this page since February 23, 2009.