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

% Computer : n012.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:04 EDT 2023

% Result   : Unknown 160.17s 159.13s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12  % Problem  : LAT380+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n012.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:22:10 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 11.93/11.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.93/11.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.93/11.78  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.93/24.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.93/24.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.93/24.23  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.52/36.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.52/36.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.52/36.37  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.30/47.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.30/47.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.30/47.96  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.09/54.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.09/54.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.09/54.54  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 65.93/66.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.93/66.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.93/66.71  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 77.77/78.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.77/78.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.77/78.16  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 89.61/90.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.61/90.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.61/90.54  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 106.36/106.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 106.36/106.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.36/106.64  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 160.15/158.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 160.15/158.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 160.15/158.84  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 160.17/159.13  Timeout
%------------------------------------------------------------------------------