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

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

% Result   : Unknown 217.90s 212.75s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.11  % Problem  : SEU450+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.11  % Command  : nanocop.sh %s %d
% 0.11/0.32  % Computer : n025.cluster.edu
% 0.11/0.32  % Model    : x86_64 x86_64
% 0.11/0.32  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.32  % Memory   : 8042.1875MB
% 0.11/0.32  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.32  % CPULimit : 300
% 0.11/0.32  % WCLimit  : 300
% 0.11/0.32  % DateTime : Thu May 18 13:08:13 EDT 2023
% 0.11/0.32  % CPUTime  : 
% 21.21/20.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.21/20.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.21/20.71  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 40.31/39.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.31/39.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.31/39.43  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 58.37/57.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.37/57.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.37/57.07  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 85.00/82.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 85.00/82.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 85.00/82.92  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 105.62/102.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.62/102.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.62/102.99  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 123.66/121.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 123.66/121.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 123.66/121.31  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 157.81/154.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 157.81/154.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 157.81/154.25  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 217.89/212.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 217.89/212.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 217.89/212.26  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 217.90/212.75  Timeout
%------------------------------------------------------------------------------