ImageThemeFilter

所属分类:图形图像处理
开发工具:Visual C++
文件大小:9265KB
下载次数:106
上传日期:2010-04-12 15:00:21
上 传 者andersen_liu
说明:  对图像进行分主题过滤。 根据给定的图像样本集,进行样本训练,提取多个颜色空间中的多种方式(颜色矩,纹理谱,直方图,肤色模型等)的得到图像特征集;对待过滤图像进行特征提取,向量匹配,进而实现图像分主题分类功能。
(Sub-theme of the image filter. According to a given set of image samples to conduct the training samples to extract more color space in multiple ways (color moments, texture spectrum, histogram, color model, etc.) are image feature set treatment filters for feature extraction, vector match, then the sub-theme classification of image features.)

文件列表:
图像过滤器\CDIB.CPP (5971, 2007-11-27)
图像过滤器\Cdib.h (924, 2007-11-23)
图像过滤器\CmdQueBuf.cpp (3396, 2007-06-20)
图像过滤器\CmdQueBuf.h (1227, 2005-10-24)
图像过滤器\ColorSpaceDlg.cpp (1857, 2007-09-30)
图像过滤器\ColorSpaceDlg.h (1397, 2007-09-30)
图像过滤器\Debug\ImageFigure_EdgeDetect.txt (8213280, 2007-12-07)
图像过滤器\Debug\ImageMatchResult.txt (0, 2008-01-17)
图像过滤器\Debug\ImageOutputResult.txt (0, 2007-11-19)
图像过滤器\Debug\ImageVector.txt (0, 2010-04-12)
图像过滤器\Debug\Pic.bsc (2925568, 2007-06-04)
图像过滤器\Debug\Pic.exe (1048634, 2010-04-12)
图像过滤器\Debug\Pic.ilk (1072724, 2010-04-12)
图像过滤器\Debug\Pic.pch (6169024, 2010-04-12)
图像过滤器\Debug\Pic.pdb (2106368, 2010-04-12)
图像过滤器\Debug\Pic.res (14852, 2008-01-16)
图像过滤器\Debug\systemconfig.ini (320, 2010-04-12)
图像过滤器\Debug\themeclassify.txt (27, 2010-04-12)
图像过滤器\Debug\themefolderlist.txt (60, 2010-04-12)
图像过滤器\Debug\vc60.idb (492544, 2010-04-12)
图像过滤器\Debug\vc60.pdb (577536, 2010-04-12)
图像过滤器\Debug\vector_temp.txt (6872, 2008-01-17)
图像过滤器\Debug\vector_temp.vec (6872, 2008-01-17)
图像过滤器\FilterModeDlg.cpp (2364, 2007-10-09)
图像过滤器\FilterModeDlg.h (1543, 2007-09-29)
图像过滤器\FTSClient.dll (135168, 2006-05-19)
图像过滤器\FTSClient.h (97781, 2007-09-14)
图像过滤器\FTSClient.lib (60522, 2006-03-15)
图像过滤器\HistogramDib.cpp (43572, 2007-11-22)
图像过滤器\HistogramDib.h (3294, 2007-11-22)
图像过滤器\HistRGBDlg.cpp (5646, 2007-12-10)
图像过滤器\HistRGBDlg.h (1516, 2007-12-10)
图像过滤器\hsapidef.h (16882, 2006-08-16)
图像过滤器\Image.cpp (11182, 2007-06-20)
图像过滤器\Image.h (2054, 2007-06-11)
图像过滤器\ImageAdjust.cpp (3311, 1998-05-21)
图像过滤器\ImageAdjust.h (955, 2007-06-11)
图像过滤器\ImageFileBmp.cpp (2913, 2006-02-25)
图像过滤器\ImageFileGif.cpp (30761, 2007-11-08)
图像过滤器\ImageFileGif.h (3673, 1997-07-24)
... ...

