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

% Computer : n026.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:37 EDT 2023

% Result   : Unknown 150.71s 150.12s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.05/0.14  % Problem  : CSR102+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.13/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.36  % Computer : n026.cluster.edu
% 0.14/0.36  % Model    : x86_64 x86_64
% 0.14/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36  % Memory   : 8042.1875MB
% 0.14/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36  % CPULimit : 300
% 0.14/0.36  % WCLimit  : 300
% 0.14/0.36  % DateTime : Fri May 19 01:04:05 EDT 2023
% 0.14/0.36  % CPUTime  : 
% 11.65/11.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.65/11.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.65/11.38  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 23.00/22.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.00/22.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.00/22.70  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 34.26/34.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.26/34.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.26/34.01  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 45.25/45.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.25/45.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.25/45.25  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 49.51/50.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.51/50.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.51/50.15  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 60.27/60.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.27/60.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.27/60.60  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 71.42/71.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.42/71.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.42/71.37  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 82.67/82.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.67/82.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.67/82.85  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 97.15/97.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.15/97.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.15/97.40  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 150.66/149.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 150.66/149.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 150.66/149.33  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 150.71/150.12  Timeout
%------------------------------------------------------------------------------