Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
Entry  01 Apr 2025, Lukas Gerritzen, Suggestion, Sequencer ODBSET feature requests 
    Reply  01 Apr 2025, Lukas Gerritzen, Suggestion, Sequencer ODBSET feature requests 
       Reply  01 Apr 2025, Stefan Ritt, Suggestion, Sequencer ODBSET feature requests 
    Reply  01 Apr 2025, Stefan Ritt, Suggestion, Sequencer ODBSET feature requests 
    Reply  01 Apr 2025, Konstantin Olchanski, Suggestion, Sequencer ODBSET feature requests 
       Reply  01 Apr 2025, Pavel Murat, Suggestion, Sequencer ODBSET feature requests 
          Reply  02 Apr 2025, Konstantin Olchanski, Suggestion, Sequencer ODBSET feature requests 
             Reply  02 Apr 2025, Stefan Ritt, Suggestion, Sequencer ODBSET feature requests 
    Reply  07 Apr 2025, Zaher Salman, Suggestion, Sequencer ODBSET feature requests 
       Reply  07 Apr 2025, Stefan Ritt, Suggestion, Sequencer ODBSET feature requests 
Message ID: 3026     Entry time: 07 Apr 2025     In reply to: 3013     Reply to this: 3027
Author: Zaher Salman 
Topic: Suggestion 
Subject: Sequencer ODBSET feature requests 

Lukas Gerritzen wrote:

I also encountered a small annoyance in the current workflow of editing sequencer files in the browser:
  • Load a file
  • Double-click it to edit it, acknowledge the "To edit the sequence it must be opened in an editor tab" dialog
  • A new tab opens
  • Edit something, click "Start", acknowledge the "Save and start?" dialog (which pops up even if no changes are made)
  • Run the script
  • Double-click to make more changes -> another tab opens
After a while, many tabs with the same file are open. I understand this may be considered "user error", but perhaps the sequencer could avoid opening redundant tabs for the same file, or prompt before doing so?

Thanks for considering these suggestions!


The original reason the restricting edits in the first tab is that it is used to reflect the state of the sequencer, i.e. the file that is currently loaded in the ODB.

Imagine two users are working in parallel on the same file, each preparing their own sequence. One finishes editing and starts the sequencer. How would the second person know that by now the file was changed and is running?

I am open to suggestions to minimize the number of clicks and/or other options to make the first tab editable while making it safe and visible to all other users. Maybe a lock mechanism in the ODB can help here.

Zaher
ELOG V3.1.4-2e1708b5