It turns out the latest released version of scamp (from 2010…) isn’t compatible with recent versions of one of the libraries it depends on. It’s possible that in the future this will get straightened out (especially if I get around to figuring out how to fixing the scamp port file…), but in the meantime you’ll need to compile by hand. The last time I tried it, all the dependencies were fine, but scamp’s compilation failed. This will install all of scamp’s dependencies, and then try to compile and install scamp. An easy way to get these is to just download the source code and look in the “config” directory. One important caveat with extractor: the macports version installs the code, but does *not* include some of the files necessary to actually run SExtractor, like the convolution filters or default parameter files. ![]() At least on OS X 10.8 with my 2011 Macbook Pro, this just worked without any problems or modifications needed, and you can now use sextractor or swarp by just running “sex” or “swarp” anywhere. Macports will now install the “fftw-3” and “atlas” libraries (ATLAS can take a verty long time to build so be patient), and then install sextractor and swarp. You may not have to add “sudo” at the beginning of those commands, depending on how your permissions are set up, but the default way requires it. It turns out that sextractor, swarp, and scamp are all available on macports, but scamp doesn’t actually compile correctly. (You can get the command line tools either by getting Xcode and installing them via the prompts, or going directly to apple’s developer download site.) SExtrator, SWarp, and SCAMP Note that it will require C compilers, which you can get most easily via the Xcode command line tools. See the macports web site for instructions on how to get macports working. So these instructions will assume you are using macports. Others may prefer alternatives like fink or homebrew, but I’m not sure whether all the dependencies are available on them. I’ve found macports to be one of the best tools for managing such libraries, as it’s kept very up-to-date and is the easiest to use. While the first three have library dependencies needed before they will compile, they’re all open source libraries. I find this form of licensing a bit curious given the wealth of open source astronomy software already out there, but presumably there’s some reason for it. ![]() You have to e-mail the author (Peter Stetson) and ask him for a copy (and sign an agreement that you won’t re-distribute the code). The first three are all freely avaiable from their web sites, but DAOPHOT is a bit different. It turns out this is non-trivial on a recent Mac, so I’m posting here what I found to work, in the hopes that others may find it useful. As part of some upcoming work reducing pODI data, I needed to (re)install a number of different photometry tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |