/
Etalon Software Description

Etalon Software Description

The software running on the kpfetalon machine is not part of a Keck standard KROOT deployment and does not directly provide KTL keywords. Instead, scripts run which populate a redistribution database and a keyword service running on kpfserver reads that database and provides KTL keywords.

Restarting the Software on kpfetalon

To restart the scripts which populate the redis database:

  • Log in to kpfetalon as kpfdev@kpfetalon

  • Run byobu to connect to an existing session or start a new one.

    • You can toggle through byobu terminals using F3 and F4 function keys and create a new one using F2. Exit byobu (which leaves the scripts running) using F6.

    • You will need 2 byobu terminals as two scripts need to be run.

  • In the first byobu terminal:

    • cd ~/Repos/slice-qtc/

    • python kpf_vescent_external.py

    • You should see csv formatted lines start to print to the terminal.

  • In the second byobu terminal:

    • cd ~/Repos/slice-qtc/

    • python kpf_vescent_internal.py

    • You should see csv formatted lines start to print to the terminal.

  • Exit byobu using F6.

Changing Temperature Set Points

Changing the temperature set points requires calling some of the python functions directly.

  • Log in to kpfetalon as kpfdev@kpfetalon

  • cd ~/Repos/slice-qtc/

  • python

  • In python:

    • from slice import slice v1 = slice.Slice('/dev/vescent1') v2 = slice.Slice('/dev/vescent2') v2.ch3.TempSet = 25 v1.ch2.TempSet = 24.8 v1.ch3.TempSet = 24.6 v1.ch4.TempSet = 24.9

Substitute set point values as appropriate.

Double check that the scripts polling the temperatures are still running in the byobu instance. If you query the temperature directly in python (e.g. using print(v1.ch3.Temp)) it may kill the polling script needed for the redis database and KTL keywords to get populated.