-rw-rw-r-- 1 marki clas 2316 Apr 3 13:37 dc_distance_to_time.o
-rw-rw-r-- 1 marki clas 3024 Apr 3 13:37 dc_fill_d_to_t_table.o
-rw-rw-r-- 1 marki clas 2960 Apr 3 13:37 dc_fill_t_to_d_table.o
-rw-rw-r-- 1 marki clas 4632 Apr 3 13:37 dc_getcal_tdly.o
-rw-rw-r-- 1 marki clas 2868012 Apr 3 13:37 dc_getcal_xvst.o
-rw-rw-r-- 1 marki clas 4384 Apr 3 13:35 dc_nominal_geom.o
-rw-rw-r-- 1 marki clas 8432 Apr 3 13:37 dc_read_tdly.o
-rw-rw-r-- 1 marki clas 5772 Apr 3 13:37 dc_read_xvst.o
-rw-rw-r-- 1 marki clas 1868 Apr 3 13:37 dc_set_def.o
-rw-rw-r-- 1 marki clas 3084 Apr 3 13:37 dc_tcl_init.o
-rw-rw-r-- 1 marki clas 1488 Apr 3 13:37 dc_time_to_distance.o
-rw-rw-r-- 1 marki clas 3980 Apr 3 13:37 dc_xvst_choice2.o
-rw-rw-r-- 1 marki clas 2400 Apr 3 13:37 dc_xvst_choice4.o
-rw-rw-r-- 1 marki clas 4648 Apr 3 13:37 dc_xvst_curve.o
-rw-rw-r-- 1 marki clas 2540 Apr 3 13:37 dc_xvst_get_doca.o
-rw-rw-r-- 1 marki clas 3804 Apr 3 13:37 dc_xvst_get_tdrift.o
-rw-rw-r-- 1 marki clas 1092 Apr 3 13:37 ddly2dc_cal_tdly.o
This is due to the inclusion of dc_xvst.inc. That's the big one. And even
though many of the routines include it, it only happens in dc_getcal_xvst
because that routine initializes some of the dc_xvst.inc common blocks
with data statements. This an absolute crime in fortran77 although we seem
to get away with it on most platforms (we get away with other f77 crimes
as well).
The correct way to initialize a common block is with a block data
routine. I don't know whether or not that will fix Liming's problem, but
it's worth a try.
Who is the one responsible for this routine? This structure has been
present since the beginning of our cvs repository.
In the long-term: can we have a less memory-intensive way to do the d-t
relationship?
-- Mark
Mark M. Ito, Thomas Jefferson National Accelerator Facility
12000 Jefferson Ave., Mail Stop 12H, Newport News, VA 23606
Email: marki@jlab.org, Office: (757)269-5295, Pager: (757)680-7175
WWW: http://claspc2.cebaf.gov/~marki/