snoplus/tellie

The timing ELLIE LED calibration system

tellie's Issues

Temperature probe select on fake_gui

Add temperature probe select on fake_gui.

Set default values based on channel (produce map)

Add multiple channel option to fake_gui.py

Change fake_gui so it can fire multiple channels

Develop Default Run Setting

Store in database. Vague structure to be devloped so far is:

Pattern Documenent:
sub run #: fibre map->(ID,Wavelength, Time Profile ..)

Run Document:
Pattern #
Sub Run #:
PIN readings
Settings: IOP, IPW, Rate, Number of pulses

Event Data Structure (NOT IN DB)
Pattern #
Subrun #

Set up Database

Set up a database on snopl.us and test it

Investigate PIN behaviour when switching channels

Some weird behaviour was seen when switching channels UG using the Python scripts, the PIN response did not update. This was usually noticed by a significantly lower RMS (e.g. ~140). It seemed to have to do with switching boxes. It may be possible to test this on the test bench, although this will be tricky. I don't think this has been observed when pulsing via ORCA.

If nothing else, this should be put in the TELLIE hardware documentation ("known quirks and behaviours").

Temperature probe averaging

Boards near good temperature probes should use the closest 2 probes and average over them.

If near bad temperature probe just use the closest working one

Fix PIN readout on fake_gui.py

At the moment pin is returned in the form {chan:"{chan:PIN}"} change this to {chan:PIN}

External Triggering

Ensure full sequence ran before PIN is read out.

Work out what to do about run boundaries

Check bad temperature probes cannot be selected

Test with boards and fix if the bad temperature probes are being selected.

Bad temperature probes should be noted in the code somehow to ensure they are not used again. Use the next nearest probe.

There is one bad temperature probe in TELLIE. Unknown location currently. Can also test with disconnected AMELLIE probes.

Slave mode will not fire when server is re-launched

Currently if the server is relaunched TELLIE will not fire light when requested in slave mode. There is a work around whereby the user can first request a sequence in master mode, then switch into slave mode.

Ideally this should be resolved in the PIC code.

In the mean time I recommend appending the server script to fire a single shot in master mode before launching. @Mark--S

Admin rights on this repo

It seems like we have no more active admins on this repo - could @mastbaum or @EdLeming please add the current TELLIE experts as admins? That would be Martti and Michal...

Pin read from averaging mode: undefined behaviour

Firing in sequence mode and then reading the pin before the sequence is complete is currently allowed. This should not be possible; the pin diode readout may not actually be the averaged reading (undefined behaviour). Two updates are needed:

• Wait until sequence is complete and then read; if reading taken before end of sequence then an invalid flag should be applied to the pin reading.
• Character should be flushed to buffer following completed sequence (firing via "g" command), only then should pin average commands be sent.