Hi
I run weka jobs from command line or batch files on ubuntu.
Even after the job's saved the learned model it keeps on using CPU and memory as if it was still working, this can take even hours before it closes. (the process still has its PID and the resources consumed are the same as before the model was built)
I also use -v -o params to suppress any other output.This is happening regardless what model I train or regardless complexity of model and filter nesting used.
Whats the problem? Or is there a way to force it to stop after model is serialized/ stored (using -d)?
I am using:
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Weka 3.6.1
thx
f
I run weka jobs from command line or batch files on ubuntu.
Even after the job's saved the learned model it keeps on using CPU and memory as if it was still working, this can take even hours before it closes. (the process still has its PID and the resources consumed are the same as before the model was built)
I also use -v -o params to suppress any other output.This is happening regardless what model I train or regardless complexity of model and filter nesting used.
Whats the problem? Or is there a way to force it to stop after model is serialized/ stored (using -d)?
I am using:
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Weka 3.6.1
thx
f