Ranking plot making job stability #441
-
Hi, I am making ranking plots, but the job to make a runking plot is not so stable, it fails frequently. Is there any reason of instability, and is there any way to improve the stability? Best Regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Hi Tomoya, the current ranking interface unfortunately does not provide too much control. Just to make sure I understand the setup correctly:
means presumably that you only add some systematics to your workspace? Or are you dynamically disabling them by setting the parameters to constant? Or do you have some other method here?
I guess the part that fails are the fits here? Unfortunately there is currently no protection built-in against this. That is something that needs to be improved, the easiest solution might be to catch a failed fit and to just return a If you're looking to do this with >100 parameters, the next thing that needs to be improved is parallelization: currently all fits run sequentially, which will become very slow. I think a solution similar to #421 makes sense. This requires a bit of work (probably not all that much actually) and there is a bit of a backlog of open pull request to get through, so it might take me a bit to get to implementing this (contributions are very welcome though if anyone wants to give this a try). |
Beta Was this translation helpful? Give feedback.
Yes, the
max_pars
option does that, see https://cabinetry.readthedocs.io/en/latest/api.html#cabinetry.visualize.ranking.Not currently. #342 adds something like this for pulls, which could also be applied to correlations. At the moment the way to accomplish this is to pass a modified
FitResults
object intovisualize.correlation_matrix
. Here's an example: