Layout Database for CHIME Outriggers

- Layout Database Overview https://arxiv.org/pdf/1410.8418
[Layout_Database_ARXIV_1410.8418.pdf](https://github.com/chime-experiment/ch_util/files/6004237/Layout_Database_ARXIV_1410.8418.pdf)

- Layout Database Interface: https://bao.chimenet.ca/layout/component.php
- Layout Database file: https://github.com/chime-experiment/ch_util/blob/master/ch_util/layout.py
- Layout Database Naming Convention: https://docs.google.com/spreadsheets/d/1Sn8_ny-i6sJFZybJgQROhPzNQ5hW-YBSkyjylhv3q8A/edit#gid=1807920613
- Allenby Layout DB Issue: https://github.com/chime-experiment/allenby_infrastructure/issues/35
- GBO Layout DB Issue: https://github.com/chime-experiment/GBO_infrastructure/issues/24

Useful existing code bases:

- ch_util: https://github.com/chime-experiment/ch_util (some python code to interface with the layout db; see layout.py)
- ch_www: https://github.com/chime-experiment/ch_www (web php interface code)
- doc_assembly: https://github.com/chime-experiment/doc_assembly (Kiyo's code base use to scan and generate bar codes of components at the CHIME site). Entries are stored in an LTF file, and scanned using an android-based scanner.

Scanner that was used by Kiyo:

HONEYWELL, VOYAGER 1400G, USB SCANNER KIT, OMNI-DIRECTIONAL, 1D, BLACK, USB TYPE A 11.5M STRAIGHT CA (pandemic/legacy model) Kiyo paid $160 CAD, but $250 CAD is reasonable.

In doc_assembly:

- Code in field/: https://github.com/chime-experiment/doc_assembly/tree/master/field - Contains scripts that get run on the tablets in the field. There's different scripts for each field “task” (assembling a cassette, raising a cassette, etc). These produce "ltf" files.

- Code in script/: https://github.com/chime-experiment/doc_assembly/tree/master/scripts - Entries in the "ltf" files get added to the permanent layout database using these scripts.

- Code in single_use/: https://github.com/chime-experiment/doc_assembly/tree/master/single_use - Scripts for creating labels, which Kiyo printed on vinyl at kinkos. To generate the bar codes, the convention is the first 3 characters spec the type of component, after that sequentially. The conventions are quite loose.

- Code in testing_env/: https://github.com/chime-experiment/doc_assembly/tree/master/testing_env - Contains a script to duplicate the whole layout database to a local sqlite. Then you can fiddle with that database without worrying about breaking the main one. (VERY IMPORTANT!)

Suggestion from Kiyo: In the field, you break a USB to mini USB adapter about once an hour… so buy lots of them.