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

% Computer : n015.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 12:03:29 EDT 2023

% Result   : Unknown 206.68s 189.28s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : SEU414+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n015.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 12:44:03 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 15.85/15.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.85/15.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.85/15.46  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 31.15/30.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.15/30.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.15/30.57  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 46.37/46.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.37/46.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.37/46.09  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 69.93/69.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.93/69.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.93/69.70  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 85.73/84.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 85.73/84.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 85.73/84.98  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 101.50/100.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 101.50/100.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 101.50/100.59  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 149.39/133.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 149.39/133.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 149.39/133.15  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 206.64/188.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 206.64/188.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 206.64/188.29  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 206.68/189.28  Timeout
%------------------------------------------------------------------------------