Search results

Jump to navigation Jump to search

Page title matches

  • As Midas supports remote [[Frontend Operation|frontend(s)]], the method to connect the frontend to t
    824 bytes (128 words) - 14:03, 8 July 2015

Page text matches

  • ...>''mserver''</span>) provides [[Remote Access to a Midas experiment|remote access]] to any MIDAS client. Changes to {{Utility|name=mserver}} (August 2015) m ...structions: [[Security#MIDAS programs on remote machines|MIDAS programs on remote machines]]. Without this action, only programs running on the local host wi
    5 KB (692 words) - 17:15, 12 November 2015
  • ...s to a Midas experiment]]''' &rarr; ''Information about connecting to a remote experiment''
    2 KB (245 words) - 18:09, 11 December 2019
  • (shared memory odb access) and remotely (odb access through mserver tcp rpc). For example, the (the above means that each midas client has access to the list of all open records through
    4 KB (637 words) - 15:00, 7 July 2015
  • = Access Control to a MIDAS experiment = ...lt now requires an SSL Certificate and a username and password (see [[#Web Access]]).
    12 KB (1,929 words) - 14:12, 19 June 2023
  • Checking environment... experiment name is "npet", remote hostname is "" Checking environment... experiment name is "npet", remote hostname is ""
    5 KB (695 words) - 17:35, 20 November 2018
  • ...d computer (on the same node where the event buffers reside) for fast data access (no network involved). ...provide a copy or move of the logger data. The destination being usually a remote location holding a large data storage, tape robot, etc... The reason for su
    1 KB (204 words) - 17:49, 14 July 2015
  • ...e user to run a MIDAS [[#Experiment]]. MIDAS clients can be ''Local'' or ''Remote''. :;Remote
    11 KB (1,698 words) - 16:26, 8 January 2016
  • For remote midas clients, their al_check() issues an RPC_AL_CHECK RPC call into remote client).
    3 KB (472 words) - 17:42, 12 November 2015
  • ...configuration requires a dedicated PCIe interface sitting in a PC. The VME access remains available in all cases but requires a VME controller. ...re layer such as ser2net will bridge serial devices connected to a PC to a remote network application for communication.
    4 KB (668 words) - 13:23, 10 September 2015
  • ...experiment is requested. In that case, this variable is '''defined on the remote host(s)''', and predefines the name of the [[#Introduction|experiment host] ...e ODB keys names are checked to ensure they are UTF-8 compliant (see [[ODB Access and Use#ODB Keys|ODB Keys]] for more information).
    5 KB (719 words) - 00:29, 20 June 2023
  • ....e. '''localhost only'''). In this case, the MIDAS ''experiment host'' has access to any hardware required, and all frontends, logger, analyzer etc. run on t ...an experiment with additional frontend(s) running '''remotely''' (i.e. on remote cpu(s)) will also be described.
    38 KB (5,821 words) - 03:18, 3 January 2024
  • *MIDAS Server Remote access server (RPC server) - ''Interface connecting remote Midas client to your local experiment'' - ....e. big/little endian) is taken care of, such that cross-platform database access is possible, with the advantage that the RPC doesn't define a byte ordering
    18 KB (2,954 words) - 18:11, 4 January 2016
  • value of timeout for remote rpc connect ...ccess by unauthorized hosts to be prevented by the system checking the RPC access control list (see [[#RPC hosts subtree|RPC hosts/Allowed hosts]]).
    34 KB (4,512 words) - 16:39, 4 March 2021
  • ...ntend task''</span>" or program running on a particular computer which has access to hardware equipment in use by the experiment. An experiment may The hardware access is only apparent in the user part ( referred to here as ''frontend.c'', but
    8 KB (1,169 words) - 17:21, 6 July 2015
  • : Remote : Access
    5 KB (661 words) - 16:00, 23 June 2015
  • To access information in the ODB dump, you can do something like ...to a midas experiment, by wrapping midas' C library. It provides nice ODB access through functions like <code>odb_set</code> and <code>odb_get</code>, and c
    12 KB (1,873 words) - 18:23, 24 July 2023
  • ...concepts for the CAMAC and VME, the ''musbstd.h/c'' is available for USB access. ...nd Stacks'' this option is not yet supported by the MIDAS API limiting the access speed of a R/W 24bit cycle to ~360us!
    8 KB (1,319 words) - 17:10, 14 October 2016
  • ...alarm checks. To prevent race conditions between different MIDAS clients, access to al_check() is serialized using the ALARM semaphore. Inside al_check(), a * Select channel where alarms get posted, allow access
    16 KB (2,531 words) - 07:32, 5 May 2023
  • * '''MIDAS_SERVER_HOST''' MIDAS host server name for remote midas connections. On some operating systems, several MIDAS functions require administrator access:
    32 KB (5,005 words) - 11:56, 11 June 2019
  • * <code>MVOdb</code> - simplified access to ODB that suits some use cases. You can still use the <code>db_*</code> f There are 3 ways to access the TMFE class:
    28 KB (4,108 words) - 16:08, 26 April 2023
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)