|
texture - texture
face - face of cube to select.
This command should only be used when you wish to draw directly to a cubemap texture in real-time. Otherwise, just loading a pre-rendered cubemap with a flag of 128 will suffice. To understand how this command works exactly it is important to recognise that Blitz treats cubemap textures slightly differently to how it treats other textures. Here's how it works... A cubemap texture in Blitz actually consists of six images, each of which must be square 'power' of two size - e.g. 32, 64, 128 etc. Each corresponds to a particular cube face. These images are stored internally by Blitz, and the texture handle that is returned by LoadTexture/CreateTexture when specifying the cubemap flag, only provides access to one of these six images at once (by default the first one, or '0' face). This is why, when loading a cubemap texture into Blitz using LoadTexture, all the six cubemap images must be laid out in a specific order (0-5, as described above), in a horizontal strip. Then Blitz takes this texture and internally converts it into six separate images. So seeing as the texture handle returned by CreateTexture / LoadTexture only provides access to one of these images at once (no. 1 by default), how do we get access to the other five images? This is where SetCubeFace comes in. It will tell Blitz that whenever you next draw to a cubemap texture, to draw to the particular image representing the face you have specified with the face parameter. Now you have the ability to draw to a cubemap in real-time. To give you some idea of how this works in code, here's a function that updates a cubemap in real-time. It works by rendering six different views and copying them to the cubemap texture buffer, using SetCubeFace to specify which particular cubemap image should be drawn to. ; Start of code Function UpdateCubeMap( tex,camera ) tex_sz=TextureWidth(tex) ; do left view SetCubeFace tex,0 RotateEntity camera,0,90,0 RenderWorld ; copy contents of backbuffer to cubemap CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do forward view SetCubeFace tex,1 RotateEntity camera,0,0,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do right view SetCubeFace tex,2 RotateEntity camera,0,-90,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do backward view SetCubeFace tex,3 RotateEntity camera,0,180,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do up view SetCubeFace tex,4 RotateEntity camera,-90,0,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do down view SetCubeFace tex,5 RotateEntity camera,90,0,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) EndFunction ; End of code All rendering to a texture buffer affects the currently selected face. Do not change the selected cube face while a buffer is locked. Finally, you may wish to combine the vram 256 flag with the cubic mapping flag when drawing to cubemap textures for faster access. See also: CreateTexture, LoadTexture, SetCubeMode. |
|
; SetCubeFace Example
; ------------------- width=640 height=480 depth=0 mode=0 Graphics3D width,height,depth,mode SetBuffer BackBuffer() ; If user's graphics card does not support cubic mapping then quit example If GfxDriverCaps3D()<110 Then RuntimeError "Sorry, your graphics card does not support cubic environemnt maps." cam=CreateCamera() PositionEntity cam,0,10,-10 ; Create separate camera for updating cube map - this allows us to manipulate main camera and cube camera which avoids any confusion cube_cam=CreateCamera() HideEntity cube_cam light=CreateLight() RotateEntity light,90,0,0 ; Load object we will apply cubemap to - the classic teapot teapot=LoadMesh("media/teapot.x") ScaleEntity teapot,3,3,3 PositionEntity teapot,0,10,0 ; Create some scenery ; ground ground=CreatePlane() EntityColor ground,168,133,55 ground_tex=LoadTexture("media/sand.bmp") ScaleTexture ground_tex,10,10 EntityTexture ground,ground_tex ; sky sky=CreateSphere(24) ScaleEntity sky,500,500,500 FlipMesh sky EntityFX sky,1 sky_tex=LoadTexture("media/sky.bmp") EntityTexture sky,sky_tex ; cactus cactus=LoadMesh("media/cactus2.x") FitMesh cactus,-5,0,-5,2,6,.5 ; camel camel=LoadMesh("media/camel.x") FitMesh camel,5,0,-5,6,5,4 ; Load ufo to give us a dynamic moving object that the cubemap will be able to reflect ufo_piv=CreatePivot() PositionEntity ufo_piv,0,15,0 ufo=LoadMesh("media/green_ufo.x",ufo_piv) PositionEntity ufo,0,0,10 ; Create texture with color + cubic environment map + store in vram flags tex=CreateTexture(256,256,1+128+256) ; Apply cubic environment map to teapot EntityTexture teapot,tex While Not KeyDown(1) ; Control camera ; mouse look mxs#=mxs#+(MouseXSpeed()/5.0) mys#=mys#+(MouseYSpeed()/5.0) RotateEntity cam,mys#,-mxs#,0 MoveMouse width/2,height/2 ; move camera forwards/backwards/left/right with cursor keys If KeyDown(200)=True Then MoveEntity cam,0,0,.2 ; move camera forward If KeyDown(208)=True Then MoveEntity cam,0,0,-.2 ; move camera back If KeyDown(205)=True Then MoveEntity cam,.2,0,0 ; move camera left If KeyDown(203)=True Then MoveEntity cam,-.2,0,0 ; move camera right ; Turn ufo pivot, causing child ufo mesh to spin around it (and teapot) TurnEntity ufo_piv,0,2,0 ; Hide our main camera before updating cube map - we don't need it to be rendererd every time cube_cam is rendered HideEntity cam ; Update cubemap UpdateCubemap(tex,cube_cam,teapot) ; Show main camera again ShowEntity cam RenderWorld Text 0,0,"Use mouse to look around" Text 0,20,"Use cursor keys to change camera position" Flip Wend Function UpdateCubemap(tex,camera,entity) tex_sz=TextureWidth(tex) ; Show the camera we have specifically created for updating the cubemap ShowEntity camera ; Hide entity that will have cubemap applied to it. This is so we can get cubemap from its position, without it blocking the view HideEntity entity ; Position camera where the entity is - this is where we will be rendering views from for cubemap PositionEntity camera,EntityX#(entity),EntityY#(entity),EntityZ#(entity) CameraClsMode camera,False,True ; Set the camera's viewport so it is the same size as our texture - so we can fit entire screen contents into texture CameraViewport camera,0,0,tex_sz,tex_sz ; Update cubemap ; do left view SetCubeFace tex,0 RotateEntity camera,0,90,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do forward view SetCubeFace tex,1 RotateEntity camera,0,0,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do right view SetCubeFace tex,2 RotateEntity camera,0,-90,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do backward view SetCubeFace tex,3 RotateEntity camera,0,180,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do up view SetCubeFace tex,4 RotateEntity camera,-90,0,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; do down view SetCubeFace tex,5 RotateEntity camera,90,0,0 RenderWorld CopyRect 0,0,tex_sz,tex_sz,0,0,BackBuffer(),TextureBuffer(tex) ; Show entity again ShowEntity entity ; Hide the cubemap camera HideEntity camera End Function |


Types
Button
A standard button
Icon
A button can have only an icon
Labeled Icon
A button can have an icon and a label
Primary
A button can be formatted to greatly emphasize interaction with a particular button
Secondary
A button can be formatted to show slightly emphasis a particular button
Social
A button can be formatted to link to a social website
Groups
Buttons
Buttons can exist together as a group
Conditionals
Button groups can be separated by conditionals
States
Hover
A button can change to show a user has hovered their mouse
Down
A button can change when pressed using touch or mouse events
Active
A button can show it is currently the active user selection
Disabled
A button can show it is currently unable to be interacted with
Loading
A button can show a loading indicator
Variations
Sizes
A button can have different sizes:
Basic
A basic button removes all unnecessary formatting
Colors
A button can have different colors:
Black Button Green BUtton Red Button Blue Button Purple Button Teal Button Orange ButtonToggle
A button can be formatted to toggle on and off
Feedback
A button can be positive or negative:
Fluid
A button can fit parent container:
Circular
A button can be circular:
Vertically Attached
A button can be attached to the top or bottom of other content
Horizontally Attached
A button can be attached to the left or right of other content
Group Variations
Vertical
Groups can be formatted to appear vertically
Icon
Groups can be formatted as icons
Labeled Icon
Groups can be formatted as labeled icons
Fluid
Groups can be divided evenly to fit parent
Colors
Groups can have a shared color
Basic
A button group can be formatted to remove extra formatting
Sizes
Groups can have a shared size


