Custom Query (193 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (19 - 21 of 193)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Ticket Resolution Summary Owner Reporter
#330 wontfix grain convergence failures peter Gary J. Ferland
Description

In both c13_branch and the trunk the following sim aborts before the first zone:

########### shape of considered galaxy
table AGN T=1.5e5 k, a(ox)=-1.4, a(uv)=-0.5, a(x)=-1
Q(h) 48 % vary
#
########### gas
hden 15
metallicity -1
abundance ism, no qheat
radius 22 cm        % 2kpc from qso
#
########### grid
iterate
#
stop zone 1

Typical output follows:

 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.68
 PROBLEM  ConvFail 18, a grain failure occurred iteration 1 zone 0 fnzone  13.68 NONE!!!!! 0 0
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.69
 PROBLEM  ConvFail 19, a grain failure occurred iteration 1 zone 0 fnzone  13.69 NONE!!!!! 0 0
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.70
 PROBLEM  ConvFail 20, a grain failure occurred iteration 1 zone 0 fnzone  13.70 NONE!!!!! 0 0
 Stop due to excessive convergence failures - there have been 20 so far. 
 This limit can be reset with the FAILURES command.
 ConvFail sets lgAbort since nTotalFailures=20 is >= LimFail=20
 This limit can be reset with the FAILURES command.
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.70
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.70
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.70
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.70
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.70
 PROBLEM  charge/temperature not converged for  sil-ism04 zone 13.70
#328 fixed incorrect STOP COLUMN DENSITY nobody Gary J. Ferland
Description

A user sent this sim, reporting that it does not stop at the indicated column density

Title test effect of mettalicity on spin temperature
constant temperature 2.5
hden 1.6 
table ism 
extinguish column 22
CMB, z=0
cosmic rays rate -17.3 
abundance ism no grains
grains ism no qheat
stop temperature 3K linear
%
% this one works properly
% stop column density neutral 9 
% this one does not
stop column density neutral 20. 

The stop column density neutral 9 produces a stop message saying the following:

   Calculation stopped because H0 column dens reached. Iteration 1 of 1

and the column density is correct:

 Hydrogen    9.000  4.919  4.621 (H2)                Log10 Column density (cm^-2)

With the larger column density the stop message says

   Calculation stopped because H0-H0+H2 column dens reached. Iteration 1 of 1

and we have these column densities:

 Hydrogen   19.852 15.275 19.208 (H2)                Log10 Column density (cm^-2)

The behavior is the same on c13_branch and the trunk.

The large column density sim has significant H2. It looks like the NEUTRAL and ATOMIC keywords are swapped around?? What does

H0-H0+H2

mean??

Maybe this is a time to remove these special cases and simply stop on a species column density.

#326 fixed multiple line matches in H-like iso-sequence nobody Gary J. Ferland
Description

n - n' lines in the H-like iso-sequence have nearly degenerate wavelengths and appear as a single line in most astronomical spectroscopy. But, when treated as nl resolved levels, there are a large number of these lines and we want the total intensity, since that is what is measured.

The decision was made to add the intensities of all of the n'l' - nl lines together and place that sum in the first of the lines, then set the remaining lines to zero. This works well since it is unambiguous, we normally do not print lines of zero intensity, and the line-matching algorithm, at the time, would settle upon the first match.

The line-match logic was changed to find the "best" match in the entire lines array. That then detects that there are many n'l' - nl lines with the same wavelength and emits this warning:

WARNING: multiple matching lines found in search for "H  1" 1.73621m
WARNING: match 1 is "H  1      1.73621m [ 10^2P->  4^2S]" (dwl=-0.00195312A)
WARNING: match 2 is "H  1      1.73621m [ 10^2S->  4^2P]" (dwl=-0.00195312A)
WARNING: match 3 is "H  1      1.73621m [ 10^2D->  4^2P]" (dwl=-0.00195312A)
WARNING: match 4 is "H  1      1.73621m [ 10^2P->  4^2D]" (dwl=-0.00195312A)
WARNING: match 5 is "H  1      1.73621m [ 10^2F->  4^2D]" (dwl=-0.00195312A)
WARNING: match 6 is "H  1      1.73621m [ 10^2D->  4^2F]" (dwl=-0.00195312A)
WARNING: match 7 is "H  1      1.73621m [ 10^2G->  4^2F]" (dwl=-0.00195312A)

The auto test suite has ~15k of such lines:

cloud9 auto:grep "WARNING: match" *.out | wc
  15284  167487 1450071

The warnings like dire and were a point of concern for the participants in the recent Warsaw workshop. They are about a design decision that was made in how we treat these nearly energy-degenerate lines. We should either figure out a way to silence the warning (do not do it for the H-like iso sequence) or disable this check in release versions.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note: See TracQuery for help on using queries.