Find Google software downloads at CNET Download.com, the most comprehensive source for safe, trusted, and spyware-free downloads on the Web. SkyView Free is a beautiful and intuitive stargazing app that uses your camera to precisely spot and identify celestial objects in sky, day or night. Find popular constellations as they fade in and out while you scan across the sky, locate planets in our solar system, discover distant galaxies, and witness satellite fly-bys.
SkyView Free brings stargazing to everyone, and it's totally free. Simply point your iPhone, iPad, or iPod at the sky to identify stars, constellations, satellites, and more. Downloaded over 9 million times. If you like our Free version of SkyView then you'll love our full version. It includes: a convenient Apple Watch app, a Today Widget displaying tonight's brightest objects, ALL in-app purchases offered in this Free version, thousands more objects to discover, and more.
You don't need to be an astronomer to find stars or constellations in the sky, just open SkyView Free and let it guide you to their location and identify them. SkyView Free is a beautiful and intuitive stargazing app that uses your camera to precisely spot and identify celestial objects in sky, day or night. Find your favorite constellations as they fade in and out while you scan across the sky, locate the Moon, discover distant galaxies, and witness satellite fly-bys. Features: Simple: Point your device at the sky to identify galaxies, stars, constellations and satellites (including the ISS and Hubble) passing overhead at your location. Sightings: set reminders for celestial events and plan an evening stargazing & spotting satellites.
Augmented Reality (AR): Use your camera to spot objects in the sky, day or night. Sky Paths: Follow the daily sky tracks for the Sun and Moon to see their exact locations in the sky on any date & time. Time Travel: Jump to the future or the past and see the sky on different dates and times. Social: Capture and share beautiful images with friends and family on social networks. Mobile: WiFi is NOT required (does not require a data signal or GPS to function). Take it camping, boating, or even flying.
Supports Space Navigator binoculars, spotting scope, and telescopes. What a fun way to teach yourself, your children, your students, or your friends about our wonderful universe. Full Specifications What's new in version 3.5.1 Dear Stargazer, This release of SkyView addresses a few, small bugs regarding iOS 10. Happy Stargazing. General Publisher Publisher web site Release Date February 16, 2017 Date Added February 16, 2017 Version 3.5.1 Category Category Subcategory Operating Systems Operating Systems iOS Additional Requirements Requires iOS 8.0 or later. Compatible with iPhone, iPad, and iPod touch.
Download Information File Size 70.26MB File Name External File Popularity Total Downloads 39,074 Downloads Last Week 48 Pricing License Model Free Limitations Not available Price Free.
Wow, Nor Pirzkal and Francesco Pierfederici have kept quite busy making small updates to They released another new version today (available for ). Here’s the entire description of the changes in this version of Scisoft OSX from the release notes: This version updated Python to version 2.5.1 and correct some minor issue with the bash version of the irafuser.bash script when running under OSX 10.5 Leopard. Missing GCC runtime fortran libraries are also now included. This version was test under OSX 10.5 and seems to run fine. Note that 10.5 does deal with X11 applications slightly differently.
Once the Setup.bash script has been sourced, you should add the following line to your.bashprofile: export DISPLAY=127.0.0.1:0.0 This will enable all Scisoft X11 applications to start from Terminal.app I am not running Leopard (and probably will not switch until the winter break, when I have time to deal with all the X11 issues it creates), so I can’t confirm the ability to run under Leopard, but its great to know they are keeping SciSoft OS X up to date. Issues with this Release of Scisoft OSX. I did notice this new version of Scisoft OSX doesn’t appear to link its IRAF install with the rvsao IRAF package (used for radial velocity computations). Doesn’t matter to me to much since I compiled the newer version and linked to it, but it is funny they include the package at /scisoft/all/packages/iraf/extern/rvsao but don’t link to it in the $hlib/extern.pkg file, which I do believe they did in the older versions. I may not have noticed this earlier, but in the libraries directory /scisoft/i386/lib, some of the symbolic links are broken. Specifically:.
All the items in this directory linking to the OpenMotif library items are not linked, it appears /scisoft/i386/Packages/OpenMotif-2.3.0/lib doesn’t exist. However, /scisoft/i386/Packages/OpenMotif-2.3.0/lib.org does.
So I symbolically linked lib to lib.org via: cd /scisoft/i386/Packages/OpenMotif-2.3.0/ ln -s lib.org/ lib And now all the links to the OpenMotif libraries within /scisoft/i386/lib work. The library is mis-linked to an older version which no longer is installed.
So I needed to: cd /scisoft/i386/lib/ rm libcfitsio.a ln -s./Packages/cfitsio-3.040/lib/libcfitsio.a libcfitsio.a and the library was properly linked again. libpng.so was apparently not compiled within /scisoft/i386/Packages/libpng-1.2.10/lib, so there is no quick fix for that broken link. I removed a link to python2.4 in /scisoft/i386/lib and replaced it with a link to python 2.5: cd /scisoft/i386/lib/ rm python2.4 ln -s./Packages/pygtk-2.8.6/lib/python2.5/ python2.5. All the headers in /scisoft/i386/include/ are linking to an older version (3.006) instead of the current installed version (3.040). Fixed via: cd /scisoft/i386/include/ rm -f drvrsmem.h fitsio.h fitsio2.h longnam.h ln -s./Packages/cfitsio-3.040/include/.h.
There are symbolic links in the /scisoft/i386/bin directory to a variety of executables from the plotting package which doesn’t appear to have been installed as part of the Scisoft OSX distribution. Not really a bug, but the version of is version 4.1.3 and not the current version 5.0.0. Of course, given the long history of dangerous version X.0.0 software, this maybe safer that way.
On October 15, the folks behind SAOImage released. The big change I noticed is they now have a completely MacOS X native (read “Aqua”) version of ds9 (but only if you use the application package version of ds9, the command line versions remain X11)! I downloaded the following three versions:. The tells us that this release includes:. MacOSX Aqua Support: DS9 has been ported to MacOSX Aqua and is an universal application which no longer requires X11.
Compressed FITS Support: DS9 supports compressed FITS images using RICE compression. Mask Support: DS9 supports overlay masks. A mask is defined as a valid FITS image, in which a non zero value indicates that the selected mask color is to be displayed instead of the data value color. SkyView Support: DS9 provides support for HEASARC’s image cutout service, SkyView. This site provides image cutout service for a number of image surveys, including SDSS.
Multi-Language Support: DS9 provides multi-language support. By default, the language used for menus and dialog boxes is based on the value of the operating system locale variable. The user may override the default value by selecting the desired language in the preferences or by the -language command line option. Preferences: Preferences are automatically saved when a user changes an option. Selecting the saving preferences menu item is no longer needed.
More detailed release notes. I was able to get this version of ds9 integrated with SciSoft OSX by doing the following:.
Decompress the command line version of ds9 via the terminal using tar xzvf ds9.darwinppc.5.0.tar.gz (PPC version) or tar xzvf ds9.darwinintel.5.0.tar.gz (Intel version). When the decompression is done, all you have is an executable called ds9. Next, from the terminal, go to the /scisoft/bin directory (on PPC) or /scisoft/i386/bin/ directory (on Intel) and rename the old ds9 executable to something like ds9old (using something like mv ds9 ds9old). Copy your newly decompressed ds9 executable into the SciSoft OSX binary directory. I should note the command line version of ds9 still requires X11.
The had a post from someone having issues getting the IRAF package to compile properly on MacOS X on Intel-based Macs. I’ve commented about this before and had discussions with Doug Mink, the fellow behind rvsao as I have battled to compile it. It’s not actually that tricky, you just have to be careful. The key issue is that the most commonly used g77 compiler on Intel-based Macs is probably g77 version 3.4 as downloaded from the site. This version of g77 is a bit more picky about logical statements. Specifically, when you try to compile rvsao within IRAF using mkpkg, you get the following error ): I’m trying to install the external package rvsao on my Intel mac.
However, when I go to do the mkpkg there is a program “writetemp.f” that won’t compile: In subroutine `tmpwrf': writetemp.f:139: if (.not.(debug.eq.true.)) goto 130 1 2 3 Use.EQV./.NEQV. Instead of.EQ./.NE. At (2) for LOGICAL operands at (1) and (3 I was having exactly these sorts of errors with not only rvsao, but several of the SAO IRAF packages this summer and after banging my head on this a bit, I found a solution that worked for me. It turns out g77 needed to be told to use less restrictive logicals via a “-fugly-logint” flag during the compile.
So was to write a perl script that was saves as /usr/local/bin/f77, such that when f77 was called (by these IRAF mkpkg calls) it would issue a g77 call with this flag set on the compile. So started by Phil Massey. I got a response from Mike Fitz where he points out that you can set up the XC compiler used by IRAF to always use these flags via environmental variables: If you use ‘g77’ all the time and need this flag it can be set for all compilations either in the user environment (e.g. Your.cshrc file) using: Code: setenv XCF77 g77 setenv XCFFLAGS “-fugly-logint” or for problematic packages you can edit the ‘mkpkg.inc’ file for the package (normally in the pkg$lib directory but in the case of RVSAO it’s in the main rvsao$dir) to add “-/fugly-int” to the ‘XFLAGS’ definition. The ‘/’ tells the XC compiler to pass the flag thru to the underlying compiler unchanged, but note this sometimes causes problems or warning if say g77 knows the flag but gcc doesn’t (i.e.
The XFLAGS are passed to all sources being compiled, you’ll need the XCFFLAGS trick to pass only to fortran code). I haven’t played with this personally yet, but since I will be working on a paper for publication shortly, it looks like this might come in very handy. Figueroa-Centeno in the Department of Mathematics in Hawai`i has for getting the LaTeX syntax checker, running under MacOS X.
It doesn’t look terribly difficult. He includes instructions and a script for integration, which makes me a happier BBEdit user. To quote from the website: ChkTeX has been written in frustration because some constructs in LaTeX are sometimes non-intuitive, and easy to forget. It is not a replacement for the built-in checker in LaTeX; however it catches some typographic errors LaTeX oversees. In other words, it is Lint for LaTeX. Looks promising for me. I use when C programming (I installed splint via using the command line sudo port install splint), so the idea of a Lint for LaTeX is appealing.
I’ll be visiting Dr. Figueroa-Centeno’s website on for full details on installing it, once I get a break from teaching. Another new version of has been released and is available for. Here’s the entire description of the changes in this version of Scisoft OSX from the release notes: This version contains an updated ESO-MIDAS package.
I checked the list of packages included and sure enough, the only change was in the ESO-MIDAS package (whose current version is actually 07SEPpl1.0). (previously MIDAS 06FEBpl1.0) I don’t use ESO-MIDAS, which is an image reduction package aimed as users of ESO’s La Silla facilities and the VLT at Paranal, so I can’t really comment as to the usefulness of this update.
As with previous versions of Scisoft, the release notes warn if you use Aquaterm devices for PGPLOT, GNUPLOT, or any other packages that you “must manually run /scisoft/i386/Applications/Aquaterm.app once first to enable the aquaterm devices.” I have also confirmed that this release also fixes the problem with symbolic linking to mkpkg and xc in /scisoft/i386/bin/. Thanks for the fix guys! Finally, as I noted with the last release of Scisoft, my standard method for updating Scisoft OSX is to move my existing /scisoft directory to /scisoftold and then I unpack the new version.
That way, in case anything goes wrong, I can always switch back. When I first came to I was irritated by the fact that their wireless network didn’t use some authentication scheme.
Instead it is open, but useless unless you log in via a Cisco VPN client. This was irritating to me because the Cisco VPN server (at least the setup for MSUM) was not compatible with the built-in VPN clients in MacOS X. As such you had to use Cisco’s incredibly poorly designed client.
It worked, but everytime I wanted to connect, I had to launch the Cisco VPN application, then log in. The password was not remembered in Apple’s Keychain, which was just un-Mac-like. Lo and behold, a few week’s after getting here, I discovered the (then) newly introduced Cisco VPN frontend for the Mac,. It lives in the Menubar and all I every had to do to log in to the campus VPN network is go to the Shimo menu and click “Connect”.
This has actually come in very useful when I am away from campus since access to the VPN network allows me to connect to any MSUM server as if I was local, so I have been able to send outbound mail from Arizona, run IDL (using the campus license server) from Minneapolis, and so on. Setting up for use here is fairly simple. First go to the.
![Google Skyview Free For Osx Google Skyview Free For Osx](/uploads/1/2/5/6/125641505/418248281.jpg)
Download and install the appropriate client for MacOS Cisco VPN client software. Launch Shimo (it’s in the /Applications directory).
It’ll appear on your menubar as a “doorway” icon. Click on it and select “Preferences”.
In the General Preferences tab, I just set up Shimo to launch on startup, to disconnect the VPN on quit, and to show how long I have been connected on the menubar. I then when to the Profiles tab and clicked on the + button near the bottom of the pane to add a profile. When the Profiles sheet appears, I just set up a “msumvpn” profilename in the General tab:.
Under the Authentication tab, I had to set my username and password (blurred out here), and here’s the tricky bit, at MSUM, the Authentication method is “Group”, so you have to know the Group name and password, which (as revealed on the page for MSUM) are “wireless” and “dragon-wireless” respectively. With those four pieces of information, the MSUM VPN account was setup. I clicked “OK” to accept. The passwords are stored securely in Apple’s Keychain, so I never have to worry about them again. Under the Connection tab, I had to tell Shimo the address of my server (“msumvpn.mnstate.edu”) and the VPN protocol (IPSec over UDP). Now all I do is go to my menubar and select “Connect” and I am connected to the VPN.
Now, with a nice, simple, mac interface, the only issue I have with the MSUM VPN server is that it disconnects you from the VPN after about 60 minutes. If this bothers you, you can set up Shimo to automatically reconnect if the connection is dropped and/or to automatically connect if it sees the “msum-wireless” wireless network. Its all under the Profile “Advanced” settings. Tags: Category. I have found that the folks here at are fairly operating system agnostic (unlike St.
Cloud State University, which was relatively hostile to any OS not from Redmond). Usually if there is a problem, it is not because MSUM folks choose a Microsoft solution, but rather it is lack of documentation. This is one such case. I was trying to get my Mail program to talk to the MSUM directory server. It’s not hard, but it wasn’t documented anywhere (for either MacOS or Windows).
So I talked to Bill Scheffler, the local Mac guru, and in short order he produced a set of instructions which I am now placing online (with his permission). These instructions are for Macs running the current version of MacOS X (10.4). You can probably use them to figure out what you need on other operating systems from this. Open the Address Book application. Select Preferences from the Address Book menu. Click on the LDAP icon in the toolbar. Click the + button in the lower left hand corner to add an entry.
Fill out the fields with the following:. Name: Anything that works, I use “ MSUM LDAP“. Server address: ldap.mnstate.edu.
Search Base: ou=Users, dc=mnstate, dc=edu Once you are done, everything should look like the screenshot below:. Click the “Save” button and the LDAP section should match this screen:. Click the red close button in the top left hand corner to save changes and setup is done. Note that when you have done this, Mail.app will automatically look up matching names in the directory as you type. However, it only works if you are connected locally to the MSUM network (or if you are connected to the MSUM VPN remotely). Is an easy way to install a lot of programs. However, it does occasionally have glitches.
I installed xephem, a very powerful astronomical ephemeris package, today using sudo port install xephem Everything worked fine except when I launched xephem, it couldn’t seem to find any of its ancillary data files. A quick search revealed that they were located in /opt/local/share/xephem/. I suspect because I previously used a manually installed version of xephem, it was searching for the ancillary files in /usr/local/xephem and not finding the data there.
After reviewing the documentation for xephem the solution turned out to be simple. I was storing my private settings in the directory /.xephem and telling xephem to look in that directory using the following line in my /.xephemrc file XEphem.PrivateDir: /.xephem So all I did was open the file /.xephem/XEphem (capitalization important) and edit the line pointing to the shared directory to read: XEphem.ShareDir: /opt/local/share/xephem/ That told xephem to look in the new location in the MacPorts directories and not the default one in /usr/local/xephem. I guess RTFM can actually be important!
Francesco Pierfederici and Nor Pirzkal have released a new version of which is available for. Here’s a quote from their blog about the changes: This version is contains the latest STSDAS and TABLES Iraf packages as well as updates of a few packages.Startup scripts have also been modified to try to get around conflicts with Fink.
Please let me know if you are still getting problems with Scisoft when Fink is installed. Like many Macintosh users, the first few months of using I wasn’t even aware of what the Keychain really was. After a while, you realize just what a cool little piece of security it is.
It ensures many MacOS X programs can securely store passwords and other information without the programmer having to be a great cryptographic genius. One of my favorite programs which exploits this is. 1Passwd stores all your web form passwords (and any other data you care to secure, like credit card numbers or software serial numbers) in a Keychain, so the cryptography is managed by Apple’s Keychain. Recently, on my iMac at home, 1Passwd started locking up whenever it tried to access it’s keychain. Specifically, I have updated 1Passwd so it presented me with a dialog to allow the updated version access to the Keychain. When I clicked continue, the dreaded rainbox beachball of doom showed up and would not go away.
From that point on, logins to the machine failed and most Apps using the keychain were unable to use the keychain. I checked the system usage from the command line top -u -s 5 and discovered a program called securityd was eating up CPU cycles and RAM. I called up the manual page on securityd via the command line: man securityd and discovered: securityd maintains security contexts and arbitrates cryptographic operations and Security Authorizations. Access to keychain items is routed through securityd to enforce access controls and to keep private keys out of user process address space. Authorization calls also communicate with securityd to enforce rules contained in the /etc/authorization database.
All user interaction with securityd is mediated through the Security Agent. So by locking up securityd, I was messing up all the cryptographic operations that ran through it. I figured there had to be a corrupted file on my computer that was mucking up the works, but where.
My first thought was a corrupted keychain file, so I checked out my keychains using the “Keychain First Aid” item in the Keychain Access (in /Applications/Utilities) shown in the figure below. The files all checked out as intact, so that wasn’t it. Something was corrupted on my computer, but what. Just a Google search on “securityd” later, I found the solution on the programmers blog in an article titled ““. In a nutshell, the corrupted file is a cryptographic database at /var/db/CodeEquivalenceDatabase. In order to fix this problem they suggest: just open the Terminal (/Applications/Utilities/Terminal) and type: sudo mv /var/db/CodeEquivalenceDatabase /var/db/CodeEquivalenceDatabase.old Upon rebooting, God should be in His Heaven and all should be well with the keychain.
And I verified this worked to fix my iMac and all the Keychain apps are happy again. Update: I have updated this blog entry to reflect some updated information from Nor Pirzkal regarding the best way to fix this glitch. This problem has been fixed in During my adventures compiling the hectospec-related IRAF packages, I was using and discovered there were a couple of issues with the symbolic links for the mkpkg command necessary for compiling new IRAF packages. In the mkpkg appears to be mis-linked, so it can’t be executed. So I did the following in the terminal: cd /scisoft/binsudo rm mkpkgsudo ln -s./iraf/iraf/unix/bin.macosx/mkpkg.e mkpkg.
In the and, there are some missing symbolic links to mkpkg and xc in the directory for MacIntel binaries. As a result, both mkpkg and xc were instead pointing to PowerPC binaries. I fixed this as follows (again, from the command line): cd /scisoft/i386/bin/sudo ln -s /scisoft/all/packages/iraf/iraf/unix/bin.macintel/mkpkg.e mkpkgsudo ln -s /scisoft/all/packages/iraf/iraf/unix/bin.macintel/xc.e xcThis mis-linking certainly didn’t help getting things to compile under MacIntel, since IRAF was attempting to compile MacIntel code using PowerPC versions of mkpkg and xc. Thanks for Nor Pirzkal for giving me some feedback on fixing this problem. He tells me he has made the appropriate changes so that the next version of Scisoft OSX will not have this issue.By the way, my complaint here should in no way be construed as a critique of the efforts of Francesco Pierfedericki and Nor Pirzkal in putting together. They have done a great deal of work to put together an awesome package. For two people to track over 2 GB of software and not expect some glitches is unrealistic.
And I for one am extremely grateful that his efforts have saved me a lot of time.