You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Fortran 77 version of UOBYQA encounters infinite cyclings very often if PRIMA_REAL_PRECISION is 32. This has been observed on the following CUTEst problems:
Surely, this is not a concern for us, because it happens only to the original Fortran 77 implementation. Nevertheless, it is still interesting to investigate the reason underneath, to further understand the shortcomings of the original Fortran 77 implementation.
The text was updated successfully, but these errors were encountered:
zaikunzhang
changed the title
The Fortran 77 version of UOBYQA constantly encounters infinite cycling very often if PRIMA_REAL_PRECISION is 32
The Fortran 77 version of UOBYQA encounters infinite cycling very often if PRIMA_REAL_PRECISION is 32
Oct 13, 2023
zaikunzhang
changed the title
The Fortran 77 version of UOBYQA encounters infinite cycling very often if PRIMA_REAL_PRECISION is 32
The Fortran 77 version of UOBYQA encounters infinite cyclings very often if PRIMA_REAL_PRECISION is 32
Oct 13, 2023
The Fortran 77 version of UOBYQA encounters infinite cyclings very often if
PRIMA_REAL_PRECISION
is 32. This has been observed on the following CUTEst problems:There do exist problems where the solver works, e.g.,
HILBERTA
andPRICE3
, but they seem to be rare among problems under 3 dimensions.This is observed via the workflow https://github.com/fortlab/prima/actions/workflows/profile_uobyqa_small_sq.yml with 2394f47 . To reproduce it locally, do the following in a MATLAB command window.
This will drive UOBYQA into an infinite cycling.
Surely, this is not a concern for us, because it happens only to the original Fortran 77 implementation. Nevertheless, it is still interesting to investigate the reason underneath, to further understand the shortcomings of the original Fortran 77 implementation.
The text was updated successfully, but these errors were encountered: