Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »


Table of Contents:


Relevant Devices

Description

Qty

Source

Part Number


Relevant Functional Block Diagram


Software Actions

Action

Notes

1

2

3


Required Adjustable Settings

Setting

When Needed

Notes

Build

Observing

Maintenance


Required Telemetry

Parameter

Report Frequency

Purpose

Notes

1

f_rep

Used to define comb output frequencies

2

f_0

Used to define comb output frequencies

3


Required Alarms

Parameter

Threshold

Notes

1

2


Relevant Datasheets & Manuals

Description

File

Source

1

XML Manual

Should be supplied by Menlo

2


Relevant Software

From Sam:

“Hi Steve,

We will need to query the LFC desktop for (at least) two pieces of telemetry -- f_rep and f_0, which fully define the output frequencies of the comb. These need to be saved in each FITS header to derive the absolute wavelength solution and also tell the act as a flag for whether or not the comb is locked. There are also a few other health-check metrics that can be stored, such as the comb lock status. 

For NEID, I believe the Astrocomb computer is queried via XML to send a set of telemetry values, which the NEID server then stuffs into the FITS header of the observation. I'm not too familiar with this telemetry handoff (sorry), but there is a specific manual that we will get with the comb delivery that outlines the command protocols and query-able data products.

Is that what you were asking? I can also see if I can find the NEID LFC XML manual, if this would help give a sense of the complexity.

Sam”

  • No labels