Ferret is an application produced by the NOAA . It is an interactive computer visualization and analysis environment used by Geographers and the like. This is how I installed it onto Ubuntu 10+ and my notes from following their install guide.
Download the three files into a know location. I keep all my software files together so inside my software folder I created a new folder called ferret and used wget to grab copies. This means I have a record of what files and versions I’m using:
mkdir -p ~/software/ferret cd ~/software/ferret
These are links to the 32bit versions. You are advised to check that this is what you want and that the 64bit versions would suit your system better – see note at bottom. I use
wget to grab these.
Change to the recommended install location and create a new folder called ferret and step into this folder. You will probably need to SUDO from this point on.
cd /usr/local mkdir ferret cd ferret
Installing the Support Files
Now you need to extract the support files into the ferret folder you just created. Type:
sudo tar -xzf ~/software/ferret/fer_environment.tar.gz
~/software/ferret/ is replaced with the location you saved the original download files in. Doing a
ls in that folder should now give you the following listing – different to what is given on the NOAA install pages.
bin contrib examples ext_func go ppl
Now you need a location to store the sample files for ferret and should extract them from the downloads location.
sudo tar -xzf ~/software/ferret/fer_dsets.tar.gz
which should give you:
data descr grids
You should now be able to install ferret using a supplied script. If you have followed the instructions above you can run.
And make the following choices:
To customize the paths so Ferret knows where to find everything we must do the following:
/usr/local/ferretas the FER_DIR if you followed the instructions above.
/home/username/fer_dataas FER_DSETS if you followed the instructions above.
Lastly you need to add the required paths to your bash path profile by running the script created in the previous section. Type:
at the command line where
/usr/local was the location selected above for the path files. You should now be able to run Ferret with the
ferret command. Success should equal something like:
NOAA/PMEL TMAP FERRET v6.71 Linux 2.6.32-131.6.1.el6.x86_64 32-bit - 08/08/11 30-Aug-11 10:31 yes?
quit to exit.
If this doesn’t work – then jump to the bottom to see a possible resolution.
However, once you have closed your terminal window you will also lose the ability to type ferret into the command line with success. So I recommend you add the sources line to your bashrc file (at the top):
Set up your Graphical Interface
So that you can get graphical output from your workstation you need to specify the X windows display correctly Ferret suggests you type
setenv DISPLAY WORKSTATION:0.0 where WORKSTATION is replaced with the name of your machine. You can find out your hostname by typing more
setenv is not a Ubuntu Bash command and if you try it you are likely to get
setenv: command not found. There are also issues with DISPLAY as explained on this page. The following code should work:
NOTE: There is a problem with this section that appears to crash the terminal 🙁 On running the test (below) and closing the test window the terminal becomes unresponsive and leaves me with the following message.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 318 requests (50 known processed) with 0 events remaining.
I’ve done a quick search and spend a few moments trying to resolve it but didn’t find any immediate success and with other stuff to do today I’m going to need to leave it here for now.
You can test your setup with the following command (be sure to type ferret first and get the yes? prompt:
Error: bash, no such file or directory
SO this was a marginally successful install onto Ubuntu Natty if you exclude the graphical problems. When we tried to replicate the install onto my wifes netbook we came upon this error. Everything was the same except that our server runs Intel 64 and the netbook is on AMD 64. Well thanks to this this forum post we were able to fix our issue by installing
ia32-libs via apt-get. Easiest way to check your CPU is sysinfo again grabbed via