intel
Section: Devices and Network Interfaces (4)Updated: xf86-video-intel 2.16.0
Index Return to Main Contents
NAME
intel - Intel integrated graphics chipsetsSYNOPSIS
Section N'34'DeviceN'34' Identifier N'34'devnameN'34' Driver N'34'intelN'34' ... EndSection
DESCRIPTION
intel is an Xorg driver for Intel integrated graphics chipsets. The driver supports depths 8, 15, 16 and 24. All visual types are supported in depth 8. For the i810/i815 other depths support the TrueColor and DirectColor visuals. For the i830M and later, only the TrueColor visual is supported for depths greater than 8. The driver supports hardware accelerated 3D via the Direct Rendering Infrastructure (DRI), but only in depth 16 for the i810/i815 and depths 16 and 24 for the 830M and later.SUPPORTED HARDWARE
intel supports the i810, i810-DC100, i810e, i815, i830M, 845G, 852GM, 855GM, 865G, 915G, 915GM, 945G, 945GM, 965G, 965Q, 946GZ, 965GM, 945GME, G33, Q33, Q35, G35, GM45, G45, Q45, G43, G41 chipsets, and Pineview-M in Atom N400 series, Pineview-D in Atom D400/D500 series.CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver.The Intel 8xx and 9xx families of integrated graphics chipsets have a unified memory architecture meaning that system memory is used as video RAM. For the i810 and i815 family of chipsets, operating system support for allocating system memory is required in order to use this driver. For the 830M and later, this is required in order for the driver to use more video RAM than has been pre-allocated at boot time by the BIOS. This is usually achieved with an "agpgart" or "agp" kernel driver. Linux, FreeBSD, OpenBSD, NetBSD, and Solaris have such kernel drivers available.
By default, the i810/i815 will use 8 MB of system memory for graphics if AGP allocable memory is < 128 MB, 16 MB if < 192 MB or 24 MB if higher. Use the VideoRam option to change the default value.
For the 830M and later, the driver will automatically size its memory allocation according to the features it will support. Therefore, the VideoRam option, which in the past had been necessary to allow more than some small amount of memory to be allocated, is now ignored.
The following driver Options are supported
- Option N'34'ColorKeyN'34' N'34'integerN'34'
- This sets the default pixel value for the YUV video overlay key.
- Default: undefined.
- Option N'34'DRIN'34' N'34'booleanN'34'
- Disable or enable DRI support.
-
Default: DRI is enabled for configurations where it is supported.
The following driver Options are supported for the i810 and i815 chipsets:
- Option N'34'CacheLinesN'34' N'34'integerN'34'
- This allows the user to change the amount of graphics memory used for 2D acceleration and video when XAA acceleration is enabled. Decreasing this amount leaves more for 3D textures. Increasing it can improve 2D performance at the expense of 3D performance.
- Default: depends on the resolution, depth, and available video memory. The driver attempts to allocate space for at 3 screenfuls of pixmaps plus an HD-sized XV video. The default used for a specific configuration can be found by examining the Xorg log file.
- Option N'34'DDCN'34' N'34'booleanN'34'
- Disable or enable DDC support.
- Default: enabled.
- Option N'34'Dac6BitN'34' N'34'booleanN'34'
- Enable or disable 6-bits per RGB for 8-bit modes.
- Default: 8-bits per RGB for 8-bit modes.
- Option N'34'XvMCSurfacesN'34' N'34'integerN'34'
- This option enables XvMC. The integer parameter specifies the number of surfaces to use. Valid values are 6 and 7.
- Default: XvMC is disabled.
- VideoRam integer
- This option specifies the amount of system memory to use for graphics, in KB.
- The default is 8192 if AGP allocable memory is < 128 MB, 16384 if < 192 MB, 24576 if higher. DRI require at least a value of 16384. Higher values may give better 3D performance, at expense of available system memory.
- Option N'34'NoAccelN'34' N'34'booleanN'34'
- Disable or enable acceleration.
-
Default: acceleration is enabled.
The following driver Options are supported for the 830M and later chipsets:
- Option N'34'VideoKeyN'34' N'34'integerN'34'
- This is the same as the N'34'ColorKeyN'34' option described above. It is provided for compatibility with most other drivers.
- Option N'34'XvPreferOverlayN'34' N'34'booleanN'34'
- Make hardware overlay be the first XV adaptor. The overlay behaves incorrectly in the presence of compositing, but some prefer it due to it syncing to vblank in the absence of compositing. While most XV-using applications have options to select which XV adaptor to use, this option can be used to place the overlay first for applications which don't have options for selecting adaptors.
- Default: Textured video adaptor is preferred.
- Option N'34'FallbackDebugN'34' N'34'booleanN'34'
- Enable printing of debugging information on acceleration fallbacks to the server log.
- Default: Disabled
- Option N'34'DebugFlushBatchesN'34' N'34'booleanN'34'
- Flush the batch buffer after every single operation.
- Default: Disabled
- Option N'34'DebugFlushCachesN'34' N'34'booleanN'34'
- Include an MI_FLUSH at the end of every batch buffer to force data to be flushed out of cache and into memory before the completion of the batch.
- Default: Disabled
- Option N'34'DebugWaitN'34' N'34'booleanN'34'
- Wait for the completion of every batch buffer before continuing, i.e. perform synchronous rendering.
- Default: Disabled
- Option N'34'ShadowN'34' N'34'booleanN'34'
- This option controls the use of GPU acceleration and placement of auxiliary buffers in memory. Enabling the Shadow will disable all use of the GPU for RENDER acceleration and force software-fallbacks for all but updating the scan-out buffer. Hardware overlay is still supported so Xv will continue to playback videos using the GPU, but GL will be forced to use software rasterisation as well. This is a last resort measure for systems with crippling bugs, such as early 8xx chipsets. It is still hoped that we will find a workaround to enable as much hardware acceleration on those architectures as is possible, but until then, using a shadow buffer should maintain system stability.
- Default: Disabled
- Option N'34'SwapbuffersWaitN'34' N'34'booleanN'34'
- This option controls the behavior of glXSwapBuffers and glXCopySubBufferMESA calls by GL applications. If enabled, the calls will avoid tearing by making sure the display scanline is outside of the area to be copied before the copy occurs. If disabled, no scanline synchronization is performed, meaning tearing will likely occur. Note that when enabled, this option can adversely affect the framerate of applications that render frames at less than refresh rate.
- Default: enabled.
- Option N'34'TripleBufferN'34' N'34'booleanN'34'
- This option enables the use of a third buffer for page-flipping. The third buffer allows applications to run at vrefresh rates even if they occasionally fail to swapbuffers on time. The effect of such missed swaps is the output jitters between 60fps and 30fps, and in the worst case appears frame-locked to 30fps. The disadvantage of triple buffering is that there is an extra frame of latency, due to the pre-rendered frame sitting in the swap queue, between input and any display update.
- Default: enabled.
- Option N'34'TilingN'34' N'34'booleanN'34'
- This option controls whether memory buffers for Pixmaps are allocated in tiled mode. In most cases (especially for complex rendering), tiling dramatically improves performance.
- Default: enabled.
- Option N'34'LinearFramebufferN'34' N'34'booleanN'34'
- This option controls whether the memory for the scanout (also known as the front or frame buffer) is allocated in linear memory. A tiled framebuffer is required for power conservation features, but for certain system configurations you may wish to override this and force a linear layout.
- Default: disabled
- Option N'34'RelaxedFencingN'34' N'34'booleanN'34'
- This option controls whether we attempt to allocate the minimal amount of memory required for the buffers. The reduction in working set has a substantial improvement on system performance. However, this has been demonstrate to be buggy on older hardware (845-865 and 915-945, but ok on PineView and later) so on those chipsets defaults to off.
- Default: Enabled for G33 (includes PineView), and later, class machines.
- Option N'34'XvMCN'34' N'34'booleanN'34'
- Enable XvMC driver. Current support MPEG2 MC on 915/945 and G33 series. User should provide absolute path to libIntelXvMC.so in XvMCConfig file.
- Default: Disabled.
- Option N'34'ThrottleN'34' N'34'booleanN'34'
- This option controls whether the driver periodically waits for pending drawing operations to complete. Throttling ensures that the GPU does not lag too far behind the CPU and thus noticeable delays in user responsible at the cost of throughput performance.
- Default: enabled.
- Option N'34'HotPlugN'34' N'34'booleanN'34'
- This option controls whether the driver automatically notifies applications when monitors are connected or disconnected.
- Default: enabled.
- Option N'34'ZaphodHeadsN'34' N'34'stringN'34'
-
Specify the randr output(s) to use with zaphod mode for a particular driver
instance. If you this option you must use it with all instances of the
driver
For example: Option N'34'ZaphodHeadsN'34' N'34'LVDS1,VGA1N'34' will assign xrandr outputs LVDS1 and VGA0 to this instance of the driver.
OUTPUT CONFIGURATION
On 830M and better chipsets, the driver supports runtime configuration of detected outputs. You can use the xrandr tool to control outputs on the command line as follows:
- xrandr --output output --set property value
Note that you may need to quote property and value arguments that contain spaces. Each output listed below may have one or more properties associated with it (like a binary EDID block if one is found). Some outputs have unique properties which are described below. See the "MULTIHEAD CONFIGURATIONS" section below for additional information.
VGA
VGA output port (typically exposed via an HD15 connector).LVDS
Low Voltage Differential Signalling output (typically a laptop LCD panel). Available properties:
BACKLIGHT - current backlight level (adjustable)
- By adjusting the BACKLIGHT property, the brightness on the LVDS output can be adjusted. In some cases, this property may be unavailable (for example if your platform uses an external microcontroller to control the backlight).
-
scaling mode - control LCD panel scaling mode
- When the currently selected display mode differs from the native panel resolution, various scaling options are available. These include
-
-
Center
- Simply center the image on-screen without scaling. This is the only scaling mode that guarantees a one-to-one correspondence between native and displayed pixels, but some portions of the panel may be unused (so-called "letterboxing").
Full aspect
- Scale the image as much as possible while preserving aspect ratio. Pixels may not be displayed one-to-one (there may be some blurriness). Some portions of the panel may be unused if the aspect ratio of the selected mode does not match that of the panel.
Full
- Scale the image to the panel size without regard to aspect ratio. This is the only mode which guarantees that every pixel of the panel will be used. But the displayed image may be distorted by stretching either horizontally or vertically, and pixels may not be displayed one-to-one (there may be some blurriness).
The precise names of these options may differ depending on the kernel video driver, (but the functionality should be similar). See the output of xrandr --prop for a list of currently available scaling modes.
-
TV
Integrated TV output. Available properties include:
BOTTOM, RIGHT, TOP, LEFT - margins
- Adjusting these properties allows you to control the placement of your TV output buffer on the screen. The options with the same name can also be set in xorg.conf with integer value.
-
BRIGHTNESS - TV brightness, range 0-255
- Adjust TV brightness, default value is 128.
-
CONTRAST - TV contrast, range 0-255
- Adjust TV contrast, default value is 1.0 in chipset specific format.
-
SATURATION - TV saturation, range 0-255
- Adjust TV saturation, default value is 1.0 in chipset specific format.
-
HUE - TV hue, range 0-255
- Adjust TV hue, default value is 0.
-
TV_FORMAT - output standard
- This property allows you to control the output standard used on your TV output port. You can select between NTSC-M, NTSC-443, NTSC-J, PAL-M, PAL-N, and PAL.
-
TV_Connector - connector type
- This config option should be added to xorg.conf TV monitor's section, it allows you to force the TV output connector type, which bypass load detect and TV will always be taken as connected. You can select between S-Video, Composite and Component.
-
TMDS-1
First DVI SDVO outputTMDS-2
Second DVI SDVO outputTMDS-1, TMDS-2, HDMI-1, HDMI-2
DVI/HDMI outputs. Avaliable common properties include:BROADCAST_RGB - method used to set RGB color range(full range 0-255, not full range 16-235)
- Adjusting this propertie allows you to set RGB color range on each channel in order to match HDTV requirment(default 0 for full range). Setting 1 means RGB color range is 16-235, 0 means RGB color range is 0-255 on each channel.
-
SDVO and DVO TV outputs are not supported by the driver at this time.
See xorg.conf(5) for information on associating Monitor sections with these outputs for configuration. Associating Monitor sections with each output can be helpful if you need to ignore a specific output, for example, or statically configure an extended desktop monitor layout.
MULTIHEAD CONFIGURATIONS
The number of independent outputs is dictated by the number of CRTCs (in X parlance) a given chip supports. Most recent Intel chips have two CRTCs, meaning that two separate framebuffers can be displayed simultaneously, in an extended desktop configuration. If a chip supports more outputs than it has CRTCs (say local flat panel, VGA and TV in the case of many outputs), two of the outputs will have to be "cloned", meaning that they display the same framebuffer contents (or one displays a subset of another's framebuffer if the modes aren't equal).
You can use the "xrandr" tool, or various desktop utilities, to change your output configuration at runtime. To statically configure your outputs, you can use the "Monitor-<type>" options along with additional monitor sections in your xorg.conf to create your screen topology. The example below puts the VGA output to the right of the builtin laptop screen, both running at 1024x768.
Section N'34'MonitorN'34' Identifier N'34'Laptop FooBar Internal DisplayN'34' Option N'34'PositionN'34' N'34'0 0N'34' EndSection Section N'34'MonitorN'34' Identifier N'34'Some Random CRTN'34' Option N'34'PositionN'34' N'34'1024 0N'34' Option N'34'RightOfN'34' N'34'Laptop FoodBar Internal DisplayN'34' EndSection Section N'34'DeviceN'34' Driver N'34'intelN'34' Option N'34'monitor-LVDSN'34' N'34'Laptop FooBar Internal DisplayN'34' Option N'34'monitor-VGAN'34' N'34'Some Random CRTN'34' EndSection
TEXTURED VIDEO ATTRIBUTES
The driver supports the following X11 Xv attributes for Textured Video. You can use the "xvattr" tool to query/set those attributes at runtime.XV_SYNC_TO_VBLANK
XV_SYNC_TO_VBLANK is used to control whether textured adapter synchronizes the screen update to the vblank to eliminate tearing. It is a Boolean attribute with values of 0 (never sync) or 1 (always sync). An historic value of -1 (sync for large windows only) will now be interpreted as 1, (since the current approach for sync is not costly even with small video windows).XV_BRIGHTNESS
XV_CONTRAST
REPORTING BUGS
The xf86-video-intel driver is part of the X.Org and Freedesktop.org umbrella projects. Details on bug reporting can be found at http://www.intellinuxgraphics.org/how_to_report_bug.html. Mailing lists are also commonly used to report experiences and ask questions about configuration and other topics. See lists.freedesktop.org for more information (the<EMAIL_ADDRESS>mailing list is the most appropriate place to ask X.Org and driver related questions).
SEE ALSO
Xorg(1), xorg.conf(5), Xserver(1), X(7)AUTHORS
Authors include: Keith Whitwell, and also Jonathan Bian, Matthew J Sottek, Jeff Hartmann, Mark Vojkovich, Alan Hourihane, H. J. Lu. 830M and 845G support reworked for XFree86 4.3 by David Dawes and Keith Whitwell. 852GM, 855GM, and 865G support added by David Dawes and Keith Whitwell. 915G, 915GM, 945G, 945GM, 965G, 965Q and 946GZ support added by Alan Hourihane and Keith Whitwell. Lid status support added by Alan Hourihane. Textured video support for 915G and later chips, RandR 1.2 and hardware modesetting added by Eric Anholt and Keith Packard. EXA and Render acceleration added by Wang Zhenyu. TV out support added by Zou Nan Hai and Keith Packard. 965GM, G33, Q33, and Q35 support added by Wang Zhenyu.
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- SUPPORTED HARDWARE
- CONFIGURATION DETAILS
- OUTPUT CONFIGURATION
- MULTIHEAD CONFIGURATIONS
- TEXTURED VIDEO ATTRIBUTES
- REPORTING BUGS
- SEE ALSO
- AUTHORS
This document was created by man2html, using the manual pages.
Time: 05:33:53 GMT, December 24, 2015


