Rapeseed Options Explained

Best Binary Options Brokers 2020:
  • Binarium

    The Best Binary Options Broker 2020!
    Perfect For Beginners and Middle-Leveled Traders!
    Free Demo Account!
    Free Trading Education!
    Get Your Sign-Up Bonus Now!

  • Binomo

    Good Broker For Experienced Traders!

Building from source : configure options explained

Packages ngs-sdk , ncbi-vdb , sra-tools have some unusual configure options.

Here we will try to explain them.

ncbi-vdb package depends on ngs-sdk , sra-tools – on ngs-sdk and ncbi-vdb .

ncbi-vdb should be able to find include files of ngs-sdk , sra-tools – ngs-sdk package and sources and build results of ncbi-vdb .

By default build output / build results of ngs / ncbi-vdb / sra-tools is created in

You can change it by using –build-prefix , but then – you should tell sra-tools where to find build results of ncbi-vdb .

Defaults: Standard / default / recommended location of source files

Default recommended locations of source files of ngs / ncbi-vdb / sra-tools is:

ngs / ncbi-vdb / sra-tools packages should be located in subdirectories named ngs , ncbi-vdb , sra-tools inside of the same directory.

Usually it is done automatically by running: git clone https://github.com/ncbi/ngs.git ; git clone https://github.com/ncbi/ncbi-vdb.git ; git clone https://github.com/ncbi/sra-tools.git

Then you should see the following:

If you create repositories as described above and run ./configure and make in each of ngs / ncbi-vdb / sra-tools subdirectories – each of them should find all required files from ngs / ncbi-vdb .

Non-standard location of ngs-sdk / ncbi-vdb

If location of ngs-sdk / ncbi-vdb or their build output directory is not standard (see above), you need to specify it:

  • ngs-sdk is in

ncbi-vdb is in

sra-tools in

ncbi-vdb/configure requires to find header files of ngs-sdk :

sra-tools needs to find ngs-sdk package and ncbi-vdb ‘s sources and build results.

Configure options are sticky!

Configure options are sticky. Running configure without options will use the options that you used the last time.

./configure –with-debug # will configure with debug :)

If next time you run

./configure # it will use the same options ( same as ./configure –with-debug)

To clear the saved options and all generated files run “./configure –clear”.

To check current configuration information and options you used run:

Standard option – Install machine-independent data file’s in subdirectories of directory.

Examples of subdirectories are: bin include lib64 lib32 share

Some tools and libraries depend on third party libraries and development headers ( libxml2 , libhdf5 , . ). By default configure will attempt to utilize them from your system if they can be located.

You can provide their location by specifying one of the options: –with-hdf5-prefix , –with-xml2-prefix , etc.



Scientific classification
Kingdom: Plantae
Division: Magnoliophyta
Class: Magnoliopsida
Order: Capparales
Family: Brassicaceae
Genus: Brassica
Species: B. napus
Binomial name
Brassica napus

Rapeseed (Brassica napus), also known as rape, oilseed rape, rapa, rapaseed and (in the case of one particular group of cultivars) canola, is a bright yellow flowering member of the family Brassicaceae (mustard or cabbage family). The name is derived from the Latin for turnip, rāpum or rāpa, and is first recorded in English at the end of the 14th century. Older writers usually distinguished the turnip and rape by the adjectives round and long(-rooted) respectively. [1] See also Brassica napobrassica, which may be considered a variety of Brassica napus. Some botanists include the closely related Brassica campestris within B. napus. (See Triangle of U)

8 Steps to a Clean Balance – and 5 Solutions to Keep It Clean

How to ensure accurate weighing results every day?

Safe Weighing Range Ensures Accurate Results


Cultivation and uses

Rapeseed is grown for the production of animal feed, vegetable oil for human consumption, and biodiesel; leading producers include the European Union, Canada, the United States, Australia, China and India. In India, it is grown on 13% of cropped land. According to the United States Department of Agriculture, rapeseed was the third leading source of vegetable oil in the world in 2000, after soybean and oil palm, and also the world’s second leading source of protein meal, although only one-fifth of the production of the leading soybean meal. World production is growing rapidly, with FAO reporting that 36 million tonnes of rapeseed was produced in the 2003-4 season, and 46 million tonnes in 2004-5. In Europe, rapeseed is primarily cultivated for animal feed [citation needed] (due to its very high lipid and medium protein content [citation needed] ), and is a leading option for Europeans to avoid importation of GMO products [citation needed] . Natural rapeseed oil contains erucic acid, which is mildly toxic to humans in large doses but is used as a food additive in smaller doses. Canola, originally a syncopated form of the abbreviation “Can.O., L-A.” (Canadian Oilseed, Low-Acid) that was used by the Manitoba government to label the seed during its experimental stages, is now a tradename for low erucic acid rapeseed that is sometimes mis-applied to other varieties [citation needed] .

The rapeseed is the valuable, harvested component of the crop. The crop is also grown as a winter-cover crop. It provides good coverage of the soil in winter, and limits nitrogen run-off. The plant is ploughed back in the soil or used as bedding. On some ecological or organic operations, livestock such as sheep or cattle are allowed to graze on the plants.

Processing of rapeseed for oil production provides rapeseed animal meal as a by-product. The by-product is a high-protein animal feed, competitive with soya [citation needed] . The feed is mostly employed for cattle feeding, but also for pigs and chickens (though less valuable for these). The meal has a very low content of the glucosinolates responsible for metabolism disruption in cattle and pigs [citation needed] . Rapeseed “oil cake” is also used as a fertilizer in China, and may be used for ornamentals, such as Bonsai, as well.

Rapeseed leaves and stems are also edible, similar to those of the related bok choy or kale. Some varieties of rapeseed (called 油菜, yóu cài, lit. “oil vegetable” in Chinese; yau choy in Cantonese; cải dầu in Vietnamese; and 菜の花, nanohana in Japanese) are sold as greens, primarily in Asian groceries.

Rapeseed is a heavy nectar producer, and honeybees produce a light colored, but peppery honey from it. It must be extracted immediately after processing is finished, as it will quickly granulate in the honeycomb and will be impossible to extract. The honey is usually blended with milder honeys, if used for table use, or sold as bakery grade. Rapeseed growers contract with beekeepers for the pollination of the crop.

Nutritional value

Canola oil (or rapeseed oil) contains both omega-6 and omega-3 fatty acids in a ratio of 2:1 and is second only to flax oil in omega-3 fatty acid. It is one of the most heart-healthy oils and has been reported to reduce cholesterol levels, lower serum tryglyceride levels, and keep platelets from sticking together. Some UK farmers (such as Hillfarm Oils[1]) & Farrington Oils[2]) have started to produce cold-pressed rapeseed oil as a versatile cooking oil and dressing, similar in use to olive oil.


Rapeseed oil is used in the manufacture of biodiesel for powering motor vehicles. Biodiesel may be used in pure form in newer engines without engine damage, and is frequently combined with standard diesel in ratios varying from 2% to 20% biodiesel. Formerly, due to the costs of growing, crushing, and refining rapeseed biodiesel, rapeseed derived biodiesel cost more to produce than standard diesel fuel. Prices of rapeseed oil are at very high levels presently (start November 05) due to increased demand on rapeseed oil for this purpose. Rapeseed oil is the preferred oil stock for biodiesel production in most of Europe, partly because rapeseed produces more oil per unit of land area as compared to other oil sources, such as soy beans.

Rapeseed and health

Rapeseed has been linked with adverse effects in asthma and hay fever sufferers. [citation needed] Some suggest that oilseed pollen is the cause of increased breathing difficulties. [citation needed] This is unlikely however [citation needed] , as rapeseed is an entomophilous crop, with pollen transfer primarily by insects. Others suggest that it is the inhalation of oilseed rape dust that causes this [2] , and that allergies to the pollen are relatively rare. [citation needed] There may also be another effect at work; since rapeseed in flower has a distinctive and pungent smell, hay fever sufferers may wrongly jump to the conclusion that it is the rapeseed that is to blame simply because they can smell it. [citation needed] An alternative explanation may be that it is simply the sheer volume of rapeseed pollen in the air around farmland which triggers an allergic reaction in hayfever sufferers on inhalation, or following prolonged exposure to high levels.


The Monsanto Company has genetically engineered new cultivars of rapeseed that are resistant to the effects of its herbicide Roundup. They have been vigorously prosecuting farmers found to have the Roundup Ready gene in Canola in their fields without paying a license fee [citation needed] . These farmers have claimed the Roundup Ready gene was blown into their fields and crossed with unaltered Canola [citation needed] . Other farmers claim that after spraying Roundup in non-Canola fields to kill weeds before planting, Roundup Ready volunteers are left behind, causing extra expense to rid their fields of the weeds [citation needed] .

In a closely followed legal battle, the Supreme Court of Canada found in favor of Monsanto’s patent infringement claim for illegal growing of Roundup Ready in its 2004 ruling on Monsanto Canada Inc. v. Schmeiser. The case garnered international controversy as a court-sanctioned legitimation for the global patent protection of genetically modified crops [citation needed] .


Worldwide production of rapeseed (including canola) rose to 46.4 million metric tons in 2005, the highest recorded total (source: FAO).

Rapeseed Options Explained

Please ask questions or offer corrections and suggestions. Thanks.

device name: [EDID Product Name] A name for the display (customizable).
device type: [unknown] Sets the icon for the display. When set to projector the ‘screen config’ section is available.

EDID information, some displays are detected with different identifications depending on how they are attached or detected. You can drag and drop these identification entries to combine displays.

the display expects the following RGB output levels: [PC levels (0-255)] This is what your display expects to receive. ‘PC levels (0-255)’ means “use a 16-235 YCbCr to 0-255 RGB conversion matrix” and ‘TV levels (16-235)’ means “use a 0-255 YCbCr to 0-255 RGB conversion matrix”. If the source is flagged full range either a 0-255 YCbCr to 0-255 RGB or a 0-255 YCbCr to 16-235 RGB conversion matrix is used instead.
the native display bitdepth is: [8 bit] This is the bit depth madVR will dither to. madVR offers very high quality dithering so if you are using a low bit depth display (e.g. a 6-bit TN) you may get better quality when setting this to 6-bit. Due to limited support for high bit depths, madVR dithers to 8-bit even when this is set to 9 or 10-bit except when using D3D11 ‘full screen exclusive’ (or D3D11 fullscreen windowed in Windows 10 with AMD or Nvidia GPUs). It can be interesting to turn this down to a very low value (2-4) while testing the dithering options but make sure to have the ‘trade quality for performance’ option ‘don’t use linear light for dithering’ unchecked even if you leave it checked for normal use.
3D format: [auto, disabled] Set the 3D format to: auto, side-by-side, top-and-bottom, row alternative, or column alternative. There is also an option to swap the left and right eyes.

calibration [disable calibration controls for this display]

disable calibration controls for this display: The display is assumed to have a BT.709 gamut with a pure power gamma of 2.2 (probably).
this display is already calibrated: [BT.709, pure power curve, 2.20] This sets the current display characteristics. The gamut option affects the conversions used by madVR when playing video with different gamuts. The gamma options only have an effect when using ‘tone map HDR using pixel shaders’ for HDR content or when using the ‘enable gamma processing’ option in ‘color & gamma’.
calibrate this display by using yCMS: yCMS offers a simple gamut and gamma calibration method. It requires a few measurements of the display that can be done with HCFR. If gamut or grayscale measurements are not supplied only the other correction is performed. Usually bad results (mostly banding and odd effects in shadows) are obtained if gamma measurements below

20% IRE are used so only enter values above 15-30% IRE.
calibrate this display by using external 3DLUT files: Use a calibration package such as Argyllcms, Calman, or LightSpace to generate a 256x256x256 3DLUT to perform a full calibration. For Argyllcms see this AVS Forum thread, for Calman, or for LightSpace. If the provided 3DLUT file contains calibration curves (e.g. in the case of ArgyllCMS, the collink “-a” or “-H” options were used), madVR will load the calibration curves into the system-wide GPU hardware gamma ramps, which affects everything displayed, not only madVR. madVR will restore the original gamma ramps (if any) when it is closed.
disable GPU gamma ramps: [Disabled] Clears system-wide GPU gamma ramps (monitor calibration), if any, replacing them with linear (no-op) curves. This affects everything displayed, not only madVR. madVR will restore the original GPU gamma ramps (if any) when it is closed. This option changes its behavior when using the ‘rendering -> general settings’ option ‘enable windowed overlay’ to only apply to madVR because madVR is emulating the gamma ramps in that case. This option has no effect if a 3DLUT file that contains calibration curves is loaded (see above).

display modes [None]
Allows setting refresh rate and resolution automatically depending on the source video.
list all display modes madVR may switch to: An example for a modern 4K display: 2160p23, 2160p24, 2160p25, 2160p29, 2160p30, 2160p50, 2160p59, 2160p60
treat 25p movies as 24p (requires Reclock or VideoClock): [Disabled] Uses 24 Hz modes to display 25 fps content, it requires Reclock or VideoClock to slow down the audio to match.
hack Direct3D to make 24.000Hz and 60.000Hz work: [Disabled] A hack to Direct3D that enables true 24 and 60 Hz display modes in Windows 8.1 or 10 which are usually locked to 23.976 Hz and 59.940 Hz. May cause presentation queues to not fill.

custom modes
A second tab in display modes. Allows configuring custom refresh rates and can assist in optimizing them for the purpose of avoiding dropped or repeated frames without frame blending (smooth motion) or resampling the audio (ReClock, VideoClock). Only custom timings can be optimized but simply editing a mode and applying the “EDID / CTA” timing parameters creates a custom mode, and is the recommended way to start optimizing a refresh rate. New timing parameters must be tested before they can be applied. Delete replaces the add button when selecting a custom mode. It uses each of GPU vendor’s private APIs to add these modes and does not work with EDID override methods like CRU; supports AMD, Intel, and Nvidia GPUs. With Nvidia these custom modes can only be set to 8-bit.

color & gamma [Disabled]

pure power curve: [Default] use the standard pure power gamma function
BT.709/601 curve: Use the inverse of a meant for camera gamma function. It has a linear section near black so shadows lighten faster as you move away from black. This can be helpful if your display has crushed shadows.
2.20, 2.40, etc.: [2.20] changes the display’s gamma, based on the display’s settings in ‘calibration’, to this target gamma. Lower brightens mid range values which can be nice in a brightly lit room. Higher darkens mid range values which might look better in a darker room.

hdr [let madVR decide]

let madVR decide: Sends HDR data to displays capable of HDR, otherwise coverts to SDR using pixel shader math.
passthrough HDR to display: Passes the HDR video to the display as is, along with the metadata if ‘send HDR metadata to the display’ is enabled.
tone map HDR using pixel shaders: Enables the options below-
-target peak nits: [200] Set the target display’s peak white brightness. Above this value is used as the highlights. A lower setting increases the brightness of mid range values.
-tone mapping curve: [BT.2390] The curve used when compressing the range.
-color tweaks for fire & explosions:: [balanced] Keeps the color approximately the same while de-saturating and/or reducing luminance to bring a pixel to a value the display can represent.
-highlight recovery strength: [None] Sharpening the highlights after range compression.
-measure each frame’s peak luminance: [Disabled] Allows madVR to only compress highlights as much as necessary on a per frame basis resulting in more detail in highlights.
-output video in HDR format: [Disabled] Add HDR metadata to the output video.
convert or process HDR content by using an external 3DLUT: Requires display calibration hardware and software. Possible with DisplayCal (Argyllcms) or Lightspace.

screen config [Disabled]
This section is hidden unless the device is set as a projector.

