[MITgcm-devel] testreport again

[Martin Losch]

Hi Jean-Michel, Oliver,

the new flag for testreport, that I just checked in works fine with all experiments, except for the ones that compile ptracers, e.g.
e.g., cfc_example, exp4, global_ocean.90x40x15. The reason is that “make small_f” does not work properly, eg. in global_ocean_ebm I get this:

>>> make small_f
[…]
cat monitor_ad.F |  /lib/cpp -traditional -P -DTARGET_NEC_SX -DWORDLENGTH=1 -DHAVE_CLOC -UHAVE_SIGREG -DSEAICE_VECTORIZE_LSR -DSEAICE_VECTORIZE_LSR_ZEBRA -DCG2D_OUTERLOOPITERS=10 -DCG3D_OUTERLOOPITERS=10 -DALLOW_USE_MPI -DHAVE_SYSTEM -DHAVE_FDATE -DHAVE_ETIME -DHAVE_SETRLSTK -DHAVE_STAT -DHAVE_NETCDF -DHAVE_FLUSH  -I/SX/usr/include -I/home/repo/nodes/netcdf/3.6.1_32_dw/SX/include -I/SX/opt/mpisx/LC110002/include | ../../../tools/set64bitConst.sh  > monitor_ad.f
cat monitor_g.F |  /lib/cpp -traditional -P -DTARGET_NEC_SX -DWORDLENGTH=1 -DHAVE_CLOC -UHAVE_SIGREG -DSEAICE_VECTORIZE_LSR -DSEAICE_VECTORIZE_LSR_ZEBRA -DCG2D_OUTERLOOPITERS=10 -DCG3D_OUTERLOOPITERS=10 -DALLOW_USE_MPI -DHAVE_SYSTEM -DHAVE_FDATE -DHAVE_ETIME -DHAVE_SETRLSTK -DHAVE_STAT -DHAVE_NETCDF -DHAVE_FLUSH  -I/SX/usr/include -I/home/repo/nodes/netcdf/3.6.1_32_dw/SX/include -I/SX/opt/mpisx/LC110002/include | ../../../tools/set64bitConst.sh  > monitor_g.f
cat ptracers_ad_dump.F |  /lib/cpp -traditional -P -DTARGET_NEC_SX -DWORDLENGTH=1 -DHAVE_CLOC -UHAVE_SIGREG -DSEAICE_VECTORIZE_LSR -DSEAICE_VECTORIZE_LSR_ZEBRA -DCG2D_OUTERLOOPITERS=10 -DCG3D_OUTERLOOPITERS=10 -DALLOW_USE_MPI -DHAVE_SYSTEM -DHAVE_FDATE -DHAVE_ETIME -DHAVE_SETRLSTK -DHAVE_STAT -DHAVE_NETCDF -DHAVE_FLUSH  -I/SX/usr/include -I/home/repo/nodes/netcdf/3.6.1_32_dw/SX/include -I/SX/opt/mpisx/LC110002/include | ../../../tools/set64bitConst.sh  > ptracers_ad_dump.f
sxmpif90 -Pstack -sxace -pi -pi auto fullmsg exp=barrier,ucase,timestep_tracer,ilnblnk,ifnblnk,cycle_tracer,pressure_for_eos,sw_temp,sw_ptmp,gsw_pt_from_ct rexp=fool_the_compiler,fool_the_compiler_r8,bar2,sw_adtg,gsw_ct_from_pt,gsw_gibbs_pt0_pt0 expin=barrier.f,timestep_tracer.f,fool_the_compiler.f,bar2.f,utils.f,cycle_tracer.f,pressure_for_eos.f,seawater.f,gsw_teos10.f -C vsafe -c ptracers_dyn_state_mod.f
sxf90 fatal : File could not open : barrier.f
make: *** [ptracers_dyn_state_mod.o] Error 1

Why is the fortran compiler (sxmpif90) called for ptracers_dyn_state_mod.f when I do “make small_f”? What’s different for this package?

Do you have any clue?

Martin

> On 07 Apr 2015, at 15:22, Jean-Michel Campin <jmc at ocean.mit.edu> wrote:
> 
> Hi Martin,
> 
> New option name "-small_f" sounds good to me.
> 
> Cheers,
> Jean-Michel
> 
> On Tue, Apr 07, 2015 at 11:58:32AM +0200, Martin Losch wrote:
>> Hi Jean-Michel,
>> 
>> I can try to implement such an option. What do you suggest for a name? ???-small_f??? (already long, but ???-explict_small_f??? is even longer).
>> 
>> Martin
>> 
>>> On 24 Mar 2015, at 15:08, Jean-Michel Campin <jmc at ocean.mit.edu> wrote:
>>> 
>>> Hi Martin,
>>> 
>>> I would prefer to keep the testreport built as close as possible
>>> to the "normal" built, so that we really "test" experiments in
>>> the same conditions.
>>> The other thing is that I am not sure if this "small_f" target will fix completly
>>> the inlining issue for AD and OAD built, but it does not matter too much.
>>> 
>>> What about adding a new option to testreport that would go through this
>>> intermediate "samll_f" step ?
>>> 
>>> Cheers,
>>> Jean-Michel
>>> 
>>> On Tue, Mar 24, 2015 at 01:22:03PM +0100, Martin Losch wrote:
>>>> Hi there,
>>>> 
>>>> do you think we can modify the build procedure for testreport? I.e. in
>>>> makemodel()
>>>> replace 
>>>> 	    $MAKE_CMD $TARG >> make.tr_log 2>&1
>>>> by
>>>> 	    $MAKE_CMD small_f >> make.tr_log 2>&1
>>>> 	    $MAKE_CMD $TARG >> make.tr_log 2>&1
>>>> 
>>>> On my vector computer (we have a new one!), explicit inlining only works if ***all*** ???small_f" files are availabe when the compiler is called, and just doing ???make??? does not work. Can we find a solution for this? Alternatively I have turn off explicit inlining for the tests, which I would like to avoid.
>>>> 
>>>> Martin
>>>> 
>>>> 
>>>> _______________________________________________
>>>> MITgcm-devel mailing list
>>>> MITgcm-devel at mitgcm.org
>>>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
>>> 
>>> _______________________________________________
>>> MITgcm-devel mailing list
>>> MITgcm-devel at mitgcm.org
>>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
>> 
>> 
>> _______________________________________________
>> MITgcm-devel mailing list
>> MITgcm-devel at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel