Initilizing yamls with yamls in the directory copies the old ones to _default which is confusing

ld-cd commented 3 months ago

Generating XKID yamls generates MEC yamls as well...

!?yamlgen ~/Workspace/research/MKIDPipeline> diff pipe.yaml pipe_default.yaml
5a6
>   filter_cutoff_min: 950
7,8c8,9
<   nominal_platescale_mas: 10.4
<   device_orientation_deg: 0.0
---
>   nominal_platescale_mas: 10.05
>   device_orientation_deg: -43.24
10c11
<   name: XKID
---
>   name: MEC
29,31c30,32
<     /Users/aled/Workspace/research/MKIDPipeline/.venv/lib/python3.12/site-packages/mkidcore/xkid.bmap
<   nrows: 125
<   ncols: 80
---
>     /Users/aled/Workspace/research/MKIDPipeline/.venv/lib/python3.12/site-packages/mkidcore/mec.bmap
>   nrows: 146
>   ncols: 140

ld-cd commented 3 months ago

Never mind this is a bug in my test

ld-cd commented 3 months ago

Actually this behavior is confusing

MazinLab / MKIDPipeline

Initilizing yamls with yamls in the directory copies the old ones to _default which is confusing #105