The simplest way to run the code HOSPHE (v1.00) consists in providing the namelist input data in the following form:
./hosphe << end > pb208.n50.out &input AN=126,AZ=82,noscmax=50, icm=1,icoudir=-1,icouex=-1,keta_J=1,intera="SLy4",ordermax=2, epsilon=1.e-7,itermax=1000, Flag_read_ini_dm = .false.,restart = 0, alpha=0.65,ngrid=-80,boscil=-2,hbarom=-1/ end
The script above is provided in the distribution file of the code HOSPHE (v1.00). By executing the script, one obtains the output file ``pb208.n50.out'', which is also provided in the distribution file. The main section of this file, which gives the total energies in Pb calculated for the maximum HO shell included in the basis of and SLy4 Skyrme functional [14], reads
Kin.prot Kin. neut. Tot. kin. 1337.059947 2529.116266 3866.176214 T=0 Skyrme T=1 Skyrme Tot. Skyrme -6405.081099 106.598348 -6298.482751 Energy HF Energy Rearr. ene -1635.692396 -1635.692396 -1221.821085 Cou. tot. Cou. dir. Cou. exc. 796.614142 827.882912 -31.268770
|
In Figs. 1 and 2, we present results of
similar calculations performed for Pb and the HO bases of -70.
Fig. 1 shows the convergence of the total energy in function
of . It turns out that the energy converges exponentially
to the limiting value of , namely,
(118) |
By considering convergence patterns in a few more cases for different options and nuclei, we found that the trend with two different slopes is not a general feature. In the few cases we looked at, we found that it is only above 40-50 shells that the rate seems to stabilize to an exponential convergence. These results show that, in general, its not possible to find the extrapolated limit of energy just by calculating only a few points of the curve for some small numbers of shells.
|
Fig. 2 shows the dependence of CPU times on , obtained on the AMD Opteron Processor 2352 running at 2100MHz clock speed. First, one can see that the spherical-basis code HOSPHE (v1.00) is, of course, orders of magnitude faster that the 3D code HFODD (v2.40h) [15]. For , the former needs only 20sec of CPU time while the latter needs 250 000sec. Second, for both codes, the dependencies on are clearly given by power lows indicated in the figure. Strangely enough, these power lows are different for calculations performed below and above . At the moment, no explanation for such a timing pattern could be found.