Re: [arts-users] ARTS OEM

2018-10-17 Thread Oliver Lemke
Hi Byungsuk,

> On 17 Oct 2018, at 10:54, Byungsuk Lee  wrote:
> 
> Hello Oliver,
> 
> Thank you for your reply. 
> 
> I have tried with AppleClang without OpenMP, and the installation was 
> successfully completed. Thank you. 
> 
> With that, I tried my OEM code, but the irregular t_field errors (discussed 
> previously in emails with ARTS users and Simon Pfreundschuh) still occurred. 
> 
> I have tried with Homebrew Clang or GCC compilers and without the fortran and 
> netCDF supports as well, and the errors still persisted. 
> 
> I am starting to question that the externally installed compilers or the 
> packages might not be the problem. Maybe it has something more to do with 
> some fundamental or built-in feature of Mac that is different from Ubuntu. 
> What it may actually be, I could not guess.  

Yes, looking at the "consistency" of the results, I totally agree with you.

> If anyone has tried the development version's OEM on Mac (or Macbook), with 
> the test file "ARTS/controlfiles/artscomponents/oem/TestOEM.arts", with the 
> retrieval quantity switched from O3 vmr to temperature, with the number of 
> frequencies and the number of pressure layers reduced to about 20 (f_grid, 
> p_gird, and p_ret_grid), and was successful without irregularly occurring 
> errors for t_field during OEM, please let me know.  

I'm developing on Mac myself and can take a closer look at it. But can you 
please mail me the controlfile which exhibits this behaviour? I want to be 100% 
sure I'm running the same as you and don't want to dig through the whole mail 
thread piecing together the bits of information about the exact setup. :-)

Cheers,
Oliver

___
arts_users.mi mailing list
arts_users.mi@lists.uni-hamburg.de
https://mailman.rrz.uni-hamburg.de/mailman/listinfo/arts_users.mi


Re: [arts-users] ARTS OEM

2018-10-17 Thread Byungsuk Lee
Hello Oliver,

Thank you for your reply.

I have tried with AppleClang without OpenMP, and the installation was
successfully completed. Thank you.

With that, I tried my OEM code, but the irregular t_field errors (discussed
previously in emails with ARTS users and Simon Pfreundschuh) still
occurred.

I have tried with Homebrew Clang or GCC compilers and without the fortran
and netCDF supports as well, and the errors still persisted.

I am starting to question that the externally installed compilers or the
packages might not be the problem. Maybe it has something more to do with
some fundamental or built-in feature of Mac that is different from Ubuntu.
What it may actually be, I could not guess.

If anyone has tried the development version's OEM on Mac (or Macbook), with
the test file "ARTS/controlfiles/artscomponents/oem/TestOEM.arts", with the
retrieval quantity switched from O3 vmr to temperature, with the number of
frequencies and the number of pressure layers reduced to about 20 (f_grid,
p_gird, and p_ret_grid), and was successful without irregularly occurring
errors for t_field during OEM, please let me know.

Regards,

Byungsuk Lee



On Mon, Oct 15, 2018 at 3:45 PM Oliver Lemke 
wrote:

