Phase out use of observationlist.yaml (?) about mirage HOT 2 CLOSED

The motivation behind using the observation list yaml file was for cases where there are multiple filter pairs within a given observation, implying that the user would want to use multiple point source (or galaxy, or extended) catalogs within that observation. Using the observation list yaml file was the only way I could think of to be in this situation and still allow the simulator yaml files to be produced in an automated way with the correct catalog names. Have you been able to create input yaml files for this case without using the observation list?

from mirage.

Ah, I see! No, I've only been running things in the F212N and F480M bands, since those are the bands that will be used for basically all of commissioning. So I've only ever had two catalog files (SW and LW) per observation.

Then I will leave the observation list as it is. If I happen to think of a way to easily incorporate different catalog files within the same observation (which I kind of doubt), I'll come back to it.

Thanks for pointing this out!

from mirage.