Importance of Information
Invisible Hand
By pursing his own interest, he frequently promotes that of the society more effectively than when he really intends to promote it... led by an invisible hand to promote an end which was no part of his intention
Adam Smith
conditions for perfectly competitive markets
- many buyers and sellers who are price takers
- products are homogeneous
- there are no barriers to entry or exit
- perfect information about actions is available (not just complete information abut payoff and preference)
perfectly competitive markets are only theoretically possible
Effects of Imperfect Information
- game theory
- prisoner's dilemma
- choices
- testify against the other
- keep quiet
- neither knows what the other chooses
- low prison time if neither confess
- no prison time if you're the one to confess and the other does not
- medium prison time if you both confess
- Nash equilibrium where each person confesses is the worst situation
- Pareto optimal where neither confesses is the best situation
- John Nash won a Nobel prize in 1994
- proved the existence of a t least one equilibrium point for any non-cooperative non zero-sum game with any numbers of players
- market and invisible hand fails because only imperfect information and not complete information is available when players are choosing an action
- information technology is especially useful in addressing this problem
- information technology makes it easier to share information about actions among agents


What's on Rails 4.2?
Nov 10, 2015
I've develped a couple of rails app recently and learned some neat tricks and tips I would like to share. Some of them are little pick from Rails 4.2 new release.
Rails 4.2 Adequate Record
Adequate Record is a set of performance improvements in Active Record that makes common find and find_by calls and some association queries up to 2x faster.
Rails 4.2 Web Console
New applications generated with Rails 4.2 now come with the Web Console gem by default. Web Console adds an interactive Ruby console on every error page and provides a console view and controller helpers.
Rails 4.2 Foreign Key Support
The migration DSL now supports adding and removing foreign keys. They are dumped to schema.rb as well. At this time, only the mysql, mysql2 and postgresql adapters support foreign keys.
Rails 4.2 Deprecations - Timestamp
Removed unused :timestamp type. Transparently alias it to :datetime in all cases. Fixes inconsistencies when column types are sent outside of Active Record, such as for XML serialization.


{% extends "layout.html" %} {% block page_title %} {{ proto.title + ' ' + proto.version }} - Accident details {% endblock %} {% block content %} When did the accident happen? If you are unsure of the exact date you can just enter the month and year When did the accident happen? For example, 31 3 1990 Day Month Year Form Navigation {% endblock %} {% block body_end %} {{ super() }} {% endblock %}
If you are unsure of the exact date you can just enter the month and year
For example, 31 3 1990


References
Citing RnBeads
Please cite RnBeads 2.0 as follows:
For citing the original version of RnBeads:
On the Shoulders of Giants
We would also like to emphasize that RnBeads makes extensive use of other R packages, and it may be appropriate to cite some of the underlying methods and contributing packages as well.
Infinium data processing
- Davis, S., Du, P., Bilke, S., Triche, T., Bootwalla, M. (2013) methylumi: Handle Illumina methylation data. R package version 2.6.1.
Filtering cross-reactive and SNP-overlapping probes
- Chen, Y., Lemire, M., Choufani, S., Butcher, D.T., Grafodatskaya, D., Zanke, B.W., Gallinger, S., Hudson, T.J., Weksberg, R. (2013) Discovery of cross-reactive probes and polymorphic CpGs in the Illumina Infinium HumanMethylation450 microarray. Epigenetics, 8(2), 203-209
- Nordlund, J., Bäcklin, C. L. et al. (2013) Genome-wide signatures of differential DNA methylation in pediatric acute lymphoblastic leukemia. Genome Biology, 14:r105
- Pidsley, R., Zotenko, E., Peters, T.J., Lawrence, M.G., Risbridger, G.P., Molloy, P., Djik, S.V., Muhlhausler, B., Strizaker, C., Clark, S.J. (2016) Critical evaluation of the Illumina MethylationEPIC BeadChip microarray for whole-genome DNA methylation profiling. Genome Biology, 17(1), 208
Background correction
- Triche, T.J., Jr., Weisenberger, D.J., Van Den Berg, D., Laird, P.W., Siegmund, K.D. (2013). Low-level processing of Illumina Infinium DNA Methylation BeadArrays. Nucleic Acids Res, 41(7), e90.
SWAN
- Maksimovic, J., Gordon, L., Oshlack, A. (2012). SWAN: Subset quantile Within-Array Normalization for Illumina Infinium Infinium 450k BeadChips. Genome Biology, 13(6), R44.
Functional normalization (minfi.funnorm)
- Fortin, J., Labbe, A., Lemire, M., Zanke, B.W., Hudson, T. J., Fertig, E.J., Greenwood, C.M.T., Hansen, K.D. (2014) Functional normalization of 450k methylation array data improves replication in large cancer studies. BioRxiv.
SWAN, functional normalization
- Aryee, M.J., Jaffe, A.E., Corrada-Bravo, H., Ladd-Acosta, C., Feinberg, A.P., Hansen, K.D., Irizarry, R.A. (2014) Minfi: a flexible and comprehensive Bioconductor package for the analysis of Infinium DNA methylation microarrays. Bioinformatics 30(10), 1363-1369
BMIQ
- Teschendorff, A.E., Marabita, F., Lechner, M., Bartlett, T., Tegner, J., Gomez-Cabrero, D., Beck, S. (2013) A beta-mixture quantile normalization method for correcting probe design bias in Illumina Infinium 450 k DNA methylation data. Bioinformatics 29(2), 189-196.
Data-driven normalization approaches
- Pidsley, R., Wong, C., Volta, M., Lunnon, K., Mill, J., Schalkwyk, L. (2013) A data-driven approach to preprocessing Illumina 450K methylation array data. BMC Genomics, 14(1), 293.
- Schalkwyk, L.C., Pidsley R., Wong C.C., Touleimat, W.C.F.N., Defrance M., Teschendorff A., Maksimovic J. (2013). wateRmelon: Illumina 450 methylation array normalization and metrics. R package version 1.4.0.
Genome-wide coverage plots in quality control for bisulfite sequencing data
- Yin, T., Cook, D., Lawrence, M. (2012). ggbio: an R package for extending the grammar of graphics for genomic data. Genome Biology, 13(8), pp. R77.
Differential methylation using the "limma" method
- Smyth, G.K. (2005). Limma: linear models for microarray data. In Gentleman R, Carey, V., Dudoit., S., Irizarry R., Huber W. (eds.), Bioinformatics and Computational Biology Solutions Using R and Bioconductor, pp. 397-420. Springer, New York.
Reference-based cell type heterogeneity estimation
- Houseman, E.A., Accomando, W.P., Koestler, D.C., Christensen, B.C., Marsit, C.J., Nelson, H.H., Wiencke, J.K., Kelsey, K.T. (2012). DNA methylation arrays as surrogate measures of cell mixture distribution. BMC Bioinformatics 13:86.
Reference-free correction for cell type heterogeneity
- Houseman, E.A., Molitor, J., Marsit, C.J. (2014). Reference-Free Cell Mixture Adjustments in Analysis of DNA Methylation Data. Bioinformatics, btu029.


| Module | ActiveScaffold::Actions::Core |
| In: |
vendor/plugins/active_scaffold/lib/actions/core.rb
|
Returns true if the client accepts one of the MIME types passed to it ex: accepts? :html, :xml
Override this method on your controller to define conditions to be used when querying a recordset (e.g. for List). The return of this method should be any format compatible with the :conditions clause of ActiveRecord::Base‘s find.
Builds search conditions by search params for column names. This allows urls like "contacts/list?company_id=5".
Redirect to the main page (override if the ActiveScaffold is used as a component on another controllers page) for Javascript degradation


| Total net profit | 0.69 | Gross profit | 20.7 | Gross loss | -20.01 |
| Profit factor | 1.03 | Expected payoff | 0.08 | ||
| Absolute drawdown | -11.78 | Maximal drawdown (%) | 7.82 (-197.47%) | ||
| Total trades | 9 | Profit trades (% of total) | 4 (44.44%) | Loss trades (% of total) | 5 (55.56%) |
| Long positions (won %) | 1 (100.0%) | Short positions (won %) | 8 (37.5%) | ||
| Largest | profit trade | 9.98 | loss trade | -4.15 | |
| Average | profit trade | 5.17 | loss trade | -4.0 | |
| Minimum | profit trade | 1.92 | loss trade | -3.9 | |
| Maximum | take profit in pips | 75.5 | stop loss in pips | -31.2 | |
| Average | take profit in pips | 42.3 | stop loss in pips | -30.0 | |
| Minimum | take profit in pips | 4.8 | stop loss in pips | -27.3 | |
| Maximum | Reward-Risk | 2.5 | Duration in minutes | 3921 | |
| Average | Reward-Risk | 1.4 | Duration in minutes | 1478.1 | |
| Minimum | Reward-Risk | 0.1 | Duration in minutes | 52 | |
| Maximum | consecutive wins (profit in money) | 3.0 (14.28) | consecutive losses (loss in money) | 3.0 (-11.78) | |
| Average | consecutive wins | 2.0 | consecutive losses | 2.0 |
| Total net profit | 2.38 | Gross profit | 2.38 | Gross loss | 0.0 |
| Profit factor | 0.0 | Expected payoff | 2.38 | ||
| Absolute drawdown | 0.0 | Maximal drawdown (%) | 0.0 (0.0%) | ||
| Total trades | 1 | Profit trades (% of total) | 1 (100.0%) | Loss trades (% of total) | 0 (0.0%) |
| Largest | profit trade | 2.38 | loss trade | 0.0 | |
| Average | profit trade | 2.38 | loss trade | 0.0 | |
| Minimum | profit trade | 2.38 | loss trade | 0.0 | |
| Maximum | take profit in pips | 17.8 | stop loss in pips | -30.9 | |
| Average | take profit in pips | 17.8 | stop loss in pips | -30.9 | |
| Minimum | take profit in pips | 17.8 | stop loss in pips | -30.9 | |
| Maximum | Reward-Risk | 0.6 | Duration in minutes | 52.0 | |
| Average | Reward-Risk | 0.6 | Duration in minutes | 52.0 | |
| Minimum | Reward-Risk | 0.6 | Duration in minutes | 52.0 | |
| Maximum | consecutive wins (profit in money) | 1.0 (2.38) | consecutive losses (loss in money) | 0.0 (0.0) | |
| Average | consecutive wins | 1.0 | consecutive losses | 0.0 |
| Total net profit | -1.69 | Gross profit | 18.32 | Gross loss | -20.01 |
| Profit factor | 0.92 | Expected payoff | -0.21 | ||
| Absolute drawdown | -11.78 | Maximal drawdown (%) | 7.82 (-197.47%) | ||
| Total trades | 8 | Profit trades (% of total) | 3 (37.5%) | Loss trades (% of total) | 5 (62.5%) |
| Largest | profit trade | 9.98 | loss trade | -4.15 | |
| Average | profit trade | 6.11 | loss trade | -4.0 | |
| Minimum | profit trade | 1.92 | loss trade | -3.9 | |
| Maximum | take profit in pips | 75.5 | stop loss in pips | -31.2 | |
| Average | take profit in pips | 45.3 | stop loss in pips | -29.9 | |
| Minimum | take profit in pips | 4.8 | stop loss in pips | -27.3 | |
| Maximum | Reward-Risk | 2.5 | Duration in minutes | 3921.0 | |
| Average | Reward-Risk | 1.5 | Duration in minutes | 1656.4 | |
| Minimum | Reward-Risk | Duration in minutes | 103.0 | ||
| Maximum | consecutive wins (profit in money) | 2.0 (11.9) | consecutive losses (loss in money) | 3.0 (-11.78) | |
| Average | consecutive wins | 1.0 | consecutive losses | 2.0 |


Getting Started
Thanks For Purchasing
Base Admin 2.0 is a full featured admin template based on Twitter Bootstrap Framework.
Get Support
Our general support hours are Monday to Friday, 10am to 2pm Pacific Standard Time. We generally provide feedback on any support requests within 12 – 24 hours.
Featured Showcase
Thanks for downloading Base Admin 2.0. If you happen to do something interesting with it, just drop me a line and I’ll feature your work in a showcase post on the JumpstartUI blog.
Upgrading to 2.0
What's New?
Base Admin 2.0 comes with a bunch of new features many of which are listed to the right.
Upgraded To: UPDATED
- Bootstrap 2.3.1
- jQuery 1.8.3
- jQuery UI 1.10.0
- Font Awesome 3.0.2
- Responsive Layout
Styled Elements: ALL NEW
- Bootstrap Buttons
- Bootstrap Accordion
- Bootstrap Progress Bars
- Bootstrap Modal
- Bootstrap Pagination
- Bootstrap Dropdowns
- Bootstrap Tables
Added Features: ALL NEW
- Form Validation
- Lightbox Evolution
- Cirque Plugin
- Msg Growl
- Alert Boxes
- jQuery UI Sliders
- Image Gallery
- Scroll to Top
File Upgrades
File changes needed to get your project from Base Admin v1.0 to v2.0
File Updates
Copy the following directories to your project and overrite any necessary files.
/css/ /js/ /img/ /font/
Twitter Bootstrap
Insert the following css Bootstrap files to your css directory.
/css/bootstrap.min.css /css/bootstrap-responsive.min.css
Insert the following javascript Bootstrap file to your js directory.
/js/libs/bootstrap.min.js
Base Admin 2.0 Styles
Remove the old style sheets from your document.
<link href="./css/base-admin.css" rel="stylesheet"> <link href="./css/base-admin-responsive.css" rel="stylesheet">
Insert the following two stylesheets to the head of your document after the Twitter Bootstrap includes:
<link href="./css/base-admin-2.css" rel="stylesheet"> <link href="./css/base-admin-2-responsive.css" rel="stylesheet">
jQuery
Remove the old jQuery include from your document.

Insert the following jQuery include with the following in your document above the closing
tag:

jQuery UI
Insert the following to the
of your document:
<link href="./css/ui-lightness/jquery-ui-1.10.0.custom.min.css" rel="stylesheet">
Insert the following to the end of your document above the closing
tag:

Font Awesome
Insert the following Font Awesome css files to your css directory overwriting the old file.
/css/font-awesome.min.css
Copy all the files from the /font
directory included in this theme to your project.
/font/FontAwesome.otf /font/fontawesome-webfont.eot /font/fontawesome-webfont.svg /font/fontawesome-webfont.ttf /font/fontawesome-webfont.woff
Html Updates
HTML changes needed to get your project from Base Admin v1.0 to v2.0
Navbar Container
Add the class .navbar-inverse
to your .navbar
container

Navbar Button
Remove the following element from your .navbar
container.

Insert the following element in your .navbar
container directly above the .brand
element.

Sub Navbar
Insert the a.btn-suvnavbar
element right above the ul.subnav-collapse
element.

Components
Widgets
You can use widget containers within the Bootstrap grid to better organize and separate your content.
Example Widget
Example of a basic widget with header and content sections.

Widget Title

 -- All content goes here --

Widget w/ No Header
Example widget with no header section.

 -- All content goes here --

Widget Table
Example widget for a table width no content padding.

 -- TABLE CODE GOES HERE --

Stacked
Example of a basic widget with header and content sections.

 -- CONTENT GOES HERE --

Validation
For complete information about this plugin and how to get started view:
jQuery Validation DocumentationIncludes
Insert the following javascript file into your document.

Validation Example
In order to use the validation styles provided with this theme you need combine your written validation rules with the custom rules provided by this theme. An example is below:
var rules = { rules: { name: { minlength: 2, required: true }, email: { required: true, email: true }, validateCheckbox: { required: true, minlength: 2 } } }; var validateObj = $.extend (rules, Theme.validationRules); $('#myForm').validate(validateObj);
Plans Wrapper
All pricing plans need to be placed within this container.

 --- Plans go here ---

You can add or remove the number of pricing tables in a row using the following classes:
- plans-1
- plans-2
- plans-3
- plans-4
Plan Html

 Micro

 $ 15 Per Month

Free setup

1 Website

2 Projects

1GB Storage

$0 Google Adwords Credit

 Purchase Now

Gallery
An easy way to display images and videos to your users use a flexible and responsive lightbox.
Includes
Insert the following javascript in your document when you use charts.
/js/demos/demo.gallery.js
Gallery Container
All gallery items will go within the ul
tag. An example of the gallery item is in the next section.

 --- GALLERY ITEMS GO HERE ---

Gallery Items
An example gallery item for you to use:

FAQ Plugin
Easy to use faq plugin with automatic table of contents and in-page search functionality.
Includes
Insert the following includes into your document.
<link href="./js/plugins/faq/faq.css" rel="stylesheet" />
FAQ Html
The html for the faq plugin is very basic. Styling and layout will be added when the plugin is called.
NOTE: Be sure the set your faq title as an h4 tag as that is what the table of contents is generated from.

FAQ Title

FAQ Text

Faq Javascript
Below is the javascript to initialize the faq plugin and the available configuration options
$('.faq-list').goFaq ({ enableSearch: true, enableToc: true, enableStyling: true });
Cirque Plugin
Setup
Insert the following includes into your document:
<link rel="stylesheet" href="./js/plugins/cirque/cirque.css">
Create an empty div element to hold your stat:

Attach the Cirque stat widget to your html element:
$('.my-stat').cirque ({ value: 234, total: 765, arcColor: '#FF9900' });
Helper
To create a Cirque stat without using writing javascript add the following class to your container: ui-cirque

This will initialize your cirque stat widget with default parameters defined in Theme.js
HTML5 Data Attributes
By setting HTML5 data attributes on a Cirque container you will override any default values previouly set. ALL values of a Cirque widget can be set via data attributes.

Options
| Class | Default | Description |
|---|---|---|
| value | 0 | Used to calculate the percentage to fill. The 'value' will be divided by the 'total' to derive the percentage. |
| total | 100 | Set the total value that will be used in the calculation to derive the percentage. |
| radius | 60 | Sets the radius of the circular stat. To get the total width of the canvas multiply the radius by 2. |
| label | percent | Set to percent to display the percentage in the stat. Set to ratio to display the actual ratio used to calculate the stat.
|
| lineWidth | 10 | Defines the thickness of the circle. |
| arcColor | #0066CC | Defines the fill color of the arc. |
| trackColor | #EEEEEE | Defines the color of the track. |
| trackFill | transparent | Defines the fill color of the track. |
| animate | true | Set to true/false depending on animation preference. |
| speed | 20 | Set the speed of the animation in milliseconds. |
Charts
Charting is provided by the awesome jQuery Flot plugin. It's easy to use and pretty flexible.
Documentation
Helper
Add the class .chart-holder
to your div that is going to contain the chart. This helper class give the chart container a default height which it needs to display properly.

Examples
You can find chart examples for line, pie, donut, vertical bar and horizontal bar charts in the /js/demos/charts/
folder. The code is clean and organized and should be a great start in creating your own charts.
Shortcuts
Easy to use shortcuts to provide your users easy access to any section of your app.
Shortcuts Container

 --- SHORTCUTS GO HERE ---

Shortcut Item
  Apps
External Docs
Bootstrap Docs
Bootstrap was made to not only look and behave great in the latest desktop browsers, but in tablet and smartphone browsers via responsive CSS as well.
Documentation
Twitter Bootstrap DocumentationFont Awesome
The iconic font designed for use with Twitter Bootstrap
Documentation
Font Awesome DocumentationMsg Box
jQuery MsgBox is a jQuery plugin highly configurable to replace the basic functionality provided by the standard javascript alert(), confirm(), and prompt() functions.
Documentation
MsgBox DocumentationjQuery Validation
This jQuery plugin makes simple clientside form validation trivial, while offering lots of option for customization.
Documentation
Validation DocumentationjQuery Flot
Flot is a pure JavaScript plotting library for jQuery, with a focus on simple usage, attractive looks and interactive features.
Documentation
Flot DocumentationLightbox Evolution
Lightbox Evolution is a tool for displaying images, html content, maps, and videos in a “lightbox” style that floats overtop of web page.
Documentation
Lightbox Evolution DocumentationMsg Growl
MsgGrowl is a clean CSS3 notification system for alerting users to site information, errors, warnings, and successes.
Documentation
jQuery Sliders
The jQuery UI Slider plugin makes selected elements into sliders. There are various options such as multiple handles and ranges.
Documentation
jQuery Datepicker
The jQuery UI Datepicker is a highly configurable plugin that adds datepicker functionality to your pages.


First, the person's name and photograph are populated from the M3C People Portal.
Then, their email address is used to find the corresponding profile on OpenVIVO to populate the ORCID ID and links.
All sans-serif, orange text is fetched from M3C.
All serif, green text is fetched from OpenVIVO.