This demo uses the Basis C++ transcoder (compiled to Javascript using Emscripten) to transcode a .basis file to FORMAT Thanks to Evan Parker for providing webgl-texture-utils and this test bed.
.basis file:
Use Container Independent Transcoding API's:
NOTE: Your browser does not support several compressed texture format, so using RGB565.


pumpkin_roll(5) - [RECIPES] pumpkin roll (LICENSE:PD)
Description
Directions
Recipe Tip
Libbys Pumpkin RollPumpkin cake, also called pumpkin roll, is easy to make and sure to please, perfect for Thanksgiving or Christmas parties.  Grease 15x10x1-inch jelly-roll pan; line with parchment or waxed paper. Grease and flour paper; set aside. Arrange clean thin, cotton kitchen towel on counter; sprinkle with powdered sugar.
Combine flour, baking powder, baking soda, cinnamon, cloves and salt in small bowl. Combine eggs and sugar in large bowl; beat until thickened. Add pumpkin; beat until well mixed. Stir in flour mixture. Spread batter evenly into prepared pan. Sprinkle with walnuts, if desired.
Bake for 13 to 15 minutes or until center springs back when lightly touched. Immediately loosen cake from edges of pan; invert onto prepared towel. Remove pan; carefully peel off paper. Roll up cake in towel while hot, starting with 10-inch side. Cool completely on wire rack.
Beat cream cheese, 1 cup powdered sugar, softened butter and vanilla in small bowl until smooth. Carefully unroll cake; remove towel. Spread cream cheese mixture over cake. Reroll cake. Wrap in plastic food wrap; refrigerate at least one hour. Sprinkle with powdered sugar before serving, if desired..
Nutrition Facts (1 serving)
o Be sure to put enough powdered sugar on the towel before rolling up cake so it will not stick. Recipe courtesy of NESTL USA and www.VeryBestBaking.com.
o Calories: 400 o Fat: 24g o Cholesterol: 105mg o Sodium: 290mg o Carbohydrates: 41g o Dietary Fiber: 2g o Protein: 7g I was running short of time so I let the baked pumpkin cool flat on the towel and then cut it in 3 pieces and layered it will the filling!! SO EASY if you are afraid of making a pumpkin roll! and always a hit!!Posted Dec 09 2013 by jo
Fantastic treat to have for Thanksgiving week. I also make toasted cinnamon pecans to sprinkle over the roll and around the serving plate, which adds a nice autumn flavor to it as well.Posted Dec 17 2011 by Kimi added 2-4 drops of orange extract instead of vanilla, and it was excellent, made it seem a little "lighter" when eating it, and sooo refreshing.
This cake was delicious!! I made it for Thanksgiving, and there was none left. However, I only added 2/3 cups sugar to the cake, and added an extra 1/4 cup pumpkin. Also, for the frosting, I added a little more milk to make it more creamy. It was very good and delicious though.Posted Nov 24 2011 by Nadja
I make this pumpkin roll every holiday, and Birthdays and it is the best out there! I usually double stuff it with the cream cheese and walnut filling tho.Posted Nov 20 2011 by SandraI have been making these for years! I make several for the holidays starting with Thanksgiving and freeze them, this makes slicing so much easier. I can slice off what I need and keep the rest frozen, doesnt take long for it to thaw and be enjoyed. One thing is that the cake always cracks, sometime splitting completely when unrolling, not sure why but it doesnt affect the flavor
I have been making these pumpkin rolls for years. I add crushed walnuts to some for a twist. I slice them and freeze them so that they can be pulled out and thawed with ease.Posted Oct 15 2011 by GingerTHis is really not difficult to make, just time consuming. Preparation of the pans and towels before beginning is key. 1 Large can of Libbys pumpkin makes 5 rolls.
I have been doing this roll for about 8 years and my kids love it. Gotta watch the calories though. Definitely not for a low fat diet. I also freeze my sliced rolls and put them in Tupperware to protect flavor.  Using a sifter, cover the towel liberally with powdered sugar--about 1/4 inch. The more powdered sugar on the towel, the easier it is to unroll the pumpkin roll without cracks. Make sure you allow the roll to cool for at least 30 to 35 minutes before unrolling. If the roll should crack...not to worry....sprinkle the roll with powdered sugar and nobody will see the crack.
| Nemo Release 3.1 | pumpkin_roll (7) | July 22, 2023 |


Why do I get a java.lang.NullPointerException
when I try to marshal a document?
Does JiBX work with other bytecode modification techniques, such as JDO or Hibernate?
Which JDK versions are supported by JiBX?
Is there a DTD or schema available for the binding definitions?
I want to use JiBX data binding with Axis2. How can I learn more about this combination?
Q. What does it mean when I get
java.lang.IncompatibleClassChangeError
thrown while trying to
compile a binding?
A. This is caused by having an older version of the Apache BCEL library somewhere
in your classpath ahead of the JiBX libraries. It usually occurs when using the
Ant binding task, because Ant often includes an XSLT library named
xsltc.jar in the classpath, and this library uses BCEL. It could also
occur outside of Ant if you have xsltc.jar in your Java installation's
/lib/ext directory. xalan.jar can also cause the same problem, and
for the same reason.
Q. What does it mean when I get
org.jibx.runtime.JiBXException: Unable to access binding information for
class ...
thrown while trying to run my application with JiBX?
A. This means your class files (or at least the one for the class you asked the
org.jibx.runtime.BindingDirectory
to look up) haven't been processed
by the JiBX binding compiler. Check your build process and make sure you're
doing the binding compiler step. This problem has been known to occur in some
IDEs when the IDE uses a different location for compiled class files from what
is used by an Ant build script or manual build process.
Q. Why do I get a java.lang.NullPointerException
when I try to marshal a document?
A. The most likely cause is that you've got a null
value
for an object that's not marked as optional in the binding definition. JiBX
trusts what you tell it, so if you don't say an object property is optional the
generated code won't check for a null
. To isolate the cause of this
type of problem, look through the stack trace (starting at the top) for the
first class name from your code. This will normally be the class that contains
the null property. You can then verify the binding definition for that class. If
it's not obvious which property is causing the problem, add a pre-get
method to that class for debugging purposes which checks if any of the
non-optional object properties used by the binding are null
(throwing an exception when it finds a null
, with any added
information you want to see). This will let you find out all the details of the
problem so that you can fix either the code or the binding, whichever is wrong.
Q. How can I control the package used for the classes
generated by JiBX (including the binding factory class or classes, and the
JiBX_MungeAdapter.class
)?
A. You can control the package used for the binding factory class for a
binding by using the package attribute of the binding element. The
JiBX_MungeAdapter.class
is only generated if needed. When needed,
it's created in the package of the first mapping class which is both
modifiable (a class defined in its own file, rather than in a jar file) and not
an interface. If you need this to be in a particular package (as may happen when
you're binding classes that have package access), include a mapping for
one of the classes in this package before any other mappings in the
binding definition, and if you're compiling more than one binding make the one
with this mapping the first one in the list. If necessary, you can
compile bindings in multiple sets to get more than one
JiBX_MungeAdapter.class
in different packages. This only works if
you have bindings with no overlapping packages, though - otherwise running the
binding compiler twice with different sets of bindings will cause information
from the first set to be lost.
Q. Does JiBX work with other bytecode modification
techniques, such as JDO or Hibernate?
A. Yes, JiBX works well with other frameworks which build on bytecode
modification. In the case of JDO you'll generally need to run the JiBX binding
compiler before you run the JDO bytecode enhancement, since the latter may need
to intercept field accesses from the JiBX code. In the case of Hibernate this is
not an issue, since Hibernate only uses runtime bytecode enhancements; however,
you will generally need to have JiBX use get/set methods rather than directly
access fields with working with Hibernate.
Q. Which JDK versions are supported by JiBX?
A. The JiBX runtime and binding compiler have been tested on JDK versions
1.3-1.6. There are some minor differences on the build
for JDK 1.3, but these differences do not effect the runtime operation. The new
JiBX tools introduced with the 1.2 release () require JDK 1.4.1 or higher.
Q. Is there a DTD or schema available for the binding
definitions?
A. The /docs directory of the distribution includes both a DTD
(binding.dtd) and an XML schema (binding.xsd) for the binding
definitions. These will hopefully be kept up to date, but the definitive
reference for the binding definition format is the HTML
documentation.
Q. I want to use JiBX data binding with Axis2. How can
I learn more about this combination?
A. There's an Axis2 subproject page on this site which
provides some basic information and links, and that page will be expanded to
include more information for the upcoming JiBX 1.2 beta release. Beyond that, I offer an
Apache Axis2 training
class that covers all three major data binding frameworks supported by Axis2,
including JiBX. Depending on your needs, the class can be customized to provide
more in-depth coverage of the JiBX framework, and can also include coverage of the
JiBX/WS web services support. This class can also be combined with my
SOA developers training
class for organizations that are moving to a SOA structure and want to use
JiBX in this context.
Q. Where can I find more information or examples?
A. There are
searchable archives for the JiBX mailing lists, at the Mail Archive (jibx-users
and jibx-devs)
and MARC: Mailing List Archives at AIMS
(jibx-users,
jibx-devs, and
jibx-cvs). You're
welcome to ask questions on the mailing lists (especially the jibx-users
list), but it's always a good idea to check the archives first before asking a
usage question, just in case it's already been discussed. The archives are
public, but you must subscribe to each list before you can post to that list.


title = "Event" url = "/event" layout = "dashboard" is_hidden = 0 [listEvents] eventsPerPage = 6 == addCss('assets/css/custom-autocomplete.css'); } ?> ==


UX TASKS
While clients can not be shared, in the past few months I have also done the following UX work:
- Heuristic UI Audits- audit of a software testing service client facing product
- Interactive Data Visualization for a complex internal sales sheet representing multiple product levels
- User Research/Interviews
- User Flows- Revised flows for a large international sporting goods brand
- Site Content Analyses and Mapping
- Information Architecture
- Wireframe and Prototyping


Implements a very fast C++ algorithm to quickly bootstrap receiver operating characteristics (ROC) curves and derived performance metrics, including the area under the curve (AUC) and the partial area under the curve as well as the true and false positive rate. The analysis of paired receiver operating curves is supported as well, so that a comparison of two predictors is possible. You can also plot the results and calculate confidence intervals. On a typical desktop computer the time needed for the calculation of 100000 bootstrap replicates given 500 observations requires time on the order of magnitude of one second.
| Version: | 0.4.0 |
| Depends: | R (≥ 3.2.0), ggplot2, methods, stats, utils |
| Imports: | Rcpp |
| LinkingTo: | Rcpp |
| Published: | 2016-06-21 |
| Author: | Erik Peter [aut, cre] |
| Maintainer: | Erik Peter <jerikpeter at googlemail.com> |
| BugReports: | http://github.com/erikpeter/fbroc/issues |
| License: | GPL-2 |
| URL: | http://www.epeter-stats.de/roc-curve-analysis-with-fbroc/ |
| NeedsCompilation: | yes |
| Materials: | README NEWS |
| CRAN checks: | fbroc results |
| Reference manual: | fbroc.pdf |
| Package source: | fbroc_0.4.0.tar.gz |
| Windows binaries: | r-devel: fbroc_0.4.0.zip, r-release: fbroc_0.4.0.zip, r-oldrel: fbroc_0.4.0.zip |
| OS X binaries: | r-release: fbroc_0.4.0.tgz, r-oldrel: fbroc_0.4.0.tgz |
| Old sources: | fbroc archive |
Please use the canonical form https://CRAN.R-project.org/package=fbroc to link to this page.


It doesn't matter if data is being migrated from SQL to NoSQL, from flat files to key-value store, or from XML to an object database, or every permutation of any data store to any other data store. What stays constant is the fact that data migrations are scary and painful. Without the right strategy, a big data migration will leave you with inconsistent data, strange errors, and very angry users. Read on for a data migration checklist that'll save you days of headache.
It doesn't matter if data is being migrated from SQL to NoSQL, from flat files to key-value store, or from XML to an object database, or every permutation of any data store to any other data store. What stays constant is the fact that data migrations are scary and painful. Without the right strategy, a big data migration will leave you with inconsistent data, strange errors, and very angry users. Read on for a data migration checklist that'll save you days of headache.
Before even considering a massive destructive mutation of your data, you should have working backups. The keyword is "working". Take production dumps of your data, and make sure you can load the same data on a cloned environment. If anything goes wrong when migration day comes along, these backups will be your last line of defense. Backups are also useful for doing practice runs of a migration.
Create a logger that logs to a separate place from your application logs that's specific for the migration. When the migration is running, the logger should warn on strange data and error on exceptional cases. To keep the log useful, it's important not to flood it with debugging information. Log only the most important details needed for troubleshooting problems: a timestamp, an id reference to the failing record, and a brief description of the failure reason.
Regardless of whether the destination data store supports transactions or not, the migration should always define an invariant for when a record is successfully imported. If this invariant is broken, then whatever has been done to break the invariant should be undone so that your data isn't in some zombie half consistent state.
Not strictly the definition of idempotence, but similar to maintaining consistency, your code should be able to handle re-migrating the same data. If the migration crashes halfway, having this property allows you restart and import again without worrying about weird state issues.
Having atomicity and idempotence lets your migration be split up into smaller migrations. Instead of migrating a million records in an all-or-nothing migration and crossing your fingers, you can split them up into small 500 record batches. If any single batch fails, you can redo just that single batch, rather than redo the entire migration. This also allows you to balance the migration across more resources like multiprocessors, different servers, and different slave databases.
After a migration is complete, it's important to be able to validate that everything is still working. This means running your test suite, your integration tests, and also logging in as existing users and clicking around.
Running a migration with scheduled downtime is hard enough as it is, but in certain applications, a big chunk of downtime is unacceptable. If this is the case, then it's critical to add bookkeeping code that tracks which records has been migrated and which haven't. This allows you to query and incrementally upgrade parts of your system while co-existing with old data and old code.
Data migrations will always be a chore. But with the right strategy, at least it'll be one that can be finished, rather than something that drags along and repeatedly slows down your whole team.


assertThat($someString, is(equalToIgnoringCase(“A sTrIng”))); assertThat($someString, containsString($subString)); assertThat($someString, startsWith(“foo”));


Next Pattern
Wait
Foreground Color
Background Color
Frequency
Brightness
Foreground Color 2
Signal From the Tower
×
Wait
Wait in MS:
×
Foreground Color
Red:
Green:
Blue:
×
Background Color
Red:
Green:
Blue:
×
Brightness
Brightness:
×
Frequency
Frequency:
×
Foreground 2 Color
Red:
Green:
Blue:
×
Signal From the Tower
Tower:


Agglomeration: Buffenmyer and McNaught
February 2012
Gallery I “Agglomeration” McNaught and Bufenmyer
NKG February 3-24, 2012
Opening Reception Friday February 3, 2012 5-8 pm
NK Gallery
450 Harrison Avenue #61
Boston MA 021118
Gallery hours Wed- Sat 11am – 4pm
NKG is pleased to present “Agglomeration”, an exhibition of paintings and drawings by artists Luke Buffenmeyer and Megan McNaught.
Megan McNaught’s work has been focused on formal issues of image making using strategies similar to game playing as building blocks to tap into her creativity. Her tightly planned structures using repetitive pattern, mark making, and shapes result in a complexity that creates a dynamic geometry that takes on a life of its own. Luke Bufenmeyer’s work has entailed intuitively creating objects that make substance of his intellectual ideas and his feelings. His whimsical shapes and invented worlds using varied media address political, social, and historical issues.
In “Agglomeration” MacNaught and Bufenmeyer merge their individuality to create something bigger than themselves as a collaborative experiment to see what combining two different approaches to image making would yield. The combination creates unexpected results and a sense of the world with an endless source of surprises. The unpredictability of the work as it is created becomes a fascinating game of transformation both visually and intellectually.
Meghan McNaught, Assistant Professor of Interdisciplinary Arts and Fine Arts, Chester College of New England, received her BFA from the Massachusetts College of Art and her MFA from University Massachusetts Amherst.
Luke Buffenmyer, Assistant Professor of Photography, Media Arts and Design at Chester College of New England, received his BFA from the Rhode Island School of Design and his MFA from the School of Visual and Performing Arts at Syracuse University.


Subreddit
·
Top 10s
·
Frequently Asked Questions
Mutual Fund and Unit Investment Trust Fund Returns -
Web
·
Google Sheet
·
Graphs
Listed Company Financials


LAN Academy Acknowledgments
LAN Academy is made possible by our talented team of volunteers and the wealth of open source software and tutorials available online.
The site was architected by John Williams. Learn.php was a joint effort of John Williams and Eric Marriott, started sometime in July 2013 in rural Karnataka, India while doing research for LAN Academy.
The current style is based off the open source "kilroy" stacey app theme.


Documentation for Umbraco 7
Contributing
The documentation project is open source and hosted on Github. If you have any corrections or additions to the documentation clone the project and make a pull request. Guidelines on how to contribute to the documentation.
Umbraco 4 Documentation
Installation
Describes how Umbraco is installed, using either WebMatrix, Microsoft Platform Installer, or from a zip-file.
Using Umbraco
Describes Umbraco terminology, configuration files/settings & step by step guides on how to approach the different areas in Umbraco.
Developers' Reference
Templating, querying, searching and other Umbraco APIs.
Cheatsheets
Cheatsheets for easy overview of different areas like the Razor API and Views syntax.
Umbraco Add-on documentation
Documentation for the Umbraco add-ons 'Forms' and 'Courier'
Extending Umbraco
Documentation on how to extend umbraco with your own editors, trees, sections, and how to distribute those extensions as packages. (coming soon)
Development Guidelines
How to work with the Umbraco codebase.


Add Basic Toppings:
Small: $1/each, Medium & Large: $1.50/each
Add Premium Toppings:
Small: $2/each, Medium & Large: $3/each
Size: Sauce: Toppings:


WITNESS LIST Finance Committee (Subcommittee on Graduate Medical Education (Charge 4)) February 11, 2000-10:00A Medicaid GME Funding/State Resource On: Berndt, Trey (Legislative Budget Board), Austin Flack, Teri (Texas Higher Education Coordinating Board), Austin Other States Efforts on GME Funding On: Nash, Dr. Lisa (Texas Medical Association), Galveston Public Testimony On: Turner, Teri (Texas Children's Hospital), Houston Teaching Hospitals Financial Update On: Garvey, Dr. Skip (University of Texas Health Center at Tyler), Tyler Maxwell, Brian (University of Texas Medical Branch at Galveston), Galveston Mendelsohn, Dr. John (University of Texas M.D. Anderson Cancer Center), Houston Revill, Larry (University of Texas Medical Branch at Galveston), Galveston Stobo, Dr. Jack (University of Texas Medical Branch at Galveston), Galveston


--- layout: post title: 'Monkey-patching Rails: Extending Routes #2' post_id: 187 categories: - under the hood date: 2006-10-26 08:03:00.000000000 -06:00 author: Jamis permalink: 2006/10/26/monkey-patching-rails-extending-routes-2.html ---
Last Friday, I introduced my routing tricks plugin for Rails, by walking through the implementation of a routing extension that let you specify HTTP redirections via routes. Today’s article extends that plugin with a new feature: recognition by host, domain, or subdomain.
Suppose, for instance, that I wanted my blog’s admin feature to live at its own subdomain, admin.jamisbuck.org. Currently, that means I’d need the action that maps to ”/” to determine how to proceed based on the subdomain. Using this plugin, though, I could simply define my routes like this:
1 2 3 4 5 6 |
ActionController::Routing::Routes.draw do |map| map.connect "/", :controller => "admin", :conditions => { :subdomain => "admin" } map.connect "/", :controller => "blog" # ... end |
Note that I’ve defined two routes that map to ”/”, but the first is constrained by the subdomain. Any request for ”/” that comes in with a subdomain of “admin” will be routed to the admin controller. If the subdomain is not “admin”, the “blog” controller will be used instead.
You can do the same thing with :host
and :domain
, and any three of them may be regexes if you want that kind of flexibility.
Nifty! However, let’s get to the point of this article: how does this extension work its magic? Though not as trivial as the last article, it’s still remarkably simple.
The first thing we need to do, is record what the host, domain, and subdomain are for every request we’re asked to recognize. As you may or may not recall from the lesson on route recognition, one of the first things route recognition does is extract the request method from the request, via the extract_request_environment
method. Our task, then, is to extend that method:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
# jamisbuck/routing/routeset.rb module JamisBuck module Routing module RouteSetExtensions def self.included(base) base.alias_method_chain :extract_request_environment, :host end def extract_request_environment_with_host(request) env = extract_request_environment_without_host(request) env.merge :host => request.host, :domain => request.domain, :subdomain => request.subdomains.first end end end end |
As you’ll see shortly, we’ll extend the RouteSet
class with the RouteSetExtensions
module. (That alias_method_chain
method is a handy trick, defined in ActiveSupport: it just aliases extract_request_environment
to extract_request_environment_without_host
, and then aliases extract_request_method_with_host
to extract_request_method
. It’s a very common idiom in Rails—you’ll see it everywhere.)
Once we’ve extracted that data from the request, we need to alter the routines that generate the route recognition code, such that they now need to take into consideration the new data. This is easily done, as it happens. We just need to extend the Route#recognition_conditions
method:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
# jamis_buck/routing/route.rb module JamisBuck module Routing module RouteExtensions def self.included(base) base.alias_method_chain :recognition_conditions, :host end def recognition_conditions_with_host result = recognition_conditions_without_host result << "conditions[:host] === env[:host]" if conditions[:host] result << "conditions[:domain] === env[:domain]" if conditions[:domain] result << "conditions[:subdomain] === env[:subdomain]" if conditions[:subdomain] result end end end end |
This bit simply appends up to three new comparisons to the results
array. That array (as you may or may not recall) gets joined together with “&&”, and set in an “if” statement at the top of the generated recognition method. We can see this by looking at the Route#recognize
method that gets generated for the “admin” route:
1 2 3 4 5 6 |
def recognize(path, env={}) if (match = /\A\/?\Z/.match(path)) && conditions[:subdomain] === env[:subdomain] params = parameter_shell.dup params end end |
It just checks the path, to see that it is ”/” or ””, and then compares the subdomain of the request (in the env
variable) to the subdomain in the conditions for the route (in the conditions
variable). If all matches, the parameter shell for the route is returned. Beautiful!
Ok, one last thing: we can’t forget to tie the bits together and plug them into the routing code itself.
1 2 3 4 5 6 7 8 9 10 |
# init.rb require 'jamis_buck/routing/routeset' require 'jamis_buck/routing/route' require 'action_controller/routing' ActionController::Routing::RouteSet.send :include, JamisBuck::Routing::RouteSetExtensions ActionController::Routing::Route.send :include, JamisBuck::Routing::RouteExtensions |
And thus, gentle readers, does the proverbial “fat lady” sing. Note, though, that this is really only half of the solution, as it doesn’t handle route generation at all. However, it does demonstrate how simple it can be to extend route recognition to include aspects of the request and its environment.
As before, you can check out the entire plugin from my subversion repository.


A few weeks ago, on 20th February, Hooting Yard provided full instructions for Saving Your Swan in the event of a bird flu pandemic. Clearly, the gritty northern folk who live in Cellardyke up in Scotland took absolutely no notice.
I love the way the Daily Mail manages to inject a note of patriotic fervour.  I hope they sent a reporter to hand-deliver a message of condolence to our bereaved monarch (see Frequently Asked Question, yesterday).


Classes
The following classes are available globally.
-
Webhook HTTP client.
See moreDeclaration
Swift
public class WebhookClient
-
Team HTTP client
See moreDeclaration
Swift
public class TeamClient
-
A Call represents a media call on Cisco Spark. The application can create an outgoing call object by calling phone.dial function:
let address =<EMAIL_ADDRESS>let localVideoView = MediaRenderView() let remoteVideoView = MediaRenderView() let mediaOption = MediaOption.audioVideo(local: localVideoView, remote: remoteVideoView) let call = spark.phone.dial(address, option: mediaOption) { success in if success { // success } else { // failure } }
The application can receive an incoming call object via …
code
See
Phone API about how to create calls.See moreSince
1.2.0Declaration
Swift
open class Call
-
Storage class that uses the device keychain
See moreDeclaration
Swift
public class JWTAuthKeychainStorage: JWTAuthStorage
-
Membership HTTP client.
See moreDeclaration
Swift
public class MembershipClient
-
Phone represents a Cisco Spark calling device. The application can obtain the phone object from Spark object and use phone to call other Cisco Spark users or PSTN when enabled. The phone must be registered before it can make or receive calls.
spark.phone.register() { success in if success { ... // Successfully registered device } else { ... // Device was not registered, and no calls can be sent or received } }
See moreSince
1.2.0Declaration
Swift
public class Phone
-
The CallNotificationCenter class is used to add & remove call observer.
See moreDeclaration
Swift
public class CallNotificationCenter
-
Declaration
Swift
public class MessageClient
-
An authentication strategy that uses Spark’s OAuth2 mechanism to provide access tokens
See moreDeclaration
Swift
public class OAuthStrategy: AuthenticationStrategy
-
Person HTTP client
See moreDeclaration
Swift
public class PersonClient
-
The data type include email validation and equatable implementation.
See moreDeclaration
Swift
open class EmailAddress: Equatable
-
The PhoneNotificationCenter class is used to add & remove phone observer.
See moreDeclaration
Swift
public class PhoneNotificationCenter
-
Declaration
Swift
public class JWTAuthStrategy: AuthenticationStrategy
-
Defines notifications to notify SparkSDK of calls when the application is in the background.
These notifications can be posted to
See moreNSNotificationCenter
to let SparkSDK handle background calls.Declaration
Swift
@objc public class SparkBackgroundCallNotifications: NSObject
-
Global settings for the default phone audio and video modes. These settings are not persisted.
See moreDeclaration
Swift
public class PhoneSettings
-
An OAuthStorage mechanism that uses the keychain for underlying storage
See moreDeclaration
Swift
public class OAuthKeychainStorage: OAuthStorage
-
Room HTTP client
See moreDeclaration
Swift
public class RoomClient
-
Spark object is the entry point to use this Cisco Spark iOS SDK. A Spark object must be created with one of the following AuthenticationStrategy.
- OAuthStrategy - this should be used when Spark is to be authenticated as a registered Cisco Spark user.
let clientId = "Def123456..." let clientSecret = "fed456..." let scope = "spark:people_read spark:rooms_read spark:rooms_write spark:memberships_read spark:memberships_write spark:messages_read spark:messages_write" let redirectUri = "MyCustomApplication://response" let oauthStrategy = OAuthStrategy(clientId: clientId, clientSecret: clientSecret, scope: scope, redirectUri: redirectUri) let spark = Spark(authenticationStrategy: oauthStrategy) ... if !oauthStrategy.authorized { oauthStrategy.authorize(parentViewController: self) { success in if !success { print("User not authorized") } } }
- JWTAuthStrategy - this should be used when Spark is to be authenticated as a CIsco App ID.
let jwtAuthStrategy = JWTAuthStrategy() let spark = Spark(authenticationStrategy: jwtAuthStrategy) ... if !jwtAuthStrategy.authorized { jwtAuthStrategy.authorizedWith(jwt: myJwt) }
Attention
All APIs on Cisco Spark iOS SDK are expected to run on the application’s main thread.See moreSince
1.2.0Declaration
Swift
public class Spark
-
TeamMembership HTTP client.
See moreDeclaration
Swift
public class TeamMembershipClient


Kings Premier League
Register Now
Auctions 2020 Date
Watch Live on January 6
Auction List Announced
Teams 2020
Teams Announced
Tournament Dates
Coming Soon
©2019 Kings Premier League. Made by Rohan Pal
Instagram
Facebook


lingvo.tasks.mt.model module¶
MT models.
-
class
lingvo.tasks.mt.model.
MTBaseModel
(*args, **kwargs)[source]¶ Bases:
lingvo.core.base_model.BaseTask
Base Class for NMT models.
-
ComputePredictions
(theta, batch)[source]¶ Computes predictions for
input_batch
.The output can be in the form of probablistic distributions, e.g., softmax logits for discrete outputs, mixture of logistics for continuous values, or regression values.
For training/evaluation, the output will be used for computing loss and gradient updates, including comparing predicted distributions between teacher and student for distillation. During inference the output can be used to compute final outputs, perhaps with sampling.
Parameters: Returns: Predictions, either a single Tensor, a
NestedMap
, or a namedtuple.
-
ComputeLoss
(theta, batch, predictions)[source]¶ Computes loss and other metrics for the given predictions.
Parameters: - theta – A
NestedMap
object containing variable values of this task. - input_batch – A
NestedMap
object containing input tensors to this tower. - predictions – The output of
ComputePredictions
.
Returns: A dict containing str keys and (metric, weight) pairs as values, where one of the keys is expected to be ‘loss’.
- theta – A
-
_PostProcessBeamSearchDecodeOut
(dec_out_dict, dec_metrics_dict)[source]¶ Post processes the output from
_BeamSearchDecode
.
-
CreateDecoderMetrics
()[source]¶ Creates a dict of decoder metrics for
PostProcessDecodeOut
to update.Returns a dict mapping from string keys to
BaseMetric
objects.
-
-
class
lingvo.tasks.mt.model.
TransformerModel
(*args, **kwargs)[source]¶ Bases:
lingvo.tasks.mt.model.MTBaseModel
Transformer Model.
Implements Attention is All You Need: https://arxiv.org/abs/1706.03762
-
PostProcessDecodeOut
(dec_out, dec_metrics)[source]¶ Post-processes decoder out and updates contents of
decode_metrics_dict
.Parameters: - decode_out_dict – A dictionary of Tensors fetched.
- decode_metrics_dict – A dict mapping from string key to
BaseMetric
object as created byCreateDecoderMetrics
.
Returns: output_key_value_pairs - a list of (key, value) pairs that can be saved (i.e. of type str, bytes, or unicode).
-


Connected clients
Total messages sent
Average rate (messages/second)
Last 5 minutes rate (messages/second)
Service Uptime
Average time to establish connection
Maximum time to establish connection
Collected samples
Average notification latency
Maximum notification latency
Collected samples
Sorry, data is not available yet.


hepatitis HCV HBV infections Hepatitis chronic Health health viral virus Geisinger case (., patients positive infection reported laboratory {border-style United persons acute px;} #ffffff;} PDoH Pennsylvania []. underreporting Viral criteria living Case Pennsylvania, disease pathogens state study Criteria PDoH, sciences Department Disease data patient test public reporting CDC CDC/CSTE Control Medicine months Biology Chronic Diagnosis National Ref States characteristics diagnosed following (Table Accessed Available Centers Classification Laboratory age at: infected infections, CHeCS Definition States, Underreporting clinical confirmed genotype px; result surveillance unreported {font-family :–. Antibodies Patients Prevention. RNA and/or antigen diagnosis font-size infection. life liver meet n/a prevalence ratio review Box Confirmed Infect Liver Microbial Pennsylvania. Sciences access association care cohort departments diseases double; having infection, largely percentage rates time used viruses: (HBV) (HCV) (including Acute Clin DNA Electronic HBsAg ICD- Immune Infectious March Medical Pennsylvania’s Surveillance alanine analysis antibody associated border-color border-width cases confidence consistent cut-off definitions diagnosis. does high infections. initial meets positive, primary-care qualitative, quantitative records reports select signal solid; study, {font-style {font-weight (IgM Adjusted America[], Asian/Pacific CDC. Clinical Data Dis; Epidemiology Flaviviruses HBeAg Health, Health; Hepacivirus: Organisms Persons Rural SOURCE: Viruses WNH acid aminotransferase apart assay bold burden codes courier; current em; findings group, hepatitis: infectious initially medical million non-Hispanic participants, patient’s population progress proportion pt;} race/ethnicity, status, surface tested true variables virus, viruses went year years,


GUID
Path
Name
Type
State
Connect?
Error
Security
Tech
Activation
Roam
Frequency
Strength
GUID
Path
Name
Type
Profile
Visible
ONC Source


Iann Dior Makes "Industry Plant" Debut
Iann Dior shares new album.
by Milca P.Industry Plant
Iann Dior
Editor Rating: HOTTTTT
User Rating: n/a - 0% (0)
With his rapid ascent being marked by accusations of "industry plant" status, Corpus Christie-bred artist Iann Dior has officially dropped off his debut album titled Industry Plant.
Arriving via 10K Projects, Industry Plant is equipped with 15 total tracks as featured appearances are shared between Travis Barker, Trippie Redd, and Gunna among others.
Speaking with Zane Lowe, Dior discussed the new project, acknowledging the quick adjustment he had to make for such a rapid explosion in popularity and success, noting that his move to Los Angeles from Corpus Christie, Texas marked the first time he had ever "seen the world."
"I didn't know what an Uber was," he told the Beats 1 host.
Get into Industry Plant below.


| Front Page / Tutorial: Metafunctions and Higher-Order Metaprogramming / Handling Placeholders / The apply Metafunction |
Invoking the result of lambda is such a common pattern that MPL provides an apply metafunction to do just that. Using mpl::apply, our flexible version of twice becomes:
#include <boost/mpl/apply.hpp> template <class F, class X> struct twice : mpl::apply<F, typename mpl::apply<F,X>::type> {};
You can think of mpl::apply as being just like the apply1 template that we wrote, with two additional features:
While apply1 operates only on metafunction classes, the first argument to mpl::apply can be any lambda expression (including those built with placeholders).
While apply1 accepts only one additional argument to which the metafunction class will be applied, mpl::apply can invoke its first argument on any number from zero to five additional arguments. [5] For example:
// binary lambda expression applied to 2 additional arguments mpl::apply< mpl::plus<_1,_2> , mpl::int_<6> , mpl::int_<7> >::type::value // == 13
| [5] | See the Configuration Macros section of the the MPL reference manual for a description of how to change the maximum number of arguments handled by mpl::apply. |
Guideline
When writing a metafunction that invokes one of its arguments, use mpl::apply so that it works with lambda expressions.


{% extends "base_uikit.html" %} {% block content %} {% load static %} {% load sass_tags %}
The UMSI Data4Good center brings together non-profit organizations' data into larger datasets for benchmarking and trend analysis. Putting data in the hands of nonprofits contributes to the body of knowledge about a broad scope of development and relief programs, which in turn will lead to better decision-making in nonprofit work.
The Data4Good center values transparency and equal access to information and data analysis that has the potential to impact lives through nonprofit organizations.


Installing Kahina for TRALE
Dependencies
To obtain, build and run Kahina for TRALE, you need:
- SICStus Prolog 3 or 4, with Jasper installed (see below)
- access to the TRALE repository (ask Gerald Penn)
- Subversion
- GNU Make or similar
- Apache Ant
Installing SICStus Prolog with Jasper
TRALE requires SICStus Prolog, so you need to buy a license and install it if you have not done so already. It supports SICStus Prolog 3 (SP3) and, experimentally, SICStus Prolog 4 (SP4).
Kahina for TRALE also requires that the existing installation of SICStus Prolog include the Prolog-Java interface Jasper, set up with a version 6 or higher Java Development Kit (JDK).
You may have to modify your LD_LIBRARY_PATH before installation to ensure SICStus Prolog can find libjvm.so. Under Ubuntu 13.04, I added this line to my ~/.bashrc:
export LD_LIBRARY_PATH=/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/client:$LD_LIBRARY_PATH
The successful installation then looked like this (a successful run of the SP4 installation script looks similar):
ke@apis:~/install/sp-3.12.11-x86-linux-glibc2.5$ ./InstallSICStus --all-questions SICStus Prolog Release 3 ======================== http://www.sics.se/sicstus/ --------------------------------------- Binary Distribution Installation Script --------------------------------------- This script will install SICStus Prolog 3.12.11 on your computer. Before proceeding, make sure that you have downloaded the correct distribution and that you have your licensing information at hand, as you will be prompted for site-name, license code, and expiration date during the installation. It is also recommended that you read the Release Notes before installing SICStus Prolog. The Release Notes can be found online at http://www.sics.se/sicstus/docs/ During the installation, a cache-file (install.cache) will be created which will store your answers to be used as defaults if you need to run the installation script again. You may safely delete this file if you wish. The installation script will ask a couple of questions regarding the installation. Most of these questions have a default alternative in square brackets ([]). Pressing return will give you the default answer. If you do not understand the question, the default answer will usually do what you want. Note: You must have Perl installed and available in your PATH. Perl is available for free from www.cpan.org. Typically Perl is already installed. Report bugs and other problems to SICStus Support using http://www.sics.se/sicstus/bugreport/bugreport.html Install SICStus Prolog 3.12.11 [yes] ? Checking installation cache... install.cache Where do you want to install SICStus [/home/ke] ? Creating uninstall script... Decrypt key [xxxxxxxxxxxx] ? You should now enter your site-name, license-code, and expiration date. Sitename [Kilian Personal] ? License-code [xxxx-xxxx-xxxx-xxxx-xxxx] ? Expiration date [permanent] ? Install the pre-built binaries (chose "no" for full installation, or "help") [no] ? The script will now ask you for some information about external software packages. If you leave the answers blank, the script will try to determine the information automatically. Do you wish to install the Tcl/Tk interface (library(tcltk)) [no] ? Do you wish to install Jasper (the Java interface) [yes] ? For the Java interface you should now specify the 'installation path' of the Java installation. E.g. if the path to the java compiler is /usr/local/jdk/bin/javac, the 'installation path' is probably /usr/local/jdk. Note that this is somewhat platform dependent. In case of problems you should consult the installation instructions for your Java installation to find out what the 'installation path' is. Specify JDK installation path, e.g., /usr/jdk1.2.2 (or leave blank) [/usr/jdk1.2.2] ? /usr/lib/jvm/java-7-openjdk-i386 (This information is displayed regardless of the JDK installation path specified.) NOTE: About JDK 1.3.X and later Read *important* compatibility information in the release notes in Section "Supported Java Versions". NOTE: About Java location. By default the location of Java is embedded in the SICStus development system executable (sicstus) or the jasper foreign resource. This makes it possible for library(jasper) to find the Java libraries (e.g., libjvm.so) without setting LD_LIBRARY_PATH. See the release notes. Embed JDK paths for library(jasper) (recommended) [yes] ? Do you wish to install the Berkeley DB module (library(bdb)). [no] ? Specify the path to your C compiler (or leave blank) ? Specify the path to your C++ compiler (or leave blank) ? *************************************************************** The installation will proceed without further user interaction, unless there are errors. *************************************************************** Configuring system. This may take a few minutes... done. Installation package was built for Glibc 2.5. This systems uses Glibc 2.17. SICStus is built and distributed for several versions of Glibc. If there is a version of the SICStus installation package corresponding to the version of Glibc installed on your machine, you should use that installation package. Attempt an installation anyway [no] ? yes Continuing despite wrong Glibc version... Decrypting sicstus.tar.compress.crypt... ok. Unpacking sicstus.tar... (please wait) ok. Copying files to /home/ke. This may take a few minutes... Installing documentation into /home/ke/lib/sicstus-3.12.11 done. Creating development system symlinks... Creating development system binary... done. Creating copies of SICStus run-time for multiple run-time support Creating spdet and spxref... done. Creating save-dumps... done. Compiling license file... Performing final link step for the Jasper module... Linking jasper.so... ok. Linking jasper.s.o... ok. Creating libspnative.so... ok. Completing uninstall info... Cleaning up... Installation complete. The SICStus development system has been installed as: /home/ke/bin/sicstus The documentation can be accessed locally by opening the URL: file:/home/ke/lib/sicstus-3.12.11/doc/html/ or on the SICStus website: http://www.sics.se/sicstus/docs/ Uninstall by running /home/ke/install/sp-3.12.11-x86-linux-glibc2.5/UnInstallSICStus
Obtaining TRALE
Current versions of TRALE contain a new version of TRALE's source-level debugger, called trale-sld, that uses Kahina as a GUI. Check out the latest version of TRALE from the Subversion repository. To do so, open a shell, go to the directory under which you want your TRALE installation to live, and then run:
svn checkout<EMAIL_ADDRESS>trale
This will create a directory called trale and checkout TRALE into it.
Note: As of this writing, a bug prevents trale-sld from working when SICStus Prolog 3 is used. You may try to use an older TRALE revision by passing the option -r 260 to the svn checkout command to work around this for the moment.
Obtaining Kahina
Now run:
cd trale git clone https://github.com/texttheater/kahina
This will create a directory kahina inside the trale directory.
Building Kahina
After checking out TRALE, go into the trale directory and run:
make kahina-build
The first time, this will fail and instruct you to create a file build.properties in the kahina subdirectory, pointing to the jasper.jar file of your SICStus Prolog installation. Follow the instructions, then just re-run the command.
Updating Kahina to a new version
Whenever a new version of Kahina is released, you can obtain it from the trale/kahina directory like this:
git pull
Then, from the trale directory, run:
make kahina-build
Using TRALE with Kahina
You start TRALE from the command-line by running the trale script found in the trale directory. Before running it, make sure that the environment variable TRALE_HOME is either not set or set to the path of the trale directory.
First steps
After starting TRALE using trale, activate the debugger by setting the debugger flag to on:
ale_flag(debugger,_,on).
You can try if it works by using the predicates dcompile_gram/1 to compile a TRALE grammar and drec/1 to parse a sentence, or (experimentally) dquery/1 to resolve a query in the ALE programming language. Each of these commands should bring up the Kahina GUI (you can read more about their function and usage in the TRALE documentation). Alternatively, you can just ask the following query:
dgo.
This will start the GUI but make the Prolog prompt inaccessible, in return giving you the possibility to start compilation processes and parsing via the Parse menu in the GUI. Closing the GUI will return you to the Prolog prompt. You can do this at any time while debugging, resulting in the abortion of the current compilation/parsing/query resolution process.
Using TRALE's XEmacs-based debugger
TRALE's Kahina-based source-level debugger is the successor of an older XEmacs-based source-level debugger, which is still available by setting the TRALE_DEBUGGER environment variable to xemacs before starting TRALE, like so:
export TRALE_DEBUGGER=xemacs trale


Latest upgrade package can be found under the following upgrade package link
Instructions for upgrading your NooBaa system to the latest version can be found in the following article
Latest OVA can be found under the following OVA link
Container deployment instructions can be found here
Please note that for containers, you don't need to provide an upgrade package, but apply the YAML with the latest tag.
If you need KVM, VHD or any other format, please let us know.
NooBaa core machine is also available on:
1) Azure marketplace - link here
2) Alibaba marketplace - link here
3) AWS marketplace - link here
4) Google marketplace - link here (online test drive on Google platform. Image available upon request).


Lebab transpiles your ES5 code to ES6/ES7. It does exactly the opposite of what Babel does. If you want to understand what Lebab exactly does, try the live demo.
Install it using npm:
Full build:
Convert your old-fashioned code using the lebab
cli tool, enabling a specific transformation:
Or transform an entire directory of files in-place:
# .js files only
$ lebab --replace src/js/ --transform arrow
# For other file extensions, use explicit globbing
$ lebab --replace 'src/js/**/*.jsx' --transform arrow
For all the possible values for --transform
option see the detailed docs below or use --help
from command line.
The recommended way of using Lebab is to apply one transform at a time, read what exactly the transform does and what are its limitations, apply it for your code and inspect the diff carefully.
These transforms can be applied with relatively high confidence. They use pretty straight-forward and strict rules for changing the code. The resulting code should be almost 100% equivalent of the original code.
function(){}.bind(this)
this
arguments
obj-method
transform)that = this
assignments{ return x; }
to => x
arrow
transform first)item
for loop variable when loop body begins with var item = array[i];
let
transform first)Array.forEach()
item
for forEach parameter when loop body begins with var item = array[i];
let
transform first)args
variable already existsargs
Array.slice.call(arguments)
obj.method.apply(obj, args)
func.apply(undefined, args)
{foo: foo}
to {foo}
NaN
properties"use strict"
directives
x = "use strict";
Math.pow()
to **
operator (ES7)
var x,y;
declaration to multiple var x; var y;
(refactor)
These transforms should be applied with caution. They either use heuristics which can’t guarantee that the resulting code is equivalent of the original code, or they have significant bugs which can result in breaking your code.
var
to let
/const
const
let
/const
declarations if neededlet
/const
are not convertedFoo.prototype.method = function(){ ... };
Foo.prototype = { ...methods... };
Foo.method = function(){ ... };
Object.defineProperty()
Child.prototype = new Parent()
util.inherits(Child, Parent);
super()
super.method()
var foo = require("foo")
to import foo from "foo"
var bar = require("foo").bar
to import {bar} from "foo"
var {bar} = require("foo")
to import {bar} from "foo"
module.exports = <anything>
to export default <anything>
exports.foo = function(){}
to export function foo(){}
exports.Foo = class {}
to export class Foo {}
exports.foo = 123
to export var foo = 123
exports.foo = bar
to export {bar as foo}
require()
calls in var
declarationsconst
${...}
.toString()
and .valueOf()
a = a || 2
a = a || 2
a = a ? a : 2
a = a === undefined ? 2 : a
a = typeof a === 'undefined' ? 2 : a
a = a || 2
does not produce strictly equivalent code(obj) => obj.a + obj.b
to ({a, b}) => a + b
array.indexOf(foo) !== -1
to array.includes(foo)
(ES7)
!== -1
to array.includes(foo)
=== -1
to !array.includes(foo)
>= 0
, > -1
, etcindexOf() != -1
and -1 != indexOf()
Simply import and call the transform()
function:
import {transform} from 'lebab';
const {code, warnings} = transform(
'var f = function(a) { return a; };', // code to transform
['let', 'arrow', 'arrow-return'] // transforms to apply
);
console.log(code); // -> "const f = a => a;"
The warnings will be an array of objects like:
[
{line: 12, msg: 'Unable to transform var', type: 'let'},
{line: 45, msg: 'Can not use arguments in arrow function', type: 'arrow'},
]
Most of the time there won’t be any warnings and the array will be empty.
Alternatively one can use Lebab through plugins in the following editors:
Which feature should Lebab implement next? Let us know by creating an issue or voicing your opinion in existing one.
Want to contribute? Read how Lebab looks for patterns in syntax trees.


