bayeswave issueshttps://git.ligo.org/lscsoft/bayeswave/-/issues2020-08-13T15:56:04Zhttps://git.ligo.org/lscsoft/bayeswave/-/issues/97Override datafind server for OSG jobs2020-08-13T15:56:04ZJames Alexander Clark PhDOverride datafind server for OSG jobs`bayeswave_pipe` has a hardcoded datafind server (`datafind.ligo.org:443`) whenever the `--osg-deploy` flag is issued. Make this optional.
For that matter, the `--osg-deploy` option should probably be deprecated or just cause the dataf...`bayeswave_pipe` has a hardcoded datafind server (`datafind.ligo.org:443`) whenever the `--osg-deploy` flag is issued. Make this optional.
For that matter, the `--osg-deploy` option should probably be deprecated or just cause the datafind server to default to the one above: there aren't really any functional differences in the submit files any more.James Alexander Clark PhDJames Alexander Clark PhDhttps://git.ligo.org/lscsoft/bayeswave/-/issues/98Bug in reading in BW internal injections from glitch model2021-03-04T00:14:05ZMeg MillhouseBug in reading in BW internal injections from glitch modelWhen doing a BW internal injection using the glitch model (i.e. BW reads in a glitch model chain), bw_pipe tries to read in a old filename format. The `glitch_params_ifo0.dat.0` [here](https://git.ligo.org/lscsoft/bayeswave/-/blob/master...When doing a BW internal injection using the glitch model (i.e. BW reads in a glitch model chain), bw_pipe tries to read in a old filename format. The `glitch_params_ifo0.dat.0` [here](https://git.ligo.org/lscsoft/bayeswave/-/blob/master/BayesWaveUtils/bayeswave_pipe/bayeswave_pipe_utils.py#L521) should be `glitch_params_H1.dat.0` (or H1->L1/V1).James Alexander Clark PhDJames Alexander Clark PhDhttps://git.ligo.org/lscsoft/bayeswave/-/issues/107Make additional checks before deciding run uses simulated data upon seeing '0...2020-12-17T18:46:35ZSudarshan GhongeMake additional checks before deciding run uses simulated data upon seeing '0noise'When bayeswave_pipe sees a `0noise` option in `[bayeswave_options]`, it automatically sets the `sim-data` flag. This can sometimes lead to problems where the intention was to run on frames but the `0noise` option was accidentally left in...When bayeswave_pipe sees a `0noise` option in `[bayeswave_options]`, it automatically sets the `sim-data` flag. This can sometimes lead to problems where the intention was to run on frames but the `0noise` option was accidentally left in. Need to make an additional check, perhaps of the frame-type and channel-type before deciding the run is indeed `sim-data`Sudarshan GhongeSudarshan Ghonge