JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for ALLSTAT Archives


ALLSTAT Archives

ALLSTAT Archives


allstat@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ALLSTAT Home

ALLSTAT Home

ALLSTAT  2000

ALLSTAT 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

SAS/IML: non linear optimization procedures: NLPTR, NLPNRA, NLPQN and NLPCG

From:

Thierry Gorlia <[log in to unmask]>

Reply-To:

Thierry Gorlia <[log in to unmask]>

Date:

Tue, 22 Aug 2000 14:32:20 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (75 lines)

Dear allstat,

We have a problem with the SAS/IML non linear opimization procedures such as
NLPTR, NLPNRA, NLPQN and NLPCG. Let's call them the "NLOP"

We are trying to fit a gompertz survival distribution on simulated survival
data (obtained from piecewise exponentials + censoring). We are first
computing the starting values by non-linear regression (NLIN). These values
are then used as starting values in the log likelihood non linear
optimization procedure. Everything goes well for the first 50-200
simulations. Then the "NLOP" (at least those I have tested, see above)
generates a fatal error with the following message attached: 

ERROR: The function value of the objective function cannot be computed
during the optimization    
process.


We thought that providing the analytical form of the gradient/hessian would
solve but without success.
What astonished us is that for errors like:
 
WARNING: Optimization routine cannot improve the function value.

ERROR: TRUREG Optimization cannot be completed.

the procedure resumes and the next simulation is entered, documenting the
previous one with a return code equal to -5 which can be detected and
treated appropriately.
This is what we would expect for all errors. On the contrary, after the
fatal error has occured,  the "NLOP" are returning the same output for all
the next simulated datasets and no specific return code is output.
The RESUME statement has no effect. What is probably needed is a
reinitialization of the the "NLOP" but how to do that ? Relaunching the PROC
IML procedure ?

Has somebody an idea ? Any suggestion is welcome. 


Thierry Gorlia



	
----------------------------------------------------------------------------
----------------
	 Thierry Gorlia             Email : [log in to unmask]
	 Statistician
	 Health Economic Unit
	 Quality of Life Unit
	 European Organization for research and Treatment of Cancer
	 Data Centre - Avenue Mounier 83, 1200 Brussels, Belgium
	 Phone : +32 2 774 16 80
	 Fax     : +32 2 779 45 68

	    Web site: http://www.eortc.be/home/qol/
 
----------------------------------------------------------------------------
----------------














%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager