TSTP Solution File: HWV131+1 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : HWV131+1 : TPTP v8.1.2. Released v6.1.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n003.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 11:18:21 EDT 2023

% Result   : Unknown 208.69s 204.88s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : HWV131+1 : TPTP v8.1.2. Released v6.1.0.
% 0.08/0.16  % Command  : nanocop.sh %s %d
% 0.16/0.38  % Computer : n003.cluster.edu
% 0.16/0.38  % Model    : x86_64 x86_64
% 0.16/0.38  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.16/0.38  % Memory   : 8042.1875MB
% 0.16/0.38  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.16/0.38  % CPULimit : 300
% 0.16/0.38  % WCLimit  : 300
% 0.16/0.38  % DateTime : Fri May 19 03:37:01 EDT 2023
% 0.16/0.38  % CPUTime  : 
% 20.37/19.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.37/19.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.37/19.80  Peak sizes were: global stack 125720 kbytes, trail stack 5352 kbytes
% 41.42/40.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.42/40.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.42/40.34  Peak sizes were: global stack 125720 kbytes, trail stack 5352 kbytes
% 62.08/60.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.08/60.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.08/60.66  Peak sizes were: global stack 125720 kbytes, trail stack 5480 kbytes
% 81.46/80.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.46/80.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.46/80.30  Peak sizes were: global stack 124312 kbytes, trail stack 6760 kbytes
% 101.19/99.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 101.19/99.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 101.19/99.36  Peak sizes were: global stack 125720 kbytes, trail stack 5352 kbytes
% 118.99/117.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 118.99/117.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 118.99/117.18  Peak sizes were: global stack 125848 kbytes, trail stack 5352 kbytes
% 147.67/145.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 147.67/145.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.67/145.25  Peak sizes were: global stack 124312 kbytes, trail stack 6760 kbytes
% 208.67/204.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 208.67/204.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 208.67/204.22  Peak sizes were: global stack 125720 kbytes, trail stack 5352 kbytes
% 208.69/204.88  Timeout
%------------------------------------------------------------------------------