Add 'getPathForPython'
parent
df8ad39131
commit
2eb1ab0add
27
getPathForPython.md
Normal file
27
getPathForPython.md
Normal file
@ -0,0 +1,27 @@
|
||||
This script is a helper function for the python scripts. It loads the hardcoded paths from [[Paths.hpp|Paths.hpp]] and returns them as a string based on the specified options.
|
||||
|
||||
First, compile the script to be a standalone executable that can be called by pyhton:
|
||||
```
|
||||
g++ getPathForPython.cc `root-config --libs --cflags` -o getPathForPython
|
||||
```
|
||||
|
||||
The executable takes arguments in this order
|
||||
* command (can be either "input", "BDTinput", "inputBkg" or "BDToutput"
|
||||
* year
|
||||
* Run
|
||||
* magnet ("down", "up", "both")
|
||||
* Preselected (1 or 0)
|
||||
* MC (1 or 0)
|
||||
* ReferenceChannel (1 or 0)
|
||||
* PHSP (1 or 0)
|
||||
* KshortDecayInVelo (1 or 0)
|
||||
* Selection (not used anymore)
|
||||
* UseLowQ2Range (1 or 0, effectively obsolete)
|
||||
|
||||
|
||||
So to get the path of the **todo** test signal MC 2011 sample, magnet down, after the MVA selection, do
|
||||
```
|
||||
getPathForPython "BDToutput 2011 1 "down" 1 1 0 0 0 0 0
|
||||
```
|
||||
|
||||
The executable returns 0 if everything is okay, 1 if something fails. Which is the standard actually.
|
Loading…
Reference in New Issue
Block a user