AutoWEKA on Windows

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

AutoWEKA on Windows

Alexander Osherenko
Hi,

There are many posts here that complain about not-working-AutoWEKA. Unfortunately, I also have problems with it. I am running Weka-3-8 on Win10.

I had the problem with evaluating classifier: null https://github.com/automl/autoweka/issues/31 . Then I installed Autoweka 2.2 from http://www.cs.ubc.ca/~larsko/autoweka.zip and have another problem -- AutoWEKA doesn't find java.exe.

D:\Program Files\Java\jdk1.8.0_111\bin>.\java -cp "d:/Program files/Weka-3-8/weka.jar" weka.Run .AutoWEKAClassifier -t "d:/Program files/Weka-3-8/data/iris.arff"
java.lang.Exception: Java executable could not be found. Please refer to "Known Issues" in the Auto-WEKA manual.
        at weka.classifiers.meta.AutoWEKAClassifier.buildClassifier(AutoWEKAClassifier.java:346)
        at weka.classifiers.evaluation.Evaluation.evaluateModel(Evaluation.java:1529)
        at weka.classifiers.Evaluation.evaluateModel(Evaluation.java:650)
        at weka.classifiers.AbstractClassifier.runClassifier(AbstractClassifier.java:141)
        at weka.classifiers.AbstractClassifier.run(AbstractClassifier.java:546)
        at weka.Run.main(Run.java:349)

I already adjusted the path but the exception is the same. I also copied the java.exe from JDK (java version "1.8.0_131", Java(TM) SE Runtime Environment (build 1.8.0_131-b11)). Also the same exception. I wonder where Weka searches for the java executable.

Best, Alexander
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Eibe Frank-2
Administrator
AutoWEKA appears to work fine for me on Windows 10 with WEKA 3.8.1. I’ve tried it both in the Explorer and from the command-line (using a command-line like yours, but with weka.jar in the current directory).

I’m using Oracle Java 1.8.0_131.

Entering

  where java

in the Windows console gives me

  C:\ProgramData\Oracle\Java\javapath\java.exe

This is a symlink to

  C:\Program Files\Java\jre1.8.0_131\bin\java.exe

Cheers,
Eibe

> On 31/05/2017, at 12:51 AM, Alexander Osherenko <[hidden email]> wrote:
>
> Hi,
>
> There are many posts here that complain about not-working-AutoWEKA.
> Unfortunately, I also have problems with it. I am running Weka-3-8 on Win10.
>
> I had the problem with evaluating classifier: null
> https://github.com/automl/autoweka/issues/31 . Then I installed Autoweka 2.2
> from http://www.cs.ubc.ca/~larsko/autoweka.zip and have another problem --
> AutoWEKA doesn't find java.exe.
>
> D:\Program Files\Java\jdk1.8.0_111\bin>.\java -cp "d:/Program
> files/Weka-3-8/weka.jar" weka.Run .AutoWEKAClassifier -t "d:/Program
> files/Weka-3-8/data/iris.arff"
> java.lang.Exception: Java executable could not be found. Please refer to
> "Known Issues" in the Auto-WEKA manual.
>        at
> weka.classifiers.meta.AutoWEKAClassifier.buildClassifier(AutoWEKAClassifier.java:346)
>        at
> weka.classifiers.evaluation.Evaluation.evaluateModel(Evaluation.java:1529)
>        at weka.classifiers.Evaluation.evaluateModel(Evaluation.java:650)
>        at
> weka.classifiers.AbstractClassifier.runClassifier(AbstractClassifier.java:141)
>        at
> weka.classifiers.AbstractClassifier.run(AbstractClassifier.java:546)
>        at weka.Run.main(Run.java:349)
>
> I already adjusted the path but the exception is the same. I also copied the
> java.exe from JDK (java version "1.8.0_131", Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)). Also the same exception. I wonder where Weka
> searches for the java executable.
>
> Best, Alexander
>
>
>
> --
> View this message in context: http://weka.8497.n7.nabble.com/AutoWEKA-on-Windows-tp40807.html
> Sent from the WEKA mailing list archive at Nabble.com.
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Alexander Osherenko
I have everything almost the same -- 
 C:\Program Files\Java\jre1.8.0_111\bin\java.exe and weka 3.8.1.

I assume the problem is not Autoweka, but localization in Weka. For example, I use German Win10 meaning that the the directory "Program files" 's name is Programme. I reinstalled Weka 3.8.1 and tried to start Weka from Windows menu -- however, the Windows console flashes, but Weka doesn't start.  I already know this problem but I didn't pay attention to it. If, however, I open the console, go to the Weka directory and start "RunWeka.bat" or "java -jar weka.jar" everything works very good (besides AutoWEKA, but it doesn' matter since the problem is probably the same -- java.exe can't start). I looked at the systeminfo -- java.home is there C:\Program Files\Java\jre1.8.0_111 not C:\Programme\Java\jre1.8.0_111. 

2017-05-31 4:37 GMT+01:00 Eibe Frank <[hidden email]>:
AutoWEKA appears to work fine for me on Windows 10 with WEKA 3.8.1. I’ve tried it both in the Explorer and from the command-line (using a command-line like yours, but with weka.jar in the current directory).

I’m using Oracle Java 1.8.0_131.

Entering

  where java

in the Windows console gives me

  C:\ProgramData\Oracle\Java\javapath\java.exe

This is a symlink to

 
​​
C:\Program Files\Java\jre1.8.0_131\bin\java.exe

Cheers,
Eibe

