These solutions are MAC OS platform-based, with cheap faster or slower machines, all of which though will give you access to those prized nVidia cards (the caveats about OS/drivers and DS version numbers mentioned above would apply here too). From what I hear, there are also many youtube videos that visually show how to set up such a rig. Jul 31, 2020.
These instructions should install the Anaconda Python distribution and three separate Anaconda environments:
- The Anaconda default (root) environment running Python 3
- An AstroConda environment running Python 3
- An AstroConda/IRAF environment running Python 2.7. This is because IRAF doesn't 'play well' with Python 3.
You can switch environments as needed.
Installation
The following installation instructions is a summary drawn from the Installation Instructions on the Space Telescope Science Institue AstroConda page. Refer to that page for more detailed instructions.
- Download Anaconda Graphical Installer (Python 3.6) from Anaconda Download and follow the instructions on that page to install Anaconda. NOTE: When you get to the Destination Select step, be sure to pause and select the Install for me only tab. This will install a directory under your login directory called
anaconda
. This seems to work better than installing system wide. - Open a terminal window and type
which conda
. If the installation worked, this should display the path to theconda
. - Configure Andaconda to install packages directly from the AstroConda repository.
- Create the Python 3 AstroConda environment. This command will generate some output and then will display the prompt
Proceed ([y]/n)?
. Just type y or hit<return>
to accept the installation. This is a large installation so it may take a few minutes to finish. - Now install the Python 2.7 package with IRAF by using the command: You will again be prompted to proceed with the installation. Again, it's a large amount of code so it will take a few minutes to install.
Working with environments
Installing these environments allows you to use whichever version of Python you need. For general purpose programming the default
root
environment is probably best. You don't need to do anything to activate the root
environment, but to activate the other environments you issue the command source activate environment_name. For example if you wanted to run ipython
in the astroconda
environment you would use the following commands. The which python command isn't necessary, but it was included to verify the path to the current environment is correct. The command ipython --matplotlib runs IPython with a switch that sets-up IPython to do interactive plotting.
The command source deactivate deactivates the environment returns the Terminal window to the default
root
environment. Warning: Activating an environment in a particular Terminal window only effects that terminal session and programs spawned from that session. All other Terminal windows continue to use the default environment.
The session below illustrates the effect of source deactivate.
Setup to use IRAF
In order to use IRAF you must activate the
iraf27
environment. The session below illustrates how to activate iraf27
and set up a new IRAF environment working directory. See the IRAF Tutorial to learn more about using IRAF. IRAF should now be running properly. However, if after entering the cl command you get the prompt
curdir:
instead of the usual 'Welcome to IRAF' message see the comment below. https://tempcofer.hatenablog.com/entry/2020/11/22/204832.Updating the environments
All of these environments are continually being updated to fix bugs and add features. Each of the environments is updated separately. To update the root environment including the Navigator app use the command conda update anaconda. To update all of the packages in the other two environments use conda update -n environment_name --all, where environment_name is either astroconda or iraf27.
The
This error usually occurs when the
curdir:
errorThis error usually occurs when the
SHELL
environment variable isn't read properly by IRAF. This installation of IRAF requires that SHELL=/bin/bash
. The sample session below illustrates the problem and how to fix it. NOTE: You can abort IRAF at the
curdir:
prompt by entering <control-C>. This is a guest post by Christine Slocum, a software engineer at Space Telescope Science Institute (STScI), on behalf of the Ureka team.
Last month, STScI and Gemini announced the first public beta release of the Ureka binary installer for common astronomical software (primarily for the UV/Optical/IR community). The goals of the Ureka installer are to:
- Minimize the number of actions needed to install all the different software components. We provide an install script that detects the user’s platform then downloads and installs the appropriate binary build.
- Permit installation without requiring system privileges.
- Make installs as problem-free as possible for the great majority of users. Cannyou download windows.on a mac.
- Allow users to install their own software (particularly Python-based) within this framework, or update versions of software within the framework. For example, pip and easy_install work just as they normally would.
- Permit different Ureka installations to coexist and to easily switch between them. This is useful if you want to try a new version of Ureka, but still want to keep an older one around as well. Basilisk anime episode 1.
- Enable installing different versions of the same software package under a particular Ureka installation.
- Support Macs and most popular Linux variants.
Ureka does not use the environment variable LD_LIBRARY_PATH (DYLD_LIBRARY_PATH on Macs) and thus should not affect existing software after installation or use.
Keep in mind that no installation system is completely foolproof–that’s nearly impossible to achieve. In particular, when users update or add software to the Ureka framework, they increase the risk of breaking something, but we feel that is an option users should have as long as they understand the risks.
This beta version includes IRAF 2.16 and associated packages for IRAF, DS9, and a fairly full suite of Python scientific software packages (e.g., numpy, scipy, and matplotlib). The full listing of included software can be found at this link: http://ssb.stsci.edu/ureka/1.0beta5/docs/components.html. Download porting kit for mac.
How To Download Iraf27 Mac Os
Ureka can be downloaded from: http://ssb.stsci.edu/ureka (choose “1.0 beta 5”). Installation and usage instructions can be found on the same web page. We have also provided an FAQ.
How To Download Iraf27 Macos
https://yellowwalk773.weebly.com/mac-product-key-finder-download.html. This is a beta release. We do expect to uncover some problems that we did not encounter during our testing. However, Ureka has institutional support from STScI and Gemini, so if you do experience problems, send an email to [email protected] for assistance. We also welcome feedback on additional software components you think we should include.