Conversation
…sses in spartan.yaml new file: ScannerBit/include/gambit/ScannerBit/scanners/diver_1.3.0/diver.hpp new file: ScannerBit/src/scanners/diver_1.3.0/diver.cpp modified: cmake/scanners.cmake modified: config/scanner_locations.yaml.default
modified: ScannerBit/src/scanners/diver_1.3.0/diver.cpp
modified: ScannerBit/src/scanners/diver_1.3.0/diver.cpp
modified: yaml_files/gambit_light_example.yaml
modified: yaml_files/gambit_light_example.yaml
…hich parameters they set, and therefore which parameters need to be specified in order to use theire inverse_transform method. Also updated Diver 1.3 interface to use getSetParameters as a more robust way of checking that the parameters provided by the user as initial guesses are the same as those being scanned. modified: ScannerBit/include/gambit/ScannerBit/base_prior.hpp modified: ScannerBit/include/gambit/ScannerBit/priors/composite.hpp modified: ScannerBit/src/priors/composite.cpp modified: ScannerBit/src/scanners/diver_1.3.0/diver.cpp
|
Thanks @patscott. But other than the changes in |
Yes it is. Ah OK sorry, didn't realise that's how you're managing it. In that case, do you want me to just close this one, and add the changes to |
|
Good plan, let's keep this open until the auto-generated PR is ready to go, and then close it. I'll merge the original GAMBIT PR and run the sync action today. |
|
Now everything from this PR is in master via the auto-generated sync PR, so closing this. |
2 participants
This is the corresponding PR to GambitBSM/gambit#533.
Here I've added an example of the usage of
initial_guessesto thegambit_light_example.yamlfile. Note that to run it, you'll need to switch to diver as the scanner, uncomment the regular priors and comment out the python prior. This is because the custom Python prior precludes the use of the new option, as it relies onprior::inverse_transform, which isn't included in gambit_light for Python priors.