define visible screen area by cropping masked borders: Allows scaling to a smaller resolution and adding black pixels to the edges. Useful if the projector is overshooting the edges of the screen. Only active when full screen.
activate lens memory number: Sends a command to a JVC or Sony projector to activate an on-projector lens memory number.
anamorphic lens: Allows output to non-square pixels.

if in doubt, activate deinterlacing: [Disabled] deinterlace video not flagged as progressive
if in doubt, deactivate deinterlacing: [Enabled] deinterlace video flagged as interlaced
force film mode: [Disabled] force IVTC, reconstructing the original progressive frames from video encoded as interlaced, decimating duplicate frames if necessary. madVR’s IVTC is not functional when using DXVA2 or D3D11 native GPU decoding because madVR’s IVTC algorithm runs on the CPU and the decoded video data is never copied to system memory.
force video mode: [Disabled]force DXVA deinterlacing, uses the GPU’s native deinterlacing. This is the same as automatic and cannot decimate frames.
only look at pixels in the frame center: [Enabled] As described; good for broadcast (with its messy edges) but bad for Anime.

reduce banding artifacts: [Disabled, low/high] Fade detection does not run if both options are set to the same value for a small increase in performance. Five frames are removed from madVR’s rendering buffer every time a fade is detected if the trade quality for performance option ‘don’t rerender frames when fade in/out is detected’ is disabled.
reduce ringing artifacts: [Disabled] Attempts to reduce any ringing/halos present in the source caused by downscaling or sharpening before madVR, e.g. during mastering.
reduce compression artifacts: [Disabled] A deblocking and deringing algorithm. high quality is more significant at higher strengths and is much slower. Chroma often has artifacts but they are usually less obvious and it takes a lot of power to process the chroma channels too.
activate only if it comes for free (as part of NGU): [Disabled] Only runs RCA if it can be run as part of NGU image upscaling. Requires NGU Sharp high for medium quality and NGU Sharp very high for high quality.
reduce random noise: [Disabled] A denoising or grain reduction algorithm. Chroma often has less random noise than the luma.

image enhancements [Disabled]
These are applied before scaling. See ‘upscaling refinement’

disable scaling if image size changes by only: [Enabled, . 2 lines or less] If the resolution needs scaling by the number of pixels set or less no image scaling is done, black pixels are added to the right and/or bottom edge instead.
move subtitles: [Enabled, . to bottom of the screen/window] Move subtitles, this is important when removing black bars or subtitles can be displayed outside the visible screen area. Cannot move PGS subtitles if they are encoded as fullscreen images or Advanced Substation Alpha (ASS) subtitles which have a specific location defined.
automatically detect hard coded black bars: [Disabled] This enables the options below. madVR can detect and remove black bars on all sides of the video. Black bars cannot be detected when using DXVA2 or D3D11 Native decoding.
if black bars change pick one zoom factor: [Disabled, . which doesn’t lose any image content] Using this setting madVR will avoid changing the zoom or crop. e.g. It will not zoom or crop a 16:9 section in a normally 4:3 film when set to “which doesn’t lose any image content” and will zoom or crop all of the 4:3 footage the amount needed to remove the black bars from any 16:9 sections when set to “which doesn’t show any black bars”.
if black bars change quickly back and forth: [Disabled, . once every 2 sec] If not using the above option this option allows a limit on how often madVR can change the zoom or crop while playing to remove black bars as they are detected. Without either of these options madVR will always change the crop or zoom to only remove the black bars.
notify media player about cropped black bars: [Disabled, . no more than once every 2 sec] How often to notify the media player of changes in the black bars. Some media players use this information to resize the window.
always shift the image: [Disabled, . to the top of the screen] This allows setting whether the top or bottom of the video is cropped when zooming.
keep bars visible if they contain subtitles: [Disabled, . forever] Disables zooming or cropping any black bar in which subtitles are detected. Either forever or for a set time.
cleanup image borders by cropping: [Disabled, . 1 line from all black bar borders] Crop extra non-black pixels away from black bars or all edges. When set to crop all edges they are cropped even when no black bars are detected.
if there are big black bars: [Disabled, . reduce bar size by 25%] Allows setting separate handling of large black bars.
zoom small black bars away: [Disabled] This zooms into the video to remove the black bars, cropping a small amount of video off of one edge to maintain the original aspect ratio and resizing to the original display resolution. e.g. The bottom is cropped when cropping small black bars on the left and right and the video scaled to the original resolution.
crop black bars: [Disabled] This crops black bars, changing the display aspect ratio and resolution. Cropping black bars increases performance; the pixels no longer need to be processed. Profile rules referencing resolution will use the after crop resolution.

Nearest Neighbor: A low quality method, the value of the closest pixel is used. This looks very bad when not doing integer scaling (1x, 2x, 3x, etc.). Configure a custom keyboard shortcut to enable it.
Bilinear: A low quality method. It is as fast as Nearest Neighbor because GPUs have hardware to do bilinear filtering in a single operation.
DXVA2: Uses the GPU drivers to access hardware scaling. Transfer to and from hardware is done at the video bit depth so it may introduce banding or cause scaled dither noise. It can be very fast and low power. The quality varies between GPU brands and models but none are particularly good. Can do chroma upscaling as well so this option might override ‘chroma upscaling’. Requires a restart of madVR to take effect. Does not bypass the graphics card’s video (damage) algorithms so make sure they are off.
Cubic: [Bicubic60] Bicubic is b = 0, c = value / 100. SoftCubic is b = value / 100, c = 0. Mitchell-Netravali is b = 1/3, c = 1/3. Bicubic125 and 150 (c > 1) are special cases for downscaling because they have nasty artifacts when used for upscaling.
Lanczos: [3] A sharp sinc type
Spline: [3] A different sinc type
Jinc: A more advanced sinc type, uses 3-taps (based on an EWA LanczosSharp from ImageMagick)
Bilateral: A chroma scaler that uses the luma channel as reference. This can be very good but it can fail too.
Reconstruction: [soft] Similar to Bilateral in that it uses luma channel information to aid chroma scaling. Soft is less prone to artifacts.
SSIM: [1D-100%] Downscaling only. It is very sharp and detailed, especially useful with high downscaling ratios and fine details. with Shiandow
super-xbr: [100] xBR means scale By Rules, it works by detecting edges and interpolating pixels along them. Can only perform a 2x upscale.
NGU Family: [medium] madshi’s own Next Generation Upscaling. A sharp doubling algorithm with minimal artifacts. NGU Soft, Standard, and Sharp can also quadruple the luma in one step. The Anti-Alias version is softer but reduces aliasing and is more tolerant of source artifacts. Works in Windows XP.

activate anti-ringing filter: [Disabled, relaxed] madshi’s method to reduce ringing, the major artifact caused by sharp scalers. Designed to only remove the ringing introduced by the filter it accompanies.

chroma upscaling [Bicubic60]
Cb and Cr are stored at half the resolution of Y in a standard YCbCr 4:2:0 source and this controls how madVR doubles their resolution in both dimensions to create YCbCr 4:4:4 for the conversion to RGB. When downscaling a lot this setting is used to bring the chroma to the target resolution, not the luma resolution, so the luma is downscaled before the conversion to RGB.

activate SuperRes filter, strength: [Disabled, 3] A special version of SuperRes designed for the chroma upscaling step. Not recommended with NGU.

image downscaling [Bicubic150]
How madVR scales to the target resolution if it is smaller than the source.

scale in linear light: [Disabled] Using linear light when downscaling produces a result more similar to what one would get with optical scaling; bright specks such as stars in a night sky are preserved much better. The chroma must be upscaled to match the luma before downscaling when using this option because linear light is only possible in RGB.
activate anti-bloating filter: [Disabled, 100%] A post process method to reduce the fatness created by downscaling with SSIM.

image upscaling [Lanczos 3]
How madVR scales to the target resolution if it is larger than the source.

scale in sigmoidal light: [Disabled] Linear light but for upscaling, applies a sigmoidal curve after the conversion to linear light. This reduces the dark halo artifacts around sharp edges caused by upscaling in linear light.

NGU or super-xbr: When choosing a doubling scaler the ‘algorithm quality’, ‘activate doubling / quadrupling. ‘, and ‘if any (more) scaling needs to be done’ options become available. Algorithm quality is much more important for luma than chroma. “let madVR decide” chooses options appropriate for the performance requirements of the chosen luma algorithm quality. It is recommended to turn the luma quality up as high as possible before adjusting other options.

algorithm quality:
upscaling refinement [All Disabled]
These are applied as part of upscaling or supersampling.

sharpen edges: [1.0] Only sharpens edges instead of textures like skin or cloth. Avoids sharpening artifacts too much.
crispen edges: [1.0] A tamed version of FineSharp, a sharpener originally by Didйe that attempts to keep local energy close to the original. Better used with higher quality sources because it sharpens artifacts.
thin edges: [1.0] As its name implies. Good for SD Anime or cartoons.
enhance detail: [1.0] Sharpens textures like skin or cloth, also sharpens artifacts.
soften edges: [1] Applied as part of NGU. Useful for large upscaling ratios with this very sharp upscaler.
add grain: [1] Applied as part of NGU. Useful for large upscaling ratios with this very sharp upscaler. Combats the artificial flat look caused by the combination of a lack of detail in non-edge textures with very sharp upscaling of edges.
LumaSharpen: [0.65] Blurs the original pixel with the surrounding pixels and then subtracts the blur. Avoids sharpening artifacts.
AdaptiveSharpen: [0.5] Tries to sharpen medium sharp edges the most, it avoids sharpening near flat areas and very sharp edges. From bacondither
activate anti-bloating filter: A post process method to reduce the fatness created by line sharpeners. Not needed for crispen edges, which is already “skinny.”
activate anti-ringing filter: A post process method to reduce ringing due to sharpening.
SuperRes: [3] A post process method from Shiandow. Not recommended in combination with NGU.
—-use linear light: Ideally use the same method that the source was originally downscaled with when it was mastered. This is usually not known but gamma light might be more likely. When enabled the image may be slightly darker and dark lines slightly fatter.

  1. Calculate an initial guess (using the configured upscaler)
  2. Downscale and calculate differences with original image.
  3. Scale those differences to the final size (SoftCubic50)
  4. Improve guess by:
    • Softening the image
    • Subtracting differences with the original image
    • Sharpening
    • Removing aliasing
    • Removing ringing
  5. Repeat steps 2-4 several times.


