08-26-2008 01:00 AM
If your desktop hardware includes a graphics processing unit (GPU), you can do some cool image processing with the CVL suite of tools, which includes in image viewer, an image tone mapper, and a command-line tool for non-interactive image processing.
Hi All
I'm find out a way to disable the DGD: AMD Radeon HD 7470M on my Ubutu 16.04.2 LTS because radeon open source module is not capable to support this GPU and consequence the boot is very slow.
I have tried serveral way with pci-stub.ids in the grub menu but not work.
In general how... (11 Replies)
In one of our computers a Zotac GPU was installed (Zotac GeForce GTX 780 3GB AMP! to be exact) and the processor remained an Intel Core i7 2600. For the processor a new after-market cooler was installed and for the GPU also, together with fans on all case grids.
Initially the temperatures as... (4 Replies)
Ultimately, I'm looking to create a script that allows me to plug in a usb drive with lots of jpegs on it & copy them over to a folder on my hard drive. So in the process of copying I am looking to hash check them, record dupes to a file, copy only 1 of the identical files (if it doesn't exsist... (1 Reply)
Dear all,
I set up a external Gforce GPU using the PE4H (Pcie passive adapter) from HWTOOLS.NET.
I'm able to add and remove the device doing
and
The point is the kernel does not initialized the device correctly.
Here is what dmesg gives after the scan:
lspci -t gives
and lspci... (2 Replies)
Hi ,
i want begin programming using CUDA
which enviroment can i get .I don't have desktop to buy GPU graphics card.
what should to do to get CUDA enviroment.
i'm thinking to buy desktop has this card or laptop (1 Reply)
Hello,
Can give me some tips to trace the GPU usage on a solaris8 update7 box?
I try to understand why a Cadcam app is so slow on my Solaris box compared to a win$ box. I guess it comes from the poor graphic card I have but i would like to emphasize it.
My bench is 150sec long on a Solaris... (0 Replies)
pfsouthdrhtml(1) General Commands Manual pfsouthdrhtml(1)NAME
pfsouthdrhtml - Create a web page with an HDR viewer
SYNOPSIS
pfsouthdrhtml [<page_name>] [--quality <1-5>] [--image-dir <directory_name>] [--page-template <template_file>] [--image-template <tem-
plate_file>] [--object-output <file_name.js>] [--html-output <file_name.html>]
DESCRIPTION
The command creates in the current directory an HTML web page containing multi-exposure HDR viewer. The multi-exposure viewer displays a
portion of the available dynamic range with minimum contrast distortions and provides a slider control to move the dynamic range window
towards brighter or darker tones. The interface is very similar to pfsview, which is a pfstools application for displaying HDR images. The
web page employs only JavaScript and CSS opacity property and does not require Java applets or the Flash plugin. Note that because this
techniques encodes 20-60 exposures using only few images, the displayed exposures may not be identical to the exposures that are shown in
pfsview. For examples and more information, visit
http://pfstools.sourceforge.net/hdrhtml/.
<page_name> specifies the file name, of the web page to be generated. If <page_name> is missing, the file name of the first image with
.html extension will be used.
The command can take as input several images and put them all on the same web page. For each image, its file name (from the FILE_NAME tag
in the pfsstrem) without extension and a leading path will be used as a name for all JavaScript variables corresponding to that image. If
the filename contains illegal characters (such as space, '-', '[', etc), these will be converted to '_'.
--quality <1-5>, -q <1-5>
Quality of the interpolated exposures, from the worst (1) to the best (5). The default is 2, which is sufficient for most applica-
tions. Higher quality will introduce less distortions in the brightest and the darkest tones, but will also generate more images.
More images means that there is more data that needs to be transferred to the web-browser, making HDR viewer less responsive.
--image-dir <directory_name>, -d <directory_name>
Specify where to store the resulting image files. Links to images in HTML will be updated accordingly. This must be a relative path
and the directory must exist. Useful to avoid clutter in the current directory.
--page-template <template_file>, -p <directory_name>, --image-template <template_file>, -i <template_file>
Replaces the template files used to generate an HTML web page. The template files contain all HTML and JaveScript code with special
keywords (@keyword@) that are replaced with image specific data, such as width, height, image base name, etc. The default template
files can be found in INSTALL_DIR/share/pfstools/hdrhtml_*_templ.html. See TEMPLATE FILE FORMAT below more details.
--object-output <file_name.js>, -o <file_name.js>
Store JavaScript objects (hdr_<base_name>) associated with each image in a separate file. This is useful if you want to script cre-
ating HTML pages.
--html-output <file_name.html>, -l <file_name.html>
Store HTML code that shows HDRHTML viewer for each image in a separate file. This is useful if you want to script creating HTML
pages.
TEMPLATE FILE FORMAT
pfsouthdrhtml uses two template files hdrhtml_page_templ.html and hdrhtml_image_templ.html, located in INSTALL_DIR/share/pfstools/, to gen-
erate a web page with an HDR HTML viewer. The 'page' file contains the HTML of the entire web page and the 'image' file is used to paste a
viewer code for a single image. You can replace one or both these templates with your own using --page-template and --image-template
options.
Each template contains HTML code with additional keywords surrounded by @ marks (@keyword@), which are replaced with HDR HTML specific
code. Most of the keywords are self explanatory, therefore only the most important are described below.
@hdr_img_def@ JavaScript objects that must be put in the 'body'
section before any images. These define all the parameters needed to control HDR HTML viewer.
@cf_array_def@
Pre-computed array of opacity coefficients. The same array is used for all images that use the same quality setting. Currently only
one such array could be used per web-page, so images generated with different quality setting cannot be mixed on a single web page.
@image_htmlcode@ or @image_htmlcode[base_name]@
Inserts HTML code of all images or a single image with the base_name (name with no file extension) specified as a parameter. This
should be put where HDR HTML viewer should be located.
EXAMPLES
pfsin memorial.hdr | pfshdrhtml memorial_church
Generates a web page memorial_church.html with a set of images memorial_church_*.jpg in the current directory.
pfsin ~/hdr_images/*.exr | pfssize --maxx 512 --maxy 512 | pfsouthdrhtml hdr_images
Generate a web page with all OpenEXR images from ~/hdr_images/. The images are resized so that they are not larger than 512x512.
SEE ALSO pfsin(1)pfsout(1)BUGS
Please report bugs and comments to the discussion group http://groups.google.com/group/pfstools
pfsouthdrhtml(1)