> On 31/05/2017, at 12:51 AM, Alexander Osherenko <[hidden email]> wrote:
>
> Hi,
>
> There are many posts here that complain about not-working-AutoWEKA.
> Unfortunately, I also have problems with it. I am running Weka-3-8 on Win10.
>
> I had the problem with evaluating classifier: null
> https://github.com/automl/autoweka/issues/31 . Then I installed Autoweka 2.2
> from http://www.cs.ubc.ca/~larsko/autoweka.zip and have another problem --
> AutoWEKA doesn't find java.exe.
>
> D:\Program Files\Java\jdk1.8.0_111\bin>.\java -cp "d:/Program
> files/Weka-3-8/weka.jar" weka.Run .AutoWEKAClassifier -t "d:/Program
> files/Weka-3-8/data/iris.arff"
> java.lang.Exception: Java executable could not be found. Please refer to
> "Known Issues" in the Auto-WEKA manual.
>        at
> weka.classifiers.meta.AutoWEKAClassifier.buildClassifier(AutoWEKAClassifier.java:346)
>        at
> weka.classifiers.evaluation.Evaluation.evaluateModel(Evaluation.java:1529)
>        at weka.classifiers.Evaluation.evaluateModel(Evaluation.java:650)
>        at
> weka.classifiers.AbstractClassifier.runClassifier(AbstractClassifier.java:141)
>        at
> weka.classifiers.AbstractClassifier.run(AbstractClassifier.java:546)
>        at weka.Run.main(Run.java:349)
>
> I already adjusted the path but the exception is the same. I also copied the
> java.exe from JDK (java version "1.8.0_131", Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)). Also the same exception. I wonder where Weka
> searches for the java executable.
>
> Best, Alexander
>
>
>
> --
> View this message in context: http://weka.8497.n7.nabble.com/AutoWEKA-on-Windows-tp40807.html
> Sent from the WEKA mailing list archive at Nabble.com.
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Eibe Frank-2
Administrator
Strange, never heard of this problem before. I did a quick grep for JAVA_HOME in WEKA's SVN trunk and there doesn’t seem to be any place where JAVA_HOME is set in WEKA.

Perhaps you just need to set the correct value for the JAVA_HOME environment variable yourself?

There is some info here:

http://www.torsten-horn.de/techdocs/java-install.htm

Cheers,
Eibe

> On 1/06/2017, at 12:13 AM, Alexander Osherenko <[hidden email]> wrote:
>
> I have everything almost the same -- ​ C:\Program Files\Java\jre1.8.0_111\bin\java.exe and weka 3.8.1.
>
> I assume the problem is not Autoweka, but localization in Weka. For example, I use German Win10 meaning that the the directory "Program files" 's name is Programme. I reinstalled Weka 3.8.1 and tried to start Weka from Windows menu -- however, the Windows console flashes, but Weka doesn't start.  I already know this problem but I didn't pay attention to it. If, however, I open the console, go to the Weka directory and start "RunWeka.bat" or "java -jar weka.jar" everything works very good (besides AutoWEKA, but it doesn' matter since the problem is probably the same -- java.exe can't start). I looked at the systeminfo -- java.home is there C:\Program Files\Java\jre1.8.0_111 not C:\Programme\Java\jre1.8.0_111.
>
> 2017-05-31 4:37 GMT+01:00 Eibe Frank <[hidden email]>:
> AutoWEKA appears to work fine for me on Windows 10 with WEKA 3.8.1. I’ve tried it both in the Explorer and from the command-line (using a command-line like yours, but with weka.jar in the current directory).
>
> I’m using Oracle Java 1.8.0_131.
>
> Entering
>
>   where java
>
> in the Windows console gives me
>
>   C:\ProgramData\Oracle\Java\javapath\java.exe
>
> This is a symlink to
>
>  ​​ C:\Program Files\Java\jre1.8.0_131\bin\java.exe
>
> Cheers,
> Eibe
>
> > On 31/05/2017, at 12:51 AM, Alexander Osherenko <[hidden email]> wrote:
> >
> > Hi,
> >
> > There are many posts here that complain about not-working-AutoWEKA.
> > Unfortunately, I also have problems with it. I am running Weka-3-8 on Win10.
> >
> > I had the problem with evaluating classifier: null
> > https://github.com/automl/autoweka/issues/31 . Then I installed Autoweka 2.2
> > from http://www.cs.ubc.ca/~larsko/autoweka.zip and have another problem --
> > AutoWEKA doesn't find java.exe.
> >
> > D:\Program Files\Java\jdk1.8.0_111\bin>.\java -cp "d:/Program
> > files/Weka-3-8/weka.jar" weka.Run .AutoWEKAClassifier -t "d:/Program
> > files/Weka-3-8/data/iris.arff"
> > java.lang.Exception: Java executable could not be found. Please refer to
> > "Known Issues" in the Auto-WEKA manual.
> >        at
> > weka.classifiers.meta.AutoWEKAClassifier.buildClassifier(AutoWEKAClassifier.java:346)
> >        at
> > weka.classifiers.evaluation.Evaluation.evaluateModel(Evaluation.java:1529)
> >        at weka.classifiers.Evaluation.evaluateModel(Evaluation.java:650)
> >        at
> > weka.classifiers.AbstractClassifier.runClassifier(AbstractClassifier.java:141)
> >        at
> > weka.classifiers.AbstractClassifier.run(AbstractClassifier.java:546)
> >        at weka.Run.main(Run.java:349)
> >
> > I already adjusted the path but the exception is the same. I also copied the
> > java.exe from JDK (java version "1.8.0_131", Java(TM) SE Runtime Environment
> > (build 1.8.0_131-b11)). Also the same exception. I wonder where Weka
> > searches for the java executable.
> >
> > Best, Alexander
> >
> >
> >
> > --
> > View this message in context: http://weka.8497.n7.nabble.com/AutoWEKA-on-Windows-tp40807.html
> > Sent from the WEKA mailing list archive at Nabble.com.
> > _______________________________________________
> > Wekalist mailing list
> > Send posts to: [hidden email]
> > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Alexander Osherenko
It becomes stranger. Now I deinstalled exising jdks and javas and installed weka-3.8.1.exe and jdk-7u80-windows-i586.exe both on XP and Win10. The JAVA_HOME variable is not necessary in both cases. The difference is: Weka runs only on XP successfully both from the Windows menu and console (java -jar weka.jar); on Win10 only from the console.

​Best, Alexander

2017-05-31 23:31 GMT+01:00 Eibe Frank <[hidden email]>:
Strange, never heard of this problem before. I did a quick grep for JAVA_HOME in WEKA's SVN trunk and there doesn’t seem to be any place where JAVA_HOME is set in WEKA.

Perhaps you just need to set the correct value for the JAVA_HOME environment variable yourself?

There is some info here:

http://www.torsten-horn.de/techdocs/java-install.htm

Cheers,
Eibe

> On 1/06/2017, at 12:13 AM, Alexander Osherenko <[hidden email]> wrote:
>
> I have everything almost the same -- ​ C:\Program Files\Java\jre1.8.0_111\bin\java.exe and weka 3.8.1.
>
> I assume the problem is not Autoweka, but localization in Weka. For example, I use German Win10 meaning that the the directory "Program files" 's name is Programme. I reinstalled Weka 3.8.1 and tried to start Weka from Windows menu -- however, the Windows console flashes, but Weka doesn't start.  I already know this problem but I didn't pay attention to it. If, however, I open the console, go to the Weka directory and start "RunWeka.bat" or "java -jar weka.jar" everything works very good (besides AutoWEKA, but it doesn' matter since the problem is probably the same -- java.exe can't start). I looked at the systeminfo -- java.home is there C:\Program Files\Java\jre1.8.0_111 not C:\Programme\Java\jre1.8.0_111.
>
> 2017-05-31 4:37 GMT+01:00 Eibe Frank <[hidden email]>:
> AutoWEKA appears to work fine for me on Windows 10 with WEKA 3.8.1. I’ve tried it both in the Explorer and from the command-line (using a command-line like yours, but with weka.jar in the current directory).
>
> I’m using Oracle Java 1.8.0_131.
>
> Entering
>
>   where java
>
> in the Windows console gives me
>
>   C:\ProgramData\Oracle\Java\javapath\java.exe
>
> This is a symlink to
>
>  ​​ C:\Program Files\Java\jre1.8.0_131\bin\java.exe
>
> Cheers,
> Eibe
>
> > On 31/05/2017, at 12:51 AM, Alexander Osherenko <[hidden email]> wrote:
> >
> > Hi,
> >
> > There are many posts here that complain about not-working-AutoWEKA.
> > Unfortunately, I also have problems with it. I am running Weka-3-8 on Win10.
> >
> > I had the problem with evaluating classifier: null
> > https://github.com/automl/autoweka/issues/31 . Then I installed Autoweka 2.2
> > from http://www.cs.ubc.ca/~larsko/autoweka.zip and have another problem --
> > AutoWEKA doesn't find java.exe.
> >
> > D:\Program Files\Java\jdk1.8.0_111\bin>.\java -cp "d:/Program
> > files/Weka-3-8/weka.jar" weka.Run .AutoWEKAClassifier -t "d:/Program
> > files/Weka-3-8/data/iris.arff"
> > java.lang.Exception: Java executable could not be found. Please refer to
> > "Known Issues" in the Auto-WEKA manual.
> >        at
> > weka.classifiers.meta.AutoWEKAClassifier.buildClassifier(AutoWEKAClassifier.java:346)
> >        at
> > weka.classifiers.evaluation.Evaluation.evaluateModel(Evaluation.java:1529)
> >        at weka.classifiers.Evaluation.evaluateModel(Evaluation.java:650)
> >        at
> > weka.classifiers.AbstractClassifier.runClassifier(AbstractClassifier.java:141)
> >        at
> > weka.classifiers.AbstractClassifier.run(AbstractClassifier.java:546)
> >        at weka.Run.main(Run.java:349)
> >
> > I already adjusted the path but the exception is the same. I also copied the
> > java.exe from JDK (java version "1.8.0_131", Java(TM) SE Runtime Environment
> > (build 1.8.0_131-b11)). Also the same exception. I wonder where Weka
> > searches for the java executable.
> >
> > Best, Alexander
> >
> >
> >
> > --
> > View this message in context: http://weka.8497.n7.nabble.com/AutoWEKA-on-Windows-tp40807.html
> > Sent from the WEKA mailing list archive at Nabble.com.
> > _______________________________________________
> > Wekalist mailing list
> > Send posts to: [hidden email]
> > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Alexander Osherenko
Just an idea. I found in the src of the Auto-WEKA package a method that could provide a hint of differences. If WEKA does the same (reads java.home to get the path to the java executable), it wouldn't probably find the executable in the English and the localized Windows.

    /**
     * Tries to get the full path to the Java Executable that we're running.
     *
     * @return The string describing the path to the executable.
     */
    public static String getJavaExecutable()
    {
        return System.getProperties().getProperty("java.home") + File.separator + "bin" + File.separator + "java";
    }


2017-06-01 10:50 GMT+01:00 Alexander Osherenko <[hidden email]>:
It becomes stranger. Now I deinstalled exising jdks and javas and installed weka-3.8.1.exe and jdk-7u80-windows-i586.exe both on XP and Win10. The JAVA_HOME variable is not necessary in both cases. The difference is: Weka runs only on XP successfully both from the Windows menu and console (java -jar weka.jar); on Win10 only from the console.

​Best, Alexander

2017-05-31 23:31 GMT+01:00 Eibe Frank <[hidden email]>:
Strange, never heard of this problem before. I did a quick grep for JAVA_HOME in WEKA's SVN trunk and there doesn’t seem to be any place where JAVA_HOME is set in WEKA.

Perhaps you just need to set the correct value for the JAVA_HOME environment variable yourself?

There is some info here:

http://www.torsten-horn.de/techdocs/java-install.htm

Cheers,
Eibe

> On 1/06/2017, at 12:13 AM, Alexander Osherenko <[hidden email]> wrote:
>
> I have everything almost the same -- ​ C:\Program Files\Java\jre1.8.0_111\bin\java.exe and weka 3.8.1.
>
> I assume the problem is not Autoweka, but localization in Weka. For example, I use German Win10 meaning that the the directory "Program files" 's name is Programme. I reinstalled Weka 3.8.1 and tried to start Weka from Windows menu -- however, the Windows console flashes, but Weka doesn't start.  I already know this problem but I didn't pay attention to it. If, however, I open the console, go to the Weka directory and start "RunWeka.bat" or "java -jar weka.jar" everything works very good (besides AutoWEKA, but it doesn' matter since the problem is probably the same -- java.exe can't start). I looked at the systeminfo -- java.home is there C:\Program Files\Java\jre1.8.0_111 not C:\Programme\Java\jre1.8.0_111.
>
> 2017-05-31 4:37 GMT+01:00 Eibe Frank <[hidden email]>:
> AutoWEKA appears to work fine for me on Windows 10 with WEKA 3.8.1. I’ve tried it both in the Explorer and from the command-line (using a command-line like yours, but with weka.jar in the current directory).
>
> I’m using Oracle Java 1.8.0_131.
>
> Entering
>
>   where java
>
> in the Windows console gives me
>
>   C:\ProgramData\Oracle\Java\javapath\java.exe
>
> This is a symlink to
>
>  ​​ C:\Program Files\Java\jre1.8.0_131\bin\java.exe
>
> Cheers,
> Eibe
>
> > On 31/05/2017, at 12:51 AM, Alexander Osherenko <[hidden email]> wrote:
> >
> > Hi,
> >
> > There are many posts here that complain about not-working-AutoWEKA.
> > Unfortunately, I also have problems with it. I am running Weka-3-8 on Win10.
> >
> > I had the problem with evaluating classifier: null
> > https://github.com/automl/autoweka/issues/31 . Then I installed Autoweka 2.2
> > from http://www.cs.ubc.ca/~larsko/autoweka.zip and have another problem --
> > AutoWEKA doesn't find java.exe.
> >
> > D:\Program Files\Java\jdk1.8.0_111\bin>.\java -cp "d:/Program
> > files/Weka-3-8/weka.jar" weka.Run .AutoWEKAClassifier -t "d:/Program
> > files/Weka-3-8/data/iris.arff"
> > java.lang.Exception: Java executable could not be found. Please refer to
> > "Known Issues" in the Auto-WEKA manual.
> >        at
> > weka.classifiers.meta.AutoWEKAClassifier.buildClassifier(AutoWEKAClassifier.java:346)
> >        at
> > weka.classifiers.evaluation.Evaluation.evaluateModel(Evaluation.java:1529)
> >        at weka.classifiers.Evaluation.evaluateModel(Evaluation.java:650)
> >        at
> > weka.classifiers.AbstractClassifier.runClassifier(AbstractClassifier.java:141)
> >        at
> > weka.classifiers.AbstractClassifier.run(AbstractClassifier.java:546)
> >        at weka.Run.main(Run.java:349)
> >
> > I already adjusted the path but the exception is the same. I also copied the
> > java.exe from JDK (java version "1.8.0_131", Java(TM) SE Runtime Environment
> > (build 1.8.0_131-b11)). Also the same exception. I wonder where Weka
> > searches for the java executable.
> >
> > Best, Alexander
> >
> >
> >
> > --
> > View this message in context: http://weka.8497.n7.nabble.com/AutoWEKA-on-Windows-tp40807.html
> > Sent from the WEKA mailing list archive at Nabble.com.
> > _______________________________________________
> > Wekalist mailing list
> > Send posts to: [hidden email]
> > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html



_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Eibe Frank-2
Administrator
But have you tried setting JAVA_HOME as an environment variable containing the appropriate location? My understanding (which might be wrong) is that everything should work fine if you specify the correct location in this environment variable.

Cheers,
Eibe

