TSTP Solution File: CSR102+6 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR102+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n013.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:04:37 EDT 2023

% Result   : Unknown 135.10s 133.23s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : CSR102+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.06/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n013.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 : Fri May 19 00:15:35 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 9.84/9.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.84/9.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.84/9.68  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.31/19.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.31/19.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.31/19.78  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 28.95/29.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.95/29.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.95/29.32  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.59/38.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.59/38.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.59/38.68  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.97/41.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.97/41.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.97/41.93  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 51.57/52.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.57/52.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.57/52.10  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 61.27/61.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.27/61.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.27/61.52  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 70.79/70.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.79/70.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.79/70.70  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 80.54/80.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.54/80.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.54/80.23  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.66/83.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.66/83.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.66/83.32  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 92.93/92.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.93/92.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.93/92.24  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.07/133.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.07/133.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.07/133.04  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.10/133.23  Timeout
%------------------------------------------------------------------------------