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

% Computer : n002.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:38 EDT 2023

% Result   : Unknown 147.80s 147.77s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.13  % Problem  : CSR103+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n002.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Fri May 19 00:03:50 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 10.85/10.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.85/10.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.85/10.72  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 21.57/22.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.57/22.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.57/22.01  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 32.36/32.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.36/32.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.36/32.46  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 43.15/42.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.15/42.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.15/42.84  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 47.36/46.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.36/46.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.36/46.95  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 58.40/57.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.40/57.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.40/57.57  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 69.35/68.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.35/68.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.35/68.88  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 80.22/80.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.22/80.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.22/80.23  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 94.19/94.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.19/94.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.19/94.77  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 147.70/147.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 147.70/147.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.70/147.04  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 147.80/147.77  Timeout
%------------------------------------------------------------------------------