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

View Problem - Process Solution

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

% Computer : n005.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:28:49 EDT 2023

% Result   : Unknown 109.03s 112.20s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : LAT325+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n005.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Thu May 18 14:34:13 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 5.76/5.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.76/5.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.76/5.80  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.50/12.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.50/12.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.50/12.00  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.78/18.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.78/18.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.78/18.83  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.63/24.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.63/24.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.63/24.60  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.35/29.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.35/29.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.35/29.74  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 36.47/38.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.47/38.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.47/38.21  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 43.58/45.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.58/45.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.58/45.56  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.16/53.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.16/53.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.16/53.22  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.31/61.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.31/61.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.31/61.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 63.36/66.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.36/66.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.36/66.30  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 70.47/73.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.47/73.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.47/73.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 82.61/85.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.61/85.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.61/85.53  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 108.95/111.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 108.95/111.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 108.95/111.79  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 109.03/112.20  Timeout
%------------------------------------------------------------------------------