MIDI – - Max-Planck-Institut für Astronomie
Contents
1. UNAMEN miins src sshd SUN etc init d sshd wminrts gt cd etc rc3 d wminrts gt ln s init d sshd S18sshd wminrts gt cd etc rc2 d wminrts gt ln s init d sshd K25sshd Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 15 7 Edit usr local etc sshd_config to allow X11 forwarding X11Forwarding yes X11DisplayOffset 10 KeepAlive yes 8 Allow the execution of ssh on the DWS without prompting for the password Proper installation of the PECS templates in the earlier sections ensures that the PATH of the midi account on the IWS already contains the new executables in usr local bin but the DWS is not administered in an equivalent way which may call for additional configuration there 4 1 5 P2PP For the test environment at MPIA on the IWS one ought also install P2PP 13 This does not make sense on Paranal because p2pp is not started on the IWS there any longer As vltmgr 1 Copy the Unix distribution kit from http www eso org observing p2pp P2PP tool html or ftp ftp eso org pub users uss ohs jp2pp to v1t Note that it is not necessary to install the Java Runtime Environment since this has already been installed in the process of installing the VLTCS 12 Unpack wmidi gt cd vlt wmidi gt gunzip p2pp gz tar xf p2pp tar 2 Follow the instructions in the INSTALL htm1 file wmidi gt cd vlt p2pp 2 8 wmidi gt make wmidi gt rm vlt p2pp tar wmidi gt mkdir p vl2. 1 does not work under Solaris Symptom The man 1 command does not work under SunOS Cause This seems to occur when the machine is rebooted as the actions in etc rc2 d RMTMPFILES may end up in missing write permissions for the tmp directory Recovery Restore write permissions for everyone to tmp 5 1 2 CMM fails under Solaris Symptom The CMM commands 15 do not work after re installation of the operating system and VLTCS on the Solaris computer Cause Probably a missing etc defaultrouter or etc resolv conf or an error in etc inet netmasks 6 APPENDIX References 1 Udo Neumann and Clemens Storz MIDI Detector Control Software User and Maintenance Manual 20 October 2005 VLT TRE MID 15823 0268 2 Richard J Mathar MIDI Observation Software User and Maintenance Manual 24 November 2004 VLT TRE MID 15824 0264 3 Udo Neumann MIDI Instrument Control Software User and Maintenance Manual 16 June 2004 VLT TRE MID 15823 0266 4 S Hippler MIDI Computer System Architecture 30 January 2001 VLT TRE MID 15823 0127 5 Richard J Mathar MIDI Instrument Control Software 1 February 2001 VLT TRE MID 15823 0128 6 C Storz MIDI Detector control software 7 February 2001 VLT TRE MID 15823 0129 7 W Jaffe Overview of MIDI Software Systems 31 January 2001 VLT TRE MID 15824 0130 8 D Popovic VET Software INS Common Software Startup Tool User Manual 26 August 2005 VLT MAN ESO 17240 2153 9 N Hou
3. 2004 also on Paranal cross mounts the home directory of the midimgr which means that midimgr refers to the same directory on the HP UX workstation and the Solaris workstation see also VLTSW20020194 If one would not separate the modules the binaries of all modules that are used on wmidi as well as on wminrts i e mio would be overwritten by pkginBuild in an unpredictable way this would create a mess of binaries at installation time and confuse the makefile dependency generator This precaution would not be needed at MPIA 4 3 9 Parameter Ranges for Use with Templates Question Where are the allowable parameters for use with templates Answer The recognized keyword value lists are at their standard place the instrument summary file miotsf config isf e The motor positions names including filters and instrument modes in this file should be kept up to date with the contents of mimcfg config mimcfgINS cfg The list of pre defined schedule files and windowing files should be updated with the file lists in the INS_ROOT directory on the IWS as documented in the ISF itself after going online with the software Most of the windowing files are generated dynamically during this process as documented in 14 It is highly recommended that the template software does this also dynamically instead of being based on static lists e Parameters that cannot be changed by software example the detector gains should not be used by the templates a
4. DL delay line DWS Detector Workstation ESO European Southern Observatory http www eso org GUI s Graphical User Interface s GEIRS Generic infrared software HP Hewlett Packard ICS Instrument Control Software IRACE Infrared array control electronics ISF Instrument summary file IWS Instrument Workstation LAN s Local Area Network s LCU s Local Control Unit s MIDI Mid infrared Interferometric Instrument for the VLTI http www mpia de MIDI MPIA Max Planck Institut fiir Astronomie Heidelberg http www mpia de NRTS Near Real Time System OPD s optical path difference s OS Observation software PLIN point list index number ROE Readout electronics SUN Sun microsystems UWS User workstation VLTCS VLT Common Software http www eso org v1lt sw dev VLTI Very Large Telescope Interferometer http www eso org projects v1ti WS s workstation s 2 MIDI SYSTEM ARCHITECTURE 2 1 Data Processing Requirements MIDI is equipped with a mid infrared sensitive detector which can together with its controlling readout electronics ROE deliver data at rates as high as about 53 MB s burst mode Normal observing does not require these rates but average rates of 2 3 MB s are foreseen along with a total data volume of 41 GB night These video data rates require powerful instrument hardware to collect and compress the data before archiving In order to efficiently acquire reliable interferometric data MIDI has to track t
5. of the daemon If miinsStop does not work due to this ACC problem the shutdown of Sect 3 1 2 must be done in more irregular ways e shutdown ICS with wmidi gt icbStop MIDI e shutdown VLTI only if the simulation wmiV1ti is active wmidi gt vltisimStop wmidi gt ccsShutdown e wmiVlti e shutdown OS with wmidi gt msgSend mioControl exit wmidi gt msgSend bossArchiver_mio exit e shutdown DCS with wmidi gt msgSend midroControl off wmidi gt msgSend midroControl exit wmidi gt msgSend midControl exit wminrts gt minrtsStop wminrts gt middiStop wminrts gt vccEnvStop e wminrts 12 Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 4 MAINTENANCE MANUAL 4 1 Installation 4 1 1 Instrument Workstation The standard installation of the OS ICS and the DRO part of the DCS software on the IWS uses one of various options of pkginBuild 11 to retrieve and compile the source codes as layed out in the files miins config miinsINSTALL cfg as midimgr wmidi gt cd MIDI_SOURCES UNAMEN wmidi gt mv INS_ROOT INS_ROOT date Y m dT7X wmidi gt mv INTROOT INTROOT date Y m ZdT X wmidi gt cmmCopy vltisimBUILD wmidi gt pkginBuild vltisimBUILD fromstep RETRIEVE tostep INSTALL_FILES wmidi gt export PKGIN_BUILD MIDI_SOURCES UNAMEN miins define source directory if not yet wmidi gt cd PKGIN_BUILD wmidi gt cmmCopy miin
6. Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 MIDI OS Engineering wmidi File Std Options Simulation CCS LCU Figure 4 miopanEngineering a slightly modified ESO standard panel accessible also with the Engineering option on the top bar of Fig 3 See the man page miopanEngineering 1 Reproduced from 2 File Std Options Figure 5 miipanControl pops up if the GUI button in the ICS column of the GUI in Fig 4 is pressed The further tree of GUI s hiding behind the mimpan and mimalign buttons is shown elsewhere 3 See miipanControl 1 Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 11 3 2 FAQ and Troubleshooting 3 2 1 msql Connectivity On Paranal the ACC database on the workstation ACC_HOST tends to become unstable which emits error messages like environment_loader pecs 000 ERROR bootstrapping failed environment_loader pecs 000 ERROR bootstrapping failed if one logs in to wmidi Other symptoms are that wmidi gt vccFastShow does not show the complete lists of some hundred workstations and LCU s or that the shutdown procedures of Sect 3 1 2 fail From the MIDI point of view there is nothing one can do but to call the support hotline to have the msql daemon restarted It is clear from a UNIX administrator s point of view that an extra user ought be created on the ACC_HOST which instead of getting an ordinary shell upon login just initiates the revival
7. OT config MIDI isf INTROOT config MIDI zip p2pp Proper installation of the PECS templates in the earlier sections ensures that the PATH of the midi account on the MPIA IWS already contains the new executables in v1t p2pp bin 4 2 Startup Reconfiguration The UNIX command line call on the Instrument Workstation to edit some global configuration parameters in the mimcfgINS cfg and mimcfgSTART cfg configuration files is wmidi gt miinsStartup which opens a GUI shown in Fig 6 Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 17 4 3 FAQ and Troubleshooting 4 3 1 OS keeps talking to wmiVIti instead of wvgvlti Symptom After modifying the OCS TEL ENVNAME in mimcfgINS cfg recompilation with make clean all man install in mimcfg src and re starting the OS servers OS still seems to forward commands to the VLTI server in the old environment Main Cause Behaviour of some parts of OS and the BOB setup is not only steered by the con figuration keywords that are read once when OS is started but also through additional parameters of the UNIX shell It also seems that mioControl as it is started as a subprocess of RTAP inherits shell environment variables from RTAP and needs to be started under a wmidi fullCCS environment that already keeps the correct shell variables Workaround Follow a proper sequence of actions if the VLTI environment is to be changed e Shutdown the old MIDI processes on wmidi with mii
8. RS and NRTS software on one computer is shown The alternative two computer solution is mentioned in 1 Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 5 Commands Status MIDI Science Data n11 gt Synch Trigger X Protocoll XXX Software YYY Hardware DRO GEIRS PP WS DWS MIDI DL LCU ICS MIDI MM LCU Figure 2 MIDI data and command status flow 6 _ Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 3 USER MANUAL 3 1 Startup Tool 3 1 1 Interactive Startup The recommended startup sequence in an interactive session 1 ensure that the DISPLAY variable of the UNIX shell is defined wmidi gt echo DISPLAY 2 optionally start the OS control panel Fig 4 wmidi gt miopanEngineering amp 3 start ICS either with wmidi gt miinsStart proc ICS or with the STARTUP button of Fig 4 This should result in ICS being LOADED 4 start DCS either with wmidi gt miinsStart proc DCS or by pushing the STARTUP button of DCS in Fig 4 5 Start the VLTI interface with wmidi gt miinsStart proc VLTI 6 start OS either with wmidi gt miinsStart proc 0S or by pushing the STARTUP button of OS in Fig 4 7 bring all subsystems into the ONLINE IDLE states with either wmidi gt msgSend mioControl online or by pushing the ONLINE button of OS in Fig 4 The less experienced user should simply se
9. The Mid Infrared Interferometric Instrument for the Very Large Telescope Interferometer MIDI Software User and Maintenance Guide Overview User Manual Doc No VLT TRE MID 15824 0262 Issue 1 5 235 Date August 23 2007 a Prepht rd J Mathar Walter J Jaffe August 23 2007 Name Date Signature Name Date Signature ii Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 Change Record Issue Date Section Parag affected Reason Initiation Documents Remarks 1 0 27 July 2002 all first preparation 1 1 29 May 2003 6 3 2 added merged Reference Docs with References removed empty List of Tables corrected cross references in Fig Captions 30 May 2003 4 3 1 added 11 Jun 2003 Fig 1 shows 1 Computer DCS solution Sec 4 2 Fig 6 added 26 Jun 2003 4 1 1 added hint on netrc and pecs installation 4 3 5 added 27 Jun 2003 4 1 4 added 30 Jun 2003 4 1 5 4 3 6 added 15 Jul 2003 4 3 7 added 17 Jul 2003 5 1 2 added 05 Nov 2003 4 3 3 added 19 Nov 2003 3 1 3 changed name of NRTS default server 20 Nov 2003 5 1 1 added 1 2 27 Nov 2003 4 3 8 4 3 4 added 05 Dec 2003 6 update man page listings 11 Dec 2003 4 1 1 updated 23 Jan 2004 4 1 5 updated for P2PP 2 7 1 3 21 May 2004 1 1 update URL s 09 Jul 2004 4 1 1 updated w r t vltisimBUILD 3 2 removed section on vltisim chopping 10 Sep 2004 4 3 8 updated 4 3 9 added 21 Sep 2004 4 1 5 upda
10. escribed in unlink 2 This probably means that pkginBuild is using oslx which is linked to cfitsio In a ab initio compilation without any prior files in INT_ROOT 1ib this problem does not show up Workaround Execute the make clean all man install from the UNIX shell in the module not via pkginBuild or remove INT_ROOT 1lib libcfitsio sl manually before starting pkginBuild Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 19 4 3 5 NRTS environment cannot be started Symptom After first installation of the instrument on Paranal in Nov 2002 the NRTS environ ment wminrts could not be started on the workstation wminrts after rebuilding everything from scratch Some of the standard processes listed in CcsEnvTable core dumped Cause The VLTCS including the binaries had just been copied from another computer of a different type than MIDI s ULTRA Enterprise 450 Server Workaround Install the VLTCS properly according to the manual 12 step by step Note that though 1 tries to distribute a different idea in some of its sections that deal with GEIRS the MIDI DWS is not what SUN calls SPARCstation or UltraSparc computers It is only the four processors SPARC II which carry this name 4 3 6 No logFile on wminrts Symptom The files logAuto and logFile in the vltdata tmp directory on the DWS do not exist and apparently have been removed Cause This seems to be a rare event caused by the periodic invocatio
11. g push buttons on other Graphical User In terfaces or calling them by name Some of them are also bound to the ctoo STARTUP configuration whence e the standard ESO BOB panel 10 can be called by either wmidi gt bob amp or by wmidi gt miinsStart panel BOB amp 8 _ Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 e the standard ESO LOG Monitor panel can be called by either wmidi gt logMonitor amp or by wmidi gt miinsStart panel LOG amp e the standard ESO v1tisim Control panel 9 can be called by either wmidi gt vltisimcon amp or by wmidi gt miinsStart panel VLTI amp e Fig 3 can also be called by wmidi gt miinsStart panel OS_CONTROL amp e Fig 4 can also be called by wmidi gt miinsStart panel OS_ENGINEERING amp e Fig 5 can also be called by wmidi gt miinsStart panel ICS amp Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 9 MIDI Control w File Options Engineering Instrument Disks ICS RID a ERa LOADED Mode Undefined a ES NRTS ICS ES e ee Access Simulation mes e o oil RA Exposure undefined Elapsed s DECO NRTS Mace ABORT Exp Time 0 0 s CHOPE E Ean Frame 2 In inactive Ac active Un undefined Nu nulling lt alias gt ISS chop status Figure 3 miopanControl a slightly modified ESO standard Buttons are described in the man page miopanControl 1 Reproduced from 2 10_ Software User and
12. he atmospheric con tributions to the fringe motion at rates of 1 Hz i e in Near Real time These requirements have led to non ESO standard elements of MIDI data processing design de scribed in more detail in documents 4 5 6 7 Additionally for pragmatic reasons during system development the DCS system does not use the ESO IRACE system but rather the Heidelberg GEIRS system of hardware and software to control the detector electronics We summarize the non standard elements here e The DCS system is subdivided into three subsystems Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 3 1 The DCS Server resident on the Instrument Workstation IWS which provides a central ESO style communications point with the other subsystems 2 GEIRS which controls the ReadOut Electronics and collects data from the detector and is largely resident on the Detector Workstation DWS 3 NRTS the Near Real Time System which receives windowed data from GEIRS via a high speed parallel connection and prepares it for archiving and is resident on the Post Processing PP computer wminrts It also performs online so called Data Quality Analysis of which the most important is fringe tracking e The ICS system must control the fringe piezos in real time via the MIDI Delay Line LCU The exact timing and position of piezo motions and telescope chopping movements must be known to the NRTS both for fringe
13. n of logVLTBackup 1 see the crontab 1 of the account vlt in conjunction with a high log level of the NRTS processes Recovery Remake empty logFile and logAuto as described in 12 3 4 2 As root restart the logger as described in 12 3 4 2 If this is impractical reboot the NRTS computer 4 3 7 hisDHMngr errors at environment start Symptom At start time of the RTAPENV the logFile reports warnings of the kind wmidi his hisDHMngr 214 62 hisControlPoint c 1005 5 1 S ccsERR_HIS_CONTROL_TABLES No setup can be enabled for history table with PLIN 47 wte35 his hisDHMngr 214 62 hisDHMngr c 1002 5 2 W ccsERR_HIS_CHECK_TABLES Point PLIN 47 could NOT be set to IDLE ARMED for two different PLIN s Cause The corresponding setup functionality is not enabled in CCS ccs db1 CCSMON db for the two OLDB points ccs_config monitoring trend 12 The association of PLIN s with OLDB points can be deduced from VLTDATA ENVIRONMENTS RTAPENV ccs_log Workaround Ignore This seems not to be an error but a feature of the CCS monitor in combi nation with a diligant logging within the his module 4 3 8 Why are the module sources not at the standard place Question Why are the MIDI modules not in the MIDI_SOURCES directory but one store lower at MIDI_SOURCES UNAMEN 20_ Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 Answer The computer disk layout in the Garching VLT Control Model and since Aug
14. nd therefore not be mentioned e The telescope and VLTI DL keywords need to be updated with whatever has been documented in the ISS modules this is certainly not part of the MIDI software and therefore not to be documented here It obviously indicates bad design of P2PP that this information must be kept in an instrument specific file VLTSW20040302 Additional documentation of some of these is in the comments of the dictionary entries module dicMIDI This includes documentation of keywords with specific values that trigger automatic choices by the subsystems themselves 4 3 10 CMM modules Question Which are the MIDI CMM modules Answer The software modules are obviously listed at the standard places used by pkginBuild which is PKGIN_BUILD config miinsINSTALL cfg on wmidi and MIDI_SW minrts config minrtsINSTALL cfg on wninrts The software documentation is generally kept in the doc subdirectory of these modules but additional copies exist in the CMM modules VLT TRE MID 15824 0262 VLT TRE MID 15824 0264 VLT TRE MID 15823 0266 VLT TRE MID 15823 0268 and VLT TRE MID 15824 0270 All these are subject to change the template type of modules mi seq and mi tsf have been tripli cated recently for instance rendering it almost impossible to figure out the currently active set Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 21 5 ISSUES UNRELATED TO MIDI SOFTWARE 5 1 FAQ and Troubleshooting 5 1 1 man
15. nsStop 1 including the VLTI e Stop the CCS environment with wmidi gt vccEnvStop e wmidi and close all BOB windows e Edit OCS TEL ENVNAME in mimcfg config mimcfgINS cfg and distribute with cd src make clean all man install e Logout and login again on all terminals on the IWS to have osbEnvSet 1 redefine TCS_ENVNAME and VLTI_ENVNAME e Re start the CCS environment and MIDI SW with wmidi gt miinsStart The script miinsSwitchVlti in miins test is tailored to support this cycle A more advanced proposal was made in VLTSW20030001 but was rejected by ESO Second Cause Someone tried to be smart and created subordinate copies of the mimcfgINS cfg file to avoid editing and moved them around which dodged the Makefile idea of which files are older than others Workaround Use only one configuration file mimcfgINS cfg edit it only in the source code di rectory and always run make there Third Cause It is actually not the OS server but one of the sequencer template scripts that uses a hardcoded environment name This error usually means that a programmer tried to bypass the isstcl interface library in these scripts but this would anyway be out of the scope of this document 18_ Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 4 3 2 Scan Link Setup at VLTI Environment Switching Symptom In some cases especially when switching between wmiVlti and wvgvlti environments the miinsStart reports problem
16. ollowing the instructions including the temporary run of p2pp This installs the in strument package on wvgdhs instmgr instruments in conjunction to a reference to this directory in wvgdhs visitor p2pp cf On the wmidi test machine at the MPIA it is useful to install the user instmgr on wmidi according to 12 to simplify this step if not yet done as root Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 13 wmidi useradd g vlt d diska home instmgr s bin bash c P2PP Installation m instms wmidi passwd instmgr and after rlogin as instmgr wmidi gt etc pecs bin pecssh mklinks i wmidi gt echo wmidi midimgr gt gt rhosts edit for login as midi wmidi gt chmod go r rhosts wmidi gt cd pecs wmidi gt ln s introot config miins apps wmidi env apps wmidi env wmidi gt ln s introot config miins misc wmidi env misc wmidi env wmidi gt ln s introot config miins misc wmidi ali misc wmidi ali 4 1 2 Preprocessor Workstation The equivalent standard installation of the NRTS software on the PP WS ensures that configuration files for schedules see the man page mioSched ins 5 and for FITS templates see the man page mioSetup fits are consistent Absence of cross compilation facilities in the installation tool 11 means that this compilation of the PP WS must be done separately wminrts gt export PKGIN_BUILD MIDI_SOURCES UNAMEN minrts chose source directory if not y wmin
17. ooting 0 0 0 000 ee ee 4 3 1 OS keeps talking to wmiVlti instead of wvgvlti 4 3 2 Scan Link Setup at VLTI Environment Switching 4 3 3 missing separator make messages on wminrts 00 4 3 4 pkginBuild errors compiling miopub 0 02 0004 4 3 5 NRIS environment cannot be started 2 2 20 0 020000 2 eae 4 3 6 No logFileon wminrts a e sas aenal e a a e e aAa ah a ee 4 3 7 hisDHMnegr errors at environment start ooa a 4 3 8 Why are the module sources not at the standard place 4 3 9 Parameter Ranges for Use with Templates 20 4 3 10 CMM modules s seos ssa p 0426s Dae eR ee ee ee a a a 5 ISSUES UNRELATED TO MIDI SOFTWARE 5 1 FAQ and Troubleshooting lt s soo so cc 2244 eee Re ee ee ee ee 5 1 1 man 1 does not work under Solaris 0 00005 5 1 2 CMM fails under Solaris s i a aytsa a e5 e544 eee e wee wa 6 APPENDIX List of Figures 1 MIDI computer Architecture Only the solution with placement of the GEIRS and NRTS software on one computer is shown The alternative two computer solution is mentioned ty I r oa os se sra Boe od lw Ge 84 ES oe haw DG Ra Bw Bee OS MIDI data and command status flow 2 64544 25544 58444 Bee eee ha miopanControl a slightly modified ESO standard Buttons are described in the man page miopanControl 1 Reproduced from 2 2 04 miopanEngineering a
18. ource and openssh 3 6 1p2 tar gz from http www openssh com portable html to vltdata tmp Unpack cd vltdata tmp gunzip openssl tar xf openssl gunzip openssh gz tar xf openssh tar 2 cd vltdata tmp openss1 0 9 6i PATH v1t 20 7 gnu bin PATH config make make install 3 Only on the IWS for HP UX Ensure the zlib is found wmidi gt export LDFLAGS L v1t APR2003 tcltk 1lib Note that the exact library path depends on the current VLTCS version 4 cd vltdata tmp openssh p CFLAGS I v1t APR2003 tcltk include configure with utmpx without pam with ssl dir usr local ssl Note that the exact include path depends on the current VLTCS version 5 on the IWS HP UX wmidi gt vi config h and insert define HAVE_UTIMES wmidi gt useradd d home sshd s bin false c openssh daemon sshd wmidi gt PATH PATH v1lt 20 gnu hppa bin or alternatively on the DWS Solaris wminrts gt useradd d dev null g bin s bin false c openssh daemon sshd wminrts gt PATH PATH v1lt 20 7 gnu sparc bin The PATH extension ensures that strip is found Then make make install 6 on the IWS HP UX wmidi gt cp midimgr MIDI_SOURCES UNAMEN miins src sshd HP sbin init d sshd wmidi gt cd sbin rc2 d wmidi gt ln s init d sshd S180sshd wmidi gt cd sbin rci d wmidi gt ln s init d sshd K170sshd or aternatively on the DWS Solaris wminrts gt rcp wmidi midimgr MIDI_SOURCES
19. rts gt cd PKGIN_BUILD wminrts gt mv INS_ROOT INS_ROOT date Y m AdT X not needed with pkginBuild 1 75 and IN wminrts gt mv INTROOT INTROOT date Y m Z dTAX not needed with pkginBuild 1 75 and INST wminrts gt cmmCopy minrts wminrts gt pkginBuild fromstep RETRIEVE Note that some of the DCS installation the GEIRS part is not covered by pkginBuild as described above and needs additional action as described in 1 After a re installation of the user midi on the DWS one must recreate midi rhosts to allow remsh 1 access from the IWS account midi 4 1 3 Finalize Since this installation is done after login as midimgr on these computers and since pkginBuild finally starts the environments on these computers under the same account it is advisable to stop the workstation environments afterwards wmidi gt vccEnvStop e wmidi wmidi gt vccEnvStop e wmiVlti wminrts gt vccEnvStop e wminrts Otherwise a subsequent attempt to run the environments as the ordinary midi user may result in problems with file permissions 4 1 4 Secure Shell For the test environment behind a firewall it may also be necessary to install the secure shell to allow remote access to the machine This does not make sense on Paranal but is usually done at MPIA As root 14 Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 1 Copy openss1 0 9 6i tar gz from http www openssl org s
20. s wmidi gt pkginBuild step RETRIEVE If the modules slx oslx or cfitsio are in the list of modules in miinsINSTALL VLTSW cfg it may be advisable to compile these first individually because pkginBuild uses shared libraries created by these modules and these cannot be replaced at pkginBuild runtime under HP UX wmidi gt pkginBuild fromstep BEFORE_INSTALL tostep BUILD_MOD Ensure that miinsEnvSet 1 is called which is done via the PECS scripts by logging in again wmidi gt logout wmidi gt rlogin wmidi l midimgr wmidi gt pkginBuild fromstep BUILD_ENV After a re installation of the user midi on the IWS one must recreate wmidi midi netrc to allow ftp 1 file transfer to the DWS with mioSetupDistr 1 optionally including infor mation for mioFtp2Ews 1 In this case it is also strongly recommended to establish symbolic links in the midi pecs directory as already established at that time in midimgr pecs For the equivalent reason update the FITS template files on the IWS one must recreate wminrts midimgr netrc to allow ftp 1 file transfer in the other direction At the time of this writing there is a slight asymmetry here because the transfer is done from DWS at compile time by midimgr but from IWS at startup time by midi If p2pp is to be used on Paranal the instrument package must also be uploaded to the wvgdhs workstation with wmidi gt cd PKGIN_BUILD miotsf src wmidi gt make install_ip and f
21. s with setting up the scan links between wmidi and VLTI_ENVNAME Cause Workaround In these cases one should explicitly close the connection with wmidi gt miinsStop e VLTI then call wmidi gt scanei to clean erase the scan tables towards wmiV1ti and wvgvl1ti then try again wmidi gt miinsStart e VLTI If the error is close to Failed to add or delete an entry CE function for attribute already existing line this will not help and one must re build the databases of the environments as midimgr wmidi gt pkginBuild fromstep BUILD_ENV env wmidi wmidi gt pkginBuild fromstep BUILD_ENV env wmiVlti 4 3 3 missing separator make messages on wminrts Symptom Compiling NRTS modules or VLTSW on wminrts creates errors of the form tmp vltMake_3420_midimgr 28 missing separator Stop Cause The environment variable CPU is probably not set See VLTSW20000323 and VLTSW 20030174 Workaround Set the environment variable export CPU PPC604 either in the local PECS files apps HOST env of all relevant parties midimgr vltmgr or bet ter in the global configuration file of the pecsmgr releases 000 etc locality apps HOST env 4 3 4 pkginBuild errors compiling miopub Symptom Recompilation of the miopub module with pkginBuild returns an ERROR Cause As one can see in the MIDISW INSTALL pkginBuild err file some shared libraries cannot be replaced with rm rf and cp the error message is Text file busy as d
22. sen Simulation of VETICS for Instrumentation SW User Manual 1 December 2001 VLT MAN ESO 15410 2372 10 E Allaert VLT Software HOS Broker for Observation Blocks User Manual 24 April 2007 VLT MAN ESO 17220 1332 22 Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 11 S Skole and R Schmutzer VLT Software Installation Tool for VLT SW Packages User and Maintenance Manual 31 December 2005 VLT MAN ESO 17240 1913 12 S Feyrin VET Common Software Installation Manual 21 February 2007 VLT MAN ESO 17200 0642 13 F Comer6n and D Silva Phase 2 Proposal Preparation Tool P2PP User Manual 6 edition 20 December 2004 VLT MAN ESO 19200 1644 14 J de Jong MIDI Near Real Time Software User and Maintenance Manual 8 February 2004 VLT TRE MID 15824 0270 15 P Sivera VLT Software Configuration Management Module User Manual 22 October 2001 VLT MAN ESO 17200 0780 oo _
23. slightly modified ESO standard panel accessible also with the Engineering option on the top bar of Fig 3 See the man page miopanEngineering 1 Reproduced from B sa t 84860 ob i kG EP Gee hE Die ede he Se bd miipanControl pops up if the GUI button in the ICS column of the GUI in Fig 4 is pressed The further tree of GUI s hiding behind the mimpan and mimalign buttons is shown elsewhere 3 See miipanControl 1 2 2 22000 The graphical user interface accessible with the miinsStartup 1 command Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 1 1 INTRODUCTION MIDI is a Michelson type interferometric instrument to be operated at 10 um at the VLTI on Paranal Chile The instrument s most challenging tasks from a control point of view are the high detector readout frequencies 40 250 Hz which will be processed in a near real time environment The wish for setting up a feed back system with an open loop frequency of up to 10 Hz to stabilize fringes when no external fringe tracker is available sets increased demands on data acquisition real time processing and near real time processing capabilities Accurate synchronization among many different sub systems chopping control systems fringe tracker delay line controllers etc introduces further strong requirements 1 1 Scope This document is the introduction to the MIDI Software User and Maintenance Manuals Separate manuals ha
24. t p2pp 2 8 cache instruments wmidi gt chmod gtwx vlt p2pp 2 8 cache instruments wmidi gt chmod gtwx vlt p2pp 2 8 cache 3 If the midi account has been re created also add the file midi p2pp cf with the lines CACHE FOLDER diska home midi p2pp cache IMPEX FOLDER diska home midi p2pp impex INSTRUMENTS FOLDER diska home midi p2pp instruments APPSERVER LOG diska home midi p2pp logs appserver log and execute wmidi gt mkdir p p2pp cache p2pp instruments MIDI as user midi 4 Edit v1t p2pp 2 8 config site cf to penetrate the MPIA firewall APPSERVER HTTPPROXYHOST web proxy mpia hd mpg de APPSERVER HTTPPROXYPORT 3128 16_ Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 gt miinsStartup j full software and hardware Paranal x Ww Start Figure 6 The graphical user interface accessible with the miinsStartup 1 command and optionally DEFAULT PRINTER laps_u 5 Ensure that each start of p2pp works with the latest instrument package This is achieved by adding the following ten lines before the Standard settings in vlt p2pp 0 9 bin p2pp at MPIA ensure that the midi account uses the most recently installed TSF s case USER in midi instmgr ifold fgrep INSTRUMENTS FOLDER p2pp cf awk F print 2 cd ifold MIDI rm tsf ln s INS_ROOT SYSTEM COMMON TEMPLATES TSF MIDI tsf esac and adding two links wmidi gt In s INTRO
25. t the DISPLAY and use wmidi gt miinsStart which starts the instrument software plus a default set of GUI s with slightly less selective control Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 7 3 1 2 Interactive Shutdown The shutdown process follows the opposite ordering 1 wmidi gt miinsStop proc OS 2 wmidi gt miinsStop proc VLTI 3 wmidi gt miinsStop proc DCS 4 wmidi gt miinsStop proc ICS 5 Close the remaining GUI s with their Quit selector The quick procedure is wmidi gt miinsStop with no command line arguments which also takes care of closing the light path by moving the FILT and SHUT to their CLOSED positions 3 1 3 Processes Starting and stopping of instrument subsystems OS ICS DCS VLTT is supported through software based on the Startup Tool 8 The UNIX command line calls on the Instrument Workstation are wmidi gt miinsStart proc OS to start the OS server processes mioControl and bossArchiver_mio wmidi gt miinsStart proc ICS to start the ICS server processes miiControl and miSimControl wmidi gt miinsStart proc DCS to start the DCS server processes on wmidi and wminrts which comprise the split server midControl the NRTS server minrtsControl and the DRO server midroControl wmidi gt miinsStart proc VLTI to start the VLTI simulation servers 9 3 1 4 Graphical Interfaces Graphical User Interfaces are created by either followin
26. ted for P2PP 2 8 1 4 30 Oct 2004 4 1 1 removed comments on fv 25 Nov 2004 6 removed man page printouts 1 5 235 23 Aug 2007 all produced PDF version 6 partially updated Contents 1 INTRODUCTION Il SCOPE 2 4 s h4 Ges Mew Shee he be ee bh a oe ee ee 1 2 Abbreviations and Acronyms se sesi ee PoR aa En 2 MIDI SYSTEM ARCHITECTURE 2 1 Data Processing Requirements s os ss s deca xor sa m eee ee ee 3 USER MANUAL 3 1 Startup Tool 2s 4 22425 24 Se Ok Re DR ee SA ee ek a be ee 31 1 Interactive Startup 2 2 2406 ce Sb ere oe eS ee ee ah a Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 _ iii 3 2 3 12 Interactive shutdown 2 44 a beige ob Ao OE we BE A A ae ek aa Sla Processes sg 27s s ace eon BONG ROS Bek ge Oe A ee Se et Re ee 214 Graphical Interfaces sus sie e ne ee eek Bia Re a toe Be we Oe ae ce FAQ and Troubleshooting 0 0 0 ee ee 3 2 1 msl Connectivity s siik i Os ee eA Aw ee ee PO Gee Sd 4 MAINTENANCE MANUAL A 4 2 4 3 Tnstallation sest ace 8 edo eed Be Re ek a eA eee BO ee eee Ads Instrument Workstation s sacie ocna abe ee ASG ee Ee be aes 41 2 Preprocessor Workstation sosti assa eek ie Re Ro e Sh ek a Se eS AWS Hinalize 2046S h bee ee OR A A ee Re es a a Ae aa AJA Secure Shell erisa iis ia Bae hee oe OA See ea ee ee EAT Alb P2PP o acia n ee hae De Sea eee oe ee we See Ge es Startup Reconfiguration e 2 248 452 a e 44 2 OS AG ee Se Ee ae ee FAQ and Troublesh
27. tracking and for inclusion in the archived data This has as consequences 1 The Observing System OS downloads a preplanned Schedule of piezo movements to the DL LCU and to NRTS during observation SETUP via the ESO CCS messaging system 2 The DL LCU forwards actual piezo positions exposure timing and chopping mirror timing information to NRTS again via CCS messaging Figure 1 illustrates the hardware components of the MIDI computer system For more details see 4 Figure 2 also taken from 4 illustrates the flow of commands image data and OPD timing infor mation between software systems 4 _ Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 e Detector Data Link PCD 60 Readout ere Pre processor Electronics Workstation DCS Command GEIRS and NRTS Link RS 232 Readout and OPD Synchronization I i MIDI Delay Line Internal Delay Li LCU I i VLT Timing Switch cane i Router T TTE Reflective Me ATM mory Network Fast f f _ a Ethernet l Motors Instrument Motors and Encoders Workstation Metrology ICS DCS OS ee Cryo and Metrology Hardware General VLTI Services and Coordination Subnet Pipeline Archive User Work Workstation Workstation station Expert Workbench Graphical System User Interfaces Figure 1 MIDI computer Architecture Only the solution with placement of the GEI
28. ve been written for the major MIDI software subsystems OS ICS DCS NRTS and for the Observation Templates The current document summarizes the software architecture of MIDI describes the differences between MIDI and earlier standard VLT instruments and describes the procedures and GUIs for starting up and shutting down the system as a whole Detailed descriptions of the procedures and GUIs for the subsystems are described in their separate documents This report contains the following sections INTRODUCTION The present section which states the aim of this report and lists the references as well as the used abbreviations and acronyms OVERALL ARCHITECTURE SYSTEM USER MANUAL Commands and GUIs for starting up running and shutting down MIDI as a whole MAINTENANCE MANUAL Procedures for installing the MIDI software New versions of this document are distributed on the world wide web under http www mpia de MIDI internal vlt_docs html in the CMM module miins directory miins doc therefore also on the IWS in midimgr UNAMEN miins doc in the CMM module VLT TRE MID 15824 0262 on the world wide web under http www strw leidenuniv nl mathar public 2 _ Software User and Maintenance Guide Issue 1 5 235 VLT TRE MID 15824 0262 1 2 Abbreviations and Acronyms ACC Access and Configuration Control ATM Asynchronous transfer mode CE Calculational engine CMM Configuration Management module DCS Detector control system
Download Pdf Manuals
Related Search