> On 2/06/2017, at 2:35 AM, Alexander Osherenko <[hidden email]> wrote:
>
> Just an idea. I found in the src of the Auto-WEKA package a method that could provide a hint of differences. If WEKA does the same (reads java.home to get the path to the java executable), it wouldn't probably find the executable in the English and the localized Windows.
>
>     /**
>      * Tries to get the full path to the Java Executable that we're running.
>      *
>      * @return The string describing the path to the executable.
>      */
>     public static String getJavaExecutable()
>     {
>         return System.getProperties().getProperty("java.home") + File.separator + "bin" + File.separator + "java";
>     }
>
>
> 2017-06-01 10:50 GMT+01:00 Alexander Osherenko <[hidden email]>:
> It becomes stranger. Now I deinstalled exising jdks and javas and installed weka-3.8.1.exe and jdk-7u80-windows-i586.exe both on XP and Win10. The JAVA_HOME variable is not necessary in both cases. The difference is: Weka runs only on XP successfully both from the Windows menu and console (java -jar weka.jar); on Win10 only from the console.
>
> ​Best, Alexander
> ​
> 2017-05-31 23:31 GMT+01:00 Eibe Frank <[hidden email]>:
> Strange, never heard of this problem before. I did a quick grep for JAVA_HOME in WEKA's SVN trunk and there doesn’t seem to be any place where JAVA_HOME is set in WEKA.
>
> Perhaps you just need to set the correct value for the JAVA_HOME environment variable yourself?
>
> There is some info here:
>
> http://www.torsten-horn.de/techdocs/java-install.htm
>
> Cheers,
> Eibe
>
> > On 1/06/2017, at 12:13 AM, Alexander Osherenko <[hidden email]> wrote:
> >
> > I have everything almost the same -- ​ C:\Program Files\Java\jre1.8.0_111\bin\java.exe and weka 3.8.1.
> >
> > I assume the problem is not Autoweka, but localization in Weka. For example, I use German Win10 meaning that the the directory "Program files" 's name is Programme. I reinstalled Weka 3.8.1 and tried to start Weka from Windows menu -- however, the Windows console flashes, but Weka doesn't start.  I already know this problem but I didn't pay attention to it. If, however, I open the console, go to the Weka directory and start "RunWeka.bat" or "java -jar weka.jar" everything works very good (besides AutoWEKA, but it doesn' matter since the problem is probably the same -- java.exe can't start). I looked at the systeminfo -- java.home is there C:\Program Files\Java\jre1.8.0_111 not C:\Programme\Java\jre1.8.0_111.
> >
> > 2017-05-31 4:37 GMT+01:00 Eibe Frank <[hidden email]>:
> > AutoWEKA appears to work fine for me on Windows 10 with WEKA 3.8.1. I’ve tried it both in the Explorer and from the command-line (using a command-line like yours, but with weka.jar in the current directory).
> >
> > I’m using Oracle Java 1.8.0_131.
> >
> > Entering
> >
> >   where java
> >
> > in the Windows console gives me
> >
> >   C:\ProgramData\Oracle\Java\javapath\java.exe
> >
> > This is a symlink to
> >
> >  ​​ C:\Program Files\Java\jre1.8.0_131\bin\java.exe
> >
> > Cheers,
> > Eibe
> >
> > > On 31/05/2017, at 12:51 AM, Alexander Osherenko <[hidden email]> wrote:
> > >
> > > Hi,
> > >
> > > There are many posts here that complain about not-working-AutoWEKA.
> > > Unfortunately, I also have problems with it. I am running Weka-3-8 on Win10.
> > >
> > > I had the problem with evaluating classifier: null
> > > https://github.com/automl/autoweka/issues/31 . Then I installed Autoweka 2.2
> > > from http://www.cs.ubc.ca/~larsko/autoweka.zip and have another problem --
> > > AutoWEKA doesn't find java.exe.
> > >
> > > D:\Program Files\Java\jdk1.8.0_111\bin>.\java -cp "d:/Program
> > > files/Weka-3-8/weka.jar" weka.Run .AutoWEKAClassifier -t "d:/Program
> > > files/Weka-3-8/data/iris.arff"
> > > java.lang.Exception: Java executable could not be found. Please refer to
> > > "Known Issues" in the Auto-WEKA manual.
> > >        at
> > > weka.classifiers.meta.AutoWEKAClassifier.buildClassifier(AutoWEKAClassifier.java:346)
> > >        at
> > > weka.classifiers.evaluation.Evaluation.evaluateModel(Evaluation.java:1529)
> > >        at weka.classifiers.Evaluation.evaluateModel(Evaluation.java:650)
> > >        at
> > > weka.classifiers.AbstractClassifier.runClassifier(AbstractClassifier.java:141)
> > >        at
> > > weka.classifiers.AbstractClassifier.run(AbstractClassifier.java:546)
> > >        at weka.Run.main(Run.java:349)
> > >
> > > I already adjusted the path but the exception is the same. I also copied the
> > > java.exe from JDK (java version "1.8.0_131", Java(TM) SE Runtime Environment
> > > (build 1.8.0_131-b11)). Also the same exception. I wonder where Weka
> > > searches for the java executable.
> > >
> > > Best, Alexander
> > >
> > >
> > >
> > > --
> > > View this message in context: http://weka.8497.n7.nabble.com/AutoWEKA-on-Windows-tp40807.html
> > > Sent from the WEKA mailing list archive at Nabble.com.
> > > _______________________________________________
> > > Wekalist mailing list
> > > Send posts to: [hidden email]
> > > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
> >
> > _______________________________________________
> > Wekalist mailing list
> > Send posts to: [hidden email]
> > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
> >
> > _______________________________________________
> > Wekalist mailing list
> > Send posts to: [hidden email]
> > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Michael Hall
In reply to this post by Alexander Osherenko
On Jun 1, 2017, at 9:35 AM, Alexander Osherenko <[hidden email]> wrote:

