Given Robert Lupton's comment I'm more than happy to fix the ENG-R1 – I don't see any reason for us to confuse the gen3 registry by leaving an "r1" band hanging around in there.

John Parejko I'm more than happy for Paul Price to comment but the current situation does not match the comment from him you posted above.

I have no recollection of intentionally special-casing "r1" or "ENG-R1", and it's plausible I just missed it (and miscommunicated with John on that). I think I would have remembered doing it if I did have a good reason, unless it was just out of a no-unnecessary-changes paranoia, which might have been a good reason to leave it "r1" back then, but would not be a good reason to leave it "r1" now.

Nobody's going to be able to come up with a solid answer to NONE vs UNRECOGNI[ZS]ED without digging in and looking at the data that actually uses them, I fear, and I suspect that's not a good use of anyone's time. I'm not sure what to do about that.

Paul Price can you take a quick look?

I do feel that we should match bands so if you object to UNRECOGNISED becoming "unknown" and NONE becoming "empty" then I still think we should unify the band name of "unknown" and "white" to match the recent RFC and obs_lsst.

I can easily change the metadata translator to convert UNRECOGNISED and NONE in the headers (are all those other aliases used in headers?) to unknown and empty but wanted your feedback first.

Seems reasonable to me.

It's possible "Unrecognised" is Subaru's choice of value when the true value isn't available to the header writer, but it's at least equally likely (due to the English spelling) it's something I chose for when we didn't have the filter name in our list. In any case, you should have HSC correspond to other obs packages as much as possible, and we can worry about corner cases if and when they arise.

Okay. Thanks. I will go ahead with modifying the metadata translator to catch the aliases and convert them to standard form.