> Hi Byungsuk,
>
> > On 8 Oct 2018, at 07:26, Byungsuk Lee  wrote:
> >
> > Hello Oliver,
> >
> > Thank you for your reply.
> >
> > 1) I don't think there is any Intel-related library in my PATH. Could
> any of them below be an Intel library? Below are some of the lines from
> CMakeCache.txt after cmake command using Apple Clang v10 and GNU gfortran
> v8.2.0:
> > [snip]
> > //Details about finding OpenMP
> > FIND_PACKAGE_MESSAGE_DETAILS_OpenMP:INTERNAL=[TRUE][TRUE][TRUE][c
> ][v3.1()]
> > //Details about finding OpenMP_C
> > FIND_PACKAGE_MESSAGE_DETAILS_OpenMP_C:INTERNAL=[-Xclang
> -fopenmp][/usr/local/lib/libomp.dylib][v3.1()]
> > //Details about finding OpenMP_CXX
> > FIND_PACKAGE_MESSAGE_DETAILS_OpenMP_CXX:INTERNAL=[-Xclang
> -fopenmp][/usr/local/lib/libomp.dylib][v3.1()]
> > //Details about finding OpenMP_Fortran
> >
> FIND_PACKAGE_MESSAGE_DETAILS_OpenMP_Fortran:INTERNAL=[-fopenmp][/usr/local/Cellar/gcc/8.2.0/lib/gcc/8/libgomp.dylib][v4.5()]
> > [snip]
>
> Doesn't look like any Intel related libraries are present. I guess
> /usr/local/lib/libomp.dylib comes from brew? You could try to do a
> compilation without the Fortran, NetCDF and OpenMP features. I don't think
> you need any of the Fortran modules for your calculation. You can disable
> OpenMP with 'cmake -DNO_OPENMP=1 ..'. Just to see if that fixes the
> compilation errors.
>
> > 2) After installing ARTS with Homebrew llvm clang/clang++:
> > export CC=/usr/local/opt/llvm/bin/clang
> > export CXX=/usr/local/opt/llvm/bin/clang++
> > export FC=/usr/local/opt/gcc/bin/gfortran
> > cmake -DENABLE_C_API=1
> -DARTS_XML_DATA_PATH=/Users/BLee/Desktop/ARTS/arts-xml-data-dev
> -DENABLE_FORTRAN=1 -DENABLE_NETCDF=1 ..
> > make -j4
> >
> > I get the following from typing "otool -L src/arts":
> > src/arts:
> >   /usr/lib/libz.1.dylib (compatibility version 1.0.0, current
> version 1.2.11)
> >   /usr/local/opt/netcdf/lib/libnetcdf.13.dylib (compatibility
> version 13.0.0, current version 13.0.0)
> >
>  /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
> (compatibility version 1.0.0, current version 4.0.0)
> >   /usr/local/opt/gcc/lib/gcc/8/libgfortran.5.dylib (compatibility
> version 6.0.0, current version 6.0.0)
> >   /usr/local/lib/gcc/8/libgcc_s.1.dylib (compatibility version
> 1.0.0, current version 1.0.0)
> >   /usr/local/opt/gcc/lib/gcc/8/libquadmath.0.dylib (compatibility
> version 1.0.0, current version 1.0.0)
> >   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 1252.50.4)
> >   /usr/local/opt/libomp/lib/libomp.dylib (compatibility version
> 5.0.0, current version 5.0.0)
> >   /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current
> version 400.9.0)
> >
> > I am guessing that the Accelerate framework is properly included?
>
> Yes, that looks correct.
>
> Cheers,
> Oliver
>
>
> > Thank you,
> >
> > Byungsuk Lee
> >
> >
> >
> > On Thu, Oct 4, 2018 at 5:49 PM Oliver Lemke 
> wrote:
> > Hi Byungsuk,
> >
> > > On 2 Oct 2018, at 11:39, Byungsuk Lee  wrote:
> > >
> > > Dear Jonas and Oliver,
> > >
> > > Thank you for your replies. I wanted to give you a sort of status
> report regarding the use of ARTS on my Mac.
> > >
> > > 1) I checked ARTS/build/CMakeCache.txt and confirmed that no conda
> package was used, other than CONDA_PROG:FILEPATH=... which I think is
> irrelevant.
> > >
> > > 2) I tried compiling with gcc/g++ instead, both from Homebrew and from
> manually installing tar.gz files from the gnu website for a few different
> versions, but the same irregular invalid t_field errors in OEM happened.
> Plus, at the cmake stage, they constantly produced a failure message for
> "Wno-return-type-c-linkage" as follows, about which I am curious why. This
> doesn't happen with