NeXus workflow: Why the name `FrameMonitor`?

[nvaytet]

Stupid question: where did the name "frame monitor" come from?
In the nexus types, we have FrameMonitor0-3, but a more common name (at least when talking to scientists) seems to be "beam monitor".

Should we rename FrameMonitor to BeamMonitor?

[jl-wynen]

It comes from BIFROST. I think we can remove it here since we are now able to define custom monitors in the subpackages.

[nvaytet]

Does this mean we should also remove things like ScatteringRunType (which doesn't seem to be used in any downstream packages: https://github.com/search?q=org%3Ascipp%20ScatteringRunType&type=code).

And maybe also:

• EmptyBeamRun (from sans)
• VanadiumRun (from powder)
• TransmissionRun (from sans)
• CaveMonitor (from dream)
• IncidentMonitor (from sans)
• TransmissionMonitor (from sans)
  ?