Skip to content
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

Choose visit image IQ window for successful template generation #435

Open
drphilmarshall opened this issue Jan 25, 2017 · 18 comments
Open

Comments

@drphilmarshall
Copy link
Contributor

@SimonKrughoff Sounded like a minimum IQ of 2.5 pixels might work - keep us posted! When you find a set up that works, I guess we'll need the cookbook updated for @tony-johnson to work off. Good luck!

PS. Ill add this to the Run 3 DM Workflow epic #421

@SimonKrughoff
Copy link
Contributor

Some background. I thought that u-band was not subject to the issue we were seeing. I.e. in r-band:
image

But it also happens in u-band.
image

It turns out that there are far fewer images in u-band with IQ in the range 2. - 2.5 pixels.

@SimonKrughoff
Copy link
Contributor

Here is an r-band image with reported FWHM = 2.5:
image

It seems to be right on the hairy edge. E.g. for another image with FWHM = 2.45:
image

To be conservative, I'm going to suggest we make the window 2.6 < FWHM < 3.0. Here is an example of an image with FWHM = 2.63:
image

I am wondering if this has something to do with a minimum size for the PSF basis set.

@drphilmarshall
Copy link
Contributor Author

drphilmarshall commented Jan 26, 2017 via email

@SimonKrughoff
Copy link
Contributor

I'll file a ticket. The problem is putting together a minimal "how to repeat".

@SimonKrughoff
Copy link
Contributor

And I think it will have enough frames, but I don't have a histogram on hand to show that.

@SimonKrughoff
Copy link
Contributor

O.K. I ran a coadd generation with makeCoaddTempExp.py /global/cscratch1/sd/desc/twinkles/work/6/output --output $SCRATCH/test_out --selectId filter=r --id filter=r --config modelPsf.defaultFwhm=3.00 select.minPsfFwhm=2.60 select.maxPsfFwhm=3.00 --clobber-config --no-versions. That seemed to work pretty well. It produces a coadd with 166 visits (over all 10 years) as opposed to 295 visits.

Here's a cutout:
image

There are still a few artifacts I don't understand, but we should look at some diffims to see how they look.

I'll update the cookbook later today.

@drphilmarshall
Copy link
Contributor Author

drphilmarshall commented Jan 27, 2017 via email

@SimonKrughoff
Copy link
Contributor

Yes. 10-20 should be plenty. Of course, the fewer images that go into the template, the less sensitivity we have, but we'll still get something useful out.

@SimonKrughoff
Copy link
Contributor

FYI, I didn't get the cookbook out yesterday, because I'm trying to update both at once since they are related.

@drphilmarshall
Copy link
Contributor Author

drphilmarshall commented Jan 27, 2017 via email

@SimonKrughoff
Copy link
Contributor

O.K. so this ended up being a the place where I did a bunch of things. I now have a cookbook that sketches out both level 1 and level 2 processing using appropriate configs for each. There are still some things I'd like to try out: e.g. a different PSF estimation algorithm.

I don't know how to review this and get it merged, but my suggestion is that we use this cookbook to do run 3. I also suggest merging twinkles_#435 to twinkles_3 instead of merging it with twinkle_1, but I'm can certainly be talked out of that.

@drphilmarshall
Copy link
Contributor Author

drphilmarshall commented Feb 3, 2017 via email

@SimonKrughoff
Copy link
Contributor

So the diaObjectMaker.py can take any valid dataId, so you can build per filter DiaObjects, but if you don't specify a filter it will aggregate over all of them.

Just to be clear, I am not doing any sort of averaging over the source properties. That's hard enough to get right that I want to do that in the issue that covers the forced photometry. @wmwv may have ideas about that.

I have made a few single band DiaObjects, but one remaining issue is how to reject the epochs from the DiaObject that went into the coadd.

@drphilmarshall
Copy link
Contributor Author

drphilmarshall commented Feb 3, 2017 via email

@SimonKrughoff
Copy link
Contributor

I just updated the cookbook again. I'm considering this a fairly complete list of example command lines except forced phot for diaObjects.

@drphilmarshall
Copy link
Contributor Author

@SimonKrughoff Looks like the cookbook recipe at https://github.com/LSSTDESC/Twinkles/blob/master/doc/Cookbook/Coadd_Diffim_Recipe.md needs finalizing to reflect the final scheme (including using Year 1 for the template and Years 2-10 for science).

@SimonKrughoff
Copy link
Contributor

O.K. I will try to get to this today.

@rbiswas4
Copy link
Member

Since we are looking into this now again to understand what needs to be done.

@SimonKrughoff : Is this still the recommended way to go?

If I understand the last comment right, we need to build the template for coadd using the visits in year 1. Is that correct @drphilmarshall ?
We have those obsHistIDs. Is the way to implement these here in adding the list of obsHistIDs to the makeDiscreteSkyMap flag --id @SimonKrughoff ?

Thanks!

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

No branches or pull requests

3 participants