Keck-DataReductionPipelines / KPF-Pipeline

KPF-Pipeline
https://kpf-pipeline.readthedocs.io/en/latest/
Other
11 stars 2 forks source link

Exceptionally high systemic velocity star #781

Open howardisaacson opened 8 months ago

howardisaacson commented 8 months ago

The star HIP112486 has a systemic RV of -269 km/s. The result is that the Cross correlations are flat. The current L0 files have a value of 0 for TARGRADV. I think if these are updated, the high systemic RV can be accounted for. ex: https://jump.caltech.edu/observing-logs/kpf/KP.20231124.16822.76

bpholden commented 8 months ago

The FITS header keyword TARGRADV comes from the telescope control system, and not from the kpfconfig service (that is where newer keywords like the GAIA ID come from.) To be filled in, the starlist must include the value. It is possible that the value could be directly written to the dcs service by the observing software. Otherwise, we need a separate way to include that information. I could replicate the keyword but make it part of kpfconfig.

On Tue, Jan 16, 2024 at 10:40 AM Howard Isaacson @.***> wrote:

The star HIP112486 https://jump.caltech.edu/star/hip112486 has a systemic RV of -269 km/s. The result is that the Cross correlations are flat. The current L0 files have a value of 0 for TARGRADV. I think if these are updated, the high systemic RV can be accounted for. ex: https://jump.caltech.edu/observing-logs/kpf/KP.20231124.16822.76

— Reply to this email directly, view it on GitHub https://github.com/Keck-DataReductionPipelines/KPF-Pipeline/issues/781, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJJHGQYLFDHWQNAMKWQRVDYO3CQ7AVCNFSM6AAAAABB5JBZ4GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DINJZGI2TONI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

howardisaacson commented 8 months ago

Thanks Brad. I think I found that the OB can populate TARGRADV, along with Teff.

Star: T005398 from the OB: RadialVelocity: -10.23 Example of Obs with populated TARGRADV: KP.20240116.53318.31 I did find one example that did not populate TARGRADV: KP.20240116.38119.81

I confirmed for these other two stars that TARGRADV is being populated appropriately.

star 217014 The OB populates the Radial Velocity and it shows up in TARGRADV eg: KP.20240116.22283.38

star: 10700, The OB does not populate TARGRADV KP.20240116.23649.71

On Tue, Jan 16, 2024 at 9:05 PM Brad Holden @.***> wrote:

The FITS header keyword TARGRADV comes from the telescope control system, and not from the kpfconfig service (that is where newer keywords like the GAIA ID come from.) To be filled in, the starlist must include the value. It is possible that the value could be directly written to the dcs service by the observing software. Otherwise, we need a separate way to include that information. I could replicate the keyword but make it part of kpfconfig.

On Tue, Jan 16, 2024 at 10:40 AM Howard Isaacson @.***> wrote:

The star HIP112486 https://jump.caltech.edu/star/hip112486 has a systemic RV of -269 km/s. The result is that the Cross correlations are flat. The current L0 files have a value of 0 for TARGRADV. I think if these are updated, the high systemic RV can be accounted for. ex: https://jump.caltech.edu/observing-logs/kpf/KP.20231124.16822.76

— Reply to this email directly, view it on GitHub https://github.com/Keck-DataReductionPipelines/KPF-Pipeline/issues/781,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAJJHGQYLFDHWQNAMKWQRVDYO3CQ7AVCNFSM6AAAAABB5JBZ4GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DINJZGI2TONI>

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/Keck-DataReductionPipelines/KPF-Pipeline/issues/781#issuecomment-1894948296, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFHJ7GDPNPYLBT6UKGO7LYO5L2HAVCNFSM6AAAAABB5JBZ4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUHE2DQMRZGY . You are receiving this because you authored the thread.Message ID: @.*** com>

--

Howard Isaacson Research Scientist in Astronomy University of California, Berkeley

bjfultn commented 8 months ago

We really want to be populating the TARGRADV since it defines the center of the CCF window and the initial guess for the fits to the CCF. Not having it will have a small, but measurable effect on the RV precision at best, and at worst we'll miss the peak entirely like we did for this star.