[scilab-Users] Problems of compilation of nightly build under opensuse

[Sébastien Bihorel]

Hi Michael, Sylvestre and Pierre,

I have download and uncompressed the nightly build
scilab-master-1256156380.bin.linux-i686.tar.gz. I was able to start it
but could get much further because it appears that the 'getd' function
is not functional. If you uncompress the attachement to /testing/tmp,
and try getd('/testing/tmp/'), the function myanalysis is not
accessible. The function can be loaded with
exec('testing/tmp/myanalysis.sci'), and then be executed (myanalysis
does nto take any input arguments). Scilab will complaining about
missing variable which actually be functions loaded from local
directories with getd.

So, I am still unable to test the new Nelder-Mead algorithm...

Sebastien

If you want to reproduce

On Mon, Oct 19, 2009 at 7:58 AM, Sébastien Bihorel <pomchip at free.fr> wrote:
>
> Hi Michael,
>
> I will give the new nightly build a try this evening and let your know whether or not I experience the same problems. In case I do, I would sent my code and data to the bug tracking system, so you could try to reproduce them.
>
> Sebastien
>
>
> On Mon, Oct 19, 2009 at 4:49 AM, Michaël Baudin <michael.baudin at scilab.org> wrote:
>>
>> Dear Sébastien,
>>
>> Thank you for reporting your experience with fminsearch
>> in the nighty build.
>> Any bug which might be discovered before the actual release
>> of v5.2 will help us to release an even more robust version.
>>
>> As soon as you are able to run any version of Scilab (be it a
>> nighty build or a source version), whatever the platform,
>> do not hesitate to report any bug you may find on our
>> bug tracking system :
>>
>> http://bugzilla.scilab.org
>>
>> Could you clarify the error message you got with respect
>> to the "funccount vs funcCount" problem ?
>>
>> Your problem with the number of function evaluations is not clear for
>> me. I checked the behaviour of Scilab's fminsearch by comparison
>> with Matlab's, and found exactly the same number of function
>> evaluations in the end (I can provide further details if necessary).
>> The initial number of function evaluations is n+1,
>> since one function evaluation is required for each vertex.
>>
>> Best regards,
>>
>> Michaël
>>
>> Sébastien Bihorel a écrit :
>>
>>> By the way,
>>>
>>> If that can help anybody finalizing the Nelder-Mead algorithm, I saw something that looks like a bug to me. Although I was unable to run the fminsearch function to its end, I saw that for the initial iteration (ie. the iteration 0), more than one function evaluations are reported... this is weird, the cost or objective function (however your want to call it) should only be evaluated once, ie using the initial guesses of the parameters to optimize.
>>>
>>> Sebastien
>>
>>
>