search

XENON1T / pax

The XENON1T raw data processor [deprecated]
BSD 3-Clause "New" or "Revised" License
16 stars 15 forks source link

Custom plugin locations don't work #178

Closed tunnell closed 9 years ago

tunnell commented 9 years ago

In some cases, people have plugins that aren't useful to other people on XENON1T. Specifically, this tends to be people's standalone TPCs. However, specifying plugins via

[pax]
plugin_path = [blah]

Doesn't seem to work because the variable is later overwritten. We should add a test for this. This relates to issues brought up by e.g. @sanderbreur and @ErikHogenbirk about how to store local test TPC information. (I suggest people put it in examples/tpc_name, use --config_path, then add additional plugin search paxes such as plugin_path = ['examples/tpc_name']).

Thanks for @xolotl90 for reporting.

xolotl90 commented 9 years ago

Would we want to prioritize those plugins over the ones in the master branch? Or would we rather want to have a different names for those custom plugins?

JelleAalbers commented 9 years ago

The option is called plugin_paths, and it seems to work. I've added a test in 402b71aecf985ba6b50282daad40d89e96c14cd3.