Added getacqinfo / getfileinfo functions for HFB acquisitions.

[james-s-willis]

No description provided.

[james-s-willis]

@ketiltrout is there a way to test this before merging?

[ketiltrout]

There seems to be confusion here over whether HFB files are corr files or something new.

You're adding entries to CorrAcqInfo here but over in chime-experiment/chimedb_di#14 you've defined new HFB-specific tables.

So, definitely step one is to figure out whether HFB files are corr files or not.

If they're not, you'll also need to define them in the acq_format file before this PR can be approved. The TeX for that is over here and the document provides instructions on the procedure for updating itself: https://github.com/chime-experiment/ch_memos/blob/master/acq_format/acq_format.tex

The PDF version of the acq format document is in doclib: https://bao.chimenet.ca/doc/documents/5

[jrs65]

@james-s-willis as Don says you'll also need to create a new hfb acq type for this. The corr acq type is to hold visibility correlation (which these are not).

[james-s-willis]

alpenhorn/alpenhorn/auto_import.py

Line 589 in 2796cfd

if not file.corrinfos.count():

I know I'm not editing this part, but shouldn't this line have file.hkinfos.count() instead of corrinfos? @ketiltrout

[james-s-willis]

@ketiltrout, @jrs65 I have updated this PR with your corrections and I have created a new PR (https://github.com/chime-experiment/ch_memos/pull/4) for the HFB acq type in the CHIME Archive Data Format document.

[ketiltrout]

I know I'm not editing this part, but shouldn't this line have file.hkinfos.count() instead of corrinfos? @ketiltrout

More amazingness from this code. You're right, and I made an issue for it, but really it looks like that if should be deleted and the except line above should be fixed so it only catches the exception thrown if the update fails, not everything.