Professional Documents
Culture Documents
Handbook
Handbook
|
|
|
|
|
MAXCLOCK 3.2 USER HANDBOOK
|
|
|
|
|
| ( Part 1 of the software documentation for MAXCLOCK 3.2 ) |
|
Copyright (c) 2010 Udo Mark
|
|
|
|
|
|
|
|
Table of Contents:
|
|
|
|
1. GENERAL INFORMATION
|
|
2. USING THE PROGRAM
|
|
3. TROUBLESHOOTING
|
|
4. SOME IDEAS FOR EXPERIMENTS
|
|
5. UPDATE HISTORY
|
|
|
|
|
|---------------------------------------------------------------|
To do this, MAXCLOCK only uses the internal clock of the computer and an
easy-to-edit configuration file.
Computations may also be made for user-supplied date & time (typed through
keyboard or read from file, non-clock mode), and output may also be
directed to a protocol file.
MAXCLOCK.EXE
MAXCLOCK.CFG
MAX_DOS.BAT
MAX_WIN.BAT
ANSI.COM
SAMPLE.DAT
SAMPLE.BAT
SDATE.EXE
README.TXT
32-bit
MAXCLOCK.EXE
MAXCLOCK.CFG
--MAX_WIN.BAT
--SAMPLE.DAT
SAMPLE.BAT
SDATE.EXE
README.TXT
HANDBOOK.TXT
SPECIALS.TXT
11 files
HANDBOOK.TXT
SPECIALS.TXT
9 files
n = control parameter
n = 0
: clock mode, user controlled update.
n = 1...60: clock mode, auto update every n seconds.
n = 77
: non-clock mode, input by keyboard.
n = 88
: non-clock mode, input from file.
cfgfile = full path & name of configuration file (max. 60 character), when
not specified, the file MAXCLOCK.CFG will be searched in the
current directory.
outfile = full path & name of outputfile (max. 60 character), when not
specified, output will be sent to screen.
The normal mode is the fully-automated clock mode. For maximum convenience
and clock-like appearance, it is recommended to select just a few seconds
for the screen update interval "n": Then, every n seconds a new screen of
results will be computed and displayed.
For lowering processor workload, a user controlled update has also been
provided (semi-automated clock mode).
If you do not specify any arguments, title and user information will be
displayed upon starting the program.
If your current directory is not the same as MAXCLOCK's directory, specify
full path and filename of any file you want to use.
Initially, you will perhaps conveniently use the configuration file
MAXCLOCK.CFG which has come with the package.
To increase accuracy and fully exploit the capabilities of the program,
you may later edit MAXCLOCK.CFG with a text editor and build individual
configuration files from it. (See below in chapter "CONFIGURATION FILES".)
As a supplement to this clock mode, you can use MAXCLOCK for occasional
single computations with dates and times of your choice:
This is called the "non-clock mode", and is invoked by typing:
maxclock /77
With this option you may enter date & time through the keyboard, and you
will receive one single screen of results for every date/time entered.
In this non-clock mode, you also may direct the output to an outputfile
(protocol file) by specifying its name in the command line, like for
example:
maxclock /77 maxclock.cfg mytest.out
If you wish to additionally read dates & times from an inputfile, see
below in the section "WORKING WITH INPUTFILES IN THE NON-CLOCK MODE".
CONFIGURATION FILES:
A standard configuration file named MAXCLOCK.CFG has come with the package
and will be used unless you specify another file on the command line. If
you received MAXCLOCK via e-mail, this configuration file usually contains
a rough longitude specification for your location. If you downloaded
MAXCLOCK from its webpage, it contains a longitude specification for
Copernicus' workplace in Fromborg, Poland, just to make an example.
In any case, you may modify the configuration data according to your
personal needs with any text editor on your computer.
Just refer to MAXCLOCK.CFG, it will provide all relevant information.
Beyond, to yield maximum computational accuracy for the given geographic
location, the longitude specification in the configuration file should
follow some rules. A detailed discussion of this topic may be found in the
information file SPECIALS.TXT
Years may range from -9999 to +9999, years BC must carry a symbolic minus
sign (directly preceding it), years AD may carry a plus sign, no year zero
is allowed. (For some other calendrical restrictions, see the chapter on
input values in file SPECIALS.TXT.)
The items must be separated by any one character. (e.g. blank, tab, colon,
etc.) Any such string may be followed by additional text in its line.
Decimal fractions must be written with points (full stops), not with
commas.
This writing of date and time closely conforms to general conventions and
the ISO 8601 / EN 28601 international standards. For an example, see the
file SAMPLE.DAT
Note that DUT1 values (-99 to +99 seconds allowed) in such inputfile will
always override DUT1 value specified in any configuration file.
Also note, that Delta-T values in such inputfile (-999 to +999 hours
allowed) will override program internal ephemeris time model only if this
has been selected in the configuration file. (For details on this, see in
configuration file MAXCLOCK.CFG)
When invoked like:
maxclock /88
program will first ask you for the name of the inputfile, and then you
will receive one single screen of results for every date/time string in
this file.
You may try this with the sample inputfile SAMPLE.DAT, which has come with
the package. In this file, the strings cover the time span 45 BC till
AD 1583 and you will see the situation on every 21st of March.
You may go back and forth through inputfiles by giving appropriate
commands.
For building your own inputfiles, you may conveniently use SAMPLE.DAT as a
specimen.
Date/time strings already given in ISO 8601 / EN 28601 writing in a
textfile can be easily moulded into MAXCLOCK format with any text editor.
Make sure to save inputfiles as ordinary ASCII/ANSI ("text only", "plain
text", or "DOS Text"), without any formatting specific to your text
editor. Also, make sure that the last line (just like any other line) of
such inputfile is properly terminated with a carriage-return character.
You also may direct the output to an outputfile (protocol file) by
specifying its name in the command line, like for example:
maxclock /88 maxclock.cfg mytest.out
--- 3. TROUBLESHOOTING --------------------------------1) MAXCLOCK "hangs up" or occasionally shows wrong time:
When you run MAXCLOCK in the clock mode, you should never use BIOS
options which perform "power management", "power saving", or "green"
functions.
These functions in some cases disable interrupts and hinder MAXCLOCK
from receiving correct time information from the hardware clock.
Consequently, as for your BIOS setup, do NOT allow that interrupts are
ignored, or that components of your computer are switched down for the
sake of power saving (as is very common with laptop or notebook
computers).
2) Clock mode: Screen does not update with new time telegram though
update interval has elapsed:
On older and slower computers, the computations take considerable time.
Make a few computations in the non-clock mode (invoke with "maxclock 77") and observe the time lag information given in the upper right
corner of the screen.
If time lag exceeds 60000 (sixtythousand) milliseconds, the fullyautomated clock mode cannot be used at all on your computer. If it
does not exceed this value, proceed as follows:
1) Suppress acoustic beeps by setting the respective option in the
configuration file to "noBEEP" or "BEEP0".
2) Choose an update interval which is longer than the longest time lag
observed.
3) If you now wish to additionally send acoustic beeps, you will
probably have to increase the update interval by some further
amount.
3) Obscure characters on the screen, screen jammed:
Probably you started MAXCLOCK by *not* using one of the batchscripts MAX_DOS.BAT and MAX_WIN.BAT *and* the ANSI support of your
operating system is not as extensive as one would wish.
Start MAXCLOCK by using the respective batchscript (as described above
in chapter "INSTALLING AND RUNNING") and follow any instructions
issued by that batchscript.
If you started from a self-built desktop icon or a self-built
batchscript, check the settings of these (paths, directories, etc.)
and refer to sample batchscript SAMPLE.BAT.
4) Data are read erroneously from configuration file or from input file:
--- 4. SOME IDEAS FOR EXPERIMENTS --------------------------------------------1) Watch the Sun passing through the thirteen constellations of the
zodiac:
Times and positions considerably differ from what mythologically is
said for the so-called twelve "signs" of the zodiac. (In late
December, for example, the Sun is in the 13th constellation, the
Ophiuchus.)
2) Verify that sidereal days are shorter than solar days:
From one civil midnight to the next, sidereal time will have increased
by more than 24 hours.
3) When aiming your telescope at a celestial object of known right
ascension RA, you can conveniently use the sidereal time shown by
MAXCLOCK to find hour angles:
Start MAXCLOCK in the clock mode and simply find hour angle according
to:
HourAngle = LocalSiderealTime - RAofObject
4) See the consequences of precession:
In the non-clock mode, for example, compute for your birthday, and
then for the same date appr. 2000 years later. Mostly the Sun will be
in another constellation, while still being at approximately the same
longitude and as such in the same mythological "sign".
5) See how seasons begin to shift across the year when there are slight
calendar imperfections accumulating, as was the case in the calendar
introduced by Julius Caesar in 45 BC:
The sample inputfile SAMPLE.DAT gives date/time strings for every 21st
of March, ranging from 45 BC till AD 1583. You may notice an equinox
shift amounting to more than 12 days, until, in the year 1583, the
Gregorian reform brought the equinox back to the point where it had
been observed at appr. AD 300.
(Regarding the usage of inputfiles, see above in the section "WORKING
WITH INPUTFILES IN THE NON-CLOCK MODE".)
6) In the clock mode, watch the moment, when seasons change:
This happens when the Sun reaches apparent longitudes of integer
multiples of 90 degrees.
MAXCLOCK gives announcements one week in advance, so you may observe
the respective event approaching. Alternatively, you may wish to run
MAXCLOCK for a short time interval near the following moments only:
Event:
first equinox 2010 :
first solstice 2010 :
second equinox 2010 :
second solstice 2010:
first equinox 2011 :
first solstice 2011 :
second equinox 2011 :
second solstice 2011:
first equinox 2012 :
Wed.
Sat.
Fri.
Wed.
Fri.
Sun.
Sat.
Thu.
Sat.
Tue.
Sun.
Fri.
Sun.
Wed.
Tue.
Sun.
Mon.
Thu.
Wed.
June
Sept.
Dec.
March
June
Sept.
Dec.
March
June
Sept.
Dec.
March
June
Sept.
Dec.
March
June
Sept.
Dec.
20
22
21
20
21
22
21
20
21
23
21
20
21
23
22
20
20
22
21
23:09
14:49
11:12
11:02
05:04
20:44
17:11
16:57
10:51
02:29
23:03
22:45
16:38
08:21
04:48
04:30
22:34
14:21
10:44
7) You can use the program to layout sundials without need for
geometrical constructions (clock mode):
First, to find perfect north-south alignment of the gnomon (which is
difficult with ordinary compasses), just wait for the moment, when the
Sun is due south of your location: This is, when apparent solar time
for your location is exactly 12:00:00.
At this moment, adjust the gnomon in a way that its shadow strikes a
vertical plumb line, hanging from its upper end. (Respectively in a
way, that its shadow appears right under itself.) For this, turn
azimutally only and leave elevation unchanged, since elevation usually
should have been matched to your latitude before.
Then, if you want your sundial to show the civil (zone) time of your
time zone as accurate as possible, you must take into account the
equation of time (EQT): This means, simply do not draw the hour lines
on the full civil hours, but on full civil hours minus EQT: When
EQT = -12 min, you will have to draw the 9 o'clock line at 9:12 zone
time, when EQT = +3 min, draw the 9 o'clock line at 8:57 zone time.
However, if you want your sundial to show the local time of your
location (instead of zone time), you may use MAXCLOCK's local time
display instead: Draw the 9 o'clock line at exactly 9:00 local
apparent time, and so on.
You can apply any procedure on any sunny day of the year.
As usual, when compared to mean time, your sundial reading will always
be "fast" when EQT is positive, and "slow" when EQT is negative.
8) Extremes and zeros of the equation of time:
Watch the four days in a year, when the equation of time is zero. On
these days, readings from ordinary uncompensated sundials agree with
mean time - mean solar time equals apparent solar time.
While the days of agreement vary slightly from year to year as we
adjust for leap years, this usually happens at about April 16,
June 14, September 2, and December 25.
You may also watch the extreme values of the equation of time (up to
appr. 17 minutes), which appear at about February 12 and November 3.
Note that for epochs in the far past or far future these days of
occurence will wander considerably through the calendar year: This is
- First release
Oct.1.,1997 - Version 2.0
- Modified Julian date and day number displayed;
- Improved algorithm for Sun yields 3-arcsec-accuracy;
- Zodiac sign, distance, and equinox/solstice messages for the Sun
displayed;
- Equation of time computed by iteration to improve accuracy;
- Precession incorporated in finding the constellation for Sun;
- Display of position and appearance of the Moon included;
- Positions of Sun and Moon can now be computed with/without
nutation/aberration;
- Apparent solar time displayed, true solar time discontinued;
- Non-clock mode added to enable single computations;
- Screen buildup improved for slower computers, minor flaws corrected;
Jan.1.,1998 - Version 2.1
- Announcements for phases of Moon, solstices, and equinoxes are issued
more precisely;
- Non-clock mode modified to go back and forth in input files;
- Documentation supplemented;
- Minor screen cosmetics;
June 1.,1998 - Version 2.2
- DUT incorporated in configuration file, JD and MJD computations strictly
based upon UT1;
- Delta-T displayed, most recent IERS/NEOS values adopted for years from
1996 on;
- Date writing follows international standards ISO 8601 / EN 28601;
- Documentation supplemented;
Apr.7.,2002 - Version 3.0
- New algorithm for Sun coordinates (VSOP87) and Moon coordinates (ELP2000
82) considerably increases accuracy from arcsec to milliarcsec domain;
coordinates displayable both in mean dynamical ecliptic and equinox of
date and FK5 catalog equinox, latitude of Sun displayed;
- Illuminated fraction of the Moon, Sun-Moon elongation, and constellation
for Moon displayed;
- Equation of time computed by dynamically subtracting hour angles of mean
and apparent Sun (no more by iteration) - improves accuracy;
- DUT terminologically corrected to DUT1, DUT1 handling according to
common definition (DUT1=UT1-UTC), values may also be read from inputfile
and keyboard and then override configuration settings;
- Extended announcement intervals for solstices and equinoxes
(7days...1sec), new and full Moon (5days...1sec), 1st and 3rd quarter
(1day...1sec);
- Equation of equinoxes and apparent sidereal time displayed, various
computational alternatives for these items;
- Julian date and modified Julian date displayed both in terms of UT1 and
ET;
- Display of configuration file name discontinued;
- Display numerical resolution extended, screen cosmetics, some
announcements in color;
- Internal ephemeris time model updated: Taking regard of historical
eclipse data and most recent value for Moon's tidal acceleration yields
improved extrapolation for ancient and future times;
- Both clock and non-clock mode allow to override internal ephemeris time
model with user-supplied Delta-T values;
- Comes with window generators which supply the necessary support for ANSIescape-sequences under any DOS or WINDOWS operating system (no more