-
Type:
Story
-
Status: Won't Fix (View Workflow)
-
Priority:
Normal
-
Resolution: Won't Fix
-
Component/s: drp_1d, drp_1dpipe
-
Labels:
The simple sanity check on the redshift determination in the recent end-to-end processing (see attached) seems to show strangely bad redshift determination. The redshifts from 1D pipeline are mostly ~0.9 or ~2.3. Could you confirm that this is real or I'm doing something wrong? I'm using version 0.22.0 and the configuration is attached. The results are also in https://pfs.ipmu.jp/internal/devarch/ipmu/pipe_e2e/ .
This is an example pfsObject, which is z=1.4979 object but the 1D result is 2.2925.
pfsObject-00001-00000-0,0-0000000000000318-006-0x7ace412dc05971ff.fits
The two horizontal lines in the z_meas vs z_true plot are typical of artefacts at given wavelength that are mistaken for emission lines. z=2.29 is a redshift for which OII corresponds to a strong sky emission line, and therefore the subtraction residual can be identified as OII (see plot Skyline_1226nm). We have to check the associated variance, and decide wether we'll have to mask this spectrum part.
Indeed the error associated to the spectrum does not indicate that this pseudo emission line is not real but the mask has a non zero value. We therefore have to include the mask values in the 1D pipeline. I'll open a new ticket
Thank you for the investigation. Can I close this ticket and move to the new ticket?
OK, thank you. I closed this one.
This may be due to the issue in
PIPE2D-873, which will be resolved with the new simulated data.