Gp/fix/act flags

[iparask]

This PR makes the glitch path configurable for glitch flags. It assumes that the flags are under a nested path and traverses it based on a separator. This can later be expanded to accept operations over paths.

[mhasself]

I think we need to rethink this -- the additions actually break the abstraction (note the SignalCut inherits from Signal); MLMapmaker caches several Signal objects in self.signals, and loops over them.

So I suspect the right thing to do is have the glitch_flags setting enter through the SignalCut constructor, and be saved as an instance variable.

[iparask]

I moved the path information in the init of the signal classes.

[chervias]

I think going through the Signal objects is fine. We could also go through the init of the MLMapmaker object and pass it there as a "global" parameter that applies to all sub-signal objects included.

[iparask]

I think going through the Signal objects is fine. We could also go through the init of the MLMapmaker object and pass it there as a "global" parameter that applies to all sub-signal objects included.

Included. Also the ACT tod that was causing errors now works.