|
jade-engine
0.0
|
#include <Sprite.h>
Public Member Functions | |
| Sprite (const SpriteParams ¶ms) | |
| Sprite (const ObjectLayer layer, std::shared_ptr< Texture > texture, const int32_t z) | |
| void | Render (SDL_Renderer *renderer) override |
| void | Clean () override |
| void | Tint (const SDL_Color &tintColor) |
| void | SetAlpha (const float alpha) |
| void | MakeTextureUnique () |
| virtual float | GetAlpha () const |
| void | SetRotation (const double angle) |
| virtual bool | HitTest (const int32_t x, const int32_t y) const |
| virtual bool | HasHitTest () const |
| void | SetSampling (const TextureSampling sampling) |
| void | SetSpriteSheetSprite (const std::string &sprite) |
| void | SetSpriteSheetMask (const Rectangle &mask) |
| const std::string & | GetTextureName () const |
| Public Member Functions inherited from JadeEngine::IGameObject | |
| IGameObject () | |
| virtual void | Update () |
| virtual LoadState | Load (SDL_Renderer *renderer) |
| LoadState | GetLoadState () const |
| void | SetLoadState (const LoadState newState) |
| bool | IsShown () const |
| virtual void | Show (const bool show) |
| int32_t | GetZ () const |
| void | Destroy () |
| bool | DestructionWanted () const |
Protected Attributes | |
| std::shared_ptr< Texture > | _textureDescription |
| const detail::SpriteSheetDescription * | _spriteSheetDescription |
| SDL_Texture * | _texture |
| bool | _spriteSheetMasked |
| Rectangle | _spriteSheetMask |
| std::string | _textureName |
| bool | _rotated |
| float | _alpha |
| double | _rotationAngle |
| ObjectLayer | _layer |
| Protected Attributes inherited from JadeEngine::IGameObject | |
| LoadState | _loadState |
| bool | _shown |
| int32_t | _z |
Additional Inherited Members | |
| Public Attributes inherited from JadeEngine::IGameObject | |
| const std::shared_ptr< Transform > | transform |
Game object that renders a texture on screen.
| JadeEngine::Sprite::Sprite | ( | const SpriteParams & | params | ) |
Constructor for Sprite that accepts SpriteParams.
Game::Create
function to create Sprites instead of constructing the object directly.| JadeEngine::Sprite::Sprite | ( | const ObjectLayer | layer, |
| std::shared_ptr< Texture > | texture, | ||
| const int32_t | z | ||
| ) |
Utility constructor for Sprites where their texture is already known and created elsewhere.
Game::Create
function to create Sprites instead of constructing the object directly.Used internally by the Jade Engine and most likely of limited use otherwise.
|
overridevirtual |
Triggered when the game object is about to be destroyed or reset.
All resources belonging solely to the game object, such as textures, should be released at this point. The game object instance itself may or may not be destroyed after this callback.
Reimplemented from JadeEngine::IGameObject.
|
virtual |
Return the current transparency alpha value.
| const std::string & JadeEngine::Sprite::GetTextureName | ( | ) | const |
Return the texture name that the sprite is rendering. In the case of sprite-sheet sprite it is the texture name of one of the packed textures.
|
virtual |
Return whether the sprite's texture was initialized with hit map.
Reimplemented in JadeEngine::BoxSprite.
|
virtual |
Perform a hit test, returning whether a pixel of the sprite is not empty (not completely transparent, alpha > 0).
| void JadeEngine::Sprite::MakeTextureUnique | ( | ) |
Create a deep-copy of the Sprite texture that is not shared with other Sprites using the same texture.
This operation is necessary for Sprite::Tint
and Sprite::SetAlpha
and will be called automatically on their first call unless already called by the user.
Game::CopyTexture
.
|
overridevirtual |
Triggered every frame while the scene that owns this game object is active, the game object was successfully loaded and the game object is shown.
The trigger order is the following: IScene::PreUpdate -> IGameObject::Load -> IGameObject::Update -> IScene::Update -> IGameObject::Load -> IGameObject::Render.
| renderer | The engine's SDL2 renderer that should be used to render the game object. |
Reimplemented from JadeEngine::IGameObject.
Reimplemented in JadeEngine::TextSprite.
| void JadeEngine::Sprite::SetAlpha | ( | const float | alpha | ) |
Changed the transparency of the sprite.
MakeTextureUnique
is called which is potentially expensive operation. Consider calling MakeTextureUnique
explicitly during initialization to avoid flickering. | alpha | Transparency alpha value to set. 0 will make the sprite completely invisible, 1 fully opaque. It will be clamped to [0.0f, 1.0f] range. |
| void JadeEngine::Sprite::SetRotation | ( | const double | angle | ) |
Set the rotation the sprite will rendered with.
The rotation center will be the center of the sprite, i.e. GetWidth() / 2 and GetHeight() / 2. This only affects the rendering of the sprite and not its transform.
| angle | Rotational angle in degrees in a clockwise direction. |
| void JadeEngine::Sprite::SetSampling | ( | const TextureSampling | sampling | ) |
Change the sampling of the texture.
| void JadeEngine::Sprite::SetSpriteSheetMask | ( | const Rectangle & | mask | ) |
Change the what rectangle of the sprite-sheet is used for rendering the sprite.
As sprite-sheets are collections of texture it is recommended to use Sprite::SetSpriteSheetSprite instead of directly specifying the rectangle.
| void JadeEngine::Sprite::SetSpriteSheetSprite | ( | const std::string & | sprite | ) |
Change the sprite's texture to a different texture that is part of the same sprite-sheet.
Useful for simple frame-based animations of sprites. Nothing happens if the new texture is not found.
| sprite | Name of the new texture as defined by the sprite-sheet. Usually original file name of the texture before packing into sprite-sheet. |
| void JadeEngine::Sprite::Tint | ( | const SDL_Color & | tintColor | ) |
Tint the sprite with a single color.
MakeTextureUnique
is called which is potentially expensive operation. Consider calling MakeTextureUnique
explicitly during initialization to avoid flickering. | tintColor | RGBA 0-255 color that will be used to multiply each pixel of the sprite. Alpha component is ignored. |


Occupied Crimea sees another environmental damage as lake near Sevastopol dries up (Photo)
Photos depicting the lake before and after were posted by a blogger.
Russia-occupied Crimea sees another environmental damage as a lake in the village of Kyzylove near the city of Sevastopol has dried up.
"A lake in Kyzylove is no more. Yet it was there before. And it wasn't a drought that purposefully destroyed the harbor," blogger RoksolanaToday&Crimea25% (@KrimRT) wrote on Twitter, posting respective photos.
As UNIAN reported earlier, Russia-occupied Crimea may face irreversible environmental damage over the lack of fresh water, since large rivers of the peninsula have dried up.


---
title: What Is an Expert?
excerpt: What does being an "expert" mean in complex knowledge work? Here are some reflections.
date: '2022-03-22 08:11:23 +0100'
categories:
- Agile
- Motivation
- General
- Teams
image:
path: /assets/images/social/being_an_expert.jpg
---
What does being an "expert" mean in complex knowledge work? That's one of the questions I've been pondering for a while. Last week we discussed it also with my wise colleagues at One Agency, so I thought I'd post some reflections here :)
Without dissing any experts out there, I've become slightly allergic to the word itself. Traditionally, an expert is a "person with a high level of knowledge or skill relating to a particular subject or activity" (Cambridge Dictionary).
I have high respect for these people. However, here are some implications of that definition that I can think of, especially in our complex VUCA world:
it focuses on a specialized person (internal focus) and not on a team (external/outcome focus)
it optimises for Resource Efficiency (single person) instead of Flow Efficiency (unit), possibly creating dependencies and bottlenecks in the process
it doesn't mention that expertise is time/situation-bound, with an ever-changing "best-before" date
it doesn't mention the context in which the expertise is applied (no one-size-fits-all)
it doesn't mention if this expertise exists in theory only, or also in practice. Being experienced can often mean admitting not knowing the answer - and finding out through experiments. Navigating in the mist is an important skill :)
Being an expert is then perhaps more of a mindset than a fixed trait. As such, it can't be evaluated by years of experience, but rather by focusing on the scientific method and a process that produces positive results. In other words, in my mind, a good expert has grit.
Some further thoughts on being an expert
An expert should be able to communicate and interact with non-experts. It's quite common to refrain from commenting if we feel we're not "experts" in the topic. A respectful dialogue between humans should always be possible, to increase understanding, regardless of experience level.
An expert shouldn't get irritated if his/her knowledge is challenged or criticised. An expert understands that it's not about his/her ego, but about advancing the knowledge to improve both the system and the outcome.
An expert should be able to rethink and relearn, adapt, be aware, and listen. Changing your mind based on critical thinking and new information is not weakness; it leads to wisdom. In fact, the person who can't change his or her mind is dangerous.
It's the others that see you as an expert and choose to trust you as such. It's not a self-proclaimed title. If you think that you, the "expert", are always right, you've already lost your expertise in the VUCA world, and damaged trust in your team.
Finally, it's the team that has the combined expertise to deliver an effective outcome. Everyone in the team has a piece of the truth.


Listening to Webhook
Subscription Id:
Perform the action you created a subscription for (eg, sending/receiving email, creating a message in Teams...), you'll see the notification appear below.


jqxBulletChart settings
Show labels
Near
Far
Both
Labels format:
Currency
Percent
None
Enable animation
Pointer value:
Pointer color:
Target color:
Disabled
Right-to-left


DONATE!¶
Work on this project is currently driven by my own interests, needs and spare time. If you appreciate this software or if you want to sponsor a currently not translated API feature, please consider donation to the project.
PyBSDDB/BSDDB3 needs your help.
You can donate using BitCoins. The destination address is 16avqyUK4vDqBdpUy365PPW44zNqVHLZSC.
Since donations thru BitCoin are not revocable, please be sure your are transfering to the right account (this document could have been modified for a third party). You can verify it in two diffent ways:
Reading this document in the project original website: https://www.jcea.es/programacion/pybsddb_doc/donate.html. Make sure you are seeing the right webpage.
Verifying the PGP digital signature of the following document:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The BitCoin address for donating to PyBSDDB/BSDDB3 project is "16avqyUK4vDqBdpUy365PPW44zNqVHLZSC". -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJT0AKrAAoJEGjgN61Khv5DK1kH/3JctpZUr+h8iFCfpRCaHsX8 +6dmncm3ebAWt9kCRqZZ74Eq8h9918C4UwxLLPrskAIqQw3g2IyTdaPOHomM23XH Ru1ok5fhCjNMCw4+dnnO/AXxEY6cIf2PjsQlkUznCe0zz1ndZQ33XbdI/1ItUEhy nZVWblnCCAQnO69Nhf6vPxfRDol1oDTh0bginhflmS01P2r8m9Mzx9h7Rrx7oKwG meNIVIzwdA+Tbex0GvQGorPSwEuid/mVYuDp9jSLp8XgeXBQfeqPWv+PO2tkijYE Zs1A1YuFA3S8uDnZhe9P7u4w7PGlCNIrDvTyippXiYB9fnSHu6mPmCw3wv+SWkM= =9xWm -----END PGP SIGNATURE-----
Doing something like gpg --verify and pasting this block, your should get something like:
gpg: Signature made Wed 23 Jul 2014 08:44:59 PM CEST using RSA key ID 4A86FE43 gpg: Good signature from "Jesús Cea Avión<EMAIL_ADDRESS>My PGP key ID is “4A86FE43”. My key fingerprint is:
pub 4096R/1567BC0F 2014-01-13 Key fingerprint = 8627 62C4 6EC3 567C B58C 7FB1 A510 404E 1567 BC0F uid Jesús Cea Avión<EMAIL_ADDRESS>sub 2048R/4A86FE43 2014-01-13 sub 2048R/05488493 2014-01-13


