1 | initial version |
known bug
2 | No.2 Revision |
known bug , unfortunately no way to do so without falling back to JNI
3 | No.3 Revision |
known bug , unfortunately no way to do so without falling back to JNIJNI.
you'll have to create a new EM instance with: : Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code
4 | No.4 Revision |
known bug , unfortunately no way to do so without falling back to JNI.
you'll have to create a new EM instance with: :
Ptr<ml::EM> em =
Algorithm::load<ml::EM>(filename);Algorithm::load<ml::EM>(filename);
and return that to your java code
5 | No.5 Revision |
known bug , unfortunately no way to do so without falling back to JNI.
you'll have to create a new EM instance with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument properly)
6 | No.6 Revision |
known bug , unfortunately no way to do so without falling back to JNI.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument properly)
7 | No.7 Revision |
known bug , unfortunately no way to do so without falling back to JNI.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java codecode like:
return (jlong)(new Ptr<ml::EM>(em));
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument properly)
8 | No.8 Revision |
that's a known bug , unfortunately no way to do so without falling back to JNI.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument properly)
9 | No.9 Revision |
that's a known bug , unfortunately no way to do so without falling back to JNI.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
yes, it has to be wrapped into a 2nd Ptr to keep the refcounts proper ;(
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument properly)
10 | No.10 Revision |
that's a known bug , for now, unfortunately there's no way to do so without falling back to JNI.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
yes, it has to be wrapped into a 2nd Ptr to keep the refcounts proper ;(
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument properly)
11 | No.11 Revision |
that's a known bug , for now, unfortunately there's no way to do so without falling back to JNI.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
yes, it has to be wrapped into a 2nd Ptr to keep the refcounts proper ;(
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument properly)argument)
12 | No.12 Revision |
that's a known bug , for now, unfortunately there's no way to do so without falling back to JNI.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
yes, it has to be wrapped into a 2nd Ptr to keep the refcounts proper ;(
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument)argument at that stage)
13 | No.13 Revision |
that's a known bug , for now, unfortunately there's no way to do so without falling back to JNI.JNI/NDK.
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
yes, it has to be wrapped into a 2nd Ptr to keep the refcounts proper ;(
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument at that stage)
14 | No.14 Revision |
that's a known bug , for now, unfortunately there's no way to do so without falling back to JNI/NDK.JNI/NDK (the problem is not specific to EM, but applies to all the ml classes).
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
yes, it has to be wrapped into a 2nd Ptr to keep the refcounts proper ;(
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument at that stage)
15 | No.15 Revision |
that's a known bug , for now, unfortunately there's no way to do so without falling back to JNI/NDK (the problem is not even specific to EM, but applies to all the ml classes).
you'll have to create a new EM instance (in c++) with:
Ptr<ml::EM> em = Algorithm::load<ml::EM>(filename);
and return that to your java code like:
return (jlong)(new Ptr<ml::EM>(em));
yes, it has to be wrapped into a 2nd Ptr to keep the refcounts proper ;(
(and again, the problem with the script, that generates the java/python/matlab wrappers is, that it cannot deduce the template argument at that stage)