JWEED Manual

Basic operation

When first invoked JWEED presents a screen with a scrolling list of servers. The servers are grouped by organization and within this grouping, by type. There are three types of servers, seismogram, event, and network/station metadata servers.

[ view video ]

Here is an example "walk through":

Select the IRIS_DataCenter seismogram server from the list. Both of the NetworkDC and EventDC servers should be highlighted. If not. select them.

Click on the Select Events tab.

You can enter a variety of event parameters on which to base your query. Query for all (within the default time parameter) by clicking the Query DHI button.

[In the example below, the user set a parameter of 4.0 and greater magnitudes for events from the QED catalog].

Selecting a catalog such as QED or NEICALRT will avoid duplication.

For more information about IRIS catalogs please refer to: Event Catalogs

This will fetch all events from the DHI event server within the time range specified. You can now map these events by clicking on the

"Map Events" button.  The events are indicated by the yellow dots. Passing the mouse over each dot will reveal the event's information.

Similarly fetch all networks by going to the Select Networks tab and selecting the Query DHI button. You can specify networks, stations, location codes or channels. You should see a listing of network/stations on the right part of the screen. Click on the triangles to expand or contract the listing. You can select individual networks or stations. Clicking on a station will result in the station's information to be printed out. Be aware that if you leave a station or network "selected", all subsequent processing will work on those selections. For instance, if you click on station ANMO to read the station information, clicking on "Map Stations" will result in only ANMO being mapped.

Since you now have some events and stations on the map, the next step is to generate a request. Clicking on the Generate Request tab will present a screen which allows you to specify start and stop times of waveforms at the selected stations arriving from the selected events. This is accomplished by selecting a starting phase and an ending phase arrival. The calculated time of the starting phase and the ending phase, along with a bias before (-) or after (+) the calculated arrival, define the data collection window.

Once you have the starting and ending phase arrivals indicated you then need to generate a request file, called a Summary File. Once you click on the Generate Summary File button you will be asked for a file name. [See the Generate Request section for a description of the summary file.]

With the summary file created you can either mail in your request (E-mail Request Tab) or initiate the download process by clicking on the DHI Seismogram Servers tab.

Here is the screen for emailing the request:

Your newly made summary file will be highlighted (selected).  Enter a name, email address, phone number and a SEED label. The SEED label you enter will be used by IRIS to identify this request. Use the default data center selection of netdc@fdsn.org. There are two types of email request, a Net DC or a breq_fast request.  To select one or the other, click on the menus and select a data center, the email is printed out. For now just accept the NetDC's netdc@fdsn.org.

When you click on "Mail it" the program will print out mailer messages as it mails them. You will receive notices via email from the data center about your request status and when and how you can pick it up.  The finished file will be in SEED format which you will have to "ftp".

You can save the request to disk in a text file.

Once you have a summary file selected you can send it to the data center via the "Online System"'s "Retrieve Seismograms" button.  You can probably ignore the "Archival System" as almost all data can be obtained from the the "Online Systems". More on that later, for now just use the "Online System"s "Retrieve Seismograms" button.

You will see messages appear indicating the success or failure of the retrieval process. It may happen that there is no data for a particular event for the stations requested. A running total of number of seismograms is printed.

At this point each event's waveforms are listed by event in the scrolling list. You can select event individually or as a group for further processing.

Further processing includes viewing or saving to disk. If you wish to view the waveforms, each event's waveforms will appear in their own screen.

If you wish to save to disk each event's waveforms are saved in a directory based on the waveform server's name and under that, the event name.

Here is an example viewing:

 When saving the waveforms to SAC, or when viewing sorted by distance, JWEED needs to extract from a network server the lat/lon position of the stations and/or the sensitivity of the instrument. You therefore must have selected a Network server from the servers list, or these buttons remain green (inactive).

This concludes the quick run-through.

Map Screen

Along the bottom of the map screen is the control panel. It is divided into 3 functional areas, "Map a Distance", "Great Circles and MidPoints" and "Azimuth". [ view video ]

Using the Map Screen:

There are two basic ways to use the map.

1: You can define areas and then query for events and stations which lie in these areas. Here you use the map first then you use the "Events" tab or the "Stations" tab.