TermCalculator widget allows you to use extended capabilities of a calculator in 'console' version.
Avaible operations:
- trig identities,
- factorials up to 10^4, (more on faster machines),
- modulus,
- any other, (basic) operation


Fill in the fields below to create a new slideshow containing photos that meet any of the criteria you choose.
All fields except the name are optional. If you choose no filtering criteria then the default Past 7 Days will be implemented.
This means that depending on the day you are viewing the slideshow, the images will be from the past 7 days of the current and previous years.
N.b. The more criteria you choose, the more specific your search for images becomes.


| RGB | R. Lum. | H | S | V | ||
|---|---|---|---|---|---|---|
| 0 | 79 | 176 | 66 | 213 | 100 | 69 |
| 0 | 79 | 176 | 66 | 213 | 100 | 69 |
| 0 | 79 | 176 | 66 | 213 | 100 | 69 |
| 0 | 79 | 176 | 66 | 213 | 100 | 69 |
| 0 | 79 | 176 | 66 | 213 | 100 | 69 |
| Colour | FG Base | FG One | FG Two | FG Three | FG Four | Black | White |
|---|---|---|---|---|---|---|---|
| BG Base | |||||||
| BG One | |||||||
| BG Two | |||||||
| BG Three | |||||||
| BG Four | |||||||
| Black | |||||||
| White |
In 2011, the UK's Department for Transport (DfT) started to issue datasets for public use under the Open Government License. The first of these was planned roadworks issued by the Highways Agency.
Presented here is the latest data on planned roadworks on the Highway Agency's roads, distilled from the data files on this page. You can find information by road number, or search by location. The roadworks that are shown have already started or will start within the next week. Roadworks which should have been complete at least a week ago are filtered out (hopeful, I know).
These are the outstanding planned roadworks from the 29 Jun 2015 data file on the site, covering planned roadworks up to the end of 2017. I will keep this page updated as new roadworks are posted on the DfT site, which is currently happening most weeks.


