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

% Computer : n021.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:58 EDT 2023

% Result   : Unknown 165.36s 159.45s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.13  % Problem  : LAT359+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.36  % Computer : n021.cluster.edu
% 0.14/0.36  % Model    : x86_64 x86_64
% 0.14/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36  % Memory   : 8042.1875MB
% 0.14/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36  % CPULimit : 300
% 0.14/0.36  % WCLimit  : 300
% 0.14/0.36  % DateTime : Thu May 18 14:04:22 EDT 2023
% 0.14/0.36  % CPUTime  : 
% 13.12/12.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.12/12.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.12/12.80  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 24.90/24.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.90/24.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.90/24.18  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 36.63/35.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.63/35.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.63/35.53  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 48.46/47.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.46/47.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.46/47.06  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 55.36/53.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.36/53.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.36/53.68  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 67.06/65.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.06/65.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.06/65.63  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 78.90/77.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.90/77.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.90/77.23  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 91.14/88.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 91.14/88.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.14/88.95  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 107.65/105.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 107.65/105.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 107.65/105.57  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 165.33/158.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 165.33/158.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 165.33/158.71  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 165.36/159.45  Timeout
%------------------------------------------------------------------------------