Guidelines for developing, improving, and using ACES2/ACES3.
The source codes in ~rjbprogs/Src are considered the current standard.
I am reponsible for keeping them up to date. Any questions about
~rjbprogs/Src should be addressed directly to me.
The binaries generated from those source files are located in
~rjbprogs/bin/`arch`. Use ~rjbprogs/bin/set-path to put the appropriate
directory in your path.
I have designated Ken and Toby to maintain the local binaries (updating
them to match the compilers and operating systems). Group accessible CRAY
binaries are maintained by Ken and myself.
If you are developing new programs or modifing existing programs, please
copy the required modules to your working area from ~rjbprogs/Src. Then, do
the modifications in your local area.
Please avoid multiple copies of modules. ACES II is large program with
a complicated structure. Libraries are shared by many modules, and even a
mundane change may effect the functionality of another module. I want to
emphasize the fact that if you make changes to shared routines, you are
responsible for checking to make sure your changes do not effect the others.
The module joda does many, many things. Any changes to it, cosmetic or
otherwise, should be done with extreme caution. Please refrain from assiging
new key-words witout my consent.
It is our job to write new programs to go along with the standard
ACES II (or ACES III) structure. I am always availble to prime anyone on
basic ACES II structures. It is my experience however that the best way to
learn the structure is to look through a existing program (e.g., vcc).
Everything we do must eventually be added to the standard code, but how
soon and how often need to be decided by the developers and RJB. Therefore,
only I commit changes to ~rjbprogs/Src. If someone else in the group needs
to use new developments which have not yet been implemented, the programmer
is responsible for giving appropriate instruction to the users. This capacity
is only extended to group members. We do not support users outside rjbgroup
running non-standard applications.
Any changes to the standard will be sublject to the standard ACES II test
suite unless it is obvious to me that it is not necessary. Failing it is
an immediate ground for a re-write/debug.
External user issues are handled by myself and any questions regarding
external users must be directed to me.