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

% Computer : n007.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:41 EDT 2023

% Result   : Unknown 155.79s 156.04s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.11  % Problem  : CSR108+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.11  % Command  : nanocop.sh %s %d
% 0.11/0.33  % Computer : n007.cluster.edu
% 0.11/0.33  % Model    : x86_64 x86_64
% 0.11/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33  % Memory   : 8042.1875MB
% 0.11/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33  % CPULimit : 300
% 0.11/0.33  % WCLimit  : 300
% 0.11/0.33  % DateTime : Thu May 18 23:32:53 EDT 2023
% 0.11/0.33  % CPUTime  : 
% 12.91/12.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.91/12.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.91/12.68  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 26.42/25.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.42/25.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.42/25.83  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 39.51/38.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.51/38.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.51/38.80  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 50.54/50.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.54/50.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.54/50.41  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 54.98/55.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.98/55.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.98/55.32  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 66.00/66.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.00/66.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.00/66.88  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 77.10/78.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.10/78.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.10/78.38  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 88.41/89.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 88.41/89.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.41/89.98  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 102.17/103.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.17/103.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.17/103.82  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 155.75/155.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 155.75/155.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 155.75/155.47  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 155.79/156.04  Timeout
%------------------------------------------------------------------------------