2: After downloading events and stations, you can use the map screen to draw an area and plot event and stations whose mid-points lie in this area. You can also plot stations and events using azimuth/back azimuth values. Here you first download events and stations, then you use the map for further processing.

Drawing lat/lon boxes:

The map screen allows the user to specify lat/lon boxes which can then be used to query for events and/or stations. The default drawing mode of the map is lat/lon boxes. Simply move the mouse pointer onto the map and click and drag, releasing when you've defined the area to your satisfaction. After you have an area defined, when you query for events via the "Events" tab or stations via the "Stations" tab your query will be limited to those areas.

Map a Distance:

You can define angular distances from plotted events, stations or user defined point(s). This is useful if you wish to find all stations within a distance from events, all events within a distance from stations, or all events and or stations from a user enter point on the globe.

 

Finding all stations within a distance from events:

To draw distances from events first download some events with the "Select Events" screen. Map these points using the "Select Events" screen's "Map Events" button. This will also take you to the map with the events displayed. Since there are events plotted you can define a distance from each one. Simply enter in a minimum and a maximum value and press the "Map a Distance from Events" button. You will see circles around each event which represents the angular distance from each event.

 

With these distances you can then query for stations which lie within these distances.

Finding all events within a distance from stations:

Similarly you can find all events within a distance from stations. Download and plot stations. Define a min/max distance. Plot the distance from each station using the "Map Distance from Stations" button. Then query for events.

Find all events and/or stations from a point on the globe:

Again you can find all events and or stations from any point on the globe. By clicking on the "More Tools" button a new popup window will be displayed. From this window's Map Mode pane you can select the crosshair icon which will allow you to click on the map and define any number of points. Once you've done this you can draw distances from these points. Then querying for stations and/or events will limit the search to these areas.

 

Great Circles and Midpoints:

Plot Mid-Points:

 

This feature allows the user to limit their request to just those stations and events whose midpoints lie within a user defined lat/lon box.

 

To plot mid-points you first download events to the "Select Events" screen and some stations into the "Select Stations" screen. Do not plot them, just download them. Move to the map screen. Draw a lat/lon box on the map by clicking and dragging the cursor. In this manner you indicate an area on the map from which you want mid-points calculated. When you press the "Plot Mid-points"  button, only those events and stations which have mid-points of their great circle routes passing through this area will be plotted.

 

Here is the map after mid points have been plotted. Only those stations (red) and events (yellow) which have mid-points in the lat/lon box are mapped. They can be further processed into a request. Notice there is a small lat/lon box drawn (in black) which is used to find mid-points.

 

Plot GC Paths:

 

As in plotting mid-points, to plot great circles you first download events to the "Select Events" screen and some stations into the "Select Stations" screen. Do not plot them, just download them. Move to the map screen. Pressing "Plot GC Paths" will draw all great circle routes from all events to all stations.

 

Plot GC which X region:

 

The same as "Plot Mid-Points" except that all great circles which travel through a lat/lon box will be drawn, irregardless of whether their midpoints lie within this area.

Azimuth:

As in the above functions, download events and stations first. Enter azimuths or back azimuths and press apply. Only those events and stations with matching azimuths and back azimuths.will be plotted.

Clear Map, Reset Map, Zoom In, Zoom Out:

Clear Map does just that. All user entered plots will be erased.

Reset Map will bring map to original size if zoomed and then clear the map.

Zoom In functions in two ways.

1: If you have defined one and only one area (lat/lon box), then pressing the "Zoom In" button will use this defined area and expand it to fit the window.

2: If no regions are defined, or more than one, then the current map is zoomed in.

Zoom out bring back the previous map before zooming in.

More Tools:

Pressing the "More Tools" button will bring up a small screen which will allow more functionality.

 

 

Map Mode:

There are 5 map modes. Here they are in order from left to right.

1: Box drawing (default). By clicking and dragging the user can define a rectangle.  When querying for stations and/or events you can limit the search to these areas. You can make as many rectangles as you want.

 

2: Map Point.  The user can use this to define an arbitrary point on the map. From this distances can be drawn for querying events or stations.

 

