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

% Computer : n008.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:27 EDT 2023

% Result   : Unknown 193.38s 191.10s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : SEU410+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n008.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 13:14:34 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 15.74/15.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.74/15.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.74/15.36  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 31.35/30.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.35/30.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.35/30.90  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 46.85/46.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.85/46.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.85/46.32  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 70.79/69.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.79/69.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.79/69.95  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 86.52/85.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.52/85.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.52/85.91  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 102.06/101.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.06/101.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.06/101.38  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 135.63/134.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.63/134.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.63/134.08  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 193.27/190.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 193.27/190.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 193.27/190.50  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 193.38/191.10  Timeout
%------------------------------------------------------------------------------