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

% Computer : n009.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:41 EDT 2023

% Result   : Unknown 147.76s 147.97s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12  % Problem  : CSR109+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.12/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n009.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:16:32 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 10.60/10.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.60/10.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.60/10.39  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 21.53/21.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.53/21.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.53/21.23  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 32.07/32.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.07/32.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.07/32.23  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 43.03/43.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.03/43.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.03/43.08  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 47.40/48.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.40/48.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.40/48.10  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 58.37/58.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.37/58.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.37/58.67  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 69.35/70.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.35/70.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.35/70.03  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 80.34/81.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.34/81.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.34/81.57  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 94.46/95.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.46/95.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.46/95.97  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 147.65/147.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 147.65/147.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.65/147.89  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 147.76/147.97  Timeout
%------------------------------------------------------------------------------