%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR084+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:25 EDT 2023

% Result   : Unknown 158.89s 160.03s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : CSR084+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.12/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n015.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Fri May 19 01:04:07 EDT 2023
% 0.19/0.34  % CPUTime  : 
% 14.37/14.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.37/14.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.37/14.08  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 25.51/25.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.51/25.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.51/25.50  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 36.24/36.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.24/36.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.24/36.60  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 47.21/48.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.21/48.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.21/48.08  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 51.25/52.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.25/52.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.25/52.93  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 62.55/64.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.55/64.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.55/64.01  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 78.05/79.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.05/79.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.05/79.59  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 91.17/92.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 91.17/92.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.17/92.80  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 105.56/107.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.56/107.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.56/107.38  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 158.85/159.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 158.85/159.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 158.85/159.21  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 158.89/160.03  Timeout
%------------------------------------------------------------------------------