Re-enabled fpeak analysis with updated file transfers
BNS postmerger fpeak analysis disabled during file transfer tests. This MR should re-enable fpeak analyses.
If a section [bayeswave_fpeak_options] is added to the config.ini for bayeswave_pipe, the workflow contains a BayesWavePost job whose parent is BayesWave and has any additional options specified in that new section.
NOTE to @katerina.chatziioannou: this has not been tested; I highly recommend testing before merging.
Merge request reports
Activity
@james-clark if the config has
[bayeswave_fpeak_options]then you mean the workflow has theBayesWaveFpeakjob right?
(this is a minor change from before where you had to do
[bayeswave_fpeak_options] fpeak-analysis=to enable it. Now just adding that section will activate the job.)
I also just realised you need:
[engine] bayeswave_fpeak=/path/to/executableAnd it'll throw what's probably a pretty inscrutable error if it's not there. I'll update that with something more user friendly.
Great! I tried testing this but it looks like the fpeak part was not actually run.
I used the following config (full file at
/home/marcella.wijngaarden/Projects/PostMergerBursts/analysis/Test/6xDS_fpeak/compEoS5_1221525/config.ini):[engine] bayeswave=/home/marcella.wijngaarden/opt/bayeswave/bin/BayesWave bayeswave_post=/home/marcella.wijngaarden/opt/bayeswave/bin/BayesWavePost bayeswave_fpeak=/home/marcella.wijngaarden/opt/bayeswave/bin/BayesWaveFpeak ... [bayeswave_fpeak_options] suppress-inspiral= srate=16384 flow=512[](url) fpeakmin=1500 fpeakmax=4000 threshold= 0noise=Resulting in this shell script with the jobs submitted to condor (which includes BayesWaveFpeak): compEoS5_1221525.sh.
It looks like the fpeak part was not run because no output from that part was created (i.e., no log or out files). Is there something I am still missing in how to execute this? The other parts of the job (BayesWave, BayesWavePost did run as expected, see e.g. results at: https://ldas-jobs.ligo.caltech.edu/~marcella.wijngaarden/Projects/PostMergerBursts/compEoS5_1221525/bayeswave_fpeak/)
@james-clark any clues about this?
