%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : SEU446+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:04:41 EDT 2023

% Result   : Unknown 210.04s 206.45s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : SEU446+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/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:09:19 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 17.60/17.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.60/17.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.60/17.21  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 34.41/34.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.41/34.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.41/34.05  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 52.15/51.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.15/51.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.15/51.60  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 76.74/75.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.74/75.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.74/75.80  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 94.38/92.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.38/92.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.38/92.89  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 112.13/110.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 112.13/110.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 112.13/110.60  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 146.50/144.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 146.50/144.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 146.50/144.18  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 210.01/205.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 210.01/205.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 210.01/205.50  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 210.04/206.45  Timeout
%------------------------------------------------------------------------------