On Mar 6, 2021, at 4:09 PM, Tony D
Michael Hall wrote
> On Mar 2, 2021, at 10:55 AM, Tony D <
-n would also have to indicate where weka.jar is, since you don’t have a
new version jar to point to in this case
-t would be a training set to create a new model with the new jar on.
-d would be where to save the new model (destination?)
The final argument would be the existing model file.
So something like…
java -cp .:weka.jar WekaSerialConverter -n weka.jar -d newModel.m -t
So, me being a JavaNoob, I have placed copies of the WekaSerialConverter
everywhere I think might be in a path... no luck. Java can't find it. tried
to run from several directories - also no luck. I realize thisis a Java
specific thing... Feel free to point me at a ref guide (RTFM, Noob!) for
this part of the operation.
What I pointed you to was java source you would need to compile it to a class first with
javac -cp /where-ever/is/your/weka.jar WekaSerialConverter.java
Then run it with something like...
java -cp .:/where-ever/is/your/weka.jar WekaSerialConverter -n
/where-ever/is/your/weka.jar -d /where-ever/you/want/newModel.model -t /where-ever
You should only need it one place but the paths to the files need to be right. If you are
not familiar with command line or java this might not be something for you to try.
FYI - I also tried fracpete model viewer installed as a tab in Weka -
nothing happens when i try to open the model. no error - no nothing.
Again, errors probably would be in the weka.log. Unless the application catches them and
Searching weka.log for ‘exception' maybe if it’s too big to spot the stack traces, if
there is even a stack trace, I guess no guarantee.
But if the stack trace is there it would give us something to go on.
Or if you can attach or put the model file somewhere we could get at?