From nashjc at uottawa.ca  Tue Nov 16 23:52:42 2010
From: nashjc at uottawa.ca (Prof. John C Nash)
Date: Tue, 16 Nov 2010 17:52:42 -0500
Subject: [Rd] DBLEPR?
In-Reply-To: <AANLkTi=uPiLv-GWGDN6O=m=o4aTA+8ASesS2VmuzkAvA@mail.gmail.com>
References: <4CE2EAF7.5020202@uottawa.ca>	<AANLkTimbP_BfXjzjXNqkJq7a4=Mu_rr9r6UXyTogsEfd@mail.gmail.com>	<4CE30050.3090909@uottawa.ca>
	<AANLkTi=uPiLv-GWGDN6O=m=o4aTA+8ASesS2VmuzkAvA@mail.gmail.com>
Message-ID: <4CE30B3A.4030109@uottawa.ca>

My reaction is leaning heavily towards "Virtuoso!" as opposed to "Show Off!".

Thanks very much.

JN


On 11/16/2010 05:39 PM, Douglas Bates wrote:
> Try this.
> 
> On Tue, Nov 16, 2010 at 4:06 PM, Prof. John C Nash <nashjc at uottawa.ca> wrote:
>> We've tried to contact Stig since July. Possibly he changed emails.
>>
>> My thought was to use Rprintf as suggested and was looking into doing that to see if our
>> optimx problems would go away. Will keep it as open issue while we give a bit more time
>> for response, and welcome input from others.
>>
>> JN
>>
>>
>> On 11/16/2010 04:52 PM, Douglas Bates wrote:
>>> On Tue, Nov 16, 2010 at 2:35 PM, Prof. John C Nash <nashjc at uottawa.ca> wrote:
>>>> I normally see digest once per day, but got msg from Doug Bates so responding with context.
>>>
>>>> UCMINF is a package on CRAN that implements a variable metric minimizer.
>>>
>>> A pedant might point out that the package is called "ucminf".
>>>
>>>> It does quite
>>>> well on unconstrained problems. Stig Mortensen packaged the Fortran version for R, but is
>>>> not at moment responding to emails. There's also a Matlab version. We have it in optimx
>>>> and get some occasions where it just stops if we set trace>0. Other times we can't get it
>>>> to fail. My guess is something like an undefined variable or a bad declaration of a
>>>> pointer, but C and C++ are not languages I've much experience with.
>>>
>>> Well, it doesn't work well for me because my version of gfortran (GNU
>>> Fortran (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5) objects to the format
>>> strings in some of the Fortran WRITE statements.
>>>
>>> The recommended approach is to avoid all Fortran I/O including writing
>>> to a Fortran character array.   As there are only 3 such WRITE
>>> statements in the Fortran code it would be very simple to replace them
>>> with calls to C functions that in turn call Rprintf.  However, it
>>> would be best if Stig could take ownership of the modifications.
>>



[Rd] DBLEPR?
Prof. John C Nash