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

% Computer : n006.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:40 EDT 2023

% Result   : Unknown 151.77s 149.52s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR107+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n006.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 23:44:36 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 11.33/11.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.33/11.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.33/11.15  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.23/22.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.23/22.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.23/22.17  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 32.89/33.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.89/33.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.89/33.35  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 43.63/43.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.63/43.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.63/43.88  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 47.50/48.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.50/48.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.50/48.56  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 58.50/59.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.50/59.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.50/59.67  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 69.67/71.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.67/71.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.67/71.15  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 80.50/82.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.50/82.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.50/82.27  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 94.28/96.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.28/96.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.28/96.50  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 151.70/149.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 151.70/149.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 151.70/149.25  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 151.77/149.52  Timeout
%------------------------------------------------------------------------------