head	1.3;
access;
symbols;
locks
	ids:1.3; strict;
comment	@# @;


1.3
date	2001.10.05.19.24.57;	author ids;	state Exp;
branches;
next	1.2;

1.2
date	2000.10.15.17.44.59;	author ids;	state Exp;
branches;
next	1.1;

1.1
date	99.04.27.18.07.16;	author ids;	state Exp;
branches;
next	;


desc
@@


1.3
log
@wow! these new PCs we've got *are* fast!
So: further keeping up with Moore's law.
@
text
@0.01	1	100000	(MAX_REL_DISP, PLOT_HOW_OFTEN, PRINT_HOW_OFTEN)

Sun_1		2e30	-1.5e11 3e10 4e10	-761 -11232 -671	comments
Sun_2		2.5e30	+1.5e11 -2e10 1.1e10	+345 +18762 375

Sun_3		3e30	-1.5e12 1e11 2e11	0 -15000 -20000
Sun_4		1.5e30	-1.8e12 1e11 2e11	0 +15000 -20000


other_1		2e30	9.85e12 13e10 4e10	-100761 -11232 -671	comments
other_2		2.5e30	10.15e12 8e10 1.1e10	-99655 +18762 375

other_3		3e30	8.5e12 2e11 2e11	-100000 -15000 -20000
other_4		1.5e30	8.2e12 2e11 2e11	-100000 +15000 -20000
@


1.2
log
@changed to keep up with Moore's law!
(The gravity program runs at least 10 times as fast as it did back in 1993.
 So, to at least partly compensate, we print 10 times less often,
 avoiding an avalanche of trace outputs; and since a typical run will go
 much further into the simulated future - for any equal amount of human
 patience! - than before, we turn down the maximum relative displacement
 tolerated, thus keeping the accuracy good over such a long haul.)
@
text
@d1 1
a1 1
0.02	1	10000	(MAX_REL_DISP, PLOT_HOW_OFTEN, PRINT_HOW_OFTEN)
@


1.1
log
@Initial revision
@
text
@d1 1
a1 1
0.03	1	1000	(MAX_REL_DISP, PLOT_HOW_OFTEN, PRINT_HOW_OFTEN)
@