crazyseabiscuit / jfeaturelib Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/jfeaturelib
Automatically exported from code.google.com/p/jfeaturelib
Different feature descriptors are parameterized differently.
It would be nice to have a full Java based API for settings parameters.
Some examples:
PHOG has Setters for bins and recursions, but not for canny.
setGradientSource seems to be a bit odd. There is an initial value, but after
the first run() it becomes null, making the feature descriptor somewhat
non-reentrant.
AutoColorCorrelogram on the other hand apparently cannot be configured at all
from Java, but only via properties, meaning you can't use different
parameterizations in the same run if you want to compare them.
Original issue reported on code.google.com by [email protected]
on 13 Feb 2013 at 5:16
The Haralick implementation is missing Feature 14 (Maximal Correlation
Coefficient).
See:
Haralick, Shanmugam, Dinstein. Textural Features for Image Classification.
1973. Page 10.
Original issue reported on code.google.com by [email protected]
on 10 May 2012 at 8:55
Catch Exception w/out logging or rethrowing in
/trunk/src/de/lmu/dbs/jfeaturelib/ThreadWrapper.java
de.lmu.dbs.jfeaturelib.ThreadWrapper
catch(InstantiationException | IllegalAccessException e){
//FIXME Fix this or little kittens will die!
System.out.println("Error during instantiation");
e.printStackTrace();
}
Log Exception and throw an InvalidStateException
Original issue reported on code.google.com by franz.graf
on 14 Nov 2011 at 8:10
provide simple tests for all features and - if possible also some sanity checks
Original issue reported on code.google.com by franz.graf
on 25 May 2012 at 8:26
PHOG sets the SUPPORTS_MASKING enum but in L.117ff there is no check accordig
to the masks.
I dare say that PHOG actually dows NOT support masking.
Original issue reported on code.google.com by franz.graf
on 22 Oct 2012 at 8:12
Please, report which descriptors are able to work with binary masks.
Currently, the only way to know whether a descriptor supports a mask or not is
if you look at the source code.
A wiki page could be provided to describe which descriptors support masks and
which don't.
Original issue reported on code.google.com by [email protected]
on 25 Oct 2012 at 5:54
This issue was created by revision r230.
The detector should be refactored to work on graylevel images as it converts
color images to grays in the code anyways
Original issue reported on code.google.com by `` on 3 Jan 2012 at 7:06
The shape descriptors only accept binarized images.
It should be thought about changing it to Supports.BINARY (which must be
introduced)
Maybe it should be thought about pulling the automatic-conversion out of the
extractors into a separate class.
Original issue reported on code.google.com by franz.graf
on 14 Feb 2013 at 7:17
It would be great if the Extractor utility could accept binary masks to extract
image features. Maybe adding a new parameter to indicate the directory
containing corresponding masks to those images inside the image directory.
Best regards,
Patrícia.
Original issue reported on code.google.com by [email protected]
on 22 Oct 2012 at 7:14
This issue was created by revision r236.
This is a minor performance issue.
By using a 3x3 kernel, imageJ's methods can be used directly.
Can be replaced with a more efficient implementation
Original issue reported on code.google.com by `` on 3 Jan 2012 at 7:37
This issue was created by revision r308.
beautify/test cleanup Method Kernel.process()
Original issue reported on code.google.com by franz.graf
on 21 May 2012 at 8:30
currently the LibProperties can only be instanciated with a properties files.
This can lead to problems in some configuration.
A possibility to instanciate the LibProperties without file is appreciated
(also for testing)
Original issue reported on code.google.com by franz.graf
on 14 Feb 2013 at 7:09
CUrrently the shape descriptors accept several kinds of images yet they really
work only on binary images.
It should be checked if the application should be restricted to a ByteProcessor
or BinaryProcessor
* http://rsbweb.nih.gov/ij/developer/api/ij/process/BinaryProcessor.html
* http://rsbweb.nih.gov/ij/developer/api/ij/process/ByteProcessor.html
Original issue reported on code.google.com by franz.graf
on 29 Sep 2012 at 8:12
// mean values
for (int i = 0; i < NUM_GRAY_VALUES; i++) {
mu_x += i * p_x[i];
mu_y += i * p_y[i];
}
that doesn't compute the mean - and subsequently the variance is wrong as well
Original issue reported on code.google.com by franz.graf
on 13 May 2012 at 9:00
It has been reported that some shapre descriptors define the background as 0
some as -1.
This should be unified to 0.
Original issue reported on code.google.com by franz.graf
on 14 Feb 2013 at 7:20
SIFT currently needs the binary path in the constructor.
This parameter could be passed via JVM-Env. variable or global properties
Original issue reported on code.google.com by franz.graf
on 24 Nov 2011 at 1:00
Hi,
as stated in the mail, please move the featurecomparator and compare package to
your project as long as we don't have enough ppl to implement really a lot of
comparison techniques and distance metrics.
Original issue reported on code.google.com by franz.graf
on 9 Dec 2011 at 7:47
It would be easier if the canny edge detector was added to PHOG extraction
process. It could be called internally to do the PHOG extraction in only one
step.
Also, a validation check need to be done to accept only graylevel images. Or
even better to convert color images to grayscale automatically, as it is done
in PHOG algorithm (http://www.robots.ox.ac.uk/~vgg/research/caltech/phog.html)
Original issue reported on code.google.com by [email protected]
on 1 Oct 2012 at 2:09
This is in version 1.3.0
When I run PHOG on an image, the resulting feature is twice as large as it
should be, with the first half of the features equal to zero.
The reason for this is the following:
-- PHOG initializes the feature vector in the function 'void initFeature()'. initFeature computes the size of the final size of the feature vector (correctly) and then allocates memory for it (feature = new double[length];). These are all zero.
-- In 'void buildHistogramRecursively()', the feature vector is _appended_ to by the histogram data (feature = Arrays2.append(feature, histogram.getData());). This adds features to the end of the vector (after re-sizing it).
A solution is to change initFeature and set feature=new double[0].
Arrays2.append handles this case, and results in the correct size feature vector
Original issue reported on code.google.com by [email protected]
on 20 Feb 2013 at 8:04
Attached are (yet untested) classes for RGB/HSB Histograms that allow non
uniform splitting / sizing of the bins.
The content should/could be merged with
de.lmu.ifi.dbs.jfeaturelib.features.Histogram
Original issue reported on code.google.com by franz.graf
on 13 Feb 2013 at 7:02
Attachments:
From an HowTo's comment:
When I add JFeaturelib as a Maven dependency in Netbeans (7.3), this happens:
"Failed to read artifact descriptor for net.semanticmetadata:lire:jar:0.9.3:
Could not transfer artifact net.semanticmetadata:lire:pom:0.9.3 from/to lib
(file://${project.basedir}/lib): Repository path /lib does not exist, and
cannot be created"
Is this some internal local dependency? I actually do have a "lib" folder,
although it doesn't contain the lire pom/jar. I have lire available as a maven
dependency, but JFeaturelib appears to be looking for it in a very specific
place.
There should be a better solution for this.
Original issue reported on code.google.com by franz.graf
on 2 May 2013 at 8:05
There are some italian comments in harris corner detector
http://code.google.com/p/jfeaturelib/source/browse/trunk/src/de/lmu/dbs/jfeature
lib/pointDetector/Harris.java
which should be translated to english
Original issue reported on code.google.com by franz.graf
on 20 Dec 2011 at 11:39
The Extractor class currently only supports FeatureDescriptor s that live in the
de.lmu.ifi.dbs.jfeaturelib.features
package (or below).
It should support third-party packages, too, as long as they implement the
desired interface.
Original issue reported on code.google.com by [email protected]
on 14 Feb 2013 at 3:09
image class should not be required or at least use some reasonable defaults in
commandline extractor.
Wither set a default-class or try to ignore the class if no class is set.
Original issue reported on code.google.com by franz.graf
on 27 Sep 2012 at 9:00
The AutoColorCorrelogram feature does not seem to work:
Exception in thread "main" java.lang.NullPointerException
at net.semanticmetadata.lire.imageanalysis.AutoColorCorrelogram.extract(AutoColorCorrelogram.java:304)
at net.semanticmetadata.lire.imageanalysis.AutoColorCorrelogram.extract(AutoColorCorrelogram.java:230)
at de.lmu.ifi.dbs.jfeaturelib.features.AutoColorCorrelogram.run(AutoColorCorrelogram.java:62)
Maybe the bug is in lire, though.
Original issue reported on code.google.com by [email protected]
on 14 Feb 2013 at 9:50
This issue was created by revision r233.
The detector should be refactored to work on graylevel images as it converts
color images to grays in the code anyways
Original issue reported on code.google.com by `` on 3 Jan 2012 at 7:13
Sometimes I've got phog bins with zero values. I don't know if it is an error
in phog descriptor or not.
I'm using chi-square distance to measure the distance between two phog feature
vectors. Since this metric doesn't allow bins with zero values, it results with
error.
I attach an image (28.jpg) which I got this behaviour (phog.txt, see 24th bin).
Phog parameters are the deafults: bins=8 and recursions=1
I used the Extractor utility to extract phog features. My command line: java
-cp JfeatureLib.jar de.lmu.dbs.jfeaturelib.utils.Extractor -D PHOG -c c -d
/home/patricia/imgs/ -o phog.txt
Best regards,
Patricia
Original issue reported on code.google.com by [email protected]
on 31 Oct 2012 at 6:02
Attachments:
Color Correlograms might be easy and wellknown to implement.
Image Indexing Using Color Correlograms
@inproceedings{huang1997image,
title={Image indexing using color correlograms},
author={Huang, J. and Kumar, S.R. and Mitra, M. and Zhu, W.J. and Zabih, R.},
booktitle={Computer Vision and Pattern Recognition, 1997. Proceedings., 1997 IEEE Computer Society Conference on},
pages={762--768},
year={1997},
organization={IEEE}
}
Original issue reported on code.google.com by franz.graf
on 5 Nov 2012 at 5:48
Please remove the "Lire"-Prefix in the classes
LireCEDD
LireFCTH
LireFuzzy
LireGabor
LireJCD
LireTamura
Original issue reported on code.google.com by franz.graf
on 7 Dec 2011 at 3:02
Surafe Roughness Features
http://www.gcsca.net/IJ/SurfCharJ.html provides an ImageJ Plugin.
de.lmu.dbs.features.haralick.RoughnessCalculator might be an implementation.
Possibly a wrapper around the plugin is more appropriate.
Scientific publication:
Chinga, G., Gregersen, O., Dougherty, B.,
"Paper surface characterisation by laser profilometry and image analysis",
Journal of Microscopy and Analysis, July 2003.
Original issue reported on code.google.com by franz.graf
on 13 Jul 2011 at 8:34
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.