Today I tested the new version of the SEI configuration Guardian code. The old version was a product of Jim and I testing out how it should be done over the last year and half or so. This meant that the code was not organized, was not general, and honestly a bit hacky. A few key differences between this version and the old:

• Blends and sensor correction will be split into two separate nodes.
  • This cleans everything up and really helps simplify how/when the SC can be changed.
• Most of the states and edges are now auto-generated from a single configuration file.
  • The user can simply change the name of configurations, filter banks, filters, etc. in the file and then load the node. No editing of code necessary. This is very similar to how the rest of the SEI Guardian code is written. I tried to stay consistent at least.
• Allows for two different ways to switch sensor correction.
  • We do it slightly different compared to how LLO wants to do it, so I wrote both in.

I only had enough time to test out the sensor correction code before I had to hand it over to Hang and TVo, so I will have to test out the blend code another time. The blend code is much the same as before, besides the state and edge generation which is the same as for SC (tested good), so I think the testing should be fast. Until I test the blend code, I will not be able to implement the new nodes since the old configuration Guardians control both blends and SC. When it is time to implement the new stuff, I will have to change out all of the HAM SC nodes, stage 1&2 blends and SC for all BSCs, and then change the manager to have the new names. This will take a bit of time and I'll think about how I can speed up the process soI don't tie up the IFO in the future.

Moral of the story is: I tested most but not all of the new SEI configuration Guardian code, and everything was put back to how it was previously.