-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update Targname for 3 exposures on UT 8/16/2024 #933
Comments
The files have been updated on kpfserver.
The OBJECT keyword comes from the kpfexpose service.
That service says that the OBJECT being observed was 4628.
Is this an OB problem?
…On Fri, Aug 16, 2024 at 10:09 AM Howard Isaacson ***@***.***> wrote:
These three observations are of HD 10700, but have incorrect targname
values.
Update header with correct starname where appropriate.
DCS name keyword in the header confirms the star is HD 10700.
KP.20240816.55881.38
KP.20240816.55787.70
KP.20240816.55693.82
—
Reply to this email directly, view it on GitHub
<#933>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJJHGVBXMZGKJEX6X42GULZRYW57AVCNFSM6AAAAABMUNBACWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TANRUGA4TMMI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Correct, the OB for 4628 was run, but the observed star was 10700.
On Fri, Aug 16, 2024 at 10:46 AM Brad Holden ***@***.***>
wrote:
… The files have been updated on kpfserver.
The OBJECT keyword comes from the kpfexpose service.
That service says that the OBJECT being observed was 4628.
Is this an OB problem?
On Fri, Aug 16, 2024 at 10:09 AM Howard Isaacson ***@***.***>
wrote:
> These three observations are of HD 10700, but have incorrect targname
> values.
> Update header with correct starname where appropriate.
> DCS name keyword in the header confirms the star is HD 10700.
>
> KP.20240816.55881.38
> KP.20240816.55787.70
> KP.20240816.55693.82
>
> —
> Reply to this email directly, view it on GitHub
> <#933>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAJJHGVBXMZGKJEX6X42GULZRYW57AVCNFSM6AAAAABMUNBACWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TANRUGA4TMMI>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#933 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKFHJ67EYFZUVJZPRYYOPLZRY3G7AVCNFSM6AAAAABMUNBACWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTHEYTCMJZGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
--
------------------------------------------------------------------------------------------------
Howard Isaacson
Research Scientist in Astronomy
University of California, Berkeley
------------------------------------------------------------------------------------------------
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These three observations are of HD 10700, but have incorrect targname values.
Update header with correct starname where appropriate.
DCS name keyword in the header confirms the star is HD 10700.
KP.20240816.55881.38
KP.20240816.55787.70
KP.20240816.55693.82
The text was updated successfully, but these errors were encountered: