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

% Computer : n002.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:39:10 EDT 2023

% Result   : Unknown 166.78s 166.30s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : TOP047+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n002.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 20:22:42 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 11.72/11.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.72/11.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.72/11.49  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.34/22.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.34/22.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.34/22.93  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 34.87/34.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.87/34.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.87/34.29  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.31/45.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.31/45.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.31/45.60  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 52.93/52.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.93/52.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.93/52.31  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 68.35/68.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.35/68.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.35/68.15  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 81.56/81.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.56/81.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.56/81.47  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 94.77/94.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.77/94.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.77/94.90  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 112.23/112.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 112.23/112.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 112.23/112.54  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 166.76/165.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 166.76/165.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 166.76/165.67  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 166.78/166.30  Timeout
%------------------------------------------------------------------------------