TSTP Solution File: ALG228+4 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : ALG228+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 10:08:18 EDT 2023

% Result   : Unknown 124.37s 126.84s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : ALG228+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n002.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 23:26:25 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 8.04/7.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.04/7.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.04/7.93  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 15.86/16.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.86/16.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.86/16.15  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 23.71/24.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.71/24.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.71/24.46  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 31.73/32.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.73/32.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.73/32.88  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 36.89/38.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.89/38.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.89/38.48  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 47.10/48.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.10/48.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.10/48.55  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 55.18/56.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.18/56.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.18/56.74  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 63.23/65.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.23/65.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.23/65.10  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 71.24/73.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.24/73.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.24/73.31  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 76.28/78.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.28/78.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.28/78.79  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 84.08/86.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 84.08/86.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.08/86.59  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 124.32/126.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 124.32/126.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 124.32/126.01  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 124.37/126.84  Timeout
%------------------------------------------------------------------------------