Skip to content
Snippets Groups Projects
Commit 7de9e928 authored by Wuttke, Joachim's avatar Wuttke, Joachim
Browse files

+ frida1

parent a3200095
Branches
Tags
1 merge request!5Import documentation from old dokuwiki
Showing
with 1485 additions and 0 deletions
The following people are acknowledged for their contribution in
maintaining the program in recent years.
------------------------------------------------------------------------
Tobias Unruh (TOFTOF @ FRM-II) provided us with a refined version\
of the Ida program existing at the FOCUS spectrometer at PSI.\
The original Focus Read In was written by Andreas Meyer (E13, TUM),\
and required a NeXus to Ascii converter program. To read in\
the HDF/NEXUS data directly a subroutine was written by\
Fanni Juranyi (FOCUS @ PSI) that has been modified by T. Unruh.\
A commented version of this read in routine is provided in this\
program for details see [(4.)](bugs).\
M. M. Koza maintained a version of IDA at ILL. For the release\
of Frida-1 the latest update of this version become not\
available to us. The backscattering read in routines adapted\
to new ILL standards will be included in the next release.\
There are a number of people working on the code over the past\
13 years. Their contribution is acknowledged within the source\
code. Details will be attached to a forthcoming version of this\
README.\
This page contains a number of currently known bugs or not properly
working features of the program.
------------------------------------------------------------------------
* In the current release the NEXUS Read in (RRT_In_Foc in i80.f) \\ is out-commented code. The switch used to call this routine\\ is also deactivated (i00.f). \\ To include the code the latest Version of NEXUS and HDF has \\ to be installed on the system. The napif.inc of the NEXUS \\ distribution shall be copied in the source tree of the Frida-1 \\ program. The Makefile has to be modified accordingly. \\ See commented library calls in the Makefile attached to \\ this release (LIBNAG definition and following lines). \\ Check for missing libraries on your system. \\
* The program dumps if a wrong file number is entered \\ while reading in DCS (//'rdcs'// command) data. Please \\ be careful on using the correct numbers. \\ Otherwise data might get lost if not saved prior to usage of //'rdcs'//. \\
* The multiphonon correction procedure //'_muc'// based \\ on code of R. Reichardt is still in a cryptic state. The source \\ code may provide you with some ideas.
Frida contains a quite extensive set of routines to fit data.\
For fitting of the data a Gauss-Newton algorithm is employed at the
moment.\
Fitting of the data makes use of the
[E04FCF](http://www.nag.co.uk/numeric/FL/manual/xhtml/E04/e04fcf.xml)
routine of the [NAG
FORTRAN](http://www.nag.co.uk/numeric/fl/FLdescription.asp) library.\
Frida allows to adjust a number of parameters such as the tolerance of
the fit\
etc.. The following page lists a description of the different commands
available\
in the curve fitting menu **c**.\
- **cc** creates a curve. The curves are selected by number. The
available curves are\
specified in the file *i66.f*. Some of the curves that make use of
externally provided\
numerical tables have subroutines defined in the file *i67.f*.
```{=html}
<!-- -->
```
- **cf** executes the fit of the curve created by **cc** to the data.
Upon execution\
this command asks for the file number of the data and possibly a
file to convolve this\
*analytical* function with, as well as which spectra of the file
should be fit.
```{=html}
<!-- -->
```
- **cp** allows to change the parameters of the curve created with
**cc** at any time.
```{=html}
<!-- -->
```
- **cpa** *parameters (alt)*
```{=html}
<!-- -->
```
- **ca** specifies auxiliary parameters, which are the fit range, and
wether\
the fit shall be weighted with stepwidth in *x*, error bars
associated to the\
data points, or logarithmically. The latter takes especially into
account if\
data is varying over several orders of magnitude as it is typically
the case for\
scattering laws measured by means of quasielastic neutron
scattering. Moreover, a\
flag can be set to specify that the analytical curve shall be
convolved with a\
another curve (e. g. resolution function).
```{=html}
<!-- -->
```
- **cnn** *new number*
```{=html}
<!-- -->
```
- **cs** allows to change standard parameters for the fit routine.
The parameters\
are \...
```{=html}
<!-- -->
```
- **ci** allows to extract the fit parameters from the fit curve
saving them into\
an integral file. Imagine the following: The scattering law *S(q,w)*
has been\
measured for several different *q*-values. *S(q,w)* is fit to a
model function\
e. g. a Lorentzian. The linewidth HWHM is one of the fit parameters
that varies\
with *q*. **ci** extracts this parameter with *q* as the *x*-grid
and HWHM as\
the *y*-grid.
```{=html}
<!-- -->
```
- **cg** creates a file that contains the curve on a grid which can
be specified to be\
the same as the data-file, linear, logarithmical, semi-lograthmic or
user-specified.\
This is e. g. useful if one wants to subtract the fit-curve from the
data file or the direct display of the function yields oscillations.
Frida is written in FORTRAN 77. Hence it uses static memory allocation.
Files are stored internally. Operation on\
files changes them also only internally. In order to show details about
these internally stored files, such as the\
file number, their title, whether the have been manipulated in any way,
etc., the directory commands starting with\
the letter *d* are used.
- **df** prints a directory of the files contained in the on-line
memory to the screen. A typical printout can be\
found [here](directdf).
```{=html}
<!-- -->
```
- **dp** prints data points of selected spectra to the screen. This
includes there x and y values as well as the\
error bars. A typical printout can be found [here](directdp). The
command works in two different ways: If there is only\
a single spectrum contained in the file the **dp** command asks
immediately for the number of channels\
(data points) that should be shown. In case of more than one
spectrum, the user is first asked for the\
number of the spectrum and in a second stage for the number of the
data points to be shown.
```{=html}
<!-- -->
```
- **ds** prints information of the spectra contained in the selected
files. The information provided are the\
z-values for every single spectrum, the number of points and the
x-range boundaries (minimum and\
maximum value). A typical output can be found [here](directds).
```{=html}
<!-- -->
```
- **dz** prints the z-values of selected files to the screen. A
typical output can be found [here](directdz).
FRIDA () df
13947940 lines free in run-time memory (99.6%)
1=32235msd _4Joooo 0.5 D2O q I dw S 41* 51
2 32280msd _4Joooo 0.5 D2O q I dw S 41* 51
3 32363msd _4Joooo 1.0 D2O q I dw S 41* 51
4 32486msd _4Joooo 0.5 D2O q I dw S 41* 51
5 32324msd _4Joooo 0.5 H2O q I dw S 35* 51
6 32573msd _4Joooo 0.5 H2O q I dw S 41* 51
7 32406msd _4Joooo 1.0 H2O q I dw S 41* 51
8 32529msd _4Joooo 0.5 H2O q I dw S 41* *
The first line of the output specifies the internal memory in number of
free lines. The important bit\
is the percentage number in brackets. Theres is no compression
associated with file storage in the\
internal memory. This means that the file size of the *\*.i96 file* as
it is seen on the harddisk roughly\
corresponds to the internal memory used.\
\
The first column of the output contains the file numbers associated with
different files. An equal sign\
in the second column defines the file as saved to the harddisk. The
third column corresponds to the\
filename. This is also the name under which the file is/was stored on
the harddisk. The fourth column\
contains flags specifying modifications that have been done with the
file (e. g. *\_4* defines that the *oi*\
command and its option *4* have been used, which means integration of
the data). The fifth column\
contains a more detailed file description. The sixth column is reserved
to the denominator of the\
x-values (In this case q for momentum transfer). The seventh column
contains the denominator of\
the y-values. Column eight defines the number of spectra and column nine
finally the number of\
channels associated with each spectrum. A star in column nine indicates
that the different spectra\
have different number of channels. The space available for all the
columns containing denominators\
or flags is limited. Hence not all information available and stored in
the associated variable might be\
shown.
FRIDA ( ) 1 dp
listing x-y for file 1
Spectrum no. (0=quit) [3] ? 3
Show which channels [1-4] ?
3# z1 = 160.0
ch 1 x = 0.420499 , y = 1.00943 +-0.6455E-01; dx = 0.4402E-01
ch 2 x = 0.464523 , y = 0.996659 +-0.6391E-01; dx = 0.4389E-01
ch 3 x = 0.508280 , y = 0.923375 +-0.5615E-01; dx = 0.4361E-01
ch 4 x = 0.551743 , y = 0.976414 +-0.6806E-01; dx = 0.4330E-01
Show which channels [-] ?
Spectrum no. (0=quit) [0] ?
FRIDA ( ) 1-2 ds
spectra of file 1
1# z = 150.0 n = 51 X = 0.4205 << 1.852
2# z = 155.0 n = 51 X = 0.4205 << 1.852
3# z = 160.0 n = 51 X = 0.4205 << 1.852
4# z = 165.0 n = 51 X = 0.4205 << 1.852
5# z = 170.0 n = 51 X = 0.4205 << 1.852
spectra of file 2
1# z = 150.0 n = 51 X = 0.4205 << 1.852
2# z = 155.0 n = 51 X = 0.4205 << 1.852
3# z = 160.0 n = 51 X = 0.4205 << 1.852
4# z = 165.0 n = 51 X = 0.4205 << 1.852
5# z = 170.0 n = 51 X = 0.4205 << 1.852
The first line of each block provides the file number associated to the
output produced in\
the following by **ds**.\
\
The first column contains the number of the spectrum. The second block
//z = // defines the\
z-values associated to the different spectra. In case of more than one
z-value per spectrum\
only the first is plotted to the screen. The third block //n = // shows
the number of channels\
each spectrum consists of. The last block //X = // shows the minimum and
maximum x-value\
associated with each spectrum, respectively. Channel number one would
correspond for\
ordered data to the minimal x-value, whereas the last channel would in
this case correspond\
to the maximum x-value.
FRIDA ( ) 1-2 dz
z coordinates of file 1
T [K]
1 150.0
2 155.0
3 160.0
4 165.0
5 170.0
z coordinates of file 2
T [K]
1 150.0
2 155.0
3 160.0
4 165.0
5 170.0
The set of commands starting with the letter **e** allows to edit
various properties of the files available\
in the online memory of FRIDA. The different command currently available
are:\
\
- **ec** prints the coordinate names of selected files to the screen.
It allows to change the name of the\
coordinates (x,y, and z-value denominators) as well as their unit.
In case of selecting more than\
one file the coordinates of all files are changed simultaneously to
the new set of coordinates. A\
typical output of *ec* can be found [here](editec).
```{=html}
<!-- -->
```
- **ed** prints the documentation of the selected files to the screen.
This command further allows to\
modify this information. Most of the information given by this
command is a track record of how the\
file has been modified. A typical output of produced by *ed* can be
found [here](edited).
```{=html}
<!-- -->
```
- **eg** allows to define the basic plotstyle for the data. There are
three different modes available.\
Selecting a number greater than zero will always plot the data as a
line, with its style defined by\
he chosen number. Selecting a negative number will always plot the
data using symbols for every\
data point. The symbol style is again defined by the chosen number.
The third option is to chose\
zero leading to an automatic selection of either symbols or lines
depending on whether the data\
to be plotted is real data or a fit curve, respectively. If more
than one curve is plotted selecting\
the automatic option will also ensure that every real data curve is
plotted with a unique symbol,\
whereas for fit curves always the same linestyle is used. Ad-hoc
changes may be done by using\
the command *gd*. Data output is black and white due to the
restrictions of Tektronix. Only in a\
later stage, once the PostScript figure has been created from the
plotted data, colours become\
available. Therefore different curves can only be distinguished by
differences in the plotsymbol or\
the chosen linestyle. A typical output generated by *eg* can be
found [here](editeg).
```{=html}
<!-- -->
```
- **ei** print integer data associated with a file to the screen.
These parameters can currently not be\
modified in any way other than editing the file stored on the
harddisk. Typically integer parameters\
are used by certain read-in routines in order to define generic
features of the data for later treatment.\
One example is for instance the definition of positive and negative
energy transfer and whether\
the file has been already symmetrized in case of inelastic neutron
scattering. A set of very common\
parameters shown in this case can be found [here](editei).
```{=html}
<!-- -->
```
- **er** prints a set of real parameters of the chosen files to the
screen. Already existing parameters\
can be modified by the user. New parameters can be appended at any
time. A typical output of\
this command including showcases for the usage of the different
options can be found [here](editer).
```{=html}
<!-- -->
```
- **ez** prints the z-coordinates of the chosen files to the screen.
There are different options available to\
append new z-parameters or to delete z-parameters. A typical output
generated by this command\
and some showcases to explain the different functions of this
command can be found [here](editez).
The following output is typical for using a single file. The first
column lists the different\
variables of the file. The second column contains the variable
denominators. The third\
column contains the units of the different variables. *A-1* is the
denominator for inverse\
Angstrom. The unit meV-1 stands for inverse millielectronvolt.
FRIDA ( ) 1 ec
x is q in A-1 for files 1 .. 1
y is S(2th,w) in meV-1 for files 1 .. 1
z1 is T in K for files 1 .. 1
\
The following output is created if two files with the same names and
units for the different\
variables are subjected to the *ec* command.
FRIDA ( ) 1,2 ec
x is q in A-1 for files 1 .. 2
y is S(2th,w) in meV-1 for files 1 .. 2
z1 is T in K for files 1 .. 2
\
The following output is created if two files with different names and
units for the different\
variables are subjected to the *ec* command. If the first file contains
a z-variable and the\
second file does not then a error message is shown instead of the
z-variables.
FRIDA ( ) 1,2 ec
x is q in A-1 for files 1 .. 1
x is T in K for files 2 .. 2
y is S(2th,w) in meV-1 for files 1 .. 1
y is D in m^2/s for files 2 .. 2
z1 is T in K for files 1 .. 1
z1 is P in bar for files 2 .. 2
An important point of any program dealing with data reduction is\
the ability to visualize or print data in a fast and reliable way. For\
this purpose a short introduction to the plotting capabilities of
Frida-1\
is given below.\
- We gratefully acknowledge the work of H. P. Schildberg providing\
together with Joachim Wuttke a PostScript header file with
intriguing\
user commands.
```{=html}
<!-- -->
```
- The latest modification of the header file *\'wups05a.ps\'* and a\
previous version *\'wups97a.ps\'* are attached to this release.\
The first file now allows also for correct printing of error bars
in\
logarithmic y-axis environments.\
- *\'g3.ps\'* contains basic definitions of the linestyle and general\
layout of a file printed from the Frida-1 program to the\
harddisk.
```{=html}
<!-- -->
```
- *\'g2.ps\'* has been issued to the program package from frida-1-2\
onwards. This file is a merger of the *\'wups05.ps\'* file
containing the\
header definitions and the formerly described file *\'g3.ps\'*.
```{=html}
<!-- -->
```
- A figure shown in the Textronix window can be printed by typing\
*\'gp \<file-name.ps\>\'* at the command line. If *\<file-name.ps\>*
is\
omitted a file *\'l\#.ps\'* with *\'\#\'* being the smallest not yet
existing\
number is created. The ps-file contains the file g2.ps, axis\
definitions and the data provided by Frida-1. The created figure
can\
be readily opened with a PostScript viewer.
```{=html}
<!-- -->
```
- For creating a file containing multiple figures at once, the new\
command *gs* has been implemented. Using this command instead\
of *gp* creates the postscript file without the *\'wups05a.ps\'*
header\
defining the different non-Standard PostScript commands used\
in the file. This makes it easier to concatenate a number of
PostScript\
files created in this way to a single file. To print or visualize
files\
created with *gs* the header *\'wups05a.ps\'* has to be attached by\
e. g. *\'cat wups05a.ps file.ps \> \~/P.ps\'*. The latter may be
defined\
as *alias \'gn\'* in your *\'.bashrc\'*.
```{=html}
<!-- -->
```
- In the file *\'g3.ps\'* as well as at the bottom of *\'g2.ps\'*
there are a\
number of switches that allow to modify the ps-file. A figure
containing\
a number of different possibilities like Greek letters,
annotations,\
lists for curve descriptions can be obtained upon request from
Florian\
Kargl.
The prompt IDA normally is followed by a list of default-files.
Most commands operate on these files. To operate on other files,
enter a new filelist, followed by a command or not.
\*f
IDA> command group f*
(files: input, output, creation,
reorganisation in on-line-memory)
fl = load from disk
fm = make
fc = copy
fdel= delete
fx = exchange (fc and fdel)
fw = write to disk
\*fl
IDA () fl <filename> : load file(s)
Load data files into on-line memory.
Usage : with argument : load one file
without argument : loop (reply nothing [RETURN] to exit)
If File names are given without extension, the program looks first
for ".dat", then for ".asc".
File formats : ILL-CrossX, IDA-binary, or IDA-ASCII
Source : FileWrite in i2.f, colling LoadSpectrum in i1.f
\*fw
IDA (file-nos) fw : write file(s)
Save internal files on external device.
Any files hold in IDA's on-line memory can be saved, including curves.
As external filename, any valid path name is accepted. If filenames
are given without extension, files will be saved as ".dat", except
if ASCII-format is chosen in which case the extension will be ".asc".
Recommended storage format is IDA-binary; use IDA-ASCII if data shall
be send to sites with different operating system.
Source : FileLoad in i2.f, calling SaveSpectrum in i1.f
\*fdel
IDA (file-nos) fdel : delete files
Files are deleted from on-line memory.
There is no way to recover deleted files. Use "fw" to save results.
Source : FileKill in i3.f, calling FileDel in i2.f
\*fc
IDA (file-nos) fc : copy files
Duplicate files in on-line memory.
Source : FileCopy in i3.f
\*fx
IDA (file-nos) fx : exchange order of files
Files are copied to the end of the on-line memory,
then deleted from their original positions.
Source : FileCopy and FileKill in i3.f
\*fm
IDA () fm : make a new file
Create a new on-line file.
This option is used to enter data manually, or to convert foreign formats.
It includes the older conversion program any2ied.
For converting foreign data formats, first go through the interactive
questions section. Then, the program asks to enter spectra in a format
you have determined before. At this point, use "\ie <filename>" to read
the data points from an external file.
Source : FileMake in i3.f
This page contains the general information related to the FRIDA-1 source
code and the copyright information.
------------------------------------------------------------------------
Copyright Disclaimer FRIDA (fast reliable inelastic data analysis)\
[\<http://frida.sourceforge.net\>](http://frida.sourceforge.net) is a
program for generic spectral\
analysis, with many specialized routines for inelastic neutron\
scattering. The FORTRAN version Frida-1 is an updated version of\
Joachim Wuttke\'s IDA, with contributions from the community. The\
maintainer is Florian Kargl <f_kargl@users.sourceforge.net>.\
FRIDA is released under the GNU public license.\
(C) Joachim Wuttke 1990-2001\
(C) Florian Kargl 2006\
\-\-\--
The program consists of a number of modules containing subroutines\
providing the general program structure and allowing for different\
kinds of data treatment.\
\
The source code can be found on
[\<http://sourceforge.net/projects/frida\>](http://sourceforge.net/projects/frida)\
\
General information regarding the different modules can be found\
in *\"i00.f\"*. Subsequent information is found in the modules
themselves.\
\
A more detailed information can be found on
[\<http:*frida.sourceforge.net\>\]\].\
\
Details on the project status will be posted via the mailing list of
the\
project on
\[\[http:*sourceforge.net/projects/frida\|\<http://sourceforge.net/projects/frida\>](http://frida.sourceforge.net).\
\
The README file contains information on persons [(2.)](Ackn) involved
in\
the project and providing different versions of the program\
maintained in different locations. These versions have been merged\
in this first release.\
Details regarding the installation procedure on a Linux platform\
are found under [(3.)](Instr).\
Known problems arising during the installation are listed in\
[(4.)](Bugs). Here, a list of not yet fully implemented read in
routines\
is posted.\
[(5.)](figpr) contains information regarding the printout of figures
and\
their modification.\
\*gp
IDA () gp <ps-filename> : graphic to postscript
Write the graphic actually shown in the Tektronix window
in a PostScript file. Works even after the Tektronix window
has been closed.
The default filename is l<n>.ps, where <n> is the lowest
integer for which no such file already exists.
The PostScript file may subsequently be modified using
a text editor. Search for the string "Switchboard" for the
most relevant commands.
Source : GraSoftCopy in g2.f
\*g:
IDA () g: : list graphic setup
List setup of the chosen graphic window.
Use "gw" to change the window.
Source : GraChoice in g2.f
\*gw
IDA () gw <window-no> : select graphic window
A graphic window is here the ensemble of all parameters defining
a graphic setup, like coordinate bounds, symbol size, and toggles
between linear/logarithmic scales and so on. It is useful to switch
between graphic windows when functions of incommensurable coordinates
with completely different x- and y-bounds are to be plotted.
Different graphic windows do NOT correspond to different windows
on the X-terminal.
Source : GraChoice in g2.f
**[Frida-1](Frida-1):** old IDA documentation: command reference, File
\"Ida.hlp\"
Here is the list of the subroutines and what they are doing:
- i00 : main program
- i01 : plot
- i10 : input/output
- i20 : on-line memory
- i23 : directories, editing, r/z-handling
- i25 : file copy, delete, make
- i30 : file manipulations, auxiliary calculations
- i32 : general functions and symbolic calculation
- i40 : manipulations on data / per channel
- i41 : manipulations on data / per spectrum
- i42 : manipulations on data / per file
- i43 : special manipulations on data
- i50 : operations on data
- i60 : curves and fit
- i66 : collection of fit functions
- i67 : very special fit functions
- i70 : rescaling operations
- i71 : Fourier transforms
- i72 : neutron kinematics, constant-q
- i73 : density of states
- i74 : self absorption
- i75 : nuclear forward scattering
- i76 : mode coupling integration
- i77 : full mode coupling model ! LINK ONLY WHEN NEEDED
- i80 : raw data read / neutron scattering
- i87 : raw data read / light scattering
- i94 : simulation / multiple scattering ! LINK ONLY WHEN NEEDED
- i95 : simulation / optics
```{=html}
<!-- -->
```
*this$file
Ida.hlp
last change 3mar94
contains on-line help for IDA
*Ida
IDA () main command line.
Short commands :
p = plot
a = add to plot
qui = quit IDA
Command groups :
f* = files (input, output, ..)
d* = directory (and modification of file headers)
e* = edit parameters
m* = manipulations (delete, sum, interpolate, ..)
o* = operations (arithmetics)
t* = transforms (Fourier, ..)
_* = incorporated programs
r* = raw data input
c* = curves and fits
g* = graphics
i* = info
For lists of command groups, enter the first letter.
For help on specific commands, try '? ' followed by the command.
The prompt IDA normally is followed by a list of default-files.
Most commands operate on these files. To operate on other files,
enter a new filelist, followed by a command or not.
*f
IDA> command group f*
(files: input, output, creation,
reorganisation in on-line-memory)
fl = load from disk
fm = make
fc = copy
fdel= delete
fx = exchange (fc and fdel)
fw = write to disk
*fl
IDA () fl <filename> : load file(s)
Load data files into on-line memory.
Usage : with argument : load one file
without argument : loop (reply nothing [RETURN] to exit)
If File names are given without extension, the program looks first
for ".dat", then for ".asc".
File formats : ILL-CrossX, IDA-binary, or IDA-ASCII
Source : FileWrite in i2.f, colling LoadSpectrum in i1.f
*fw
IDA (file-nos) fw : write file(s)
Save internal files on external device.
Any files hold in IDA's on-line memory can be saved, including curves.
As external filename, any valid path name is accepted. If filenames
are given without extension, files will be saved as ".dat", except
if ASCII-format is chosen in which case the extension will be ".asc".
Recommended storage format is IDA-binary; use IDA-ASCII if data shall
be send to sites with different operating system.
Source : FileLoad in i2.f, calling SaveSpectrum in i1.f
*fdel
IDA (file-nos) fdel : delete files
Files are deleted from on-line memory.
There is no way to recover deleted files. Use "fw" to save results.
Source : FileKill in i3.f, calling FileDel in i2.f
*fc
IDA (file-nos) fc : copy files
Duplicate files in on-line memory.
Source : FileCopy in i3.f
*fx
IDA (file-nos) fx : exchange order of files
Files are copied to the end of the on-line memory,
then deleted from their original positions.
Source : FileCopy and FileKill in i3.f
*fm
IDA () fm : make a new file
Create a new on-line file.
This option is used to enter data manually, or to convert foreign formats.
It includes the older conversion program any2ied.
For converting foreign data formats, first go through the interactive
questions section. Then, the program asks to enter spectra in a format
you have determined before. At this point, use "\ie <filename>" to read
the data points from an external file.
Source : FileMake in i3.f
*d
IDA> command group d*
(directory of on-line memory,
inspection and modification of file headers)
df = list of files
dz = list of spectra
dd = list of data entries
di = inspect integer parameters
dr = inspect (and modify) real parameters
dt = inspect (and modify) text parameters
dg = inspect (and modify) graphic parameters
*df
IDA () df : directory of on-line files
Source : FileInfo in i2.f
*dz
IDA (file-nos) dz : directory of spectra
For given files, list all spectra with their z-values
and their x-data ranges.
Source : FileInfo in i2.f
*dd
IDA (file-nos) dd : directory of data entries
For given files, ask for spectra and channels to list,
Source : FileInfo in i2.f
*di
IDA (file-nos) di : inspect integer parameters
Source : FileInfo in i2.f
*dr
IDA (file-nos) dr : inspect (and modify) real parameters
Source : FileRPar in i3.f
*dt
IDA (file-nos) dt : inspect (and modify) text parameters
Source : FileTPar in i3.f
*dg
IDA (file-nos) dg : inspect (and modify) graphics parameters
Source : FileGPar in i3.f
*mca
IDA (file-nos) mca : add channels
For each spectrum of given input files, channels are grouped
together : x and y will be replaced by their average values.
Groups are to be specified in ordered list format, e.g. if there
are 12 channels, "*i3" (which is shorthand for "1,4,7,10") means that
there will be four groups containing channels 1-3,4-6,7-9, and 10-12.
If some spectra of one file are defined on different subranges of a
common grid, the new groups can be set with respect to the common grid.
If spectra have different length and there is no common grid, groups
must be specified individually for each spectrum.
Source : OrgChSum in i4.f
*mcd
IDA (file-nos) mcd : delete channels
For each spectrum of given input files, some channels can be deleted.
The channels that shall NOT be deleted are to be specified, either by
their numbers in ordered list format, or by their x- or y-values.
Channel specification from files is decouraged.
If channels are specified by numbers, all spectra of one file are
compared in order to decide whether there is a common x-grid; in this
case, numbers can be specified with respect to the common grid.
If spectra have different length and there is no common grid, channel
numbers must be given individually for each spectrum.
Source : OrgChCut in i4.f
*mco
IDA (file-nos) mco : sort channels
Sort each spectrum of given input files in ascending order in x.
If there is more than one occurence of some x-value, the corresponding
channels are grouped together, taking the average y-value.
Source : OrgChSort in i4.f
*msa
IDA (file-nos) msa : add spectra
For each input file, replace spectra by groups of spectra.
For each group, channel by channel, input y are replaced by their
average values.
Groups are to be specified by the number of the first old spectrum
of each new group, in ordered list format.
If spectra have different x-grids but the same number of channels,
it is possible to proceed by channel numbers. New x-values are then
set by averaging over input files. It recommended, however, to first
regroup the data onto a common grid (using "mgr") before using "msa".
Source : OrgSpectraSum in i4.f
*msd
IDA (file-nos) msd : delete spectra
For each input file, delete some spectra.
The spectra to be deleted are to be specified in ordered list format.
Answer "-" (empty list) to escape.
Source : OrgSpectraCut in i4.f
*mso
IDA (file-nos) mso : sort spectra
For each input file, sort spectra by their z-value. The contents
of the spectra themselves is not changed.
Source : OrgSpectraSort in i4.f
*msj
IDA (file-nos) msj : join spectra
For each input file, group some spectra together. Output spectra
are build by simply appending input spectra one after each other.
Optionally, channels can be sorted (same as calling "mco").
Groups are to be specified the same way as in "msa".
Source : OrgSpectraJoin in i4.f
*msx
IDA (file-nos) msx : exchange spectra <-> channels
For each input file, exchange x- and z-coordinate.
Evidently, all spectra must be defined on a common x-grid.
Source : OrgSpectraExch in i4.f
*mfs
IDA (file-nos) mfs : sum spectra of different files
It supposed that the input files have commensurable z-scales.
Then, all spectra sharing the same z are averaged to form one
output spectrum (whether two z's are considered equal is controlled
by a "tolerance" parameter).
The averaging can only be done, if the x-grids are identical.
Source : OrgFileJoin in i4.f
*mfj
IDA (file-nos) mfj : append files into one file
Simply, make one file out of several input files.
Say, there are 2 files with 3 spectra each : (ABC) and (abc).
Then, the output file will contain either (ABCabc) (option "file
after file"), or (AaBbCc) (option "spectrum after spectrum").
The spectra themselves remain unchanged (except if "msj" is
called at the end).
Source : OrgFileJoin in i4.f
*mfx
IDA (file-nos) mfx : exchange files <-> spectra
Suppose, spectra y(x) have been measured for different values
of two parameters U and V. Originally, spectra with the same U
may have been grouped into files with a real-parameter r(n)=U,
and V has a z-coordinate. The operation "mfx" regroups them into
files with the same real-parameter r(n')=V and a z-coordinate U.
Source : OrgFileJoin in i4.f
*mgi
IDA (file-nos) mgi : new x-grid, interpolate y
Choose a new x-grid, then determine y(x) on this grid by
interpolation of input data.
Options for choosing a grid are :
> from a file f2
> > (1:1) for each output spectrum one spectrum of f2
with same z is searched for
> > (select one) one spectrum of f2 defines the grid for all output
> regular grid
> > (lin) X(i) = X(1) + [X(n)-X(1)]*[(i-1)/(n-1)]
> > (log) X(i) = X(1) * [X(n)/X(1)]^[(i-1)/(n-1)]
> > (1/2-log) starts logarithmically at X(1)=-X(n), becomes linear
around 0 (from -crossover to +crossover), then
returns to logarithmic increase until X(n).
Source : OrgGrid in i4.f
*mge
IDA (file-nos) mge : new x-grid, extrapolate y
Choose a new x-grid, then determine y(x) on this grid by
interpolation and extrapolation.
Options for extrapolations include
> by 0
> by any other given value
> by value of nearest neighbours
Options for choosing a new grid are the same as for mgi (see there).
Source : OrgGrid in i4.f
*mgr
IDA (file-nos) mgr : new x-grid, redistribute y
Choose a new x-grid, then determine y(x) on this grid by
redistributing histogram intensities of input data.
Options for choosing a new grid are the same as for mgi (see there).
Source : OrgGrid in i4.f
*mgd
IDA (file-nos) mgd : new x-grid, reduce input
Choose a new x-grid. If there are several x on input which
fall into the same interval of the new grid, only one x-y pair
per interval is retained, the other input data are thrown away.
This option is needed for producing final output, when experimental
data had to be temporarily interpolated onto a finer grid.
Options for choosing a new grid are the same as for mgi (see there).
Source : OrgGrid in i4.f
*ox
IDA (file-nos) ox <function <2nd argument>> : operate on x
Replace x by a function of x and possibly a second argument.
Examples : "6-8 ox / ef" devides x by a constant which will be asked
for individually for each of the input files 6-8;
"7 ox $ x'" replaces x by x' of another file (the number
of which will be asked for)
Source : OprPoint in i5.f
*oy
IDA (file-nos) oz <function <2nd argument>> : operate on y
Replace y by a function of y and possibly a second argument.
Examples : "6 oy * i" multiplies y by an argument y'(z) which
will be read from another file
"1-2 oy $/ d" replace y by dy/y, where dy will be taken
from the same input files 1-2 as y
Source : OprPoint in i5.f
*oz
IDA (file-nos) oz <function <2nd argument>> : operate on z
Replace z by a function of z and possibly a second argument.
Source : OprPoint in i5.f
*oi
IDA (file-nos) oi : calculate an integral property
For a spectrum y(x), a property i[y(x)] is calculated.
Examples: maximum value of y,
x at maximum of y,
integral I dx y(x).
If there is only one input spectrum, the output is a single number.
If the input file contains several spectra, the output is saved
as a file containing the spectrum i(z).
Source : OprIntegral in i5.f
*ot
IDA (file-nos) ot : clone y(x) into a tensor product y(x,z)
Suppose you have one spectrum y(x), and you want to manipulate
this spectrum for different values of a parameter p.
A convenient way to achieve this is to expand y(x) into a file y(x,z),
consisting of a set of identical spectra y(x) with z=p.
You can either read z from another file or specify a regular grid.
Source : OprTensor in i5.f
*p
IDA (file-nos) p <spectra-nos> : plot
Plot the input files.
When called for the first time, this command opens a graphic window;
on later calls, previous plots are cleared.
Use "a" to add more spectra into existing plot.
See "g*" commands for more graphic options.
Source : IdaPlot in i0.f, calling the graphic library g*.f
*a
IDA (file-nos) a <spectra-nos> : add
Add more spectra to existing plot.
See 'g*' commands for more graphic options.
Source : IdaPlot in i0.f, calling the graphic library g*.f
*gp
IDA () gp <ps-filename> : graphic to postscript
Write the graphic actually shown in the Tektronix window
in a PostScript file. Works even after the Tektronix window
has been closed.
The default filename is l<n>.ps, where <n> is the lowest
integer for which no such file already exists.
The PostScript file may subsequently be modified using
a text editor. Search for the string "Switchboard" for the
most relevant commands.
Source : GraSoftCopy in g2.f
*g:
IDA () g: : list graphic setup
List setup of the chosen graphic window.
Use "gw" to change the window.
Source : GraChoice in g2.f
*gw
IDA () gw <window-no> : select graphic window
A graphic window is here the ensemble of all parameters defining
a graphic setup, like coordinate bounds, symbol size, and toggles
between linear/logarithmic scales and so on. It is useful to switch
between graphic windows when functions of incommensurable coordinates
with completely different x- and y-bounds are to be plotted.
Different graphic windows do NOT correspond to different windows
on the X-terminal.
Source : GraChoice in g2.f
*cc
IDA (file-nos) cc : create curve
Create a curve for fitting the input files.
Curves are saved internally like data files; they can be written
to external files with "fw", they can be plotted with "p" and "a",
but most other operations are meaningless with curves.
Source : CuCreate in i6.f
*i
IDA> command group i* (info on the state of the program)
ia = array dimensions'
*eoi
**\"Frida-1\"** installation instruction.
This page contains for the moment installation instructions for FRIDA-1
on a Linux PC. The installation procedure depends on whether you need to
compile the program or you have an already compiled version which you
just want to port to another computer. If the latter is the case, skip
the first section and start directly with the
[\#Installation](#Installation).
In the following, it assumed that you have root access and want to
install Frida-1 in the directory `/opt/ida/` If you do not have root
access or do not want to use that directory for other reasons, you can
easily replace the path with the one according to your preferences. The
following has to hold:
- In the file *i00.f*, there has to be a correct path to the file
*frida1.su* or *ida.su*, depending on your version of Frida-1,
before compilation. If you have only the compiled file, you have to
stick to the directories listed there.
- The file (*frida1.su*\|*ida.su*) has to be in one of the directories
named in *i00.f* and contain the correct paths to the executable and
the ps-files.
### Compilation
##### prerequisites
Attention: commercial (= pay a lot) libraries (NAG) and compiler
(Absoft) are needed to **compile** (not to run the compiled) Frida-1. If
an Absoft compiler is not available for you, you may ask for an
executable by writing an email to floriank at chalmers.se.
- **Absoft compiler is necessary for proper compilation**
- unzip and untar the source code with `tar -zxvf frida-1-0.tgz` This
will unpack the data in a new directory FRIDA1. Do it in a place
where you want to compile the program (this does not need to be the
place from where you want to run it later on). The subdirectory
//for/num/ // contains numerical tables for fitting.
- create subdirectories *oba* and *exa*
- make sure that you have access to external libraries:
- NAG: libnag.a (NAG FORTRAN 77 library)
- G2C: libg2c.a
- M: libm.a
##### configure
- The respective paths for the external libraries has to be set
accurately in the Makefile
- NeXus support for FOCUS at the Paul Scherrer Institut, Switzerland,
is now available! For using the FOCUS read-in routine, link also to
the additional libraries (NeXus, hdf5, mfhdf, df, z, and jpeg); if
the NeXus libraries for FOCUS support are not available, comment the
FOCUS read in routine in i80.f
- include or exclude optional modules (MCT, MSC etc.) in the Makefile.
- Note: if MSCAT shall be executable, modify Makefile by including
*i94.f* in compilation procedure. Change i00.f removing the
comment signs at '\_mss'.
- If the full mode coupling model shall be used, remove comment
signs at \"\_fmm\" in *i00.f*.
- caveat: for the moment libraries are statically linked
- modify path for (*frida1.su*\|*ida.su*) in *i00.f* to the directory
you want to put the su-file. This file contains some basic
information, for example the directory of the Frida-1 executable. As
this will not change regularly, you do not need to keep it in a
place easily accessible (like your home directory) but you can. In
the following, it will be assumed that (*frida1.su*\|*ida.su*)
resides in the // /opt/ida/ // directory, as well. The *i00.f*
should then contain a section similar to
` ! search for the setup file :
CALL ExeML ('\i ida.su', aus)
IF (aus(1:4).ne.'\i +') CALL ExeML ('\i ../ida.su', aus)
IF (aus(1:4).ne.'\i +') CALL ExeML ('\i ../../ida.su', aus)
IF (aus(1:4).ne.'\i +') CALL ExeML ('\i ~/ida.su', aus)
IF (aus(1:4).ne.'\i +') CALL ExeML ('\i /opt/ida/ida.su',
* aus)
` When launched in some directory, Frida-1 will look in this very
directory for an (*frida1.su*\|*ida.su*), then in the parent
directory, then in the grandparents\' ;-) directory, then in your
home, and finally in // /opt/ida/ //. The first one it finds will be
used.
##### make
- compile program by \<code\> make -f Makefile \</code\> or simply
`make` in the source directory
- the object files are created in the *oba* subdirectory
- if the compilation is successful, an executable *frida1* is
created in the *exa* subdirectory
### Installation
##### prerequesites
- A compiled version of Frida-1
- If you want to use the graphics window of Frida-1, you need to have
an xserver and for example the terminal *xterm* installed. Any other
terminal providing Tektronix support performs equally well. You do
*not* need Absoft, NAG, etc.
##### make install
- You can use the directory as it is after the compilation for running
Frida-1. However, only few files are actually needed for running so
you can copy them to a place where you want to run it from (this is
for example required if you compiled Frida-1 on another machine than
you want to run it from). The following files are
required:`> ls /opt/ida/
frida1 g2.ps g3.ps g4.ps Ida.hlp ida.su wups05a.ps wups97a.ps
` Except the file *frida1* which is in the subdirectory *exa*, all
files are directly in the directory you compiled Frida-1 in.
- modify path variables in (*frida1.su*\|*ida.su*) according to your
needs. In the given example, it should then contain a section
`% ida default setup in ida.su
\p dir-hlp /opt/ida
\p fil-gra-def.ps /opt/ida/g3.ps
\p fil-gra-ful.ps /opt/ida/g2.ps
\p fil-gra-app.ps /opt/ida/g4.ps
\p dir-num /opt/ida/for/num/
` In case you want to install Frida-1 in another directory or left
it in the directory structure it compiled in, simply adjust the
paths. You are somewhat limited in the choice of directory for the
(*frida1.su*\|*ida.su*) as it has to be in a place specified in the
*i00.f* file ([see above](#configure)). However, the other files can
be placed at discretion as long as the correct path is given in the
(*frida1.su*\|*ida.su*).
##### run
- Frida-1 should be run in a xterm window to have the graphics
available. You start xterm simply by calling `xterm` in a shell. The
directory you launch it from will be the directory in which Frida-1
looks for the data and saves the files, images, etc.
- To start Frida-1, you simply run the command `/opt/ida/exa/ida` in
the xterm
- If on startup the message \<code\> Could not load setup file ida.su
\</code\> appears, the (*frida1.su*\|*ida.su*) is not in a directory
specified in your *i00.f*. Please check the directories listed there
and place the (*frida1.su*\|*ida.su*) accordingly.
##### shortcut
- To avoid having to start an xterm and enter all the path to the
Frida-1 executable every time you want to start, it is convenient to
define a shortcut \<code\> frida-1 \</code\> There are two ways of
doing so which both require bash installed on your system: The first
one requires write access to the directory // /usr/local/bin/ //,
the second doesn\'t but can sometimes be a bit cumbersome (and has
to be adjusted if your standard shell is not bash).
1. Create the file // /usr/local/bin/frida-1 // containing
`#! /usr/bin/env bash
xterm -title 'Frida-1 Linux Version' -sb -sl 5000 -bg white -fg black -cr chartreuse -fn 8x13 -g 80x58+0+0 -e /opt/ida/exa/ida &
` and make it executable
2. Alternatively, assuming that your terminal is bash \-- you can
check launching \<code\> echo \$SHELL \</code\> it is possible
to define an alias in the *.bashrc* file in your home directory
which will be read when a new terminal is started. To do so,
open the *.bashrc* in a text editor and add the following line
at the end (or create the file if it didn\'t exist before):
\<code\> alias frida-1=\"xterm -title \'Frida-1 Linux Version\'
-sb -sl 5000 -bg white -fg black -cr chartreuse -fn 8x13 -g
82x27+2+358 -e /opt/ida/exa/ida &\" \</code\> Close the terminal
and start a new one.
The following page contains installation instructions\
contained in the README file attached to the source code\
distribution. Respecting the user support this file\
contains some additional information compared to the\
standard readme instructions posted on the Frida-1 wiki site.\
##### Linux Absoft Compiler !!
- pre installation instructions
```{=html}
<!-- -->
```
* unzip and untar the source code \\ **tar -zxvf frida-1-0.tgz** \\ will unpack the data in a new directory FRIDA1. \\ Subdirectory **for/num/** contains numerical tables for fitting.
* create subdirectory 'oba'
* create subdirectory 'exa'
* Note: if MSCAT shall be executable, modify Makefile by including 'i94.f' \\ in compilation procedure. \\ Change i00.f removing the comment signs at '_mss'.
* If the full mode coupling model shall be used, \\ remove comment signs at '_fmm' \\ in i00.f.
- requirements
```{=html}
<!-- -->
```
* libnag.a (NAG FORTRAN 77 library)
* libg2c.a
* libm.a
- installation
```{=html}
<!-- -->
```
* type //'make -f Makefile'// or simply //'make'// in source directory
* the object files are created in the //'oba'// subdirectory
* if the compilation is successful a executable //'frida1'// is created \\ in the //'exa'// subdirectory
- post installation instructions
```{=html}
<!-- -->
```
* to invoke Frida-1 a x-terminal or any terminal providing \\ Tektronix support is mandatory for full graphical capabilities.
* Note: In a standard shell only the text base part is working.\\ No visualization is possible.
* it might be convenient to define the following //alias// in the //'.bashrc'//: \\ \\ **//alias i="xterm -title 'Frida-1 Linux Version 1.0' -sb -sl 5000 -bg white -fg black \\ -cr chartreuse -fn 13x8 -g 82x27+2+358 -e /home/user/Frida1/exa/frida1 &"//** \\ \\ modify path according to where frida1 is located on the harddisk.
##### Linux GNU Compiler !!
* The posted version cannot be compiled with the standard GNU compiler shipped with\\ standard Linux versions for PC. A major problem is the string handling and some intrinsics.\\
* The sgtring handling problem was partly solved by Christian Geisler.\\ However, the program (not this release) has still to be tested for some minor bugs.
##### SGI workstation !!
* Compilation on a SGI workstation should in principle be possible. \\ Be aware off using the correct l0sgi.f instead of l0x11.f in the Makefile.
**MANUAL PAGE** for [FRIDA-1](frida-1)
This page is intended to contain the manual for the usage of
[Frida-1](frida-1).
The manual is intended to be created on a voluntary basis of all
[Frida-1](frida-1) users. Parts of the manual shall be sent to one of
the maintainers of this page (preferably Florian Kargl).
The manual is structured in main groups according to the *i00.f* file.
The different commands in those main groups shall be explained in
alphabetic order.
- [c\*: curve](curve) creation, manipulation and fitting of data
- [d\*: directory and data](dir-prop) listing
- [e\*: editing](edit) of file-content in online memory
- [f\*: file](file) manipulation
- [g\*: graphical](graph) routines (plotting and storage to disk)
- [m\*: manipulation](manip) of online data
- [o\*: operation](opera) on online data
- [r\*: read-in](read-in) routines
- [\_\*: special](unders) routines for manipulation of data
- [t\*: transformation](transf) of online data
* **mcd** = channels delete
* **mca** = channels add
* **mcaa**= channels add automatically
* **mco** = channels order (sort/sum)
* **mcg** = channels determine groups
* **mcm** = channels y -> f(y)
* **mch** = channels histogram binning
* **mcx** = channels x <-> y
* **mcs** = channels break into spectra
* **mgi** = grid interpolate
* **mge** = grid extrapolate
* **mgd** = grid delete
* **mga** = grid add
* **mgr** = grid redistribute
* **mgh** = grid points -> histogram
* **msd** = spectra delete
* **msa** = spectra add
* **msaw**= spectra add (weighted)
* **msj** = spectra join
* **mso** = spectra order
* **msx** = spectra exchange <-> channels
* **mfj** = files join
* **mfs** = [not implemented] files sum
* **mfx** = [not implemented] files exchange <-> spectra
In the **o**-menu,
- **oi** = integral properties
```{=html}
<!-- -->
```
* **1** simply z
* **2** one value x
* **3** one value y(x)
* **4** integral dx y(x)
* **5** value y_max
* **6** value y_min
* **7** position x of y_max
* **8** position x of y_min
* **9** match #K to #K-1
* **10** quality of match
* **11** match #K to #K'
* **12** quality of match
* **13** half width
* **14** integral-de-luxe
* **15** sum
* **16** average
- **ox** = pointwise operation on x
```{=html}
<!-- -->
```
- Function?
* **0** (= ) lhs = x
* **1** (ln ) lhs = ln x
* **2** (lg ) lhs = lg x
* **3** (e^ ) lhs = exp x
* **4** (^2 ) lhs = x^2
* **5** (^1/2 ) lhs = x^1/2
* **6** (10^ ) lhs = 10^x
* **7** (0- ) lhs = -x
* **8** (1/ ) lhs = 1/x
* **9** (|| ) lhs = |x|
* **11** (sin ) lhs = sin x
* **12** (asin ) lhs = asin x
* **13** (cos ) lhs = cos x
* **14** (acos ) lhs = acos x
* **16** (atan ) lhs = atan x
* **21** (sind ) lhs = sind x
* **22** (asind) lhs = asind x
* **23** (cosd ) lhs = cosd x
* **24** (acosd) lhs = acosd x
* **31** (sinh ) lhs = sinh x
* **32** (cosh ) lhs = cosh x
* **41** (Gamma) lhs = Gamma(x)
* Binary Operations :
* **50** (~ ) lhs = #2
* **51** (+ ) lhs = x+#2
* **52** (- ) lhs = x-#2
* **53** (~- ) lhs = #2-x
* **54** (* ) lhs = x*#2
* **55** (/ ) lhs = x/#2
* **56** (~/ ) lhs = #2/x
* **57** (^ ) lhs = x^#2
* **58** (min ) lhs = min(x,#2)
* **59** (max ) lhs = max(x,#2)
* **60** (mod ) lhs = x|#2
* Ida-defined functions :
* **81**(q ) : lhs = q(2th=x;E0=#2)
* **82**(tof_w) : lhs = tof(w=x;E0=#2)
* **83**(w_tof) : lhs = w(tof=x;E0=#2)
* **84**(Dki ) : lhs = Dki(w=x;E0=#2)
* **85**(2th ) : lhs = 2th(q=x;E0=#2)
* **86**(a_mct) : lhs = a_mct(lambda=x)
* **87**(b_mct) : lhs = b_mct(lambda=x)
- 2nd argument?
* **ec** : one value for all files, enter once
* **ef** : one value per file, enter per file
* **if** : one value per file, take from one-point-file
* **r** : one value per file, take a real parameter
* **r2y** : one value per file, take y'(real-par) from 2nd file
* **es** : one value per spectrum, enter per spectrum
* **z<n>**: one value per spectrum, take z<n>
* **i** : one value per spectrum, take y'(z) from 2nd file (integral file)
* **i1** : one value per spectrum, take y'(z) from 2nd file (integral file, old 1dim version)
* **ep** : one value per point, enter per point
* **x** : one value per point, take x
* **y** : one value per point, take y
* **d** : one value per point, take d
* **n** : one value per point, take number of point
* **y2** : one value per point, take y'(x) from 2nd file
* **d2** : one value per point, take the error dy'(x) from 2nd file
* **^[** : escape
- **oxs** = dito, selected subrange
- same options as for ox
```{=html}
<!-- -->
```
- **oy** = pointwise operation on y
- same options as for ox
```{=html}
<!-- -->
```
- **oys** = dito, selected subrange
- same options as for ox
```{=html}
<!-- -->
```
- **oz** = pointwise operation on z (also oz1, oz2, \...)
- same options as for ox
```{=html}
<!-- -->
```
- **of** = operate on y as function of x
- **1** delta x
- **2** delta y
- **3** dy / dx
- **4** I_a\^x dx\' y(x\')
- **5** y\*f(x)
- **6** y/f(x)
```{=html}
<!-- -->
```
- **ot** = form tensor product.\
CHECK THIS! Suppose you have one spectrum y(x), and you want to
manipulate this spectrum for different values of a parameter p. A
convenient way to achieve this is to expand y(x) into a file y(x,z),
consisting of a set of identical spectra y(x) with z=p. You can
either read z from another file or specify a regular grid.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment