↑ Up

nanoCoP---2.0.UNK-Non.f

View TPTP
Problem
Process solution in
SystemOnTSTP
Download .tgz
%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : TOP035+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n025.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 12:39:07 EDT 2023

% Result   : Unknown 98.00s 102.00s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12  % Problem  : TOP035+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n025.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Thu May 18 20:13:23 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 6.03/6.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.03/6.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.03/6.04  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.95/12.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.95/12.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.95/12.22  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.79/18.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.79/18.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.79/18.37  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.75/24.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.75/24.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.75/24.73  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.82/29.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.82/29.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.82/29.19  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.75/35.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.75/35.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.75/35.08  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.66/41.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.66/41.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.66/41.22  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.58/47.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.58/47.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.58/47.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.29/53.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.29/53.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.29/53.53  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.12/57.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.12/57.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.12/57.91  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.97/64.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.97/64.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.97/64.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.82/70.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.82/70.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.82/70.29  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.72/76.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.72/76.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.72/76.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.96/101.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.96/101.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.96/101.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.00/102.00  Timeout
%------------------------------------------------------------------------------