Updating the version of jAmaSeis on a Raspberry Pi is a pretty straight forward exercise. jAmaSeis will perform a check from time to time, when a new version is available a pop up window will appear detailing the new version.
Upgrading is not necessary for uploading you stations image to the University but it is a good practice to keep the software up-to-date. If you are sharing your data with IRIS you will need to upgrade your software.
To update visit the IRIS website, http://www.iris.edu/hq/jamaseis/ from the Raspberry Pi using the Web Browser. Download the Linux jAmaSeis_x_x_x_x.sh to your Downloads directory.
Make sure to close jAmaSeis before updating. You will need to open a Terminal prompt and make the script executable. It’s important to run the script with the sudo command, this will upgrade the currently installed version of jAmaSeis.
Commands to run, replace jAmaSeis_x_x_x_x.sh with your downloaded version. You can use tab completion to fill in the filename by typing jA then pressing the tab key. The shell will fill out the rest for you.
cd Downloads
ls
chmod +x jAmaSeis_x_x_x_x.sh
sudo ./jAmaSeis_x_x_x_x.sh
Enter the seismometeruser password to start the installer
Follow the installer prompts to complete the upgrade.
Released August 2014, this upgrade is to be installed on the machines connected to the seismometers.
If your version of jAmaseis needs updating, you will see an alert titled “Incompatible Version“. The text below the title will say something about needing to upgrade to version 1.0.2.x to be compatible with the IRIS data collection server. This incompatibility does not affect our ability to upload the screen grabs -just the way in which the instrumentation data is pushed to IRIS -given we are not yet doing this in any concerted fashion, this update is not essential.
The following is a recording of the process:
Step by Step
Quit jAmaseis and log out
Log in using the Seismometer Admin[istrator] account.
Open a finder window, and browse to the data hard drive.
Open this, then open the data folder, then open Shared
You should see a file labelled jAmaseis1020_install.app.zip
Copy this to the desktop.
Double click to unzip the file.
Double click on the extracted application jAmaseis_install[.app]
You should be able to click through the various dialogues without changing anything, but double check the settings if you like -the application needs to be installed in the Applications folder on the system drive (this will normally be named nzseis-XXX).
Once finished, check that the “Prevent Appnap” setting is checked, and restart the computer.
This should eventually bring the jAmaseis application back in the Seismometer User account -the new version should be up and running!
In the video above, I check the “Prevent Appnap” settings -but it looks as though the upgrade does not affect this.
Our TC-1 came as a kitand was very easy to complete
Location
There are a couple of ways of getting good location information suitable for configuring jAmaseis. The software needs a longitude, latitude and altitude value. Where these are accurately known on a number of stations, it is easier to calculate good magnitude and depth values for events observed on multiple stations.
How accurate should it be? At the latitude of the example discussed in this article, each degree East or West is ~90km (at the equator, a degree is ~111km), so the 4 decimal places used below suggests an accuracy of ~0.010m for longitude. Latitude is similar.
iPhone (or similar)
Assuming you are close to or on the point where the TC-1 will be deployed, your GPS enabled phone/pad/computer can give you suitable coordinates.
The compass provides longitude and latitude
jAmaseis wants decimal values for longitude and latitude, so you need to do a bit of maths. Latitude is how far up (+) or down (-) you are on the arc joining the North pole (90ºN or 90º) to the South pole (90ºS or -90º) running though your location. In the example above, my latitude is 36º51’8”S (degrees, minutes, seconds South), which can be converted to
36 + 51/60 + 8/(60*60) x -1≈ -35.8522
(the -1 is due to the S)
Longitude is how far East (+) or West (-) around the Earth you are on a circle parallel to the equator (where all points on the circle share the same latitude) where 0 is the intersection of the arc running between the North and South poles intersecting the Royal Observatory at Greenwich. In the example above, my longitude is 174º46’7”E (degrees, minutes, seconds East), which can be converted to
174 + 46/60 + 7/(60 x 60) ≈ 174.7686
Google Maps
If you know here your seismometer is, then you can use Google maps. Centre the map above your target location and copy the longitude and latitude from address bar.
If your machine has the capability, Google Maps can use location services to centre the map.
A Google Maps like interface allows you to locate and find an altitude!
jAmaseis
When you plug your seismometer in, your computer may ask about a new network or communications device -ignore it (close it, whatever)
The port you use is important -if you change it, you may need to reconfigure the source (so jAmaseis can find it again). On the Macs we are deploying, we will typically use the USB port closest to the power socket. The TC-1 needs power, so it is best not to use one of the ports on a keyboard (if you have such a keyboard).
Assuming jAmaseis is already installed, you can run the Source configuration wizard from the File menu.
next…Choose the appropriate seismometer type and modelChoose the device…Fill in the details
Sort out your location (see above)
Fill in the longitude and latitude … Next …Untick for nowditto -we will put this back laterNot right now thanks…Up to you, but these can be confusing when you’re setting up…I did not have data from another machine, so stepped past this -use at your discretionDone!
Screen shots
Let’s change the FTP target … The settings dialogue accessed through the file menu, offers places to configure this.
Configure upload settings, etc
To switch upload back on, select Manage sources from the File menu.
Manage sourcesAutomatically send screenshots to FTP serverUp and running…
