New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QL config update and fibermap conform #699
Conversation
@felipelm since I don't have writing privileges there please copy the new redwood data set [night 20200515] that QL/F have to work with, from this address on NERSC: /project/projectdirs/desi/datachallenge/redwood/20200515 onto desi-1. This PR only has two changes for QLF:
let me know if it would be helpful to create a PR for the changes on the qlf side. Thanks. |
@Srheft you have the same permissions as I because we use the same Ok, I'll make a PR on qlf with these changes and reference here. |
@felipelm last time I tried to copy data on /data directory it said permission denied. Will you copy the redwood data or I should go ahead and do that? |
Got errors running
|
Yeah this is one change I had to make because of the redwood data. I'll see how can i make it to work for both. Lack of key 'PROGRAM' made me do some changes. Could you try an arc and make the change I mentioned to arc processing? |
Arc ran fine but arc XWsigma plot didn't work so I'm trying to debug it now. |
Yeah this PR has added xwsigma in arc. Thanks. |
@Srheft seems like |
Running |
calibration frames [flat and arc] are not pointed at any set of astronomical objects so the RA DEC arrays are empty. one would only look for them in a science exposure. |
@felipeaoli care to give your input on this plot? |
you mean the xwsigma plot for arc? the xwsigma plot for any flavor is created here: xsigma plot |
@Srheft we also use reference values in color maps for some cases. |
@felipeaoli oh not only I did not know that, I also don't know what color map in this context :) update: upon remembering bokeh graphics, I just got what you meant :) @felipelm is everything ok with the science exposure runs now? |
@Srheft just finish testing and everything seems ok now. |
@felipeaoli did you merge this PR? |
@felipelm could you let me know why this merge happened? |
sorry, I was answering another PR and made a mistake |
@felipeaoli I don't see this being reverted. I still see this branch merged. |
@felipeaoli @Srheft you have to merge the other PR to revert the changes on master and open a new one with this changes |
@felipelm i don't know what is going on here. |
@felipeaoli accidentally merged this pull request to master and opened a new one to revert this merge #701 To undo the merge you will have to:
|
@felielm and @felipeaoli Please do not merge QL branches/PRs. These should only be merged by @Srheft or myself (or @sbailey) because we are aware of any internal reviews, tests or edits we are pursuing. PR #701 unfortunately does not retain the comment history, and I am unclear on the status of master at this point. @sbailey could you please indicate if master has still the merged code, or has been returned to the pre-merge basis? Please do no further merge until I can finish examining the final edits. Assuming master is in a pre-merge state, we will merge the outstanding PR. |
Sure @rkehoe . This was exclusively my fault, I accidentally merged it. I'm very sorry |
@felipeaoli I accept your apology, but then why did you create another PR #702? I have to be clear: do not continue to try to 'fix' this situation in desispec. @Srheft This PR (#699) looks good and accomplishes the tasks of converging science configs, evening out calibration exposure processing chains, and further improving fitting QAs like XWSigma and SNR. There appears to be another PR built to restore this one, so I am further confused as to the status of this code. I have only one suggestion before signing off on this PR as it was originally before the accidental merge: I think you can go ahead and remove the now obsolete darksurvey, brightsurvey and _graysurvey_configs. We just have science now. I have some other questions/suggestions, but aside from removing the obsolete configs, these should not hold up a final merge of this code. If master has been restored to pre-merge status, then this PR (#699) should still be able to be remerged into master. We can chat about how to proceed offline. I will contact you this afternoon. |
@rkehoe once a PR has been merged, it can't be re-merged. What can be done is open a new PR to undo (revert) the accidental merge changes (which @felipeaoli did with PR #701), and then when ready open a new PR to perform the same merge as the original PR when ready (which is what he prepared with PR #702, which correctly references this PR for traceability, but hasn't been merged yet). @felipelm and @Srheft : please deploy the equivalent of PR #702 and desihub/qlf#253 on http://desi-1.kpno.noao.edu:9090 . When that is tested and it all works together we can proceed with merging those two PRs. desi-1 was offline yesterday for cooling system maintenance but it is back today. |
I've made the deploy of #702 using desihub/qlf#253 on http://desi-1.kpno.noao.edu:9090 Ran arc, flat, and three science (dark, gray, bright) exposures and seems to be working fine. All plots are showing with the changes made using the new science config file and xwsigma is now showing on arcs CHECK_CCDs. Seems like the production database is not up so http://desi-1.kpno.noao.edu:9000/ backend is offline. |
@felipelm great, thank you. |
@Srheft @felipelm @rkehoe : let's merge #702 and deishub/qlf#253 and then make new tags. I have meetings for the next 2 hours, but if you haven't made the merges by then I can do it. I'll submit tickets for any problems I find on @rkehoe from |
…revert QL config update and fibermap conform - #699 changes
@sbailey. There were three potential small updates, one of which was mentioned in my comment 5 days ago (eg. Removing the now obsolete dark/gray/bright Survey configuration in favor of the merged config). Two others I discussed offline w/@Srfheft, one I remember was about choice of arc-lines to look at in the configuration. None of the three were implemented yet into #699 — they were about to be before the accidental merge. They are not necessary for this PR or #702, but we agreed to do them. They can be in a subsequent PR, for sure. |
This PR:
@sbailey please see ticket #698.
Keeping with our general rule, this PR will be tested in QLF [with new format data] before merge.