$Header: /usr/people/sam/tiff/libtiff/RCS/README,v 1.19 1994/07/26 16:48:07 sam Exp $ # # Tag Image File Format Library # # Copyright (c) 1***8, 1***9, 1990, 1991, 1992, 1993, 1994 Sam Leffler # Copyright (c) 1991, 1992, 1993, 1994 Silicon Graphics, Inc. # # Permission to use, copy, modify, distribute, and sell this software and # its documentation for any purpose is hereby granted without fee, provided # that (i) the above copyright notices and this permission notice appear in # all copies of the software and related documentation, and (ii) the names of # Sam Leffler and Silicon Graphics may not be used in any advertising or # publicity relating to the software without the specific, prior written # permission of Sam Leffler and Silicon Graphics. # # THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, # EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY # WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. # # IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR # ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, # OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, # WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF # LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE # OF THIS SOFTWARE. # Configuration Comments: ---------------------- Aside from the compression algorithm support, there are configuration-related defines that you can override in the Makefile or in the default configuration file tiffconf.h: COLORIMETRY_SUPPORT if this is defined, support for the colorimetry tags will be compiled in. JPEG_SUPPORT if this is defined, support for the JPEG-related tags will be compiled in. Note that at the present time the JPEG compression support is not included. YCBCR_SUPPORT if this is defined, support for the YCbCr-related tags will be compiled in. Note that you'll want YCBCR support for JPEG compression+decompression. CMYK_SUPPORT if this is defined, support for the CMYK-related tags will be compiled in. MMAP_SUPPORT if this is set, and OS support exists for memory mapping files, then the library will try to map a file if it is opened for reading. If mmap does not exist on your system, or the mmap call fails on the file, then the normal read system calls are used. It is not clear how useful this facility is. By default tiffconf.h defines COLORIMETRY_SUPPORT, JPEG_SUPPORT, YCBCR_SUPPORT, CMYK_SUPPORT. MMAP_SUPPORT is not defined. General Portability Comments: ---------------------------- I run this code on SGI machines (big-endian, MIPS CPU, 32-bit ints, IEEE floating point). Makefiles exist for other platforms that the code runs on -- this work has mostly been done by other people. The code runs on Macintosh and PC-based systems, although I don't know all the particulars. In general, I promise only that the code runs on SGI machines. I will, however, gladly take back fixes to make it work on other systems -- when the changes are reasonable unobtrusive. The software is written to assume an ANSI C compilation environment. If your compiler does not support ANSI function prototypes, const, and then you will have to make modifications to the software. In the past I have tried to support compilers w/o const and systems w/o , but I am NO LONGER INTERESTED in these antiquated environments. With the general availability of gcc, I see no reason to incorporate modifications to the software for these purposes. I've tried to isolate as many of the OS-dependencies as possible in two files: tiffcomp.h and tif_.c. The latter file contains OS-specific routines to do I/O and I/O-related operations. The UNIX (tif_unix.c), Macintosh (tif_apple.c), and VMS (tif_vms.c) code has had the most use; the MS/DOS support (tif_msdos.c) assumes some level of UNIX system call emulation (i.e. open, read, write, fstat, malloc, free). Machine dependencies such as byte order are determined on the fly and do not need to be specified. Two general portability-related defines are: BSDTYPES Define this if your system does NOT define the usual BSD typedefs: u_char, u_short, u_int, u_longs. HAVE_IEEEFP Define this as 0 or 1 according to the floating point format suported by the machine. If your machine does not support IEEE floating point then you will need to add support to tif_machdep.c to convert between the native format and IEEE format. Note that tiffcomp.h defines HAVE_IEEEFP to be 1 (BSDTYPES is not defined). Types and Portability: --------------------- The software makes extensive use of typedefs to promote portability. Two sets of typedefs are used, one for communication with clients of the library and one for internal data structures and parsing of the TIFF format. There are interactions between these two to be careful of, but for the most part you should be able to deal with portability purely by fiddling with the following machine-dependent typedefs: uint16 16-bit unsigned integer tiff.h int16 16-bit signed integer tiff.h uint32 32-bit unsigned integer tiff.h int32 32-bit signed integer tiff.h dblparam_t promoted type for floats tiffcomp.h (to clarify dblparam_t, it is the type that float parameters are promoted to when passed by value in a function call.) The following typedefs are used throughout the library and interfaces to refer to certain objects whose size is dependent on the TIFF image structure: typedef unsigned int ttag_t; directory tag typedef uint16 tdir_t; directory index typedef uint16 tsample_t; sample number typedef uint32 tstrip_t; strip number typedef uint32 ttile_t; tile number typedef int32 tsize_t; i/o size in bytes typedef void* tdata_t; image data ref typedef void* thandle_t; client data handle typedef int32 toff_t; file offset (should be off_t) typedef unsigned char* tidata_t;internal image data Note that tstrip_t, ttile_t, and tsize_t are constrained to be no more than 32-bit quantities by 32-bit fields they are stored in in the TIFF image. Likewise tsample_t is limited by the 16-bit field used to store the SamplesPerPixel tag. tdir_t constrains the maximum number of IFDs that may appear in an image and may be an arbitrary size (w/o penalty). ttag_t must be either int, unsigned int, pointer, or double because the library uses a varargs interface and ANSI restricts the type of the parameter before an ellipsis to be a promoted type. toff_t is defined as int32 because TIFF file offsets are (unsigned) 32-bit quantities. A signed value is used because some interfaces return -1 on error (sigh). Finally, note that tidata_t is used internally to the library to manipulate internal data. User-specified data references are passed as opaque handles and only cast at the lowest layers where their type is presumed. General Comments: ---------------- The library is designed to hide as much of the details of TIFF as possible. In particular, TIFF directories are read in their entirety into an internal format. Only the tags known by the library are available to a user and certain tag data may be maintained that a user doesn't care about (e.g. transfer function tables). To add support for a new directory tag the following mods are needed: 1. Define the tag in tiff.h. 2. Add a field to the directory structure in tiffiop.h and define a FIELD_* bit. 3. Add an entry in the FieldInfo array defined at the top of tiff_dirinfo.c. 4. Add entries in TIFFSetField1() and TIFFGetField1() for the new tag. 5. (optional) If the value associated with the tag is not a scalar value (e.g. the array for TransferFunction), then add the appropriate code to TIFFReadDirectory() and TIFFWriteDirectory(). You're best off finding a similar tag and cribbing code. 6. Add support to TIFFPrintDirectory() in tiff_print.c to print the tag's value. If you want to maintain portability, beware of making assumptions about data types. Use the typedefs (uint16, etc. when dealing with data on disk and t*_t when stuff is in memory) and be careful about passing items through printf or similar vararg interfaces. To add support for a compression algorithm: 1. Define the tag value in tiff.h. 2. Edit the file tiff_compress.c to add an entry to the CompressionSchemes[] array. 3. Create a file with the compression scheme code, by convention files are named tif_*.c (except perhaps on some systems where the tif_ prefix pushes some filenames over 14 chars. 4. Edit the Makefiles to include the new source file. A compression scheme, say foo, can have up to 10 entry points: TIFFfoo(tif) /* initialize scheme and setup entry points in tif */ fooPreDecode(tif) /* called once per strip, after data is read, but before the first row in a strip is decoded */ fooDecode*(tif, bp, cc, sample)/* decode cc bytes of data into the buffer */ fooDecodeRow(...) /* called to decode a single scanline */ fooDecodeStrip(...) /* called to decode an entire strip */ fooDecodeTile(...) /* called to decode an entire tile */ fooPreEncode(tif) /* called once per strip/tile, before the first row in a strip is encoded */ fooEncode*(tif, bp, cc, sample)/* encode cc bytes of user data (bp) */ fooEncodeRow(...) /* called to decode a single scanline */ fooEncodeStrip(...) /* called to decode an entire strip */ fooEncodeTile(...) /* called to decode an entire tile */ fooPostEncode(tif) /* called once per strip/tile, just before data is written */ fooSeek(tif, row) /* seek forwards row scanlines from the beginning of a strip (row will always be >0 and
近期下载者

相关文件


收藏者