SAC Developers

A forum for SAC developers to exchange ideas about SAC enhancements, bug fixes, etc.

Email address
sac-dev@lists.ds.iris.edu
Type
Subscribers
154
Moderated by
IRIS Webmaster
Related tags
None
Login to manage your subscriptions
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June (2)
May
April
March
February
January
December
November
October (3)
September
August
July (1)
June
May
April
March
February
January
December (1)
November
October
September
August
July
June
May
April (2)
March
February (1)
January (2)
December
November (1)
October
September (2)
August (1)
July
June (11)
May
April
March
February
January
December
November
October
September
August
July
June
May
April (1)
March
February
January
December
November
October
September
August (2)
July
June
May (1)
April (1)
March (1)
February
January
December
November (1)
October (25)
September (33)
August (12)
July
June (1)
May
April
March
February
January (7)
December
November
October
September
August
July
June (2)
May
April
March (2)
February (5)
January

Active Message Threads for September 2008

Kuang He
2008-09-18 22:58:53
Hi, I've developed a patch for the readline/libedit related codes. It includes the following: - Fix: SAC with readline cannot read commands from STDIN (sac < macro_file) - Fix: for SAC compiled with either libedit or readline, when reading commands from STDIN, the command history gets truncated when SAC exits - When not using interactive mode (sac < macro_file), do not show the copyright information. (This is my idea, following the practice of some other popular software packages such as `... [more]
No replies
Kuang He
2008-09-14 10:41:41 - 2008-09-17 05:52:31
Hi all, Attached is a patch (against v101.2) to make SAC use a pager specified by environment variable $PAGER, instead of the current home-grown tool similar to ``more'', to show the help files. The good thing is that in this way, people get to use their favorite pager when viewing the help files. I personally use ``less'', and its biggest advantage over ``more'' is that it can support scrolling backwards using hotkeys like Up Arrow, PageDown, Ctrl+U, k, etc. Plus, I get to scroll either way... [more]
Replies
Kuang He
2008-09-17 03:48:35
Hi all, Eric S. Raymond says in the chapter "Best Practices for Working with Open-Source Developers" of his book The Art of Unix Programming: Choose a coding standard. The debate over the choice of standard can go on forever—regardless, it is too difficult and expensive to maintain software built using multiple coding standards, and so some common style must be chosen. Enforce your coding standard ruthlessly, as consistency and cleanliness of the code are of the highest priority; the detail... [more]
No replies
Kuang He
2008-09-14 08:16:45
Hi, I've attached a patch which has some code refactoring I've done recently. The affected files are: src/bot/crname.c src/co/zbasename.c src/co/zinquire.c src/co/zopen.c src/co/zopens.c I've mainly updated the comments in those files to doxygen style, following Brian's practice. Some useless goto statements are deleted as I go along. I've been extremely careful, and tested the code to make sure that no functionality is changed during the refactoring. Best re... [more]
No replies
Brian Savage
2008-09-12 18:21:48
Attachments: (1) - testsuite.patch (2) - inctim.patch At the prodding of Kuang He, an initial testing suite has been developed for SAC; see attachment, patch against v101.2. The patch includes the infrastructure to test the individual subroutines within SAC to guarantee changes made to the code do not begin to break things. We envision the use by developers and possibly users who wish to compile SAC on their own systems. After installing the patch do the normal % ./configure... [more]
No replies
Kuang He
2008-09-12 09:31:50 - 2008-09-12 18:05:14
Hi all, Actually, this is something related to sac-help mailing list, but since it is a development issue, I thought it should be more appropriate to post it here. In a lot of SAC documents, such as README, doc/README, configure --help, any help pages, etc. you can see words like this: If you experience problems at any stage please report the issue to sac-help@iris.washington.edu However, nowadays one has to subscribe to that mailing list first in order to be able to send an email to ... [more]
Replies
Kuang He
2008-09-11 00:31:25 - 2008-09-12 04:37:34
Hi all, BUG: When a user accidentally closes the plotting window, SAC will crash. $ sac SEISMIC ANALYSIS CODE [09/04/2008 (Version 101.2)] Copyright 1995 Regents of the University of California SAC> fg seis SAC> p [ ... closing plotting window ... ] SAC> Seismic Analysis Code (SAC): Fatal IO Error 11 (Resource temporarily unavailable) on the X server Attached please find a patch for SAC 101.2 (provided by George Helffrich and adapted a little by me) to prevent this by disabling the "X" ... [more]
Kuang He
2008-09-10 04:12:53
Hi, The string sachistory below is overrun by 1 byte. diff --git a/src/co/select.c b/src/co/select.c index 580db77..578360b 100644 --- a/src/co/select.c +++ b/src/co/select.c @@ -162,10 +162,11 @@ sac_history_file_set(char *name) { /* Null name signifies default */ home = getenv("HOME"); if(home) { - len = strlen(home) + strlen(SAC_HISTORY_FILE) + 1; + /* "+ 2": characters '/' and '\0' */ + len = strlen(home) + strlen(SAC_HISTORY_FILE) + 2; sachistory = ... [more]
No replies
Hi all, I just got the source code of SAC 101.2 today, and found that if it is configured with readline (), the compile process would halt at the step of compiling src/co/zgpmsg.c (and later src/co/zgtmsg.c). The error message is: $ ./configure --enable-readline $ make .... gcc -DHAVE_CONFIG_H -I. -I. -I../inc -I../inc -c -o co/zgpmsg.o co/zgpmsg.c In file included from /usr/include/readline/chardefs.h:26, from /usr/include/readline/keymaps.h:36, fr... [more]
No replies
Kuang He
2008-09-06 09:06:16 - 2008-09-08 17:40:39
Hi, I'm using SAC v101.1 on a linux box (Ubuntu 8.04), and the glibc version is 2.7 (2.7-10ubuntu3, to be exact). $ uname -a Linux ....... 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux Bug 1: Trying to use Ctrl+D to quit SAC instead of using the command `quit' will always cause a segmentation fault. $ sac SAC> [Press CTRL+D] Segmentation fault Bug 2: Putting a space after the comma in something like "&1,DIST" will _sometimes_ cause SAC to suddenly abort, with a mes... [more]
Replies
Kuang He
2008-09-06 09:43:33 - 2008-09-07 23:47:00
Dear SAC users and devs, There is a useful feature in softwares like bash, which can save command history to a disk file and load it the next time they run. In this way, people can use hotkeys like Up Arrow, Down Arrow, Alt+P, Alt+N, etc. to access the commands they've used not only in the current session but also in the previous sessions. I hope that SAC can have the same feature so as to make our lives a bit easier. The feature should not be difficult to implement, and if people (hopefull... [more]
Dear Brian, Probably folks here have much more experience on building testing suites than I do, but since you ask, I'll share my two cents. If I understand you correctly, the idea of the macro approach you mentioned is to create something using Expect (http://expect.nist.gov/) to interact with SAC as if a human being is operating on it, or more simply just to write shell scripts to feed commands to SAC using *nix pipes. This is obviously doable, but I agree with you that it does not offer a... [more]
No replies
Kuang He
2008-08-28 19:48:14 - 2008-09-03 22:11:08
Hi there, I met this "WARNING: Number 4003 integer too large" when I tried to multiply my data by a factor of 10^9, and found in the changelog that it is a known bug. I took a look at the corresponding code snippet in src/ucf/cnvati.c starting from L163: /* - Build integer from the stored digits. */ ifac = 1; *intgr = 0; for( j2 = j1; j2 >= 1; j2-- ){ /* -- Warning.. Approaching maximum integer size. * - Use a fudge factor of... [more]
Kuang He
2008-08-31 04:33:29 - 2008-09-01 02:07:21
Hi, I found a problem with sacswap. Although nowadays with sac's ability to read both big- and little-endian sac files, sacswap must be less often used, some people I know are still using it since some of the legacy software such as pssac [3] can only deal with big-endian sac files. PROBLEM: I used sacswap on my linux system to convert a random sac file vel.sac (little-endian) to vel.sac.swap (big-endian), and then from vel.sac.swap (big-endian) to vel.sac.swap.swap (little-endian). By doi... [more]
Replies
Page built 01:35:20 | v.6a0a3e16