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

% Computer : n009.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:32 EDT 2023

% Result   : Unknown 136.88s 137.61s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR094+7 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n009.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Fri May 19 00:17:02 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 9.93/9.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.93/9.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.93/9.74  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.88/20.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.88/20.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.88/20.23  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.73/30.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.73/30.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.73/30.54  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 39.33/40.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.33/40.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.33/40.81  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 42.79/44.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.79/44.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.79/44.12  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 52.87/54.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.87/54.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.87/54.70  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 62.64/64.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.64/64.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.64/64.77  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 72.13/74.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.13/74.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.13/74.88  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 85.03/87.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 85.03/87.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 85.03/87.55  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 136.80/137.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 136.80/137.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 136.80/137.27  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 136.88/137.61  Timeout
%------------------------------------------------------------------------------