Using the Data Storage Software (TapeServer) (1) Look at the MIDAS icons on the top task bar. The extreme right icon is TapeServer. Click on this. The command script /MIDAS/Linux/startup/TapeServer is run. This starts a terminal window and you will get output like this Tidy up master: no process killed stats: no process killed driver: no process killed linkTCP: no process killed Starting Tape Server startup complete MIDAS Tape Server: Message logger not contacted. MIDAS Tape Server: MIDAS Tape Server Build February 14 2014 MIDAS Tape Server: Unable to change scheduling priority - Permission denied MIDAS Tape Server: Using default startup MIDAS Tape Server: Configuration: UDP port = 10205, SHM key=10205. MIDAS Tape Server: File mapped object /SHM_10205 of size 1331104 created MIDAS Tape Server: Shared memory ID is 3 MIDAS Tape Server: Shared memory segment located at address 7f45841a6000. MIDAS Tape Server: Configuration file used - /MIDAS/config/TS_10205/TS_configuration MIDAS Tape Server: Stats task /MIDAS/TapeServer/Linux64/stats MIDAS Tape Server: Using device file /dev/file/0 /MIDAS/TapeServer/Linux64/driver MIDAS Tape Server: Using device sink /dev/null/0 /MIDAS/TapeServer/Linux64/driver MIDAS Tape Server: Data link /MIDAS/TapeServer/Linux64/linkTCP 10305 MIDAS Tape Server: Message reporting level = 0x180fff8 MIDAS Tape Server: Message logging level = 0xfff8 MIDAS Tape Server: Tape Server Options = 0x2 MIDAS Tape Server: File device path base = /TapeData MIDAS Tape Server: Data buffer size = 65536 MIDAS Tape Server: Tape block size = 65536 MIDAS Tape Server: File mapped object /SHM_110205 of size 4195880 created MIDAS Tape Server: Shared memory ID is 3 MIDAS Tape Server: Shared memory segment located at address 7f4583da5000. MIDAS Tape Server: File mapped object /SHM_210205 of size 3100 created MIDAS Tape Server: Shared memory ID is 3 MIDAS Tape Server: Shared memory segment located at address 7f4584305000. MIDAS Tape Server: Capabilities restored. MIDAS Tape Server: Master global area initialised. MIDAS Tape Server: Stats task has pid 28131 MIDAS Tape Server: Driver process for /dev/file/0 has pid 28132 MIDAS Tape Server: Driver process for /dev/null/0 has pid 28133 MIDAS Tape Server: Link task 0 has pid 28134 MIDAS Tape Server: Starting the RPC interface MIDAS Tape Server: Created RPC Program 28000205 Version 4 on UDP port 10205. MIDAS Tape Server: Entering server loop MIDAS Tape Server: MIDAS Tape Server now available on UDP port 10205. MIDAS Tape Statistics: Message logger not contacted. MIDAS Tape Statistics: MIDAS Tape Statistics Build February 14 2014 MIDAS Tape Statistics: Started with args 10205 MIDAS Tape Statistics: Configuration: SHM key=10205 MIDAS Tape Driver (28132): Message logger not contacted. MIDAS Tape Driver (28132): MIDAS Tape Driver Build February 14 2014 MIDAS Tape Driver (28132): Started with args 0 10205 MIDAS Tape Statistics: File mapped object /SHM_10205 of size 1331104 created MIDAS Tape Driver (28132): Configuration: driver=0, key=10205. MIDAS Tape Statistics: Shared memory ID is 3 MIDAS Tape Driver (28133): Message logger not contacted. MIDAS Tape Driver (28133): MIDAS Tape Driver Build February 14 2014 MIDAS Tape Statistics: Shared memory segment located at address 7f1f89727000. MIDAS Tape Driver (28133): Started with args 1 10205 MIDAS Tape Driver (28132): File mapped object /SHM_10205 of size 1331104 created MIDAS Tape Driver (28132): Shared memory ID is 3 MIDAS Tape Driver (28133): Configuration: driver=1, key=10205. MIDAS Tape Driver (28132): Shared memory segment located at address 7f2a1c7fc000. MIDAS Tape Driver (28132): Using device /dev/file/0 of type file. MIDAS Tape Driver (28133): File mapped object /SHM_10205 of size 1331104 created MIDAS Tape Driver (28133): Shared memory ID is 3 MIDAS Tape Driver (28133): Shared memory segment located at address 7f708728d000. MIDAS Tape Driver (28133): Using device /dev/null/0 of type sink. MIDAS Data Link (28134): Message logger not contacted. MIDAS Data Link (28134): MIDAS Tape Data Link Build February 14 2014 MIDAS Data Link (28134): Started with args 10205 10305 MIDAS Data Link (28134): Configuration: SHM key=10205, TCP port = 10305 MIDAS Data Link (28134): File mapped object /SHM_10205 of size 1331104 created MIDAS Data Link (28134): Shared memory ID is 3 MIDAS Data Link (28134): Shared memory segment located at address 7f5ba5d7b000. MIDAS Data Link (28134): Starting the network interface MIDAS Data Link (28134): TCP socket receive buffer was 87380 - now 458752 MIDAS Data Link (28134): TCP socket send buffer was 16384 - now 458752 MIDAS Data Link (28134): MIDAS Data Link thread 0 using TCP port 10305. MIDAS Data Link (28134): Entering server loop MIDAS Data Link (28134): thread 0 listening on port 10305 (2) Look at the MIDAS icons on the top task bar. The second icon from the left is "MIDAS for Merge". Click on this. A terminal window is created and the command /MIDAS/bin_Linux64/MIDAS64-session Merge /MIDAS/experiments/Merge runs. A GUI window is created labelled "Merge Base Frame" See ScreenH This contains a menu item "Tape Control". Click on this. The control window for the Tape Server starts See ScreenI For the item under "Available Drives" click on Allocated. No turns to Yes In the "Load Tape" menu select "Initialise" and follow the on window instructions. The Volume name will be a directory created under the Tape Server file root (/TapeData) You can now choose a "Run Name Prefix" and/or "Run Number". The file name in the direct will be these concatinated. Ie R3. Click on "Server State" Go and you are ready to write incoming data to disc. See ScreenJ (3) If you now return to the LyrTech Experiment Control. Ensure that the Readout is in the GO state and that the TS Transfer Enabled is selected (tick). The tick box will be RED if there is no data connection (or the acquisition is in STOP state) and will be GREEN if there is an active data connection. The Tape Server terminal will show progress MIDAS Tape Server: Initialising volume on device /dev/file/0. MIDAS Tape Server: Mounting volume EXPT4 on device /dev/file/0. MIDAS Tape Server: Opening file R3 on device /dev/file/0. MIDAS Data Link (28134): thread 0 accepted connection from 192.168.0.200, port 58930 MIDAS Data Link (28134): buffer size changed to 65536 MIDAS Data Link (28134): thread 0 client closed connection MIDAS Data Link (28134): thread 0 listening on port 10305 and there will be a "spinner" in the last line which changes as each data block is written to disc.