delay playback start until render queue is full: [Disabled] Pauses playback until all the buffers are full. With this option disabled only the present buffer needs to fill before playback starts.
enable windowed overlay (Windows 7 and newer): [Disabled] Only available on Nvidia and Intel GPUs. Uses a low level overlay method which bypasses the GPU LUT (monitor profile) so madVR emulates it when using this option, this is done in 16-bit so madVR can provide better quality than the GPU. Overlay also bypasses the OS to a large extent; screen-shots are not possible. D3D9 Only. Incompatible with ‘fullscreen exclusive mode’.
enable automatic fullscreen exclusive mode: [Enabled] madVR has exclusive access to the display, nothing else can draw to the display without dropping out of this mode. This is the most stable mode for madVR because it has the most control over when and how video frames are displayed. There is a slight flicker and delay as madVR enters and exits this mode. Required for 10 bit in Windows 7 or 8.
disable desktop composition (Vista and Windows 7): [Disabled] Disables Aero which has its own v-sync that can conflict with madVR’s. This option cannot disable desktop composition on Windows 8 or 10 but desktop composition also works better on 8 and 10.
use Direct3D 11 for presentation (Windows 7 and newer): [Disabled] Use Direct3D 11 instead of D3D9. Requires a restart of madVR to take effect. Required for >8 bit output. Slightly more responsive than D3D9. Overrides windowed overlay.
present a frame for every VSync: [Enabled] when disabled madVR only presents new frames when needed, relying on D3D11 to repeat frames for each VSync. Disabled may improve performance but may also cause presentation glitches.
use a separate device for presentation (Vista and newer): [Disabled] Might improve performance slightly, or it might hurt it slightly.
use a separate device for DXVA processing (Vista and newer): [Disabled] Might improve performance slightly, or it might hurt it slightly.
CPU queue size: [16] The buffer in system memory for decoded video and xySubFilter subtitles.
GPU queue size: [8] The buffer in the graphics memory for madVR’s rendering.

windowed and exclusive mode settings

present several frames in advance: [Enabled] Uses a new method for presenting frames in advance instead of using a back-buffer queue.
how many video frames shall be presented in advance or how many backbuffers shall be used: [8 or 3] The present queue, a final buffer in DirectX, after madVR sends completed frames to Windows.
when and how shall the GPU be flushed: [flush, flush & wait (sleep), don’t flush, don’t flush] To be able to display rendering times in the OSD the ‘. after last render step’ must be one of the ‘flush & wait’ options.

stereo 3d
madVR only supports frame packed 3D with the LAV video decoder.

enable stereo 3d playback: [Enabled] Allow madVR to output stereoscopic 3D content. 3D output is currently limited to 1080p23 with smooth motion automatically disabled.
when playing 2d content: [Disabled, disable os stereo 3d support for all displays] Change the stereo 3D setting in the OS when playing 2D content.
when playing 3d content: [Disabled, enable] Change the stereo 3D setting in the OS when playing 3D content. Depending on the display and GPU, 3D support may not need to be enabled in the OS to display 3D content.
restore os stereo 3d settings when media player is closed: [Disabled]

smooth motion [Disabled]
Uses frame blending to perfectly display the video’s frame rate at the display’s refresh rate without any dropped or repeated frames and while staying in sync with the audio. This eliminates frame time judder in exchange for slightly increased blurring due to the frame blending. The blurring is more visible when the refresh rate matches the source frame rate because all the frames will be blended frames. The blurring is less visible on higher refresh rate displays because fewer frames will be blended frames. Smooth motion will harm motion interpolation, do not use them at the same time.

only if there would be motion judder without it. : [Default] Smooth motion will activate when the refresh rate is not close to a multiple of the frame rate, e.g. it activates for 23.976 fps at 60Hz but not for 29.976 fps at 60Hz.
. or if the display refresh rate is an exact multiple of the movie frame rate: Smooth motion will always activate unless the frame rate matches the refresh rate, e.g. it will also activate for 29.976 fps at 60Hz but will still not activate for 23.976 fps at 24Hz.
always: Smooth motion is always active. This allows no dropped or repeated frames even when the source frame rate is very close, but not quite equal to, the real refresh rate of the display. Note that smooth motion has less blurring when displaying 23.976 fps at 60 Hz than 23.976 fps at 24 Hz so this option is not recommended unless you cannot increase the display’s refresh rate.

Dithering is performed as the very last step in madVR to convert its internal 16 bit data to the bit depth set for the display. Any time madVR does anything to the video high bit depth information is created and dithering allows much of this information to be preserved when displayed at a lower bit depth. For example, the conversion of 8-bit YCbCr to RGB generates >8-bit RGB data. The higher the output bit-depth, as set in madVR’s ‘devices’ -> ‘properties’, the less important dithering quality is.

None: Only use for testing, it is never useful for normal use, banding.
Random Dithering: Highest noise, but it is also the fastest option.
Ordered Dithering: [Default] This option has the lowest visible dithering noise. It uses a fixed dither texture that was optimized for low visible noise and offers high quality dithering with a low performance hit.
Error Diffusion: Uses DirectCompute to perform very high quality error diffusion dithering, similar to the Floyd–Steinberg or Sierra dithering algorithms. Test option 1 and 2 for yourself (or pick one randomly). They are both very good and my preference seems to change depending on the display.
use colored noise: [Enabled] Uses an inverted dither pattern for green which reduces luma noise but adds chroma noise. I like this option disabled, but test it for yourself.
change dither for every frame: [Enabled] Uses a new dither seed for every frame or, for ordered dithering, adds a random offset and rotates the dither texture 90° between every frame.

