%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : LAT338+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n001.cluster.edu
% Model    : x86_64 x86_64
% CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 2.10GHz
% Memory   : 8042.1875MB
% OS       : Linux 3.10.0-693.el7.x86_64
% CPULimit : 300s
% WCLimit  : 300s
% DateTime : Fri May 19 11:28:52 EDT 2023

% Result   : Unknown 148.45s 147.68s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT338+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n001.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Thu May 18 14:49:27 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 11.26/11.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.26/11.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.26/11.03  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 21.31/21.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.31/21.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.31/21.38  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 31.22/31.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.22/31.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.22/31.69  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.62/42.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.62/42.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.62/42.46  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 47.76/48.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.76/48.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.76/48.74  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 58.76/59.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.76/59.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.76/59.69  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 69.22/70.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.22/70.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.22/70.53  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 79.91/81.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.91/81.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.91/81.16  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 96.02/96.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 96.02/96.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 96.02/96.75  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 148.43/147.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 148.43/147.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 148.43/147.07  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 148.45/147.68  Timeout
%------------------------------------------------------------------------------