Company profile - Canadian Company Capabilities
Third-Party Information Liability Disclaimer
Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.
Electric Edge Systems Group Inc.
Mailing Address:
3016 Orillia StVICTORIA, British Columbia
V9A 1Y8
Location Address:
3016 Orillia StVICTORIA, British Columbia
V9A 1Y8
Tel.:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
Logo
Company Profile
Electric Edge was founded in September, 2000 by three partners: Bryan Stevenson, Phil Bailey, and Greg Rusak (Greg was with Electric Edge until June, 2009). Each partner had many years of experience in different fields including website and web applications development, client/server software development, and database design. The partners had worked on projects of all sizes, including development of major systems for organizations such as TELUS, BC Ferry Services, Canfor, Worksafe BC, and many others.
Our company was formed when the three founders realized that by combining their diverse skills, they could provide the full spectrum of systems development services with unsurpassed quality.
In spite of forming the company in the darkest days of the dot-com collapse of 2000, our company has been profitable and has grown steadily every year. Today, the partners and staff of Electric Edge Systems Group produce top-quality websites, web applications, and software for numerous clients of all sizes.
We are often contacted by organizations with websites and applications that were produced by individuals or companies that were unable to complete the projects, or that produced poor quality results. A considerable portion of our work involves redevelopment of web, software, and database projects in order to raise them to the high standards that we are known for.
For the last several years, we have evolved into experts in fisheries management systems through our extensive work for Fisheries and Oceans Canada - Pacific Region. Major changes have taken place in fisheries management, not only in Canada, but around the world. We have been at the forefront of building systems to implement those changes for various Canadian fisheries. As a result, we are extending our reach as we promote our skills and experience to governments and fishery organizations around the world.
For more information, please contact us.
Full profile
Full profile
Contact information
Company description
Product / Service / Licensing
In fisheries that use dockside monitoring, fishing vessels are required to provide notification prior to the start of a fishing trip and again when fishing has concluded and the vessel is returning to port. These notifications are referred to as "hails". At a minimum, hails provide the time and place where the vessel will be offloading its catch.
In addition to providing data to regulatory and industry bodies, hails provide advance notice to dockside monitors so that they can meet the vessel upon its arrival in port and monitor the offloading of catch. The hail data can also help to ensure that vessels cannot go out fishing when certain regulatory requirements are not met.
Electric Edge Systems Group has developed a complete solution for electronic hails from vessels while they are at sea.
Please contacts us for full details
Web and Software Applications Development:
A basic website is like an online brochure - It will provide you customers with a predetermined set of information. If you require greater interactivity with your website visitors (e.g. searching through your products, registration, logon, online purchases, automatic generation of e-mails, etc.), then you need a web application.
Although many individuals and companies can produce basic websites, web and software applications development requires a far greater skill set. Our extensive experience is your assurance that your web and software applications will be done right the first time.
Our successes are largely based upon our disciplined approach to the development process. This means taking the time to understand your business needs, designing your database so that it will operate with maximum efficiency and scale to your future needs, and consulting with you and obtaining your "sign-off" on all major milestones along the way.
Database Design:
For your web or client/server based applications, nothing is more important than having databases that are set-up for maximum performance, flexibility, and growth potential. Our experience in database design, data modeling, and SQL can help make sure that your databases are set-up right from the start.
Analysis and Documentation:
For larger projects, we can analyze and document your business processes, existing systems, and development requirements. Our experience in a wide variety of sectors helps us to identify your needs and to ask you the right questions. We can also produce full technical designs, data models, web content, and end-user manuals.
Fisheries Management - Changing Times and Requirements
Around the world, we are witnessing a fundamental shift in fishery management. Declining stocks require increased enforcement through trip, catch, and offload monitoring. Environmental concerns require drastic reductions in discarded bycatch. This is being handled through individual vessel quota that allows for retention of bycatch species and the transfer of quota between vessels.
The quantity of data being tracked and the need to process and report on it quickly and effectively has never been greater. This requires new software applications, revamped databases, and new systems that are geared toward the requirements of today's fisheries.
What We have been Doing
For the last several years, Electric Edge Systems has worked closely with the Pacific region of Fisheries and Oceans Canada to maintain and add new functionality to existing systems and to create entirely new systems. During that time, Fisheries and Oceans Canada has implemented a wide variety of changes in various aspects of its business including trip/catch monitoring and integration of various fisheries via bycatch retention and individual transferable quota.
Electric Edge has been at the forefront of implementing the many changes to Fisheries and Oceans Canada's systems. We have created or performed major work on the following systems:
* Fishery Operations System
* Quota Management System
* Scientific Licensing System
* Plant Inspections System
* National Recreational Licensing System (publically accessible)
* Regional External Party Management System
Electric Edge Systems is a group of highly skilled, dedicated I.T. professionals with experience in all aspects of systems development including the following:
* Business Analysis
* Technical Design
* Data Modeling
* Database Development
* Programming of Web and Client/Server Systems
* Unit and Integrated Testing
* Documentation and User Training
* Ongoing Support and Systems Maintenance
What We are Doing Now
Going forward, Electric Edge Systems Group is expanding its operations. We will build upon our experience with Fisheries and Oceans Canada by providing our services and expertise to government departments and other fishery management organizations around the world. We will be seeking projects ranging from high-level consultative/advisory roles, to complete end-to-end systems planning, development, and ongoing support. We will be pleased to work independently or in partnership with organizations in the countries that they serve.
Electric Edge Systems will add value to fishery management organizations as they create, adapt and improve I.T. systems to cope with the demands of today's fisheries and legislation.
D307-Automated Information System Design and Integration Services
D308-Programming Services
D309-Information and Data Broadcasting or Data Distribution Services
D317-Automated News Services, Data Services, or Other Information Services. Buying data (the electronic equivalent of books, periodicals, newspapers, etc.
Technology profile
Web applications and PowerBuilder plus Oracle and other SQL
databases for client/server applications.
Market profile
Alliances:
- Sales/Marketing
- Technology
Industry sector market interests:
- Information Technology and Telecommunications
Geographic markets:
Export experience:
- United States
Actively pursuing:
- United Kingdom
Sector information
Key / Major clients:
BC Tel / Telus:
Designed and implemented a Corporate Intranet for
the Human Resource Department of Telus. The
project involved the use of several different
technologies including; Microsoft Access, dBase,
and Cold Fusion. This site provides corporate
information to over 3000 Telus managers
throughout BC and Alberta. The system was an
integral part of re-structuring the company
during the recent BC Tel / Telus merger.

BC Ferry Corporation (Traffic Management
System):

Lead developer of the Traffic Management System
(TMS). As ferry tickets for vehicles and foot
passengers are purchased through PC POS,
statistical information is fed into TMS. The data
is displayed in real time in the traffic
control tower. Tower operators use the data for
tracking all traffic in the compound and for
loading the traffic onto the appropriate vessels
in accordance with coast guard regulations. TMS
was developed in PowerBuilder 5.0 using the pfc
library.

BC Ferry Corporation (Point-of-Sale System):

Co-developed PC POS - The point of sale system
now in use at all BC Ferry Terminals that have
ticket booths. BC Ferries transports over 25
million passengers per year with annual revenues
of approximately $500 million. Over 80% of all
corporate revenues are processed through PC POS.

PC POS was built using PowerBuilder with the
Powersoft Foundation Class (pfc) library. PC POS
is architected for continuous service at
locations that may be subject to frequent network
outages. Each POS device is a Windows-based PC
with its own local Sybase SQL Anywhere
database. Attached peripherals include an
electronic cash drawer, customer display, barcode
scanner and ticket printer. Each POS database
communicates with an Oracle 7.3 database in the
ferry terminal. The Oracle databases connect to a
central Sybase System 11 database in Victoria.
All inter-database communication occurs as a
background process. In the event of a network
outage, the databases accumulate transactions
until the network is re-connected. Upon re-
connection, all data is streamed to the target
databases.
Testimonial:
Our clients say:
"Electric Edge was easy to work with and laid out
a clear plan of work that needed to be done and
the costs involved. They were quick to respond to
any concerns and corrections to be made as we
proceeded through the work...we greatly
appreciated their commitment"

- Robert Harris, Director, Dr. Vodder School-
North America
Third-Party Information Liability Disclaimer
Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.
Contacts
Contact information
Description
Company description
Products, services and licensing
Product / Service / Licensing
In fisheries that use dockside monitoring, fishing vessels are required to provide notification prior to the start of a fishing trip and again when fishing has concluded and the vessel is returning to port. These notifications are referred to as "hails". At a minimum, hails provide the time and place where the vessel will be offloading its catch.
In addition to providing data to regulatory and industry bodies, hails provide advance notice to dockside monitors so that they can meet the vessel upon its arrival in port and monitor the offloading of catch. The hail data can also help to ensure that vessels cannot go out fishing when certain regulatory requirements are not met.
Electric Edge Systems Group has developed a complete solution for electronic hails from vessels while they are at sea.
Please contacts us for full details
Web and Software Applications Development:
A basic website is like an online brochure - It will provide you customers with a predetermined set of information. If you require greater interactivity with your website visitors (e.g. searching through your products, registration, logon, online purchases, automatic generation of e-mails, etc.), then you need a web application.
Although many individuals and companies can produce basic websites, web and software applications development requires a far greater skill set. Our extensive experience is your assurance that your web and software applications will be done right the first time.
Our successes are largely based upon our disciplined approach to the development process. This means taking the time to understand your business needs, designing your database so that it will operate with maximum efficiency and scale to your future needs, and consulting with you and obtaining your "sign-off" on all major milestones along the way.
Database Design:
For your web or client/server based applications, nothing is more important than having databases that are set-up for maximum performance, flexibility, and growth potential. Our experience in database design, data modeling, and SQL can help make sure that your databases are set-up right from the start.
Analysis and Documentation:
For larger projects, we can analyze and document your business processes, existing systems, and development requirements. Our experience in a wide variety of sectors helps us to identify your needs and to ask you the right questions. We can also produce full technical designs, data models, web content, and end-user manuals.
Fisheries Management - Changing Times and Requirements
Around the world, we are witnessing a fundamental shift in fishery management. Declining stocks require increased enforcement through trip, catch, and offload monitoring. Environmental concerns require drastic reductions in discarded bycatch. This is being handled through individual vessel quota that allows for retention of bycatch species and the transfer of quota between vessels.
The quantity of data being tracked and the need to process and report on it quickly and effectively has never been greater. This requires new software applications, revamped databases, and new systems that are geared toward the requirements of today's fisheries.
What We have been Doing
For the last several years, Electric Edge Systems has worked closely with the Pacific region of Fisheries and Oceans Canada to maintain and add new functionality to existing systems and to create entirely new systems. During that time, Fisheries and Oceans Canada has implemented a wide variety of changes in various aspects of its business including trip/catch monitoring and integration of various fisheries via bycatch retention and individual transferable quota.
Electric Edge has been at the forefront of implementing the many changes to Fisheries and Oceans Canada's systems. We have created or performed major work on the following systems:
* Fishery Operations System
* Quota Management System
* Scientific Licensing System
* Plant Inspections System
* National Recreational Licensing System (publically accessible)
* Regional External Party Management System
Electric Edge Systems is a group of highly skilled, dedicated I.T. professionals with experience in all aspects of systems development including the following:
* Business Analysis
* Technical Design
* Data Modeling
* Database Development
* Programming of Web and Client/Server Systems
* Unit and Integrated Testing
* Documentation and User Training
* Ongoing Support and Systems Maintenance
What We are Doing Now
Going forward, Electric Edge Systems Group is expanding its operations. We will build upon our experience with Fisheries and Oceans Canada by providing our services and expertise to government departments and other fishery management organizations around the world. We will be seeking projects ranging from high-level consultative/advisory roles, to complete end-to-end systems planning, development, and ongoing support. We will be pleased to work independently or in partnership with organizations in the countries that they serve.
Electric Edge Systems will add value to fishery management organizations as they create, adapt and improve I.T. systems to cope with the demands of today's fisheries and legislation.
D307-Automated Information System Design and Integration Services
D308-Programming Services
D309-Information and Data Broadcasting or Data Distribution Services
D317-Automated News Services, Data Services, or Other Information Services. Buying data (the electronic equivalent of books, periodicals, newspapers, etc.
Technology
Technology profile
Web applications and PowerBuilder plus Oracle and other SQL
databases for client/server applications.
Market
Market profile
Alliances:
- Sales/Marketing
- Technology
Industry sector market interests:
- Information Technology and Telecommunications
Geographic markets:
Export experience:
- United States
Actively pursuing:
- United Kingdom
Sector
Sector information
Key / Major clients:
BC Tel / Telus:
Designed and implemented a Corporate Intranet for
the Human Resource Department of Telus. The
project involved the use of several different
technologies including; Microsoft Access, dBase,
and Cold Fusion. This site provides corporate
information to over 3000 Telus managers
throughout BC and Alberta. The system was an
integral part of re-structuring the company
during the recent BC Tel / Telus merger.

BC Ferry Corporation (Traffic Management
System):

Lead developer of the Traffic Management System
(TMS). As ferry tickets for vehicles and foot
passengers are purchased through PC POS,
statistical information is fed into TMS. The data
is displayed in real time in the traffic
control tower. Tower operators use the data for
tracking all traffic in the compound and for
loading the traffic onto the appropriate vessels
in accordance with coast guard regulations. TMS
was developed in PowerBuilder 5.0 using the pfc
library.

BC Ferry Corporation (Point-of-Sale System):

Co-developed PC POS - The point of sale system
now in use at all BC Ferry Terminals that have
ticket booths. BC Ferries transports over 25
million passengers per year with annual revenues
of approximately $500 million. Over 80% of all
corporate revenues are processed through PC POS.

PC POS was built using PowerBuilder with the
Powersoft Foundation Class (pfc) library. PC POS
is architected for continuous service at
locations that may be subject to frequent network
outages. Each POS device is a Windows-based PC
with its own local Sybase SQL Anywhere
database. Attached peripherals include an
electronic cash drawer, customer display, barcode
scanner and ticket printer. Each POS database
communicates with an Oracle 7.3 database in the
ferry terminal. The Oracle databases connect to a
central Sybase System 11 database in Victoria.
All inter-database communication occurs as a
background process. In the event of a network
outage, the databases accumulate transactions
until the network is re-connected. Upon re-
connection, all data is streamed to the target
databases.
Testimonial:
Our clients say:
"Electric Edge was easy to work with and laid out
a clear plan of work that needed to be done and
the costs involved. They were quick to respond to
any concerns and corrections to be made as we
proceeded through the work...we greatly
appreciated their commitment"

- Robert Harris, Director, Dr. Vodder School-
North America


Greenhouse Gas Reporting Program and the U.S. Inventory of Greenhouse Gas Emissions and Sinks
Many industries and activities, large and small, emit greenhouse gases in the United States. These sources are found across all segments of the U.S. economy. EPA is responsible for characterizing greenhouse gas emissions using two complementary programs designed to help the public and policymakers understand both the sources and magnitude of these emissions.
The Inventory of U.S. Greenhouse Gas Emissions and Sinks (Inventory) is a document prepared annually by EPA, for over 20 years, that estimates the total greenhouse gas emissions across all sectors of the economy using national-level data.
The Greenhouse Gas Reporting Program (GHGRP) collects detailed emissions data from the largest greenhouse gas emitting facilities in the U.S.
While the Inventory provides high level perspective needed to understand the United States’ total emissions or “carbon footprint,” the GHGRP provides the detailed information that helps us better understand the sources and types of greenhouse gas emissions at individual facilities. This information can help industry identify opportunities for reduction and help communities identify nearby sources of greenhouse gas emissions. These data can be used to compare facilities or industries, track emissions from one year to the next, inform policy at the state and local levels, and provide important information to the finance and investment communities.
You can use the data from these two programs to answer common questions about U.S. greenhouse gas emissions. For example, the Inventory could help you find the contribution of the transportation sector, or the power sector, to total U.S. greenhouse gas emissions. The Greenhouse Gas Reporting program could help you find the biggest stationary sources of greenhouse gas emissions in your region.
| Inventory of U.S. Greenhouse Gas Emissions and Sinks | Greenhouse Gas Reporting Program | |
|---|---|---|
| Find total U.S. emissions | ||
| Review trend data for the past 20 years |
||
| Browse a map to find largest emitters in your area | ||
| Compare facility emissions across an industrial sector |
||
| Find reported emissions by state |
Percent of U.S. Emissions Covered
The Inventory estimates the total greenhouse gas emissions across all sectors of the economy using national-level data such as fuel use. This includes estimates of greenhouse gas emissions from fossil fuel combustion, various industrial processes, and agricultural sources. The comprehensive greenhouse gas data presented in the Inventory comprise the official U.S. estimate of total national emissions that is submitted to the United Nations in accordance with the Framework Convention on Climate Change.
The GHGRP includes most, but not all, U.S. emissions. In general only large suppliers of greenhouse gas emitting products, or facilities that emit more than 25,000 metric tons of CO2 equivalent (CO2e) per year (roughly equivalent to the CO2 emitted from the burning of 131 rail cars of coal), are required to report their annual greenhouse gas emissions. Some entire sectors, such as the agricultural and land-use sectors, are not required to report. Over 8,000 facilities reported greenhouse gas data to EPA for 2014, covering approximately 85-90% of total U.S. greenhouse gas emissions.
Years of Data Available
The Inventory presents national greenhouse gas emissions estimates from 1990 and each subsequent year. Through the Inventory, EPA now has trend data for national greenhouse gas emissions for over 20 years.
The GHGRP is a more recent program, developed in response to Congressional mandate from 2008, so there are fewer years of data available. Annual GHG data for covered facilities in 29 industry types is available starting in 2010. Annual GHG data for covered facilities in an additional 12 industry types is available starting in 2011.
Geographic Information
Because the Inventory uses aggregate national data (such as fuel use) to estimate greenhouse gas emissions for most sources, it generally does not provide geographic information showing the location of the emissions.
In contrast, since the GHGRP data is collected from facilities, it is possible to map source location and aggregate reported emissions by county, state, or region, for industries who report direct emissions. The GHGRP’s online Facility Level Information on GreenHouse gases Tool (FLIGHT) allows users to locate large emitters in their communities or state, and to view emissions by industry type or greenhouse gas.
Facility Map
Industry-Specific Information
A large amount of greenhouse gas emissions in the industrial sector come from the burning of fossil fuels for energy. The Inventory has a comprehensive estimate of these emissions, but because it is based on aggregate national data for fuel use, the Inventory cannot show relative emissions from specific industries within the industrial sector. Likewise, the Inventory cannot show the largest emitting facilities within a specific industry.
The GHGRP data provides EPA with a new and invaluable opportunity to use facility-specific information to disaggregate the national estimate for emissions from fossil fuel combustion to specific industries such as refineries, metals production, and chemical manufacturing. In addition, it allows for comparison of emissions between facilities within the same industry. These data can be an important tool for businesses and other innovators to find cost- and fuel-saving efficiencies that reduce greenhouse gas emissions.
For a more detailed comparison of Inventory and GHGRP emissions data for the industrial sector, please see the fact sheet GHG Emissions by Industry – GHGRP vs. U.S. GHG Inventory (PDF) (3pp, 244K).


'Save the Tiger'
A retrospective movie review by Walter Frith
As a testament to questionable business ethics, 'Save the Tiger' works. As a testament to the most extreme of human conditions, 'Save the Tiger' works. As a testament to some of the finest screen acting ever, 'Save the Tiger' works magnificently. Don't mistake it as a preachy, self-indulgent guilt trip on the part of its main characters. What the film is really about is one man's longing for the past to a happier time in his life as he sees his marriage crumble, his business decline and his sanity tested.
Jack Lemmon who has been a shining example of screen acting in its purest form won a Best Actor Oscar for this film which has all the subtlety of a traffic jam and twice the ulcer inducing lifestyle of a common businessman. Lemmon stars as Harry Stoner, a clothing manufacturer facing bankruptcy, foreclosure and the most important moral decision of his life. He and his partner (Jack Gilford) have to decide whether or not to hire the services of a professional arsonist to set fire to their main building in order to collect badly needed money from an insurance settlement for a corporate diversion of funds.
Locked in a heated exchange of moral justification for their opposite positions, Lemmon and Gilford are a great pair of actors looking at times as if they are acting in a stage play and making the most of their roles. Lemmon is in favour of torching the building while Gilford is not. Lemmon's secret desire as we find out in the course of the film was to be a big league baseball player. As a veteran of war, there is one emotionally gut wrenching scene where Lemmon is delivering a speech before a large audience and in his mind sees the combat beaten bodies of soldiers in the crowd instead of the real people who are there.
'Save the Tiger' is a film that doesn't jump all over the place. It has focus and is set primarily over the course of two days in the life of a tormented individual who is very human, a little bit sad and even though he is going to commit a criminal act to save his business, a strange sense of sympathy is generated for his character. Written by Steve Shagan and directed by John G. Avildsen ('Rocky'), 'Save the Tiger' is a film that doesn't strain its convictions, it presents them honestly.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


A class that manages the state of transactions.
This includes creating consistent snap shots for transactions.
| def google.appengine.datastore.datastore_stub_util.BaseTransactionManager.BeginTransaction |
( |
|
self, |
|
|
|
app, |
|
|
|
allow_multiple_eg |
|
) |
| |
Start a transaction on the given app.
Args:
app: A string representing the app for which to start the transaction.
allow_multiple_eg: True if transactions can span multiple entity groups.
Returns:
A datastore_pb.Transaction for the created transaction
| def google.appengine.datastore.datastore_stub_util.BaseTransactionManager.Clear |
( |
|
self | ) |
|
Discards any pending transactions and resets the meta data.
| def google.appengine.datastore.datastore_stub_util.BaseTransactionManager.Flush |
( |
|
self | ) |
|
Applies all outstanding transactions.
| def google.appengine.datastore.datastore_stub_util.BaseTransactionManager.GetTxn |
( |
|
self, |
|
|
|
transaction, |
|
|
|
request_trusted, |
|
|
|
request_app |
|
) |
| |
Gets the LiveTxn object associated with the given transaction.
Args:
transaction: The datastore_pb.Transaction to look up.
request_trusted: A boolean indicating If the requesting app is trusted.
request_app: A string representing the app making the request.
Returns:
The associated LiveTxn object.
| def google.appengine.datastore.datastore_stub_util.BaseTransactionManager.Groom |
( |
|
self | ) |
|
Attempts to apply any outstanding transactions.
The consistency policy determins if a transaction should be applied.
| def google.appengine.datastore.datastore_stub_util.BaseTransactionManager.SetConsistencyPolicy |
( |
|
self, |
|
|
|
policy |
|
) |
| |
Set the consistency to use.
Causes all data to be flushed.
Args:
policy: A obj inheriting from BaseConsistencyPolicy.
The documentation for this class was generated from the following file:
- code/googleappengine-read-only/python/google/appengine/datastore/datastore_stub_util.py


Last presentation at work, Amber will be by shortly to pick me up, onward to Thailand!
11/18/2009, 2:16:41 PM
Favs: 0
Retweets: 0
link--- layout: tweet ---
Last presentation at work, Amber will be by shortly to pick me up, onward to Thailand!
11/18/2009, 2:16:41 PM
Favs: 0
Retweets: 0
link


Releases
Version downloads and complete release notes
Security Contact
The FreeRADIUS security contact is<EMAIL_ADDRESS>All security related information or notifications should be sent to that address. Security notifications may be signed with the pgp key<EMAIL_ADDRESS>Security announcements
2017.07.17Multiple issues found by Guido Vranken
We requested that Guido Vranken do fuzz testing against the server. He found issues in all versions of the server. These issues are documented on the fuzzer page.
2017.05.26Erroneous Session Resumption
We discovered that the server could be convinced to permit TLS session resumption before the authentication finished. A partial fix was put into 3.0.13. Pavel Kankovsky verified that the fix was insufficient, and provided a tool to test the issue. A better fix was put into the server, and was released in version 3.0.14.
The original EAP-TLS code would refuse to resume sessions unless there were policy attributes in the session cache. This check was put in place to work around this issue with the OpenSSL API. At some point, the code was changed to cache policy attributes by default, which opened up the vulnerability. Given the long history of the server, it is not clear when that change was made.
FIX: The short-term fix is to disable session resumption in the
cache
subsection of the eap
module.
We believe that this issue affects version 2.1.1 through 2.1.7 inclusive. Other versions seem to be unaffected. We remind users that versions 1.0.x, 1.1.x, 2.0.x, 2.1.x, and 2.2.x are old and unsupported. Patches for those versions will not be released, as the issue can be corrected with a minor configuration change. We also note that prior to version 3, the session cache was disabled by default, and required administrator intervention to enable it.
The v4.0.x branch is not vulnerable to this issue. The underlying code has been refactored to hide the TLS session data until the final EAP Success is sent, in the Access-Accept. This change means that the issue is impossible to reoccur in the future.
At this time, we have not had reports of the issue being exploited in the wild.
2017.05.16FreeRADIUS server scanned by PVS-Studio
The people at PVS-Studio were kind enough to give us a temporary license so that we could scan FreeRADIUS. We scanned the v3.0.x branch of the server, as of commit a7df94.
You can read our write-up here.
2015.09.16Tunnel-Password Vulnerabilities
Denis Andzakovic found issues with the decryption of very long Tunnel-Passwords. The decryption routines could walk off of the end of a buffer, and write to adjacent addresses. The data being written is not under control of an attacker. The end result is usually a crash of the server.
The initial report was for version 3.0. We determined that the v3.1.x branch in git is also vulnerable. Version 2 has similar code for Tunnel-Password, which we were not able to exploit. However, for safety, all currently supported versions of the server were fixed.
The packet decoder in FreeRADIUS ensures that the only time this issue is exploitable is when a proxy server receives a long Tunnel-Password attribute in the reply from a home server. The attack cannot be performed by a RADIUS client, or an end user. As such, the exploitability of the attack is limited to systems within the trusted RADIUS environment.
We are releasing version 2.2.9 and version 3.0.10 to correct the issue.
2015.06.22Revoked intermediate certificates are not properly validated
oCert-CVE 2015-4680
All versions which implement EAP-TLS, prior to 2.2.8 and 3.0.9 do not check intermediate CAs for revocation. We have put patches into the version 2 and version 3 branches to fix these issues.
We expect that this issue has minimal effect on the majority of RADIUS systems. If you are using a self-signed CA for 802.1X, this issue does not seriously affect you, as only you can issue intermediate certificates. If you are using certificates from a public CA, then your configuration already permits third parties to issue certificates which will be accepted by your RADIUS server.
i.e. The act of using a public CA cert in RADIUS can open your systems to security issues which are larger, and much worse than this one. The fix for this particular issue does not change the underlying security problem behind using a public CA.
Our analysis of the issue led us to disagree with the analysis done by oCert, and the (alleged) original vendor who made the report. We a requested a response to our analysis, and oCert refused. We requested that the public notice contain an accurate description of the issue and it’s impact. oCert again refused. After repeated messages, the response from Andrea Barisani of oCert was:
The reporter disagrees with your assessment yet cannot share details
about their setup, oCERT has no wishes to do technical support on
their setup as we just care about the reported bug.
Which is missing the point. We never asked to do “technical support on their setup”. We asked for an accurate description of the issue and it’s impact. oCert refused, whichs means that they do not, in fact, “care about the reported bug”.
We wanted to work together to come up with an accurate description of the issue, including it’s impact. It was clear that oCert was had no such goal. They saw their work as simply taking the original report, and forwarding it to a wider audience (including us).
We can only conclude that our analysis is correct, and that the original report, and the summary published by oCert is largely wrong. We can also recommend that people avoid oCert, as they are unwilling to work with authors to publish accurate reports.
2015.04.04EAP-PWD Vulnerabilities
The EAP-PWD module performed insufficient validation on packets received from an EAP peer. This module is not enabled in the default configuration. Administrators must manually enable it for their server to be vulnerable. Only versions 3.0 up to 3.0.8 are affected.
These issues were found by Jouni Malinen as part of investigating 2015-4 for HostAP.
- The EAP-PWD packet length is not checked before the first byte is dereferenced. A zero-length EAP-PWD packet will cause the module to dereference a NULL pointer, and will cause the server to crash.
- The commit message payload length is not validated before the packet is decoded. This can result in a read overflow in the server.
- The confirm message payload length is not validated before the packet is decoded. This can result in a read overflow in the server.
- A strcpy() was used to pack a C string into an EAP-PWD packet. This would result in an over-run of the destination buffer by one byte.
2014.09.24SSLv3 (POODLE)
POODLE attack.
FreeRADIUS is not vulnerable to this issue. All version to at least 1.0.0 (and possibly earlier) require TLSv1.
2014.09.24Bash (Shellshock)
Shellshock bug.
Systems running FreeRADIUS may be vulnerable to this bug. The
default configuration does not execute any external programs or
shell scripts. However, administrators who have configured the
server to execute shell scripts must upgrade their version of
bash
to a version which is not vulnerable.
2014.02.17Stack overflow in the PAP module
The CVE notification is CVE-2014-2015
The PAP module takes a “known good” password (e.g. Crypt-Password), and compares it to the password entered by the user (e.g. User-Password). In cases where the “known good” password was very long, insufficient input validation was performed. An administrator who controlled the password store could enter long passwords, and cause the server to crash.
2012.11.10Unix module allows expired passwords
The CVE notification is CVE-2011-4966.
It was found that the “unix” module ignored the password expiration setting in “/etc/shadow”. The default configuration does not use the “unix” module, so there is no issue for most deployments. However, if the server was configured to use this module for authentication, users with an expired password could successfully authenticate, even though their access should have been denied. We recommend managing users in a database, instead of leveraging /etc/passwd. The fact that a user has login access to a machine does not necessarily mean that they can use RADIUS for other kinds of network access.
2012.09.10Overflow in EAP-TLS
The CVE notification is CVE-2012-3547. The issue was found by Timo Warns, and communicated to<EMAIL_ADDRESS>A sample exploit for the issue was included in the notification.
We recommend all administrators using EAP and 2.1.10, 2.1.11, 2.1.12, or the git “master’ branch upgrade immediately.
The vulnerability was created in commit a368a6f4f4aaf on August 18, 2010. Vulnerable versions include 2.1.10, 2.1.11, and 2.1.12. Also anyone running the git “master” branch after August 18, 2010 is vulnerable.
All sites using TLS-based EAP methods and the above versions are vulnerable. The only configuration change which can avoid the issue is to disable EAP-TLS, EAP-TTLS, and PEAP.
An external attacker can use this vulnerability to over-write the stack frame of the RADIUS server, and cause it to crash. In addition, more sophisticated attacks may gain additional privileges on the system running the RADIUS server.
This attack does not require local network access to the RADIUS server. It can be done by an attacker through a WiFi Access Point, so long as the Access Point is configured to use 802.1X authentication with the RADIUS server.
We scanned the rlm_eap_tls.c file with the LLVM checker-267, taken from http://clang-analyzer.llvm.org/. It did not find this issue. However, a Coverity scan did discover it.
2011.09.22Manually enabling OCSP has no effect
This issue is applicable only to version 2.1.11.
The CVE notification is CVE-2011-2701. The discoverer notified us and sent a patch.
The OCSP functionality in 2.1.11 could be enabled manually, but it would never mark certificates as revoked. As such, it did not behave as expected.
Since this issue requires manually enabling OCSP, it’s severity is low. The recommended solution is to upgrade to version 2.1.12.
2010.10.08FreeRADIUS may crash if database goes down
If FreeRADIUS depends on a database, and the database goes down for extended periods, the server may crash. This issue applies to versions 2.0.0 through 2.1.9. This issue is not externally exploitable.
The CVE notification is CVE-2010-3697.
As with many such notifications, the issuer did not communicate with us before releasing the alleged vulnerability. We also disagree with their description of the problem.
The short description of this problem is that any administrator who can (a) take the database down, or (b) disrupt communication between FreeRADIUS and the database can prevent FreeRADIUS from operating correctly. This result should not be a surprise.
In normal operation, when the server stops responding to packets (i.e. because the database is down), the NAS will stop sending it packets, and will fail over to another server. In addition, our tests indicate that this issue occurs only when the database is down for extended periods of time, and the server receives many millions of packets during that time. i.e. the problem will not occur in most deployments.
There is no possibility for privilege escalation, or access to the system running FreeRADIUS. The issue is marked “network exploitable” in the CVE database because it requires the network to be down for the attack to work.
Our recommendation is to upgrade to the latest version of the server. We also recommend that mission-critical systems be monitored. If they go offline for extended periods, they should be restarted.
2010.10.08Code modifications to the server can cause it to crash
This issue is applicable only to version 2.1.9.
The CVE notification is CVE-2010-3696.
The issuer did not communicate with us before releasing the alleged vulnerability, and we disagree with their description of the problem.
The DHCP functionality in 2.1.9 is not enabled by default. Enabling it requires code modifications, a complete re-build and re-install of the server, and a manual enabling of DHCP in the configuration. Further, the DHCP functionality is marked “experimental” in this release. As such, it should be used only on trusted networks.
This issue is exploitable whenever FreeRADIUS has had DHCP functionality enabled, and where the administrator has manually configured the server to accept DHCP packets. Any DHCP packet with a “Relay Agent” sub-option can cause FreeRADIUS to enter an infinite loop.
Our recommendation is to run experimental features only in trusted networks.
2010.02.03Apple Mac OS X server misconfiguration
CVE-2010-0524 - This issue only affects Mac OS X Server systems.
Apple had apparently configured FreeRADIUS to accept all “well known” Certificate Authorities as valid for EAP-TLS. This configuration permitted almost anyone to create a client certificate for use with EAP-TLS, which would then be accepted by Mac OS X Server systems.
We recommend that the list of Certificate Authorities configured in FreeRADIUS be audited, and kept as small as possible.
2009.09.09Server crash with Tunnel-Password attribute
Anyone who can send packets to the server can crash it by sending a Tunnel-Password attribute in an Access-Request packet. This vulnerability is not otherwise exploitable. We have released 1.1.8 to correct this vulnerability.
This issue is similar to the previous Tunnel-Password issue noted below. The vulnerable versions are 1.1.3 through 1.1.7. Version 2.x is not affected.
2007.04.10Memory leak in EAP-TTLS can cause server crash
This issue affects version 1.1.5 and earlier.
A malicous 802.1x supplicant could send malformed Diameter format
attributes inside of an EAP-TTLS tunnel. The server would reject the
authentication request, but would leak one VALUE_PAIR
data
structure, of approximately 300 bytes. If an attacker performed the
attack many times (e.g. thousands or more over a period of minutes
to hours), the server could leak megabytes of memory, potentially
leading to an “out of memory” condition, and early process exit.
We recommend that administrators using EAP-TTLS upgrade immediately.
2007.01.02Stack overflow in rlm_smb means admins can write to server config
SMB_Handle_Type SMB_Connect_Server.
While the summary is superficially correct, and there is a stack overflow in rlm_smb, the issue is less problematic than it sounds.
CVE-2007-0080 has been updated with our statement.
SecurityTracker Alert ID: 1017463 has been updated with our statement.
freeradius-smbconnectserver-bo (31248) has been updated to no longer claim the issue is remotely exploitable. They do not, however, include our vendor statement, though they do reference it. They also list the issue as “High Risk”, and “Gain Privileges”, which is NOT TRUE, for the reasons outlined below.
In summary, the issue is not remotely exploitable. It is exploitable by local administrators who have write access to the server configuration files. If an attacker can write to the server configuration files, they can configure the server to run arbitrary programs. Exploiting the server via a stack overflow would be unnecessary.
The solution to this “vulnerability”, of course, is to ensure that only the correct people are given write access to the server configuration files.
2006.03.20Insufficient input validation in MS-CHAP
A validation issue exists with the EAP-MSCHAPv2 module in all versions from 1.0.0 (where the module first appeared) to 1.1.0. Insufficient input validation was being done in the EAP-MSCHAPv2 state machine. A malicious attacker could manipulate their EAP-MSCHAPv2 client state machine to potentially convince the server to bypass authentication checks. This bypassing could also result in the server crashing. We recommend that administrators upgrade immediately.
2005.09.09Multiple SQL vulnerabilities
Multiple issues exist with version 1.0.4, and all prior versions of
the server. Externally exploitable vulnerabilities exist only for
sites that use the rlm_sqlcounter
module. Those sites may be
vulnerable to SQL injection attacks, similar to the issues
noted below. All sites that have not deployed the rlm_sqlcounter
module are not vulnerable to external exploits. However, we still
recommend that all sites upgrade to version 1.0.5.
The issues are:
- SQL Injection attack in the
rlm_sqlcounter
module. - Buffer overflow in the
rlm_sqlcounter
module, that may cause a server crash. - Buffer overflow while expanding %t, that may cause a server crash.
These issues were found by Primoz Bratanic. As the rlm_sqlcounter
module is marked “experimental” in the server source, it is not
enabled or configured in most sites. As a result, we believe that
the number of vulnerable sites is low.
Additional issues, not externally exploitable, were found by Suse. A
full response to their report is available
here. A related post to
the vendor-sec
mailing list is found
here.
2005.05.01Two SQL vulnerabilities
Two vulnerabilities in the SQL module exist in all versions prior to 1.0.3. Sites not using the SQL module are not affected by this issue. However, we still recommend that all sites upgrade to version 1.0.3.
The issues are:
- Buffer overflow - A long string could overflow an internal buffer in the SQL module, and write two bytes of text [0-9a-f] past the end of the buffer. The server may exit when this happens, resulting in a DoS attack. Depending on the local configuration of the server, this may occur before a user is authenticated. This vulnerability is externally exploitable, but can not result in the execution of arbitrary code.
- SQL injection attacks - The SQL module suffers from SQL
injection attacks in the
group_membership_query
,simul_count_query
, andsimul_verify_query
configuration entries. The first query is exploitable if your site is configured to use theSQL-Group
attribute in any module in theauthorize
section ofradiusd.conf
. The last two queries are exploitable only if your site has user names that contain a single quote character ('
).
2004.09.14Multiple external DoS attacks
Multiple external DoS attacks exist in the server. These are related to the attacks below, in 0.9.2, but were not caught then. The vulnerabilities are fixed in 1.0.1, and in all later versions of the server. The vulnerabilities are not exploitable, but can be used to remotely crash the server.
2003.11.20Externally exploitable root compromise in rlm_smb
There is an externally exploitable root compromise in rlm_smb, through a stack overflow when a password greater than 128 bytes referenced by the module. The module is not built or installed by default, so we have not released a 0.9.4. This vulnerability is fixed in the CVS snapshots, and will be included in any later release of the server.
2003.10.15Crash upon receipt of Tunnel-Password attribute
Anyone who can send packets to the server can crash it by sending a Tunnel-Password attribute in an Access-Request packet. This vulnerability is not otherwise exploitable. We have released 0.9.3 to correct this vulnerability.
2002.07.26Kerberos module may grant incorrect access
The Kerberos module may grant access to a user whose Kerberos ticket cannot be verified against the server principal. We have released 0.7.1 to correct this vulnerability.
2001.12.17Multiple RADIUS vulnerabilities
CA-2002-06. Multiple vulnerabilities in multiple RADIUS implementations. We have released 0.4 to correct these vulnerabilities.
2014.04.08OpenSSL Heartbleed
Heartbleed bug.
OpenSSL has a major security issue, seen in to CVE-2014-0160. The issue mainly affects servers such as SMTPS or HTTPS, which allow random IP addresses to connect to them via TLS. Those sites must assume that all information available to the system using TLS has been compromised.
Based on further information from Jouni Malinen, it appears that both Version 2 and Version 3 of FreeRADIUS are vulnerable to the attack. It is likely that earlier versions of the server are vulnerable, too.
The problem appears to be that OpenSSL has already allowed invalid reads by the time that FreeRADIUS detects the invalid heartbeat, and closes the connection. The benefit of the way FreeRADIUS uses OpenSSL is that the attack appears to be limited to reading ~1K of data from the stack, when the server receives the malicious heartbeat. This limitation mitigates the attack, but does not remove the possibility of exposing private information.
We recommend that all administrators upgrade OpenSSL immediately.
Administrators can detect “heartbleed” attacks by looking in their
logs for a message containing the text Invalid ACK received: 24
.
If such a message is seen, it means that the attack has
been attempted. You should upgrade your version of
OpenSSL immediately.
We suggest that all administrators upgrade all of their systems to a version of OpenSSL which is not vulnerable to this attack. Sites which allow random IPs to connect to a TLS server (e.g. SMTPS or HTTPS) should assume that all information available to those servers has been stolen from those systems. This information includes user credentials, keys for private certificates, cookies sent over HTTPS, etc.
We have updated FreeRADIUS (all versions) so that it refuses to start when it detects the vulnerable versions of OpenSSL.
v3.0.x - Administrators can over-ride this check by setting
allow_vulnerable_openssl = CVE-2014-0160
in the security
subsection of radiusd.conf.
v2.2.x - Administrators can over-ride this check by setting
allow_vulnerable_openssl = yes
in the security
subsection
of radiusd.conf.
2012.04.19Versions of OpenSSL are vulnerable to malformed certificates
The CVE notification is CVE-2012-2110.
We recommend all administrators using certificates with FreeRADIUS upgrade their OpenSSL to a secure version. For details, see the OpenSSL notification
We emphasize that this is not a bug in FreeRADIUS. FreeRADIUS uses OpenSSL for many of it’s cryptographic operations, and as such, is at the mercy of any problems in OpenSSL.
2008.05.13SSL keys may be guessable
A bug added to OpenSSL on Debian and Ubuntu systems means that SSL keys on those systems may be guessable.
We recommend that administrators using OpenSSL on Debian or Ubuntu upgrade immediately. We also recommend re-generating any SSL certificates used in RADIUS systems, if those certificates were created on a Debian or Ubuntu system since 2006.
We emphasize that this is not a bug in FreeRADIUS. FreeRADIUS uses OpenSSL for many of it’s cryptographic operations, and as such, is at the mercy of any problems in OpenSSL.
FreeRADIUS Security
Defensive Programming
All input is sanity-checked before use.
Clean code
There are no C compiler warnings in the build. Builds performed by developers have -Werror set, so that new errors are not introduced.
Builds with multiple compilers
We use GCC and CLANG for all builds. Each compiler produces a slightly different set of warnings. As seen above, no warnings from any compiler are allowed in the build.
Builds on multiple operating systems
We always build on Mac OSX and Ubuntu. We are in the process of adding FreeBSD and CentOS.
Builds are done with every single module, and multiple feature permutations
There is no portion of the server which has "code rot" because it has not been built for years.
Continuous testing
The src/tests/ directory has a growing set of tests for server functionality. These tests help ensure that new commits do not accidentally break existing functionality
Continuous integration
Commits are built and tested via travis
Static analysis (3X!)
Builds are performed weekly with Coverity. Builds are performed daily with Clang static analyzer and cppcheck. The server must build with no errors before it can be released.
These practices are not perfect. The test suite is growing, but it does not cover all of the servers functionality. As a result, the latest releases may still have bugs. The version 2 "stable" release undergoes less code churn and is the "long term support" stable and bug-free release. The version 3 "feature" release has significantly more code churn, and therefore, may have more issues than version 2


Chrome DevTools device mode is needed in order to get this component working in web browser (touchstart)


Loading...
Backup Database
Direct PostgreSQL Connection
PG Connection:
*
[{{ pgc.server_name }}] {{pgc.db_user}}@{{pgc.host}}:{{pgc.port}}/{{pgc.db}}
Host:
*
Port:
*
DB:
*
User:
*
Password:
Target Backup Server
SSH Server:
*
{{ host.name }}
({{ host.host }}), {{host.hostInfo.os}}, {{host.hostInfo.mem}} GB, {{ host.hostInfo.cores }} Core(s)
Directory:
*
Filename:
*
Format:
*
c - custom (binary compressed)
d - directory (parallel capable)
p - plain text (.sql file)
t - tar (old school compressed)
Advanced Options:
Start Backup...
View Recent Jobs
{{$root.runningJobsCount}}
Restore Database
Source Backup Server
SSH Server:
*
{{ host.name }}
({{ host.host }}), {{host.hostInfo.os}}, {{host.hostInfo.mem}} GB, {{ host.hostInfo.cores }} Core(s)
Backup File:
*
Format:
*
c - custom (binary compressed)
d - directory (parallel capable)
p - plain text (.sql file)
t - tar (old school compressed)
Advanced Options:
Target PostgreSQL Connection
PG Connection:
*
[{{ pgc.server_name }}] {{pgc.db_user}}@{{pgc.host}}:{{pgc.port}}/{{pgc.db}}
Host:
*
Port:
*
DB:
*
User:
*
Password:
Start Restore...
View Recent Jobs
{{$root.runningJobsCount}}


It is possible to update your version of MNE between releases for bugfixes or new features.
Warning
In between releases, function and class APIs can change without warning.
You can use pip
for a one-time update:
$ pip install --upgrade --no-deps git+https://github.com/mne-tools/mne-python.git
Or, if you prefer to be set up for frequent updates, you can use git
directly:
$ git clone git://github.com/mne-tools/mne-python.git
$ cd mne-python
$ python setup.py develop
A feature of python setup.py develop
is that any changes made to
the files (e.g., by updating to latest master
) will be reflected in
mne
as soon as you restart your Python interpreter. So to update to
the latest version of the master
development branch, you can do:
$ git pull origin master
and MNE will be updated to have the latest changes.
If you plan to contribute to MNE, please continue reading how to How to contribute to MNE.
We have developed specialized routines to make use of NVIDIA CUDA GPU processing to speed up some operations (e.g. FIR filtering) by up to 10x. If you want to use NVIDIA CUDA, you should install:
For example, on Ubuntu 15.10, a combination of system packages and git
packages can be used to install the CUDA stack:
# install system packages for CUDA
$ sudo apt-get install nvidia-cuda-dev nvidia-modprobe
# install PyCUDA
$ git clone http://git.tiker.net/trees/pycuda.git
$ cd pycuda
$ ./configure.py --cuda-enable-gl
$ git submodule update --init
$ make -j 4
$ python setup.py install
# install skcuda
$ cd ..
$ git clone https://github.com/lebedov/scikit-cuda.git
$ cd scikit-cuda
$ python setup.py install
To initialize mne-python cuda support, after installing these dependencies and running their associated unit tests (to ensure your installation is correct) you can run:
$ MNE_USE_CUDA=true MNE_LOGGING_LEVEL=info python -c "import mne; mne.cuda.init_cuda()"
Enabling CUDA with 1.55 GB available memory
If you have everything installed correctly, you should see an INFO-level log message telling you your CUDA hardware’s available memory. To have CUDA initialized on startup, you can do:
>>> mne.utils.set_config('MNE_USE_CUDA', 'true')
You can test if MNE CUDA support is working by running the associated test:
$ pytest mne/tests/test_filter.py
If MNE_USE_CUDA=true
and all tests pass with none skipped, then
MNE-Python CUDA support works.
In Jupyter, we strongly recommend using the Qt matplotlib backend for fast and correct rendering:
$ ipython --matplotlib=qt
On Linux, for example, QT is the only matplotlib backend for which 3D rendering will work correctly. On Mac OS X for other backends certain matplotlib functions might not work as expected.
To take full advantage of MNE-Python’s visualization capacities in combination with IPython notebooks and inline displaying, please explicitly add the following magic method invocation to your notebook or configure your notebook runtime accordingly:
In [1]: %matplotlib inline
If you use another Python setup and you encounter some difficulties please report them on the MNE mailing list or on github to get assistance.
If you run into trouble when visualizing source estimates (or anything else
using mayavi), you can try setting the ETS_TOOLKIT
environment variable:
>>> import os
>>> os.environ['ETS_TOOLKIT'] = 'qt4'
>>> os.environ['QT_API'] = 'pyqt'
This will tell Traits that we will use Qt with PyQt bindings.
If you get an error saying:
ValueError: API 'QDate' has already been set to version 1
you have run into a conflict with Traits. You can work around this by telling the interpreter to use QtGui and QtCore from pyface:
>>> from pyface.qt import QtGui, QtCore
This line should be added before any imports from mne-python.
To avoid Qt conflicts, you can also try using the wx
backend via
conda install wxpython
and ETS_TOOLKIT=wx
.
For more information, see http://docs.enthought.com/mayavi/mayavi/building_applications.html.


Displays the dialog box described in a dialog box definition table.
Syntax
DIALOG.BOX(dialog_ref)
Dialog_ref is a reference to a dialog box definition table on sheet, or an array containing the definition table.
If an OK button in the dialog box is chosen, DIALOG.BOX enters values in fields as specified in the dialog_ref area and returns the position number of the button chosen. The position numbers start with 1 in the second row of the dialog box definition table.
If the Cancel button in the dialog box is chosen, DIALOG.BOX returns FALSE.
The dialog box definition table must be at least seven columns wide and two rows high. The definitions of each column in a dialog box definition table are listed in the following table.
| Column type | Column number |
| Item number | 1 |
| Horizontal position | 2 |
| Vertical position | 3 |
| Item width | 4 |
| Item height | 5 |
| Text | 6 |
| Initial value or result | 7 |
The first row of dialog_ref defines the position, size, and name of the dialog box. It can also specify the default selected item and the reference for the Help button. The position is specified in columns 2 and 3, the size in columns 4 and 5, and the name in column 6. To specify a default item, place the item's position number in column 7. You can place the reference for the Help button in row 1, column 1 of the table, but the preferred location is column 7 in the row where the Help button is defined. Row 1, column 1 is usually left blank.
The following table lists the numbers for the items you can display in a dialog box.
| Dialog-box item | Item number |
| Default OK button | 1 |
| Cancel button | 2 |
| OK button | 3 |
| Default Cancel button | 4 |
| Static text | 5 |
| Text edit box | 6 |
| Integer edit box | 7 |
| Number edit box | 8 |
| Formula edit box | 9 |
| Reference edit box | 10 |
| Option button group | 11 |
| Option button | 12 |
| Check box | 13 |
| Group box | 14 |
| List box | 15 |
| Linked list box | 16 |
| Icons | 17 |
| Linked file list box (Windows only) | 18 |
| Linked drive and directory box (Windows only) | 19 |
| Directory text box | 20 |
| Drop-down list box | 21 |
| Drop-down combination edit/list box | 22 |
| Picture button | 23 |
| Help button | 24 |
Remarks
Add 100 to an item number in the above table to define the item as a trigger. A trigger is a dialog box item that, when chosen, returns to your macro (as clicking OK would) but continues to display the dialog box, allowing your macro to change the dialog box definition or display an alert message or another dialog box. The Help button, edit boxes, group boxes, static text, and icons cannot be triggers.
Add 200 to an item number to define it as dimmed. A dimmed (gray) item cannot be chosen or selected. For example, 203 is a dimmed OK button. You can use item 223 to include a picture in your dialog box that does not behave like a button.
If a trigger has been chosen and you still want to clear a dynamic dialog box from the screen, use DIALOG.BOX(FALSE). This is useful if you want to confirm that the dialog box has been filled out correctly before dismissing it.
The dialog box definition table can be an array. If dialog_ref is an array instead of a reference, DIALOG.BOX returns a modified copy of that array, along with the results of the dialog box in the seventh column. (The first item in the seventh column is the position number of the chosen button or of a triggered item.) This is useful if you want to preserve the original dialog box definition table since DIALOG.BOX does not modify the original array argument. If you cancel the dialog box, or if a dialog box error occurs, DIALOG.BOX returns FALSE instead of an array.
Related Functions
ALERT Displays a dialog box and a message
INPUT Displays a dialog box for user input
Return to index


Text Processor
Enter a comma-separated list of words:
one, two, three
Choose some options:
Upper-case
Alphabetize