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

% Computer : n027.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:55 EDT 2023

% Result   : Unknown 143.99s 144.23s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.01/0.12  % Problem  : LAT350+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n027.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 14:57:28 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 10.09/9.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.09/9.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.09/9.90  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 23.64/23.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.64/23.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.64/23.89  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 34.32/34.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.32/34.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.32/34.43  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 45.09/44.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.09/44.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.09/44.89  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 51.36/51.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.36/51.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.36/51.86  Peak sizes were: global stack 127896 kbytes, trail stack 4200 kbytes
% 62.06/62.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.06/62.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.06/62.33  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 70.31/70.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.31/70.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.31/70.39  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 78.56/78.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.56/78.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.56/78.71  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 87.57/87.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 87.57/87.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 87.57/87.69  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 92.76/93.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.76/93.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.76/93.32  Peak sizes were: global stack 127896 kbytes, trail stack 4200 kbytes
% 101.48/101.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 101.48/101.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 101.48/101.93  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 143.89/143.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 143.89/143.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 143.89/143.78  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 143.99/144.23  Timeout
%------------------------------------------------------------------------------