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

% Computer : n029.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:31 EDT 2023

% Result   : Unknown 205.51s 202.63s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.11  % Problem  : SEU420+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n029.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  : 
% 17.04/16.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.04/16.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.04/16.68  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 34.47/33.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.47/33.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.47/33.60  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 51.81/51.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.81/51.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.81/51.28  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 76.11/75.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.11/75.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.11/75.47  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 93.46/92.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.46/92.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.46/92.59  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 111.18/110.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 111.18/110.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 111.18/110.67  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 145.36/144.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 145.36/144.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 145.36/144.07  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 205.47/202.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 205.47/202.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 205.47/202.14  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 205.51/202.63  Timeout
%------------------------------------------------------------------------------