Using OBSINP under OBSE
11-oct-1995 / jn

If you want to use single OBSINP-commands or OBSINP-command-files under OBSE , you have to be careful. The passive field will be copied into the active field, before the drive program will start to execute a scan with the parameters of the active field. That is triggered by an OBSE command-verb. This scan is performed using the content of the active field at that moment. However, there are some commands, which can be changed during a scan (See the OBSE and OBSINP-manuals !).
  • Be very careful reading new OBSINP-commands during an observation !
If you have started an observation by typing OBSE-commands, the OBSE-program calls the SIC-interpreter for reading macros (using OBSINP-commands) to fill the passive field . If at that moment you change the passive field by reading files with the OBSINP READ command or by typing single OBSINP commands, the passive field will be changed. By that also the afterwards loaded active field is influenced due to that OBSINP input different from normal OBSE-input (according to the commanded verb). In that way it is possible, that the forthcoming observation is a mixture of the commanded OBSE verb and your input from the OBSINP command-file. Normally that is not intended by the user. Only Single OBSE command-verbs can be stacked (maximum of 2) and will be executed one after the other without problems.

As the interpretation of the macros by SIC takes a lot of time, some actions will not be performed everytime a new scan is started. If OBSE-parameters have not changed since the last executed OBSE command-verb, the program does not set these parameters again assuming they are already set in the right way by the foregoing observation. That means, you can overwrite parameters in the passive field by direct OBSINP-commands without the information for OBSE , that it has to reset these parameters before performing a new observation. To force OBSE to do that you must first start an observation of another type with an OBSE command-verb , then cancel this observation and then execute your desired OBSE command-verb. Obviously that is not valid for a few parameters, which are never touched by OBSE . In conclusion:

  • Be very careful with mixing OBSE - and OBSINP-commands !
In addition to the possibilities offered by SIC for programming observations via macros, there are on the other hand the OBSE command-verbs. They allow to set all important parameters for your observation, so that it normally is not necessary to go back to OBSINPcommands or command files.