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

% Computer : n004.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:39 EDT 2023

% Result   : Unknown 141.12s 141.72s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.13  % Problem  : CSR105+7 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.12/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.35  % Computer : n004.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 300
% 0.14/0.35  % DateTime : Thu May 18 23:39:54 EDT 2023
% 0.14/0.36  % CPUTime  : 
% 10.85/10.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.85/10.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.85/10.63  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 21.37/20.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.37/20.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.37/20.87  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 31.35/30.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.35/30.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.35/30.69  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.38/41.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.38/41.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.38/41.15  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 45.00/45.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.00/45.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.00/45.37  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 54.91/55.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.91/55.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.91/55.54  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 64.69/65.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.69/65.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.69/65.90  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 75.96/77.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 75.96/77.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 75.96/77.71  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 88.88/90.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 88.88/90.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.88/90.73  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 141.03/140.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 141.03/140.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 141.03/140.68  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 141.12/141.72  Timeout
%------------------------------------------------------------------------------