Оптимизация запросов. Основы EXPLAIN в PostgreSQL (часть 3)

Предыдущие части:


— Sort (cost=117993.01..120493.04 rows=1000010 width=37) (actual time=571.591..651.524 rows=1000010 loops=1)
Sort Key: c1
Sort Method: external merge Disk: 45952kB
-> Seq Scan on foo (cost=0.00..18334.10 rows=1000010 width=37) (actual time=0.007..62.041 rows=1000010 loops=1)
Total runtime: 690.984 ms
(5 rows)

Сначала производится Seq Scan таблицы foo . Затем сортировка Sort . В выводе команды EXPLAIN знак -> указывает на иерархию действий (node). Чем раньше выполняется действие, тем с большим отступом оно отображается.
Sort Key — условие сортировки.
Sort Method: external merge Disk — при сортировке используется временный файл на диске объёмом 45952kB .

Прошу разбирающихся в теме разъяснить различия между external merge и external sort .

Проверим с опцией BUFFERS:

— Sort (cost=117993.01..120493.04 rows=1000010 width=37) (actual time=568.412..652.308 rows=1000010 loops=1)
Sort Key: c1
Sort Method: external merge Disk: 45952kB
Buffers: shared hit=8334, temp read=5745 written=5745
-> Seq Scan on foo (cost=0.00..18334.10 rows=1000010 width=37) (actual time=0.010..68.203 rows=1000010 loops=1)
Buffers: shared hit=8334
Total runtime: 698.032 ms
(7 rows)

Действительно, temp read=5745 written=5745 — во временный файл было записано и прочитано 5745 блоков по 8Kb = 45960Kb. Операции с 8334 блоками были произведены в кэше.

Операции с файловой системой более медленные, чем операции в оперативной памяти.
Попробуем увеличить объём используемой памяти work_mem :

— Sort (cost=117993.01..120493.04 rows=1000010 width=37) (actual time=265.301..296.777 rows=1000010 loops=1)
Sort Key: c1
Sort Method: quicksort Memory: 102702kB
-> Seq Scan on foo (cost=0.00..18334.10 rows=1000010 width=37) (actual time=0.006..57.836 rows=1000010 loops=1)
Total runtime: 328.746 ms
(5 rows)

Sort Method: quicksort Memory: 102702kB — сортировка целиком проведена в оперативной памяти.

— Index Scan using foo_c1_idx on foo (cost=0.42..34327.57 rows=1000010 width=37) (actual time=0.023..126.076 rows=1000010 loops=1)
Total runtime: 153.452 ms
(2 rows)

Из действий осталось только Index Scan , что заметно отразилось на скорости выполнения запроса.


Удалим ранее созданный индекс.

