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

% Computer : n026.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 165.21s 162.53s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.10  % Problem  : LAT366+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.10  % Command  : nanocop.sh %s %d
% 0.10/0.30  % Computer : n026.cluster.edu
% 0.10/0.30  % Model    : x86_64 x86_64
% 0.10/0.30  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.10/0.30  % Memory   : 8042.1875MB
% 0.10/0.30  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.10/0.30  % CPULimit : 300
% 0.10/0.30  % WCLimit  : 300
% 0.10/0.30  % DateTime : Thu May 18 14:45:58 EDT 2023
% 0.10/0.30  % CPUTime  : 
% 14.62/14.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.62/14.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.62/14.34  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 28.40/28.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.40/28.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.40/28.05  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 40.26/39.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.26/39.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.26/39.81  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 51.60/50.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.60/50.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.60/50.78  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 58.63/57.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.63/57.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.63/57.91  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 70.50/69.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.50/69.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.50/69.93  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 82.56/81.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.56/81.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.56/81.47  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 94.20/93.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.20/93.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.20/93.61  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 110.91/109.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 110.91/109.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 110.91/109.83  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 165.21/162.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 165.21/162.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 165.21/162.49  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 165.21/162.53  Timeout
%------------------------------------------------------------------------------