You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the spectral axis is generated it is done so with wmax inclusive; this leads to numbers of spectral points such as 150001. This is also the number you get when printing len(sf.wavenumber). However, s.conditions['spectral_points'] yields the exclusive answer, i.e. 150000. It would be nice if these values were consistent.
I used the following script:
from radis import SpectrumFactory
sf = SpectrumFactory(
2150,
2450, # cm-1
molecule="CO2",
isotope="1,2,3",
wstep=0.002,
)
sf.fetch_databank("hitemp")
s = sf.eq_spectrum(
Tgas=1100.0, # K
pressure=1, # bar
mole_fraction=0.8,
path_length=0.2, # cm
)
馃挕 Possible solutions
Wouldn't it be better to use spectral axes with the wmax exclusive?
Alternatively, when updating the sf.conditions['spectral_points'], rather than calculating the number of points from input parameters the integer value should be read from elsewhere.
馃幉 Radis version
0.14
馃捇 Operating system
Windows
The text was updated successfully, but these errors were encountered:
馃悰 Describe the bug
When the spectral axis is generated it is done so with
wmax
inclusive; this leads to numbers of spectral points such as150001
. This is also the number you get when printinglen(sf.wavenumber)
. However,s.conditions['spectral_points']
yields the exclusive answer, i.e.150000
. It would be nice if these values were consistent.I used the following script:
馃挕 Possible solutions
Wouldn't it be better to use spectral axes with the
wmax
exclusive?Alternatively, when updating the
sf.conditions['spectral_points']
, rather than calculating the number of points from input parameters the integer value should be read from elsewhere.馃幉 Radis version
0.14
馃捇 Operating system
Windows
The text was updated successfully, but these errors were encountered: