|
UMI3D Unity SDK
2.5.b.221125
A UMI3D sdk implementation using Unity
|
Collection of Equality functions for floats and structs containing float, using an epsilon threshold. More...
Public Member Functions | |
| bool | Vector3Equality (Vector3 a, Vector3 b) |
| Vector Equality test component by component using epsilon. More... | |
| bool | Vector2Equality (Vector2 a, Vector2 b) |
| Vector Equality test component by component using epsilon. More... | |
| bool | Vector4Equality (Vector4 a, Vector4 b) |
| Vector Equality test component by component using epsilon. More... | |
| bool | ColorEquality (Color a, Color b) |
| Color Equality test component by component using epsilon. More... | |
| bool | QuaternionEquality (Quaternion a, Quaternion b) |
| Quaternion Equality test by angle using epsilon. More... | |
| bool | FloatEquality (float a, float b) |
| Float Equality test using epsilon. More... | |
Public Attributes | |
| float | epsilon = 0.000001f |
| Epsilon threshold used for Equality test. A == B is true if A in ]B - epsilon; B + epsilon[. More... | |
Collection of Equality functions for floats and structs containing float, using an epsilon threshold.
| bool umi3d.edk.UMI3DAsyncPropertyEquality.ColorEquality | ( | Color | a, |
| Color | b | ||
| ) |
Color Equality test component by component using epsilon.
| a | |
| b |
| bool umi3d.edk.UMI3DAsyncPropertyEquality.FloatEquality | ( | float | a, |
| float | b | ||
| ) |
Float Equality test using epsilon.
| a | |
| b |
| bool umi3d.edk.UMI3DAsyncPropertyEquality.QuaternionEquality | ( | Quaternion | a, |
| Quaternion | b | ||
| ) |
Quaternion Equality test by angle using epsilon.
| a | |
| b |
| bool umi3d.edk.UMI3DAsyncPropertyEquality.Vector2Equality | ( | Vector2 | a, |
| Vector2 | b | ||
| ) |
Vector Equality test component by component using epsilon.
| a | |
| b |
| bool umi3d.edk.UMI3DAsyncPropertyEquality.Vector3Equality | ( | Vector3 | a, |
| Vector3 | b | ||
| ) |
Vector Equality test component by component using epsilon.
| a | |
| b |
| bool umi3d.edk.UMI3DAsyncPropertyEquality.Vector4Equality | ( | Vector4 | a, |
| Vector4 | b | ||
| ) |
Vector Equality test component by component using epsilon.
| a | |
| b |
| float umi3d.edk.UMI3DAsyncPropertyEquality.epsilon = 0.000001f |
Epsilon threshold used for Equality test. A == B is true if A in ]B - epsilon; B + epsilon[.
Default value for epsilon is 10E-6.


done
delete
add
add
Are you sure you want to delete the list?
add a picture or write something about it to make the event special
Take Picture
Video stream not available.
Journal Entry:


Codehaus XFire
Documentation
Quicklinks
Developers
|
The Codehaus XFire team is proud to announce XFire 1.1.2! This is a bug fix release and all users are strongly encouraged to upgrade.
XFire is an open source Java SOAP framework built on a high performance, streaming XML model. XFire includes support for web service standards, an easy to use API, Spring integration, JBI support, and plugable bindings for POJOs, JAXB, and XMLBeans.
XFire 1.1.2 incorporates several bug fixes since 1.1.1:
- Fix compilation issues with client and JAXB examples
- DOM mode namespace bug fix
- Fix minor JAX-WS fault name generation
Many thanks to those who helped build and test this release!
Download Here
Upgrading to 1.1.2 from 1.1
- If you are using services.xml to register your services, you MUST upgrade to XBean 2.4 from version 2.3.
- The Codehaus Maven repository has changed to http://repository.codehaus.org. You will need to update your POMs accordingly.
Errata
Issues closed since last release
|
jira.codehaus.org
(10 issues)
|
|
T |
Key |
Summary |
Assignee |
Reporter |
Pr |
Status |
Res |
Created |
Updated |
Due |
|
|
XFIRE-497
|
Exception when accessing the WSDL more than once (when using the <wsdlURL>)
|
Dan Diephouse
|
Chad Brandon
|
|
Closed
|
DUPLICATE
|
Jun 27, 2006
|
Jun 27, 2006
|
|
|
|
XFIRE-492
|
@WebService.wsdlLocation is not generated from wsdl
|
Dan Diephouse
|
Dan Diephouse
|
|
Closed
|
FIXED
|
Jun 24, 2006
|
Jun 27, 2006
|
|
|
|
XFIRE-489
|
Rerunning the WsGen Ant Task over-writes existing Service Impl class.
|
Tomasz Sztelak
|
Mike McAngus
|
|
Resolved
|
FIXED
|
Jun 21, 2006
|
Jun 26, 2006
|
|
|
|
XFIRE-485
|
Response message in WSDL generated by XFire Service structurally different from WSDL fed into WsGen Ant Task
|
Dan Diephouse
|
Mike McAngus
|
|
Closed
|
FIXED
|
Jun 21, 2006
|
Jun 25, 2006
|
|
|
|
XFIRE-477
|
JAXWS generate faults without an upercase initial
|
Dan Diephouse
|
Guillaume Nodet
|
|
Closed
|
FIXED
|
Jun 20, 2006
|
Jun 25, 2006
|
|
|
|
XFIRE-475
|
DOMOutHandler unconditionally dumps the message to System.out
|
Christoph Sturm
|
Slawomir Ginter
|
|
Resolved
|
FIXED
|
Jun 20, 2006
|
Jun 23, 2006
|
|
|
|
XFIRE-474
|
Namespace context is handled improperly in W3CDOMStreamWriter.java
|
Christoph Sturm
|
Slawomir Ginter
|
|
Resolved
|
FIXED
|
Jun 20, 2006
|
Jun 23, 2006
|
|
|
|
XFIRE-472
|
Spring example - log4j dependency
|
Christoph Sturm
|
Jesper Zedlitz
|
|
Resolved
|
FIXED
|
Jun 20, 2006
|
Jun 24, 2006
|
|
|
|
XFIRE-470
|
jaxb2 example does not work
|
Tomasz Sztelak
|
Jesper Zedlitz
|
|
Resolved
|
FIXED
|
Jun 20, 2006
|
Jun 23, 2006
|
|
|
|
XFIRE-423
|
rename customEditorConfigurer in customEditors.xml
|
Tomasz Sztelak
|
Marc Logemann
|
|
Closed
|
FIXED
|
May 25, 2006
|
Jun 25, 2006
|
|
|


Want your child to learn how to swim but, need a trusted and less expensive solution? We can help. Learn more or sign up now!
Alana, Breanne, and Malia have all been on the competitive swim team since they were kids where they developed their love for swimming. They are all CPR and Lifeguard Certified and have taught lessons and lifeguarded for 2 years. "We all feel strongly about the importance of learning to swim while you are young. Some of our best memories together have been on the water whether it's rafting, boating, surfing, or just swimming around without our parents having to worry about us. We would love to help your kids feel comfortable in the water so they can have their own awesome memories!"
Sign UpMade By Jonny Porter


FreeMentor
HOME
IRAKOZE Yves
Dashboard
Logout
Dashboard
Logout
Elisabeth Morgan
Teacher at university
psychologist
He was specialist in Psychologist
<EMAIL_ADDRESS>Create A session


|
home | news | discuss | issues | license LURE: INSTALL |
|
|---|---|
|
<EMAIL_ADDRESS>Why | Install | What | Guide | Style Using LuaRocksComing soon. Using GithubCheck out the repo, then create an environment
variable
Add the following function to your $HOME/.bashrc.
Make sure your source this code; e.g. logout then log back in or (much faster):
TestChange directories to some other part of your computer (away from the source code). Then try to run any code from lure. e.g.
The above code is reporting that none of the |
require "show"
|
LegalLURE, Copyright (c) 2017, Tim Menzies All rights reserved, BSD 3-Clause License Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
|


"; echo "
Incorrect UserName and Password!
"; echo "
Login
"; } }else{ ?>
AD
SMART
User Name
Password
Remember Me
Forgotten Password?
Sign in
Don't have account ?
Sign Up Here


QGeoPath Class
The QGeoPath class defines a geographic path. More...
| Header: | #include <QGeoPath> |
| qmake: | QT += positioning |
| Since: | Qt 5.9 |
| Inherits: | QGeoShape |
Properties
- 3 properties inherited from QGeoShape
Public Functions
| QGeoPath() | |
| QGeoPath(const QList<QGeoCoordinate> &path, const qreal &width = 0.0) | |
| QGeoPath(const QGeoPath &other) | |
| QGeoPath(const QGeoShape &other) | |
| ~QGeoPath() | |
| void | addCoordinate(const QGeoCoordinate &coordinate) |
| bool | containsCoordinate(const QGeoCoordinate &coordinate) const |
| QGeoCoordinate | coordinateAt(int index) const |
| void | insertCoordinate(int index, const QGeoCoordinate &coordinate) |
| double | length(int indexFrom = 0, int indexTo = -1) const |
| const QList<QGeoCoordinate> & | path() const |
| void | removeCoordinate(const QGeoCoordinate &coordinate) |
| void | removeCoordinate(int index) |
| void | replaceCoordinate(int index, const QGeoCoordinate &coordinate) |
| void | setPath(const QList<QGeoCoordinate> &path) |
| void | setWidth(const qreal &width) |
| QString | toString() const |
| void | translate(double degreesLatitude, double degreesLongitude) |
| QGeoPath | translated(double degreesLatitude, double degreesLongitude) const |
| qreal | width() const |
| bool | operator!=(const QGeoPath &other) const |
| QGeoPath & | operator=(const QGeoPath &other) |
| bool | operator==(const QGeoPath &other) const |
- 10 public functions inherited from QGeoShape
Detailed Description
The QGeoPath class defines a geographic path.
The path is defined by an ordered list of QGeoCoordinates.
Each two adjacent elements in the path are intended to be connected together by the shortest line segment of constant bearing passing through both elements. This type of connection can cross the dateline in the longitudinal direction, but never crosses the poles.
This is relevant for the calculation of the bounding box returned by QGeoShape::boundingGeoRectangle() for this shape, which will have the latitude of the top left corner set to the maximum latitude in the path point set. Similarly, the latitude of the bottom right corner will be the minimum latitude in the path point set.
This class is a Q_GADGET. It can be directly used from C++ and QML.
Property Documentation
path : QList<QGeoCoordinate>
This property holds the list of coordinates for the geo path.
The path is both invalid and empty if it contains no coordinate.
A default constructed QGeoPath is therefore invalid.
Access functions:
| const QList<QGeoCoordinate> & | path() const |
| void | setPath(const QList<QGeoCoordinate> &path) |
width : qreal
Access functions:
| qreal | width() const |
| void | setWidth(const qreal &width) |
Member Function Documentation
QGeoPath::QGeoPath()
Constructs a new, empty geo path.
QGeoPath::QGeoPath(const QList<QGeoCoordinate> &path, const qreal &width = 0.0)
Constructs a new geo path from a list of coordinates (path and width).
QGeoPath::QGeoPath(const QGeoPath &other)
Constructs a new geo path from the contents of other.
QGeoPath::QGeoPath(const QGeoShape &other)
Constructs a new geo path from the contents of other.
QGeoPath::~QGeoPath()
Destroys this path.
void QGeoPath::addCoordinate(const QGeoCoordinate &coordinate)
Appends coordinate to the path.
bool QGeoPath::containsCoordinate(const QGeoCoordinate &coordinate) const
Returns true if the path contains coordinate as one of the elements.
QGeoCoordinate QGeoPath::coordinateAt(int index) const
Returns the coordinate at index .
void QGeoPath::insertCoordinate(int index, const QGeoCoordinate &coordinate)
Inserts coordinate at the specified index.
double QGeoPath::length(int indexFrom = 0, int indexTo = -1) const
Returns the length of the path, in meters, from the element indexFrom to the element indexTo. The length is intended to be the sum of the shortest distances for each pair of adjacent points.
const QList<QGeoCoordinate> &QGeoPath::path() const
Returns all the elements. Equivalent to QGeoShape::center(). The center coordinate, in case of a QGeoPath, is the center of its bounding box.
Note: Getter function for property path.
See also setPath().
void QGeoPath::removeCoordinate(const QGeoCoordinate &coordinate)
Removes the last occurrence of coordinate from the path.
void QGeoPath::removeCoordinate(int index)
Removes element at position index from the path.
void QGeoPath::replaceCoordinate(int index, const QGeoCoordinate &coordinate)
Replaces the path element at the specified index with coordinate.
QString QGeoPath::toString() const
Returns the geo path properties as a string.
void QGeoPath::translate(double degreesLatitude, double degreesLongitude)
Translates this geo path by degreesLatitude northwards and degreesLongitude eastwards.
Negative values of degreesLatitude and degreesLongitude correspond to southward and westward translation respectively.
QGeoPath QGeoPath::translated(double degreesLatitude, double degreesLongitude) const
Returns a copy of this geo path translated by degreesLatitude northwards and degreesLongitude eastwards.
Negative values of degreesLatitude and degreesLongitude correspond to southward and westward translation respectively.
See also translate().
qreal QGeoPath::width() const
Returns the width of the path, in meters. This information is used in the contains method The default value is 0.
Note: Getter function for property width.
See also setWidth().
bool QGeoPath::operator!=(const QGeoPath &other) const
Returns whether this geo path is not equal to other.
QGeoPath &QGeoPath::operator=(const QGeoPath &other)
Assigns other to this geo path and returns a reference to this geo path.
bool QGeoPath::operator==(const QGeoPath &other) const
Returns whether this geo path is equal to other.


bug 159 DSTEMR - consolidates bugs 113 and 126
-
CONFIRMED
-
Present in LAPACK 3.6.0
-
Assigned to Osni.
-
Osni: We have a new subroutine to replace the subroutine causing us trouble. We will be sitting together (OM and Prof. Parlett) tomorrow to discuss how this will behave.
-
I expect the new version of the subroutine will fix bug 113
-
02/10/16 Osni: The bug has been traced to the factorization(s) performed by dlarrf.
-
The current implementation of dlarrf can lead to NaNs or element growth (this is expected) but the tests to deal with these cases are not working properly.
-
Beresford and I have experimented changing a few things in dlarrf, which fixes this bug and also bug 126, but we know that a more robust strategy needs to be devised.
-
2/11/16: We were able to trace the issue down here to the factorizations. We have some tests to cope with extreme growth in elements and NaNs,
-
but these tests are not robust. So we end up with linearly dependent eigenvectors when eigenvalues are close to each other.
-
5/9/16: (Osni) We had a meeting in Berkeley (Prof. Parlett, Jim, Osni, I Dhillon) Some safeguards were removed over the years thinking we did not need them;
-
perhaps they must come back (this was the focus of our discussion). For some matrices, the vectors that are returned are not orthogonal the way we would
-
like them to be---the level of orthogonality is not ideal for nearly multiple eigenvalues. Prof Parlett and I will sit together to determine the best strategy for future LAPACK release.
bug 158 problem with DC SVD least squares
-
CONFIRMED
-
Present in LAPACK 3.6.0
-
Bug reported by Alexander Kobotov in 2015 to Julien
-
Assigned to Osni.
bug 157 gesdd , gesvd, and bdsdc Workspace computation
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by Mark Gates on Feb 12th 2016 to Julie / Julien
-
Bug report from Peng HongBo (IBM) on Mar 14 th 2016, Mar 21st 2016 to LAPACK mailing List
-
Corrected by Mark (files sent to Julie) on Apr 27th, svn 1739.
bug 156 Accuracy Loss in DSTEVD and DSTEVR
-
NOT A BUG
-
Present in LAPACK 3.6.0
-
Bug reported by Pavel Holoborodko on Jan 18th 2016 on LAPACK Forum
-
http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4882
-
Closed by Osni on Feb 23rd
bug 155 [CZ]GESVJ - OMPQ eval only when rotating
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by lawrence mulholland on Jan 27th 2016 on LAPACK Forum
-
http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4892
-
Corrected by Julie on Feb 10th, svn 1688
bug 154 [LAPACKE] lapacke_?lantr: unnecessary work array allocation
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by Eugene Chereshnev on Dec 17th 2015 on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=4867
-
Corrected by Julien on Dec 17th, svn 1670
-
NEED REVIEW: Wait, that code was the fix for 141…
bug 153 Fix out of bounds error in dgeev
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by Andreas Noack (MIT) on Dec 9th 2015 on LAPACK Mailing List
-
Corrected by Julien on Dec 9th, svn 1669
bug 152 [LAPACKE] Dormbr check wrong for RowMajor
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by Tracey Brendan on Dec 9th 2015 on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=4863
-
Corrected by Julien on Dec 9th, svn 1668
bug 151 Bug in xGETC2, quick return for N=0, N=1
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by Martin Köhler on Nov 29th 2015 on LAPACK Mailing List
-
Corrected by Julien on Nov 29th, svn 1660
bug 150 [LAPACKE] Fix bug on [sd]lantr which don’t report the result
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug and fix reported by Mathieu Faverge (PLASMA team) on Nov 25 2015
-
Corrected by Mathieu Faverge on Nov 22th, svn 1658
bug 149 workspace computation for [CZ]GESVDX when a workspace query is done
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug and fix reported by Lawrence Mulholland (NAG) on Nov 22 2015 on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=4850
-
Corrected by Julien on Nov 22th, svn 1656
bug 148 workspace computation for [s/d]gesvdx.f
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug and fix reported by Lawrence Mulholland (NAG) on Nov 20 2015 on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=4850
-
Corrected by Julien on Nov 20th, svn 1655
bug 147 INFO parameter value when LVT is not correct.
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug and fix reported by Lawrence Mulholland (NAG) on Nov 20 2015 on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=4851
-
Corrected by Julien on Nov 20th, svn 1654, 1661
bug 146 properly avoid setting the install rpath when installing to system directories
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug and fix reported by Orion Poplawski on Nov 18 2015 on LAPACK Mailing List
-
Corrected by Julie on Nov 18th, rev 1653
bug 145 Fix upper case issue in CMakeLists
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug and fix reported by Julien Schueller on Nov 17 2015 on LAPACK Mailing List
-
Corrected by Julie on Nov 17th, rev 1651
bug 144 inconsistency in the lapacke cmake config files install directory location
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug and fix reported by Julien Schueller on Mon Nov 16 2015 on LAPACK Mailing List
-
Corrected by Julie on Nov 16th, rev 1650
bug 143 [CZ]GEJSV - real→ complex bugs
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by Lawrence Mulholland on Mon Nov 16 2015 on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=4844
-
Corrected by Julien and Zlatko Drmac on Nov 16th, rev 1649
bug142 Mistake in computation of workspace for ZGGEV3
-
CORRECTED
-
Present in LAPACK 3.6.0
-
Bug reported by Pavel Holoborodko on Mon Nov 16 2015 on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=4796
-
Corrected by Julien on Nov 16th, rev 1648
bug141 LAPACKE dlantr causes memory corruption
-
CORRECTED, rev 1602
-
Present in LAPACK 3.5.0
-
Bug reported by Dan Kortschak on LAPACK forum on Sep 6th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4788
-
Confirmed by Julien on Oct 7th
-
Corrected by Julie on Oct 21th rev 1602 (apply patch submitted by Dan Kortschak)
bug140 LAHEF_ROOK and LASYF_ROOK: could choose zero pivot in the case when non-zero pivot could be used
-
NOT CONFIRMED
-
Present in LAPACK 3.5.0
-
Bug reported on Oct 7th by Eugene Chereshnev on LAPACK Forum
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4812
-
Assigned to Igor on Oct 7th
bug139 xSTEDC eigenvalues not sorted
-
CORRECTED
-
Present in LAPACK 3.5.0
-
Bug reported on Oct 6th by Christoph Conrads on lapack mailing list
-
Link: http://icl.cs.utk.edu/lapack-forum/archives/lapack/msg01713.html
-
Confirmed by Julien on Oct 7th
-
Corrected by Julie on Oct 21th rev 1601 (apply patch submitted by Christoph Conrads)
bug138 :: LAPACKE_dtr_nancheck not working for trapezoidal matrix
-
CORRECTED "Quick Fix"
-
Present in LAPACK 3.5.0
-
Bug reported by Dan Kortschak on LAPACK forum on Oct 5th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4810
-
Confirmed by Julie on Oct 5th
-
Corrected by Julien on Oct 5th rev 1598
bug 137 :: Dlange gives inconsistent/incorrect results for RowMajor
-
CORRECTED, rev 1602
-
Bug reported by Dan Kortschak on Sep 16th
-
Link: https://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4789&p=0#p0
-
Assigned to Julien on Sep 16th
-
Confirmed by Julien on Sep 16th
-
Corrected by Julie on Oct 21th rev 1602 (apply patch submitted by Dan Kortschak)
bug 136 :: xGGEV3 returns zeros in BETA array
-
CORRECTED
-
CORRECTION in rev 1599
-
Bug reported by pavel (Multiprecision Computing Toolbox for MATLAB) on Sep 10th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4796&p=11509
-
Assigned to Julien on Sep 10th
-
Corrected by lawrence mulholland (NAG) in rev 1599 but not verified
bug 135 :: LAPACKE_dlansy et al cause segfault with 1-norm
-
CORRECTED, rev 1587
-
Present in LAPACK 3.5.0
-
Bug reported by kortschak on Sep 10th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4793
-
Confirmed by Julie on Sep 10th
-
Corrected by Julie on Sep 10th
bug 134 :: Rook pivoting factorization goes into an infinite loop
-
NOT A BUG
-
Present in LAPACK 3.5.0
-
Bug reported directly by Bobby Cheng (Matlab) on Aug 12th
-
Assigned to Igor on Aug 12th 2015
-
Not able to reproduce the issue (Aug 20th 2015)
-
Correction to be made: Working on having NaNs/Infs not cause an infinite loop (Aug 20th 2015)
bug 133 :: Dormlq C interface error check
-
CORRECTED
-
Present in LAPACK 3.5.0
-
Bug reported by btracey on Aug 10th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4771
-
Assigned to Julie on Aug 11th 2015
-
Confirmed by Julie on Aug 25th
-
Corrected by Julie on Sep 2nd
bug 132 :: dsyevr bug
-
NOT A BUG
-
Bug reported by osirpt on Aug 4th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=2&t=4767
-
Assigned to Osni on Aug 4th 2015
-
Osni not able to reproduce issue - unconfirmed on Sep 24th
bug 131 :: Possible bug in DORGR2
-
NOT A BUG
-
Present in LAPACK 3.5.0
-
Bug reported by hrautila on Aug 3rd
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4765
-
Unconfirmed by Julie on Sep 2nd 2015
bug 130 :: Ambiguous lapacke interfaces to Cosine/Sine decomposition - 2 Trans parameters
-
NOT A BUG on July 9th 2015
-
Present in LAPACK 3.5.0
-
Bug reported by Victor Kostin (INTEL) on July 9th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4748
-
Confirmed by Julie on July 9th 2015
bug 129 :: LAPACK_?syconv interface problem - Work is used to return values
-
CORRECTED, rev 1581
-
Present in LAPACK 3.5.0
-
Bug reported by Victor Kostin (INTEL) on July 9th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4747
-
Confirmed by Julie on July 9th 2015
-
Corrected by Julie on Aug 25th 2015
bug 128 :: lapacke_?laset has limitations - pb if initialize the matrix with NaNs (Matrix assumed to be initialized by this functions)
-
CORRECTED, rev 1580
-
Present in LAPACK 3.5.0
-
Bug reported by Victor Kostin (INTEL) on July 9th
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4746
-
Confirmed by Julie on July 9th 2015
-
Corrected by Julien on Aug 25th 2015
bug 127 :: LAPACKE interface to ?ORCSD / ?UNCSD is not fully functional - Work is used to return values
-
NOT A BUG on July 9th 2015
-
Present in LAPACK 3.5.0
-
Bug reported by Victor Kostin (INTEL) on July 9th
-
Link http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4745
-
Confirmed by Julie on July 9th 2015
bug 126 :: DSTEMR - misbehaviour of DLARRF
-
CONFIRMED on Jun 24th
-
Present in LAPACK 3.5.0
-
Bug reported by Miroslav Ilias on Jun 27th
-
Link http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=2&t=1820
-
See bug 159
bug125 :: xLAHQR v3.5 does not converge on some matrices while xLAHQR v2 converges
-
CORRECTED, rev 1537
-
Present in LAPACK 3.5.0
-
Bug reported by Yoshihide Okimi on July 16, 2014
-
Link: https://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4566
-
and, independently, by Marco Caliari (Università di Verona) on February 11, 2015.
-
Involved in bug fix: Yoshihide Okimi, Marco Caliari (Università di Verona),
-
Meiyue Shao (LBL), Julien Langou, and Daniel Kressner (EPFL).
-
Confirmed and Corrected by Julien Langou on Mar 25th 2015.
bug124 :: dpstf2 returns incorrect value of rank
-
CORRECTED, rev 1536
-
Present in LAPACK 3.5.0
-
Bug reported by Victor (INTEL) on the LAPACK forum on December 26th 2014
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4643&p=11162#p11162
-
Confirmed by Julie Langou on Mar 17th 2015
-
Corrected by Julien Langou on Mar 25th 2015. Involved as well Nick Higham, Sven Hammarling and Craig Lucas.
bug123 :: csytrf_rook test fails for dimensions 127, 260
-
CONFIRMED
-
Present in LAPACK 3.5.0
-
Bug reported by Alex (INTEL) on the LAPACK forum on September 26th 2014
-
Bug sent to Berkeley
-
Link: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4590
-
Confirmed by Igor on Apr 7th 2015
bug122 :: Wrong Info code when checking input parameter QSIZ in SLASD7 and DLASD7
-
CORRECTED, rev 1504
-
Present in LAPACK 3.5.0
-
Bug report by Elena Ivanova (Oracle) directly to Julie on Oct 2nd 2014
-
Corrected by Julie Langou on October 6th
bug121 :: Bugs in DLASD8 and DLASD6
-
CORRECTED?, rev 1505
-
Present in LAPACK 3.5.0
-
Bug report by forswg on the Forum - Sep 18th 2014
-
Links: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4586&p=11035#p11035
-
Seems to be related to bug 115
-
Corrected by Osni Marques on Oct 1st 2014
bug120 :: Workspace query return too small value for xGESDD
-
CORRECTED, rev 1503
-
Present in LAPACK 3.5.0
-
Bug report by Rasmus Munk Larsen, Google Knowledge & Research, Mountain View. on the Forum - Sep 18th 2014
-
Links: https://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4587&p=11036#p11036
-
Corrected by Julie Langou on September 22nd
bug119 :: CBLAS - missing the floating point constant argument in sdsdotsub
-
Present in CBLAS
-
Bug report by by Shandong Lao fron Oracle on LAPACK Mailing List - Aug 11th 2014
-
Corrected by Julien and Julie Langou on August 11th
bug118 :: ZLANHF and CLANHF Norm Calculation
-
CORRECTED, rev 1483
-
Present in LAPACK 3.5.0
-
Bug report by by Themos Tsikas fron NAG Ltd on LAPACK Forum - June 16th 2014
-
Links: http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4558
-
Corrected by Julien Langou on June 16th
bug117 :: NSPLIT unitialized; N=2 code wrong
-
CORRECTED, rev 1432, 1463
-
Present in LAPACK 3.4.0
-
Bug report by Lawrence Mulholland, NAG on LAPACK Forum - July 26th 2013
-
Links: http://icl.utk.edu/lapack-forum/viewtopic.php?f=2&t=4331
-
Bug fix by Ake Sandgren and Lawrence Mulholland
bug116 :: ZGGEV fails but Matlab works
-
NOT CONFIRMED
-
Present in LAPACK 3.5.0
-
Bug report by Victor Liu, Standford on LAPACK Forum - August 20th 2013
-
Links: http://icl.utk.edu/lapack-forum/viewtopic.php?f=13&t=4357
bug115 :: DSYEVD fails to converge
-
CORRECTED, rev 1505
-
Present in LAPACK 3.5.0
-
Bug report by Duncan Po on LAPACK Forum - September 12th 2013
-
Links: http://icl.utk.edu/lapack-forum/viewtopic.php?f=13&t=4391
-
Corrected by Osni Marques on Oct 1st 2014
bug114 :: (C, Z)GESVD stack corruption issue
-
CORRECTED, rev 1455
-
Present in LAPACK 3.5.0
-
Bug report by Alex Zotkevich on LAPACK Forum - September 16th 2013
-
Links: http://icl.utk.edu/lapack-forum/viewtopic.php?f=13&t=4392
-
Corrected by Julien Langou on Nov 26th
bug113 :: DLARRB() infinite loop bug
-
CORRECTED, rev 1540, rev 1603
-
Present in LAPACK 3.4.2
-
Bug report by Aleksey Vorona on LAPACK Mailing - September 11th 2013
-
Assigned to Osni (UC Berkeley) on Feb 11th 2015
-
Links: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=15211
-
The patch is attached to the bug: https://bugs.r-project.org/bugzilla3/attachment.cgi?id=1478
-
The fix consisted of setting NOFAIL=.false. in subroutine DLARRF.
-
The above fix may lead subroutine DSTEMR return INFO>0 for tridiagonal matrices with clusters of very tight eigenvalues
-
Confirmed by Osni on Mon, 06 Apr 2015
-
Corrected by Osni on Mon May 4th 2015
-
Corrected by Osni on Oct 26th 2015
-
Prevention fix to avoid enter into an infinite loop in some rare cases.
-
Fix: set the variable NOFAIL to .false.
bug112 :: DSYEVR does not seem to be thread-safe
-
CORRECTED, rev 1436
-
Present in LAPACK 3.4.2
-
Bug report by Daniel Strobusch on LAPACK Mailing - August 19th 2013
-
Fix: LAPACK needs to be compiled with option "-frecursive" so that local arrays are allocated on the stack. * Corrected by Julien on Oct 4 2013
bug111 :: incorrect RWORK size for ZGESDD
-
CORRECTED, rev 1535 (LAPACK), rev 1541 (LAPACKE)
-
Present in LAPACK 3.4.2
-
Bug report by Kevin Squire on LAPACK Mailing - August 15th 2013
-
From Kevin: We were following the recommendation for RWORK size calculation from the ZGESDD header here ( http://netlib.org/lapack/complex16/zgesdd.f), and were finding that when INFO=N, the size was insufficient, and generally led to a segmentation fault.
-
The current definition says that "If JOBZ = N, LRWORK >= 5*min(M,N)", but we found that the minimum size needed to be at least 7*min(M,N). This was through experimentation and comparison with code from Numpy and Octave, so you may wish to verify this through the code.
-
Relevant Julia links:
-
Corrected by Julie on Mar 7 2015
bug110 :: possible infinite loop in ZLARTG when input vector has NaN
-
CORRECTED, rev 1437
-
Present in LAPACK 3.4.2
-
Bug report by Mark Hoemmen and Jack Poulson
-
See http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=5&t=3267&p=9067
-
Mark Hoemmen writes: Jack Poulson found that ZLARTG has an infinite loop related
-
to NaN .EQ. 0. It’s the line below "ELSE IF( SCALE.LE.SAFMN2 )" between 10 and
-
20. When G is NaN, then the loop goes forever.
-
Corrected by Rodney on Oct 5 2013
bug0109 :: [xSTEGR_WORK] do not check ldz correctly
-
CORRECTED, rev 1425
-
Present in LAPACKE 3.4.2
-
bug report by Hong Xu (INTEL) on July 21st
-
Patch sent by Hong Xu (INTEL)
-
In the input parameter checking, LDZ was not checked correctly
-
LDZ was checked against M instead of N essentially
-
Corrected by Julien on July 22 2013
bug0108 :: [xDRVRFP] Test was failing
-
CORRECTED, rev 1416
-
Present in LAPACK 3.4.2
-
bug report by Elena Ivanova (ORACLE)
-
Patch sent by Elena Ivanova (ORACLE)
-
add MAX() to ensure index is at least 1
-
Corrected by Rodney on June 27 2013
bug0107 :: [CSD routines] fixed array index problems
-
CORRECTED, rev 1414
-
Present in LAPACK 3.4.2
-
add MAX() to ensure index is at least 1
-
this fixes array bounds violations in the test suite when array bounds checking is enabled
-
Corrected by Rodney on June 04 2013
bug0106 :: [xGEBAL] very large backward error for certain Hessenberg matrices (Watkins)
-
CORRECTED, rev 1413
-
Present in LAPACK 3.4.2
-
bug report on the forum topic 4221
-
Now using 2-norm to compute vector norms of row and column for balancing algorithm.
-
This seems to fix problems with balancing causing very large backward error for certain
-
Hessenberg matrices, including the often cited example of Watkins.
-
Corrected by Bradley Lowery, Rodney James, Julien Langou on May 26 2013
bug0105 :: [LAPACKE] lapacke.h problem
-
CORRECTED, rev 1388
-
Present in LAPACKE 3.4.2
-
bug report on the forum topic 4221
-
Patch sent by bmoloney
-
A few C++ library includes are inside of the 'extern C block which causes many template with C
-
linkage errors when the header is included in a C++ file.
-
Corrected by Julie on April 03 2013
bug0104 :: dgeqp3 fall over when asked to do a factorization of the last two columns.
-
CORRECTED, rev 1385
-
Present in LAPACK 3.4.2
-
bug report by Tyrone Rees (STFC Rutherford Appleton Laboratory) on March 22 2013
-
Patch sent by Tyrone Rees
-
Corrected by Rodney on March 22 2013
bug0103 :: [dlasd4/slasd4] fixes bug where TAU2 can be uninitialized.
-
CORRECTED, rev 1384
-
Present in LAPACK 3.4.2
-
bug report by Sergey Kuznetsov (INTEL) on March 15 2013
-
Patch sent by Sergey Kuznetsov
-
Corrected by Rodney on March 22 2013
bug0102 :: convergence problem with some particular pencils in xGGEV
-
CORRECTED, rev 1351
-
Present in LAPACK 3.4.2
-
bug report by Mathworks on October 19 2012
-
Patch sent by Mathworks
-
Corrected by Rodney on Thu Oct 19
bug0101 :: [S,D, C, Z]hsein: NaN in H can cause an infinite loop
-
CORRECTED
-
Present in LAPACK 3.4.2
-
bug report by Alexander Kobotov (INTEL) on October 3 2012
-
See forum topic 3928
-
added check for NaN after the norm of each block of H is computed
-
if NaN is detected, returns with INFO=-6 (H is the 6th parameter)
-
Corrected by Rodney
bug0100 :: [S,D]gesdd correct minimum LWORK size
-
CORRECTED
-
Present in LAPACK 3.4.1
-
bug report by Tim Wentz (CRAY) on August 23 2012
-
Email sent directly to Julie
-
correct LWORK size bug for the case JOBZ=A and M >> N (which corresponds to path 4 in the code)
-
the minimum LWORK size in this case had incorrectly used N as the length of LWORK to the DORGQR call, when it should have been M
-
Corrected by Rodney
bug0099 :: [S,D]sgesvj array SVA(N2=0) can be out of the array boundary
-
CORRECTED
-
Present in LAPACK 3.4.1
-
bug report by Shandong Lao (ORACLE) on August 20 2012
-
Email sent directly to Julie
-
Corrected by Rodney
bug0098 :: DSYEV may return non-orthogonal eigenvectors
-
CORRECTED
-
Present in LAPACK 3.4.1
-
bug report by Duncan Po (Mathworks) on August 15 2012
-
See forum topic 3597
-
Corrected by Rodney
bug0097 :: [S,D]LASQ3 could cause NaNs appearance in ?GESVD and ?GESDD
-
CORRECTED
-
Present in LAPACK 3.4.1
-
bug report by Alexander Kobotov (INTEL) on June 28 2012
-
See forum topic 3455
-
Corrected by Rodney
bug0096 :: ?STEMR sorting is not done for N=2.
-
CORRECTED
-
Present in LAPACK 3.4.1
-
bug report by Joseph Young (SANDIA) on June 26 2012
-
bug report sent to lapack mailing list
-
corrected by Julie on July 3 2012
bug0094 :: [S,D]SYEVR and [C,Z]SYEVR routine - workspace indices problem
-
CORRECTED
-
Present in LAPACK 3.4.1
-
bug report by Keita Teranishi (CRAY) on May 18 2012
-
INDIWO should be INDIFL+N. Otherwise, subsequent {S,D}STEIN call takes the same address for IWORK(INDIWO) and INWROK(INDIFL).
-
Sent to LAPACK team
-
corrected by Julie on May 21 2012
bug0093 :: LAPACKE - LAPACKE_xlange routine - workspace problem
-
CORRECTED
-
Present in LAPACK 3.4.1
-
bug report by Mathieu (PLASMA)
-
Was allocating workspace for Frobenius norm, but not inf norm - This is wrong, only the inf norm needs a workspace.
-
Sent directly yo Julie
-
corrected by Julie on May 11 2012
bug0092 :: xLAED6 avoid div by zero
-
CORRECTED
-
Present in LAPACK 3.4.0
-
bug report by Mict Pont (NAG).
-
In the 40 loop - when DSCALE(I)=TAU you get a divide by zero (rare in practice). This can cause some compilers to immediately stop, e.g. the Sun compiler.
-
Sent directly yo Julie
-
corrected by Julie on Apr 18 2012
bug0091 :: xLANHF div by zero
-
CORRECTED
-
Present in LAPACK 3.4.0
-
bug report by Ake Sandgren, Umea University and HPC2N, on 10-22-2011.
-
corrected by Rodney on Apr 11 2012
bug0090 :: xGGEV and xGGEVX: Need to unscale if necessary when there is an error in DHGEQZ (QZ iteration failed)
-
CORRECTED
-
Present in LAPACK 3.4.0
-
bug report by Hong Bo Peng Sandgren, on 03-19-2012.
-
corrected by Julie on Mar 20 2012
bug0089 :: unused external declarations
-
CORRECTED
-
Present in LAPACK 3.4.0
-
bug report by Ake Sandgren, Umea University and HPC2N, on 11-16-2011.
bug0088 :: Uninitialized variable bug in ZHERFSX
-
CORRECTED
-
Present in LAPACK 3.4.0
-
bug report by Mick Pont from NAG on Sat, 30 Nov 2011
-
See forum topic 2893
-
corrected by Julie on April 11 2012
bug0087 :: Wrong call name for XBLAS xLA_RPVGRW, needs to be xLA_GERPVGRW
-
CORRECTED - see svn 1128
-
Present in LAPACK 3.4.0
-
bug detected and corrected by Julie
bug0086 :: ILAxLR:commit r1006 reverts the change made in commit r977
-
CORRECTED - see svn 1099
-
Present in LAPACK 3.4.0
-
bug report by Ake Sandgren on Sat, 22 Oct 2011
-
corrected by Rodney James on Nov 30 2011
bug0085 :: xGESVD Problem in Workspace computation
-
CORRECTED - see svn 1207
-
Present in LAPACK 3.4.0
-
bug report by Marco on Nov 18th 2011
-
See forum topic 2861
-
Problem in Workspace computation
-
corrected by Julie on Jan 6 2012
bug0084 :: Bug Ming Gu
-
CORRECTED - see svn 1017
-
bug reported by Ming Gu (UC Berkeley) through Jim Demmel
-
LAPACK driver routine infected: All SVD solvers when asked for singular values only. (Pathological matrix only)
-
bug is present in LAPACK since 3.1.1 and in Matlab 2010a and 2010b
-
For very specific matrices (given by Ming Gu), the DQDS code converges much slower than expected. The algorithm converges for these matrices un many more iterations than the LAPACK maximum number of iterations allow.
-
bug fix: (1) increase the maximum number of iterations in xlasq2, (2) fall back on Demmel/Kahan algorithm in case of nonconvergence of dqds.
-
corrected by Benjamin Lipschitz on Mon Oct 3rd 2011
bug0083 :: Bug in the testing of CHERFSX function
-
CORRECTED - see svn 1000
-
bug reported by Olga Mitrofanova (Intel MKL team), on the LAPACK forum
-
see forum topic 2644
-
Test of CHERFSX function doesn’t work because there is an error in ../TESTING/LIN/cerrhex.f ( lines 284-330 ). This function uses the diagonal pivoting factorization of a Hermitian indefinite matrix instead of the diagonal pivoting factorization of a Hermitian indefinite packed matrix. When CHERFSX is included in conditional "IF( LSAMEN( 2, C2, HE ) ) THEN " the test works.
-
corrected by Julie on Mon Aug 15th 2011
bug0082 :: [CZ]laed2 Memory problems when COMPZ='I' in DSTEDC
-
CORRECTED - see svn 982
-
bug reported by Edward Smyth (NAG)
-
Added IF statement to prevent potential out of range errors with "K+1" indices.
-
corrected by Rodney on Wed Jun 21th 2011
bug0081 :: [SD]laed2 WORKSPACE size is wrong when NCVT = NRU = NCC = 0
-
CORRECTED - see svn 979
-
bug reported by Hatem Ltaief (KAUST)
-
Update Workspace requirement to 4*N because the routine call [SD]LASCL that requires a 4*N workspace.
-
corrected by Julie on Thu May 19th 2011
bug0080 :: [CZ]BDSQR WORKSPACE size is wrong when NCVT = NRU = NCC = 0
-
CORRECTED - see svn 979
-
bug reported by Hatem Ltaief (KAUST)
-
Update Workspace requirement to 4*N because the routine call [SD]LASCL that requires a 4*N workspace.
-
corrected by Julie on Thu May 19th 2011
bug0079 :: ILA[SDCZ]LR out of bound access in the DO LOOP for array A.
-
CORRECTED - see svn 977
-
bug detected by Julie
-
Change DO LOOP condition and add a IF inside the DO LOOP
-
corrected by Rodney on Tue April 21th 2011
bug0078 :: DBDSDC problem with orthogonality of U in certain cases
-
CORRECTED - see svn 968
-
bug report sent by duncanpo on April 4th 2011
-
see forum topic 2326
-
decreased EPS by a factor of 0.9 to correct problem with orthogonality of U in certain cases
-
corrected by Rodney on Tue April 7th 2011
bug0077 :: [DS]GESVD Minimum Worksize comments need clarification
-
CORRECTED - see svn 967
-
bug report sent by squartz on Sep 19th
-
see forum topic 2011
-
corrected by Julie on Tue April 5th 2011
bug0076 :: Problem in ?(sy/he)tri2 when nbmax greater than n
-
CORRECTED - see svn 953
-
bug report sent by nmozarto on Mar 4th
-
see forum topic 2223
-
corrected by Julie on Fri March 4th 2011
bug0075 :: not orhtogonal: eigenvectors of a symmetric matrix with DSYEV
-
CORRECTED - see svn 946
-
bug report sent by fabioaffinito on Feb 8th
-
see forum topic 2169
-
The bug appears only when the matrix is diagonalized by using the upper half, and when the leading dimension n>200 approx.
-
User gave test program see: here
-
Come from change in version 3.2 [Release Notes]
-
committed by Rodney on Thu Mar 3 2011
-
related to 0035
bug0074 :: ?sysv and ?hesv
-
CORRECTED - see svn 926 and 927
-
bug report sent by Alexander Kobotov on Feb 8th
-
see forum topic 2168
-
corrected by Julie
-
In LAPACK 3.3 ?(SY/HE)SV are updated to use TRS2. The TRS2 requires WORK(N) to operate, whereas in SV requirements for LWORK just to be >=1. There is no any check in SV if LWORK>=N, the array WORK just passed as it is to TRS2. So if LWORK<N a crash could occur while executing TRS2 due to overuse of allocated workspace.
-
I guess for the case of LWORK<N just previsous Level2 based ?(SY/HE)TRS should be used.
bug0073 :: secondtst.f and dsecnd.f
-
CORRECTED - see svn 918
-
bug report sent by John Tellefson on Feb 7th
-
email sent to lapack mailing list, user provided fix.
-
corrected by Julie
-
We went ahead and remove the dummy subroutine in those timing for the last LAPACK version because we did not find a machine or compiler that still had the problem. I guess we were too optimistic.
-
also committed the "cosmetic" modifications suggested by user as they make the program easier to modify.
bug0072 :: cchkhs.f and zchkhs.f
-
CORRECTED - see svn 904
-
bug report sent by Inge Gutheil on Feb 3rd
-
email sent to lapack mailing list, user provided fix.
-
corrected by Julie
-
Add IF statement to prevent calculation if N=0
bug0071 :: slarre and dlarre
-
CORRECTED - see svn 902
-
bug report sent by Christof Voemel on Jan 31th
-
email sent directly to Julie and Julien, Christof provided fix.
-
corrected by Julien
-
Add a line to prevent TAU from becoming zero
bug0070 :: IWORK dimension is incorrect
-
CORRECTED - see svn 899
-
bug report sent by nmozarto on Jan 27th
-
see forum topic 2156
-
confirmed by Julie and corrected by Brian Sutton
-
The correct dimension is (M-R), in which R is the smallest of P, M-P, Q, and M-Q.
-
An M-by-M matrix is partitioned into a 2-by-2 block structure. The
-
dimensions of the blocks are P-by-Q, P-by-(M-Q), (M-P)-by-Q, and
-
(M-P)-by-(M-Q). IWORK is involved in the permutation of rows or
-
columns of these blocks, and it is the largest block, in terms of
-
number of rows or columns, that determines the size of IWORK.
bug0069 :: sytri2x is writing on other part of A
-
CORRECTED - see svn 898
-
bug report sent by nmozarto on Jan 27th
-
see forum topic 2156
-
confirmed by Julie and corrected by Julie
bug0068 :: Need to add LDA in *sytrs2
-
CORRECTED - see svn 897,896
-
bug report sent by nmozarto on Jan 27th
-
see forum topic 2157
-
confirmed by Julie and corrected by Julie
bug0067 :: Need to add LDA in *syswapr
-
CORRECTED - see svn r893 and 894
-
bug report sent by nmozarto on Jan 24th
-
see forum topic 2150
-
confirmed by Julie and corrected by Julien
-
Need to add LDA in *syswapr routines and update testing to test having LDA
bug0066 :: bugs in {s,d}gejsv
-
CORRECTED - see svn r891
-
bug report sent by Paul Roberts on Oct 21st
-
reported to Zlatko Drmac and corrected by Zlatko Drmac
bug0065 :: workspace queries not being used
-
CORRECTED - see svn r1038
-
bug report by Clint Whaley on October 27th, 2010
-
DGESVD does not perform a workspace query on worker
-
functions such as DGELQF, but rather it hardwires in an assumption as
-
to LQF’s workspace requirements. This means that if LQF is changed,
-
GESVD breaks. This actually happens in ATLAS, because we provide a
-
faster GELQF, which sometimes uses extra workspace. For LAPACK itself,
-
it represents extra dependencies that don’t need to be there.
bug0064 :: got a bug in divide and conquer (non convergence)
-
CORRECTED - see svn r813
-
bug report by wdobler on November 12th 2007 and edrumwri (Evan) on October 10th 2010
-
lapackers involved in the bug fix process: Julie Langou
-
bug fix by wdobler
-
see forum topic 529
-
Increase MAXIT to 200 (was 20 before)
bug0063 :: Division by 0 in *GESVJ & *GEVSJ with zero columns
-
CORRECTED - see svn r790
-
bug report and fix from Bart Oldeman on Mon Aug 16 2010
-
independent fix proposed by Zlatko Drmac on Tue Aug 24 2010
-
see forum topic 1953
-
The problem that was reported (with zero matrix) is caused by bad initialization to xLASSQ. It should be ZERO, ONE and not ZERO, ZERO. With ZERO, ZERO, xLASSQ does not touch those variables in case of zero vector, leaving scaling at ZERO, and in the nonzero case the scaling is between ONE and SQRT(N). So, in case of zero vector, division by a variable that is normally bigger than ONE causes division by zero. This is change (i) below.
-
committed by Julie Langou (SVN revision r790, on Wed, Aug 25 2010)
-
changes from Zlatko:
-
In xgejsv.f and xgesvj.f input parameters SCALE and SUMSQ in xlassq.f are now initially set as SCALE = ZERO, SUMSQ=ONE. Setting them both to zero (without carefully reading xlassq.f) caused problems with exactly zero columns.
-
There was a problem in the branch that computes only SIGMA and U of a rank deficient matrix. The computed numerical rank (NR) was incorrectly written as N in parameter lists of the corresponding calls.
-
In xgsvj0.f, xgsvj1.f testing the input parameters is changed to prevent unnecessarily negative INFO in some situations.
-
Minor changes, renaming some variables etc.
-
bug0062 :: Array out-of-bounds reference in xLAQR5
-
CORRECTED - see svn r787
-
bug report and fix from Mathew Cross (NAG) on Sat Aug 14 2010
-
see forum topic 1949
-
In the section of the code "Special case: 2-by-2 reflection (if needed)" the logical test IF( BMP22 .AND. ( V( 1, M22 ).NE.ZERO ) ) must be split into a nested test IF (BMP22) THEN, IF (V(1,M22).NE.ZERO) THEN… If .NOT. BMP22 then M22 can exceed the second extent of V (and recall that logical expressions can be evaluated in any order in Fortran).
-
committed by Julien Langou (SVN revision r787, on Tue, Aug 17 2010)
bug0061 :: zgehrd.f is overflowing
-
CONFIRMED
-
bug report by Victor Liu on Tuesday August 03rd, 2010
-
zgehrd.f is overflowing the maximum size in bytes of the largest array that
-
can be put on the stack with gfortran (⇒ leads ,e.g., to non-reproducible and uncorrect execution
-
of zgeev in multithreaded context
-
bug report by Victor Liu on Tuesday August 03rd, 2010
-
lapackers involved in the bug fix process: Julie and Julien Langou and Mathieu Faverge
-
bug fix by Victor Liu on Wednesday August 04th, 2010
-
see forum topic 1930
-
two outstanding issues: (1) how do we go to fix this?, (2) more LAPACK subroutines might be concerned.
bug0060 :: Bug in dtgsy2, missing IWORK call
-
CORRECTED - see svn r767
-
bug report and fix sent by Vasile Sima on 24 Feb 2009 to<EMAIL_ADDRESS>-
The error is that "IWORK" must appear in the line 640. (It was included in the 1999 version.) Note that the statement IE = ( I+1 ) - 1 is strange; also, in other similar place, IWORK is used like below.
-
committed by Julie Langou (SVN revision r767, on Thu, June 24 2010)
bug0060 :: Typo in TESTING/EIG/dchkee.f and TESTING/EIG/zchkee.f
-
CORRECTED - see svn r768
-
bug report by Ake Sandgren (HPC2N, Umea University) on Thu July 1 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r768, on Fri, July 2 2010)
bug0059 :: ZGELSD crashes on large matrices (eq M=N=NHRS>=88), if real workspace allocated exactly as reported on workspace query.
-
CORRECTED - see svn r765
-
bug report and fix sent by Alexander Kobotov (Intel) on Wed, 23 June 2010 to<EMAIL_ADDRESS>-
Root cause is wrong estimation of real workspace size in ZLALSA (on path zgelsd→zlalsd→zlalsa). It assumes that RWORK array length should be max( N, (SMLSZ+1)NRHS*3 ), where SMLSIZ=25. But in fact the function calls zlals0 which requires RWORK to be ( K(1+NRHS) + 2*NRHS ), where K could be as large as number of columns in matrix A. The same is actual for CGELSD.
-
committed by Julie Langou (SVN revision r765, on Thu, June 24 2010)
bug0058 :: variable N0 in xLASQ3 is INPUT/OUTPUT. (The comments said INPUT.)
-
CORRECTED - see svn r750
-
bug report and bug fix are from William Gandler (NIH/CIT) on October 16, 2009; April 23, 2010; May 01, 2010, May 03, 2010. to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r750, on Fri, May 27 2010)
bug0057 :: Non-eigenvectors from DGEEV, problem in balancing
-
CORRECTED
-
Same bug than bug0106
-
bug report sent by Numpy team on April 22nd, 2010
-
see forum topic 1818
-
see follow-up on lapackers on April 22nd from Jim "bug in DGEHRD" "The balancing is choosing to scale some rows/columns by factors like 1e18, which rather amplifies tiny rounding errors in the (presumably correctly) computed eigenvectors of the balanced matrix, when balancing is undone at the end. The expert driver interface dgeevx would let the user disable balancing, until we figure out whether this is a bug or a feature, I’m not sure which."
-
Corrected by Bradley Lowery, Rodney James, Julien Langou on May 26 2013
bug0056 :: Non-orthogonal eigenvectors returned from DSYEVR
-
CORRECTED, rev 1540
-
bug report sent by Scipy team on April 22nd
-
Confirmed by Rodney on Tue, 17 Feb 2011
-
" I can reproduce similar problems that the user encountered with non-orthogonal eigenvectors when only
-
a few eigenvalues are requested. This also happens with SSYEVR. If I set ABSTOL to SLAMCH(Safe minimum),
-
the problem goes away in SSYEVR, and improves with DSYEVR but does not completely go away."
-
Corrected by Osni on Mon May 4th 2015
bug0055 :: Missing arguments descriptions of work and uplo in [csz]syequb
-
CORRECTED - see svn r740
-
bug report sent by Paul Roberts (NAG) on Fri, 13 Apr 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r740, on Fri, Apr 13 2010)
bug0054 :: Fix comment some of the argument descriptions have the wrong type.
-
CORRECTED - see svn r739
-
bug report sent by Paul Roberts (NAG) on Fri, 12 Apr 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r739, on Fri, Apr 12 2010)
bug0053 :: Fix external declaration issue in testing suite file: cebchvxx.f
-
CORRECTED - see svn r738
-
bug report and fix sent by Michael Chuvelev (Intel) on Fri, 5 Apr 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r738, on Fri, Apr 5 2010)
bug0052 :: Incorrect NRHS parameter in call to ?SYTRS from ?la_{po,sy,he}rfsx_extended.f.
-
CORRECTED - see svn r736
-
bug report and fix sent by Michael Chuvelev (Intel) on Fri, 2 Apr 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r736, on Fri, Apr 2 2010)
bug0051 :: INFO=N+2 in xDGGES due to too stringent threshold in xTGEX2.
-
CORRECTED - see svn r735
-
bug report sent by Ondra Kamenik on Tue Mar 16, 2010
-
see forum topic 1783
-
We have changed xLARFG to xLARFP in xGEQR2. xGEQR2 is used by xDGGES. The matrices are therefore different (although all of them are correct.) However for the matrix generated by xLARFP, xTGEX2 exceeds the THRES value by 10%, causing an error flag. We decided to increase THRES by a factor of 2. Although the bug was triggered by the change from xLARFG to xLARFP, XLARFP is not really at guilt.
-
confirmed by Julie Langou on Thu Mar 18 2010
-
fix provided by Guillaume Revy and Jim Demmel
-
committed by Julien Langou (SVN revision r735, on Thu Apr 2 2010)
bug0050 :: An extra argument after matrix A lines 348-249 in STFSM.f causes a crash of SGEMM call.
-
CORRECTED - see svn r732
-
bug report and fix sent by Alexander Kobotov (Intel) on Wed, 3 Feb 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r732, on Tue Mar 9 2010)
bug0049 :: output parameter GIVPTR stays uninitialized in case of quick exit (n.eq.0) or if the rank-1 modifier is small enough in *laed8.
-
CORRECTED - see svn r731
-
bug report and fix sent by Alexander Kobotov (Intel) on Wed, 3 Feb 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r731, on Tue Mar 9 2010)
bug0048 :: Hanging could occur in *gebal if a NaN is in input matrix.
-
CORRECTED - see svn r730
-
bug report and fix sent by Alexander Kobotov (Intel) on Wed, 3 Feb 2010 to<EMAIL_ADDRESS>-
committed by Julie Langou (SVN revision r730, on Tue Mar 9 2010)
bug0047 :: incorrect R/C parameter description in *gerfsx
-
CORRECTED - see svn r726
-
bug report sent by Michael Chuvelev (Intel) on Wed, 1 Mar 2010 to<EMAIL_ADDRESS>-
bug fix sent by James Demmel "R/C are input only by their usage" "there’s no FACT parameter in these routines"
-
committed by Julie Langou (SVN revision r726, on Tue Mar 9 2010)
bug0046 :: Incorrectly documented RWORK workspace in ZGESDD
-
CORRECTED - see svn r729 (LAPACK), rev 1541 (LAPACKE)
-
bug report from Zbigniew on Mon 15 Mar 2010
-
see forum topic 1779
-
committed by Julie Langou (SVN revision 729, on Thu Mar 18 2010)
bug0045 :: bug in dstemr.f when N = 2
-
CORRECTED - see svn r705 o bug report and fix sent by Ashutosh Mahajan (Mathematics and Computer Science Division of Argonne National Labs) on Thu, 10 Dec 2009 to<EMAIL_ADDRESS>o committed by Julien Langou (SVN revision 705, on Tue Dec 15 2009)
bug0044 :: bug in dsyevr.f when N = 1
-
CORRECTED - see svn r704 o bug report and fix sent by Ashutosh Mahajan (Mathematics and Computer Science Division of Argonne National Labs) on Fri, 11 Dec 2009 to<EMAIL_ADDRESS>o committed by Julien Langou (SVN revision 704, on Tue Dec 15 2009)
bug0043 :: VL, VU are referenced in lapack-3.2.1 dsyevr even if range.ne.V
-
CORRECTED - see svn r699 o bug report sent by Michael Chuvelev (Intel) on Wed, 14 Oct 2009 to<EMAIL_ADDRESS>"VL, VU are referenced in lapack-3.2.1 dsyevr even if range.ne.V" o committed by Julien Langou (SVN revision 699, on Tue Oct 20 2009)
bug0042 :: printing format misuse in ./TESTING/EIG/[s,c,d,z]drvgbx.f
-
CORRECTED - see svn r697
-
bug report sent by Kevin Wadleigh on Tue 29 Sep 2009 to<EMAIL_ADDRESS>"LAPACK routine ieeeck.f and compiler optimizations"
-
The LAPACK function IEEECK should be modified to keep compilers from optimizing away the line NAN6 = NAN5*0.0 and replacing it by NAN6 = 0.0. I’ve seen this happen using two different compilers at their default level of optimization. However, using NAN6 = NAN5*ZERO as in the attached file keeps this from happening.
-
committed by Julie Langou (SVN revision 697, on Wed Sep 30 2009)
bug0041 :: printing format misuse in ./TESTING/EIG/[s,c,d,z]drvgbx.f
-
CORRECTED - see svn r696
-
bug report sent by Michael Chuvelev (Intel) on Tue 29 Jul 2009 to<EMAIL_ADDRESS>"Bug in lapack-3.2.1/TESTING/EIG/zdrvgbx.f"
-
printing format misuse, this would possibly lead to a segmentation fault in case of errors in zgbsvxx.
-
committed by Julien Langou (SVN revision 696, on Tue Sep 29 2009)
bug0040 :: Q referenced in real TGSENs when WANTQ .FALSE.
-
CORRECTED - see svn r643
-
bug report from Mathew Cross on Tue 18 Aug 2009
-
see forum topic 1604
-
committed by Jason (SVN revision 643, on Tue Mar 3 2009)
bug0039 :: faulty workspace queries in GEESX
-
CORRECTED - see svn r657
-
bug report from Mathew Cross on Tue 18 Aug 2009
-
see forum topic 1602
-
committed by Julien (SVN revision 657, on Sun May 10 2009)
bug0038 :: no LIWORK query in DGELSD
-
CORRECTED - see svn r698
-
bug report from Mathew Cross on Tue 18 Aug 2009
-
see forum topic 1601
-
committed by Julie Langou (SVN revision 698, on Thu Oct 20 2009)
bug0038 :: out of range element access in DLASET when using DGELSS
-
CORRECTED - see svn r695
-
bug report sent by Tim Hopkins on Fri 31 Jul 2009
-
see forum topic 1582
-
committed by Julie Langou (SVN revision 695, on Fri Sep 25 2009)
bug0037 :: xLARFP and scaling
-
CORRECTED - see svn 754, 755
-
bug report sent by Pat Quillen on Wed 29 Jul 2009 to<EMAIL_ADDRESS>"xLARFP and scaling"
-
see Pat Quillen’s email, and quillen dlarfp2.f,
-
see Pat Quillen’s email, quillen dlarfp3.f, and quillen dlarf2.f.
-
committed by Julie Langou (SVN revision 695, on Fri Jun 18 2010)
bug0036 :: scaling in xSTEQR, xSTERF
-
CORRECTED - see svn 937
-
bug report sent by Pat Quillen on Fri 24 Jul 2009 to<EMAIL_ADDRESS>"Scaling in xSTEQR, xSTERF"
-
confirmed by Rodney on Tue Feb 21 2011
-
Correction: "changed matrix norm to M (max) from I (inf) for scaling of input matrix
-
and added check for zero norm in xSTERF (the xSTEQR already had this check)"
-
committed by Rodney on Tue Feb 24 2011
bug0035 :: dlarfb.f and likes
-
CORRECTED - see svn 946
-
bug report sent by Michael Chuvelev (Intel) on Tue 21 Jul 2009 to<EMAIL_ADDRESS>"Bug in LAPACK 3.2 dlarfb.f and likes"
-
see Michael Chuvelev and Julie’s emails, q.dat, tau.dat, and test_dorgql.f
-
confirmed by Rodney on Tue Feb 22 2011
-
committed by Rodney on Thu Mar 3 2011
bug0034 :: comments in SSPTRF not correct
-
CORRECTED - see svn r932 and 933
-
clarification asked by "sarnath" on Thu Jul 02 2009
-
confirmation of bug by "sarnath" and Julien Langou on Fri Jul 03 2009
-
The statement "JMAX is the column-index of the largest off-diagonal element in row IMAX" is not correct
-
see forum topic 1553
-
committed by Rodney (SVN revision 932, 933, on Tue Feb 17 2011)
bug0033 :: failure of zheevd on a specific matrix
-
CORRECTED, rev 1505
-
bug report sent by Cezary Sliwa (Instytut Fizyki PAN, Poland) on Thu 2 Jul 2009 to<EMAIL_ADDRESS>-
see Cezary Sliwa’s test code, Cezary Sliwa’s matrix, and Cezary Sliwa’s email.
-
Confirmed by Rodney on Tue, 17 Feb 2011
-
Corrected by Osni Marques on Oct 1st 2014
bug0032 :: matrix splitting problem with dstebz and sstebz
-
CORRECTED, rev 1540
-
bug report sent by Phil DeMier (IBM) on Mon 29 Jun 2009 to<EMAIL_ADDRESS>"matrix splitting problem with dstebz and sstebz"
-
Confirmed by Rodney on Tue, 08 Feb 2011
-
Corrected by Osni on Mon May 4th 2015
bug0031 :: whitespace fix in comments
-
CORRECTED - see svn r692
-
reported by "Jan" on Tue Jun 02 2009
-
see forum topic 1449
-
committed by Julie Langou (SVN revision 692, on Fri Sep 11 2009)
bug0030 :: line 641 of DTGSY2 (present as well in STGSY2, ZTGSY2, CTGSY2)
-
CORRECTED - see svn r766
-
Same bug than bug0060
-
reported by Zbigniew Leyk (College Station, TX) on Mon Jun 01, 2009
-
see forum topic 1445
bug0029 :: problem of WORKSPACE query with DSTEDC
-
CORRECTED - see svn r984
-
reported by Tiago Requeijo on Mon Mar 30 2009
-
see forum topic 1389
-
see also email from Edward Smyth on June 21st 2011
-
committed by Rodney (SVN revision 984, on Wed Jun 22 2011)
bug0028 :: failure of convergence of DHGEQZ for some specific matrix pencils
-
CORRECTED - see svn r1272, 1271
-
reported by Vasile Sima on Thu Jan 22 2009
-
see: email from Vasile
-
more information at: <a href=http://www-math.ucdenver.edu/~langou/lapack-3.2/lapack_known_issues.html>lapack known issues]
-
committed by Rodney (SVN revision r1272, 1271, on Tue Apr 17 2012)
bug0027 :: misleading comment in the header of DGHEQZ, the 2x2 block of the real Schur form are not as claimed
-
CORRECTED - see svn r929
-
reported by Vasile Sima on Tue Jan 27 2009
-
see: email from Vasile
-
more information: more specifically Vasile is reporting that the comments:
* [...] H contains the upper quasi-triangular
* matrix S from the generalized Schur factorization;
* 2-by-2 diagonal blocks (corresponding to complex conjugate
* pairs of eigenvalues) are returned in standard form, with
* H(i,i) = H(i+1,i+1) and H(i+1,i)*H(i,i+1) < 0.
are not correct
-
committed by Rodney James (SVN revision r929, on Tue Feb 17 2011)
bug0026 :: problem when playing with DGEEV and gfortran optimization flags
-
CORRECTED - see svn 1239
-
reported by Pauli Virtanen (scipy team) on Sat Dec 06 2008 (email to<EMAIL_ADDRESS>-
see: email from Pauli Virtanen see: http://scipy.org/scipy/scipy/ticket/709
-
Confirmed by Rodney on Tue, 08 Feb 2011
-
A patch has been proposed by Hong Bo Peng.
-
Issue was actually in DHGEQZ, the update to B22 was missing
-
committed by Rodney (SVN revision 1239, on Tue Apr 3 2012)
bug0025 :: serious problem in DGESDD: DGESDD returns negative singular values with INFO = 0
-
CORRECTED - see svn r760
-
reported by Guy Bencteux on Sat Dec 06 2008
-
see forum topic 847
-
At the time, Julie was not able to reproduce the bug. The bug is highly BLAS dependent.
-
on Sat Jun 19 2010, Bruno Pinçon from ESIAL, reported another matrix with the same problems
-
see forum topic 1868
-
we were able to reproduce the problem with MacOS with gfortran reference LAPACK and vecLib BLAS, we can not reproduce the problem with reference LAPACK and reference BLAS.
-
A patch has been proposed and committed by Julien Langou. (See forum topic 1868.)
-
Note: there is strong evidence that the bug of Guy Bencteux and this one are the same, although we were never able to reproduce Guy’s problem.
bug0024 :: the notation A' is confusing for complex matrices. Does A' stand for A transpose of A Hermitian transpose?
-
CORRECTED - see svn r969, 966 and 965
-
reported by Clint Whaley early July 2009
-
LAPACK is not consistent in it use of the notation for transpose and Hermitian transpose.
-
The use of LAPACK A' is not consistent with the BLAS useage.
-
We note that the Matlab/Scilab/Octave convention is A' stands for "conjugate transpose" and A.' stands for "transpose".
-
In the Z routines, LAPACK uses the notation A' 669 times, it means "conjugate transpose" most of the time but it means "transpose" a few times (maybe 10 times max, for BLAS-like routines). The notation A*H, A*T, A*N is used 549 times, The notation AT, AN, A^H 19 times. (This is just for the Z routines.)
-
see Julien’s emails
-
vote on the lapackers mailing list: A*T (or AT) and A*H (or AH): Clint Whaley, Jim Demmel, Sven Hammarling, Antoine Petitet, Daniel Kressner A' (for A*H) and A.' for (A*T): Julien Langou (I love to be that supported by the lapackers!)
bug0023 :: SROTMG and DROTMG uses deprecated Fortran ASSIGN statement and assigned GOTO statement
-
CORRECTED - see svn r691
-
reported by Marco Atzeri on Fri Mar 06 2009
-
see forum topic 1420
-
committed by Julie Langou (SVN revision 691, on Thu Sep 10 2009)
bug0022 :: workspace query bug with DGEJSV (when only left or right singular vectors desired)
-
CORRECTED - see 891 and 964
-
reported by Allin Cottrell on Tue Jan 15 2009
-
confirmed by Julien Langou on Fri Jan 30 2009
-
see forum topic 866
-
all information sent to Zlatko Drmac
-
committed by Julie Langou (SVN revision 891 and 964)
bug0021 :: in DGESDD, workspace query gives a value smaller than the minimal value given in the header to run the routine
-
CORRECTED - see svn r649
-
reported by Guy Bencteux on Sat Dec 06 2008
-
see forum topic 846
-
committed by Julie Langou (SVN revision 649, on Tue Mar 17 2009)
bug0020 :: in xGESDD, workspace query can overflow for large matrices
-
CORRECTED
-
reported by Stephan Ripke (Broad Institute, Boston) on Thu May 21 2009
-
confirmed by Julien Langou on Thu May 21 2009
-
see forum topic 1418
-
It’s just the usual 32-bit integer overflow issue, which is a user problem, not a bug in the code.
-
Recompiling everything with 64-bit integers is the correct way to deal with this issue.
bug0019 :: make install generates a "** Error: Time for operations was zero" too easily
-
CORRECTED - see svn r693
-
negative flop counts can be generated by make install
-
reported by Sergei Steshenko on Thu Nov 20 2008
-
see: emails
-
committed by Julie Langou (SVN revision 693, on Fri Sep 11 2009)
bug0017 :: in CHBGST/ZHBGST, reference to uninitialized elements of RWORK in the DO 240 and DO 470 loops
-
CORRECTED - see svn r656
-
patch given by Lawrence Mulholland (NAG) on Wed May 06 2009
-
see forum topic 1408
-
committed by Julien Langou (SVN revision 656, on Sun May 10 2009)
bug0016 :: problem in workspace query for CGEESX/DGEESX/SGEESX/ZGEESX
-
CORRECTED - see svn r657
-
bug report sent by Alexander V. Kobotov (Intel) on Mon, 6 Apr 2009 to<EMAIL_ADDRESS>"(c/z)geesx: no lwork=-1 branch at all, info = -15 is returned while doing lquery." The S and D versions were not exiting after WORKSPACE query as well.
-
committed by Julien Langou (SVN revision 657, on Sun May 10 2009)
bug0015 :: referencing WORK(1) and IWORK(1) when IJOB=0 in CTGSEN/DTGSEN/STGSEN/ZTGSEN contradicts header description
-
CORRECTED - see svn r658,659
-
bug report sent by Alexander V. Kobotov (Intel) on Mon, 6 Apr 2009 to<EMAIL_ADDRESS>"(d/s)tgsen.f: iwork(1) always referenced: line 455: iwork( 1 ) = LIWMIN, documentation says that if IJOB=0 it shouldn’t, so NULL pointer causes a segfault." Same problem for C and Z versions and for the WORK array.
-
committed by Julien Langou (SVN revision 658 and 659, on Sun May 10 2009)
bug0014 :: CSYEQUB/ZSYEQUB/SSYEQUB/DSYEQUB/CHEEQUB/CHEEQUB: EXTERNAL and INTRINSIC list are not accurate (or not even present)
-
CORRECTED - see svn r660
-
bug report sent by Alexander V. Kobotov (Intel) on Mon, 6 Apr 2009 to<EMAIL_ADDRESS>"c(he/sy)equb: no slamch in external lists and lsame, intrinsics not described" Same problem for D and S versions and for the WORK array.
-
committed by Julien Langou (SVN revision 660 on Sun May 10 2009)
bugXXXX Wrong type for workspace in cpot01 and zpot01
-
CORRECTED - see svn r655
-
Bug reported by Julie Langou on Th. 04/30/09
-
Workspace types needed by CPOT01 and ZPOT01, they need to be REAL (or DOUBLE PRECISION) and not COMPLEX (or DOUBLE COMPLEX).
-
committed by Julie Langou (SVN revision r655, on Sun, May 3 2009)
bugXXXX Revert DLARFG to 3.1.0, move DLARFG to DLARFP and improved DLARFP
-
CORRECTED - see svn (r706, r707, r708, r710, r712, r713) + (r755)
-
Bug reported by Pat Quillen (MathWorks)
-
The Householder reflector generation routine dlarfg (for double precision) has been changed in LAPACK-3.2 by dlarfp to generate nonnegative diagonal elements (on the diagonal of the R factor of a QR factorization). There is an issue in the dlarfp subroutine in LAPACK-3.2. The bug report is from Pat Quillen from MathWorks, have participated in the bug fix: Pat Quillen, Jim Demmel, Sven Hammarling, Mark Hoemmen, Guillaume Revy, William Kahan, Julie Langou and Julien Langou.
-
Extensive work by Jim Demmel, Guillaume Revy, and William Kahan have revealed that the new Householder reflector that guarantees a positive diagonal of R in QR has two apparently unfixable drawbacks compared to the old reflector: 1) the computed reflector can be less orthogonal by a factor of about 4, (Jim, Guillaume and William are not sure why.) 2) this new routine is intrinsically more sensitive to over/underflow, this is now well understood, details are skipped here. None of these issues arise with the conventional Householder reflector.
-
So the decision is to
1) Fix as much as possible the xLARFP routines. This was corrected by Julien (see (r706, r707, r708, r710, r712, r713)) based on Jim's idea.
2) Back out the changes in LAPACK to go back to using the old reflector (xlarfg) everywhere (e.g. in xGEQRF, xGEQR2, etc.).
3) Keep the change that saves flops when u has lots of trailing zeros, since this is independently a good idea.
4) Change the name from xLARFP to xLARFGP and introduce new QR routines (xGEQRFP and xGEQR2P) that uses xlarfp to guarantee a new positive diagonal of R, for who needs it.
5) This requires to adapt the test suites
6) Note: only the QR routines have an xGEQRFP. While it seems that quite a few users care for QR factorization with nonnegative diagonal R. Noone seemed to care for this feature on LQ, QL or RQ. So we have left out these routines.
7) Steps 2 to 6 were done during r755 by Julie.
dead code* :: xLAHRD is now replaced by xLAHR2, xLAHRD is a dead code since LAPACK 3.1
-
xLAHRD will be removed at some point in the future from the distribution


Patchy
An online jukebox by Luminarys.
- Github
- Luminarys/patchy
- IRC
- #stew@rizon
See this page for abuse info.
Upload
If you have permissions:
rsync -rP \ your/local/music/ \ url.tbd:/var/music/
otherwise:
An online jukebox by Luminarys.
See this page for abuse info.
If you have permissions:
rsync -rP \ your/local/music/ \ url.tbd:/var/music/
otherwise:


Dear User 2
The application was reopened by User 1, the lead applicant on 12 June 2020:
1234 : Application 1
You can now make any changes assigned to you, before the lead applicant resubmits this application for assessment.
Review the application
Yours sincerely
Innovate UK, part of UK Research and Innovation
Tel: 0300 321 4357
Email: competitions@iuk.ukri.org


Recently I had to produce a demo video as part of a tool paper submission. Here are some notes I gathered in the process: they might be useful to my future self or to other wannabe videomakers.
Caveat emptor
My experience amounts to the one demo video I produced and a few (say, between 5 and 10) ones I have seen in the past few weeks. So, take this post with a grain of salt.
Also, these suggestions are targeted to CLI videos. I think some of these suggestions may also apply to a GUI demo, but I am certain that demonstrating GUIs presents additional layers of complexity which I never had to deal with, luckily.
What a demo is not
A demo is not a pitch: there is a fine line between demonstrating the capabilities of a tool and trying to sell it. A tool demo should not be flashy or bombastic. If your tool is groundbreaking, a plain presentation will not hide it. Just look at The mother of all demos, and notice how doug Englebart never tries to sell the features he demonstrates. Even his voice is always composed and soothing, even though he was presenting what amounted to sci-fi stuff back in the late Sixties.
A demo is not a live coding session, either. Live coding videos may be very interesting in their own right. Being improvised by nature, they can provide a unique standpoint to understand development/architectural choices because you can actually see the process leading to these choices. For instance, take a look at the Antirez Youtube channel. On the other hand, you cannot improvise a demo video. I believe these videos should have a more-or-less fixed structure. Also, typically they are required to be shorter than a given length (say, 10 minutes). So, you should do a bit of planning.
Demo structure
In my opinion, a demo should roughly consist of:
-
An overview of the problem your tool aims at solving;
-
A basic example of said problem;
-
A first invocation of the tool on the basic example, with as few arguments/options as possible;
-
A discussion of the tool output, showing that it does solve the basic example;
-
Additional invocations showing interesting arguments/options, and discussing the respective outputs. I believe it is best to use the same basic example for all invocations, but you may introduce slight variations (in that case, reserve some time to explain these variations);
-
Final information about the tool (availability, licensing, etc.)
Outline/TLDR
What I suggest is:
-
Write down a general structure of the video;
-
Practice all the commands you need to enter on the command line;
-
Make a text file with (more or less) everything you want to say in your voiceover;
-
Use a terminal recording tool to record your commands and their outputs, without any voiceover;
-
Record your screen as you play back the recorded terminal session and do the voiceover.
Practicing commands
Demos need to effectively show the features of the tool. Fumbling on the command line is not the best course of action toward that goal.
At the same time, I think that pasting commands, or recalling them from terminal history, is not as effective as typing them in. Typing gives you a chance to explain the command on the fly. This is very important when your command involves multiple arguments and flags. (This makes me think about Powerpoint-driven lectures. On average, they are not as effective as those where the teacher actually writes on a whiteboard, are they?)
Of course, if at some point of the demo you just need to append arguments to a previous command, then you should use the terminal history rather than typing the whole command all over again.
Writing down the voiceover
Again, it is hard to do a good voiceover without writing down more or less everything you are going to say. This is especially true for non-native English speakers. Writing down a script helps you realize if you know how to pronounce uncommon words, where to pause, and so on. It also gives you a feeling of how long the video is going to be, and what parts you might want to trim down.
Recording the terminal
Next, perform your demo on a terminal and record it with a tool like asciinema
.
Do not use a screen recorder at this stage.
Personally, I set up a full-screen terminal window with a big font size
(18pt at least) and fire up a tmux
session with a vertically-split pane.
The left pane is where I type commands, while the right pane contains a pager
(i.e. less
) with my voiceover text file.
-
A big font size means that, in the end, you can export your demo at low resolutions (576p or even 480p) and your commands will still be readable.
-
The right pane acts as a teleprompter for you and as subtitles for the audience.
-
At this stage, I don’t worry about timing. I scroll down the right pane at a slow but constant speed. When it is time to launch the first command, I switch to the left pane and type it in. When the command terminates, I switch back to the right pane and resume scrolling. And so on and so forth.
Adding the voiceover
Finally. Just fire up a screen recorder with microphone capture, play back the recorded terminal session, and describe what you are doing. Pause/resume the playback so that you have time to describe everything that is happening on the screen without rushing.
- I did the screen recording/voiceover part with QuickTime and iMovie 10, but I do not recommend the latter. It only exports to MOV and will force a 16:9 format by either cropping the recording (!!!) or adding ugly black bars, and the exported videos will be blurry. In the end I managed to undo most of the damage (i.e. remove the black bars and sharpen the video) thanks to Handbrake, but I recommend looking for less painful alternatives, or at least checking if newer versions of iMovies have improved on these issues.
- Always downmix your voiceover to mono. I see no reason why you should split your microphone (which is most likely mono) across a stereo audio track. (Of course, if you’re demoing an audio processor or similar stuff, you might want stereophonic audio…)
Sharing the video
If the video is targeted at reviewers only, I believe that hosting it on cloud storage is better than a relying on video sharing services such as YouTube or Vimeo, which might add unwanted compression to your video. On the other hand, these same services can typically handle higher traffic and hosted video are somewhat “more permanent” than those on cloud storage. Thus, they may be the best choice if you must provide a video link in the published version of your paper.
Good luck with your videos :)


