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

% Computer : n001.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:32 EDT 2023

% Result   : Unknown 150.88s 149.98s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR096+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n001.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 00:20:20 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 11.21/10.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.21/10.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.21/10.97  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.29/22.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.29/22.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.29/22.41  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.65/34.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.65/34.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.65/34.06  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 44.24/44.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.24/44.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.24/44.81  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 48.56/49.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.56/49.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.56/49.08  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 59.57/59.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.57/59.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.57/59.73  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 71.03/71.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.03/71.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.03/71.51  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 83.09/83.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.09/83.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.09/83.51  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 97.73/98.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.73/98.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.73/98.52  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 150.87/149.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 150.87/149.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 150.87/149.84  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 150.88/149.98  Timeout
%------------------------------------------------------------------------------