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

[13BL] L+2-1 is showing misalignment #9

Open
mtbannister opened this issue Jun 11, 2014 · 17 comments
Open

[13BL] L+2-1 is showing misalignment #9

mtbannister opened this issue Jun 11, 2014 · 17 comments

Comments

@mtbannister
Copy link

Middle image of triplet is some distance away from first and last of triplet. Showing up consistently on multiple chips, both on reals and fks.

@ijiraq
Copy link
Member

ijiraq commented Jun 12, 2014

Also on chip 29..

@brettgladman
Copy link

On Thu, 2014-06-12 at 10:52 -0700, JJ Kavelaars wrote:

Also on chip 29..

I don't know how bad this misalignment has to be to
merit me to sending an email on it.

That is, I am frequently seeing postage stamps where there
are small misalignments of the postage stamps (a few to
perhaps 10 arcsec), which I assumed was postage stamp
creation and not an alignment problem in the data. It is
true that if the shifts I am seeing were in the real data
and one didn't know, you wouldn't find real things. But
I am assuming that this is not the problem, because if I
manually center on a star, the planted objects move
perfectly linearly.

I assume what I should be reporting is the more extreme
cases where I can tell that one of the postage stamps is
not even close... I saw that once (first triple I was shown
when the validate tool started working yesterday), but not
since.

Brett

@ijiraq
Copy link
Member

ijiraq commented Jun 12, 2014

please report 100% of the cases. the more details the more likely we can make this stop.

@mtbannister
Copy link
Author

I've been mentioning here the case when one of the cutouts is of a completely different part of the chip.

@ijiraq
Copy link
Member

ijiraq commented Jun 12, 2014

i'm happy to see them all reported. with details that will allow the errors to be fixed. I've not see any 'minor' mis alignments.

BTW: Just because something can be fixed does not mean it will be.

@mtbannister
Copy link
Author

And now p8. Will want to reprocess this field I think.

@brettgladman
Copy link

Field

L-2-1

CHIP27
according to header

Middle frame shows another portion of sky.

I don't see that we agreed what to do here.

  1. Accept what we can based on two good frames?
  2. Accept/reject all?
  3. Cntrl-C and start validate again to get different CCD?

I did the 3 for now.

Brett

On Thu, 2014-06-12 at 11:11 -0700, Michele Bannister wrote:

And now p8.


Reply to this email directly or view it on GitHub.

@ijiraq
Copy link
Member

ijiraq commented Jun 12, 2014

Chip10/CCD09 also has error.

@ijiraq
Copy link
Member

ijiraq commented Jun 13, 2014

report 100%
JJ

On Jun 12, 2014, at 1:59 PM, brettgladman [email protected] wrote:

On Thu, 2014-06-12 at 10:52 -0700, JJ Kavelaars wrote:

Also on chip 29..

I don't know how bad this misalignment has to be to
merit me to sending an email on it.

That is, I am frequently seeing postage stamps where there
are small misalignments of the postage stamps (a few to
perhaps 10 arcsec), which I assumed was postage stamp
creation and not an alignment problem in the data. It is
true that if the shifts I am seeing were in the real data
and one didn't know, you wouldn't find real things. But
I am assuming that this is not the problem, because if I
manually center on a star, the planted objects move
perfectly linearly.

I assume what I should be reporting is the more extreme
cases where I can tell that one of the postage stamps is
not even close... I saw that once (first triple I was shown
when the validate tool started working yesterday), but not
since.

Brett

Reply to this email directly or view it on GitHub.

@ijiraq
Copy link
Member

ijiraq commented Jun 13, 2014

3 seems reasonable to me

On Jun 12, 2014, at 3:01 PM, brettgladman [email protected] wrote:

Field

L-2-1

CHIP27
according to header

Middle frame shows another portion of sky.

I don't see that we agreed what to do here.

  1. Accept what we can based on two good frames?
  2. Accept/reject all?
  3. Cntrl-C and start validate again to get different CCD?

I did the 3 for now.

Brett

On Thu, 2014-06-12 at 11:11 -0700, Michele Bannister wrote:

And now p8.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub.

@brettgladman
Copy link

L-1-1 CHIP10 had/has serious misalignment. The linearity of the source looks like it planted linearly in misaligned frames.
Brett Cntrl-C'd this one, leaving it behind to be re-blinked. I am piling them up this way.

@jjk notes that this shift problem exists for both the 'p' and 's' images (i.e., effects the search and the calibration). Also, step2jmp reports '0' fully identified stars but still claims to have been successful. Also, checktrans claims this was a successful run.

@brettgladman
Copy link

L-1-1 CHIP17
also misaligned. This is one of the rare ones where I found two CCDs
on the same field misaligned.

I cntl-C'd the validate session

@mtbannister
Copy link
Author

fk_13BL+2-1_s27 misaligned.

@mtbannister
Copy link
Author

fk_13BL-2+1_s31 misaligned.

@mtbannister
Copy link
Author

fk_13BL+2-1_s35 misaligned.

@mtbannister
Copy link
Author

fk_13BL+2-1_s30 misaligned.

@mtbannister
Copy link
Author

I have moved to /quarantine:
fk_13BL+2-1_s27.measure3.cands.astrom
(fk_13BL-2+1_s31 already moved under #12)
fk_13BL+2-1_s35.measure3.cands.astrom
fk_13BL+2-1_s30.measure3.cands.astrom
and from what I interpret of the comments above which I think are getting the chip ID from the image header, these files have also gone to quarantine:
fk_13BL+2-1_s28.measure3.cands.astrom (JJ's chip 29; no p28 exists)
13BL+2-1_p8.measure3.cands.astrom (my p8)
For Brett's L-2-1 chip 27 by header, no file fk_13BL-2-1_s26.measure3.cands.astrom exists; I have moved 13BL-2-1_p26.measure3.cands.astrom which was done by Brett to /quarantine.
I can't find a L+2-1 file with a JJ tag on it that corresponds to JJ's "Chip10/CCD09". No action there.
13BL-1-1_p10.measure3.cands.astrom is reported as 'done' by gladman. p9 is reported as done by JJ. No action taken as I can't determine which file is the rejected one.
fk_13BL-1-1_s16.measure3.cands.astrom lock held by gladman, moved to /quarantine.

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

No branches or pull requests

3 participants