causes obscure runtime errors when running code from a different location. It also took forever to figure out that we also had to set this config file as smurf2mce.smurf_to_mce_file in the pysmurf config file, since that is how pysmurf knows where to write config info like filter params and the streaming-data filename. Can we figure out a better way to set this config file, which is hopefully shared by the smurf-processor and pysmurf so we don't have to worry about them writing and reading from different places?
jlashner
commented
4 years ago
Currently the smurf.cfg kludge
https://github.com/slaclab/smurf-processor/blob/bfe00ed6f4e1ed9ee629f25a68a79fa1e3076eda/src/smurf_processor.cpp#L537
causes obscure runtime errors when running code from a different location. It also took forever to figure out that we also had to set this config file as
smurf2mce.smurf_to_mce_filein the pysmurf config file, since that is how pysmurf knows where to write config info like filter params and the streaming-data filename. Can we figure out a better way to set this config file, which is hopefully shared by the smurf-processor and pysmurf so we don't have to worry about them writing and reading from different places?