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

% Computer : n015.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:40 EDT 2023

% Result   : Unknown 153.50s 154.02s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR106+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n015.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Fri May 19 00:29:52 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 12.71/12.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.71/12.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.71/12.44  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 24.97/24.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.97/24.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.97/24.64  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 37.05/36.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.05/36.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.05/36.79  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 49.08/49.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.08/49.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.08/49.20  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 53.47/54.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.47/54.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.47/54.38  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 64.16/65.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.16/65.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.16/65.59  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 74.58/75.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.58/75.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.58/75.77  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 86.06/87.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.06/87.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.06/87.11  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 99.99/100.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.99/100.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.99/100.98  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 153.47/153.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 153.47/153.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 153.47/153.13  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 153.50/154.02  Timeout
%------------------------------------------------------------------------------