--- layout: archive permalink: /authors/ title: "Posts by Author" author_profile: true --- {% include group-by-array collection=site.posts field="author" %} {% for author in group_names %} {% assign posts = group_items[forloop.index0] %}


Chris Cooksey
Menu
Projects
Back end:
Java
OOP
Spring
SQL
TDD
Front end:
HTML5
CSS3
TDD
Flexbox
jQuery
Other:
Git
Leadership
Presentation
Management
Communication


Transhack talk
- Category
- talks-conferences
- Timestamp
- Thu, 08 Dec 2016
I talked at TransH4CK's #ibuild4 conference about Hen Coop (formerly "Slime Mom"): what we do and how we do it! It was such an honor to be able to talk at the conference! I hope I have the pleasure of doing it again soon!
[Video] How to foster game dev collaboration within the trans & GNC community + a #demo by @slimemom's @LilySeabreeze #ibuild4 @TransH4CK pic.twitter.com/G8TGzUvXsQ
— The LOFT (@HackLoft) December 8, 2016


Microservices with Docker 101
Powered by Django
Powered by Golang
Powered by Flask
Powered by Ruby on Sinatra


Speech
Her Majesty's Chief Inspector Sir Michael Wilshaw's speech about school standards in Lancashire and across England.
I would like to start by thanking you for inviting me to speak today. Also, it was a joy and privilege to visit Millfield Science and Performing Arts College yesterday, where the children were delightful.
I look back with great fondness and nostalgia on my time as a secondary school head. I still think, as I’m sure you do, it’s the best job in the world. There is nothing more important than being a leader of a community which is shaping the lives of young people and through them, the society in which we live.
Of course, headship can be a tough, lonely and daunting job. There are going to be bad days that stay with you for a long time. Tough at the moment in the current financial climate and, as we await the Chancellor’s Autumn Statement next week, we can expect budgets over the next few years to be even tighter than they are now.
But let’s not allow ourselves to get too downcast. After all, when it comes to schools, the power resides with you in a way that I could never have envisaged when I first became a head 30 years ago. Successive governments have given you more autonomy, more freedom and more control over resources than ever before.
Whether you are in a local authority school, a free school or an academy, you’re the ones firmly in the driving seat, leading change and influencing education policy in a way I never could have envisaged 30 years ago.
In less than 2 weeks from now, I will publish Ofsted’s Annual Report – my fourth since being appointed Chief Inspector. Without giving too much away before the report is laid before Parliament, I’d like to share with you my thoughts on where we are as a nation in terms of educational standards.
It is fair to say that our schools are generally far better places than they were 30, 20 or just 10 years ago.
Children and young people are getting a significantly better deal than they were. The results of this summer’s GCSE and A Level examinations underline the transformation taking place in much of our education system across England. Greater autonomy matched by robust accountability have led to a steady overall improvement in standards over the past few years.
As well as improved outcomes at key stage 4 and 5, we have:
As a nation, our ability to sustain this progress and avoid slipping backwards depends on whether we can recruit and retain the best leaders in our schools.
Leaders who understand the importance of getting the right culture in the school and high enough expectations.
Leaders who understand that their chief purpose and mission is to lead the teaching in their school, to continually monitor what is happening in the classroom and to professionally develop staff to improve their performance.
As I have said on so many occasions, leadership is absolutely critical. Without good leadership, change gives way to stagnation.
Here in Lancashire you appear to have the right leaders in place to build on the achievements of recent years. However, in many parts of the country, I worry that a shortage of high-quality leaders coming through the system could jeopardise the chances of future success. I will be saying more about this in my report to Parliament in a couple of weeks.
Unless we address the capacity issues facing our system, we have little hope of overcoming the 3 fundamental issues that are preventing us from competing with the top educational performers in the OECD group of nations.
What are these 3 big issues? Firstly the unacceptably wide variations in performance both across and within the regions of England – a situation that consigns some children to substandard schools while affording other children with similar abilities and from similar backgrounds the opportunity to fulfil their potential.
Secondly, as I first highlighted in my Annual Report this time last year , a gap has emerged nationally between primary and secondary school performance – and the indications are this is not closing by very much. While primaries in the main are continuing to forge ahead right across the country, we have far too many secondaries that are not building on progress made at primary school, that are paying insufficient attention to transition from key stage 2 to 3 and that are ignoring the needs of the most able children. In the worst cases, they are too accepting of an anti-learning culture that tolerates poor behaviour and, particularly, low level disruption.
Thirdly, as a nation we are still blighted by the long tail of underachievement by the poorest children, especially in our secondary schools and among our White British communities from low income backgrounds. So let’s take a closer look at how much progress Lancashire is making in overcoming these over-lapping challenges.
By a number of key measures, you are doing well when comparing performance at both a regional and a national level.
The county’s primary schools are certainly doing well - with 89% of schools judged by Ofsted to be good or outstanding compared with 88% for the North West as a whole and 85% nationally.
In this year’s SATs at key stage 2, 81% of Lancashire pupils attained level 4 or above in reading, writing and maths. This is in line with the North West region also at 81% and just above the national figure of 80%.
But what about secondary schools? Well I’m pleased to say you are doing pretty well here too. 78% of secondary schools in Lancashire were judged good or better at their last inspection – well above the North West average of 70% and the England-wide figure of 74%.
The county certainly seems to be bucking the emerging north-south divide in GCSE attainment that was highlighted last week by the educational data firm School Dash and this is an issue I will be expanding upon in a couple of weeks.
This year 58% of pupils achieved 5 A* to C grades including maths and English. This was higher than the regional figure of 55% and the national figure of 56%.
Lancashire also outperformed many of what Ofsted calls its ‘statistical neighbours’ which share a similar demographic profile. A higher proportion of pupils here achieved 5 good GCSEs than their counterparts in local authority areas like Nottinghamshire, Northamptonshire and Staffordshire.
You deserve a great deal of the credit for the strong performance of the county’s secondary schools. Your hard work and leadership means that more than 55,000 Lancashire schoolchildren are benefitting from a good or better education from the age of 11.
However, as you are well aware, thousands of secondary school-age children in other parts of this region aren’t getting such a good deal and as a result, their life chances are being harmed.
Secondary school standards in places like Salford, Knowsley and down the M55 from here in Blackpool are, to put it bluntly, dire. Two-thirds of secondary schools in Blackpool are inadequate or require improvement, with only 42% of 16-year-olds achieving 5 A* to C grades in the key subjects this year.
So why is Lancashire doing so much better than some of its neighbours, and what on earth can be done to raise up standards in under-performing authorities in close proximity to you?
I would be very interested to hear your plans to do this.
The quality of support provided by the local authority is a factor. HMI based in this region tell me that Lancashire County Council takes a proactive approach to school improvement, certainly when compared to some other local authorities. They appear to have robust arrangements for monitoring schools that are causing concern and are challenging primary and secondary schools to ensure effective transition between key stages.
My inspectors also report that a growing number of secondary school leaders in Lancashire are offering effective professional support to other struggling schools in the county.
I have no doubt that school to school support – whether done within formal federation structures or on a more informal one-to-one basis - is absolutely key to driving improvement.
That is why as Chief Inspector, I am determined to recognise those leaders who are taking ownership of school improvement. The leaders who are committed to not only improving the prospects of children in their own schools but also to transforming the life chances of youngsters beyond the school gates.
Since September, when inspectors identify a leader who has played a key role in helping to turn round another school, Ofsted has started sending a letter to that headteacher to inform them that their leadership has been acknowledged as exceptional. That letter gets copied to the Secretary of State and those individuals will be mentioned in Annual Reports from here on.
For those exceptional leaders in Lancashire including people in this room, my question to you would be this: What could persuade or enable you to extend this support to schools outside the county boundaries – in places like Blackpool?
This is not to suggest that secondary schools in Lancashire are getting everything right. Far from it. I have already spoken about the third major challenge – probably the biggest challenge of all – facing our education system in this country. How can we do better by our poorest and most disadvantaged children?
When we look at outcomes for children eligible for free school meals in Lancashire, it is clear there is no room whatsoever for complacency.
In 2014 only 28% of free school meal pupils in Lancashire achieved five A* to C GCSE grades, including maths and English – a proportion which is below both the regional and national average.
The gap between free school meal and non-free school meal pupils in Lancashire is a massive 32% which again is above both the North West average of 30% and the national figure of 27%.
I am aware that there are some secondary schools which are putting in place effective strategies to narrow the attainment gap, including Ripley St Thomas Academy in Lancaster, Our Lady’s RC High School in Preston and the school I visited yesterday, Millfield, in Thornton, which earned the National Pupil Premium Secondary School of the Year Award in 2014.
However, it’s clear from the data that much more needs to be done to tackle the endemic under-achievement of poorer pupils in Lancashire and elsewhere. Nationwide, GCSE attainment has hardly narrowed in the last 8 years: in 2007 it was 28 percentage points; last year it was 27 percentage points.
Let’s remember that almost two thirds of children on free school meals are from white, low income, British homes. This group, both boys and girls, are the worst performing ethnic and cultural group in the country. Their lack of progress, especially at secondary school, is a scar on our system and must surely be the issue that troubles us more and more.
As an ex-secondary head who has spent a lifetime working in the poorest communities, I find this depressing. Quite frankly, too many of our secondary schools are not delivering the social mobility our country desperately needs.
It is certainly no longer the case that material poverty is an automatic predictor of failure. The impressive outcomes for free school meal children in London gives the lie to that idea. Poorer children of recent immigrants to the country – both from the Commonwealth and Eastern Europe – are also doing well across the country.
It is not only a moral imperative that we should do better for our poorest youngsters but also crucial if we are going to become a more productive nation and a more socially cohesive one.
So the question for you and for your colleagues across the country becomes ever more urgent. What can be done to raise ambitions and improve outcomes, particularly in secondary schools, to end the depressing cycle of under-achievement for our poorest youngsters?
What makes the difference for these children and others, and you know this already, is the culture and expectations of the school – a culture that is always determined by the quality of its leadership.
All my experience has taught me that when school culture is poor – where it’s disorganised and chaotic, it is the poor and the vulnerable who suffer most.
The best heads understand this and recognise the importance of developing an orderly and positive culture. Indeed, I would go further. Many of the best headteachers that I have met pursue a policy that is overtly counter-cultural because they believe that much in our society isn’t good for young people and not conducive to learning. They refuse to accept corrosive cultural norms and, indeed, often fight against them.
That is why the people in this room today are so important. We need leaders whose approach is always optimistic and always ambitious for every pupil in the school, regardless of the challenges and one brave enough to counter those cultural norms that I’ve just mentioned.
We also need leaders who understand the importance of getting the transition between primary and secondary school right. We have seen too many examples of pupils, especially the more able ones, leaving primary to encounter a secondary school culture that demotivates them.
You may have seen the report Ofsted published a couple of months ago on key stage 3 which reinforced my concerns about the early years of secondary education.
My inspectors found that in too many secondary schools, this stage was not being given the priority it deserved. Its status as the poor relation to other key stages is exemplified in the way many schools monitor and assess pupils’ progress and in the way they allocate resources and timetable teachers. Too often, inspectors found that the best and most experienced teachers were heavily weighted towards key stages 4 and 5.
I am also concerned that further up the age scale, too many secondary schools are failing to prepare young people for the world of work. We have found that the careers advice is often not encouraging enough youngsters into vocational routes and apprenticeships that would serve them best.
As another report we brought out last month on apprenticeships made clear, schools – especially those with sixth-forms – have a duty to provide impartial careers guidance to all students. Young people at 16 need to understand the options before them. They should have been exposed to the world of work so that they can make informed choices. Not every bright youngster needs to go to university to have a successful career. And schools have to realise this.
As well as the right leadership, it is of course the quality of teaching that makes such a crucial difference to pupils’ learning and achievement. Studies show that the effects of high-quality teaching are especially significant for pupils from disadvantaged backgrounds. That is why teacher recruitment and retention is so vitally important and I am sure it is an issue on your agendas as I talk to you this morning. In Lancashire, the most recently published workforce survey data from the Department for Education suggested just 0.1% of full-time posts were vacant. I will be very interested to learn from you afterwards whether this tiny figure matches your experience on the ground.
It does seem that teacher training provision in the county is strong and you have a good supply of new entrants coming through the various pipelines. This includes, at the last count, 5 accredited SCITT partnerships, 15 teaching schools, 2 of the region’s Higher Education Institutes and a number of Teach First recruits working in Lancashire’s schools.
The freedom that good and outstanding schools now have to take more control of teacher training, for example through School Direct, has been a positive step. But it is vital that training partnerships ensure that good teachers go where they are needed most and aren’t just cherry-picked by the same small group of high performing schools. We also need to make sure these partnerships are evenly distributed so they adequately serve all parts of the country, including the more disadvantaged and geographically isolated parts of this county.
Market forces alone won’t achieve this so I will continue to press the government to develop a clearer and more centrally driven strategy to make this happen.
It is also important that we get the governance arrangements right in our schools. You may have seen the commentary I published earlier this week in which I repeated my call for a more professional approach to the issue, especially in our most challenging schools serving the most deprived communities.
In the last academic year alone, there were nearly 500 schools where inspectors were so concerned about the performance of the governing board that they called for outside experts to be drafted in to carry out an urgent external review of governance.
Being a governor is far more demanding than it has ever been in the past and it carries huge levels of responsibility. For this reason, I believe we need to call time on the age of the well-intentioned amateur, especially when it comes to the key positions of chair and vice-chair.
I have commissioned inspectors to carry out an in-depth and far-reaching survey into the effectiveness of governance in our schools. We will publish this report next year.
Finally, I am determined to ensure that Ofsted is part of the solution to the challenges I have spoken about today. The solution and not the problem.
Now we know that Ofsted is never going to win any popularity contest but I have always been a firm believer in the power and influence of inspection to improve young people’s lives. It is the reason I took this job in the first place.
I want good and ambitious headteachers to recognise Ofsted as an ally in helping them to improve their schools and tackle deep-seated problems. Certainly that’s how I saw the inspectorate when I was a head. I would have found it much more difficult to raise standards in the schools I led if Ofsted had not been around to support me.
Since I took on this role in January 2012, I have overseen significant changes to the way Ofsted is organised and the way it inspects. We have substantially revised and streamlined all of our inspection frameworks and, perhaps most importantly of all, replaced the old ‘satisfactory’ grade with ‘requires improvement’. As a result, mediocre schools now know that only a good standard of education is good enough.
We have also established a regional structure to gather intelligence on standards across all areas of the country. We now have teams of knowledgeable HMI and Senior HMI , led by a Regional Director, in 8 regions of the country. They are well placed to shine a much sharper spotlight on strengths and weaknesses in each region and to both challenge and support individual institutions, multi-academy trusts and local authorities to improve.
I recognise that the inspection stakes are far higher than they’ve ever been before. That is why the pressure on Ofsted to get it right is also much higher. I genuinely believe we do get it right most of the time and providers continue to report high levels of satisfaction with the inspection process and the outcomes.
However, we know we need to continue driving up the quality and the consistency of all our inspections. That is why, 2 months ago, we made a number of landmark changes.
First, we introduced a new overarching inspection framework that focuses on the key issues across early years, schools and further education. This ‘common inspection framework’ will provide greater coherence across our inspection of the different remits and make it easier for parents and learners to compare standards when making choices between education providers.
Second, we introduced significant changes to the way we inspect good schools and colleges. Since September, HMI have been carrying out shorter, more flexible inspections, with a much stronger focus on professional dialogue with senior leaders. The starting assumption of HMI is that the school remains a good school. This should engender an atmosphere in which honest, challenging, professional dialogue can take place. Thirdly, we brought the contracting of school and further education inspections in-house. This one measure will bring much greater assurance over the selection, training and monitoring of inspectors. Under these new arrangements, more than 70% of Ofsted Inspectors are serving leaders from good or outstanding schools.
Finally, we are setting up scrutiny committees in each of Ofsted’s regions, made up of HMI and senior education practitioners, mostly heads, not involved in carrying out inspections for Ofsted. They will assess and rule on the internal reviews of complaints about inspection. Their decision will be binding on Ofsted.
So I hope you will agree that as an organisation, we do listen and take notice of what the profession is telling us. We have acted on your concerns about no-notice inspections, about the drawbacks of outsourcing inspections and the need to avoid making every inspection the same ‘cliff-edge’ experience.
And we will continue – through our ‘mythbusting’ document and other means – to try to curb unnecessary workload pressures on teachers by dispelling some of the common misconceptions about what Ofsted requires when it inspects. Leadership teams need to justify their practices around marking, pupil feedback and lesson planning, observation and grading on their own merits rather than erroneously citing Ofsted as the reason for doing these things and putting pressure on staff.
I have covered a lot of ground this morning and touched on some weighty topics. I hope you will reflect on the challenges I’ve laid down at your door and accept them in the spirit that they’re intended.
Whilst we still have a long distance to travel, we should never lose sight of just how far we have come over recent years. I am really pleased that secondary schools in Lancashire are in many ways setting the benchmark for other areas of the country, particularly in the North of England.

Thank you for listening.