      BRUCE Changes File

31/7/97 - Version 2.71 released

12/8/97 - I discovered today that there is a small error in the bruce
          user manual (section F.2 of my thesis). The parameter
          "use_mode_parameter" in the #timings command description
          should read "use_mode_period".

12/8/97 - I also found out (thanks to an observant user) today that the 
          "stellar_mass" parameter led to a run-time error. Upon inspection,
          I have discovered that the code dealing with it was broken, as
          was the code for the "polar_mks_gravity", so I fixed everything.
          Note that these bugs just stopped bruce from running - they didn't
          lead to erroneous results.


23/12/98 - Added a new TIMINGS parameter INCLUDE_ENDPOINTS which signifies that start and end spectra
           should be calculated at the start and end times, and equally spaced between, rather than
           calculated at the mid-points of equal-sized time-chunks. The latter puts the start and end
           spectra half a time-step in from the time endpoints, and is the "traditional" behaviour.

23/12/98 - Added a new TIMINGS parameter WRITE_TIMINGS_FILE which signifies that a space-separated
           list of dump files and their times should be written to the file $$$$$$$.times

25/1/99  - Added a new TIMINGS parameter TIMINGS_FROM_FILE which allows the times of all the field
           calculations to be specified in a file as a list. The argument of the parameter is the
           file name. Note that this is separate from WRITE_TIMINGS_FILE, which is for writing
           times OUT rather than reading them in. This parameter is exclusive with START_TIME,
           FINISH_TIME, INCLUDE_ENDPOINTS and NUMBER_OF_FIELDS, since the file contains all
           of this information. This change has made it necessary to now store all field times
           in the array Times, which is set up in blojob.f.

25/1/99  - Version 2.8 released
 
18/2/99  - Added in stuff to indicate the maximum size of radius variations for each field
           This required a new variable - dRMax

18/2/99  - Added in stuff to indicate the maximum size of temperature for each field
           This required a new variable - dTMax

14/6/99  - Added a new MODE parameter HORIZONTAL_PHASE_SHIFT to allow phase shifts in the horizontal 
           velocity fields to be modelled (this is primarily for simulations of wave leakage)

14/6/99  - Changed the reporting information written out, so that the effective temperature
           (=(Luminosity/(Sigma*Area))**0.25) is printed instead of the equal volume radius

13/10/99 - Radically changed the reporting used in breprt() to use FORMAT statements rather than
           character constants, in order to make the code more portable. Also moved various 
           output statements around in this file

22/05/00 - Deleted the variable AAmode, and introduced a new one in its place - TAmode.
           This gives the amplitude of fractional temperature perturbations (when combined
           with the angular basis function RBasis). If it is zero, then the original
           Buta & Smith (1979) expression is used to calculate the amplitude (the original
           behaviour). The command language has been modified accordingly - instead of
           using NA_AMPLITUDE_SHIFT, use TEMPERATURE_AMPLITUDE. Temperature perturbations 
           can be turned off completely by *not* specifying the TEMPERATURE_EFFECTS
           parameter

22/05/00 - The variable APmode (non-adiabatic temperature phase shift) has been renamed
           to TPmode ("temperature-phase"), and the parameter NA_PHASE_SHIFT has been
           renamed to TEMPERATURE_PHASE

22/05/00 - Changed the way the horizontal velocity fields are handled, to bring them in
           line with the way temperature perturbations are handled. The new variable HAmode
           gives the amplitude of horizontal velocity fields (when combined with the
           angular basis functions). If it is zero, then the amplitude is taken from the
           value of K. To set HAmode, use the HORIZONTAL_VELOCITY_AMPLITUDE parameter. Horizontal
           velocity fields can be turned off completely by *not* specifying the 
           HORIZONTAL_VELOCITY_FIELDS parameter. Note that this functionality replaces
           that originally offfered by the K_VALUE_OVERRIDE parameter; the latter has
           been deleted.

22/05/00 - Renamed the HORIZONTAL_PHASE_SHIFT parameter to HORIZONTAL_VELOCITY_PHASE, to
           bring it in line with the way temperature perturbations are handled

25/05/00 - Removed the PERIOD_FROM_NU parameter, and replaced it by the NU parameter, which
           just fundges the adopted value of NU; this involdes the new variable numode. If
           numode is zero, the nu is calculated using the usual expression nu=2Omega/omega.
           Rotational effects can be turned off completely by *not* specifying the
           MATRIX_DIMENSION parameter

08/06/00 - Noticed that, somewhere along the way, TIMINGS_FROM_FILE (see above) has been
           renamed to READ_TIMINGS_FILE - oops!

08/06/00 - Changed the way field calculations are reported in the output

19/06/00 - Version 2.83-1 released

24/07/00 - Altered the interpretation of TEMPERATURE_AMPLITUDE. Previously, it meant the
           relative amplitude of temperature perturbations; now, it acts as a conversion
           factor between the fractional radius and temperature perturbation amplitudes.
           Basically, it is the equivalent of the dR/R coefficient in the Buta & Smith
           adiabatic dT/T expression

03/08/00 - Discovered two errors in the lsdfdhor.f/lsdfdtor.f functions of the liblsd 
           library. These functions calculate the derivatives with respect to theta
           of the lsdfhor.f (horizontal displacement) and lsdftor.f (toroidal displacement)
           functions, respectively. The first error led to incorret results for (l>0,m=0) modes,
           whilst the second led to incorrect results for all (l-|m|>0) modes. I've verified
           that the functions now work for l<=4 modes (and there is no reason to expect
           that they won't work for ALL modes). The physical implications of the errors
           were erroneous horizontal velocity field eigenfunctions. Thanks to Joris
           De Ridder for spotting the problem. I guess this goes to show that BRUCE still
           may have bugs!

03/08/00 - Version 2.83-2 released



