Skip to content

Timetable for Instrument Demos

Jump to bottom
George Ryall edited this page Sep 22, 2025 · 185 revisions

Wiki > Timetable for Instrument Demos

Group B Timetable - August 2025 Deploy

Feedback from this demos is collated below, along with links to relevant tickets.

Group and Instruments IBEX Demo Team Date/Time Feedback
Disordered Materials: NIMROD, SANDALS DK/IG 10/9 - 1500 Link
Excitations: ALF, LET, MAPS, MARI, MERLIN KB/LC 2/9 - 1045 Link
Industry and Irradiation: CHIPIR JH/GR 1/9 - 0930 Link
Molecular Spectroscopy: OSIRIS, IRIS, IRIS_SETUP, TOSCA, VESUVIO TW/DM 1/9 - 1045 Link
Muons: ARGUS, CHRONUS, EMU, HIFI*, MUSR, MUONFE, RIKENFE, HIFI_CRYOMAG, MUX FA/SC 5/9 - 1500 Link
Support Systems: SELAB, SELAB2, SOFTMAT, DCLAB, DETMON LJ/CMS 3/9 - 1600 No Attendees

Rather than inviting all scientists to the end of sprint demo, a couple of developers will now be demonstrating IBEX to each instrument group separately at a time convenient to them. Such demos will occur in the weeks following an end of sprint and can be tailored for particular instrument interests.

Instrument scientist details for the various groups can be found here if they are not listed then look them up here and support groups here.

Sprint demos will:

  • Illustrate the changes made to IBEX during a sprint to instrument scientists
  • Get feedback on these changes
  • Encourage instrument scientists to share experiences with IBEX, positive and negative, with the IBEX team

There should be two people on each team. Everybody who is part of the IBEX project should always be involved in at least one demo. (See Dev Wiki for more details)

Feedback

Industry and Irradiation

Molecular Spectroscopy

  • Motion Controls: Motion controls are interlocked and cannot run until they’re released – TW suggests to make sure the scripts are loaded, and it should pass pyright.
  • Start-up Speed: Reduce worry (talking about the loading time for server and change in configurations). TW notes that this should be a once a cycle thing. One scientist pointed out it is taking around a minute for the synoptic to update.
  • IBEX Close Window: a pop up was requested to prevent users from exiting IBEX during a run, this pop up should be clear and state that the run will end if they close the application.
  • IBEX Crashing: While loading the graph in logplotter, IBEX crashed but was okay after a reboot. TW suggests that if this was to occur again, please report this issue to Experiment Controls as it would be easier to diagnose the issue.
  • LOGPLOTTER: Changing time scale will give you an approximation, but after a refresh is required. (Scaling can be misleading).
  • Separate Detector (VESUVIO): An additional detector had been purchased and they would like it to be added to IBEX, GR will speak with the group leader regarding prioritising. Captured as ticket.

Excitations

  • Hadn't been aware of the existence of the Moxa View, but had come across and liked it
  • There was mention of a camera on ALF, that the GL will discuss with GR
  • The other items mentioned (MAPS Jaws, FERMI Lift, SKF Chopper) are already on our list
  • There was mention of the rotation stage which can get itself wound up, it was noted that the alarms latching work should mitigate this
  • They are introducting a new mode of working, where they continuously rotate a crystal and want to measure the events, but they were finding the time it takes, especially with a cget() were a little long and they asked if anything could be done to mitigate that. We suggested that they get added to the bluesky list (as the use case sounded like a scan to those present), but that the improvements made to cget should help mitigate things in the short term.

Disordered Materials

  • Script checking is now slower, or appears so. Mentioned twice in meeting.
  • DAE test clock warning is much appreciated as OA has made that mistake previously.
  • SANDALS: would like chopper temperatures from condition monitoring system to be made available in IBEX. DK aware and will follow up.
  • New instrument WebDashboard: blocks expand to full width which makes it difficult to read on large monitors. Would rather have fixed maximum width. Existing ticket here
  • Group has no awkward SE equipment, so no future requests.
  • NIMROD: Would like detector environment monitors to be installed, or if they are already, read by IBEX. JD in DSG is contact, device models are 'DAEMON'.
  • NIMROD: Request to integrate new neutron camera. Existing ticket here

Muons

  • Delay on loading scripts with load_script due to type checking;
    • FA will check with Tom W about caching
    • they want to disable it for script generator generated scrips - they can have a separate load_script command that check for a header and then disabled checking?
  • Question on muon tpar editor. ticket 5081 in review to allow marking as "good" and restore can patch and test on muons
    • they want some way to know if using a non good tpar
    • maybe show last modification date on gui
    • confirm is it version controlled
    • GR to arrange a meeting on tpar files to reach a final set of agreed requirements we can meet and then call this done
  • Riken kicker - Discussion of 8808
  • script server – created ticket 8826 (bug with buttons being small/overlap on screen for certain sized displays)
    • stop button on script server stops current but not all scripts, does script generator keep sending scripts? Behaviour different to stop on script generator
    • There was a question about loops and unrolling – FA thinks this is that each line is an action and the actions may have loops?
    • From script generator not clear if script server (nicos) not running
    • Issue with multiple scripts running - can loadscript warn if script server running/script in progress?
    • follow up meeting to be arranged by GR for script generator
  • HV Caen: FA will install simple view on all muon beam lines. They would be happy with MuSR one for an advanced view, but it needs bit of rework as it uses some horrible db record fanouts

Draft email/meeting invitation

Dear all,

Following the deploy of the latest version of IBEX to your instruments, we would like to schedule a quick meeting to demonstrate the new features of IBEX to you and to gather some feedback. These features are outlined in the release notes here:

  • Insert links to relevant release notes (likely last two)

In particular, this is an opportunity:

  • For us to demonstrate the latest changes in IBEX
  • For you to give us any feedback, good or bad, about IBEX
  • For you to tell us about any new kit or changes to existing kit which may affect the control system
  • For you to ask any questions you might have about IBEX
  • For you to request any new features

It would be useful for at least one representative from each instrument to come to this meeting if possible. Please forward this invitation to anyone who we’ve inadvertently missed or you think should be there.

Thanks in advance,

Insert Hostname(s) here

Previous sprints/releases

After demos are complete update the the previous releases page to reference this as the most recent release and add the demo timetable to it.

Clone this wiki locally