December 6, 1999
The PAW version 2.11/13 is part of the 2000 release of CERNLIB. The source files, binaries and libraries are available, via anonymous ftp, on the asis system:
ftp asisftp.cern.ch
The PAW support is done by:
The PAW related packages versions are:
| |
|
|
| 06/12/1999 | ||
| 24/11/1999 | ||
| 23/03/1999 | ||
| 13/05/1998 | ||
| 18/05/1999 | ||
| 13/10/1999 | ||
| 10/02/1994 |
The following subjects can be found in this page:
PAW > hmerge LRECL 16384 | New LRECL
Next HMERGE will use LRECL = 16384
PAW > hmerge out.hbook in1.hbook in2.hbook | Use the new LRECL
To go back to the automatic record length determination mode just do:
PAW > hmerge LRECL 0
Next HMERGE will use the auto-record length detection
nt/plot 1.y%z $1 gcut 2 1.y%x $1 option=SThe S option forced GCUT to produce a histogram scatter plot which completly obscured the picture.
ve/create vec(10) R app comis quit !file example.f77 quit call exampleWhere the file example.f is:
subroutine example
vector vec(10)
vec(2) = 1.0
print *, 'vec(2)=', vec(2)
end
This macro involve some character strings manipulations using
s_cat. The
wrong
s_cat was used (the one defined in
mlp_lapack.c). To fix this
problem, the functions
s_cat,
s_cmp and
s_copy defined in
mlp_lapack.c
are now called
mlp_s_cat,
mlp_s_cmp and
mlp_s_copy. This bug has been found
in the intermediate PAW version 2.11/12 it is fixed
in 2.11/13.
PAW > message $HINFO(1000,'XBINS') *** Break *** Segmentation violation Traceq lun = 0, level = 99 Longjump n-line trace-back still not available. PAW >
SET * ; OPT * | Reset the defaults
NULL 0 10 0 10 'AB' | Draw a frame (cf HELP NULL)
SET PLCI 2 | Line color is red
SET LWID 6 | Line width is 6
SET BORD 1 | Border on
SET FAIS 1 | Filled area
SET FACI 3 | Filled area are green
ELLIPSE 5 5 3 5
A workaround is to draw the ellipse in two passes:
NULL 0 10 0 10 'AB'
SET BORD 0
SET FAIS 1
SET FACI 3
ELLIPSE 5 5 3 5
SET PLCI 2
SET LWID 6
SET FAIS 0
ELLIPSE 5 5 3 5
SET NCOL 100
PALETTE 1
There was no protections and, on some machines, wrong results may be
produced because some code or data could be overwritten.
This macro shows the problem:
Vector/create v(2,10) r
Appl Data v.dat
1 5
2 7
3 3
4 9
v.dat
Vector/read v v.dat
Vector/print v
Vector/create vbid(10)
Vector/copy v(1) vbid
Vector/print vbid
It gives the output:
PAW > exe a
V(1, 1) = 1
V(2, 1) = 5
V(1, 2) = 2
V(2, 2) = 7
V(1, 3) = 3
V(2, 3) = 3
V(1, 4) = 4
V(2, 4) = 9
V(1, 5) ...
V(2,10) = 0
VBID( 1) = 1
VBID( 2) = 5
VBID( 3) = 2
VBID( 4) = 7
VBID( 5) = 3
VBID( 6) = 3
VBID( 7) = 4
VBID( 8) = 9
VBID( 9) = 0
VBID(10) = 0
PAW >
instead of:
PAW > exe a
V(1, 1) = 1
V(2, 1) = 5
V(1, 2) = 2
V(2, 2) = 7
V(1, 3) = 3
V(2, 3) = 3
V(1, 4) = 4
V(2, 4) = 9
V(1, 5) ...
V(2,10) = 0
VBID( 1) = 1
VBID( 2) = 2
VBID( 3) = 3
VBID( 4) = 4
VBID( 5) ...
VBID(10) = 0
PAW >
![]() | Release Notes | Known bugs | FAQs | Contributions | Tutorial | Reference manual | Down load | Miscellaneous |