Skip to content
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.

arc XWSIGMA drill down error #265

Open
sbailey opened this issue Oct 24, 2018 · 5 comments
Open

arc XWSIGMA drill down error #265

sbailey opened this issue Oct 24, 2018 · 5 comments

Comments

@sbailey
Copy link

sbailey commented Oct 24, 2018

Testing http://desi-1.kpno.noao.edu:9090 using code from desispec #702 (now tag 0.25.0) and qlf #253, mostly looking at Observing History window and drill-downs.

arc exp 3571 Step 1 XWSIGMA has a warning, but the drill down view has "Can't load QA: object of type 'NoneType' has no len()" so I can't tell what is wrong.

@felipelm
Copy link
Member

felipelm commented Nov 6, 2018

@sbailey we fixed this issue please verify at http://desi-1.kpno.noao.edu:9090/

@sbailey
Copy link
Author

sbailey commented Nov 6, 2018

I no longer see the error message, but I'm not sure the values in the plots are meaningful. Please check if this is due to QL outputs, or due to the interpretation of those outputs. If the problems are in the QL outputs themselves, please open a ticket in desispec and then go ahead and close this:

  • X std dev and W std dev have some fibers that are hundreds or thousands of pixels?
  • Middle histograms could use some tuning so that the huge outliers don't dominate the bin size choices
  • XSIGMA AMP and WSIGMA AMP have 'nan' for amps 1 and 2 (I don't think per-amp values for these metrics are meaningful anyway)

image

@felipeaoli
Copy link
Contributor

felipeaoli commented Nov 7, 2018

Hi Stephen,
Thanks for your review. Regarding your points:
1) X std dev and W std dev have some fibers that are hundreds or thousands of pixels?
We are receiving this values from quicklook.

**2)** Middle histograms could use some tuning so that the huge outliers don't dominate the bin size choices

I tried here some options, but the outliers are extremely larger than median. So, I coded a modified Z-score method function but in this case it seems better to show the outliers in a different histogram (in the same plot).

**3)** XSIGMA AMP and WSIGMA AMP have 'nan' for amps 1 and 2 (I don't think per-amp values for these metrics are meaningful anyway)

I kept the plot because the is still in the ql results for this flavor, but we can remove it. Regarding the nan's it seems something strange in the shape of list XSIGMA_AMP (e.g. [[nan, nan, 0.242, 0.240], [nan, nan, 0.247, 0.248]] )

@Srheft , could you please help us with the items 1) and 3) ?

image

@Srheft
Copy link

Srheft commented Nov 7, 2018

Hi @felipeaoli could you use PR#707 and see if you still see the NaNs in XWSIGMA_AMP? let me know for what exposure it occurred. Thank you.

@Srheft
Copy link

Srheft commented Nov 7, 2018

@felipeaoli if this PR behind the master, once the changes in the master are in this PR, those spikes in the XWSigma histogram should be removed. Or if you run master on an arc exposure, you should not see the spikes; please let us know if you still see them then. Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants