[MITgcm-support] tutorial_global_oce_optim optimisation failed
andrew.mcrae at physics.ox.ac.uk
Mon Apr 30 17:38:57 EDT 2018
I tried a few steps of this, but the output of optim.x always has
cost function............... 0.62002323E+01
norm of x................... 0.00000000E+00
norm of g................... 0.12730927E-01
near the end, with no decrease in the cost function. So I guess it's not
actually taking the step?
On 27 April 2018 at 18:04, Andrew McRae <andrew.mcrae at physics.ox.ac.uk>
> !!! Okay...
> Yes, it produced the .opt0001 file. I'll see how this goes.
> On 27 April 2018 at 17:57, Matthew Mazloff <mmazloff at ucsd.edu> wrote:
>> Its been awhile, but I am pretty sure that is the normal output. It says
>> “fail", but it did give you a new and ecco_ctrl_MIT_CE_000.opt0001
>> (correct?) and if you unpack and run likely the cost will descend.
>> I think it worked correctly. lsopt/optim are just confusing…but I think
>> its working. I think all is good!
>> On Apr 27, 2018, at 8:25 AM, Andrew McRae <andrew.mcrae at physics.ox.ac.uk>
>> Just separating this from the other thread
>> I got the bundled MITgcm optim routine built (having made these changes
>> based on this
>> thread from 2010 and this
>> one from 2016).
>> I use OpenAD to create the adjoint.
>> My steps are:
>> 1) in the build directory, run ../../../tools/genmake2 -oad
>> 2) run make depend and make adAll
>> 3) copy input_oad/ into a new folder scratch/
>> 4) within scratch/, run ./prepare_run
>> 5) copy mitgcmuv_ad from build/ into scratch/, copy optim.x into
>> 6) run ./mitgcmuv_ad
>> 7) in scratch/OPTIM, create symlinks to ../data.optim and ../data.ctrl
>> 8) copy the files ecco_cost_MIT_CE_000.opt0000 and
>> ecco_ctrl_MIT_CE_000.opt0000 into the OPTIM subdirectory
>> 9) run ./optim.x within the subdirectory
>> The full output is attached, but I assume the optimisation failed since
>> the last lines are
>> optimization stopped because :
>> ifail = 4 the search direction is not a descent one
>> Any ideas? (I guess this isn't something that is tested in the daily
>> In the meantime, I'll try the m1qn3 routine as in the other thread, which
>> should help distinguish between a problem with the optimisation routine or
>> the gradient generated by mitgcmuv_ad.
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MITgcm-support