Use client API
In the design of SOFALookout client, API is decoupled from the implementation. If you need to log the events based on the SOFALookout API, you only need to add the lookout-api
Maven dependency to the pom.xml
file in your application/project. If the dependencies (such as client dependencies or SOFABoot (Spring Boot) Starter) do not exist, the API package uses NoopRegistry automatically, to replace all the locations of which the events are logged.
1.Introduce API dependency
<dependency>
<groupId>com.alipay.sofa.lookout</groupId>
<artifactId>lookout-api</artifactId>
<version>${lookout.client.version}</version>
</dependency>
2.About ID
Compared to the traditional metrics library’s single-dimensional information description, Lookout metrics provides tag capability that supports multi-dimensional descriptions. ID class, the unique identification of Lookout metrics, consists of name and tags.
Id basicId = registry.createId("rpc.provider.service.stats");
id = basicId.withTag("service", "com.alipay.demo.demoService")
.withTag("method", "sayHi")
.withTag("protocol", "tr")
.withTag("alias", "group1");
The above is a simple example of ID introducing how to create ID and how to tag. Note that every time you tag, a new ID object is generated and returned.
Do not proactively cache Id or the specific Metric object, since Lookout’s Registry has already recorded. When using a same Id (with the same name and tags), the existing Id and its corresponding Metric object will be reused.
2.1 Priority tag (optional)
PRIORITY enumeration level: HIGH, NORMAL, LOW.
id.withTag(LookoutConstants.LOW_PRIORITY_TAG);
It is recommended that you do not add this tag, the default level will be NORMAL. The level represents the collection interval (HIGH: 2s, NORMAL: 30s, LOW: 1min).
2.2 About tags
- General tags, such as local IP, data center, and other details, will be attached and no need to be specified separately.
- In a non-SOFABoot project, you must manually add tags to the client, especially the
app
tag which specifies the app name:app=appName
. - key contains only lowercase letters, numbers, and underscores. (especially the metrics at runtime, such as Counter, Timer, and DistributeSummary) The values of a tag shall be within a stable finite set. Try to use as few tags as possible to prevent the number of metrics from exceeding the maximum limit. For example: In RPC service, the value of method’s two tags shall be as few as possible. The counterexample is that each RPC call has a separate tag-value. Therefore, the overall principle is that there should be as few custom tags as possible, and the number of sets of the values should be as small as possible. Specialized TAG name “priority” indicates priority.
- The tag key reserved by the system is
_*_
. Starting with an underscore and ending with an underscore (eg: “type” ). Do not use this format for keys, since it may be overwritten or discarded by the system.
3. Accessible Statistics (Metric) Type API
Counter
- Scenario: Number of method calls;
- Actively reported data includes: count, rate (namely qps);
- How to use:
Counter counter=registry.counter(id);
counter.inc();
Timer
- Scenario: Statistical tasks, method time-consuming, support bucket statistics
- Actively reported data includes: elapPerExec (single execution time), total time-consuming, Max time-consuming, in seconds;
- How to use:
Timer timer=registry.timer(id);
timer.record(2, TimeUnit.SECONDS);
DistributionSummary
- Scenario: such as IO traffic, support bucket statistics
- Actively reported data includes: count, total(size), max(size);
- How to use:
DistributionSummary distributionSummary=registry.distributionSummary(id);
distributionSummary.record(1024);
Gauge (real-time data observation)
- Scenario: Real-time values such as thread pools, memory values.
- Actively reported data includes: value; When the new gauge is registered in the registry, if the ID values are the same, the registry continues to use the existing ones (ignoring the new ones);
Note: It is recommended that the object observed by gauge is singleton (reuse), and it is always alive during runtime (rather than as a temporary statistic). If it is not singleton or only be alive for some time, then it must be removed from the Registry, otherwise it will affect the GC, and the external object reference it holds cannot be released.
- How to use:
registry.gauge(id,new Gauge<Double>() {
@Override
public Double value() {
return 0.1;
}
});
MixinMetric (The hybrid manager of the above basic statistics metrics)
MixinMetric is unique to Lookout and represents a mixture of multiple basic metrics. The purpose of introducing this Mixin is to optimize the transmission and storage efficiency of multiple metrics indicators for the same metric target (that is, the measurement target is consistent and the tags are consistent). For example: Various indicators of the same thread pool (total number of threads, total active count, waiting queue size).
- How to use: For example, for a service call, add multiple measurement indicators: call time-consuming, input byte count, number of calls, output byte count, etc.
//1. getOrAdd MixinMetric
MixinMetric rpcServiceMetric=registry.minxinMetric(id);
//2. getOrAdd basic component metric to use
Timer rpcTimer = rpcServiceMetric.timer("perf");
DistributionSummary rpcOutSizeMetric = rpcServiceMetric.distributionSummary("inputSize");
Top Tools
- Scenario: List the metrics information of TOP 5/10/20;
- Background: When you want to track and measure more finely, such as the request time-consuming of a SQL statement (an URL), you may need to use SQL (or URL) as a tag, such as:
Sql_execute_cost:sql=select..
Sql_execute_cost:sql=insert..
Sql_execute_cost: sql=insert2..
...
The resulting metrics will be too much. The upper limit of the total number of metrics (to avoid affecting the business) is generally at around 5000. So it is recommended to have as few tags as possible, and each tag values should be enumerated as much as possible, and the number should be as small as possible.
But if you really want to target some fine-grained problems, then it is recommended to use TopUtil (it can only record the first few data and eliminate other data).
- How to use:
TopGauger topGauger = TopUtil.topGauger(registry, registry.createId("top5sql"), 5);
topGauger.record(1000l, new BasicTag("sql1", "select1"));
topGauger.record(2000l, new BasicTag("sql2", "select2"));
...


