| Age | Commit message (Collapse) | Author |
|---|
|
This is really old school, but a lot of times we have users sending us
copy pasting of codes, and that is the only way to know the version of
the code.
|
|
This is mostly a long term maintenance improvement.
Many coding styles require elimination of trailing whitespace, and
many editors and source code management configurations automatically
gobble up whitespace. When these tools gobble up whitespace, it
complicates reviewing the meaningful code changes.
By removing whitespace on one patch, it makes future
code reviews much easier.
=SCRIPT====================================================================
if which tempfile &>/dev/null; then
TEMPMAKER=tempfile
elif which mktemp &>/dev/null; then
TEMPMAKER=mktemp
else
echo "Cannot find tempfile program." 2>&1
exit 1
fi
MYTEMP=$($TEMPMAKER)
trap 'rm -f $MYTEMP' SIGINT SIGTERM
stripit() {
echo "stripping $1"
sed 's/[ \t]*$//' "$1" > $MYTEMP
cp $MYTEMP "$1"
}
if [ $# -gt 0 ]; then
while [ "$1" != "" ]; do
stripit $1
shift
done
else
while read -t 2; do
stripit $REPLY
done
fi
rm $MYTEMP
=================================================
|
|
Author: Sébastien Villemot <sebastien@debian.org>
Forwarded: yes, by email to lapack@cs.utk.edu on 2016-06-26
|
|
|
|
Use \par instead of \details for section.
add a Contributors Section and a Reference Section.
Remove (some) verbatim section when not needed.
Those changes have been done by hand so I am not sure I manage to catch them all.
|
|
Now each routine should have the correct list of arguments.
This allowed to detect and fix problems in parameter description of many routines.
|
|
|
|
Below is the help that goes with it.
Please send feedback. I tired to include several levels of output and several kind of errors
So far, I just tested it on my machine, that has no major problems.
I just tested "numerical errors", not "illegal error" neither "info error".
The goal is to have our nightly testing use it and also users.
TO DO:
- Test other kinds of errors on machines
- See to include it in ctest and buildbot (need to contact Don and Brad/Chuck)
- See if a type of error option is required.
./lapack_testing.py [-h|--help] [-s |--short] [-f |--file] [-e |--error] [-p p |--prec p] [-t test |--test test] [-n | --number]
- h is to print this message
- f is to use directly the output of the LAPACK testing (.out files). By default, the script will run all the LAPACK tests
LEVEL OF OUTPUT
- x is to print a detailed summary
- e is to print only the error summary
- s is to print a short summary
- n is to print the numbers of failing tests (turn on summary mode)
SECLECTION OF TESTS:
- p [s/c/d/z] is to indicate the PRECISION to run:
s=single
d=double
c=complex
z=double complex
x=all [DEFAULT]
- t [lin/eig/mixed/rfp/all] is to indicate which TEST FAMILY to run:
lin=Linear Equation
eig=Eigen Problems
mixed=mixed-precision
rfp=rfp format
all=all tests [DEFAULT]
EXAMPLES:
./lapack_testing.py -n -f
Will return the numbers of failed tests by analyzing the LAPACK output
./lapack_testing.py -n -f -p s
Will return the numbers of failed tests in REAL precision by analyzing the LAPACK output
./lapack_testing.py -n -f -p s -t eig
Will return the numbers of failed tests in REAL precision by analyzing only the LAPACK output of EIGEN testings
Written by Julie Langou (June 2011)
|
|
|
