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

View Problem - Process Solution

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

% Computer : n019.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:47 EDT 2023

% Result   : Unknown 99.22s 102.06s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.11  % Problem  : LAT316+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n019.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 14:31:47 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.12/6.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.12/6.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.12/6.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.96/12.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.96/12.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.96/12.20  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.85/18.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.85/18.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.85/18.43  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.89/24.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.89/24.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.89/24.83  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.19/29.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.19/29.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.19/29.35  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.33/35.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.33/35.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.33/35.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 40.45/41.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.45/41.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.45/41.49  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 46.40/47.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.40/47.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.40/47.59  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 52.25/53.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.25/53.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.25/53.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.03/57.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.03/57.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.03/57.96  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.84/63.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.84/63.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.84/63.94  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.90/70.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.90/70.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.90/70.59  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.75/76.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.75/76.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.75/76.49  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.13/101.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.13/101.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.13/101.49  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.22/102.06  Timeout
%------------------------------------------------------------------------------