A doodle is an unfocused or unconscious drawing made while a person's attention is otherwise occupied. Doodles are simple drawings that can have concrete representational meaning or may just be abstract shapes.
Stereotypical examples of doodling are found in school notebooks, often in the margins, drawn by students daydreaming or losing interest during class. Other common examples of doodling are produced during long telephone conversations if a pen and paper are available.
Popular kinds of doodles include cartoon versions of teachers or companions in a school, famous TV or comic characters, invented fictional beings, landscapes, geometric shapes and patterns, textures, banners with legends, and animations made by drawing a scene sequence in various pages of a book or notebook.


- damerau(String, String) - Static method in class squidpony.squidtext.StringUtils
-
Computes the Damerau-Levenshtein distance between two words.
- DamerauLevenshteinAlgorithm - Class in squidpony.squidtext
-
The Damerau-Levenshtein Algorithm is an extension to the Levenshtein Algorithm which solves the
edit distance problem between a source string and a target string with the following operations:
Character Insertion
Character Deletion
Character Replacement
Adjacent Character Swap
Note that the adjacent character swap operation is an edit that may be applied when two adjacent
characters in the source string match two adjacent characters in the target string, but in
reverse order, rather than a general allowance for adjacent character swaps.
- DamerauLevenshteinAlgorithm(int, int, int, int) - Constructor for class squidpony.squidtext.DamerauLevenshteinAlgorithm
-
Constructor.
- DARK_BLUE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_BLUE_DYE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_BLUE_LAPIS_LAZULI - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_BROWN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_CERULEAN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_CHESTNUT - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_CORAL - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_GOLDENROD - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_GRAY - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_GREEN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_INDIGO - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_KHAKI - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_PASTEL_GREEN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_PINK - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_RED - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_RED_DYE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_SALMON - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_SCARLET - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_SLATE_GRAY - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_SPRING_GREEN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_TAN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_TURQUOISE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DARK_VIOLET - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DAWN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DAYLILY - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEAD_MANS_FINGERS_SEAWEED - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DECAYING_LEAVES - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_CERISE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_CHESTNUT - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_FUCHSIA - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_LILAC - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_MAGENTA - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_PEACH - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_PINK - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_PURPLE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEEP_SCARLET - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DEFAULT_FITTING - Static variable in class squidpony.squidgrid.gui.TextCellFactory
-
- deltaX - Variable in enum squidpony.squidgrid.util.Direction3D
-
The x coordinate difference for this direction.
- deltaX - Variable in enum squidpony.squidgrid.util.DirectionCardinal
-
The x coordinate difference for this direction.
- deltaX - Variable in enum squidpony.squidgrid.util.DirectionIntercardinal
-
The x coordinate difference for this direction.
- deltaY - Variable in enum squidpony.squidgrid.util.Direction3D
-
The y coordinate difference for this direction.
- deltaY - Variable in enum squidpony.squidgrid.util.DirectionCardinal
-
The y coordinate difference for this direction.
- deltaY - Variable in enum squidpony.squidgrid.util.DirectionIntercardinal
-
The y coordinate difference for this direction.
- deltaZ - Variable in enum squidpony.squidgrid.util.Direction3D
-
The z coordinate difference for this direction.
- Demos - Class in squidpony.examples
-
Launcher for various demos and utilities associated with the SquidLib library
suite.
- Demos() - Constructor for class squidpony.examples.Demos
-
Creates new form Demos
- DENIM - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- desaturate(SColor, double) - Static method in class squidpony.squidcolor.SColorFactory
-
Returns an SColor that is the version of the provided color desaturated
the given amount.
- desaturated(SColor) - Static method in class squidpony.squidcolor.SColorFactory
-
Returns an SColor that is the fully desaturated (greyscale) version of
the provided color.
- deteriorate(double, String) - Method in class squidpony.squidgrid.shape.TiledShape
-
Deteriorates the given TiledShape on a per-cell random chance.
- DIAGONALS - Static variable in enum squidpony.squidgrid.util.Direction3D
-
An array which holds only the twelve directions that are diagonal to two
axis, but not the third.
- DIAGONALS - Static variable in enum squidpony.squidgrid.util.DirectionIntercardinal
-
An array which holds only the four diagonal directions.
- Dice - Class in squidpony.squidmath
-
Class for emulating various traditional RPG-style dice rolls.
- DijkstraAlgorithm - Class in squidpony.squidutility.graph
-
- DijkstraAlgorithm(PointGraph) - Constructor for class squidpony.squidutility.graph.DijkstraAlgorithm
-
- dim(SColor) - Static method in class squidpony.squidcolor.SColorFactory
-
Returns an SColor that is a slightly dimmer version of the provided
color.
- dimmer(SColor) - Static method in class squidpony.squidcolor.SColorFactory
-
Returns an SColor that is a somewhat dimmer version of the provided
color.
- dimmest(SColor) - Static method in class squidpony.squidcolor.SColorFactory
-
Returns an SColor that is a lot darker version of the provided color.
- Direction3D - Enum in squidpony.squidgrid.util
-
Represents the eight grid directions and the deltaX, deltaY, and deltaZ
values associated with those directions.
- DirectionCardinal - Enum in squidpony.squidgrid.util
-
Represents the eight grid directions and the deltaX, deltaY values associated
with those directions.
- DirectionIntercardinal - Enum in squidpony.squidgrid.util
-
Represents the eight grid directions and the deltaX, deltaY values associated
with those directions.
- DISAPPEARING_PURPLE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- distance(Point3D) - Method in class squidpony.squidmath.Point3D
-
Returns the linear distance between this coordinate point and the provided one.
- DISTANT_RIVER_BROWN - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DODGER_BLUE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DOVE_FEATHER_GREY - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DRIED_WEATHERED_BAMBOO - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DULL_BLUE - Static variable in class squidpony.squidcolor.SColor
-
Color constant
- DungeonGenerator - Class in squidpony.squidgrid.generation
-
Creates a map for use in creating adventure areas.
- DungeonGenerator(TiledShape[]) - Constructor for class squidpony.squidgrid.generation.DungeonGenerator
-
- DungeonGenerator(TiledShape[], String[]) - Constructor for class squidpony.squidgrid.generation.DungeonGenerator
-


