Opened 2 years ago

Last modified 2 years ago

#334 new defect - wrong answer

LAMDA level energies are approximate and cannot be used to derive line energies

Reported by: Gary J. Ferland Owned by: nobody
Priority: good to do Milestone: database infrastructure
Component: atomic/molecular data base Version: trunk
Keywords: Cc:

Description

We use level energies to derive line wavelengths in the LAMDA database. The level energies are frequently only given to ~5 significant figures. The levels are closely spaces to this carries over into a significant uncertainty in the line wavelength.

The fix is to use the line frequencies, also in the LAMDA file, to set the line energy/frequency/wavelength.

Note from Nick:

I think there is a discrepancy.  If I take transition #2, which is the difference in 
the energy of level 3 to level 1, I get 0.0556.  However, the third transition, 
which is the difference between level 4 and level 2, is also 0.0556.  This is why 
the same wavelength appears, because of the same energy difference.  You are 
correct, the energies need better precision for molecules with hyperfine 
structure.

I get a wavelength of 17.9860c for the two transitions.  I took the difference of 
0.0556, multiplied by the ERG1CM conversion factor in Cloudy, then used the 
same value of Planck's constant and the speed of light in Cloudy to get the 
wavelength.  

Change History (1)

comment:1 Changed 2 years ago by Gary J. Ferland

Milestone: C16_branchdatabase infrastructure
Priority: blockergood to do

Nick derived accurate level energies for the three lowest levels of OH. With r10537 OH now has correct line wavelengths and energies. Checks showed that OH was the only one of the LAMDA molecules which had low precision energies.

This issue is resolved for OH and LAMDA appears OK as we now have it. But it would be very nice to have the ability to use their line frequencies, which are quoted to high precision, rather than relying on their energies. So I am demoting this from a blocker to C16 to something good to do for the database.

Note: See TracTickets for help on using tickets.