%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : LAT365+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:59 EDT 2023

% Result   : Unknown 171.53s 157.98s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.09  % Problem  : LAT365+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.09  % Command  : nanocop.sh %s %d
% 0.07/0.28  % Computer : n027.cluster.edu
% 0.07/0.28  % Model    : x86_64 x86_64
% 0.07/0.28  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.07/0.28  % Memory   : 8042.1875MB
% 0.07/0.28  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.07/0.28  % CPULimit : 300
% 0.07/0.28  % WCLimit  : 300
% 0.07/0.28  % DateTime : Thu May 18 14:30:57 EDT 2023
% 0.07/0.28  % CPUTime  : 
% 13.98/13.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.98/13.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.98/13.74  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 25.32/24.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.32/24.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.32/24.68  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 37.09/36.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.09/36.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.09/36.43  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 48.90/47.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.90/47.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.90/47.91  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 55.65/54.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.65/54.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.65/54.46  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 67.12/66.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.12/66.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.12/66.22  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 89.37/77.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.37/77.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.37/77.54  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 100.71/88.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.71/88.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.71/88.96  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 117.47/105.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 117.47/105.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 117.47/105.51  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 171.42/157.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 171.42/157.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 171.42/157.90  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 171.53/157.98  Timeout
%------------------------------------------------------------------------------