3: Pointer. This is used to select individual events or stations mapped. If you have 100 events mapped and you pick on one using this pointer, any subsequent processing will only apply to this event, not the 100. This is the same for stations. You can select any user entered edits, such as lat/lon boxes, shapes, distance circles, the exception being the great circle paths.  When you select an object the color changes indicating the selection. Click again to deselect. For area objects, lat/lon boxes, distance circles or shapes, clicking anywhere in the object selects or deselects.

 

4: Drawing tool: this tool is used to draw an arbitrary shape on the map. Querying for events or stations will be limited to this shape.

 

5: Great Circle drawing tool.  You can  plot great circle routes by clicking and dragging. After releasing a great circle route will be drawn between the starting click and the release point.

Lat/Lon Box and Define a Point:

You can enter floating point coordinates for lat/lon box boundaries and a user defined point. This allow for greater accuracy than is attainable using the mouse pointer.

 

Select Events Screen

[ view video ]

Starting/Ending Dates: Enter a starting and ending date for the event query. The default is today's date for the ending date and 30 days previous to this as the starting date. You can click on the up and down triangles to scroll the dates up or down.

 

Catalogs: These catalogs are retrieved from the event server at program startup. There is no default catalog. It is likely that you will get duplicate events unless you specify a catalog. For the IRIS Event server the most useful catalogs might be the QED or the NEICALRT. Using these might result in the least duplication of events. The FINGER catalog is the most current. It takes about a week for an event to get into the QED. If you don't specify a catalog and query for events you might end up with a lot of duplication.

For more information on IRIS catalogs refer to: Event Catalogs.

 

Magnitude Parameters: Enter a magnitude minimum and maximum. You can enter a floating-point number for magnitudes and depth.

 

Query DHI: This will query the IRIS DMC's event server. A listing will appear matching the parameters as entered above and which fall into any boxes, distance circles or shapes as entered on the map.

 

Apply Local: After you have an event listing, you can further exclude events by altering the event parameters and clicking this button. For instance, if you loaded event from a previously saved file, you could then modify the minimum magnitude value and after clicking this button this list will be updated.

Eliminating duplicate events by selecting a catalog and then clicking on this button is another useful function. JWEED will not re-query from the DHI but rather use the local set.

 

Map Events: After retrieving some events you can map all the listed events or selected subset. Events appear on the map as yellow circles.

 

Save Events to File: After downloading a set of events, the user may want to  save this set for further use. This option allows the user to save the events to disk as a text file. A popup window will appear listing previously saved event files and directories. It also allows for file naming and also navigation between directories. File names entered will have a suffix of ".events" appended to it when writing to disk.

 

Load Events from File: A popup window will appear with event files and directories listed. It allows for navigation between directories. After choosing a file, a listing of events in this file will appear in the main screen's listing. Note that the time, magnitude, depth parameters as well as any map defined areas are ignored when loading a file as it is

assumed that the events that are in the file are what you want. The time range is altered to reflect the earliest and latest event times however.

 

Event listing: The events are listed in a selectable list. You can select one, multiple or none (meaning all). How you make a selection varies with the operating system.

• Sun/Linux/Windows computers: <control><left mouse btn> to select multiple.
• Mac computers: <Apple><mouse btn> to select multiple
• To deselect, use the same sequence

Select Stations Screen

[ view video ]

Starting/ending dates: Enter a start/end date for the network query. By default it uses the date as entered in the Select Event Screen. If you modify the start/end date range, this change is reflected back to the Event screen's start/end date range.

 

Select Channels/Locations: You can limit queries to specific networks, stations, locations, or channels.

 

Query DHI: You can query the DHI server for stations meeting the user entered parameters. A tree-structured listing should appear to the right of the screen. In the listing are networks and stations which have met your criteria. If you click on the grey triangles the listing will expand. For instance, clicking on the triangle adjacent to the IRIS_NetworkDC will reveal all networks for the network data center. Similarly clicking on each network's triangle will reveal the network's stations. Clicking on the station name will result in this station's information to be printed in the Station  Detail/Messages area.

 

Be aware that clicking on a network name or station will select this item for exclusive processing such as mapping or request generation.

 

You can select one, multiple or none (meaning all). How you make a selection varies with the operating system.

