Search results

Edit-on-sequence parameters are displayed ([[#Figure_1|Figure 1]]) when the {{Button|name=Start Script}} button is pressed. ...dit-on-sequence parameters are displayed for editing in [[#Figure_1|Figure 1]] below.

$| = 1; my $ls = `$cmd 2>&1`;

<table align="center" border="1"> <td>1</td>

An example of the Config page is shown in Figure 1. [[File:config_page.png|thumb|left|Figure 1 Example of Configure Page]]

Create database BOOL 1 4 27s 0 RWD n Write data BOOL 1 4 27s 0 RWD n

Create database BOOL 1 4 27s 0 RWD n Write data BOOL 1 4 27s 0 RWD n

Write data BOOL 1 4 >99d 0 RWD n filename STRING 1 80 >99d 0 RWD runlog.log

Name STRING 1 32 1h 0 R ODBEdit Host STRING 1 256 1h 0 R dasdevpc2.triumf.ca

...p:R]Channels>copy 0 1 <<< Duplication of channel 0 to channel 1 <br> [local:deap:R]Channels>cd 1/settings

...tyle="color: sienna;">TID_DWORD </span> four bytes 0 2**32-1 ...yle="color: sienna;">TID_INT</span> signed DWORD -2**31 2**31-1

An example of the Help page is shown in Figure 1. [[File:help_page.png|thumb|left|Figure 1 Example of Help Page. Click on thumbnail to enlarge]]

<table border="1"> 1, /* TID_BYTE unsigned byte 0...

Enable localhost port BOOL 1 4 12m 0 RWD y localhost port INT 1 4 12m 0 RWD 8080

State INT 1 4 2h 0 RWD 3 Online Mode INT 1 4 2h 0 RWD 1

Alarm system active BOOL 1 4 4h 0 RWD y Active BOOL 1 4 >99d 0 RWD n

-l # : display # events (look 1) ------------------------ Event# 1 --------------------------------

The Chat Page (Figure 1) is displayed by clicking on the {{Button|name=Chat}} button on the {{Util The Chat page (Figure 1) is composed of 4 areas:

...n requires the index format to be present (see [[#1.Asynchronized|example 1]]). === 1.Asynchronized ===

-rw-r--r-- 1 mpet users 0 Nov 20 14:44 .ODB.SHM 1: "npet" <-- selected experiment

New File BOOL 1 4 5h 0 RWD n Path STRING 1 256 5h 0 RWD /home/cdms/packages/SuperCDMS_DAQ/MidasDAQ/online/s

An example of the Message page is shown in Figure 1. [[File:message_page.png|thumb|left|Figure 1 Example of Messages page for an experiment, Click to enlarge]]

...st time the button is pressed, the Sequencer Page will appear as in Figure 1, where no load file has been specified. ...t-align: left; width: 100%; background-color: rgb(255, 255, 255);" border="1" cellpadding="2" cellspacing="2"

[[File:programs_page.png|thumb|left|Figure 1: Programs page example]] The Programs page (Figure 1) presents the current active list of the clients attached to the given expe

...age|usage]]). An example of the status page is shown in [[#Figure 1|Figure 1]]. By default, anyone can access the experiment via the web. <div id="Figure 1"></div>

Pwd STRING 1 32 31h 0 RWD Comment STRING 1 32 31h 0 RWD SCBs

...ontend]] program and [[mlogger]], which also allocate buffer space to hold 1 event of maximum size. GBytes, set ODB MAX_EVENT_SIZE to 1 Gbyte, and in theory, you should be able to

LoggerHistoryChannel STRING 1 32 24h 0 RWD DisableTags BOOL 1 4 1h 0 RWD n

Figure 1 shows examples of the Start page with and without [[Edit-on-start Paramete |+ Figure 1 Start Page

...l be visible as key-links (i.e.links to a key) ([[#Example ODB Page|Figure 1]]). [[File:alarms_page_untriggered.png|thumb|left|Figure 1: Alarms page example]]

=== Example 1 - The /elog tree === Display run number BOOL 1 4 17m 0 RWD y

[[File:Deap_mscb.png|thumb|left|Figure 1: Example of a MSCB page]] The MSCB page (see Figure 1) displays information from the [[/MSCB ODB tree]]. It obtains a list of all

1. Environment variable [[Compilation & Build #MIDAS_DIR|MIDAS_DIR]] if defi

Epics INT 1 4 25h 0 RWD 3 [1] GPS:VAR2

...; background-color: mintcream; font-size: 110%; font-style:bold;> Figure 1: Structure of MIDAS event showing Event and Bank headers with data banks.< ...: the @ref FE_tbl_Event ID "eventID" describes the type of event. Usually 1 is used for triggered events, 2 for scaler events, 3 for HV events etc.

...: Format of odb file name (''run%05d.odb'' by default) '''see Note 1''' <dt>Note 1</dt>

...ber|run number]] of the upcoming run will be displayed for editing (Figure 1). |+ Figure 1: Run start with no edit-on-start parameters defined

Execute on start run STRING 1 256 18h 0 RWD /home/bnmr/online/bnmr/bin/at_start_run.csh Execute on stop run STRING 1 256 18h 0 RWD /home/bnmr/online/bnmr/bin/at_end_run.csh

Maintain free space(%) INT 1 4 3m 0 RWD 0 Stay behind INT 1 4 3m 0 RWD -3

[[File:odb_page.png|thumb|left|Figure 1: ODB Page example]] ...l be visible as key-links (i.e.links to a key) ([[#Example ODB Page|Figure 1]]).

mh2sql --hs-debug 1 --sqlite . 130813.hst

...: Keep lazylogger copying runs with run# - "stay behind" (ex: 1) ...ion : Enable multiple lazy on same source. Ex: 3ch : 3.0, 3.1, 3.2

1. If environment variable [[Compilation & Build #MIDAS_DIR|MIDAS_DIR]] is de

...or graph or histogram if several are used. 0 is completely transparent and 1 is opaque. ...ng to next Y index", e.g. (0,0), (1,0), (2,0), (1,0), (1,1) .... (3,0), (3,1), (3,2).

Event ID WORD 1 2 9h 0 RWD 3 Trigger mask WORD 1 2 9h 0 RWD 8

1 Core system : Core functionalities * [[1 Core]]

Control STRING 1 256 1h 0 RWD /home/expt/online/custom/control.html valve.png! STRING 1 256 1h 0 RWD /home/expt/online/custom/valve.png

** /path/array[*] -> index=-1 ...ll subkeys are enumerated and passed to output_key() with "index" set to "-1". Output for all subkeys is concatenated without any separators.

[[File:History main page.png|thumb|left|Figure 1: Example of a History Page]] Figure 1 shows the History Page from the agmini experiment. This page shows the pane

...om-button, the contents of this key is interpreted as HTML content. Figure 1 shows an internal custom page which has been imported into the ODB at key < | [[File:Mhcustom1.gif|thumb|left|Figure 1: Internal Custom Page example]]

chart-interval: 1.000 id_char: 1

File:gstripchart1.jpg|Figure 1:<br>gstripchart display with parameters and data pop-up.

[-n 0|1|2] Encoding: 0:ELcode,1:plain,2:HTML

* STATE_STOPPED 1 * TR_START 1

| [[File:Elog_initial.png|thumb|left|Figure 1: Initial ELOG Page example]] is pressed, the Elog page will appear as in Figure 1.

|RO_RUNNING || 1 || While running

...',''c''... are passed to the subroutine, where they can be referenced via $1, $2, $3, etc. The subroutine can either reside in the current file, or in a ...ite" can be specified as ''n''. Optionally, the loop variable running from 1...''n'' can be accessed inside the loop via $''name''.

else if (offset == -1) // close the Super-event if offset is -1

** P-ONE, Stefan comment about approach to a DAQ design [01:25:40-1:27:25 ]

# - [1] is a C-string containing the "arguments" const char* args = CSTRING(1);

Name STRING 1 32 14s 0 RWD midas SYSMSG DWORD 1 4 11h 0 RWD 100000

return -1; &level, sizeof(INT), 1, TID_INT);

...this register to allow to set a "general" LAM register containing either "1" (At least one LAM from the masked LAM is set) or "0" ( no LAM set from the

The four available Alarm Types are shown in Table 1. They are defined in [http://ladd00.triumf.ca/~daqweb/doc/midas-devel/html/ |+ Table 1 : Defined Alarm Types

self register = 1 Reverse sort = 1

Figure 1: Structure of MIDAS event showing Event and Bank headers with data banks.< ..._List_Parameters#EventID|EventID]] identifies the event by number. Usually 1 is used for triggered events, 2 for scaler events, 3 for HV events etc.

[-v [level]] : Set verbosity level (as an integer). A bare '-v' implies '-v 1'

...tRecord(path) || no || no || no || no || [[AJAX#jget|cmd=jget]] with "name=1" || by caller||ODBMCopy ||mjsonrpc_db_get_values See: [[AJAX#jget]] with parameter "name=1"

e.g. to create a second logging channel (Channel 1) using [[odbedit]] [local]Channels>copy 0 1

Event ID -1 Trigger mask -1

run00001_00.mid run #1

...time <code>exp["Transition timeout"]</code> is mentioned), and written to 1 <pre>odb["Example"][1] = 1.2;</pre>

; Example 1

; > make ... NEED_OPTION=1 : ...istory system ). The Makefile will automatically include ODBC (HAVE_ODBC = 1) if the file /usr/include/sql.h is found. Otherwise ODBC will not be includ

for each defined logging channel (channel number 0,1...). ...been replaced by [[Keys in the ODB /Logger/History subtree#/Logger/History/1/Debug|Debug]] key.

[local:pol:S]/test>set fred[1..3] 6 [local:midas:Stopped]/>move custom 1

{ "Runinfo" : { "State" : 1, "Online Mode" : 1, "Run number" : 13585 } } status: 1, json: {

ProxyPass /rootana/ http://midastestdaq.triumf.ca:8088/ retry=1 ProxyPass / http://midastestdaq.triumf.ca:8081/ retry=1

<li> tags are created for each subdirectory entry (1 tag per entry)</li> <li> There is no possibility for naming array elements, so 1 tag per array, regardless of the number of elements.</li> </ol></dd>

client.odb_set("/pyexample", {"an_int": 1, "eg_float": 4.56}) default_common.event_id = 1

So a deadlock I see within 1 minute of running the torture test, other lucky people will see after runni for 1 year, or 1 month, or 1 day, depending.

| [[File:Capture_sgas.png|thumb|left|Figure 1: MEG Gas System]] || '''Example 1''' This page (Figure 1) from the MEG experiment at PSI shows a complex gas system. This shows the

| colspan="1" rowspan="1" style="text-align: center; vertical-align: top; background-color: rgb(204, | colspan="1" rowspan="1" style="text-align: center; vertical-align: top; background-color: rgb(204,

{ 1, // event ID If not using an interrupt, this field is set to 1.

note 1: I do not completely understand the ss_suspend_xxx() stuff. The best I can

| colspan="1" rowspan="1" style="vertical-align: top; background-color: rgb(255, 255, 204); font-wei | colspan="1" rowspan="1" style="vertical-align: top; background-color: rgb(255, 255, 204); font-wei

1=read | 2=write | 4=delete

;NOTE 1 ...x feature (NO_ROOT,NO_MYSQL,NO_ODBC,NO_SQLITE,NO_MSCB), e.g. "make NO_ROOT=1" to disable ROOT. These NO_xxx Makefile variables are only used to control

...key "enable non-localhost rpc" to "yes" and restart the [[mserver]] (step 1 above) ;NOTE 1

: In older MIDAS versions, the history-logging-channel subtrees were named 0,1,2... respectively

Listening on "http://[::1]:8080", passwords OFF, hostlist OFF Listening on "http://[::1]:8080", passwords OFF, hostlist OFF

# Note that midas defines SUCCESS as 1! ...ilure without specifying a specific midas status code (SUCCESS in midas is 1; this wrapper will set a code of 0)

1) Install rootana in usual place and make