Custom Query (193 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 193)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#342 fixed enable H2 Lique collisions by default AFTER branch nobody Gary J. Ferland
Description

r10640 added the Lique (2015) H2 collision data set. These are better than the Flower data we now use, and includes reactive op changing collisions. There are a number of botches when there data are used. Phillip recommended using these data.

#341 fixed Co 2 atomic data by Storey et al. nobody Gary J. Ferland
Description

We now have only a baseline model - g-bar for CS. This will be a nice improvement.

Title:	
Collision strengths and transition probabilities for Co II infrared forbidden lines
Authors:	
Storey, P. J.; Zeippen, C. J.; Sochi, Taha
Publication:	
eprint arXiv:1509.03164
Publication Date:	
09/2015
Origin:	
ARXIV
Keywords:	
Physics - Atomic Physics, Astrophysics - Solar and Stellar Astrophysics, Physics - Computational Physics
Comment:	
9 pages, 4 figures, 7 tables
Bibliographic Code:	
2015arXiv150903164S
Abstract

We calculate collision strengths and their thermally-averaged Maxwellian values 
for electron excitation and de-excitation between the fifteen lowest levels of 
singly-ionised cobalt, Co+, which give rise to emission lines in the near- and 
mid-infrared. Transition probabilities are also calculated and relative line 
intensities predicted for conditions typical of supernova ejecta. The diagnostic 
potential of the 10.52, 15.46 and 14.74 micro-metre transition lines is briefly 
discussed.
#340 fixed SPECIES command issues nobody Gary J. Ferland
Description

The SPECIES command allows details of the treatment of database species to be changed. Tests show the following:


The command is not defended against user error. The command

species "ty3" lvls 3

does not result in any error message, even though the species name is invalid, and the option is misspelled. This is especially important because we now are case sensitive. It will be common for a user to make a mistake with the species name, since we were not case sensitive in the past.


The command parser does the following

species "Si+" levels 10
species "Si+" levels all
species "Si+" levels=all

The first and last work as expected while the middle does not work and does not result in an error.


species level does not work for Fe, probably because we use more levels for this element, as explained in Lykins+13, section 2.9.

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