• Sun/Linux/Windows computers: <control><left mouse btn> to select multiple.
• Mac computers: <Apple><mouse btn> to select multiple
• Deselect using the same sequence.

 

From this listing you can select one or many or none (meaning all) for further mapping and/or processing.

 

Map Stations: By clicking this button the stations will be placed on the map. Stations are represented by red triangles. If you have selected individual networks or stations, only these will be mapped.

 

Save Stations to File: You can save the listed stations to a local text file. A popup window will appear with station files and directories listed. It allows for navigation between directories as well as file naming. File names entered will have a suffix of ".stations" appended to it when writing to disk.

 

Load Stations from File: You can load stations from a previously saved file. Note that the user entered parameters will not be active as it is assumed that the previously saved stations are wanted regardless of the time range or network/station/location/channels the user may have entered or any map areas. The time range is NOT modified to match the station files. In this regard, this screen is different from the Event screen's Load Events from File button.   A popup window will appear with station files and directories listed. It allows for navigation between directories. When you see the file you want click on the "Open" button. Networks and stations will be listed in the area Network Data Centers area in the upper right of the screen.

 

Clear Detail: This clears the station information area.

 

Generate Request Screen

[ view video ]

Time Window Parameters: The Generate Request Screen is used to specify a starting/ending time window for waveform extraction. To accomplish this you specify a Phase arrival of interest for the start of waveform extraction and for the end of waveform extraction.

 

There are entries for supplying a bias in seconds. Negative biases will be subtracted from the calculated arrivals. To enter surface wave parameters, select "Surface Wave" (at bottom of listing) from either the starting or ending arrival.

 

Surface Wave calculations: Enter the Km/sec. Enter an Arrival distance. There two ways to calculate arrivals between events and stations. You can go the short way, or around the globe the other direction. If you enter an odd arrival index, JWEED calculates using the short route. Entering a one would calculate the arrival time from the event to the recording station directly. Enter a 3 and it goes once around the globe first. And so forth. Entering a 2 will calculate the distance going the long way around the globe. Enter a 4 and it will do this twice. And so forth.

 

Use Map / Listing for events/stations buttons: To generate a request you specify whether to use station/events from the map or the originating screen listing (the Select Events and Networks Screen). Most people will probably use the events/stations as mapped, but this is not a requirement. If you have events listed in the Event screen and stations downloaded in the Stations screen, click on the "Use listing for events/stations" button. If you have mapped some events using the Map screen's Mid-points, Great Circle or Azimuth tools you will need to use the "Use Map for events/stations" button.

 

Generate Summary File: When you click on this button JWEED will calculate the start/stop times and construct a summary file. Each event processed is appended onto the listing.

 

A summary file is a text file used by JWEED as an intermediary format. JWEED will use the summary file to convert to BREQ_FAST /Net DC type request formats or the DHI server supported formats.

 

Being a text file, a summary file is easily viewable. Looking inside you will see each event listed. Underneath each event are the stations for which JWEED was able to calculate arrivals. Underneath this is a listing detailing the phase arrival time calculations. If you email the request to IRIS and thus obtain a seed volume, you can use this summary file in conjunction with rdseed for a more finely tuned data extraction. See the rdseed manual for more information, http://www.iris.edu/manuals/rdseed.htm.

 

Map Request: This will draw connecting lines from stations to events for those stations which JWEED was able to compute an arrival.

 

If you have many events and stations in the same vicinity you might have better results if you pick individual events for mapping. You can select individual events for mapping by clicking on the event name in the listing.

Email Request Screen

[ view video ]

After a summary file is generated you can use this screen to obtain a seed volume.  You email a request to IRIS using the BREQ_FAST mode or the NET_DC mode. Either way the end result is a seed volume. You will be notified when your seed volume is ready. Pickup is by ftp.

 

You select a summary file; enter your name, email address, phone number, optional media types, and a seed label.

 

There are two types of requests possible, a NetDC and a breq_fast request. The most usual are a NetDC request using the fdsn address or a breq_fast using the iris address.You can move between the two by clicking on the appropriate buttons.

 

The two request types, NetDC and breq_fast are nearly identical except that a NetDC request will be forwarded through a network of data centers which support the request mechanism. A breq_fast request only goes to the institution listed.

 

