Skip to content

MUON Instrument Notes

Jump to bottom
Adrian Potter edited this page Feb 5, 2018 · 2 revisions

MUON Instruments Notes

Introduction

The following notes are simply a collection of notes and points that need to be considered when planning the migration of MUON instruments to IBEX. As the points listed below are addressed and the instruments migrated, these notes will become redundant.

Notes

Muon instruments can be thought of as comprising a mix of "normal" devices and "specialist" equipment.

  1. The Muons team have often written their own LabVIEW VIs to support "specialist" equipment. These VIs usually have their own LabVIEW GUI screens.
  2. There might also be additional LabVIEW VIs, written by the instrument scientists, which do not fall within the scope of SECI (i.e. are not in SourceSafe, are not in LabVIEW/Modules). Most likely to find such VIs on HIFI, but may also find them on MUSR & EMU.
  3. Muon instruments use the ISISCP in a different way. Need to discuss with Freddie to understand how. The difference may arise via custom features of OpenGENIE. Do these need to be replicated in genie_python?
    • ISISICP: BEGIN command
    • may only affect the BEGIN command in OpenGENIE (i.e. when using command console; DAE UI might behave as normal)
    • user gets asked some extra questions when using BEGIN command on muon instruments
    • there might be other "special" OpenGENIE commands for Muons
  4. Muon instruments have their own ScriptBuilder (originally written by Matt Clarke in C#). Need to consider the extent to which the existing ScriptBuilder meets the needs of the Muons group.
  5. Muon instruments use Beam Cameras (scintillating material which flashes when stuck by a muon - conventional camera collects the light flash). use for "spot" finding (i.e. the "spot" is the beam). Could create an EPICS driver (areaDetector), could lvDCOM or could run "stand-alone".
  6. MUSR can operate in one of two modes: Transverse or Longitudinal. Needs a setup script to put the machine in the relevant mode. KVLB wrote the current script to switch modes. Are separate config files also needed?
  7. There is an additional Control PC: NDXMUSR_SETUP, which is used to setup & prepare Cryogenics samplesw.
  8. Muons use several different types of DANFYSIK PSU. Each type of device probably has its own VI/UI. Need to check out which device use which VI/UI. May need to create several different types of OPI (but , ideally, only one IOC).
  9. Muon devices like to share each others PVs (e.g. MUONFE), because they share magnets. Should be do-able as Blocks.
  10. Specialist Equipment:
    • RF equipment: has its own collection of VIs (ask Gareth).
    • NMR & Lasers (used on HIFI, VIs are stored on HIFI)
      • NMR is from a 3rd party system (was provided with LabVIEW drivers)
    • "zero" field system - feedback system used to mantain a constant magnetic field
      • Uses cDAQS And Kepcos
  11. May need to consider moving all 3 muon instruments simultaneously.
  12. MUSR may be upgraded in 2018? or 2019?
  13. There are 2 SECI instruments on the RIKEN beamline - ARGUS & CHRONUS.
    • these interact with the RIKEN control system
    • consider migrating these as the RIKEN beamline evolves
    • don't need to migrate these two at the same time as other muon instruments.
Clone this wiki locally