Closed moustakas closed 1 year ago
Here's this same object with the #92 branch of the code. I think I'm still inclined to fit these two lines as a single super broad line...
DEBUG:emlines.py:1400:_populate_emtable: SILIII_1892 VSHIFT: -350.9382
DEBUG:emlines.py:1400:_populate_emtable: SILIII_1892 SIGMA: 5847.4839
DEBUG:emlines.py:1400:_populate_emtable: SILIII_1892 AMP: 0.9683
DEBUG:emlines.py:1400:_populate_emtable: SILIII_1892 AMP_IVAR: 23.6975
DEBUG:emlines.py:1400:_populate_emtable: SILIII_1892 CHI2: 1.9116
DEBUG:emlines.py:1400:_populate_emtable: SILIII_1892 NPIX: 620.0000
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 FLUX: 301.1134
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 BOXFLUX: 367.9625
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 FLUX_IVAR: 0.0481
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 BOXFLUX_IVAR: 0.0481
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 CONT: 1.5050
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 CONT_IVAR: 31967.3565
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 EW: 59.4932
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 EW_IVAR: 1.2314
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 FLUX_LIMIT: 1.7393
DEBUG:emlines.py:1402:_populate_emtable: SILIII_1892 EW_LIMIT: 0.3436
DEBUG:emlines.py:1400:_populate_emtable: CIII_1908 VSHIFT: -350.9382
DEBUG:emlines.py:1400:_populate_emtable: CIII_1908 SIGMA: 5847.4839
DEBUG:emlines.py:1400:_populate_emtable: CIII_1908 AMP: 0.0032
DEBUG:emlines.py:1400:_populate_emtable: CIII_1908 AMP_IVAR: 24.0513
DEBUG:emlines.py:1400:_populate_emtable: CIII_1908 CHI2: 1.9203
DEBUG:emlines.py:1400:_populate_emtable: CIII_1908 NPIX: 626.0000
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 FLUX: 0.9942
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 BOXFLUX: 341.1957
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 FLUX_IVAR: 0.0493
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 BOXFLUX_IVAR: 0.0493
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 CONT: 1.5000
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 CONT_IVAR: 31872.2498
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 EW: 0.1971
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 EW_IVAR: 1.2538
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 FLUX_LIMIT: 1.7573
DEBUG:emlines.py:1402:_populate_emtable: CIII_1908 EW_LIMIT: 0.3484
Vicky has suggested we continue to model these lines separately and indeed the data do seem to demand two lines; closing.
SiIII] 1892 and CIII 1908 are sufficiently blended in many QSO spectra (given their line-widths) that it may be more numerically stable to fit both lines using a single Gaussian model. One example is
Here, I have tied the velocity width and centroid of the two lines together, but the optimizer chooses to drop CIII] and fit the whole line-emission with a single SiIII] line with a velocity shift of 2500 km/s (which is at the boundary of the prior) and a line-width of 4700 km/s. Meanwhile, allowing both lines to be fit independently results in both lines being dropped, which is not ideal.