Just an idea. I found in the src of the Auto-WEKA package a method that could provide a hint of differences. If WEKA does the same (reads java.home to get the path to the java executable), it wouldn't probably find the executable in the English and the localized Windows.

    /**
     * Tries to get the full path to the Java Executable that we're running.
     *
     * @return The string describing the path to the executable.
     */
    public static String getJavaExecutable()
    {
        return System.getProperties().getProperty("java.home") + File.separator + "bin" + File.separator + "java”;

If you have any way to change the jvm launch parameters you could set java.home to your localized name there.
say for normal launch (I think, I don’t do it command line much)
java -D java.home=/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home HelloWorld
I would know how to change that for the Weka application on OS X but do not know how you could do it on Windows for the actual Weka application

Michael Hall




_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Eibe Frank-3
With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.

Cheers,
Eibe

On Fri, Jun 2, 2017 at 1:27 PM, Michael Hall <[hidden email]> wrote:
On Jun 1, 2017, at 9:35 AM, Alexander Osherenko <[hidden email]> wrote:

Just an idea. I found in the src of the Auto-WEKA package a method that could provide a hint of differences. If WEKA does the same (reads java.home to get the path to the java executable), it wouldn't probably find the executable in the English and the localized Windows.

    /**
     * Tries to get the full path to the Java Executable that we're running.
     *
     * @return The string describing the path to the executable.
     */
    public static String getJavaExecutable()
    {
        return System.getProperties().getProperty("java.home") + File.separator + "bin" + File.separator + "java”;

If you have any way to change the jvm launch parameters you could set java.home to your localized name there.
say for normal launch (I think, I don’t do it command line much)
java -D java.home=/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home HelloWorld
I would know how to change that for the Weka application on OS X but do not know how you could do it on Windows for the actual Weka application

Michael Hall




_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html



_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Michael Hall
> On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>
> With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.


I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.

I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.

The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.

For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.

Michael Hall


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Alexander Osherenko
I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.

Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?

2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
> On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>
> With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.


I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.

I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.

The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.

For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.

Michael Hall


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Michael Hall
On Jun 2, 2017, at 2:15 PM, Alexander Osherenko <[hidden email]> wrote:

I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further

he difference is: Weka runs only on XP successfully both from the Windows menu and console (java -jar weka.jar); on Win10 only from the console.

I’m sorry I missed that the discussion had switched from AutoWeka not working to Weka itself  on Win 10 not working?

Just an idea. I found in the src of the Auto-WEKA package a method that could provide a hint of differences.

Changing the java.home property might help Auto-Weka but it shouldn’t help Weka Explorer launch.

Maybe there is something in Weka log concerning why the application isn’t launching. That should be at…

${user.home}/wekafiles/weka.log

For whatever user.home is for you on Windows.

Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?

How are you comparing this for Win 10 when the application doesn’t launch? Again the java.home property shouldn’t help the Explorer application itself launch. I don’t know what the sun.java.command is, I don’t show it set for my own application on OS X.

Michael Hall




_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Eibe Frank-2
Administrator
In reply to this post by Alexander Osherenko
Try setting a new variable 

  _JAVA_OPTIONS

as a Windows environment variable and give it the value

  -Djava.home=...

Cheers,
Eibe



Sent from my iPad
On 3/06/2017, at 7:15 AM, Alexander Osherenko <[hidden email]> wrote:

I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.

Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?

2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
> On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>
> With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.


I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.

I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.

The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.

For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.

Michael Hall


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Alexander Osherenko
I wonder why you are talking about this variable. Is it the only way to set java.home variable in Weka or I can set it in RunWeka.bat?

​Cheers, Alexander

2017-06-02 23:10 GMT+01:00 Eibe Frank <[hidden email]>:
Try setting a new variable 

  _JAVA_OPTIONS

as a Windows environment variable and give it the value

  -Djava.home=...

Cheers,
Eibe



Sent from my iPad
On 3/06/2017, at 7:15 AM, Alexander Osherenko <[hidden email]> wrote:

I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.

Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?

2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
> On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>
> With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.


I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.

I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.

The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.

For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.

Michael Hall


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html



_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Eibe Frank-2
Administrator
Yes, modifying RunWeka.bat should work too.

The advantage of using an environment variable is that you won't have to fix this problem again when you install a different version of WEKA. Also, it works even if you don't have admin rights. A correct setting for JAVA_HOME may also be useful for other applications, so from that point of view it may also make sense to set this globally in an environment variable.

The advantage of using _JAVA_OPTIONS in particular is that any settings specified in this variable take precedence over other settings provided for the java command, see

https://stackoverflow.com/questions/28327620/difference-between-java-options-java-tool-options-and-java-opts

Cheers,
Eibe

> On 3 Jun 2017, at 16:08, Alexander Osherenko <[hidden email]> wrote:
>
> I wonder why you are talking about this variable. Is it the only way to set java.home variable in Weka or I can set it in RunWeka.bat?
>
> ​Cheers, Alexander
> ​
> 2017-06-02 23:10 GMT+01:00 Eibe Frank <[hidden email]>:
> Try setting a new variable
>
>   _JAVA_OPTIONS
>
> as a Windows environment variable and give it the value
>
>   -Djava.home=...
>
> Cheers,
> Eibe
>
>
>
> Sent from my iPad
> On 3/06/2017, at 7:15 AM, Alexander Osherenko <[hidden email]> wrote:
>
>> I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.
>>
>> Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?
>>
>> 2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
>> > On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>> >
>> > With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.
>>
>>
>> I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.
>>
>> I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.
>>
>> The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.
>>
>> For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.
>>
>> Michael Hall
>>
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Fwd: AutoWEKA on Windows

Alexander Osherenko
In reply to this post by Michael Hall

On Jun 2, 2017, at 2:15 PM, Alexander Osherenko <[hidden email]> wrote:

I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further

he difference is: Weka runs only on XP successfully both from the Windows menu and console (java -jar weka.jar); on Win10 only from the console.

I’m sorry I missed that the discussion had switched from AutoWeka not working to Weka itself  on Win 10 not working?
The problem is: ​I installed java, update 80 and Weka 3.8.1 on two OS: XP and Win10. Although the installations should be identical, something is wrong. On XP, the installation works perfectly: I can start Weka from Windows menu and from the console. There are problems on Win10 -- I can only start Weka from the console (java -jar weka.jar), but not from the Windows menu.



Just an idea. I found in the src of the Auto-WEKA package a method that could provide a hint of differences.

Changing the java.home property might help Auto-Weka but it shouldn’t help Weka Explorer launch.

Maybe there is something in Weka log concerning why the application isn’t launching. That should be at…

${user.home}/wekafiles/weka.log

For whatever user.home is for you on Windows.
​There are no ​entries in this file concerning any errors. I don't think that Weka has the possibility to take control over execution since startup is aborted before, for example, because the weka.jar is not found.

 

Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?

How are you comparing this for Win 10 when the application doesn’t launch? Again the java.home property shouldn’t help the Explorer application itself launch. I don’t know what the sun.java.command is, I don’t show it set for my own application on OS X.
​I can start Weka on Win10 only from the console
(java -jar weka.jar)
​ that starts in Weka GUI chooser
.
​ ​
​In WekaGuiChooser
​,​
​I can choose the Help-Systeminfo command that shows
​a windows with ​
different variable
​s​
, for example
​, sun.java,command (
see snapshot)​

Inline-Bild 4

​However,
on Win10 the value of sun.java.command is weka.jar; on XP the value is weka.gui.GuiExplorer (or something like that).
​Best, Alexander​


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Alexander Osherenko
In reply to this post by Eibe Frank-2
Got it, thanx. It is also possible to set the sun.java.command in Systeminfo by setting
_JAVA_OPTIONS=-Dsun.java.command="dummy".

Best, Alexander

2017-06-03 5:44 GM
​​
T+01:00 Eibe Frank <[hidden email]>:
Yes, modifying RunWeka.bat should work too.

The advantage of using an environment variable is that you won't have to fix this problem again when you install a different version of WEKA. Also, it works even if you don't have admin rights. A correct setting for JAVA_HOME may also be useful for other applications, so from that point of view it may also make sense to set this globally in an environment variable.

The advantage of using _JAVA_OPTIONS in particular is that any settings specified in this variable take precedence over other settings provided for the java command, see

https://stackoverflow.com/questions/28327620/difference-between-java-options-java-tool-options-and-java-opts

Cheers,
Eibe

> On 3 Jun 2017, at 16:08, Alexander Osherenko <[hidden email]> wrote:
>
> I wonder why you are talking about this variable. Is it the only way to set java.home variable in Weka or I can set it in RunWeka.bat?
>
> ​Cheers, Alexander
> ​
> 2017-06-02 23:10 GMT+01:00 Eibe Frank <[hidden email]>:
> Try setting a new variable
>
>   _JAVA_OPTIONS
>
> as a Windows environment variable and give it the value
>
>   -Djava.home=...
>
> Cheers,
> Eibe
>
>
>
> Sent from my iPad
> On 3/06/2017, at 7:15 AM, Alexander Osherenko <[hidden email]> wrote:
>
>> I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.
>>
>> Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?
>>
>> 2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
>> > On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>> >
>> > With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.
>>
>>
>> I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.
>>
>> I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.
>>
>> The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.
>>
>> For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.
>>
>> Michael Hall
>>
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html


_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Alexander Osherenko
Is it possible to set several variables in JAVA_OPTIONS, for example,
to set _JAVA_OPTIONS to sun.java.command=var1 and java.home=var2?

If I specify string -Dsun.java.command=var1;java.home=var2it is not parsed correctly in Systeminfo.

Cheers, Alexander

2017-06-03 8:59 GMT+01:00 Alexander Osherenko <[hidden email]>:
Got it, thanx. It is also possible to set the sun.java.command in Systeminfo by setting
_JAVA_OPTIONS=-Dsun.java.command="dummy".

Best, Alexander

2017-06-03 5:44 GM
​​
T+01:00 Eibe Frank <[hidden email]>:

Yes, modifying RunWeka.bat should work too.

The advantage of using an environment variable is that you won't have to fix this problem again when you install a different version of WEKA. Also, it works even if you don't have admin rights. A correct setting for JAVA_HOME may also be useful for other applications, so from that point of view it may also make sense to set this globally in an environment variable.

The advantage of using _JAVA_OPTIONS in particular is that any settings specified in this variable take precedence over other settings provided for the java command, see

https://stackoverflow.com/questions/28327620/difference-between-java-options-java-tool-options-and-java-opts

Cheers,
Eibe

> On 3 Jun 2017, at 16:08, Alexander Osherenko <[hidden email]> wrote:
>
> I wonder why you are talking about this variable. Is it the only way to set java.home variable in Weka or I can set it in RunWeka.bat?
>
> ​Cheers, Alexander
> ​
> 2017-06-02 23:10 GMT+01:00 Eibe Frank <[hidden email]>:
> Try setting a new variable
>
>   _JAVA_OPTIONS
>
> as a Windows environment variable and give it the value
>
>   -Djava.home=...
>
> Cheers,
> Eibe
>
>
>
> Sent from my iPad
> On 3/06/2017, at 7:15 AM, Alexander Osherenko <[hidden email]> wrote:
>
>> I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.
>>
>> Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?
>>
>> 2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
>> > On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>> >
>> > With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.
>>
>>
>> I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.
>>
>> I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.
>>
>> The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.
>>
>> For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.
>>
>> Michael Hall
>>
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html



_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Peter Reutemann-3
On June 5, 2017 2:57:55 AM GMT+12:00, Alexander Osherenko <[hidden email]> wrote:
Is it possible to set several variables in JAVA_OPTIONS, for example,
to set _JAVA_OPTIONS to sun.java.command=var1 and java.home=var2?

If I specify string -Dsun.java.command=var1;java.home=var2it is not parsed correctly in Systeminfo.

Cheers, Alexander

2017-06-03 8:59 GMT+01:00 Alexander Osherenko <[hidden email]>:
Got it, thanx. It is also possible to set the sun.java.command in Systeminfo by setting
_JAVA_OPTIONS=-Dsun.java.command="dummy".

Best, Alexander

2017-06-03 5:44 GM
​​
T+01:00 Eibe Frank <[hidden email]>:

Yes, modifying RunWeka.bat should work too.

The advantage of using an environment variable is that you won't have to fix this problem again when you install a different version of WEKA. Also, it works even if you don't have admin rights. A correct setting for JAVA_HOME may also be useful for other applications, so from that point of view it may also make sense to set this globally in an environment variable.

The advantage of using _JAVA_OPTIONS in particular is that any settings specified in this variable take precedence over other settings provided for the java command, see

https://stackoverflow.com/questions/28327620/difference-between-java-options-java-tool-options-and-java-opts

Cheers,
Eibe

> On 3 Jun 2017, at 16:08, Alexander Osherenko <[hidden email]> wrote:
>
> I wonder why you are talking about this variable. Is it the only way to set java.home variable in Weka or I can set it in RunWeka.bat?
>
> ​Cheers, Alexander
> ​
> 2017-06-02 23:10 GMT+01:00 Eibe Frank <[hidden email]>:
> Try setting a new variable
>
>   _JAVA_OPTIONS
>
> as a Windows environment variable and give it the value
>
>   -Djava.home=...
>
> Cheers,
> Eibe
>
>
>
> Sent from my iPad
> On 3/06/2017, at 7:15 AM, Alexander Osherenko <[hidden email]> wrote:
>
>> I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.
>>
>> Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?
>>
>> 2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
>> > On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
>> >
>> > With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.
>>
>>
>> I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.
>>
>> I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.
>>
>> The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.
>>
>> For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.
>>
>> Michael Hall
>>
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>>
>> _______________________________________________
>> Wekalist mailing list
>> Send posts to: [hidden email]
>> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
>> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html



Separate the options with blanks instead of semicolons. This variable acts like a partial command-line string, which gets added to the actual command-line to start the jvm.

Cheers, Peter
--
Peter Reutemann
Dept. of Computer Science
University of Waikato, NZ
+64 (7) 858-5174
http://www.cms.waikato.ac.nz/~fracpete/
http://www.data-mining.co.nz
_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AutoWEKA on Windows

Eibe Frank-2
Administrator
Yes, on my Mac, the following works:

export _JAVA_OPTIONS="-Dsun.java.command=dummy -Djava.home=/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre"

Cheers,
Eibe

PS: Interestingly, I had to set -Djava.home to .../jre to make WEKA work, but the /jre part can be omitted when using the JAVA_HOME environment variable instead.


> On 5 Jun 2017, at 07:08, Peter Reutemann <[hidden email]> wrote:
>
> On June 5, 2017 2:57:55 AM GMT+12:00, Alexander Osherenko <[hidden email]> wrote:
> Is it possible to set several variables in JAVA_OPTIONS, for example,
> to set _JAVA_OPTIONS to sun.java.command=var1 and java.home=var2?
>
> If I specify string -Dsun.java.command=var1;java.home=var2, it is not parsed correctly in Systeminfo.
>
> Cheers, Alexander
>
> 2017-06-03 8:59 GMT+01:00 Alexander Osherenko <[hidden email]>:
> Got it, thanx. It is also possible to set the sun.java.command in Systeminfo by setting
> _JAVA_OPTIONS=-Dsun.java.command="dummy".
>
> Best, Alexander
>
> 2017-06-03 5:44 GM​​T+01:00 Eibe Frank <[hidden email]>:
>
> Yes, modifying RunWeka.bat should work too.
>
> The advantage of using an environment variable is that you won't have to fix this problem again when you install a different version of WEKA. Also, it works even if you don't have admin rights. A correct setting for JAVA_HOME may also be useful for other applications, so from that point of view it may also make sense to set this globally in an environment variable.
>
> The advantage of using _JAVA_OPTIONS in particular is that any settings specified in this variable take precedence over other settings provided for the java command, see
>
> https://stackoverflow.com/questions/28327620/difference-between-java-options-java-tool-options-and-java-opts
>
> Cheers,
> Eibe
>
> > On 3 Jun 2017, at 16:08, Alexander Osherenko <[hidden email]> wrote:
> >
> > I wonder why you are talking about this variable. Is it the only way to set java.home variable in Weka or I can set it in RunWeka.bat?
> >
> > ​Cheers, Alexander
> > ​
> > 2017-06-02 23:10 GMT+01:00 Eibe Frank <[hidden email]>:
> > Try setting a new variable
> >
> >   _JAVA_OPTIONS
> >
> > as a Windows environment variable and give it the value
> >
> >   -Djava.home=...
> >
> > Cheers,
> > Eibe
> >
> >
> >
> > Sent from my iPad
> > On 3/06/2017, at 7:15 AM, Alexander Osherenko <[hidden email]> wrote:
> >
> >> I tried to find the problem and didn't. Maybe you remember I have Weka 3-8-1 and AutoWEKA installed and they are running without any problems on XP. That's why I have to seek further.
> >>
> >> Let us please compare the settings in Weka Systeminfo. I found some differences, for example, in java.home and sun.java.command. Can I set these variables in RunWeka.bat?
> >>
> >> 2017-06-02 9:24 GMT+01:00 Michael Hall <[hidden email]>:
> >> > On Jun 1, 2017, at 8:48 PM, Eibe Frank <[hidden email]> wrote:
> >> >
> >> > With Oracle JVMs, you can use the _JAVA_OPTIONS environment variable to pass such command-line parameters to the JVM. This works on all platforms.
> >>
> >>
> >> I wasn’t aware of that one. It should work for this then, I would think. Unless Java itself sets java.home and overrides the one you specify.
> >>
> >> I didn’t entirely follow this thread and I am not sure why it is necessary. A jvm to run the application is obviously being found and if the same one is used to set the java.home property you would think AutoWeka would work with that? Possibly some localization issue as the original poster indicated. Then setting the property could work.
> >>
> >> The other possibility would be that it is the same situation as on OS X. For that the ‘java’ executable command is not included in the Weka application embedded jre. So AutoWeka can’t find it there and fails to Runtime exec java. I still believe this is the behavior of the appbundler version that is being used to create the application bundle. Probably just to save some space the executables are omitted. I also still think a fix there would be for whatever is used for the application build process to create a ‘bin' directory in the embedded jre and copy in the ‘java’ executable command. This did in fact work for me, doing it myself, to get AutoWeka going on OS X.
> >>
> >> For what this has to do with Windows, if you try to override java.home I would make sure you are pointing it at a jre/jdk that includes bin/java or bin/java.exe.
> >>
> >> Michael Hall
> >>
> >>
> >> _______________________________________________
> >> Wekalist mailing list
> >> Send posts to: [hidden email]
> >> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> >> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
> >>
> >> _______________________________________________
> >> Wekalist mailing list
> >> Send posts to: [hidden email]
> >> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> >> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
> >
> > _______________________________________________
> > Wekalist mailing list
> > Send posts to: [hidden email]
> > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
> >
> >
> > _______________________________________________
> > Wekalist mailing list
> > Send posts to: [hidden email]
> > List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> > List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
>
>
>
> Separate the options with blanks instead of semicolons. This variable acts like a partial command-line string, which gets added to the actual command-line to start the jvm.
>
> Cheers, Peter
> --
> Peter Reutemann
> Dept. of Computer Science
> University of Waikato, NZ
> +64 (7) 858-5174
> http://www.cms.waikato.ac.nz/~fracpete/
> http://www.data-mining.co.nz
> _______________________________________________
> Wekalist mailing list
> Send posts to: [hidden email]
> List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
> List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html

_______________________________________________
Wekalist mailing list
Send posts to: [hidden email]
List info and subscription status: https://list.waikato.ac.nz/mailman/listinfo/wekalist
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html
12
Loading...