Computing for Science

The Computing for Science (CS) group supports ILL scientists, students and visitors in a number of activities including data analysis, instrument simulation and sample simulation.

Back to ILL Homepage

All Software

5. Manipulating Workspaces

The 'Formula-Entry Area' showing entered formulae and workspace history
The 'Formula-Entry Area' showing entered formulae and workspace history

Imagemap - Click on any point to go to the relevant paragraph.

To top

Formula-Entry Window

All formulae and commands entered in this field (by typing them in and hitting return) are scanned by LAMP for workspace manipulations. They are also executed by IDL so that almost all IDL commands and functions can be entered in this field.

One-line Macros (Do buttons)

As well as using the formula-entry window, one-line commands can be also be written in any of the windows on the right of the area in classical Lamp and executed by pressing its neighbouring Do button. You can also get them from the menu-bar item "lamp/layout".
Commands can be copied from any field of the LAMP interface (using left-mouse button and dragging) and pasted (using the middle mouse-button) into a one-line macro. These macros are stored when you exit LAMP and restored next time LAMP is run. They are associated with the working directory (your path), so if you change this they will not be restored.

To top

Errors

A crunch sound signifies an error and a message will appear beneath the formula-entry window or the DATA COLLECTOR area (cursor values are also displayed here). Please report unexplained errors.

To top

Workspace Array and Data Dimensions

Each time a workspace is altered its dimensions and data minimum and maximum values may change. If the W Min,Max button is selected this information will be displayed in the neighbouring window.

To top

Workspace History

Each operation which modifies a workspace is stored in its history. If the W History button is selected the histories are displayed in place of the W Min,Max values. (see also Session Journal below)

User-Macro Files

The User Macros? button opens a window which allows the LAMP macros and their descriptions to be visualised and searches for all <code>*.pro</code> files in the directory appearing in the users path. It also allows new macro and command files to be made by the user. You can also open the window from the menu-bar item "Edit".
From the runtime version of Lamp you have only access to the <code>*.prox</code> batch files.

To top

INTERNALS ACCESSIBLE FUNCTIONS

Lot of internal functions are accessible and can be called by user. Their descriptions can be visualised from the menu-bar item "Info".

IDL Help

The IDL? button activates full IDL on-line help, the ' ? ' button also gives a few tips on using functions and commands.

Instrument or Data Parameters

Each workspace has its own set of instrument parameters (eg. stored in p1(0) to p1(120) for w1, see Main Concepts ), these can be displayed and edited by pressing the Data Params button or from the menu-bar item "Info". For example if you extracted spectra from a workspace you would need to edit the Number of detectors by selecting the Workspace # and changing the number in the corresponding row.

To top

** Session Journal

All of the workspace operations that you perform (reading data, formulae entered etc.) are logged and can be viewed by pressing the button labelled The Journal which is on the right of the main LAMP interface and the menu-bar item "Info". There is also a print option to obtain a hard copy. This journal is saved in local directory as file lamp.jou

To top

** Saving the Session

The button labelled Save Lamp Session (presents also in the menu-bar item "File") saves the entire current status of LAMP. Next time LAMP is started (from the same directory or path as the session was saved in) the session can be restored, ignored or deleted. You may rename the file lamp.ses to prevent it being overwritten.

To top

** Exiting LAMP

The button EXIT from Lamp exits cleanly from LAMP and IDL.
N.B. If LAMP shows no response ie. appears to have " crashed " then close the shell window in which LAMP was started.

To top

Previous - 5. Manipulating Workspaces - Next