TSTP Solution File: ITP016+5 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : ITP016+5 : TPTP v8.1.2. Bugfixed v7.5.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:23:19 EDT 2023

% Result   : Unknown 69.95s 75.07s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : ITP016+5 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n005.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 21:25:39 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 3.89/3.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.89/3.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.89/3.97  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 7.62/8.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.62/8.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.62/8.03  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 11.27/12.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.27/12.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.27/12.18  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 15.03/16.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.03/16.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.03/16.39  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 17.74/19.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.74/19.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.74/19.51  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 21.49/23.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.49/23.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.49/23.65  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 25.21/27.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.21/27.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.21/27.78  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 28.89/31.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.89/31.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.89/31.92  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 32.77/36.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.77/36.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.77/36.19  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 35.31/39.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.31/39.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.31/39.07  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 39.26/43.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.26/43.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.26/43.61  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 43.10/47.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.10/47.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.10/47.56  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 46.77/51.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.77/51.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.77/51.59  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 69.93/74.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.93/74.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.93/74.40  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 69.95/75.07  Timeout
%------------------------------------------------------------------------------