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

% Computer : n003.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 192.03s 188.06s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : SEU407+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n003.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:09:24 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 15.68/15.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.68/15.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.68/15.32  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 31.29/30.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.29/30.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.29/30.84  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 46.75/46.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.75/46.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.75/46.31  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 70.47/69.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.47/69.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.47/69.75  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 86.20/84.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.20/84.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.20/84.92  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 101.45/99.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 101.45/99.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 101.45/99.98  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 134.75/132.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 134.75/132.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 134.75/132.87  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 191.99/188.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 191.99/188.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 191.99/188.03  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 192.03/188.06  Timeout
%------------------------------------------------------------------------------