A forum for SAC developers to exchange ideas about SAC enhancements, bug fixes, etc.
This list has moved to https://groups.google.com/a/earthscope.org/g/sac-community.
- Email address
- sac-dev@lists.ds.iris.edu
- Type
-
Announcement
Announcement lists are for sending a one-way message to a wide audience. Anyone can post a message — only subscribe if you want to start receiving this type of announcement.
- Subscribers
- 178
- Moderated by
- IRIS Webmaster
- Related tags
- None
October
September
August
July
June
May
April
March
February
January
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
November
October
September
August
July
June
May
April
March
February
January
December
November (1)
October
September
August (1)
July (1)
June (6)
May
April (1)
March
February
January (1)
November (1)
October
September
August (1)
July (1)
June (6)
May
April (1)
March
February
January (1)
December (1)
November
October
September
August
July
June
May
April (2)
March
February (1)
January (2)
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
November (1)
October
September (2)
August (1)
July
June (11)
May
April
March
February
January
December
November
October
September
August (2)
July
June
May (1)
April (1)
March (1)
February
January
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)
November (1)
October (25)
September (33)
August (12)
July
June (1)
May
April
March
February
January (7)
December
November (4)
October (1)
September (2)
August (1)
July (1)
June
May (1)
April
March (3)
February
January (1)
November (4)
October (1)
September (2)
August (1)
July (1)
June
May (1)
April
March (3)
February
January (1)
Active Message Threads for September 2008
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 ``b…
[more]
No replies
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
b…
[more]
Replies
-
Re: Use a pager to show the help files - Brian Savage - 2008-09-14 19:04:13
-
Re: Use a pager to show the help files - Kuang He - 2008-09-14 19:32:50
-
Re: Use a pager to show the help files - Brian Savage - 2008-09-14 20:00:15
-
Re: Use a pager to show the help files - Kuang He - 2008-09-16 10:42:38
-
Re: Use a pager to show the help files - Brian Savage - 2008-09-16 19:13:53
-
Re: Use a pager to show the help files - Kuang He - 2008-09-17 00:22:38
-
Re: Use a pager to show the help files - Kuang He - 2008-09-17 05:52:31
-
-
-
-
-
-
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 details …
[more]
No replies
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 rega…
[more]
No replies
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
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 it…
[more]
Replies
-
Re: Mailing list problem - George Helffrich - 2008-09-12 16:03:06
-
Re: Mailing list problem - James Wookey - 2008-09-12 14:53:03
-
Re: Mailing list problem - Arthur Snoke - 2008-09-12 18:05:14
-
-
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" (c…
[more]
Replies
-
Re: Patch to prevent an accidental close of the plotting window - Brian Savage - 2008-09-12 00:49:47
-
Re: Patch to prevent an accidental close of the plotting window - Kuang He - 2008-09-12 02:16:21
-
Re: Patch to prevent an accidental close of the plotting window - Brian Savage - 2008-09-12 04:37:34
-
-
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 = (c…
[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,
from…
[more]
No replies
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 messa…
[more]
Replies
-
Re: Bugs found - Kuang He - 2008-09-06 09:22:34
-
Re: Bugs found - Kuang He - 2008-09-08 06:34:03
-
Re: Bugs found - Kuang He - 2008-09-08 09:17:41
-
Re: Bugs found - Brian Savage - 2008-09-08 17:40:39
-
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
(hopefully …
[more]
Replies
-
Re: Feature proposal -- saving command history to a disk file for later use - Brian Savage - 2008-09-07 23:47:00
Kuang He
2008-09-04 03:38:20
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 f…
[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 1…
[more]
Replies
-
Re: A possible way to fix "WARNING: Number 4003 integer too large" - Brian Savage - 2008-08-28 20:01:12
-
Re: A possible way to fix "WARNING: Number 4003 integer too large" - Kuang He - 2008-09-03 21:11:54
-
Re: A possible way to fix "WARNING: Number 4003 integer too large" - Brian Savage - 2008-09-03 22:11:08
-
-
-
Re: A possible way to fix "WARNING: Number 4003 integer too large" - Arthur Snoke - 2008-08-29 20:52:35
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
doing…
[more]
Replies
-
Re: sacswap's byte swapping bug - George Helffrich - 2008-08-31 20:06:23
-
Re: sacswap's byte swapping bug - Kuang He - 2008-08-31 17:45:21
-
Re: sacswap's byte swapping bug - George Helffrich - 2008-08-31 23:56:03
-
Re: sacswap's byte swapping bug - Kuang He - 2008-08-31 20:41:24
-
Re: sacswap's byte swapping bug - George Helffrich - 2008-09-01 02:07:21
-
Re: sacswap's byte swapping bug - Kuang He - 2008-08-31 21:25:26
-
-
-
-
-