pvDatabaseRPC provides an example of a pvDatabase PVRecord which also supports multiple RPC services.
pvDatabaseRPC is an example of a pvAccess server that has a PVRecord that supports Channel RPC as well as the usual operations: Channel Get, Put and Monitor and get introspection data.
It illustrates synchronous and asynchronous RPC services, selecting services based on the supplied pvRequest and using EPICS V4 to talk to an existing object which has no knowledge of EPICS and call its methods, so creating distributed objects.
It represents a device which has a 2D position setpoint and readback as well as a state. The device can be controlled through a client using RPC commands to move through a sequence of points as well as conventionally by putting to the setpoint.
In the exampleJava/pvDatabaseRPC directory
On Linux
./scripts/exampleRPCMain
On Windows:
set JAVA_HOME=C:\Program Files\Java\jdk1.8.0_25 (where your Java is)
.\scripts\exampleRPCMain.bat
When the device is in the idle state its setpoint can be set using a Channel Put in the conventional way: With pvput in your path
pvput -r positionSP.value mydevice 1 2
will set the setpoint to the point (1,2).
In the exampleJava/pvDatabaseRPC directory
On Linux
./scripts/control <command> [<args>]
E.g.
./scripts/control help
./scripts/control configure 1 2 10 20
./scripts/control run
./scripts/control pause
./scripts/control resume
./scripts/control rewind 5
./scripts/control stop
./scripts/control scan
./scripts/control abort
On Windows:
set JAVA_HOME=C:\Program Files\Java\jdk1.8.0_25 (where your Java is)
.\scripts\control.bat <command> [<args>]
E.g.
.\scripts\control.bat help
.\scripts\control.bat configure 1 2 10 20
.\scripts\control.bat run
.\scripts\control.bat pause
.\scripts\control.bat resume
.\scripts\control.bat rewind 5
.\scripts\control.bat stop
.\scripts\control.bat scan
.\scripts\control.bat abort
The device has 4 states: IDLE, READY, RUNNING and PAUSED.
The state machine is shown below (Intermediate ABORTING and STOPPING states added for clarity).
In the IDLE state the device can be controlled in a conventional way by writing to the positionSP (setpoint) field. The device's positionRB field (readback) will move to the setpoint. In other states such writes are ignored. Writes to other fields are always ignored.
From IDLE the command "configure" sets the sequence of points through which the device will move and changes state to READY.
From READY the command "run" will start the device moving through the sequence of points and set the state to RUNNING. The command "scan" does the same but blocks until completion. On successful completion in each case the state will return to READY. Any motion will stop.
In the RUNNING state "pause" pauses the scan and changes the state to PAUSED. When PAUSED, "resume" resumes the scan.
When RUNNING or PAUSED "rewind" (which takes an integer argument "n") rewinds n steps (or to the beginning if n is sufficiently large). If PAUSED the device will move to the requested rewind position when it resumes.
In any state except IDLE "stop" stops a scan and the state goes to READY. A "scan" operation in progress will return an error.
In any state "abort" stops any scans in progress (including paused scans) and the state goes to IDLE. Any configuration information is rest. Any motion will stop. A "scan" operation in progress will return an error.
The current state appears in the device's structure along with the two position fields. Each field has a time stamp. There is also a top-level time stamp.
The record's structure in full is:
structure Point positionSP point_t value double x double y time_t timeStamp long secondsPastEpoch int nanoseconds int userTag Point positionRB point_t value double x double y time_t timeStamp long secondsPastEpoch int nanoseconds int userTag epics:nt/NTEnum:1.0 state enum_t value int index string[] choices time_t timeStamp long secondsPastEpoch int nanoseconds int userTag time_t timeStamp long secondsPastEpoch int nanoseconds int userTag


Maybank Kim Eng (MKE) is a local stock-broking firm looking to adopt data science into their research process. As MKE's first data science intern, I am responsible for spearheading MKE's thrust towards data-driven investing.
- Developed a model that forecasts expected stock returns and select stocks using factors correlated to long-term returns. Features were calculated based on historical stock price patterns and financial data.
- Used robust regression methods to prevent overfitting and ensure reliability of expected return forecasts.
- Built a portfolio optimization tool that recommends portfolios based on a given risk/return profile.
- Backtested returns outperformed the index by 1/5 on a risk adjusted basis.


Order a Pizza
Your Information:
First name
Last name
Customize your pizza:
Size
Small
Medium
Large
Extra Large
Sauce
Classic Marinara
Garlic Parmesan
BBQ
Buffalo
Topping 1
Pepperoni
Italian Sausage
Salami
Meatball
Bacon
Smoked Ham
Chicken
Mushrooms
Red Onions
Black Olives
Bell Peppers
Banana Peppers
Pineapple
Jalapeno Peppers
Diced Tomatoes
Topping 2
Pepperoni
Italian Sausage
Salami
Meatball
Bacon
Smoked Ham
Chicken
Mushrooms
Red Onions
Black Olives
Bell Peppers
Banana Peppers
Pineapple
Jalapeno Peppers
Diced Tomatoes
Topping 3
Pepperoni
Italian Sausage
Salami
Meatball
Bacon
Smoked Ham
Chicken
Mushrooms
Red Onions
Black Olives
Bell Peppers
Banana Peppers
Pineapple
Jalapeno Peppers
Diced Tomatoes
Another pizza
Place Order!
Your Order:
First name:
Last name:
Order(s):


---
layout: post
title: "My Week in Review"
date: 2015-11-22 10:59:00 +0000
categories:
tags:
image: https://s3.amazonaws.com/audreywatters/2015-11-22-austin.jpg
imagecredits: https://www.flickr.com/photos/dawilson/6028948450
---
Travel
- Austin, TX and Hermosa Beach, CA
- Upcoming week: No travel (and I'm hoping no more travel for the year)
Hack Education
Essays Elsewhere
Speaking
- I was on a panel on diversity at API Strategy and Practice
Known Notes and Fragments
Other Projects
- I’m still working on a lengthy story on coding bootcamps as the new for-profit higher ed
- I’ve finalized the list of the Top 10 Ed-Tech Trends of 2015, and I’ll start working on these stories this week


Subclass of Handler which allows for the combination of SimpleHandlers.
An intuitive way to think about globbed patterns is as sets - for example, the
pattern "admin/*" is the set of all paths that are in the admin/ directory,
and the pattern "*.txt" is the set of all paths to text files. An
OverlappedHandler is designed to describe the intersection of the sets
of paths - ie the set of paths that is matched by EVERY one its
handler patterns.
In the Xml files, paths are specified in different places - in servlet
patterns, in static files includes, in security constraint specifications,
etc. There is often some overlap between the paths that are specified by
these patterns. Since App.Yaml does not have separate places to specify how
different paths are handled, but rather just lists paths along with a bunch
of ways that the paths is handled, we need to make sure that these properties
for various paths are being combined at some point in the translation process.
Thus an OverlappedHandler holds a list of "matchers" - ie. handlers with more
general patterns, to choose properties from. OverlappedHandlers do not
explicitly specify properties but rather choose the value from the most
specific "matcher" with the value of that property specified. The matchers
are SimpleHandlers.
Attributes:
pattern: inherited from Handler.
matchers: A list of SimpleHandlers. Matchers are handlers which happen to
match OverlappedHandler's pattern and whose properties are thus necessary
to track in order to make sure that OverlappedHandler's pattern is handled
correctly.


Menu
Home
Entity Type Scores
Contact
Polymer Explorer
Home
This is an experimental version of wpcat explorer.
Rob
Contact
This is the contact section