Lukas

Hello -- just commenting here as well to share our science use-case. "Black box" functions that are expensive to evaluate are a common setup in optimization problems. Often a machine-learning...

Hi -- I think a callback would work equally well. definitely not a hard requirement. Are you thinking one call back for all function calls (where the callback specifies some...

yes, if we could read workspaces and run fits, that would be quite helpful. To give you a feel, this is a not-so-minimal example of running it via PyROOT https://gist.github.com/lukasheinrich/4afa0159fd3f3f51620b12e66abbdf08...

calling a docker image that was built for everware e.g. via `remotedocker cranmer/everwarewithgeorge bash` already gives you a nice shell with the `Welcome to everware` message. But this currently needs...

it would be great if this would somehow natural support developing a container in multiple sessions. i.e under the hood some cycle of docker pull/attach/save/tag/push which might be a bit...

yeah something like give back the user an session ID (could be straight up the container ID, or for security something else) and allow the user to attach/detach/save. What's the...

hi @AkihiroSuda - do you have any guidance on this. If so that'd be much appreciated!

Thanks @AkihiroSuda ! @anthonyhartin - were you able to try this?

I'm reactivating this based on the recent #1625 PR. The goal is to make this fucnttion diffable (and removiing the `.tolist()` calls. ```python def makeit( pars, nominal, uncorr_data, corrup_data, corrdn_data,...

would you say `model.config.par_slice("staterror_Signal_region[0]")` is better than `model.config.par_slice("staterror_SR")[0]` is bette thann and if so .. should we also allow slices? `model.config.par_slice("staterror_Signal_region[0:2]")`