Something I've been exploring lately is the idea of abstracting data access away completely using the repository pattern. Before I get into the meat of this post, let's look at a basic user repository, this one uses dictionary to simulate a primary key index in a database.
class UserNotFound(Exception): def __init__(self, *args): super().__init__("User {0} not found".format(args[0].username)) class UserRepository: def __init__(self): self.users = {} def add(self, user): self.users[user.id] = user def extend(self, *users): for user in users: self.add(user) def remove(self, user): self.users.pop(user.id, None) def get(self, id): try: return self.users[id] except KeyError: raise UserNotFound(id) from None
There's a few things missing, like ordering and slicing but it works for what I'm about to get into. One of the biggest issues with the repository pattern is since it acts like an arbitrary collection of arbitrary items, finder methods tend to proliferate for every potential selection query.
Say we're writing a communal blogging site. There's one blog and many users. We'd probably like to be able to select users based on their name. So we'd add a find_by_username method. Then we add groups and now we'd like to be able to find users based on their group, so we add find_by_membership. And so on, until there's a billion find_by_x for every potential query we've thought of and there's still more missing!
Instead, what if we pretended there was some filter method on the class that would accept the idea of what we were looking for and just magically do the right thing. That's what criteria are. The method would probably look like this:
def filter(self, *criteria): query = self.users.values() for criterion in criteria: query = criterion(type(self), query) return query
Well, that's interesting, Alec, but how does it work? What's with that type(self) in the criterion call? Well, first let's look at an example.
from collections import namedtuple User = namedtuple("User", ["id", "username", "permission_level", "groups"]) users = UserRepository() users.extend(User(1, "HannahBanna", 1, ['Admins']), User(2, "FredHead", 0, ['Commenters'])) IsAdmin = PermissionLevel(1) list(users.filter(IsAdmin))
[User(id=1, username='HannahBanna', permission_level=1, groups=['Admins'])]
Whoa...what? It gets more interesting...
Group = namedtuple("Group", ['id', 'name', 'perm_level']) groups = GroupRepository() groups.extend(Group(1, 'Admins', 1), Group(2, 'Commenters', 0)) list(groups.filter(IsAdmin))
[Group(id=1, name='Admins', perm_level=1)]
...so what's going on here? Obviously the base class -- PermissionLevel -- is able to dynamically dispatch on type. Presumably if we had some SQLAlchemy based repository, we'd be able to filter that way too. The setup is actually quite simple and requires just three pieces:
- A repository [✓]
- A metaclass [ ]
- A base class [ ]
Let's start with the metaclass as it's really the heart of this all:
from functools import singledispatch from abc import ABCMeta, abstractmethod class CriterionMeta(ABCMeta): def __new__(mcls, name, bases, attrs): dispatcher = singledispatch(attrs['_default']) attrs.update({'_dispatcher': dispatcher, 'register': dispatcher.register}) return super(CriterionMeta, mcls).__new__(mcls, name, bases, attrs)
Basically, when ever a new class is created using this metaclass it gains two new attributes:
- A dispatcher
- And a registration method
For this example, I'm using functools.singledispatch because it's a really good implementation of what I'm after. However, a simpler example could just be a dictionary and it's get method. The reason for this going into a metaclass is that the dispatcher needs to be unique for every class but shared between all instances of that class. Putting this into a metaclass allows us to provide a default implementation for the single dispatch. We'll see this in a minute.
class Criterion(metaclass=CriterionMeta): @abstractmethod def _default(self, current_query): return current_query def __call__(self, repository, current_query): matcher = self._dispatcher.dispatch(repository) return matcher(self, current_query)
The base class is actually really simple. A single abstract method and the implementation of how the dispatcher is used and calling the result. As an allowance, we need to provide the type of repository being used with the criterion as well as the "current query". The current query is really anything that'll fit into the implementation we find.
Finally, let's implement the PermissionLevel criterion I showcased above.
import operator class PermissionLevel(Criterion): def __init__(self, permission_level, op=operator.eq): self.op = op self.permission_level = permission_level def _default(self, current_query): return filter(lambda obj: self.op(obj.permission_level, self.permission_level), current_query)
This is surprisingly simple. There's a default implementation of this criteria that works with iterables of objects that all have a permission_level attribute. It show cases the intent of what the criterion is supposed to do at a low level, but it's still very clear. But because of the Criterion class and the metaclass, we can implement other ways that this criterion works. For example, our Group class doesn't have permission_level attribute, but a perm_level (someone got lazy!), however this is easy to fix:
@PermissionLevel.register(GroupRepository) def group_permission_critera(criterion, cq): return filter(lambda obj: criterion.op(obj.perm_level, criterion.permission_level), cq)
Now, this is the part that feels a little hacky to me. We have to write what is essentially a method for a class, meaning we get access to all of the internals of the class, but it's an external thing that gets monkey patched into our dispatch system. It's an allowance for decoupling, but it doesn't feel kosher to me though.
However, we can use this same criterion with our UserRepository and GroupRepository. If in production, we ran with SQLAlchemy, obviously we'll want to adapt this to fit there, too.
# myapp/repositories/sqla.py from myapp.criteria import PermissionLevel @PermissionLevel.register(SQLAUserRepository) def sqla_perm_level_filter(criterion, current_query): return current_query.filter(criterion.op(User.permission_level, criterion.permission_level))
At runtime, we can configure not only which repositories are setup but all the adapters for the criteria as well with a simple import. The biggest downsides I see to this:
- Start up will be slower, as we'll end up configuring and register every criteria for every repository
- If you have five different repositories and a hundred criteria, you end up writing 500 criteria.
The first might be mitigated by Python's bytecode generation until the configuration file changes. If this changes often, it might be better to just configure all the implementations of the criteria on startup. Though this is based purely on hunches and no empirical evidence.
The second could be avoided with good, consistent design. If you have three models that all have permission levels, if the permission levels are all named the same, you could simply set up a loop that registers a lambda for each one (just be sure to keep Python's late binding rules in mind!). For example, if our User and Group both had the actual permission_level attribute, this is possible:
for repo, model in [(SQLAUserRepo UserModel), (SQLAGroupRepo, GroupModel)]: PermissionLevel.register( repo, lambda criterion, current_query, model=model: criterion.op( getattr(model, 'permission_level'), criterion.permission_level) )
There's still other issues I've yet to resolve. For example, the thing returned by default is a filter but it'd be nice if we got back something that could support further operations. So something like SQLAlchemy's query object, but only sort of. It'd be nice to do something like:
users.filter(IsAdmin & NameBeginsWith('j') & ~NameEndsWith('r')).sort(lambda user: username, reverse=True).all()
But at that point, how thin is the abstraction? I'm still mulling this over and wondering if this is viable beyond an intriguing thing.
I spilled my brains, spill some of yours.


Test cases populate localStorage in Chrome and Firefox. Review localStorage using browsers debugging tools to see database structure after running tests.


--- title: Converts a text to a sequence of indexes in a fixed-size hashing space. type: docs repo: https://github.com/rstudio/keras menu: main: name: Converts a text to a sequence of indexes in a fixed-size hashing space. - keras parent: keras-reference aliases: - /reference/keras/text_hashing_trick.html - /keras/reference/text_hashing_trick.html - /guide/keras/reference/text_hashing_trick.html - /tools/tools/keras/reference/text_hashing_trick.html - /installation/keras/reference/text_hashing_trick.html - /tutorials/keras/reference/text_hashing_trick.html - /guide/tools/keras/reference/text_hashing_trick.html - /deploy/keras/reference/text_hashing_trick.html - /tools/keras/reference/text_hashing_trick.html - /tutorials/tools/keras/reference/text_hashing_trick.html ---
Converts a text to a sequence of indexes in a fixed-size hashing space.
text_hashing_trick(
text,
n,
hash_function = NULL,
filters = "!\"#$%&()*+,-./:;<=>?@[\\]^_`{|}~\t\n",
lower = TRUE,
split = " "
)
| text | Input text (string). |
| n | Dimension of the hashing space. |
| hash_function | if |
| filters | Sequence of characters to filter out such as punctuation. Default includes basic punctuation, tabs, and newlines. |
| lower | Whether to convert the input to lowercase. |
| split | Sentence split marker (string). |
A list of integer word indices (unicity non-guaranteed).
Two or more words may be assigned to the same index, due to possible collisions by the hashing function.
Other text preprocessing:
make_sampling_table()
,
pad_sequences()
,
skipgrams()
,
text_one_hot()
,
text_to_word_sequence()


In the last section, we had an example showing a “date of birth element”:
1 2 3 4 5 6 7 8 9 10 11 |

<?php echo $form->dateOfBirth->renderLabel() ?>
<?php echo $this->formText('dateOfBirth[day]', '', array(
'size' => 2, 'maxlength' => 2)) ?>
/
<?php echo $this->formText('dateOfBirth[month]', '', array(
'size' => 2, 'maxlength' => 2)) ?>
/
<?php echo $this->formText('dateOfBirth[year]', '', array(
'size' => 4, 'maxlength' => 4)) ?>

|
How might you represent this element as a Zend\Form\Element? How might you write a decorator to render it?
The questions about how the element would work include:
The first two questions center around the form element itself: how would setValue() and getValue() work? There’s actually another question implied by the question about the decorator: how would you retrieve the discrete date segments from the element and/or set them?
The solution is to override the setValue() method of your element to provide some custom logic. In this particular case, our element should have three discrete behaviors:
Internally, the day, month, and year will be stored discretely. When the value of the element is retrieved, it will be done so in a normalized string format. We’ll override getValue() as well to assemble the discrete date segments into a final string.
Here’s what the class would look like:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 | class My_Form_Element_Date extends Zend\Form\Element\Xhtml
{
protected $_dateFormat = '%year%-%month%-%day%';
protected $_day;
protected $_month;
protected $_year;
public function setDay($value)
{
$this->_day = (int) $value;
return $this;
}
public function getDay()
{
return $this->_day;
}
public function setMonth($value)
{
$this->_month = (int) $value;
return $this;
}
public function getMonth()
{
return $this->_month;
}
public function setYear($value)
{
$this->_year = (int) $value;
return $this;
}
public function getYear()
{
return $this->_year;
}
public function setValue($value)
{
if (is_int($value)) {
$this->setDay(date('d', $value))
->setMonth(date('m', $value))
->setYear(date('Y', $value));
} elseif (is_string($value)) {
$date = strtotime($value);
$this->setDay(date('d', $date))
->setMonth(date('m', $date))
->setYear(date('Y', $date));
} elseif (is_array($value)
&& (isset($value['day'])
&& isset($value['month'])
&& isset($value['year'])
)
) {
$this->setDay($value['day'])
->setMonth($value['month'])
->setYear($value['year']);
} else {
throw new Exception('Invalid date value provided');
}
return $this;
}
public function getValue()
{
return str_replace(
array('%year%', '%month%', '%day%'),
array($this->getYear(), $this->getMonth(), $this->getDay()),
$this->_dateFormat
);
}
}
|
This class gives some nice flexibility – we can set default values from our database, and be certain that the value will be stored and represented correctly. Additionally, we can allow for the value to be set from an array passed via form input. Finally, we have discrete accessors for each date segment, which we can now use in a decorator to create a composite element.
Revisiting the example from the last section, let’s assume that we want users to input each of the year, month, and day separately. PHP fortunately allows us to use array notation when creating elements, so it’s still possible to capture these three entities into a single value – and we’ve now created a Zend_Form element that can handle such an array value.
The decorator is relatively simple: it will grab the day, month, and year from the element, and pass each to a discrete view helper to render individual form inputs; these will then be aggregated to form the final markup.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 | class My_Form_Decorator_Date extends Zend\Form\Decorator\Abstract
{
public function render($content)
{
$element = $this->getElement();
if (!$element instanceof My_Form_Element_Date) {
// only want to render Date elements
return $content;
}
$view = $element->getView();
if (!$view instanceof Zend\View\Interface) {
// using view helpers, so do nothing if no view present
return $content;
}
$day = $element->getDay();
$month = $element->getMonth();
$year = $element->getYear();
$name = $element->getFullyQualifiedName();
$params = array(
'size' => 2,
'maxlength' => 2,
);
$yearParams = array(
'size' => 4,
'maxlength' => 4,
);
$markup = $view->formText($name . '[day]', $day, $params)
. ' / ' . $view->formText($name . '[month]', $month, $params)
. ' / ' . $view->formText($name . '[year]', $year, $yearParams);
switch ($this->getPlacement()) {
case self::PREPEND:
return $markup . $this->getSeparator() . $content;
case self::APPEND:
default:
return $content . $this->getSeparator() . $markup;
}
}
}
|
We now have to do a minor tweak to our form element, and tell it that we want to use the above decorator as a default. That takes two steps. First, we need to inform the element of the decorator path. We can do that in the constructor:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | class My_Form_Element_Date extends Zend\Form\Element\Xhtml
{
// ...
public function __construct($spec, $options = null)
{
$this->addPrefixPath(
'My_Form_Decorator',
'My/Form/Decorator',
'decorator'
);
parent::__construct($spec, $options);
}
// ...
}
|
Note that this is being done in the constructor and not in init(). This is for two reasons. First, it allows extending the element later to add logic in init without needing to worry about calling parent::init(). Second, it allows passing additional plugin paths via configuration or within an init method that will then allow overriding the default Date decorator with my own replacement.
Next, we need to override the loadDefaultDecorators() method to use our new Date decorator:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | class My_Form_Element_Date extends Zend\Form\Element\Xhtml
{
// ...
public function loadDefaultDecorators()
{
if ($this->loadDefaultDecoratorsIsDisabled()) {
return;
}
$decorators = $this->getDecorators();
if (empty($decorators)) {
$this->addDecorator('Date')
->addDecorator('Errors')
->addDecorator('Description', array(
'tag' => 'p',
'class' => 'description'
))
->addDecorator('HtmlTag', array(
'tag' => 'dd',
'id' => $this->getName() . '-element'
))
->addDecorator('Label', array('tag' => 'dt'));
}
}
// ...
}
|
What does the final output look like? Let’s consider the following element:
1 2 3 4 5 6 7 | $d = new My_Form_Element_Date('dateOfBirth');
$d->setLabel('Date of Birth: ')
->setView(new Zend\View\View());
// These are equivalent:
$d->setValue('20 April 2009');
$d->setValue(array('year' => '2009', 'month' => '04', 'day' => '20'));
|
If you then echo this element, you get the following markup (with some slight whitespace modifications for readability):
1 2 3 4 5 6 7 8 9 10 11 |

Date of Birth:

<input type="text" name="dateOfBirth[day]" id="dateOfBirth-day"
value="20" size="2" maxlength="2"> /
<input type="text" name="dateOfBirth[month]" id="dateOfBirth-month"
value="4" size="2" maxlength="2"> /
<input type="text" name="dateOfBirth[year]" id="dateOfBirth-year"
value="2009" size="4" maxlength="4">

|
We now have an element that can render multiple related form input fields, and then handle the aggregated fields as a single entity – the dateOfBirth element will be passed as an array to the element, and the element will then, as we noted earlier, create the appropriate date segments and return a value we can use for most backends.
In the end, you get a uniform element API you can use to describe an element representing a composite value.
The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed.


New Project
Open Project
Click me I'm a map editor and you want to edit maps.
Click me I'm a settings button and you want to edit settings.


This is an H1 Title
Under the above h1 title we have some paragaph text. We even have a link that goes to the blog. You can click on it just fine.
Look funny chars: æ, ø, å
And a little H3 to mix it up
And under the little h3, we have more text. We can even throw a blockquote ...
We are now inside a blockquote. Look at my snazzy border.
This is copy of an H1 Title
Under the above h1 title we have some paragaph text. We even have a link that goes to the blog. You can click on it just fine.
Look funny chars: æ, ø, å
And a little H3 to mix it up
And under the little h3, we have more text. We can even throw a blockquote ...
We are now inside a blockquote. Look at my snazzy border.


@ember-data_serializer Module
Overview
In order to properly manage and present your data, EmberData needs to understand the structure of data it receives.
Serializers
convert data between the server's API format and
the format EmberData understands.
Data received from an API response is normalized into JSON:API (the format used internally by EmberData), while data sent to an API is serialized into the format the API expects.
Implementing a Serializer
There are only two required serializer methods, one for
normalizing data from the server API format into JSON:API, and
another for serializing records via Snapshots
into the expected
server API format.
To implement a serializer, export a class that conforms to the structure
described by the MinimumSerializerInterface
from the app/serializers/
directory. An example is below.
import EmberObject from '@ember/object';
export default class ApplicationSerializer extends EmberObject {
normalizeResponse(store, schema, rawPayload) {
return rawPayload;
}
serialize(snapshot, options) {
const serializedResource = {
id: snapshot.id(),
type: snapshot.modelName,
attributes: snapshot.attributes()
};
return serializedResource;
}
}
Serializer Resolution
store.serializerFor(name)
will lookup serializers defined in
app/serializers/
and return an instance. If no serializer is found, an
error will be thrown.
serializerFor
first attempts to find a serializer with an exact match on name
,
then falls back to checking for the presence of a serializer named application
.
store.serializerFor('author');
// lookup paths (in order) =>
// app/serializers/author.js
// app/serializers/application.js
Most requests in EmberData are made with respect to a particular type
(or modelName
)
(e.g., "get me the full collection of books" or "get me the employee whose id is 37"). We
refer to this as the primary resource type
.
Typically serializerFor
will be used to find a serializer with a name matching that of the primary
resource type
for the request, falling back to the application
serializer for those types that
do not have a defined serializer. This is often described as a per-model
or per-type
strategy
for defining serializers. However, because APIs rarely format payloads per-type but rather
per-API-version, this may not be a desired strategy.
It is recommended that applications define only a single application
adapter and serializer
where possible.
If you have multiple API formats and the per-type strategy is not viable, one strategy is to
write an application
adapter and serializer that make use of options
to specify the desired
format when making a request.
Using a Serializer
Any serializer in app/serializers/
can be looked up by name
using store.serializerFor(name)
.
Default Serializers
For applications whose APIs are very close to or exactly the REST format or JSON:API
format the @ember-data/serializer
package contains implementations these applications can
extend. It also contains a simple JSONSerializer
for serializing to/from very basic JSON objects.
Many applications will find writing their own serializer to be more performant and less complex than extending these classes even when their API format is very close to that expected by these serializers.
It is recommended that apps write their own serializer to best suit the needs of their API and application.
This module provides the following classes:


Hot in the city 23 Nov 2019, 18:03 by AFP Firemen hose down a fire that gutted homes at a residential area in the financial district of Manila on Nov. 22. Related stories:


I'm a Front-End/Ruby/Rails developer with an extensive background in media production.
Below, you'll find a stream of constantly updated work.
Ruby
Rails with AngularJS
Sinatra
Rails/JavaScript
Latest
Recent


Spectrum: Polyphonic synthesizer, 14 oscillator algorithms
Modal: Bowed/Blowed/Struck exciter into 64-band resonator
Resonator: 7-algorithm string synthesizer.
Granular: Granular synthesis / pitch shift / reverb / looper FX
Modulation LFO and Env for each synthesizer.
Flexible 2-source modulation routing engine.


Replies "pong!" when DTE bot is running
Displays the DTE room rules
Displays the DTE OverPlayed list
Displays your Estimated Time of Arrival
Moves you to your lost spot, in case you disconnect
Gives your spot to another user
Links this help site
Disables automatically skipping the next song
Reloads the bot
Kills the bot
Sets required amount of Meh's to skip a song


final
class.
Suggests replacing the type parameter with the type of the specified final
class since
final
classes cannot be extended.
Example:
void foo() {
List<? extends Integer> list; // Warning: the Integer class is a final class
}
After the quick-fix is applied:
void foo() {
List<Integer> list;
}


| identify {graphics} | R Documentation |
identify
reads the position of the graphics pointer when the
(first) mouse button is pressed. It then searches the coordinates
given in x
and y
for the point closest to the pointer.
If this point is close enough to the pointer, its index will be returned as
part of the value of the call.
identify(x, ...) ## Default S3 method: identify(x, y = NULL, labels = seq_along(x), pos = FALSE, n = length(x), plot = TRUE, atpen = FALSE, offset = 0.5, tolerance = 0.25, ...)
x, y |
coordinates of points in a scatter plot. Alternatively, any
object which defines coordinates (a plotting structure, time
series etc: see |
labels |
an optional character vector giving labels for the
points. Will be coerced using |
pos |
if |
n |
the maximum number of points to be identified. |
plot |
logical: if |
atpen |
logical: if |
offset |
the distance (in character widths) which separates the
label from identified points. Negative values are allowed. Not
used if |
tolerance |
the maximal distance (in inches) for the pointer to be ‘close enough’ to a point. |
... |
further arguments passed to |
identify
is a generic function, and only the default method is
described here.
identify
is only supported on screen devices such as
X11
, windows
and quartz
. On other devices the
call will do nothing.
Clicking near (as defined by tolerance
) a point adds it to the
list of identified points. Points can be identified only once, and if
the point has already been identified or the click is not
near any of the points a message is printed immediately on
the R console.
If plot
is TRUE
, the point is labelled with the
corresponding element of labels
. If atpen
is false (the
default) the labels are placed below, to the left, above or to the
right of the identified point, depending on where the pointer was
relative to the point. If atpen
is true, the
labels are placed with the bottom left of the string's box at the
pointer.
The identification process is terminated by clicking the second button and selecting ‘Stop’ from the menu, or from the ‘Stop’ menu on the graphics window.
On most devices which support identify
, successful selection of
a point is indicated by a bell sound unless
options(locatorBell = FALSE)
has been set.
If the window is resized or hidden and then exposed before the identification
process has terminated, any labels drawn by identify
will disappear. These will reappear once the identification process has
terminated and the window is resized or hidden and exposed again.
This is because the labels drawn by identify
are not
recorded in the device's display list until the identification process has
terminated.
If you interrupt the identify
call this leaves the graphics
device in an undefined state, with points labelled but labels not
recorded in the display list. Copying a device in that state
(e.g., saving the plot from the window's menu)
will give unpredictable results.
If pos
is FALSE
, an integer vector containing the
indices of the identified points, in the order they were identified.
If pos
is TRUE
, a list containing a component
ind
, indicating which points were identified and a component
pos
, indicating where the labels were placed relative to the
identified points (1=below, 2=left, 3=above, 4=right and 0=no offset,
used if atpen = TRUE
).
The algorithm used for placing labels is the same as used by
text
if pos
is specified there, the difference being
that the position of the pointer relative the identified point
determines pos
in identify
.
For labels placed to the left of a point, the right-hand edge of the
string's box is placed offset
units to the left of the point,
and analogously for points to the right. The baseline of the text is
placed below the point so as to approximately centre string vertically.
For labels placed above or below a point, the string is centered
horizontally on the point. For labels placed above, the baseline of
the text is placed offset
units above the point, and
for those placed below, the baseline is placed so that the top
of the string's box is approximately offset
units below the
point. If you want more precise placement (e.g., centering) use
plot = FALSE
and plot via text
or
points
: see the examples.
Becker, R. A., Chambers, J. M. and Wilks, A. R. (1988) The New S Language. Wadsworth & Brooks/Cole.
dev.capabilities
to see if it is supported.
## A function to use identify to select points, and overplot the ## points with another symbol as they are selected identifyPch <- function(x, y = NULL, n = length(x), pch = 19, ...) { xy <- xy.coords(x, y); x <- xy$x; y <- xy$y sel <- rep(FALSE, length(x)); res <- integer(0) while(sum(sel) < n) { ans <- identify(x[!sel], y[!sel], n = 1, plot = FALSE, ...) if(!length(ans)) break ans <- which(!sel)[ans] points(x[ans], y[ans], pch = pch) sel[ans] <- TRUE res <- c(res, ans) } res }


assignment
Create Tiny Url
Meetupinize
Sharing Multiple Upcoming Meetup Events Made Easy
Date and Time:
Location:


{% extends 'errors/base_error.html' %} {% block error_content %}
You must be developer, maintainer or owner of {{ project_name }} in GitLab to manage this visualisation.
To request access, contact a member of {{ project_name }} or contact the Data Workspace Team.
{% endblock error_content %}


WORKTIPS LOCKER
Create an Account
LOG IN
Fully Open Sourced
Light Worktips Wallet
WORKTIPS LOCKER
Create an Account
Fully Open Sourced
Light Worktips Wallet


View motivational quotes, videos, recommend speakers, add meetups.
Everybody needs motivation. Thousands of motivation quote in your hands with regular notification.
View, share, tweet on motivational speakers.
Know someone? Share trainers, inspirational speakers & performance coach details with the world through support view. Let others benefit too.


Step 1 of 3
Step 1: Complete the following sections
| About you | {{aboutYouStatus}} {{aboutYouLink}} |
| Partner status | {{aboutPartnerStatus}} {{aboutPartnerLink}} |
| Property, savings & money | {{propertyStatus}} {{propertyLink}} |
| About where you live | {{whereYouLiveStatus}} {{whereYouLiveLink}} |


C# | Unity | Gamejam | Gameplay Features | Tools
Winner of the TGA / King Gamejam 2019 award for the most inspiring casual mobile game pitch inviting the jury to want to invest in the game and especially the passion for the team behind the game.
Old Puffer was a game created during the King and The Game Assembly's gamejam collaboration. The game was created in Unity with the theme of creating a casual game. The gamejam was held from 17:00 on Friday to 11:00 on Sunday between the 25-27th of January 2019. After the game was finished at eleven, we all made our pitches for the game, resulting in our game pitch being the winner!
We were a group of four guys, where Alexander and I as programmers. Olof was the graphical artist and Peter finalizing our crew as the level designer.
I did most of the feature coding; adding the bubbles, maelstroms, finish line and transitioning between the levels. I worked on the UI of the game as well, implementing the menu UI andI also created a prefab for the tutorial boxes, allowing Peter to place them whenever needed. After killing my ears late Saturday night trying to find sounds on freesound.org, I added all the necessary sounds as well.
The bubbles were the first feature in the game that would aid the movment of Old Puffer. When Old Puffer hit the bubbles' collider, the old fish would get sucked into them and transported around between the bubbles two transportation points.
Whenever the player would swipe on the screen, Old Puffer would move in the swipe direction and be released from the bubble.
The picture above is the prefab of the bubble. The bubbles were visualized in the editor with two bubbles, the brighter one being the start point, with the paler one being the second point of movement.
The easiest way to make sure that Old Puffer moved with the bubbles would be to set the bubble as Puffers parent object. The players movement would temporarily disabled until Puffer the coroutine to "suck" Puffer to the center of the bubble was done.
The bubbles also subscribed to a death event when holding Puffer, making sure to release control of Puffer and resetting variables.
I used a coroutine function to handle the sucktion of Puffer. I find them clean to use and easy to handle. They were also fast to use and iterate with, perfect for the gamejam. I lerped the movement to the center, pleased when the fraction was close enough.


Michael Jackson
"The King of Pop"
Jackson's Life
Michael Jackson (August 29, 1958 – June 25, 2009) was an American singer, songwriter, record producer, dancer, actor, and philanthropist. His contributions to music, dance, and fashion along with his publicized personal life made him a global figure in popular culture for over four decades.
After leaving a successful short carrer as a Jackson 5 singer, Jackson pursued a solo career in the 1980s. After The popularity of these videos helped bring the television channel MTV to fame. Jackson's 1987 album Bad spawned the U.S. Billboard Hot 100 number-one singles "I Just Can't Stop Loving You", "Bad", "The Way You Make Me Feel", "Man in the Mirror", and "Dirty Diana", becoming the first album to have five number-one singles on the Billboard Hot 100. He continued to innovate with videos such as "Black or White" and "Scream" throughout the 1990s, and forged a reputation as a touring solo artist. Through stage and video performances, Jackson popularized a number of complicated dance techniques, such as the robot and the moonwalk, to which he gave the name. His distinctive sound and style has influenced numerous artists of various music genres.
Jackson is one of the few artists to have been inducted into the Rock and Roll Hall of Fame twice, and was also inducted into the Songwriters Hall of Fame and the Dance Hall of Fame as the only dancer from pop and rock music. His other achievements include multiple Guinness World Records, 13 Grammy Awards, the Grammy Legend Award, the Grammy Lifetime Achievement Award, 26 American Music Awards—more than any other artist—including the "Artist of the Century" and "Artist of the 1980s", 13 number-one singles in the United States during his solo career—more than any other male artist in the Hot 100 era—and estimated sales of over 350 million records worldwide.
My Favorite Jackson Songs
- Beat It
- The Way You Make Me Feel
- Man in the Mirror
- Smooth Criminal
- Heal the World
- Smooth Criminal
- Don't Stop 'Til You Get Enough
- Workin' Day And Night
- Wanna be Startin' Somethin'
- Thriller
- Billi Jean
- Human Nature
- Just Good Friends
- Black or White
For more information about Michael Jackson, please visit his official website.
More About Jackson


At least seven killed in Bangladesh gas explosion
by David AaroAt least seven people were killed on Sunday after a gas pipeline exploded in the Bangladeshi port city of Chittagong, a police official said.
Police Chief Mohammed Mohsin said 25 people were also taken to the hospital and firefighters have officially joined the rescue efforts. He added the death toll could rise as some of the injured were in critical condition.
The explosion rocked an area in front of a five-story building as residents were getting ready for work in the morning -- blowing some of the building's walls off, Mohsin said, according to Reuters.
ELEPHANT NAMED USAMA BIN LADEN, DIES IN CAPTIVITY AFTER KILLING 5 VILLAGERS IN INDIA, OFFICIALS SAY
Rescue workers were seen in fire helmets gathering in the rubble of the busy street where the explosion took place.
It wasn't immediately clear what caused the blast, fire official Amir Hossain told the outlet.
News reports said the road in front of the explosion site was busy with people and tricycle rickshaws. A boundary wall also fell on some people on the road.
One person suffered burns as a result of the blast, while others were wounded following the wall collapse.
Last month, a gas cylinder used to inflate balloons exploded in the capital city of Dhaka, killing seven children, according to Reuters.
The outlet says pipelines and below-par cylinders routinely are the cause of accidents in Bangladesh due to poor monitoring.
CLICK HERE TO GET THE FOX NEWS APP
Chittagong is 216 kilometers (134 miles) southeast of the capital, Dhaka.
The Associated Press contributed to the report


Komodo
equaliser
100 messages
Before 05-Dec-19 12:00 AM
Gateway
BOT
19-Jul-18 07:33 AM
[dscrdeql] <edsky> Good yourself?
[dscrdeql] <SwimedDragon> Good, just woke up so still a bit tired, but that's over after some coffee offcourse
[dscrdeql] <
Jellysmash
> Get that good dose of double caffeine and you'll feel like a new man
[dscrdeql] <
Jellysmash
> @SwimedDragon by the way
[dscrdeql] <
Jellysmash
> Good morning I meant
[dscrdeql] <SwimedDragon> Hey
You doing good today? @
Jellysmash
[dscrdeql] <PERLANGER> man i got perlanged
[dscrdeql] <PERLANGER> Hello?
[dscrdeql] <edsky> Hey
[dscrdeql] <PERLANGER> Hi edsky i see your very active in the general channel you should be a mod
[dscrdeql] <PERLANGER> have you been perlanged by the markets?
[dscrdeql] <edsky> Haha
[dscrdeql] <x2maano>
[dscrdeql] <cypherzero> good morning!
[dscrdeql] <PERLANGER> hi guys
[dscrdeql] <
Jellysmash
> @PERLANGER perlanged by the markets?
[dscrdeql] <
Jellysmash
> @PERLANGER morning
[dscrdeql] <PERLANGER> perlanged = fuck over lost money
[dscrdeql] <x2maano> morning
[dscrdeql] <edsky> Haha I think alot of people been perlanged in this market
[dscrdeql] <PERLANGER> so whenever i purchase tokens the price tanks .. and i lose money.. scientific formula known as the perlang effect
[dscrdeql] <PERLANGER> so because of all my bad luck ive become the PERLANGER
[dscrdeql] <edsky> Nice cover story
[dscrdeql] <
Jellysmash
> @SwimedDragon hi there...yea I'm going ok
[dscrdeql] <
Jellysmash
> Just walked in for at home
[dscrdeql] <
Jellysmash
> Got home from work
[dscrdeql] <
Jellysmash
> @PERLANGER interesting...I thought whatever I buy tanks...I must be a perlanger as well.
[dscrdeql] <
Jellysmash
>
[dscrdeql] <PERLANGER> known uve been perlanged
[dscrdeql] <PERLANGER> no
[dscrdeql] <edsky> Hahaha
[dscrdeql] <
Jellysmash
> Yea...I guess so
[dscrdeql] <x2maano> hello every one
[dscrdeql] <PERLANGER> yeah join the perlang club
[dscrdeql] <
Jellysmash
> He'll there @x2maano
[dscrdeql] <
KQweci
> Morning guys
[dscrdeql] <x2maano> hows the day?
[dscrdeql] <
Jellysmash
> @
KQweci
morning
[dscrdeql] <edsky> Morning
[dscrdeql] <
Jellysmash
> Looks like everyone has jumped in together
[dscrdeql] <PERLANGER> hello @x2maano
[dscrdeql] <x2maano> hhahhaha
[dscrdeql] <
KQweci
> How was ur day @jellysmash
[dscrdeql] <
Jellysmash
> Let the orgy begin
[dscrdeql] <
KQweci
> @PERLANGER I feel it pain
[dscrdeql] <
Jellysmash
> @
KQweci
ok, got some work done...it was sunny...that's always good
[dscrdeql] <PERLANGER> @
KQweci
you been PERLANGED too?
[dscrdeql] <
KQweci
> This market is crazy
[dscrdeql] <
KQweci
> Haha yeah
[dscrdeql] <
Jellysmash
> Yea, it's a real crypto crazy
[dscrdeql] <
KQweci
> It feels good to be home @jellysmash
[dscrdeql] <
Jellysmash
> Yea..great
[dscrdeql] <x2maano> any one tells the EQL rate?
[dscrdeql] <
Jellysmash
> Lovin it
[dscrdeql] <PERLANGER> one day we will all look but a laugh @ this perlanged market
[dscrdeql] <
KQweci
> Lost a lot in shit coins and tokens
[dscrdeql] <x2maano> @
KQweci
where?
[dscrdeql] <
KQweci
> Yeah it will get better
[dscrdeql] <x2maano> hoe
[dscrdeql] <x2maano> how?
[dscrdeql] <PERLANGER> alot of shillanging going on its hard to know who to trust
[dscrdeql] <
Jellysmash
> To be honest I've never checked the EQL rate, ever
[dscrdeql] <
KQweci
> In this crazy market @x2maano
[dscrdeql] <x2maano> @
Jellysmash
why????
[dscrdeql] <
KQweci
> It's crazy up lol
[dscrdeql] <
Jellysmash
> I have no idea what it's price is to btc
[dscrdeql] <x2maano> heart breaker????
[dscrdeql] <
KQweci
> KMD is up and running
[dscrdeql] <
KQweci
> Yeah but it's part of the game @x2maano
[dscrdeql] <
Jellysmash
> @x2maano I don't know, just thought if it goes up it goes up....it's not affected by whether I watch it or not
[dscrdeql] <x2maano> hmmm
[dscrdeql] <
Jellysmash
> But I'm curious now
[dscrdeql] <x2maano> hhaaahha
[dscrdeql] <x2maano> 2 minds?
[dscrdeql] <
KQweci
> EQL is price is up
[dscrdeql] <
Jellysmash
> Since its meant to be listed on exchange within next day or so
[dscrdeql] <x2maano> @
KQweci
into USD what is it????
[dscrdeql] <
Jellysmash
> In to btc what is it?
[dscrdeql] <x2maano> bitcion
[dscrdeql] <
Jellysmash
> Yes bitcoin
[dscrdeql] <x2maano> thats what i wanna know
[dscrdeql] <x2maano>
[dscrdeql] <
Jellysmash
> I kind of expected it would be something like 0.00000010 btc
[dscrdeql] <
Jellysmash
> @x2maano so do i
[dscrdeql] <x2maano> same page
[dscrdeql] <
KQweci
> It's .30 usd
[dscrdeql] <x2maano> @
KQweci
hhow you checked?
[dscrdeql] <
KQweci
> It's doing good
[dscrdeql] <
KQweci
> Blockfolio @x2maano
[dscrdeql] <
KQweci
> Or hypedex
Gateway
BOT
19-Jul-18 08:35 AM
[dscrdeql] <Catalyst> Good morning :)
[dscrdeql] <edsky> morning mate
Gateway
BOT
19-Jul-18 08:42 AM
[dscrdeql] <PERLANGER> its night over where i live
[dscrdeql] <Catalyst> noice
[dscrdeql] <Catalyst> it's a 13:44
[dscrdeql] <Catalyst>
https://cdn.discordapp.com/attachments/436529103039102978/469425711166390282/image.jpg
[dscrdeql] <x2maano> morning dude
[dscrdeql] <
KQweci
> I agree with you. New traders always get burn
[dscrdeql] <
KQweci
> Morning @Faisal
[dscrdeql] <Cypher - Founder> Haha


| 009:070 Khan | : |
Has not the story reached them of those before them? - The people of Nuh (Noah), 'Ad, and Thamud, the people of Ibrahim (Abraham), the dwellers of Madyan (Midian) and the cities overthrown [i.e. the people to whom Lout (Lot) preached], to them came their Messengers with clear proofs. So it was not Allah Who wronged them, but they used to wrong themselves. |
| 009:070 Maulana | : |
Has not the story reached them of those before them -- of the people of Noah and 'Ad and Thamud, and the people of Abraham and the dwellers of Midian and the overthrown cities? Their messengers came to them with clear arguments. So Allah wronged them not but they wronged themselves. |
| 009:070 Pickthal | : |
Hath not the fame of those before them reached them - the folk of Noah, A'ad, Thamud, the folk of Abraham, the dwellers of Midian and the disasters (which befell them)? Their messengers (from Allah) came unto them with proofs (of Allah's Sovereignty). So Allah surely wronged them not, but they did wrong themselves. |
| 009:070 Rashad | : |
Have they not learned anything from the previous generations; the people of Noah, 'Aad, Thamood, the people of Abraham, the dwellers of Midyan, and the evildoers (of Sodom and Gomorrah)? Their messengers went to them with clear proofs. GOD never wronged them; they are the ones who wronged their own souls. |
| 009:070 Sarwar | : |
Have they not heard the stories of the people of Noah, the tribe of Ad, Thamud, the people of Abraham, the dwellers of the city of Midian, and those of the Subverted Cities? God's Messengers came to each of them with miracles. God did not do any injustice to them, but they wronged themselves. |
| 009:070 Shakir | : |
Has not the news of those before them come to them; of the people of Nuh and Ad and Samood, and the people of Ibrahim and the dwellers of Madyan and the overthrown cities; their messengers came to them with clear arguments; so it was not Allah Who should do them injustice, but they were unjust to themselves. |
| 009:070 Sherali | : |
Has not the news reached them of those before them - the people of Noah, and Ad, and Thamud, and the people of Abraham, and the dwellers of Midian, and the cities which were overthrown? Their Messengers came to them with clear Signs. So ALLAH wronged them not, but they wronged themselves. |
| 009:070 Yusufali | : |
Hath not the story reached them of those before them?- the People of Noah, and 'Ad, and Thamud; the People of Abraham, the men of Midian, and the cities overthrown. To them came their messengers with clear signs. It is not Allah Who wrongs them, but they wrong their own souls. |
Concepts/Themes Covered: أركان الإسلام > التوحيد > توحيد الله تعالي > تنزيه الله تعالى عن الظلم Pillars of Islam> Islamic> Oneness of Allah> Allah the Exalted is Free of Injustice أركان الإسلام > التوحيد > توحيد الله تعالي > دعوة من لا يقر بالوحدانية إلى الاعتبار بمن سبقهم Pillars of Islam> Islamic> Oneness of Allah>A Call to those who do not Believe in Monotheism to Learn from their Antecedents الإيمان > الإيمان بالله > النفاق Faith> Belief In Allah> Hypocrisy الجهاد > الغزوات > غزوة تبوك Jihad> The Holy Battles> Tabuk Battle القصص والتاريخ > إبراهيم > قوم إبراهيم The Stories and the History>Abraham>Abraham's People القصص والتاريخ > أصحاب مَديَن (قوم شعيب) The Stories and the History>Midian People (Shu'aib Nation) القصص والتاريخ > (ثمود (قوم صالح The Stories and the History>Thamoud(Salih People) القصص والتاريخ > (عاد (قوم هود The Stories and the History>Ad(Hud's People) القصص والتاريخ > العبر التاريخية فى أنباء القرى The Stories and the History> The Historic Examples of Towns' News القصص والتاريخ > نوح > قوم نوح The Stories and the History>Noah>People of Noah القصص والتاريخ > المؤتفكات The Stories and the History>The Cities Overthrown
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


--- title: What are financial derivatives? layout: post ---
This weekend my wife convinced me to see Michael Moore's movie about Capitalism. It had its good points, its bad points, and its silly points. One of the silly points was multiple purportedly smart people finding that they couldn't explain what a financial derivative was.
Excellent plain-language explanation of some key financial instruments, specifically derivatives. Definitely worth a read if you're confused by the financial argot being slung about these days.


Home Fries Reviewed by Vince Yim
As the film opens up, expectant unwed mother Sally (played by Drew Barrymore) encounters her baby's father in a fast food drive-through window. After he gets his milkshake, he drives off, only to be pursued by a military helicopter. From this moment forward, you know that this isn't going to be your run-of-the-mill romantic comedy.
Home Fries tells the tale of the relationship between Sally and Dorian (played by Luke Wilson), a helicopter pilot who has a different kind of connection with Sally...more than he would care to admit (hint: it has something to do with the father of Sally's unborn child). After taking a personal (and professional) interest in her, he finds work at the local fast food restaurant at which she works, and the fun goes on from there.
This movie is a lot of fun. It is comedic on two levels, as a romantic comedy and a dark comedy. The romantic moments are sweet, yet not sappy. One of the more poignant moments is when Dorian accompanies Sally to Lamaze classes.
However, the dark comedic moments are more memorable. This is also a tale of revenge, and a funny one at that. The father of Sally's unborn child also happened to be a married man, whose wife is played by Catherine O'Hara. She does a wonderful portrayal of a jealous wife who is targeting the person who had an affair, and is not above getting other people to do her dirty work. (My apologies if this sounds cryptic, but there is too much of the plot to give away).
Rounding out the cast are Jake Busey as Angus, Dorian's overzealous brother and Daryl Mitchell as Roy, Dorian's trainer at the fast food restaurant. The dialogue is sharp and not filled with sappy overtones, even with the romantic nature of the plot.
If there are any complaints, it is over Drew Barrymore's performance. While she does light up the screen, there are moments when she doesn't seem all that convincing. The movie was filmed in Texas, and most of the characters have southern Texan accents. Drew Barrymore's accent tends to come and go (Luke Wilson doesn't seem to have this problem). As well, she seems awfully agile for a woman that is eight months pregnant.
Still, this movie is one that will please many viewers. With plot twists galore and hilarious dark moments, this is sure to entertain.
Rating: 7.5/10
--
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


6.2
domestic | energy | building insulation envelope | 2010
Every
building
must be designed and
constructed
in such a way that
an
insulation envelope
is provided which reduces heat loss.
Limitation:
This standard does not apply to:
(a)
non-domestic
buildings
which will not be heated, other than
heating provided solely for the purpose of frost protection;
(b)
communal parts of
domestic buildings
which will not be heated,
other than heating provided solely for the purposes of frost
protection; or
(c)
conservatories
, which are either unheated or provided with
heating which is solely for the purpose of frost protection.
6.2.0 Introduction
The levels set out in the guidance to this standard are robust back-stops and
these are necessary for the following reasons:
•
to help reduce energy demand (particularly where use of low carbon
equipment (LCE) may reduce carbon dioxide emissions but not energy
consumption); and
•
to ensure that a good level of fabric insulation is incorporated, especially
to
construction
elements that would be difficult and costly to upgrade in
the future.
Non-repeating thermal bridging at the junctions of
building
elements and
around openings in the
building
envelope form part of the calculation of
energy performance in the Standard Assessment Procedure (SAP 2009, see
clause 6.1.1). Heat loss through such junctions, if poorly designed and
constructed
, can contribute significantly to the overall heat loss through the
Limiting infiltration
As fabric insulation levels improve, heat lost through uncontrolled infiltration
of air through the
building
envelope (air permeability) becomes proportionally
greater. For example, in a typical 1960s
house
with non-draughtstripped
windows 20% of the total heat could be lost through air infiltration and
ventilation. If the same
house
was upgraded to 2002 levels of fabric
insulation but no attempt made to reduce air infiltration then the losses from
infiltration could represent up to 40% of total heat losses. Limiting infiltration,
whilst providing controllable ventilation, is therefore essential if both energy
efficiency and good indoor air quality are to be achieved.
In the case of conversions, as specified in regulation 4, the
building
as
converted
shall meet the requirements of this standard in so far as is
reasonably practicable
, and in no case be worse than before the conversion
(regulation 12, schedule 6).
6.2
—
6.2.0
domestic | energy | building insulation envelope | 2010
6.2.1 Maximum
U-values
Area-weighted average
Column a of the table below sets out robust backstop measures. In most
cases, meeting standard 6.1 will result in even better levels of thermal
insulation unless the design of a
dwelling
involves extensive use of
building
-integrated or localised low carbon equipment (LCE).
Individual element
Localised areas of the same
building
element may be designed to give a
poorer performance, providing the average
U-value
for all elements of the
same type is maintained by designing the rest of the element to a more
demanding level. An example of this would be a meter box set into an
external wall.
These localised areas should have a
U-value
no worse than
the figures given in column b of the table below. This is particularly important
with regard to the control of condensation (see section 3 Environment).
Repeating thermal bridges (e.g. timber studs in a timber frame wall) should
not be considered as an individual element in this respect, as these are
already taken into account within a BS EN ISO 6946: 2007
U-value
calculation.
Common areas
For communal areas refer to clause 6.2.13.
Maximum
U-values
for
building
elements of the insulation envelope
Type of element
(b) Individual element
Wall [1]
0.25
0.70
Floor [1]
0.20
0.70
Roof
0.18
0.35
Windows,
doors, rooflights
1.8
3.3
Notes:
1.
Excluding
separating walls
and
separating floors
between heated
areas where thermal transmittance need not be assessed, provided
measures to limit heat loss arising from air movement within the
cavity
separating wall
are made (see below).
Cavity
separating walls
Recent research has established that previously unanticipated heat loss can
arise via air movement, within a cavity
separating wall
, from heated areas to
points outwith the insulation envelope. To limit heat loss, a
separating wall
cavity should have effective perimeter sealing around all exposed edges and
in line with insulation layers in abutting elements which separate the
dwelling
from another
building
or from an unheated space. Further reduction in heat
loss can be achieved where the cavity
separating wall
is also fully filled with a
material that limits air movement.
In addressing this issue, regard should be paid to the need to limit noise
transmission (see section 5 Noise).
Information on reducing heat loss from air movement in a cavity
separating
wall
can be found in the Building Standards Division document
‘Accredited
6.2.1
—
6.2.1
domestic | energy | building insulation envelope | 2010
6.2.2 Areas of windows, doors and rooflights
Due to the target method set by carbon dioxide emissions standard 6.1, there
is no need for guidance on minimum or maximum area for windows, doors,
rooflights and roof windows in new
dwellings
.
The methodology for establishing compliance with standard 6.1 considers
conflicting energy issues of heat loss versus solar gain and natural lighting
versus artificial lighting. In certain cases, where there is a desire to have a
large proportion of glass it may be difficult to demonstrate compliance with
standard 6.2. In such cases, innovative solutions will need to be considered.
All relevant standards and guidance should be considered, including
standard 6.6, on avoiding high internal summer temperatures.
Guidance on alterations, extensions and conversions is provided in clauses
6.2.6 to 6.2.13.
Common areas
For communal areas refer to clause 6.2.13.
6.2.3 Limiting heat loss through thermal bridging
As insulation values of new
buildings
improve, the need to limit heat loss
through thermal bridging becomes increasingly important. Incorrect detailing
at design stage or poor
construction work
can have a significant adverse
effect on
building
performance.
The
insulation envelope
of any heated
building
should be designed and
constructed
to limit heat loss through thermal bridging. The key areas of
concern are:
•
repeating thermal bridging within
building
elements; and
•
non-repeating thermal bridging at the junction between
building
elements
and at the edges of
building
elements where openings in the envelope are
formed.
Whilst repeating thermal bridges are taken into account in the BS EN ISO
6946: 2007
U-Value
calculation, a separate assessment of non-repeating
thermal bridging should be carried out for new
buildings
which are subject to
standard 6.1. Advice and further information on assessment of the effects of
thermal bridging can be found in BRE Information paper IP 1/06 –
‘Assessing
A value for non-repeating thermal bridging, which should be input into SAP
2009, can be determined in one of the following ways:
a. a conservative default y-value of 0.15 may be assumed; or
b. where
construction
is in accordance with the BSD document
'Accredited
Construction Details (Scotland) 2010'
an assessed value can be
calculated simply, using the
Y
(psi) value of each junction (provided in the
document) and the lengths of the thermal bridging element of each
junction; or
c. a
Y
-value derived from numerical modelling of individual
Y
(psi) values
calculated in accordance with BS EN ISO 10211: 2007 ‘Thermal bridges in
building construction - heat flows and surface temperatures - detailed
calculations’. Guidance on this process is given in BR 497,
‘
Conventions
Further commentary on this process and use of other published documents
providing sources of pre-calculated values can be found within
6.2.2
—
6.2.3
domestic | energy | building insulation envelope | 2010
6.2.4 Limiting uncontrolled air infiltration
To limit heat loss, any heated
building
should be designed to limit
uncontrolled air infiltration through the
building
fabric. This is done by
providing a continuous barrier that resists air movement through the
insulation envelope
and limits external air paths into each of the following:
•
•
spaces between the component parts of exposed
building
elements,
where such parts contribute to the thermal performance of the element.
Using a target-based methodology for new
buildings
in standard 6.1 (carbon
dioxide emissions), a reduction in uncontrolled infiltration will allow greater
design flexibility in the application of other energy performance measures.
The infiltration rate used for the TER calculation is 7 m
3
/m
2
.h @ 50 Pa (see
clause 6.1.2). Whilst no backstop value is set for uncontrolled infiltration, it is
@ 50 Pa or better to allow a balanced approach to managing
building
heat
loss.
Designing and
constructing
a
building
in accordance with the principles set
out in BSD's document
'Accredited Construction Details (Scotland) 2010'
will
assist in limiting air infiltration. Due to the contribution of both detailing and
workmanship, it remains difficult to achieve a specified air infiltration rate with
any degree of accuracy. To ensure the
dwelling
will deliver the intended
thermal performance without adversely affecting air quality, air tightness
testing should be undertaken to verify as-built air infiltration rates (see clause
6.2.5).
Limiting air infiltration to improve energy performance should not compromise
ventilation required for:
•
the health of the occupants of the
building
(section 3);
•
the removal of moisture from
building
fabric (section 3);
•
the safe operation of combustion appliances (section 3); and
•
any smoke control system (section 2).
Lower air infiltration rates, of less that 5 m³/m².h @ 50 Pa, may give rise to
problems with internal air quality and condensation. Accordingly, where
design infiltration rates are proposed below this rate, reference should be
made to additional measures needed to ensure air quality under standard
3.14, on provision of ventilation within
dwellings
.
Common areas
consideration to limit air infiltration include common stair entrances and
shafts which extend through most of the floors (e.g. lift and common stair
enclosures).
6.2.5 Air-tightness testing
Low air infiltration rates will contribute to energy performance but should not
be so low as to adversely affect the health of occupants or the
building
fabric.
There is, therefore, a need to establish
building
performance by test, to
demonstrate compliance in both these respects.
Evidence from testing of
dwellings
,
constructed
to the 2007 Accredited
Construction Details (Scotland), and of similar
constructions
elsewhere in the
UK, indicates that air-tightness levels of 5 to 7 m
3
/m
2
.h @ 50 Pa are readily
achievable and can be exceeded unintentionally. Air-tightness testing should
6.2.3
—
6.2.5
•
the ‘warm’ side of insulation layers;
domestic | energy | building insulation envelope | 2010
be carried out on new
buildings
to ensure that air infiltration rates deliver both
the stated design level under this guidance and minimum levels of ventilation
needed (see section 3 Environment).
In order to allow the capacity of the testing industry to grow in Scotland, the
need to carry out infiltration testing is being phased in as follows:
•
For building warrant applications made on or after 1 May 2011 - testing of
flats
and
maisonettes only
; and
•
For building warrant applications made on or after 1 October 2011
– testing of all
dwelling
types.
Frequency of
testing
dwellings
As a baseline, testing of completed
dwellings
should be carried out on 1 in 20
dwellings
or part thereof. The verifier may, however, request that the
frequency of testing be varied, as considered appropriate to reasonable
enquiry and in response to previous test results within a development.
In larger developments, it is advisable to test more than one example of the
same
dwelling
type, completed at different stages in the overall development,
to help establish consistency in quality of
construction
.
In smaller developments, the proportion of
dwellings
tested may need to
increase, dependant on the range of type and form of
dwellings
present, to
ensure a representative sample is taken.
Normally for a development of one
dwelling
, an air-tightness test should be
carried out as it will not be possible to obtain comparative data on the quality
of construction from similar
dwellings
. Alternatively, where a default design
value of 15 m³/m².h @ 50 Pa is stated in demonstrating compliance under
standard 6.1, testing need not be carried out.
Test methods
Testing should be in accordance with BS EN 13829: 2001 – ‘Thermal
performance of buildings - determination of air permeability of buildings - fan
pressurization method’. Practical advice on procedure for pressure testing is
given in the ATTMA publication
‘Measuring Air Permeability of Building
Testing should be carried out by persons who can demonstrate relevant,
recognised expertise in measuring the air permeability of
buildings
. This
should include membership of a professional organisation which accredits its
members as competent to test and confirm the results of testing.
6.2.6 Conversion of unheated
buildings
A
building
that was originally designed to be unheated has, in most
instances, the greatest void to fill in terms of energy efficiency. Heating such
buildings
will adversely affect energy efficiency and because of this, the most
demanding of measures are recommended when
conversion
occurs.
Where
conversion
of an unheated
building
(e.g. a barn) or part of a
dwelling
is to be carried out, the
building
should achieve the same standards to those
for an extension to the
insulation
envelope by following the guidance in
clauses 6.2.9 and 6.2.10. This same approach should be taken for the
conversion
of
buildings
with heating rated at a maximum of 25 W/m² floor
area and installed solely for the purposes of frost protection.
Conversion of part
of a
dwelling
Examples of
work
which involve
conversion
of part of a
dwelling
are:
changing a
roof space
, an unheated garage or a deep solum space into an
6.2.5
—
6.2.6
domestic | energy | building insulation envelope | 2010
•
in the case of a
roof space
, this will usually involve extending the
insulation envelope
to include, the gables, the collars, a part of the rafters
and the oxters, as well as any new or existing dormer
construction
. The
opportunity should be taken at this time to upgrade any remaining poorly
performing parts of the roof which are immediately adjacent to the
conversion, for example, insulation to parts of the ceiling ties at the eaves;
•
in the case of an unheated garage, this will usually involve extending the
insulation envelope
to include, the existing floor, perimeter walls and the
roof/ceiling to the new habitable part; and
•
in the case of a deep solum space, this will usually involve extending the
insulation envelope
to include, the solum/existing floor and perimeter walls
to the new habitable part.
6.2.7 Conversion of heated
buildings
In the case of a
building
that was previously designed to be heated, the
impact on energy efficiency as a result of the conversion, may be either
negligible, none whatsoever or in some circumstances even an improvement.
A less demanding approach than identified in clause 6.2.6 is recommended
which at the same time still ensures that some overall improvements are
being made to the existing
building
stock.
Where an extension or
conservatory
is formed and/or alterations are being
made to the
building
fabric at the same time as the conversion, the guidance
given in clauses 6.2.9 to 6.2.12 should also be followed.
Where conversion of a heated
building
is to be carried out, the
existing
insulation envelope
should be examined and upgraded following the
table below:
Maximum
U-values
for
building
elements of the insulation envelope
Type of element
Wall [1 ][2]
0.30
0.70
Floor [1 ][2]
0.25
0.70
Roof [1]
0.25
0.35
Where new and replacement
windows, doors, rooflights are
installed [3][4]
1.6
3.3
Notes:
1.
Where upgrading
work
is necessary to achieve the recommended
U-values
, reference should be made to ‘Reconstruction of elements’
in clause 6.2.11 and more demanding
U-value
s achieved, where
2.
Excluding
separating walls
and
separating floors
between heated
areas where thermal transmittance need not be assessed, provided
measures to limit heat loss arising from air movement within a cavity
separating wall
are made (see clause 6.2.1).
3.
The total area of windows, doors and rooflights, should not exceed
25% of the floor area of the
dwelling
created by conversion.
Alternatively, a compensatory approach should be taken.
4.
Windows with a window Energy rating of Band C or better may also
be used
(www.bfrc.org)
6.2.6
—
6.2.7
domestic | energy | building insulation envelope | 2010
6.2.8 Conversion of historic, listed or
traditional buildings
With historic, listed or
traditional buildings
, the energy efficiency improvement
measures that should be invoked by
conversion
can be more complex.
Whilst achieving the values recommended in clause 6.2.7 should remain the
aim for previously heated
buildings
, a flexible approach to improvement
should be taken, based upon investigation of the
traditional construction
,
form and character of the
building
in question and the applicability of
improvement methods to that
construction
. Provisions under other legislation
(e.g. planning consent for listed
buildings
or those within conservation areas,
where there is a need to maintain character, form or features) are also
relevant.
For previously unheated
buildings
, now to be heated, it would be advisable to
consider the feasibility of upgrading fabric to at least the
U-values
given in
column b in clause 6.2.9 (individual element
U-values
). In many cases,
specialist advice will be helpful in making an assessment to ensure that, in
improving energy efficiency, there is no other, adverse effect to the
building
fabric.
Accordingly, each
building
will have to be dealt with on its own merits.
Improvements to the fabric insulation of the
building
will often depend on
factors such as whether or not improvement
work
can be carried out in a
non-disruptive manner without damaging existing fabric (for example,
insulating the ceiling of an accessible
roof space)
or whether potential
solutions are compatible with the existing
construction.
In certain cases,
buildings
are given historic or listed status because of
specific features present in certain parts of the
building
. In these
circumstances, it may be possible to make greater improvements to other
less sensitive areas.
In all cases the ‘do nothing’ approach should not be considered initially.
Innovative but sympathetic and practical solutions to energy efficiency, which
are beyond the scope of this guidance, can often result in an alternative
package of measures being developed for a
building
. For example, carbon
dioxide emissions can be reduced without affecting
building
fabric through
improvements to the heating system (refer to standards 6.3 and 6.4), the
lighting system (standard 6.5) or incorporation of low carbon equipment (such
as a biomass boiler or heat pump). Consultation on such matters at an early
stage with both the verifier and the planning officer of the relevant authority is
advised.
6.2.9 Extensions to the insulation envelope
Extension of a
building
is not subject to standard 6.1. In view of this,
measures to limit energy demand and carbon dioxide emissions rely primarily
upon the performance of the new
building
fabric.
As the majority of
construction work
for an extension will be new, there will
seldom be the need to consider
construction
to a lesser specification as is
sometimes the case for conversions and alterations. The exception to this is
at the junction between existing and new, for example the need for
proprietary metal ‘wall starter’ ties where the existing brickwork stops and
new cavity blockwork begins. However other
building
standards should still
be met with regard to such transitional
construction
elements.
6.2.7
—
6.2.9
domestic | energy | building insulation envelope | 2010
benefit from the provision of an efficient heating system or low carbon
equipment (LCE). Therefore, fabric
U-values
should improve on the new build
backstops identified in clause 6.2.1 to limit CO
2
emissions and energy
demand to an equivalent level.
Accordingly, where the
insulation envelope
of a
dwelling
or a
building
designed in accordance with one of two levels of elemental
U-values
for
walls, floors, roof, windows, doors and rooflights, as shown in the table
below.
by the energy performance of the existing
building
, assessing
external wall
and roof elements. Where a
building
has
external walls
with a
U-value
poorer
than 0.7 and a roof with a
U-value
poorer then 0.25, then the more
demanding
U-values
in column a should be applied to the extension. Where,
existing wall and roof elements already meet or, as part of the
works
, will be
column b can be applied to the extension.
Maximum
U-values
for
building
elements of the insulation envelope
Type of
element
Area-weighted average
U-value
(W/m²K)
for all elements of the same type
(a)where
U-values
for wall and roof of
the existing
dwelling
are poorer
than 0.7 [1] and
0.25 respectively
(b) where
parameters for
column (a) do not
apply
Wall [2]
0.19
0.22
0.70
Floor [2]
0.15
0.18
0.70
Pitched roof
(insulation
between ceiling
ties or collars)
0.13
0.15
0.35
0.15
0.18
0.35
Windows, doors,
rooflights
1.4 [3]
1.6 [4]
3.3
Notes:
1.
The Building Standards (Scotland) Amendment Regulations 1982,
came into force on 28 March 1983, introduced thermal insulation for
an exposed wall broadly equivalent to 0.7 W/m
2
K.
2.
Excluding
separating walls
and
separating floors
between heated
areas where thermal transmittance need not be assessed, provided
measures to limit heat loss arising from air movement within a cavity
separating wall
are made (see clause 6.2.1).
6.2.9
—
6.2.9
domestic | energy | building insulation envelope | 2010
3.
Windows with a Window Energy Rating of Band A may also be used
4.
Windows with a Window Energy Rating of Band C or better may also
be used
www.bfrc.org
this clause are summarised in the diagram below. The extension is the
shaded portion, the existing
dwelling
is in elevation behind.
Area of windows, doors,
rooflights
Where the
insulation envelope
of a
domestic building
is extended, the area of
windows, doors, rooflights and roof windows should be limited to 25% of the
floor area of the extension plus the area of any openings built over and
removed as a result of the extension
work
. This figure may be exceeded if
the compensatory approach, below, is adopted.
Varying
U-values -
'Compensatory approach'
that the area-weighted overall
U-value
of all the elements in the extension is
no greater than that of a ‘notional’ extension. The ‘notional’ extension should
be the same size and shape as one designed to the elemental
U-values
in
the table above with the area of windows, doors and rooflights taken as 25%
of the total extension floor area (plus equivalent area of 'built over openings').
An example of this approach is given in annex 6B.
Where SAP data is available for the existing
dwelling
, it may be practical to
provide a revised SAP calculation to demonstrate compliance of a
dwelling
,
as proposed, including extension, as part of the enlarged
dwelling
, using the
target-based methodology (DER not more than TER) set out in guidance to
standard 6.1 (carbon dioxide emissions). This option will generally only be
viable where both extension and
dwelling
are built to the same, current
edition of the standards.
6.2.9
—
6.2.9
domestic | energy | building insulation envelope | 2010
6.2.10 Thermal bridging and air infiltration for existing
buildings
work
should follow the guidance in clauses 6.2.3 and 6.2.4 and reference
should be made to the principles set out in BSD's document
'Accredited
Construction Details (Scotland) 2010'.
It should be noted that standard 6.1
does not apply to this type of
work
unless the designer chooses to use the
methodology identified in guidance to standard 6.1, as noted in clause 6.2.9.
In such cases, a default value of 10m³/m².hr @50 pa can be assumed or the
testing of the extension carried out as identified in clause 6.2.5.
In addition, the recommendations within Building Research Establishment
(BRE) Report 262
'Thermal insulation, avoiding risks’
2002 edition can be
followed.
6.2.11 Alterations to the insulation envelope
For alterations it is more than likely that the existing
construction
will be from
will need to be considered on its own merits. Some of the guidance given in
this clause is written in specific terms, but in certain cases (e.g. historic, listed
or
traditional buildings
), it may be necessary to adopt alternative energy
efficiency measures which relate to the amount of alteration
work
being
undertaken.
Extending the
insulation
Alterations that involve increasing the floor area and/or bringing parts of the
existing
building
that were previously outwith the
insulation envelope
into the
heated part of the
dwelling
are considered as extensions and/or
conversions
(regulation 4, schedule 2) and reference should be made to the relevant
guidance clause for such
work
.
Infill of small openings
fabric should have a
U-value
which matches at least that of the remainder of
the surrounding element. In the case of a wall or floor however it should not
be worse than 0.70 W/m
2
K, and for a roof, not worse than 0.35 W/m
2
K.
Infill of large openings
The infill of an existing opening of greater area (than approximately 4 m
2
) in
of the table to clause 6.2.9. Another way would be to follow the guidance in
the paragraph above, but compensate for the energy efficiency deficit by
improving the overall
U-value
of other parts of the
insulation envelope.
Where the alteration causes an existing internal part or other element of a
building
to form the
insulation envelope
, that part of the
building
(including
any infill
construction
) should have
U-values
which achieve those in column b
of the table to clause 6.2.9. This will most likely occur where a part of a
approach would be to follow the guidance given for 'infill of small openings'
above, but compensate for the energy efficiency deficit by improving the
overall
U-value
of other parts of the
insulation envelope
. Where this occurs at
a
boundary
, no upgrading need be carried out if the element is a wall that is
exclusively the property of the adjoining
building
.
Windows, doors,
rooflights
Where windows, doors and rooflights are being created or replaced, they
should achieve the
U-value
recommended in column b of the table to clause
6.2.9. A compensating approach may be used and an example of this is
given in annex 6A. For secondary
glazing,
an existing window, after alteration
6.2.10
—
6.2.11
domestic | energy | building insulation envelope | 2010
1 or 2 replacement windows or doors, to allow matching windows or doors be
installed, the frame may be disregarded for assessment purposes, provided
Area of windows, doors,
rooflights
Where additional windows, doors and rooflights are being created, the total
area (including existing) of these elements should not exceed 25% of the
total
dwelling
floor area.
In the case of a heated communal
room
or other area (exclusively associated
with the
dwellings
), it should not exceed 25% of the total floor area of these
rooms
/areas.
Reconstruction of
elements
Where the build-up of an element forming part of the
insulation envelope
is to
be altered or dismantled and rebuilt, the opportunity should be taken to
improve the level of thermal insulation. Column b of the table to clause 6.2.9
gives benchmark
U-values
and in many cases these can be achieved without
technical risk, within the constraints of the existing
construction
. It is
recognised however that certain
constructions
are easier to upgrade than
others. A
building
that was in a ruinous state should, after renovation, be able
to achieve almost the level expected of new
construction
. It may not however
be
reasonably practicable
for a
dwelling
, which is in a habitable condition, to
have its internal space significantly reduced in area or height in order to
accommodate insulation; or for excessive enabling alterations to be caused
by the fitting of external thermal insulation, unless the owner/
occupier
of the
standards and the impact that they will have when upgrading thermal
insulation should be taken into account. In the majority of cases however
after an alteration of this nature to the
insulation envelope
, a roof should be
able to achieve at least an average
U-value
of 0.35 and in the case of a wall
or floor, 0.70 W/m
2
K.
Further guidance on this subject can be found on the Energy Saving Trust
website.
Thermal bridging and air
infiltration
When alterations are carried out, attention should still be paid to limiting
thermal bridging at junctions and around windows, doors and rooflights and
limiting air infiltration (clause 6.2.10). As far as alterations are concerned,
existing
building
need be considered.
6.2.12
Conservatories
Conservatories
are a common addition to many
dwellings
. Traditionally used
as an ancillary space, occupied for part of the year,
conservatories
are now
often used year-round leading to an increased heating demand. Accordingly,
such
buildings
should, like other heated
stand alone buildings,
be
Some smaller
conservatories
can be exempt from both
building
warrant and
building
standards (see section 0).
Conservatories
of 50 m² or more are
subject to standard 6.1 of the non-domestic guidance.
Thermal division
A
conservatory
should be thermally divided from a
dwelling
, being outwith the
insulation envelope
of the
dwelling
. The dividing elements (e.g. wall, door,
window) should have
U–values
equal or better than the corresponding
exposed elements in the rest of the
dwelling
.
6.2.11
—
6.2.12
domestic | energy | building insulation envelope | 2010
Although
conservatories
are attached to
dwellings,
they are
stand-alone
buildings
. Where not exempt, a
conservatory
(heated or unheated) should be
columns b and c of the table in clause 6.2.9, with the exception that
glazing
and framing elements forming the walls or roof of a
conservatory
are
unlimited in area and should have a maximum area weighted average
W/m²K.
elements is no greater than 2.0 W/m²K. An example of this approach is given
in annex 6A.
Thermal bridging
and air infiltration
In order to limit air infiltration and thermal bridging at junctions and around
windows, doors and rooflights, guidance in clause 6.2.10 should be followed.
If using the BSD document:
'Conservatories'
these issues will be considered
to have been taken into account. Draught stripping for windows and doors
which are part of the thermal division between the
conservatory
and the
dwelling
should be of a similar standard as the exposed windows and doors
elsewhere in the
dwelling.
6.2.13
Stand-alone buildings
Thermal division of a
stand-alone building
from the remainder of a
dwelling
or
domestic building
is explained in the clause 6.2.12.
For heated
stand-alone buildings
of less than 50 m², the fabric values
identified in columns b and c of the table to clause 6.2.9 and clause 6.2.10
should be followed.
U-value
recommendations should be met, though it
should be noted that the area of
glazing
is not limited. This allows, for
example, a
dwelling
to be extended to create a highly-
glazed stand-alone
clause 6.2.9.
Reference should be made to clause 6.1.7 and use of the non-domestic
calculation methodology to assess carbon dioxide emissions.
Common areas
Where the total area of a communal
room
or other heated accommodation
accommodation should also be treated as a
stand-alone building
. Elements
(including dividing elements) should have
U-values
equal to or better than
those chosen for the rest of the
building,
as determined in conjunction with
the methodology in standard 6.1. As part of a new
building
, the area of
windows, doors, rooflights and roof windows in these
rooms
or
accommodation should be limited to 25% of the total floor area of these
common areas.
6.2.12
—
6.2.13


The Programming Languages' World . .
Java is a class-based, object-oriented programming language developed by Sun Microsystems in the 1990s. It's one of the most in-demand programming languages, a standard for enterprise software, web-based content, games and mobile apps, as well as the Android operating system.
A general-purpose, imperative programming language developed in the early '70s, C is the oldest and most widely used language, providing the building blocks for other popular languages, such as C#, Java, JavaScript andPython.
C++ is an intermediate-level language with object-oriented programming features, originally designed to enhance the C language. C++ powers major software like Firefox, Winamp and Adobe programs. It's used to develop systems software, application software, high-performance server and client applications and video games.
C# is a multi-paradigm language developed by Microsoft as part of its .NET initiative. Combining principles from C and C++, C# is a general-purpose language used to develop software for Microsoft and Windows platforms.
Objective-C is a general-purpose, object-oriented programming language used by the Apple operating system. It powers Apple's OS X and iOS, as well as its APIs, and can be used to create iPhone apps, which has generated a huge demand for this once-outmoded programming language.
PHP (Hypertext Processor) is a free, server-side scripting language designed for dynamic websites and app development. It can be directly embedded into an HTML source document rather than an external file, which has made it a popular programming language for web developers.
Python is a high-level, server-side scripting language for websites and mobile apps. It's considered a fairly easy language for beginners due to its readability and compact syntax, meaning developers can use fewer lines of code to express a concept than they would in other languages.
A dynamic, object-oriented scripting language for developing websites and mobile apps, Ruby was designed to be simple and easy to write. It powers the Ruby on Rails (or Rails) framework, which is used on Scribd, GitHub, Groupon and Shopify. Like Python, Ruby is considered a fairly user-friendly language for beginners.
JavaScript is a client and server-side scripting language developed by Netscape that derives much of its syntax from C. It can be used across multiple web browsers and is considered essential for developing interactive or animated web functions.
Structured Query Language (SQL) is a special-purpose language for managing data in relational database management systems. It is most commonly used for its "Query" function, which searches informational databases.
Copyright © 2014 Pillars Of IT. All rights reserved.


SA based Zimbo teacher gunned down in broad daylight over cell phone
by Sharon ChirisaSA based Zimbo teacher gunned down in broad daylight over cell phone
South African police are investigating a homicide after a 49-year-old school teacher was gunned down for his cellphone.
The incident happened early on Monday morning in Delft South as Zimbabwean national Henry Chikutuva was on his way to work.
Chikutuva had come to South Africa three months ago for work, leaving behind a wife and three children.
He was shot twice in the left side of his chest, close to his heart and in his left shoulder and he succumbed to the injuries before paramedics arrived.
According witnesses five armed men came out of the bushes and demanded Henry’s cellphone and taxi money.
 The robbers took off and left Chikutuva lying on the ground bleeding.
According to the deceased’s sister-in-law, Florence Chigume, 43, he lived alone in a flat around the corner from her Kershout Street home.
She says Henry graduated from the University of Zimbabwe, and had recently taught at the University of Namibia, but opted to come to Cape Town three months ago when he got a job to teach at the Bright Student Learning Centre in Summer Greens, a private school specifically for Zimbabwean nationals.
Police spokesperson Siyabulela Malo told the Daily Voice case of murder has been opened for investigation with no arrests so far.
YOU MAY ALSO BE INTERESTED IN
Shocker As Police Detain 10-Month-Old Baby & Mother After Brutal Crackdown On Civilians
WATCH: Armed Robbers Make Off With $18K After Unleashing Terror In Harare Shop
LATEST:Hungry Soldier Fires Gun At Zimbabwe State House
To View and Apply for the latest Jobs and Vacancies in Zimbabwe, Please Visit our Sister website iHarare Jobs


IV Calculator
IV Calculator
IV Calculator
Pokemon (required):
CP (required):
HP:
Stardust:
Raid
Hatched
Field research
Anything else
Calculate
Reset
CP
AT/DF/ST
Level
HP
IV
CP Calculator
Pokemon :
Evolve into :
Original Level:
ATK IV:
DEF IV:
HP IV:
Target Level:
Hatched?
Lucky?
Calculate
Reset
CP
AT
DF
ST
Catch Rate Calculator
Pokemon :
Pokemon Level:
Ball Type :
Red
Blue
Ultra
Curve?
Berry :
Normal
Silver
Golden
Medal :
None
Bronze
Silver
Golden
Platinum
Radius :
None
Nice
Great
Excellent
Calculate
Reset
CP
AT
DF
ST
Errors?
Drop me an email.


Responsive images
Test purpose
- Setup the canvas element so it picks up its parent element's dimension updates
- Import a responsive image (with a srcset attribute) from the DOM
- Create a Picture entity and set it to cover the canvas
- Change the browser's viewport size
- Check that when the browser selects a different srcset image, the canvas displays that image
- Check that the canvas always displays the entire image, not a part of it
Annotated code


| Stratify {BIOsurvey} | R Documentation |
Selects data and calculates within strata estimates of mean and variance.
Stratify(data.obj, strata.group, species, subset)
data.obj |
data.frame (class = strata.data) prepared by Prepare.strata.data .
|
strata.group |
List object prepared by Prepare.strata.file .
|
species |
name of element in data.obj specifying what species' catches are to be analysed.
|
subset |
expression specifying which subset of observations should be used in the fit. This can be a logical vector (which is replicated to have length equal to the number of observations), a numeric vector indicating the observation numbers to be included, or a character vector of the observation names that should be included. All observations are included by default. |
The data object can contain survey data for more than just the strata of interest. Selection of which strata are to be included are specified with strata.group.
Missing values (NA's) are allowed for all arguments and are automatically removed from the analysis.
stratify returns a list of class strata with required components for further analyses of the data. If the result is unassigned, print.strata will automatically give means, variances, sample sizes and the stratum weight for each stratum.
yhi |
the number of animals caught in tow i in strata h. |
Strata |
the stratum label for each tow. |
Nh |
the total number of population sample units in stratum h. |
Wh |
the proportion of the area in stratum h. |
nh |
the total number of sampled units in stratum h. |
descrip |
the total number of sampled units in stratum h. |
Cochran, W.G. (1977). Sampling Techniques. John Wiley & Sons. New York, N.Y.
Smith, S.J. (1996). Analysis of bottom trawl survey data, In Assessment of groundfish stocks based on bottom trawl survey results. H. Lassen (Ed.) NAFO Scientific Council Studies 28: 25–53.
Prepare.strata.data
,
print.strata
,
summary.strata
.
Scallop.numbers.2008<-Stratify(Scallop.stratadata,Scallop.strata, species=Commercial)