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

% Computer : n031.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:29:01 EDT 2023

% Result   : Unknown 167.15s 166.07s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.02/0.11  % Problem  : LAT370+4 : TPTP v8.1.2. Released v3.4.0.
% 0.02/0.11  % Command  : nanocop.sh %s %d
% 0.10/0.32  % Computer : n031.cluster.edu
% 0.10/0.32  % Model    : x86_64 x86_64
% 0.10/0.32  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.10/0.32  % Memory   : 8042.1875MB
% 0.10/0.32  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.10/0.32  % CPULimit : 300
% 0.10/0.32  % WCLimit  : 300
% 0.10/0.32  % DateTime : Thu May 18 14:33:04 EDT 2023
% 0.10/0.32  % CPUTime  : 
% 12.37/12.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.37/12.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.37/12.11  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 24.55/24.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.55/24.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.55/24.52  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 37.07/37.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.07/37.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.07/37.25  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 51.06/51.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.06/51.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.06/51.10  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 58.92/58.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.92/58.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.92/58.71  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 73.47/73.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.47/73.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.47/73.34  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 86.00/85.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.00/85.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.00/85.95  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 97.21/97.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.21/97.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.21/97.00  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 113.51/113.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 113.51/113.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 113.51/113.28  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 167.09/165.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 167.09/165.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 167.09/165.69  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 167.15/166.07  Timeout
%------------------------------------------------------------------------------