For more information regarding NetDC, go to the IRIS webpage at http://www.iris.edu/manuals/netdc/netdc_user.htm.

 

For more information regarding the breq_fast request type, go to the IRIS webpage at http:www.iris.edu/manuals/acrobat/T_brqfst.pdf or http://www.iris.edu/manuals/breq_fast.htm.

 

After emailing you will see some mailer messages appear in the listing. The last line should read: "Message accepted for delivery".

 

If you wish to keep a hard-copy version, click on the "Save to disk" button.

 

DHI Seismogram Screen

[ view video ]

The DHI Seismogram Servers screen is divided into three sections, the "Request Items", "Messages" and "Waveforms" sections.

 

Request Items:

 

Server types: There are two server types, online retrieval systems and the archive retrieval systems. As of this release (v3.0, Jan 2008), IRIS is the only institution which has implemented an archival system.

A note about seismogram servers. As of this release this is what is known.

IRIS seismogram servers:

IRIS_DataCenter: This is the server that most people will use as it holds our most complete holdings, from up-to-the-minute all the way back to the beginning of IRIS. This is IRIS' Tier 1 repository. The only data missing from this server is the tier-2 data. Tier 2 data are waveforms which are accessed infrequently or of very large volume. An example is the SAFOD 4khz data and other high sample engineering data. For more information on IRIS' data repositories refer to the IRIS web page at: http://www.iris.edu/news/newsletter/vol9no3/page2.htm and scroll down to the Waveform repositories.

 

Bud Server: The Bud is the real-time streaming system. The Bud holds data from 2 weeks to 6 months. 2 weeks for high-speed networks, 6 months for others. Only a subset of networks from our holdings are in the Bud.

If your request is for events within the last few days you could send it to the Bud as it will be quicker than the IRIS_DataCenter.

 

Pond Server: The Pond is a repository for event-oriented data as listed in the NEIC and other sources; generally events with a magnitude of 5 and above. The Pond holds waveform events starting in 1990. Not all networks from our holdings are in the Pond.

If your request is for major events after 1990, you could send it to the Pond.

 

Archive Server: The Archive is IRIS's main waveform repository. The Archive holds continuous and triggered data that has a latency of two weeks minimum to 6 months maximum.

If your request is for data older than 6 month you can try the Archive.

Berkeley servers:

The Berkeley seismogram server runs two days behind.

Retrieving data using the Online Systems:

Just click the button. Seismograms will be downloaded if they are available.

Retrieving data using the Archive: Requesting seismograms from the Archive is a three-step process, as it processes offline.

1. Queue the request. You will be asked for a name for this request. It sends the request of to be put into a queue. The name for the request is listed in the scroll area in the upper right.
2. Request Status: After selecting a request from the upper right hand scroll area, you can check its status by clicking on the "Request Status" button. If the status is finished you will get a smiley face. If it is not, a frown will appear. Messages to this effect will be printed out in the message area.
3. Retrieving Request from the Archive: Once you have a smiley face you can retrieve the request by clicking this button. Progress messages detailing how many seismograms for each event was retrieved.

Waveform section: As each event's data is retrieved a listing of these events is displayed in the "Seismogram" listing. There may not necessarily data for a particular request.

 

View: You can bring up a new window showing the waveforms for each event by clicking the "View" button. With this view screen you can individually select traces for saving by clicking on their name. The name will be highlighted. You can also clip traces into a smaller segment by moving the pointer over the trace (the pointer will transform into crosshairs). You will notice that the sample time is indicated as you move across the waveform. Click once to start the segment definition then once again to end. When you save the waveform to a file, only those samples lying between the clip marks will be saved.

Be aware that if you view many events, depending on how many stations were reporting, you can run out of memory.

 

Save: You can save waveforms into disk files in either SAC or MINISEED format. The "Save" popup displays the current directory and also there is a text area for creating a new directory. In the middle area is a listing of directories within the current directory. You can navigate by clicking on the ".." to go up or click on a directory name to descend into it.

Once a directory is chosen, JWEED will create a directory under this for each event. JWEED will place all waveforms files for each event in the appropriate directory. These directories are named using the event date and time.

Properties

