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

% Computer : n023.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:36 EDT 2023

% Result   : Unknown 158.52s 158.00s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR101+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n023.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:08:14 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 11.13/10.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.13/10.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.13/10.87  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.14/22.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.14/22.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.14/22.34  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.78/34.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.78/34.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.78/34.36  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 46.83/47.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.83/47.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.83/47.17  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 50.96/52.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.96/52.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.96/52.02  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 61.58/62.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.58/62.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.58/62.48  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 77.24/77.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.24/77.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.24/77.74  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 90.75/91.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.75/91.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.75/91.17  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 105.03/105.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.03/105.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.03/105.25  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 158.42/157.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 158.42/157.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 158.42/157.35  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 158.52/158.00  Timeout
%------------------------------------------------------------------------------