%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : SEU408+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 12:03:26 EDT 2023

% Result   : Unknown 194.83s 191.35s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.01/0.12  % Problem  : SEU408+4 : TPTP v8.1.2. Released v3.4.0.
% 0.01/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n026.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 12:46:15 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 15.90/15.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.90/15.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.90/15.50  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 31.61/30.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.61/30.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.61/30.97  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 47.35/46.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.35/46.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.35/46.60  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 71.37/70.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.37/70.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.37/70.08  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 87.31/86.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 87.31/86.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 87.31/86.29  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 103.19/101.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.19/101.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.19/101.67  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 136.66/134.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 136.66/134.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 136.66/134.21  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 194.79/190.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 194.79/190.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 194.79/190.87  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 194.83/191.35  Timeout
%------------------------------------------------------------------------------