There is a JWEED properties file which holds several program and user variables. It is located in the JWEED.dir directory under your home directory. It is called weed.props. When you click on the "Properties" button the properties are listed and are available for editing and saving.

Here are the contents of the weed.props file as it arrives from the installation process.

name_server=corbaloc\:iiop\:dmc.iris.washington.edu\:6371/NameService
map_server_basename2=http\://wms.jpl.nasa.gov/wms.cgi?version\=1.1.0... map_server_basename1=http\://www2.demis.nl/wms/wms.ashx?Service\=WMS&WMS\=.. ...

dhi_servers_online=true
map_server_online=true
AboutURL=http://www.iris.edu/manuals/jweed/about.txt
map_color2=yellow
map_color1=black
mailer=iris.washington.edu

 

In addition to these, if you save your information from the "Email request" screen there are 7 more properties added:

media=FTP
user=John Doe
media3=not used
media2=EXA-byte
phone=206 547 0393
email=doe@remi.edu
label=My Seed Label

There is one more optional property. It is the property which holds the file name which contains the passwords and emails used for the restricted access.

restricted.passwords=DHI.passwords

For more information on access to restricted data, see below.

The contents of the property file take on the format of "token=contents". An explanation of each token is given here:

name_server:

JWEED uses this token to locate the IRIS nameserver. This nameserver dispenses location information for all of the IRIS servers.

map_server_basename1, map_server_basename2:

these are where JWEED looks to download map images. In the future more map servers may become available. To add one to JWEED and have it come last in preference you would use the token "map_server_basename3".

map_color1, map_color2:

Different map servers have different color requirements. Some are light and some are dark. JWEED needs to know what color to use when drawing to the map so it can be seen. The map_server_basename1 uses light color, so a dark color (black) is selected for use by JWEED for drawing purposes. You can adjust as necessary.

dhi_servers_online:

There may be the occasional time when you don't want to connect to the DHI servers. Maybe you are offline or there maybe firewall issues, etc. It takes a while for a connection to timeout which can be annoying. You can set this to false and immediately go to work.

map_server_online:

Sometimes both map servers will be offline. JWEED comes with the old static map which can be used in these times. Set the token to false.

aboutURL:

This is the URL for the "Readme" screen.

Here  is the explanation for the optional tokens for use by the "Email request" screen: The first three are required or an email request.

user:

The name of the person making the email request.

email:

The user's email. All messages will be sent to this email.

label:

The label identifies the request. The user should specify a unique name as the email messages received by the user will all reference this label. The resulting SEED volume will be identified by this name.

phone:

The phone number contact for the email requests.

media:

The user's first choice for how to retrieve of the request. Usually ftp.

media2, media3:

The next choices is the preceding ones can't be used.

The most common choices for media are ftp, exabyte 2 and 45 gigabyte, DAT, DLT, DVD.

When the user saves the "Email Request" screen's email header info, these tokens are filled in.

Restricted Access

To obtain access to restricted data you need to create a file which contains the network code, start/stop years, password and email.

 

Here is a file illustrating the structure:

XX 2006 2007 a_password somebody@somewhere.etc
YY 2004 2005 another_password another_somebody@somewhere.etc

You put the file name into the property file, weed.props as explained above. You use the token restricted.passwords Plug in the file name there as in, restricted.passwords=my_password_file. Use the complete path and filename.

Bugs, Caveats and disclaimer

• There is a bug that manifests itself when you have a shape drawn on the map and you then zoom.
• On the Mac the info screen and the main program compete for your attention. You can display the info map on top of the main program window and move the pointing finger over stations/events. You need to move the main screen and the info screen in such a way that you can see the info screen but still drag the pointing finger over the stations/events. The map needs to be the active window for the pointing finger to appear.
• There is no way to delete entries from the Archive Request Name listing. It is a text file from which you can remove lines using an editor.
• JWEED's "Home" directory is where you installed it. On the MAC this might be the applications directory. This is probably not the best place to put JWEED's helper files; summary, archive queue files, etc.
• The Event Screen only uses stations that are on the map. There should be an option to use the stations as found on the Network Screen.
• This is the same for the Network Screen. When checking azimuth/back azimuth the Network Screen uses events as found from the map.

Contact Information

revised: 2008.10.10