— Seq Scan on foo (cost=0.00..20834.12 rows=100 width=37) (actual time=0.033..94.757 rows=3824 loops=1)
Filter: (c2

Rows Removed by Filter: 996186
Buffers: shared hit=8334
Total runtime: 94.924 ms
(5 rows)

Ожидаемо, используются Seq Scan и Filter .

— Limit (cost=0.00..2083.41 rows=10 width=37) (actual time=0.037..0.607 rows=10 loops=1)
Buffers: shared hit=26
-> Seq Scan on foo (cost=0.00..20834.12 rows=100 width=37) (actual time=0.031..0.599 rows=10 loops=1)
Filter: (c2

Rows Removed by Filter: 3053
Buffers: shared hit=26
Total runtime: 0.628 ms
(7 rows)

Производится сканирование Seq Scan строк таблицы и сравнение Filter их с условием. Как только наберётся 10 записей, удовлетворяющих условию, сканирование закончится. В нашем случае для того, чтобы получить 10 строк результата пришлось прочитать не всю таблицу, а только 3063 записи, из них 3053 были отвергнуты ( Rows Removed by Filter ).
То же происходит и при Index Scan .

Создадим новую таблицу, соберём для неё статистику.

Запрос по двум таблицам

— Hash Join (cost=13463.00..49297.22 rows=500000 width=42) (actual time=87.441..907.555 rows=500010 loops=1)
Hash Cond: (foo.c1 = bar.c1)
-> Seq Scan on foo (cost=0.00..18334.10 rows=1000010 width=37) (actual time=0.008..67.951 rows=1000010 loops=1)
-> Hash (cost=7213.00..7213.00 rows=500000 width=5) (actual time=87.352..87.352 rows=500000 loops=1)
Buckets: 65536 Batches: 1 Memory Usage: 18067kB
-> Seq Scan on bar (cost=0.00..7213.00 rows=500000 width=5) (actual time=0.007..33.233 rows=500000 loops=1)
Total runtime: 920.967 ms
(7 rows)

Сначала просматривается ( Seq Scan ) таблица bar . Для каждой её строки вычисляется хэш ( Hash ).
Затем сканируется Seq Scan таблица foo , и для каждой строки этой таблицы вычисляется хэш, который сравнивается ( Hash Join ) с хэшем таблицы bar по условию Hash Cond . Если соответствие найдено, выводится результирующая строка, иначе строка будет пропущена.
Использовано 18067kB в памяти для размещения хэшей таблицы bar .

— Merge Join (cost=1.69..39879.71 rows=500000 width=42) (actual time=0.037..263.357 rows=500010 loops=1)
Merge Cond: (foo.c1 = bar.c1)
-> Index Scan using foo_c1_idx on foo (cost=0.42..34327.57 rows=1000010 width=37) (actual time=0.019..58.920 rows=500011 loops=1)
-> Index Scan using bar_c1_idx on bar (cost=0.42..15212.42 rows=500000 width=5) (actual time=0.008..71.719 rows=500010 loops=1)
Total runtime: 283.549 ms
(5 rows)

Hash уже не используется. Merge Join и Index Scan по индексам обеих таблиц дают впечатляющий прирост производительности.

— Hash Left Join (cost=13463.00..49297.22 rows=1000010 width=42) (actual time=82.682..926.331 rows=1000010 loops=1)
Hash Cond: (foo.c1 = bar.c1)
-> Seq Scan on foo (cost=0.00..18334.10 rows=1000010 width=37) (actual time=0.004..68.763 rows=1000010 loops=1)
-> Hash (cost=7213.00..7213.00 rows=500000 width=5) (actual time=82.625..82.625 rows=500000 loops=1)
Buckets: 65536 Batches: 1 Memory Usage: 18067kB
-> Seq Scan on bar (cost=0.00..7213.00 rows=500000 width=5) (actual time=0.003..31.890 rows=500000 loops=1)
Total runtime: 950.625 ms
(7 rows)

Seq Scan ?
Посмотрим, какие результаты будут, если запретить Seq Scan.

— Merge Left Join (cost=0.85..58290.02 rows=1000010 width=42) (actual time=0.024..353.819 rows=1000010 loops=1)
Merge Cond: (foo.c1 = bar.c1)
-> Index Scan using foo_c1_idx on foo (cost=0.42..34327.57 rows=1000010 width=37) (actual time=0.011..112.095 rows=1000010 loops=1)
-> Index Scan using bar_c1_idx on bar (cost=0.42..15212.42 rows=500000 width=5) (actual time=0.008..63.125 rows=500010 loops=1)
Total runtime: 378.603 ms
(5 rows)

По мнению планировщика, использование индексов затратнее, чем использование хэшей. Такое возможно при достаточно большом объёме выделенной памяти. Помните, мы увеличивали work_mem ?
Но, если память в дефиците, планировщик будет вести себя иначе:

— Merge Left Join (cost=0.85..58290.02 rows=1000010 width=42) (actual time=0.014..376.395 rows=1000010 loops=1)
Merge Cond: (foo.c1 = bar.c1)
-> Index Scan using foo_c1_idx1 on foo (cost=0.42..34327.57 rows=1000010 width=37) (actual time=0.005..124.698 rows=1000010 loops=1)
-> Index Scan using bar_c1_idx on bar (cost=0.42..15212.42 rows=500000 width=5) (actual time=0.006..66.813 rows=500010 loops=1)
Total runtime: 401.990 ms
(5 rows)

А как будет выглядеть вывод EXPLAIN при запрещённом Index Scan ?

— Hash Left Join (cost=15417.00..63831.18 rows=1000010 width=42) (actual time=93.440..712.056 rows=1000010 loops=1)
Hash Cond: (foo.c1 = bar.c1)
-> Seq Scan on foo (cost=0.00..18334.10 rows=1000010 width=37) (actual time=0.008..65.901 rows=1000010 loops=1)
-> Hash (cost=7213.00..7213.00 rows=500000 width=5) (actual time=93.308..93.308 rows=500000 loops=1)
Buckets: 65536 Batches: 2 Memory Usage: 9045kB
-> Seq Scan on bar (cost=0.00..7213.00 rows=500000 width=5) (actual time=0.007..33.718 rows=500000 loops=1)
Total runtime: 736.726 ms
(7 rows)

cost явно увеличился. Причина в Batches: 2 . Весь хэш не поместился в память, его пришлось разбить на 2 пакета по 9045kB.

Здесь опять прошу помощи гуру. Объясните, почему при LEFT JOIN и достаточном work_mem , использование Merge Left Join более затратно, чем Hash Left Join ?

На этом сегодня остановлюсь.

Много полезного про индексы PostgreSQL рассказали Олег Бартунов и Александр Коротков.

Внесу сюда ссылку на свежую статьи от PostgreSQL Индексы в PostgreSQL, часть 2, часть 3. Там многое разъяснено.

Best Binary Options Brokers 2020:
  • Binarium

    The Best Binary Options Broker 2020!
    Perfect For Beginners and Middle-Leveled Traders!
    Free Demo Account!
    Free Trading Education!
    Get Your Sign-Up Bonus Now!

  • Binomo

    Good Broker For Experienced Traders!

Best Binary Options Brokers 2020:
  • Binarium

    The Best Binary Options Broker 2020!
    Perfect For Beginners and Middle-Leveled Traders!
    Free Demo Account!
    Free Trading Education!
    Get Your Sign-Up Bonus Now!

  • Binomo

    Good Broker For Experienced Traders!

Like this post? Please share to your friends:
Binary Options Trading: Brokers Reviews
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!:

16th February 2020, 04:39 #2 | Link