channel_completion issueshttps://git.ligo.org/cds/software/channel_completion/-/issues2019-01-23T03:37:45Zhttps://git.ligo.org/cds/software/channel_completion/-/issues/1encode default path for channel list2019-01-23T03:37:45ZJameson Rollinsjameson.rollins@ligo.orgencode default path for channel listIt would be very convenient if the ligo_channel_completion binary would recognize default paths to the channel list database if the CHAN_LIST environment variable is not defined. That would make it much easier for administrators to just...It would be very convenient if the ligo_channel_completion binary would recognize default paths to the channel list database if the CHAN_LIST environment variable is not defined. That would make it much easier for administrators to just drop the channel list into a known location and have it Just Work. Maybe the ordering should be something like:
```
CHAN_LIST
~/.cache/ligo-channel-list/chan-list.txt
/var/cache/ligo-channel-completion/chan-list.txt
```https://git.ligo.org/cds/software/channel_completion/-/issues/2include script to build channel list2019-01-31T00:27:55ZJameson Rollinsjameson.rollins@ligo.orginclude script to build channel listMaybe there's not a good way to do this generically, but we might be able to cover most cases with a script that just does the following:
```
#!/bin/bash -x
nds_query \
-n nds.ligo.caltech.edu \
-l -t raw '*' \
| tail -n +3 ...Maybe there's not a good way to do this generically, but we might be able to cover most cases with a script that just does the following:
```
#!/bin/bash -x
nds_query \
-n nds.ligo.caltech.edu \
-l -t raw '*' \
| tail -n +3 \
| awk '{print $1}'
```https://git.ligo.org/cds/software/channel_completion/-/issues/3support executable installed in incorrect location2019-02-08T21:03:17ZMichael Thomassupport executable installed in incorrect locationOn Redhat-based systems, support programs (ie ligo_channel_completion) should be installed in /usr/libexec, not /usr/lib.On Redhat-based systems, support programs (ie ligo_channel_completion) should be installed in /usr/libexec, not /usr/lib.https://git.ligo.org/cds/software/channel_completion/-/issues/5add support for nds_query2019-02-13T19:13:03ZJameson Rollinsjameson.rollins@ligo.orgadd support for nds_queryShould complete for channel.Should complete for channel.https://git.ligo.org/cds/software/channel_completion/-/issues/6Feature request: read from stdin2019-02-15T21:53:36ZMichael ThomasFeature request: read from stdinIt would be handy if ligo_channel_completion could operate in a pipeline on the command line. Specifically, allow it to take a list of channels from stdin:
nds_query -1 -n l1nds0 -p 8088 -l | awk '/:/ {print $1}' | /usr/lib/ligo_chann...It would be handy if ligo_channel_completion could operate in a pipeline on the command line. Specifically, allow it to take a list of channels from stdin:
nds_query -1 -n l1nds0 -p 8088 -l | awk '/:/ {print $1}' | /usr/lib/ligo_channel_completion > /opt/rtcds/llo/l1/cds/l1daqchannels.txthttps://git.ligo.org/cds/software/channel_completion/-/issues/7bash completion prevents completion of paths2021-10-28T17:00:46ZJameson Rollinsjameson.rollins@ligo.orgbash completion prevents completion of pathstools like ndscope support both channels and file paths as arguments, but it looks like the existing bash completion support does not support path completion. The completions should support paths as well as channels.
See https://git.li...tools like ndscope support both channels and file paths as arguments, but it looks like the existing bash completion support does not support path completion. The completions should support paths as well as channels.
See https://git.ligo.org/cds/ndscope/-/issues/151