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

% Computer : n024.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:23 EDT 2023

% Result   : Unknown 151.34s 152.14s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.13  % Problem  : CSR081+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.13/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.35  % Computer : n024.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 300
% 0.14/0.35  % DateTime : Thu May 18 23:46:36 EDT 2023
% 0.14/0.35  % CPUTime  : 
% 11.52/11.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.52/11.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.52/11.29  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.65/22.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.65/22.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.65/22.44  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.77/33.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.77/33.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.77/33.84  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 45.08/45.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.08/45.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.08/45.50  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 49.65/50.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.65/50.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.65/50.46  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 60.94/62.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.94/62.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.94/62.09  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 72.28/73.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.28/73.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.28/73.56  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 83.72/85.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.72/85.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.72/85.15  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 97.99/99.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.99/99.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.99/99.18  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 151.27/151.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 151.27/151.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 151.27/151.18  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 151.34/152.14  Timeout
%------------------------------------------------------------------------------