Giordon Stark

They just hate us.

Nope. You can't change existing decorations because they become auxdata in the mini-xAODs. You can add new ones of a different name, but can't change ones set in a previous...

> On a more general basis, what if a user wants to create a mini-xAOD which is augmented with some decorations (e.g., LH ID for electrons...) and then re-run on...

@gfacini The cutflow should be defined in the `xAH::Algorithm` class :) Every algorithm has access to it which means we can declare a static variable and only deal with initializing...

@gfacini That's the point, the algorithms don't need to be told. They can just call specific member functions defined in xAH::Algorithm that does all the lifting. So their job would...

Note that ``` print(ak.Array(np.arange(10)) == ParticleOrigin.SingleElec.value) ``` still works (as in, regular `Enums` are seemingly fine).

@rkrell - I cannot believe I just stumbled upon this. You actually fixed my exact issue I was having where I had an `ARG` before the first `FROM` statement, and...

I have never seen `HistoPath` defined this way. If that's the case, then it's gonna need the ability to split at a colon `:` and then switch out the filename...

This is what I see if I use ``` $ cat config/FitConfig_singlechannel.xml ``` output ```bash $ hist2workspace FitConfig.xml [#2] INFO:HistFactory -- hist2workspace is less verbose now. Use -v and -vv...

It's likely due to the `EMPTY` declarations in the DTD, but this hadn't been an issue in the past as presumably new lines are not considered content... or so I...