Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  22 Nov 2023, Pavel Murat, Forum, run number from an external (*SQL) db? 
    Reply  22 Nov 2023, Ben Smith, Forum, run number from an external (*SQL) db? 
    Reply  22 Nov 2023, Stefan Ritt, Forum, run number from an external (*SQL) db? 
       Reply  01 Dec 2023, Pavel Murat, Forum, run number from an external (*SQL) db? 
          Reply  02 Dec 2023, Stefan Ritt, Forum, run number from an external (*SQL) db? 
             Reply  02 Dec 2023, Pavel Murat, Forum, run number from an external (*SQL) db? 
                Reply  03 Dec 2023, Pavel Murat, Forum, run number from an external (*SQL) db? 
                   Reply  04 Dec 2023, Stefan Ritt, Forum, run number from an external (*SQL) db? 
                Reply  04 Dec 2023, Stefan Ritt, Forum, run number from an external (*SQL) db? 
Message ID: 2643     Entry time: 04 Dec 2023     In reply to: 2640
Author: Stefan Ritt 
Topic: Forum 
Subject: run number from an external (*SQL) db? 
> - how does one communicate with an external shell script from MSL ? I looked at the MIDAS Sequencer page 
>   
>   https://daq00.triumf.ca/MidasWiki/index.php/Sequencer
> 
>   and didn't find an immediately obvious candidate among the MSL commands. 
>   The closest seems to be 
> 
>   'SCRIPT script [, a, b, c, ...]' 
> 
>   but I couldn't easily figure how to propagate the output of the script back to MIDAS. 
>   Let say, the script creates an ASCII file with the next run number. What is the easiest 
>   way to import the run number into ODB? - Should an external script spawn a [short-lived] 
>   MIDAS client ?  - That would work, but I'm almost sure there is a more straightforward solution. 

The output of the SCRTIP command is stored in the variable $SCRIPT_RESULT. Please pull midas to get this
new functionality.

Stefan
ELOG V3.1.4-2e1708b5