[Met_help] [rt.rap.ucar.edu #92412] History for Help
Julie Prestopnik via RT
met_help at ucar.edu
Mon Oct 14 09:42:58 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello dear,
I am writing because I need your help.
when I run the preproc.sh with command ./preproc.sh, I get these errors.
What should I change in the preproc file before running.
It's been two weeks since I tried to run met. And, I need it as soon as
possible to fill my contingency tables and continue my work of memory.
endiantest.c: In function 'endian':
endiantest.c:2:130: warning: implicit declaration of function 'putchar'
[-Wimplicit-function-declaration]
#define Order(x) fill((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x);
i++) { c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ?
'?' : (char)c); } printf("\n");
^
endiantest.c:17:2: note: in expansion of macro 'Order'
Order(j);
^~~~~
endiantest.c:2:165: warning: implicit declaration of function 'printf'
[-Wimplicit-function-declaration]
ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?' :
(char)c); } printf("\n");
^
endiantest.c:17:2: note: in expansion of macro 'Order'
Order(j);
^~~~~
endiantest.c:2:165: warning: incompatible implicit declaration of built-in
function 'printf'
ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?' :
(char)c); } printf("\n");
^
endiantest.c:17:2: note: in expansion of macro 'Order'
Order(j);
^~~~~
endiantest.c:2:165: note: include '<stdio.h>' or provide a declaration of
'printf'
ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?' :
(char)c); } printf("\n");
^
endiantest.c:17:2: note: in expansion of macro 'Order'
Order(j);
^~~~~
endiantest.c: At top level:
endiantest.c:31:1: warning: return type defaults to 'int' [-Wimplicit-int]
main()
^~~~
irev.F:8:59: warning: missing terminating " character
C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS "LITTLE-
^
irev.F:9:11: warning: missing terminating " character
C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING THE BYTES
^
irev.F:44:54: warning: missing terminating " character
C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-ENDIAN THEN
Warm regards,
Dorès.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Help
From: Julie Prestopnik
Time: Wed Oct 02 13:05:52 2019
Hi Dorès.
It sounds like you're having trouble installing the BUFRLIB library
that
MET depends on. First, I'd like to ensure that you are compiling
BUFRLIBv10-2-3 and not a later version of BUFRLIB. MET will upgrade
the
version of BUFRLIB that it is using with our next release (METv9.0).
I
have attached BUFRLIB_v10-2-3.tar.gz along with a preproc.sh_v10.2.3
script that you can use.
You can simply run:
cp preproc.sh_v10.2.3 preproc.sh
You can follow the directions for compiling BUFRLIB in our online
tutorial
under the "Compiling BUFRLIB" section of our Required Libraries page
to be
sure that you are using the necessary compiler flags:
https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
Pleas let us know if you have any questions.
Thanks,
Julie
On Wed, Oct 2, 2019 at 8:02 AM Das Dores Ngamini via RT
<met_help at ucar.edu>
wrote:
>
> Wed Oct 02 08:02:43 2019: Request 92412 was acted upon.
> Transaction: Ticket created by ngaminidas at gmail.com
> Queue: met_help
> Subject: Help
> Owner: Nobody
> Requestors: ngaminidas at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
>
>
> Hello dear,
>
> I am writing because I need your help.
> when I run the preproc.sh with command ./preproc.sh, I get these
errors.
> What should I change in the preproc file before running.
> It's been two weeks since I tried to run met. And, I need it as soon
as
> possible to fill my contingency tables and continue my work of
memory.
>
> endiantest.c: In function 'endian':
> endiantest.c:2:130: warning: implicit declaration of function
'putchar'
> [-Wimplicit-function-declaration]
> #define Order(x) fill((char *)&x, sizeof(x)); for (i=1;
i<=sizeof(x);
> i++) { c=((x>>(byte_size*(sizeof(x)-i)))&mask);
putchar(c==0 ?
> '?' : (char)c); } printf("\n");
>
> ^
> endiantest.c:17:2: note: in expansion of macro 'Order'
> Order(j);
> ^~~~~
> endiantest.c:2:165: warning: implicit declaration of function
'printf'
> [-Wimplicit-function-declaration]
> ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?' :
> (char)c); } printf("\n");
>
>
^
> endiantest.c:17:2: note: in expansion of macro 'Order'
> Order(j);
> ^~~~~
> endiantest.c:2:165: warning: incompatible implicit declaration of
built-in
> function 'printf'
> ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?' :
> (char)c); } printf("\n");
>
>
^
> endiantest.c:17:2: note: in expansion of macro 'Order'
> Order(j);
> ^~~~~
> endiantest.c:2:165: note: include '<stdio.h>' or provide a
declaration of
> 'printf'
> ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?' :
> (char)c); } printf("\n");
>
>
^
> endiantest.c:17:2: note: in expansion of macro 'Order'
> Order(j);
> ^~~~~
> endiantest.c: At top level:
> endiantest.c:31:1: warning: return type defaults to 'int' [-
Wimplicit-int]
> main()
> ^~~~
> irev.F:8:59: warning: missing terminating " character
> C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS "LITTLE-
> ^
> irev.F:9:11: warning: missing terminating " character
> C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING THE
BYTES
> ^
> irev.F:44:54: warning: missing terminating " character
> C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-ENDIAN
THEN
>
> Warm regards,
> Dorès.
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Thu Oct 03 06:09:04 2019
Hello Julie,
Thank you for you help.
I use BUFRLIB_v10.2.3.
I was able to compile preproc.sh. I had some warning at the end.
irev.F:8:59: warning: missing terminating " character
C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS "LITTLE-
^
irev.F:9:11: warning: missing terminating " character
C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING THE
BYTES
^
irev.F:44:54: warning: missing terminating " character
C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-ENDIAN THEN
But, I continued. In compiling gcc with* gcc -c -DUNDERSCORE *.c* , I
also
had warnings.
In file included from stseq.c:56:0:
stseq.c: In function 'stseq_':
bufrlib.h:51:19: warning: implicit declaration of function 'stntbi_';
did
you mean 'stntbi'? [-Wimplicit-function-declaration]
#define stntbi stntbi_
^
stseq.c:88:5: note: in expansion of macro 'stntbi'
stntbi( &nd, lun, adn, nemo, cseq, sizeof( adn ), 8, 55 );
^~~~~~
bufrlib.h:35:19: warning: implicit declaration of function 'icvidx_';
did
you mean 'icvidx'? [-Wimplicit-function-declaration]
#define icvidx icvidx_
^
stseq.c:104:21: note: in expansion of macro 'icvidx'
&mstabs.idefxy[icvidx(&ipt,&i0,&imxcd)],
And, I still compiler gfortran with *gfortran -c -DUNDERSCORE
-fno-second-underscore *.f *.F* where I had the errors below. Since
then, I
have been trying to solve them.
wrdlen.f:411:6:
ERRSTR = '=============== '
1
Error: Unclassifiable statement at (1)
wrdlen.f:420:6:
ERRSTR = ' BYTE ORDER IS '
1
Error: Unclassifiable statement at (1)
wrdlen.f:423:6:
ERRSTR = ' '
1
Error: Unclassifiable statement at (1)
wrdlen.f:426:6:
ERRSTR = '====================== VERSION: '
1
Error: Unclassifiable statement at (1)
wrdlen.f:434:66:
900 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - MACHINE WORD LENGTH IS '
1
Error: Syntax error in WRITE statement at (1)
wrdlen.f:438:70:
901 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - MACHINE WORD LENGTH
(",I4,"'
1
Error: Syntax error in WRITE statement at (1)
wrdlen.f:442:70:
902 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - BYTE ORDER CHECKING
MISTAKE'
1
Error: Syntax error in WRITE statement at (1)
wrdlen.f:446:68:
903 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - CAN''T DETERMINE MACHINE '
1
Error: Syntax error in WRITE statement at (1)
wrdlen.f:91:72:
10 IF(I.GE.65) GOTO 900
1
Error: Label 900 referenced at (1) is never defined
wrdlen.f:92:72:
IF(MOD(I,8).NE.0) GOTO 901
1
Error: Label 901 referenced at (1) is never defined
wrdlen.f:109:72:
20 IF(J.GT.NBYTW) GOTO 902
1
Error: Label 902 referenced at (1) is never defined
wrdlen.f:122:72:
GOTO 903
1
Error: Label 903 referenced at (1) is never defined
Best Regards
Dorès
Le mer. 2 oct. 2019 à 20:05, Julie Prestopnik via RT
<met_help at ucar.edu> a
écrit :
> Hi Dorès.
>
> It sounds like you're having trouble installing the BUFRLIB library
that
> MET depends on. First, I'd like to ensure that you are compiling
> BUFRLIBv10-2-3 and not a later version of BUFRLIB. MET will upgrade
the
> version of BUFRLIB that it is using with our next release (METv9.0).
I
> have attached BUFRLIB_v10-2-3.tar.gz along with a
preproc.sh_v10.2.3
> script that you can use.
>
> You can simply run:
> cp preproc.sh_v10.2.3 preproc.sh
>
> You can follow the directions for compiling BUFRLIB in our online
tutorial
> under the "Compiling BUFRLIB" section of our Required Libraries page
to be
> sure that you are using the necessary compiler flags:
>
> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
>
> Pleas let us know if you have any questions.
>
> Thanks,
> Julie
>
>
>
>
> On Wed, Oct 2, 2019 at 8:02 AM Das Dores Ngamini via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > Wed Oct 02 08:02:43 2019: Request 92412 was acted upon.
> > Transaction: Ticket created by ngaminidas at gmail.com
> > Queue: met_help
> > Subject: Help
> > Owner: Nobody
> > Requestors: ngaminidas at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
> >
> >
> > Hello dear,
> >
> > I am writing because I need your help.
> > when I run the preproc.sh with command ./preproc.sh, I get these
errors.
> > What should I change in the preproc file before running.
> > It's been two weeks since I tried to run met. And, I need it as
soon as
> > possible to fill my contingency tables and continue my work of
memory.
> >
> > endiantest.c: In function 'endian':
> > endiantest.c:2:130: warning: implicit declaration of function
'putchar'
> > [-Wimplicit-function-declaration]
> > #define Order(x) fill((char *)&x, sizeof(x)); for (i=1;
i<=sizeof(x);
> > i++) { c=((x>>(byte_size*(sizeof(x)-i)))&mask);
putchar(c==0 ?
> > '?' : (char)c); } printf("\n");
> >
> > ^
> > endiantest.c:17:2: note: in expansion of macro 'Order'
> > Order(j);
> > ^~~~~
> > endiantest.c:2:165: warning: implicit declaration of function
'printf'
> > [-Wimplicit-function-declaration]
> > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?'
:
> > (char)c); } printf("\n");
> >
> >
^
> > endiantest.c:17:2: note: in expansion of macro 'Order'
> > Order(j);
> > ^~~~~
> > endiantest.c:2:165: warning: incompatible implicit declaration of
> built-in
> > function 'printf'
> > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?'
:
> > (char)c); } printf("\n");
> >
> >
^
> > endiantest.c:17:2: note: in expansion of macro 'Order'
> > Order(j);
> > ^~~~~
> > endiantest.c:2:165: note: include '<stdio.h>' or provide a
declaration of
> > 'printf'
> > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ? '?'
:
> > (char)c); } printf("\n");
> >
> >
^
> > endiantest.c:17:2: note: in expansion of macro 'Order'
> > Order(j);
> > ^~~~~
> > endiantest.c: At top level:
> > endiantest.c:31:1: warning: return type defaults to 'int'
> [-Wimplicit-int]
> > main()
> > ^~~~
> > irev.F:8:59: warning: missing terminating " character
> > C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS
"LITTLE-
> > ^
> > irev.F:9:11: warning: missing terminating " character
> > C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING THE
BYTES
> > ^
> > irev.F:44:54: warning: missing terminating " character
> > C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-ENDIAN
THEN
> >
> > Warm regards,
> > Dorès.
> >
> >
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: Help
From: Julie Prestopnik
Time: Thu Oct 03 13:19:05 2019
Hi Dorès.
Thank you for this information. I am sorry to see that you are still
having difficulty.
Could you please start in a new shell, try the following directions
and see
if you are able to get a successful build? I just ran through these
steps
and was able to get a successful build. I hope that you will too.
Make a new directory to contain the BUFRLIB code (e.g. mkdir
/home/user/BURFLIB_v10.2.3)
Copy the BUFRLIB tarball to the new directory (e.g. cp BUFRLIB_v10-2-
3.tar
/home/user/BURFLIB_v10.2.3/)
Copy preproc.sh_v10.2.3 into the new directory (e.g. cp
preproc.sh_v10.2.3
/home/user/BURFLIB_v10.2.3/)
Unpack the tarball (e.g. cd /home/user/BURFLIB_v10.2.3; tar -xvf
BUFRLIB_v10-2-3.tar)
Set the FC and CC:
For csh:
setenv FC /usr/bin/gfortran (set to the location of your gfortran
executable, if you're unsure of its location, run "which gfortran")
setenv CC /usr/bin/gcc (set to the location of your gcc
executable, if
you're unsure of its location, run "which gcc")
For bash:
export FC=/usr/bin/gfortran (set to the location of your gfortran
executable, if you're unsure of its location, run "which gfortran")
export CC=/usr/bin/gcc (set to the location of your gcc
executable, if
you're unsure of its location, run "which gcc")
Then run:
./preproc.sh_v10.2.3
gcc -c -DUNDERSCORE *.c
gfortran -c -DUNDERSCORE -fno-second-underscore *.f *.F
ar crv libbufr.a *.o
After that, hopefully, you will have successfully built BUFRLIB.
Please let me know how it goes. Thank you!
Julie
On Thu, Oct 3, 2019 at 6:09 AM Das Dores Ngamini via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
>
> Hello Julie,
> Thank you for you help.
> I use BUFRLIB_v10.2.3.
> I was able to compile preproc.sh. I had some warning at the end.
>
> irev.F:8:59: warning: missing terminating " character
> C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS "LITTLE-
> ^
> irev.F:9:11: warning: missing terminating " character
> C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING THE
BYTES
> ^
> irev.F:44:54: warning: missing terminating " character
> C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-ENDIAN
THEN
>
> But, I continued. In compiling gcc with* gcc -c -DUNDERSCORE *.c* ,
I also
> had warnings.
>
> In file included from stseq.c:56:0:
> stseq.c: In function 'stseq_':
> bufrlib.h:51:19: warning: implicit declaration of function
'stntbi_'; did
> you mean 'stntbi'? [-Wimplicit-function-declaration]
> #define stntbi stntbi_
> ^
> stseq.c:88:5: note: in expansion of macro 'stntbi'
> stntbi( &nd, lun, adn, nemo, cseq, sizeof( adn ), 8, 55 );
> ^~~~~~
> bufrlib.h:35:19: warning: implicit declaration of function
'icvidx_'; did
> you mean 'icvidx'? [-Wimplicit-function-declaration]
> #define icvidx icvidx_
> ^
> stseq.c:104:21: note: in expansion of macro 'icvidx'
> &mstabs.idefxy[icvidx(&ipt,&i0,&imxcd)],
>
> And, I still compiler gfortran with *gfortran -c -DUNDERSCORE
> -fno-second-underscore *.f *.F* where I had the errors below. Since
then, I
> have been trying to solve them.
>
> wrdlen.f:411:6:
>
> ERRSTR = '=============== '
> 1
> Error: Unclassifiable statement at (1)
> wrdlen.f:420:6:
>
> ERRSTR = ' BYTE ORDER IS '
> 1
> Error: Unclassifiable statement at (1)
> wrdlen.f:423:6:
>
> ERRSTR = ' '
> 1
> Error: Unclassifiable statement at (1)
> wrdlen.f:426:6:
>
> ERRSTR = '====================== VERSION: '
> 1
> Error: Unclassifiable statement at (1)
> wrdlen.f:434:66:
>
> 900 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - MACHINE WORD LENGTH IS '
> 1
> Error: Syntax error in WRITE statement at (1)
> wrdlen.f:438:70:
>
> 901 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - MACHINE WORD LENGTH
(",I4,"'
>
1
> Error: Syntax error in WRITE statement at (1)
> wrdlen.f:442:70:
>
> 902 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - BYTE ORDER CHECKING
MISTAKE'
>
1
> Error: Syntax error in WRITE statement at (1)
> wrdlen.f:446:68:
>
> 903 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - CAN''T DETERMINE MACHINE
'
>
1
> Error: Syntax error in WRITE statement at (1)
> wrdlen.f:91:72:
>
> 10 IF(I.GE.65) GOTO 900
>
1
> Error: Label 900 referenced at (1) is never defined
> wrdlen.f:92:72:
>
> IF(MOD(I,8).NE.0) GOTO 901
>
1
> Error: Label 901 referenced at (1) is never defined
> wrdlen.f:109:72:
>
> 20 IF(J.GT.NBYTW) GOTO 902
>
1
> Error: Label 902 referenced at (1) is never defined
> wrdlen.f:122:72:
>
> GOTO 903
>
1
> Error: Label 903 referenced at (1) is never defined
>
> Best Regards
> Dorès
>
> Le mer. 2 oct. 2019 à 20:05, Julie Prestopnik via RT
<met_help at ucar.edu> a
> écrit :
>
> > Hi Dorès.
> >
> > It sounds like you're having trouble installing the BUFRLIB
library that
> > MET depends on. First, I'd like to ensure that you are compiling
> > BUFRLIBv10-2-3 and not a later version of BUFRLIB. MET will
upgrade the
> > version of BUFRLIB that it is using with our next release
(METv9.0). I
> > have attached BUFRLIB_v10-2-3.tar.gz along with a
preproc.sh_v10.2.3
> > script that you can use.
> >
> > You can simply run:
> > cp preproc.sh_v10.2.3 preproc.sh
> >
> > You can follow the directions for compiling BUFRLIB in our online
> tutorial
> > under the "Compiling BUFRLIB" section of our Required Libraries
page to
> be
> > sure that you are using the necessary compiler flags:
> >
> >
> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
> >
> > Pleas let us know if you have any questions.
> >
> > Thanks,
> > Julie
> >
> >
> >
> >
> > On Wed, Oct 2, 2019 at 8:02 AM Das Dores Ngamini via RT <
> met_help at ucar.edu
> > >
> > wrote:
> >
> > >
> > > Wed Oct 02 08:02:43 2019: Request 92412 was acted upon.
> > > Transaction: Ticket created by ngaminidas at gmail.com
> > > Queue: met_help
> > > Subject: Help
> > > Owner: Nobody
> > > Requestors: ngaminidas at gmail.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412
> >
> > >
> > >
> > > Hello dear,
> > >
> > > I am writing because I need your help.
> > > when I run the preproc.sh with command ./preproc.sh, I get
these
> errors.
> > > What should I change in the preproc file before running.
> > > It's been two weeks since I tried to run met. And, I need it as
soon as
> > > possible to fill my contingency tables and continue my work of
memory.
> > >
> > > endiantest.c: In function 'endian':
> > > endiantest.c:2:130: warning: implicit declaration of function
'putchar'
> > > [-Wimplicit-function-declaration]
> > > #define Order(x) fill((char *)&x, sizeof(x)); for (i=1;
i<=sizeof(x);
> > > i++) { c=((x>>(byte_size*(sizeof(x)-i)))&mask);
putchar(c==0
> ?
> > > '?' : (char)c); } printf("\n");
> > >
> > > ^
> > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > Order(j);
> > > ^~~~~
> > > endiantest.c:2:165: warning: implicit declaration of function
'printf'
> > > [-Wimplicit-function-declaration]
> > > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ?
'?' :
> > > (char)c); } printf("\n");
> > >
> > >
^
> > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > Order(j);
> > > ^~~~~
> > > endiantest.c:2:165: warning: incompatible implicit declaration
of
> > built-in
> > > function 'printf'
> > > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ?
'?' :
> > > (char)c); } printf("\n");
> > >
> > >
^
> > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > Order(j);
> > > ^~~~~
> > > endiantest.c:2:165: note: include '<stdio.h>' or provide a
declaration
> of
> > > 'printf'
> > > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ?
'?' :
> > > (char)c); } printf("\n");
> > >
> > >
^
> > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > Order(j);
> > > ^~~~~
> > > endiantest.c: At top level:
> > > endiantest.c:31:1: warning: return type defaults to 'int'
> > [-Wimplicit-int]
> > > main()
> > > ^~~~
> > > irev.F:8:59: warning: missing terminating " character
> > > C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS
"LITTLE-
> > > ^
> > > irev.F:9:11: warning: missing terminating " character
> > > C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING
THE BYTES
> > > ^
> > > irev.F:44:54: warning: missing terminating " character
> > > C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-
ENDIAN THEN
> > >
> > > Warm regards,
> > > Dorès.
> > >
> > >
> >
> > --
> > Julie Prestopnik
> > Software Engineer
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> > My working day may not be your working day. Please do not feel
obliged
> to
> > reply to this email outside of your normal working hours.
> >
> >
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Fri Oct 04 07:36:03 2019
Hello Julie,
Thank you for your help.
I was able to compiling BUFRLIB. Now when I try to compile MET with
commands
*make install >& make_install.log &*
*tail -f make_install.log*
the command *tail -f make_install.log *gives these errors.
make[3]: *** [libvx_nc_util_a-nc_var_info.o] Error 1
make[3]: Leaving directory
'/home/dores/Tutorial_Master/TP_Prevision/MET/met-
8.0/src/libcode/vx_nc_util'
Makefile:369: recipe for target 'install-recursive' failedthe
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
'/home/dores/Tutorial_Master/TP_Prevision/MET/met-8.0/src/libcode'
Makefile:357: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
'/home/dores/Tutorial_Master/TP_Prevision/MET/met-8.0/src'
Makefile:413: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1
Attached make_install.log file.
Best Regards
Dores
Le jeu. 3 oct. 2019 à 20:19, Julie Prestopnik via RT
<met_help at ucar.edu> a
écrit :
> Hi Dorès.
>
> Thank you for this information. I am sorry to see that you are
still
> having difficulty.
>
> Could you please start in a new shell, try the following directions
and see
> if you are able to get a successful build? I just ran through these
steps
> and was able to get a successful build. I hope that you will too.
>
> Make a new directory to contain the BUFRLIB code (e.g. mkdir
> /home/user/BURFLIB_v10.2.3)
> Copy the BUFRLIB tarball to the new directory (e.g. cp BUFRLIB_v10-
2-3.tar
> /home/user/BURFLIB_v10.2.3/)
> Copy preproc.sh_v10.2.3 into the new directory (e.g. cp
preproc.sh_v10.2.3
> /home/user/BURFLIB_v10.2.3/)
> Unpack the tarball (e.g. cd /home/user/BURFLIB_v10.2.3; tar -xvf
> BUFRLIB_v10-2-3.tar)
>
> Set the FC and CC:
> For csh:
> setenv FC /usr/bin/gfortran (set to the location of your
gfortran
> executable, if you're unsure of its location, run "which gfortran")
> setenv CC /usr/bin/gcc (set to the location of your gcc
executable, if
> you're unsure of its location, run "which gcc")
> For bash:
> export FC=/usr/bin/gfortran (set to the location of your
gfortran
> executable, if you're unsure of its location, run "which gfortran")
> export CC=/usr/bin/gcc (set to the location of your gcc
executable, if
> you're unsure of its location, run "which gcc")
>
> Then run:
> ./preproc.sh_v10.2.3
> gcc -c -DUNDERSCORE *.c
> gfortran -c -DUNDERSCORE -fno-second-underscore *.f *.F
> ar crv libbufr.a *.o
>
> After that, hopefully, you will have successfully built BUFRLIB.
>
> Please let me know how it goes. Thank you!
>
> Julie
>
> On Thu, Oct 3, 2019 at 6:09 AM Das Dores Ngamini via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
> >
> > Hello Julie,
> > Thank you for you help.
> > I use BUFRLIB_v10.2.3.
> > I was able to compile preproc.sh. I had some warning at the end.
> >
> > irev.F:8:59: warning: missing terminating " character
> > C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS
"LITTLE-
> > ^
> > irev.F:9:11: warning: missing terminating " character
> > C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING THE
BYTES
> > ^
> > irev.F:44:54: warning: missing terminating " character
> > C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-ENDIAN
THEN
> >
> > But, I continued. In compiling gcc with* gcc -c -DUNDERSCORE *.c*
, I
> also
> > had warnings.
> >
> > In file included from stseq.c:56:0:
> > stseq.c: In function 'stseq_':
> > bufrlib.h:51:19: warning: implicit declaration of function
'stntbi_'; did
> > you mean 'stntbi'? [-Wimplicit-function-declaration]
> > #define stntbi stntbi_
> > ^
> > stseq.c:88:5: note: in expansion of macro 'stntbi'
> > stntbi( &nd, lun, adn, nemo, cseq, sizeof( adn ), 8, 55 );
> > ^~~~~~
> > bufrlib.h:35:19: warning: implicit declaration of function
'icvidx_'; did
> > you mean 'icvidx'? [-Wimplicit-function-declaration]
> > #define icvidx icvidx_
> > ^
> > stseq.c:104:21: note: in expansion of macro 'icvidx'
> > &mstabs.idefxy[icvidx(&ipt,&i0,&imxcd)],
> >
> > And, I still compiler gfortran with *gfortran -c -DUNDERSCORE
> > -fno-second-underscore *.f *.F* where I had the errors below.
Since
> then, I
> > have been trying to solve them.
> >
> > wrdlen.f:411:6:
> >
> > ERRSTR = '=============== '
> > 1
> > Error: Unclassifiable statement at (1)
> > wrdlen.f:420:6:
> >
> > ERRSTR = ' BYTE ORDER IS '
> > 1
> > Error: Unclassifiable statement at (1)
> > wrdlen.f:423:6:
> >
> > ERRSTR = ' '
> > 1
> > Error: Unclassifiable statement at (1)
> > wrdlen.f:426:6:
> >
> > ERRSTR = '====================== VERSION: '
> > 1
> > Error: Unclassifiable statement at (1)
> > wrdlen.f:434:66:
> >
> > 900 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - MACHINE WORD LENGTH IS
'
> >
1
> > Error: Syntax error in WRITE statement at (1)
> > wrdlen.f:438:70:
> >
> > 901 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - MACHINE WORD LENGTH
(",I4,"'
> >
1
> > Error: Syntax error in WRITE statement at (1)
> > wrdlen.f:442:70:
> >
> > 902 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - BYTE ORDER CHECKING
MISTAKE'
> >
1
> > Error: Syntax error in WRITE statement at (1)
> > wrdlen.f:446:68:
> >
> > 903 WRITE(BORT_STR,'("BUFRLIB: WRDLEN - CAN''T DETERMINE
MACHINE '
> >
1
> > Error: Syntax error in WRITE statement at (1)
> > wrdlen.f:91:72:
> >
> > 10 IF(I.GE.65) GOTO 900
> >
1
> > Error: Label 900 referenced at (1) is never defined
> > wrdlen.f:92:72:
> >
> > IF(MOD(I,8).NE.0) GOTO 901
> >
1
> > Error: Label 901 referenced at (1) is never defined
> > wrdlen.f:109:72:
> >
> > 20 IF(J.GT.NBYTW) GOTO 902
> >
1
> > Error: Label 902 referenced at (1) is never defined
> > wrdlen.f:122:72:
> >
> > GOTO 903
> >
1
> > Error: Label 903 referenced at (1) is never defined
> >
> > Best Regards
> > Dorès
> >
> > Le mer. 2 oct. 2019 à 20:05, Julie Prestopnik via RT
<met_help at ucar.edu>
> a
> > écrit :
> >
> > > Hi Dorès.
> > >
> > > It sounds like you're having trouble installing the BUFRLIB
library
> that
> > > MET depends on. First, I'd like to ensure that you are
compiling
> > > BUFRLIBv10-2-3 and not a later version of BUFRLIB. MET will
upgrade
> the
> > > version of BUFRLIB that it is using with our next release
(METv9.0). I
> > > have attached BUFRLIB_v10-2-3.tar.gz along with a
preproc.sh_v10.2.3
> > > script that you can use.
> > >
> > > You can simply run:
> > > cp preproc.sh_v10.2.3 preproc.sh
> > >
> > > You can follow the directions for compiling BUFRLIB in our
online
> > tutorial
> > > under the "Compiling BUFRLIB" section of our Required Libraries
page to
> > be
> > > sure that you are using the necessary compiler flags:
> > >
> > >
> >
> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
> > >
> > > Pleas let us know if you have any questions.
> > >
> > > Thanks,
> > > Julie
> > >
> > >
> > >
> > >
> > > On Wed, Oct 2, 2019 at 8:02 AM Das Dores Ngamini via RT <
> > met_help at ucar.edu
> > > >
> > > wrote:
> > >
> > > >
> > > > Wed Oct 02 08:02:43 2019: Request 92412 was acted upon.
> > > > Transaction: Ticket created by ngaminidas at gmail.com
> > > > Queue: met_help
> > > > Subject: Help
> > > > Owner: Nobody
> > > > Requestors: ngaminidas at gmail.com
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412
> > >
> > > >
> > > >
> > > > Hello dear,
> > > >
> > > > I am writing because I need your help.
> > > > when I run the preproc.sh with command ./preproc.sh, I get
these
> > errors.
> > > > What should I change in the preproc file before running.
> > > > It's been two weeks since I tried to run met. And, I need it
as soon
> as
> > > > possible to fill my contingency tables and continue my work of
> memory.
> > > >
> > > > endiantest.c: In function 'endian':
> > > > endiantest.c:2:130: warning: implicit declaration of function
> 'putchar'
> > > > [-Wimplicit-function-declaration]
> > > > #define Order(x) fill((char *)&x, sizeof(x)); for (i=1;
> i<=sizeof(x);
> > > > i++) { c=((x>>(byte_size*(sizeof(x)-i)))&mask);
> putchar(c==0
> > ?
> > > > '?' : (char)c); } printf("\n");
> > > >
> > > > ^
> > > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > > Order(j);
> > > > ^~~~~
> > > > endiantest.c:2:165: warning: implicit declaration of function
> 'printf'
> > > > [-Wimplicit-function-declaration]
> > > > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > > > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ?
'?' :
> > > > (char)c); } printf("\n");
> > > >
> > > >
> ^
> > > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > > Order(j);
> > > > ^~~~~
> > > > endiantest.c:2:165: warning: incompatible implicit declaration
of
> > > built-in
> > > > function 'printf'
> > > > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > > > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ?
'?' :
> > > > (char)c); } printf("\n");
> > > >
> > > >
> ^
> > > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > > Order(j);
> > > > ^~~~~
> > > > endiantest.c:2:165: note: include '<stdio.h>' or provide a
> declaration
> > of
> > > > 'printf'
> > > > ll((char *)&x, sizeof(x)); for (i=1; i<=sizeof(x); i++) {
> > > > c=((x>>(byte_size*(sizeof(x)-i)))&mask); putchar(c==0 ?
'?' :
> > > > (char)c); } printf("\n");
> > > >
> > > >
> ^
> > > > endiantest.c:17:2: note: in expansion of macro 'Order'
> > > > Order(j);
> > > > ^~~~~
> > > > endiantest.c: At top level:
> > > > endiantest.c:31:1: warning: return type defaults to 'int'
> > > [-Wimplicit-int]
> > > > main()
> > > > ^~~~
> > > > irev.F:8:59: warning: missing terminating " character
> > > > C ABSTRACT: THIS FUNCTION WILL, WHEN THE LOCAL MACHINE IS
"LITTLE-
> > > > ^
> > > > irev.F:9:11: warning: missing terminating " character
> > > > C ENDIAN" (I.E., USES A RIGHT TO LEFT SCHEME FOR NUMBERING
THE
> BYTES
> > > > ^
> > > > irev.F:44:54: warning: missing terminating " character
> > > > C "BIG-ENDIAN" OR "LITTLE-ENDIAN", IF "BIG-
ENDIAN
> THEN
> > > >
> > > > Warm regards,
> > > > Dorès.
> > > >
> > > >
> > >
> > > --
> > > Julie Prestopnik
> > > Software Engineer
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > > My working day may not be your working day. Please do not feel
obliged
> > to
> > > reply to this email outside of your normal working hours.
> > >
> > >
> >
> >
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: Help
From: Julie Prestopnik
Time: Fri Oct 04 09:49:08 2019
I am glad to hear that you were able to get BUFRLIB installed.
Thank you for passing along the make_install.log file. I see the
following
problem:
> In file included from nc_var_info.cc:24:0:
> nc_utils.h:22:10: fatal error: netcdf: No such file or directory
> #include <netcdf>
>
The file, netcdf, is part of the NetCDF C++ library, which is required
in
addition to the NetCDF-C library. MET expects both of these libraries
to
be installed in the same location, as there is only one MET_NETCDF
variable
to set in the configuration of MET (see this page for more information
on
setting the environment variables necessary for MET:
https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/configure-met).
For more information, on compiling NetCDF for use with MET, please
take a
look at the "Compiling NetCDF" section of this webpage:
https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
Please also note that HDF5 is required for use with NetCDF4. There is
also
a section on that page for Compiling HDF5 in case you need that as
well.
Please let us know if you have any questions.
Thanks,
Julie
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Mon Oct 07 03:04:39 2019
Hello Julie
Throughout the weekend, I tried to compile met. I used the same netcdf
as
during the wrf compilation. I always get the same mistakes.
I also compiled netcdf again and, I still get the errors.
Attached are these files.
Le ven. 4 oct. 2019 à 16:49, Julie Prestopnik via RT
<met_help at ucar.edu> a
écrit :
> I am glad to hear that you were able to get BUFRLIB installed.
>
> Thank you for passing along the make_install.log file. I see the
following
> problem:
>
> > In file included from nc_var_info.cc:24:0:
> > nc_utils.h:22:10: fatal error: netcdf: No such file or directory
> > #include <netcdf>
> >
>
> The file, netcdf, is part of the NetCDF C++ library, which is
required in
> addition to the NetCDF-C library. MET expects both of these
libraries to
> be installed in the same location, as there is only one MET_NETCDF
variable
> to set in the configuration of MET (see this page for more
information on
> setting the environment variables necessary for MET:
>
> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/configure-met
> ).
>
>
> For more information, on compiling NetCDF for use with MET, please
take a
> look at the "Compiling NetCDF" section of this webpage:
>
> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
>
> Please also note that HDF5 is required for use with NetCDF4. There
is also
> a section on that page for Compiling HDF5 in case you need that as
well.
>
> Please let us know if you have any questions.
>
> Thanks,
> Julie
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Mon Oct 07 03:10:51 2019
Please, can you offer me another way to fill out my contingency table
for
wrf forecasts? The filing deadline of our memories is close and my MET
still does not give.
Best Regards.
Dorès
Le lun. 7 oct. 2019 à 10:03, Das Dores Ngamini <ngaminidas at gmail.com>
a
écrit :
> Hello Julie
> Throughout the weekend, I tried to compile met. I used the same
netcdf as
> during the wrf compilation. I always get the same mistakes.
> I also compiled netcdf again and, I still get the errors.
> Attached are these files.
>
> Le ven. 4 oct. 2019 à 16:49, Julie Prestopnik via RT
<met_help at ucar.edu>
> a écrit :
>
>> I am glad to hear that you were able to get BUFRLIB installed.
>>
>> Thank you for passing along the make_install.log file. I see the
>> following
>> problem:
>>
>> > In file included from nc_var_info.cc:24:0:
>> > nc_utils.h:22:10: fatal error: netcdf: No such file or directory
>> > #include <netcdf>
>> >
>>
>> The file, netcdf, is part of the NetCDF C++ library, which is
required in
>> addition to the NetCDF-C library. MET expects both of these
libraries to
>> be installed in the same location, as there is only one MET_NETCDF
>> variable
>> to set in the configuration of MET (see this page for more
information on
>> setting the environment variables necessary for MET:
>>
>> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/configure-met
>> ).
>>
>>
>> For more information, on compiling NetCDF for use with MET, please
take a
>> look at the "Compiling NetCDF" section of this webpage:
>>
>> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
>>
>> Please also note that HDF5 is required for use with NetCDF4. There
is
>> also
>> a section on that page for Compiling HDF5 in case you need that as
well.
>>
>> Please let us know if you have any questions.
>>
>> Thanks,
>> Julie
>>
>> --
>> Julie Prestopnik
>> Software Engineer
>> National Center for Atmospheric Research
>> Research Applications Laboratory
>> Phone: 303.497.8399
>> Email: jpresto at ucar.edu
>>
>> My working day may not be your working day. Please do not feel
obliged to
>> reply to this email outside of your normal working hours.
>>
>>
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Mon Oct 07 03:20:43 2019
In my .bashrc, I export as:
export MET_NETCDFLIB=/usr/local/netcdf/lib
export MET_NETCDFLIB
export MET_NETCDFINC=/usr/local/netcdf/include
export MET_NETCDFINC
My apologies for the multiple mails. I'm confused. This is the third
week
that I'm trying to compile MET.
Cordially
Dorès
Le lun. 7 oct. 2019 à 10:10, Das Dores Ngamini <ngaminidas at gmail.com>
a
écrit :
> Please, can you offer me another way to fill out my contingency
table for
> wrf forecasts? The filing deadline of our memories is close and my
MET
> still does not give.
> Best Regards.
> Dorès
>
> Le lun. 7 oct. 2019 à 10:03, Das Dores Ngamini
<ngaminidas at gmail.com> a
> écrit :
>
>> Hello Julie
>> Throughout the weekend, I tried to compile met. I used the same
netcdf
>> as during the wrf compilation. I always get the same mistakes.
>> I also compiled netcdf again and, I still get the errors.
>> Attached are these files.
>>
>> Le ven. 4 oct. 2019 à 16:49, Julie Prestopnik via RT
<met_help at ucar.edu>
>> a écrit :
>>
>>> I am glad to hear that you were able to get BUFRLIB installed.
>>>
>>> Thank you for passing along the make_install.log file. I see the
>>> following
>>> problem:
>>>
>>> > In file included from nc_var_info.cc:24:0:
>>> > nc_utils.h:22:10: fatal error: netcdf: No such file or directory
>>> > #include <netcdf>
>>> >
>>>
>>> The file, netcdf, is part of the NetCDF C++ library, which is
required in
>>> addition to the NetCDF-C library. MET expects both of these
libraries to
>>> be installed in the same location, as there is only one MET_NETCDF
>>> variable
>>> to set in the configuration of MET (see this page for more
information on
>>> setting the environment variables necessary for MET:
>>>
>>> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/configure-met
>>> ).
>>>
>>>
>>> For more information, on compiling NetCDF for use with MET, please
take a
>>> look at the "Compiling NetCDF" section of this webpage:
>>>
>>> https://dtcenter.org/met-online-tutorial-metv8-0/tutorial-
setup/compilation/required-libraries
>>>
>>> Please also note that HDF5 is required for use with NetCDF4.
There is
>>> also
>>> a section on that page for Compiling HDF5 in case you need that as
well.
>>>
>>> Please let us know if you have any questions.
>>>
>>> Thanks,
>>> Julie
>>>
>>> --
>>> Julie Prestopnik
>>> Software Engineer
>>> National Center for Atmospheric Research
>>> Research Applications Laboratory
>>> Phone: 303.497.8399
>>> Email: jpresto at ucar.edu
>>>
>>> My working day may not be your working day. Please do not feel
obliged
>>> to
>>> reply to this email outside of your normal working hours.
>>>
>>>
------------------------------------------------
Subject: Help
From: Julie Prestopnik
Time: Mon Oct 07 12:59:00 2019
Hi Dorès.
I'm so sorry to see that you are still having difficulty getting MET
installed. We have a few options:
1. The easiest way to make MET available would be using a Docker
container. If your sys admin is willing to install Docker on that
machine, then
getting MET is as simple as running:
docker pull dtcenter/met:8.1
If not, and many sys admins object to the use of Docker, compiling
it
from scratch is the other alternative.
2. Because you are having difficulty installing the external
libraries
MET needs from scratch, we do have an install script for MET and
its
external libraries that may be useful to you. This script may or
may not
work right away. Some systems have needed more work than others.
I will
attempt to help you as best as I can.
3. We can continue with trying to resolve problems as we have been
doing. I see that you have sent your make_install.log which
contains the
same error that it did previously. We can do some further
debugging here
if you'd like. For example, next, I would have you send me
listings of the
directory (using the "ls -l" command) where the header files and
the
library files live for the NetCDF files. I would also need you to
send me
the config.log file for MET as well.
Please let me know how you would like to proceed.
Thanks,
Julie
On Mon, Oct 7, 2019 at 3:10 AM Das Dores Ngamini via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
>
> Please, can you offer me another way to fill out my contingency
table for
> wrf forecasts? The filing deadline of our memories is close and my
MET
> still does not give.
> Best Regards.
> Dorès
>
> Le lun. 7 oct. 2019 à 10:03, Das Dores Ngamini
<ngaminidas at gmail.com> a
> écrit :
>
> > Hello Julie
> > Throughout the weekend, I tried to compile met. I used the same
netcdf as
> > during the wrf compilation. I always get the same mistakes.
> > I also compiled netcdf again and, I still get the errors.
> > Attached are these files.
> >
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Tue Oct 08 02:51:35 2019
Hello Julie,
I'm so glad for the help you give me.
I will like to proceed by the solution 1. But, I don't know if my
system
administrator is willing to install Docker on my machine or not. My
machine
is DELL {LATITUDE | E5430, intel core i5, system linux, Debian,
kubuntu}.
I don't know if these informations are importantes.
I'm expecting to you.
Best Regards,
Dorès
Le lun. 7 oct. 2019 à 19:59, Julie Prestopnik via RT
<met_help at ucar.edu> a
écrit :
> Hi Dorès.
>
> I'm so sorry to see that you are still having difficulty getting MET
> installed. We have a few options:
>
> 1. The easiest way to make MET available would be using a Docker
> container. If your sys admin is willing to install Docker on that
> machine, then
> getting MET is as simple as running:
> docker pull dtcenter/met:8.1
> If not, and many sys admins object to the use of Docker,
compiling it
> from scratch is the other alternative.
> 2. Because you are having difficulty installing the external
libraries
> MET needs from scratch, we do have an install script for MET and
its
> external libraries that may be useful to you. This script may or
may
> not
> work right away. Some systems have needed more work than others.
I
> will
> attempt to help you as best as I can.
> 3. We can continue with trying to resolve problems as we have
been
> doing. I see that you have sent your make_install.log which
contains
> the
> same error that it did previously. We can do some further
debugging
> here
> if you'd like. For example, next, I would have you send me
listings of
> the
> directory (using the "ls -l" command) where the header files and
the
> library files live for the NetCDF files. I would also need you
to send
> me
> the config.log file for MET as well.
>
> Please let me know how you would like to proceed.
>
> Thanks,
> Julie
>
>
> On Mon, Oct 7, 2019 at 3:10 AM Das Dores Ngamini via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
> >
> > Please, can you offer me another way to fill out my contingency
table for
> > wrf forecasts? The filing deadline of our memories is close and my
MET
> > still does not give.
> > Best Regards.
> > Dorès
> >
> > Le lun. 7 oct. 2019 à 10:03, Das Dores Ngamini
<ngaminidas at gmail.com> a
> > écrit :
> >
> > > Hello Julie
> > > Throughout the weekend, I tried to compile met. I used the same
netcdf
> as
> > > during the wrf compilation. I always get the same mistakes.
> > > I also compiled netcdf again and, I still get the errors.
> > > Attached are these files.
> > >
> >
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: Help
From: Julie Prestopnik
Time: Tue Oct 08 09:09:57 2019
Hi Dorès.
Please refer your system administrator to the following webpage, when
you
inquire about whether or not it is ok to have MET installed using
docker:
https://dtcenter.org/community-code/model-evaluation-tools-met/docker-
container-met-8-1
Please feel free to follow up with any questions you or your system
administrator have. If you end up being unable to use Docker, we can
proceed with option 2 or 3.
Julie
On Tue, Oct 8, 2019 at 2:52 AM Das Dores Ngamini via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
>
> Hello Julie,
> I'm so glad for the help you give me.
> I will like to proceed by the solution 1. But, I don't know if my
system
> administrator is willing to install Docker on my machine or not. My
machine
> is DELL {LATITUDE | E5430, intel core i5, system linux, Debian,
kubuntu}.
> I don't know if these informations are importantes.
> I'm expecting to you.
> Best Regards,
> Dorès
>
> Le lun. 7 oct. 2019 à 19:59, Julie Prestopnik via RT
<met_help at ucar.edu> a
> écrit :
>
> > Hi Dorès.
> >
> > I'm so sorry to see that you are still having difficulty getting
MET
> > installed. We have a few options:
> >
> > 1. The easiest way to make MET available would be using a
Docker
> > container. If your sys admin is willing to install Docker on
that
> > machine, then
> > getting MET is as simple as running:
> > docker pull dtcenter/met:8.1
> > If not, and many sys admins object to the use of Docker,
compiling it
> > from scratch is the other alternative.
> > 2. Because you are having difficulty installing the external
libraries
> > MET needs from scratch, we do have an install script for MET
and its
> > external libraries that may be useful to you. This script may
or may
> > not
> > work right away. Some systems have needed more work than
others. I
> > will
> > attempt to help you as best as I can.
> > 3. We can continue with trying to resolve problems as we have
been
> > doing. I see that you have sent your make_install.log which
contains
> > the
> > same error that it did previously. We can do some further
debugging
> > here
> > if you'd like. For example, next, I would have you send me
listings
> of
> > the
> > directory (using the "ls -l" command) where the header files
and the
> > library files live for the NetCDF files. I would also need you
to
> send
> > me
> > the config.log file for MET as well.
> >
> > Please let me know how you would like to proceed.
> >
> > Thanks,
> > Julie
> >
> >
> > On Mon, Oct 7, 2019 at 3:10 AM Das Dores Ngamini via RT <
> met_help at ucar.edu
> > >
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
> > >
> > > Please, can you offer me another way to fill out my contingency
table
> for
> > > wrf forecasts? The filing deadline of our memories is close and
my MET
> > > still does not give.
> > > Best Regards.
> > > Dorès
> > >
> > > Le lun. 7 oct. 2019 à 10:03, Das Dores Ngamini
<ngaminidas at gmail.com>
> a
> > > écrit :
> > >
> > > > Hello Julie
> > > > Throughout the weekend, I tried to compile met. I used the
same
> netcdf
> > as
> > > > during the wrf compilation. I always get the same mistakes.
> > > > I also compiled netcdf again and, I still get the errors.
> > > > Attached are these files.
> > > >
> > >
> >
> > --
> > Julie Prestopnik
> > Software Engineer
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> > My working day may not be your working day. Please do not feel
obliged
> to
> > reply to this email outside of your normal working hours.
> >
> >
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Thu Oct 10 22:31:24 2019
Hello Julie,
Execuss me for not writing earlier.
I tried the best I could to install Docker. So far, the first command
gives
me the errors. So I see that it is better to change soultion.
I would like us to try the second solution.
Please, can you send me your installation script for MET and its
libraries?
I would like to start again to be sure to do everything that is to be
done.
Best Regards
Dorès
Le mar. 8 oct. 2019 à 16:09, Julie Prestopnik via RT
<met_help at ucar.edu> a
écrit :
> Hi Dorès.
>
> Please refer your system administrator to the following webpage,
when you
> inquire about whether or not it is ok to have MET installed using
docker:
>
> https://dtcenter.org/community-code/model-evaluation-tools-
met/docker-container-met-8-1
>
> Please feel free to follow up with any questions you or your system
> administrator have. If you end up being unable to use Docker, we
can
> proceed with option 2 or 3.
>
> Julie
>
> On Tue, Oct 8, 2019 at 2:52 AM Das Dores Ngamini via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
> >
> > Hello Julie,
> > I'm so glad for the help you give me.
> > I will like to proceed by the solution 1. But, I don't know if my
system
> > administrator is willing to install Docker on my machine or not.
My
> machine
> > is DELL {LATITUDE | E5430, intel core i5, system linux, Debian,
kubuntu}.
> > I don't know if these informations are importantes.
> > I'm expecting to you.
> > Best Regards,
> > Dorès
> >
> > Le lun. 7 oct. 2019 à 19:59, Julie Prestopnik via RT
<met_help at ucar.edu>
> a
> > écrit :
> >
> > > Hi Dorès.
> > >
> > > I'm so sorry to see that you are still having difficulty getting
MET
> > > installed. We have a few options:
> > >
> > > 1. The easiest way to make MET available would be using a
Docker
> > > container. If your sys admin is willing to install Docker on
that
> > > machine, then
> > > getting MET is as simple as running:
> > > docker pull dtcenter/met:8.1
> > > If not, and many sys admins object to the use of Docker,
compiling
> it
> > > from scratch is the other alternative.
> > > 2. Because you are having difficulty installing the external
> libraries
> > > MET needs from scratch, we do have an install script for MET
and its
> > > external libraries that may be useful to you. This script
may or
> may
> > > not
> > > work right away. Some systems have needed more work than
others. I
> > > will
> > > attempt to help you as best as I can.
> > > 3. We can continue with trying to resolve problems as we have
been
> > > doing. I see that you have sent your make_install.log which
> contains
> > > the
> > > same error that it did previously. We can do some further
debugging
> > > here
> > > if you'd like. For example, next, I would have you send me
listings
> > of
> > > the
> > > directory (using the "ls -l" command) where the header files
and the
> > > library files live for the NetCDF files. I would also need
you to
> > send
> > > me
> > > the config.log file for MET as well.
> > >
> > > Please let me know how you would like to proceed.
> > >
> > > Thanks,
> > > Julie
> > >
> > >
> > > On Mon, Oct 7, 2019 at 3:10 AM Das Dores Ngamini via RT <
> > met_help at ucar.edu
> > > >
> > > wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412
>
> > > >
> > > > Please, can you offer me another way to fill out my
contingency table
> > for
> > > > wrf forecasts? The filing deadline of our memories is close
and my
> MET
> > > > still does not give.
> > > > Best Regards.
> > > > Dorès
> > > >
> > > > Le lun. 7 oct. 2019 à 10:03, Das Dores Ngamini
<ngaminidas at gmail.com
> >
> > a
> > > > écrit :
> > > >
> > > > > Hello Julie
> > > > > Throughout the weekend, I tried to compile met. I used the
same
> > netcdf
> > > as
> > > > > during the wrf compilation. I always get the same mistakes.
> > > > > I also compiled netcdf again and, I still get the errors.
> > > > > Attached are these files.
> > > > >
> > > >
> > >
> > > --
> > > Julie Prestopnik
> > > Software Engineer
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > > My working day may not be your working day. Please do not feel
obliged
> > to
> > > reply to this email outside of your normal working hours.
> > >
> > >
> >
> >
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Thu Oct 10 22:32:20 2019
I use the bashrc.
Le ven. 11 oct. 2019 à 05:31, Das Dores Ngamini <ngaminidas at gmail.com>
a
écrit :
> Hello Julie,
> Execuss me for not writing earlier.
> I tried the best I could to install Docker. So far, the first
command
> gives me the errors. So I see that it is better to change soultion.
> I would like us to try the second solution.
> Please, can you send me your installation script for MET and its
libraries?
> I would like to start again to be sure to do everything that is to
be done.
> Best Regards
> Dorès
>
> Le mar. 8 oct. 2019 à 16:09, Julie Prestopnik via RT
<met_help at ucar.edu>
> a écrit :
>
>> Hi Dorès.
>>
>> Please refer your system administrator to the following webpage,
when you
>> inquire about whether or not it is ok to have MET installed using
docker:
>>
>> https://dtcenter.org/community-code/model-evaluation-tools-
met/docker-container-met-8-1
>>
>> Please feel free to follow up with any questions you or your system
>> administrator have. If you end up being unable to use Docker, we
can
>> proceed with option 2 or 3.
>>
>> Julie
>>
>> On Tue, Oct 8, 2019 at 2:52 AM Das Dores Ngamini via RT <
>> met_help at ucar.edu>
>> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
>> >
>> > Hello Julie,
>> > I'm so glad for the help you give me.
>> > I will like to proceed by the solution 1. But, I don't know if my
system
>> > administrator is willing to install Docker on my machine or not.
My
>> machine
>> > is DELL {LATITUDE | E5430, intel core i5, system linux, Debian,
>> kubuntu}.
>> > I don't know if these informations are importantes.
>> > I'm expecting to you.
>> > Best Regards,
>> > Dorès
>> >
>> > Le lun. 7 oct. 2019 à 19:59, Julie Prestopnik via RT
<met_help at ucar.edu>
>> a
>> > écrit :
>> >
>> > > Hi Dorès.
>> > >
>> > > I'm so sorry to see that you are still having difficulty
getting MET
>> > > installed. We have a few options:
>> > >
>> > > 1. The easiest way to make MET available would be using a
Docker
>> > > container. If your sys admin is willing to install Docker on
that
>> > > machine, then
>> > > getting MET is as simple as running:
>> > > docker pull dtcenter/met:8.1
>> > > If not, and many sys admins object to the use of Docker,
compiling
>> it
>> > > from scratch is the other alternative.
>> > > 2. Because you are having difficulty installing the external
>> libraries
>> > > MET needs from scratch, we do have an install script for MET
and
>> its
>> > > external libraries that may be useful to you. This script
may or
>> may
>> > > not
>> > > work right away. Some systems have needed more work than
others.
>> I
>> > > will
>> > > attempt to help you as best as I can.
>> > > 3. We can continue with trying to resolve problems as we
have been
>> > > doing. I see that you have sent your make_install.log which
>> contains
>> > > the
>> > > same error that it did previously. We can do some further
>> debugging
>> > > here
>> > > if you'd like. For example, next, I would have you send me
>> listings
>> > of
>> > > the
>> > > directory (using the "ls -l" command) where the header files
and
>> the
>> > > library files live for the NetCDF files. I would also need
you to
>> > send
>> > > me
>> > > the config.log file for MET as well.
>> > >
>> > > Please let me know how you would like to proceed.
>> > >
>> > > Thanks,
>> > > Julie
>> > >
>> > >
>> > > On Mon, Oct 7, 2019 at 3:10 AM Das Dores Ngamini via RT <
>> > met_help at ucar.edu
>> > > >
>> > > wrote:
>> > >
>> > > >
>> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412
>
>> > > >
>> > > > Please, can you offer me another way to fill out my
contingency
>> table
>> > for
>> > > > wrf forecasts? The filing deadline of our memories is close
and my
>> MET
>> > > > still does not give.
>> > > > Best Regards.
>> > > > Dorès
>> > > >
>> > > > Le lun. 7 oct. 2019 à 10:03, Das Dores Ngamini <
>> ngaminidas at gmail.com>
>> > a
>> > > > écrit :
>> > > >
>> > > > > Hello Julie
>> > > > > Throughout the weekend, I tried to compile met. I used the
same
>> > netcdf
>> > > as
>> > > > > during the wrf compilation. I always get the same mistakes.
>> > > > > I also compiled netcdf again and, I still get the errors.
>> > > > > Attached are these files.
>> > > > >
>> > > >
>> > >
>> > > --
>> > > Julie Prestopnik
>> > > Software Engineer
>> > > National Center for Atmospheric Research
>> > > Research Applications Laboratory
>> > > Phone: 303.497.8399
>> > > Email: jpresto at ucar.edu
>> > >
>> > > My working day may not be your working day. Please do not feel
>> obliged
>> > to
>> > > reply to this email outside of your normal working hours.
>> > >
>> > >
>> >
>> >
>>
>> --
>> Julie Prestopnik
>> Software Engineer
>> National Center for Atmospheric Research
>> Research Applications Laboratory
>> Phone: 303.497.8399
>> Email: jpresto at ucar.edu
>>
>> My working day may not be your working day. Please do not feel
obliged to
>> reply to this email outside of your normal working hours.
>>
>>
------------------------------------------------
Subject: Help
From: Julie Prestopnik
Time: Fri Oct 11 09:31:33 2019
Hi Dorès.
I'm sorry to hear that you are having trouble with Docker.
You can find the script to help you install MET at this link, and I'll
put
instructions below:
https://dtcenter.org/community-code/model-evaluation-tools-
met/download#compile
This script may or may not work right away. Some systems have needed
more
work than others. To get started, decide where you would like to
install
MET. The following example will assume you're going to put it in
/home/dores/Tutorial_Master/TP_Prevision/MET/8.1.
You'll need to download compile_MET_all.sh and tar_files.tar from the
link
above. You'll also need to download our latest MET release:
https://dtcenter.org/sites/default/files/community-code/met/met-
8.1.1.20190708.tar.gz
Put compile_MET_all.sh.tgz (and unpack it with "tar -zxf
compile_MET_all.sh.tgz
") and tar_files.tar in
/home/dores/Tutorial_Master/TP_Prevision/MET/8.1
(or where ever you chose to put it). Unpack the tar file and move
met-8.1.1.20190708.tar.gz into the tar_files directory.
Then, you'll need to set up some environment variables as described in
the
link above.
For reference using this example, I would set the following:
export TEST_BASE=/home/dores/Tutorial_Master/TP_Prevision/MET//8.1
export COMPILER=gnu_6.3.0 (The format is "compiler" underscore
"version".
>From previous log files you sent to me, it looks like you are using
gcc/g++, so you'll want to specify "gnu" for the compiler. You can
find the
version by running "gcc --version".)
export MET_SUBDIR=${TEST_BASE}/
export MET_TARBALL=met-8.1.1.20190708.tar.gz
If you want to install the Python embedding functionality, please set
the
following variables as well. If you do not want to use the Python
embedding functionality in MET, do not set the following environment
variables:
export MET_PYTHON_CC=`python-config --cflags`
export MET_PYTHON_LD=`python-config --ldflags` (This may not work.
Run
python-config --ldflags on the command line and see if you get output
including "-L". If you don't, please let me know and I can walk you
through how to find this information.)
export PYTHON_MODULE_USE=/usrx/local/dev/modulefiles (Assuming you're
not
using modulefiles, it doesn't matter what you set this to, but it
needs to
be set to something otherwise MET won't configure for Python
embedding.
You could just set it to "python".).
If you're not using modules, the output of the script will say
something
about modules not being found and you can safely ignore that.
You may need to make the script executable (You can do that by running
"chmod 775 compile_MET_all.sh"), but then you can run it with
"./compile_MET_all.sh". For some people who have used this script,
they
have had their own laptops with hardly anything on it. They have
needed to
install the following packages using the following commands:
sudo apt-get update
sudo apt install python-dev
sudo apt-get install flex bison
sudo apt-get install libpixman-1-dev
sudo apt-get install libjpeg-dev
sudo apt-get install pkg-config
sudo apt-get install libpng-dev
sudo apt-get install unzip
If the script runs and starts installing the external libraries
successfully but then stops, there are constants which you can set to
0, so
that you won't have to wait for them to be installed again. In the
compile
script you'll see the following which you can modify if necessary:
COMPILE_GSL=1
COMPILE_BUFRLIB=1
COMPILE_ZLIB=1
COMPILE_LIBPNG=1
COMPILE_JASPER=1
COMPILE_G2CLIB=1
COMPILE_HDF=1
COMPILE_HDFEOS=1
COMPILE_NETCDF=1
COMPILE_FREETYPE=1
COMPILE_CAIRO=1
COMPILE_MET=1
Please let me know if you have any questions. I know this is a lot to
take
in, so don't hesitate to reach out with any questions.
Thanks,
Julie
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Help
From: Das Dores Ngamini
Time: Fri Oct 11 17:18:40 2019
Hello Julie,
It is with overwhelming joy that I am writing to you at this moment.
Because thanks to you, I have the impression of having compiled MET
successfully.
I can not find the right words to tell you how much your help has been
of
undeniable benefit to me.
To express my gratitude, I would like, if you allow me to introduce
your
name in the thank you part of my master's thesis, because I will never
have
arrived without you.
I attach to this mail files so that you check, please, if everything
has
been done correctly.
Also, I do not yet know how to bring out my contingency table with
MET. I
will read the "user guide" to see if I find a solution. But, I would
like
you to guide me, please, if you can.
Best Regards
Dorès
Le ven. 11 oct. 2019 à 16:31, Julie Prestopnik via RT
<met_help at ucar.edu> a
écrit :
> Hi Dorès.
>
> I'm sorry to hear that you are having trouble with Docker.
>
> You can find the script to help you install MET at this link, and
I'll put
> instructions below:
>
> https://dtcenter.org/community-code/model-evaluation-tools-
met/download#compile
>
> This script may or may not work right away. Some systems have
needed more
> work than others. To get started, decide where you would like to
install
> MET. The following example will assume you're going to put it in
> /home/dores/Tutorial_Master/TP_Prevision/MET/8.1.
>
> You'll need to download compile_MET_all.sh and tar_files.tar from
the link
> above. You'll also need to download our latest MET release:
>
> https://dtcenter.org/sites/default/files/community-code/met/met-
8.1.1.20190708.tar.gz
>
> Put compile_MET_all.sh.tgz (and unpack it with "tar -zxf
> compile_MET_all.sh.tgz
> ") and tar_files.tar in
/home/dores/Tutorial_Master/TP_Prevision/MET/8.1
> (or where ever you chose to put it). Unpack the tar file and move
> met-8.1.1.20190708.tar.gz into the tar_files directory.
>
> Then, you'll need to set up some environment variables as described
in the
> link above.
>
> For reference using this example, I would set the following:
>
> export TEST_BASE=/home/dores/Tutorial_Master/TP_Prevision/MET//8.1
> export COMPILER=gnu_6.3.0 (The format is "compiler" underscore
"version".
> From previous log files you sent to me, it looks like you are using
> gcc/g++, so you'll want to specify "gnu" for the compiler. You can
find the
> version by running "gcc --version".)
>
> export MET_SUBDIR=${TEST_BASE}/
> export MET_TARBALL=met-8.1.1.20190708.tar.gz
>
> If you want to install the Python embedding functionality, please
set the
> following variables as well. If you do not want to use the Python
> embedding functionality in MET, do not set the following environment
> variables:
>
> export MET_PYTHON_CC=`python-config --cflags`
> export MET_PYTHON_LD=`python-config --ldflags` (This may not work.
Run
> python-config --ldflags on the command line and see if you get
output
> including "-L". If you don't, please let me know and I can walk you
> through how to find this information.)
> export PYTHON_MODULE_USE=/usrx/local/dev/modulefiles (Assuming
you're not
> using modulefiles, it doesn't matter what you set this to, but it
needs to
> be set to something otherwise MET won't configure for Python
embedding.
> You could just set it to "python".).
>
> If you're not using modules, the output of the script will say
something
> about modules not being found and you can safely ignore that.
>
> You may need to make the script executable (You can do that by
running
> "chmod 775 compile_MET_all.sh"), but then you can run it with
> "./compile_MET_all.sh". For some people who have used this script,
they
> have had their own laptops with hardly anything on it. They have
needed to
> install the following packages using the following commands:
>
> sudo apt-get update
> sudo apt install python-dev
> sudo apt-get install flex bison
> sudo apt-get install libpixman-1-dev
> sudo apt-get install libjpeg-dev
> sudo apt-get install pkg-config
> sudo apt-get install libpng-dev
> sudo apt-get install unzip
>
> If the script runs and starts installing the external libraries
> successfully but then stops, there are constants which you can set
to 0, so
> that you won't have to wait for them to be installed again. In the
compile
> script you'll see the following which you can modify if necessary:
>
> COMPILE_GSL=1
> COMPILE_BUFRLIB=1
> COMPILE_ZLIB=1
> COMPILE_LIBPNG=1
> COMPILE_JASPER=1
> COMPILE_G2CLIB=1
> COMPILE_HDF=1
> COMPILE_HDFEOS=1
> COMPILE_NETCDF=1
> COMPILE_FREETYPE=1
> COMPILE_CAIRO=1
> COMPILE_MET=1
>
> Please let me know if you have any questions. I know this is a lot
to take
> in, so don't hesitate to reach out with any questions.
>
> Thanks,
> Julie
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: Help
From: Julie Prestopnik
Time: Mon Oct 14 09:42:51 2019
Hi Dorès.
This was a very nice message to receive this morning. I am so glad
that
you were able to get MET installed using the script! I took a look at
the
files that you sent and everything looks good to me as well.
Congratulations!
Regarding mentioning my name in your master's thesis, that is totally
fine
if that is what you would like to do, but certainly not necessary. I
hope
your master's thesis will go well!
I'll go ahead and close this ticket regarding the MET installation
issues.
Please feel free to start a new ticket with met_help at ucar.edu with any
questions you have regarding contingency tables. Our team will do our
best
to help you.
Kind regards,
Julie
On Fri, Oct 11, 2019 at 5:18 PM Das Dores Ngamini via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92412 >
>
> Hello Julie,
> It is with overwhelming joy that I am writing to you at this moment.
> Because thanks to you, I have the impression of having compiled MET
> successfully.
> I can not find the right words to tell you how much your help has
been of
> undeniable benefit to me.
> To express my gratitude, I would like, if you allow me to introduce
your
> name in the thank you part of my master's thesis, because I will
never have
> arrived without you.
>
> I attach to this mail files so that you check, please, if everything
has
> been done correctly.
>
> Also, I do not yet know how to bring out my contingency table with
MET. I
> will read the "user guide" to see if I find a solution. But, I would
like
> you to guide me, please, if you can.
>
> Best Regards
> Dorès
>
> Le ven. 11 oct. 2019 à 16:31, Julie Prestopnik via RT
<met_help at ucar.edu>
> a
> écrit :
>
> > Hi Dorès.
> >
> > I'm sorry to hear that you are having trouble with Docker.
> >
> > You can find the script to help you install MET at this link, and
I'll
> put
> > instructions below:
> >
> >
> https://dtcenter.org/community-code/model-evaluation-tools-
met/download#compile
> >
> > This script may or may not work right away. Some systems have
needed
> more
> > work than others. To get started, decide where you would like to
install
> > MET. The following example will assume you're going to put it in
> > /home/dores/Tutorial_Master/TP_Prevision/MET/8.1.
> >
> > You'll need to download compile_MET_all.sh and tar_files.tar from
the
> link
> > above. You'll also need to download our latest MET release:
> >
> >
> https://dtcenter.org/sites/default/files/community-code/met/met-
8.1.1.20190708.tar.gz
> >
> > Put compile_MET_all.sh.tgz (and unpack it with "tar -zxf
> > compile_MET_all.sh.tgz
> > ") and tar_files.tar in
/home/dores/Tutorial_Master/TP_Prevision/MET/8.1
> > (or where ever you chose to put it). Unpack the tar file and move
> > met-8.1.1.20190708.tar.gz into the tar_files directory.
> >
> > Then, you'll need to set up some environment variables as
described in
> the
> > link above.
> >
> > For reference using this example, I would set the following:
> >
> > export TEST_BASE=/home/dores/Tutorial_Master/TP_Prevision/MET//8.1
> > export COMPILER=gnu_6.3.0 (The format is "compiler" underscore
> "version".
> > From previous log files you sent to me, it looks like you are
using
> > gcc/g++, so you'll want to specify "gnu" for the compiler. You can
find
> the
> > version by running "gcc --version".)
> >
> > export MET_SUBDIR=${TEST_BASE}/
> > export MET_TARBALL=met-8.1.1.20190708.tar.gz
> >
> > If you want to install the Python embedding functionality, please
set the
> > following variables as well. If you do not want to use the Python
> > embedding functionality in MET, do not set the following
environment
> > variables:
> >
> > export MET_PYTHON_CC=`python-config --cflags`
> > export MET_PYTHON_LD=`python-config --ldflags` (This may not work.
Run
> > python-config --ldflags on the command line and see if you get
output
> > including "-L". If you don't, please let me know and I can walk
you
> > through how to find this information.)
> > export PYTHON_MODULE_USE=/usrx/local/dev/modulefiles (Assuming
you're not
> > using modulefiles, it doesn't matter what you set this to, but it
needs
> to
> > be set to something otherwise MET won't configure for Python
embedding.
> > You could just set it to "python".).
> >
> > If you're not using modules, the output of the script will say
something
> > about modules not being found and you can safely ignore that.
> >
> > You may need to make the script executable (You can do that by
running
> > "chmod 775 compile_MET_all.sh"), but then you can run it with
> > "./compile_MET_all.sh". For some people who have used this
script, they
> > have had their own laptops with hardly anything on it. They have
needed
> to
> > install the following packages using the following commands:
> >
> > sudo apt-get update
> > sudo apt install python-dev
> > sudo apt-get install flex bison
> > sudo apt-get install libpixman-1-dev
> > sudo apt-get install libjpeg-dev
> > sudo apt-get install pkg-config
> > sudo apt-get install libpng-dev
> > sudo apt-get install unzip
> >
> > If the script runs and starts installing the external libraries
> > successfully but then stops, there are constants which you can set
to 0,
> so
> > that you won't have to wait for them to be installed again. In
the
> compile
> > script you'll see the following which you can modify if necessary:
> >
> > COMPILE_GSL=1
> > COMPILE_BUFRLIB=1
> > COMPILE_ZLIB=1
> > COMPILE_LIBPNG=1
> > COMPILE_JASPER=1
> > COMPILE_G2CLIB=1
> > COMPILE_HDF=1
> > COMPILE_HDFEOS=1
> > COMPILE_NETCDF=1
> > COMPILE_FREETYPE=1
> > COMPILE_CAIRO=1
> > COMPILE_MET=1
> >
> > Please let me know if you have any questions. I know this is a
lot to
> take
> > in, so don't hesitate to reach out with any questions.
> >
> > Thanks,
> > Julie
> > --
> > Julie Prestopnik
> > Software Engineer
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> > My working day may not be your working day. Please do not feel
obliged
> to
> > reply to this email outside of your normal working hours.
> >
> >
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
More information about the Met_help
mailing list