2.9
domestic | fire | escape | 2010
Every
building
must be designed and
constructed
in such a way that
in the event of an outbreak of fire within the
building
, the occupants,
once alerted to the outbreak of the fire, are provided with the
opportunity to escape from the
building
, before being affected by fire
or smoke.
be provided with at least one route of escape through an
exit
door which
leads to a
place of safety
outside the
building
. Occupants in
dwellings
may
not be aware of the speed that fire can spread and if they are asleep are
more likely to delay their escape. Therefore, it is important that a fire alarm is
installed to provide occupants with early warning of fire (see standard 2.11).
In some cases, a fire alarm alone may not be sufficient and a protected route
within the
dwelling
may be necessary due to the height that occupants are
located above the ground. Occupants in
dwellings
located near the ground
have the added benefit of access to windows to escape in an emergency.
Flats
and
maisonettes
Once outside
flats
or
maisonettes
, occupants may still need to escape
through common areas within the
building
to reach a
place of safety
. This is
termed an ‘
escape route
’. The
building
should be designed to inhibit fire and
smoke spread into the
escape route
. Where occupants have only one means
of escape from the
building
, automatic smoke ventilation is normally provided
to help remove any smoke and heat that may enter the
escape route
.
Following the outbreak of fire anywhere in the
building
, there may be
residents located in common lounges, communal laundry
rooms
and solid
waste storage
rooms
. Service engineers may also be working in service
spaces, plant rooms and lift machine rooms for example. These occupants
should also be provided with the opportunity to escape from the
building
following a fire. The non-domestic Technical Handbook should be used for
guidance on travel distances within ancillary
rooms
and for
escape routes
serving such
rooms
.
It is common practice for the fire and rescue service to intervene and
commence fire-fighting and rescue operations before all occupants have
made their escape to a
place of safety
. However compliance with standard
2.9 should reduce the risk of occupants becoming trapped by fire and smoke.
If a fire has accidentally or deliberately been set in the common stair, the
escape route
may become impassable. In such cases occupants should be
able to remain safely inside the
building
until the fire has burnt itself out or
until the fire has been contained and it is safe to use the
escape route
.
Fire protection measures
Fire protection measures used to protect routes of escape and to provide a
safe refuge include a combination of passive and active protection. Walls,
floors, and doors can provide good passive fire protection. Active systems
such as automatic detection, automatic smoke ventilation and automatic
suppression are designed to activate in the earlier stages of fire development
to provide early warning, control heat and smoke and inhibit fire growth. All
escape strategies incorporate a combination of passive and active fire
protection measures.
2.9
—
2.9.0
domestic | fire | escape | 2010
Exclusions and
obstacles to escape
A lift should not be used for escape because there is a risk that the lift could
malfunction during the outbreak of fire. Fire-fighters may use a fire-fighting lift
to rescue injured occupants but this is matter for the fire and rescue service
to decide, following a risk assessment at the incident.
Fixed ladders are considered to be too dangerous for residents to use for
escape however a fixed ladder may be used from a lift machine room or a
plant room provided it is not a
place of special fire risk
. These rooms will only
be used intermittently by engineers who are likely to be familiar with and
trained in the use of fixed ladders.
Locking devices on final
exit
doors and on escape windows should not
prevent occupants escaping from the
building
. The intention is to assist
escape, but not to exclude the use of locks or other safety devices (see
section 4 Safety). Permanent obstructions such as fixed security grills should
not be used on final
exit
doors or escape windows.
Conversions
In the case of conversions, as specified in regulation 4, the
building
as
converted
shall meet the requirement of this standard (regulation 12,
schedule 6).
2.9.1 Escape within
dwellings
- general principles
The time occupants need to escape varies enormously and is dependent on
a number of risk factors including, early warning of fire, the occupant
of the
storey
below ground.
Early warning
Early warning of fire is one of the key fire safety measures to provide
occupants with sufficient time to escape from the
building
before being
overcome from the effects of fire and smoke. Sleeping occupants will react
more slowly and it is important that they receive the earliest possible warning
of the outbreak of fire within the
dwelling
. Guidance to standard 2.11 provides
recommendations for the installation of fire detection and alarm systems in
Occupant characteristics
The occupant characteristics in
dwellings
are wide ranging and therefore
impossible to quantify in building standards. The guidance in the Handbooks
assumes that the occupants are capable of moving or being moved to a
place of safety.
For
dwellings
that require to be licensed as a house in
multiple occupation, or where a care service is provided for the occupants,
additional fire protection measures may be required to satisfy other legislation
(see 2.0 Introduction).
Number of
exit
doors
dwelling
has 2 or more
exit
doors which lead to a
place of safety
, the risk that
occupants could become trapped by fire and smoke would be low and the fire
protection measures would be minimal. However this is not practical to
achieve in the majority of cases and as a result, the guidance recommends
2.9.0
—
2.9.1
domestic | fire | escape | 2010
Area of an individual
occupants have available for escape from a fire originating in the
dwelling
. A
the guidance (see 2.0 Introduction). In such cases, an alternative approach
(see clause 2.0.8) based on the guidance contained in this handbook may be
appropriate but the need for additional
exits
and additional fire protection
measures would need to be considered on a case by case basis.
Height of
storey
above
ground
Increased height brings extra risk, both in the time needed for escape and
the difficulties posed to the fire and rescue service in attempting to assist
evacuation, effect rescue or fight fires. Therefore, the fire protection
higher above the adjacent ground level than other
rooms
. In such cases, the
storey
depth below the adjacent ground or storey height above the adjacent
ground from each
room
may be assessed individually and the guidance
followed accordingly.
The scope of the guidance is limited to those
storeys
at a depth of not more
than 4.5 m below the adjacent ground level and to those
buildings
with no
adjacent ground (see 2.0 Introduction).
2.9.2 Escape within
dwellings
- options
In the event of an outbreak of fire, every
dwelling
should be provided with at
least one route of escape through an
exit
door which leads ultimately to a
place of safety
. The route within a
dwelling
will normally comprise a
than one
storey
such as
houses
and
maisonettes
, the occupants may be
stair
towards the floor of fire origin. The occupants would then need to
therefore the guidance recognises the increased risk in multi-
storey
The following table summarises the recommendations for escape within
dwellings
. For example, a typical 2
storey house
would normally have a
topmost
storey
not more than 4.5 m and from the following table should be
provided with at least one route of escape through an
exit
door, early warning
(smoke and heat alarms) and escape windows.
2.9.1
—
2.9.2
domestic | fire | escape | 2010
Escape within
dwellings
(
houses
,
flats
and
maisonettes
)
Height of topmost
storey
of
dwelling
above, or
basement depth below
adjacent ground
Summary of recommendations [1] [2]
1 route of escape, early warning [3] and:
• escape windows (see clause 2.9.4); or
•
alternative exit
(see clause 2.9.6)
Topmost
storey
not more
than 4.5 m
1 route of escape, early warning [3] and:
• escape windows (see clause 2.9.4)
1 route of escape, early warning [3] and:
• escape windows (see clause 2.9.4) and;
•
protected enclosure
(see clause 2.9.5); or
• suppression and enhanced early warning (see clause 2.9.7)
1 route of escape, early warning [3] and:
a. for
houses
and
maisonettes
:
• escape windows (see clause 2.9.4) and;
•
protected enclosure
(see clause 2.9.5) and
alternative exit
(see clause 2.9.6); or
•
protected enclosure
(see clause 2.9.5) and suppression [5]
b. for
flats
:
• escape windows (see clause 2.9.4) and;
•
protected enclosure
(see clause 2.9.5); or
• suppression and enhanced early warning (see clause 2.9.7)
1 route of escape, early warning [3] and:
a. for
maisonettes
:
• escape windows (see clause 2.9.4);
•
protected enclosure
(see clause 2.9.5) and suppression [5]
b. for
flats
:
• escape windows (see clause 2.9.4);
• suppression and enhanced early warning (see clause 2.9.7)
Notes:
1.
No
storey
height more than 60 m (see clause 2.0.3).
2.
3.
See guidance to standard 2.14 for explanation of 7.5 m and 18 m trigger heights and
additional fire fighting facilities.
5.
See guidance to standard 2.15 for suppression systems.
2.9.2
—
2.9.2
4.
See guidance to standard 2.11 for early warning systems.
domestic | fire | escape | 2010
2.9.3 Escape within
dwellings
-
basement storeys
A
basement storey
may have no windows or a limited number of
ventilators
which can cause a significant build up of heat and smoke. The fire may
become suppressed as the oxygen is depleted however if the door to the
basement storey
(or
room
of fire origin) is opened, the sudden intake of air
together with the release of hot fire gases can cause an explosive event
known as a backdraught. This rapid fire spread places occupants on the
ground or
upper storeys
at greater risk. Therefore, the
private stair
serving
the
basement storey
should be separated at the
ground storey
by
construction
having a short fire resistance duration.
There is a risk that occupants in a
basement storey
could become trapped
following the outbreak of fire. This is because windows are often positioned
too high above the floor level to access with ease or they may lead to an
enclosed space below the adjoining ground level from which there is no
escape. Therefore, an
alternative exit
(see clause 2.9.6) should be provided
from the
basement storey
unless escape windows are provided from every
basement
apartment
.
2.9.4 Escape within
dwellings
- escape windows
Occupants in a
basement storey
or in an
upper storey
at a height of not more
than 4.5 m may have access to escape windows. The use of windows for
escape should only ever be considered in an emergency situation as a last
resort and should not form part of the principal route of escape. Where
occupants are trapped on
upper storeys
, they can use the window to call for
assistance or to supply fresh air whilst awaiting rescue. If conditions within
the
room
become untenable, the occupant can use the window to escape
and lower themselves to the adjoining ground. This inevitably involves some
degree of risk and windows in a
storey
at a height of more than 4.5 m are
considered to be too high above the adjacent ground from which to escape.
Therefore, an escape window should be provided in every
apartment
on an
upper storey
at a height of not more than 4.5 m above the adjacent ground.
However this is not necessary where there is an alternative route of escape
Occupants within an
inner room
can become trapped where there is an
outbreak of fire in the adjoining access
room
. Therefore, every
inner room
on
a
storey
at a height of not more than 4.5 m above the adjacent ground level
should be provided with an escape window unless the
inner room
has an
alternative route of escape.
Escape windows should be large enough to escape through and should be
situated in an
external wall
or roof. The windows should have an
unobstructed openable area that is at least 0.33 m² and at least 450 mm
high and 450 mm wide. The route through the window may be at an angle
rather than straight through and the bottom of the openable area should be
not more than 1100 mm above the floor.
Conservatories
The location of
conservatories
also presents some difficulties in relation to
escape windows. Where a
conservatory
is located below an escape window
consideration should be given to the design of the
conservatory
roof to
withstand the loads exerted from occupants lowering themselves onto the
roof in the event of a fire. However the choice to
construct
a more robust roof
and frame is a matter of preference and the decision to do this should remain
with the owner.
2.9.3
—
2.9.4
domestic | fire | escape | 2010
2.9.5 Escape within
dwellings
-
protected enclosures
Occupants in
apartments
(e.g. lounges, bedrooms etc) may be asleep during
the outbreak of fire. Where they are located on a
storey
at a height of more
than 4.5 m above the adjacent ground there is a greater risk of becoming
trapped by fire and smoke. For this option (see table to clause 2.9.2), every
ground should provide direct access to a
protected enclosure
which leads to
an
exit
door.
Protected enclosures
should be designed and
constructed
to withstand fire in
an adjoining
room
or space. The
protected enclosure
should form a complete
enclosure having a short fire resistance duration.  A
cupboard door need not be self-closing unless there is an ignition source
within the cupboard such as an electrical distribution board or a boiler.
2.9.6 Escape within
dwellings
-
alternative exits
For this option (see table to clause 2.9.2), every
upper storey
in a
house
or
maisonette
at a height of more than 7.5 m above the adjacent ground should
be provided with an
alternative exit
. The intention is to reduce the risk that
occupants could become trapped within their own
dwelling
and provide them
with the opportunity to turn away from the fire on the floor of fire origin and
make their escape in the other direction. Where the second route of escape
is by way of another
private stair
, the stair should be enclosed in a
protected
enclosure
which leads to an
alternative exit
.
2.9.7 Escape within
dwellings
- open plan option with suppression
and enhanced early warning
Open plan layouts are becoming more popular with modern living styles. For
this option (see table to clause 2.9.2), the following guidance should be
door.
Where the topmost
storey
height is more than 4.5 m above the adjoining
ground an automatic life safety fire suppression system and an enhanced
early warning system should be installed to protect the occupants. In a
slower developing fire, the early warning system should provide the
occupants with sufficient time to escape and in those cases where the fire
develops quickly, the suppression system should control the fire giving the
occupants the opportunity to escape.
The automatic life safety fire suppression system should be designed and
installed in accordance with BS 9251: 2005. For the purposes of satisfying
standard 2.9, the limit in the scope of BS 9251: 2005 to
buildings
below 20 m
in height can be ignored.
The enhanced early warning system should follow the guidance in
BS 5839: Part 6: 2004 for a grade D, category LD1 system. Where this option
is adopted in
sheltered housing complexes
, a grade C system should be
installed (see standard 2.11).
2.9.5
—
2.9.7
domestic | fire | escape | 2010
systems
Ducted
heating or ventilation systems should not transfer fire and smoke from
dwelling
has a
basement storey
or a
storey
at a height of more than 4.5 m
spaces:
•
•
supply and return grilles should be not more than 450 mm above floor
level; and
•
where warm air is
ducted
to a
protected enclosure
, the return air should be
ducted
back to the heater; and
•
enclosure
, all joints between the
duct
and the surrounding
construction
should be
fire stopped
; and
•
than 1370 mm and not more than 1830 mm, with an automatic control
which will turn off the heater, and actuate any circulation fan should the
ambient temperature rise to more than 35°C; and
•
where the system recirculates air, smoke detectors should be installed
within the
duct
to cause the recirculation of air to stop and direct all extract
air to the outside of the
building
in the event of fire.
Fire dampers should be installed where the
ducts
pass through fire resisting
construction
or alternatively fire resisting ductwork should be provided. In
either case, the fire resistance duration of the
construction
should be
maintained.
2.9.9
Escape routes
- general principles
Once occupants have left the
flat
,
maisonette
or any other ancillary
room
or
space, they should be protected from fire and smoke to allow them sufficient
time to escape from the
building
in relative safety. Those occupants who are
remote from the fire are more likely to be unaware of the outbreak and may
delay their evacuation. People also move more slowly on stairs than they do
stairs.
The fire dynamics can be significantly different in
high rise domestic
buildings
. The effect of the wind may be greater which could accelerate the
speed, direction and intensity of the fire. For example, if a window is open or
breaks under fire conditions or the door to the
dwelling
of fire origin is
opened, the wind could accelerate fire growth to such an extent that the
entire
flat
or
maisonette
becomes fully involved in the fire. The wind direction
might also induce cross flows of fire and smoke that could endanger
fire-fighters entering the
dwelling
and any occupants attempting to escape
from adjoining
dwellings
. A further risk in
high rise domestic buildings
is the
loss of smoke buoyancy in tall shafts such as stairs which may cause
stratification of smoke before it reaches the smoke
ventilator
at the top of the
stairwell.
2.9.8
—
2.9.9
domestic | fire | escape | 2010
2.9.10
Escape routes
- options
The guidance assumes that in most cases, a fire will start inside a
dwelling
or
escape route
should be provided from every
flat
,
maisonette
and from the
following ancillary
rooms
or spaces serving a
domestic building
:
•
communal
room
e.g. a communal lounge or laundry in a
sheltered housing
complex
;
•
plant room;
•
solid waste storage room;
•
store room;
•
lift machine room; and
•
accessible service
duct
or cupboard.
The above list is not intended to be comprehensive and any other
room
or
space should be provided with at least one
escape route
. The non-domestic
Technical Handbook should be used for guidance on travel distances within
ancillary
rooms
and
escape routes
serving such
rooms
.
There are many options available to designers when considering
escape
routes
in
buildings
containing
flats
and
maisonettes
. These options can be
subdivided into 2 broad categories:
•
internal
escape routes
e.g. protected corridors and protected stairs; and
•
external
escape routes
e.g. protected balconies or protected external
Where
protected enclosures
(see clause 2.9.5) or an automatic fire
suppression system (see clause 2.9.7) are installed within a
domestic
building
, there is no need to provide protected lobbies (see clause 2.9.13)
between the
dwellings
and the
escape stair
. However there is a risk that the
fire protection measures may not be maintained by the occupants of the
the adjacent ground level. The intention is to limit the size and height of a
domestic building
where some reliance is placed on fire precautions within a
dwelling
that also protects the common
escape route
.
The limitation on travel distance within protected lobbies is intended to
reduce the time it takes occupants to escape and to reduce their potential
exposure to fire and smoke. Automatic smoke ventilation should be provided
within every
protected lobby
to improve tenability conditions within the
The following table summarises the recommendations when designing
buildings
containing
flats
and
maisonettes
.
2.9.10
—
2.9.10
domestic | fire | escape | 2010
Escape routes
(
flats, maisonettes
and ancillary
rooms
and spaces)
Height of topmost
storey
of
dwelling
above, or
basement depth below
adjacent ground
Summary of recommendations [1]
Basement storey
(see
clause 2.9.11) at a depth
not more than 4.5 m (if
applicable) and topmost
storey
not more than 7.5 m
[2]
at least 1
escape route
:
•
protected enclosures
in
dwellings
(see clause 2.9.5); and
at least 1
escape route
and:
at least 1
escape route
and:
• protected lobbies (see clause 2.9.13);
• smoke ventilation (see clauses 2.9.14 – 2.9.16);
• not more than 10 m travel distance inside
protected lobby
; or
at least 2
escape routes
and:
• not more than 30 m travel distance in protected corridor
at least 1
escape route
and:
• protected lobbies (see clause 2.9.13);
• smoke ventilation (see clauses 2.9.14 – 2.9.16);
• not more than 10 m travel distance inside
protected lobby
; or
at least 2
escape routes
and:
• not more than 30 m travel distance in protected corridor
at least 1
escape route
and:
• protected lobbies (see clause 2.9.13);
• smoke ventilation (see clauses 2.9.14 – 2.9.16);
• suppression [3];
• not more than 10 m travel distance inside
protected lobby
; or
at least 2
escape routes
and:
• suppression [3];
• not more than 30 m travel distance in protected corridor
Notes:
1.
See diagrams for guidance on measurement of travel distance.
2.
See guidance to standard 2.14 for explanation of 7.5 m and 18 m trigger heights and
additional fire fighting facilities.
3.
See guidance to standard 2.15 for suppression systems.
2.9.10
—
2.9.10
domestic | fire | escape | 2010
2.9.10
—
2.9.10
domestic | fire | escape | 2010
2.9.11
Escape routes
-
basement storeys
A
basement storey
with insufficient ventilation can cause a significant build
up of heat and smoke. If the door to the
basement storey
is opened, the
sudden intake of air together with the release of hot fire gases can cause an
explosive event known as a backdraught which can create significant flaming
through the door opening. There is also a risk that disoriented occupants
could continue their escape to the
basement storey
instead of escaping
through the
ground storey
. In order to minimise these risks, a medium
duration fire resisting wall or screen (including a
self-closing fire door
) should
be provided in the
protected zone
at the
ground storey
to separate the
basement storey
from the remainder of the
protected zone
.
2.9.12
Escape routes
-
protected zones
Protected zones
are intended to provide a place of relative safety inside the
building
. Occupants using the
escape stair
should be safe from the effects of
fire and smoke during their evacuation to a
place of safety
. The enclosing
structure of a
protected zone
should have at least a medium fire resistance
duration. In the case of a
high rise domestic building
the
protected zone
should have a long fire resistance duration.
Self-closing fire doors
in the
enclosing structure of a
protected zone
need only achieve a short fire
resistance duration and in the case of a
high rise domestic building
, a
medium fire resistance duration.
External walls
adjacent
If a
protected zone
has an
external wall
that projects beyond the face of a
building
or is set back in a recess, the
protected zone
may be vulnerable if
fire breaks out through an adjacent window, door or other opening. Radiated
heat or flames from the fire may impede occupants using the
protected zone
to escape.
Therefore, where any part of an
external wall
of a
protected zone
is not
more than 2 m from, and makes an angle of not more than 135 degrees with
any part of an
external wall
in another part of the
building
, the
protected zone
should be protected against fire for a distance of 2 m by
construction
which
provides a medium fire resistance duration. The designer can choose which
wall should be fire resisting and may include fire resisting facades or other
2.9.10
—
2.9.12
domestic | fire | escape | 2010
fixed
glazing
or any other opening protected against fire. However it is not
sufficient to use the final
exit
door as a barrier between the occupants
escaping and the fire. In such cases, the
external wall
adjoining the
protected
2.9.13
Escape routes
- protected lobbies
A
protected lobby
is located within a
protected zone
and is designed to inhibit
the
escape stair
or fire-fighting lobby. This is normally achieved by fire
resisting
construction
together with at least 2 sets of
self-closing fire doors
between the fire and the
escape stair
or fire-fighting lobby.  For
high rise domestic
buildings t
he wall between the
escape stair
and the
protected lobby
should
have a medium fire resistance duration and any
self-closing fire door
should
have a short fire resistance duration. See guidance to standard 2.14 for
fire-fighting facilities.
Protected lobbies in
domestic buildings
are used:
•
to inhibit fire and smoke spread to
escape stairs
;
•
to help evacuees escape from the floor of fire origin;
•
to provide protection and space for the fire and rescue service to set up a
forward control point (see standard 2.14); and
•
to provide a bridgehead from which to commence fire fighting and rescue
operations (see standard 2.14).
In order to inhibit fire and smoke spread to the
escape stair
and to help
evacuees on the floor of fire origin reach the
escape stair
, automatic smoke
ventilation should be provided and travel distance within the lobby is limited
to 10 m. Where
flats
or
maisonettes
are accessed from an open access
balcony, there is no need to provide a
protected lobby
.
Protected lobbies should be designed that smoke entering one
protected
lobby
should not spread to other protected lobbies. There should be no
inter-connection between protected lobbies other than:
•
the escape stair;
•
a smoke ventilation shaft;
•
protected services;
•
fire mains; or
•
passenger lift or fire-fighting lift.
Any gaps or imperfections of fit should be
fire-stopped
.
2.9.14
Escape routes
- smoke ventilation
Although there are physical barriers to fire such as walls, floors and doors,
there is still a risk of smoke spread into
escape routes
. Therefore, smoke
ventilation should be provided in protected lobbies, fire-fighting lobbies and
protected corridors to help maintain tenable conditions within
escape routes
.
2.9.12
—
2.9.14
domestic | fire | escape | 2010
The fire and rescue service will normally be in attendance before all
flats
or
maisonettes
have been evacuated. Therefore, it is important that the smoke
ventilators
(including powered systems) are capable of being opened, closed
or shut off by fire and rescue personnel to assist them with their fire-fighting
and rescue operations (see standard 2.14).
Smoke ventilation of
escape routes
can be provided by:
•
natural smoke ventilation; or
•
mechanical smoke ventilation.
The merits and limitations of each system should be assessed by the
designer before deciding which system to choose.
2.9.15
Escape routes
- natural smoke ventilation
Natural ventilation uses external openings in the roof or walls of the
building
to remove smoke using its own buoyancy. The efficiency of a natural smoke
ventilation system depends upon the location of the
ventilator
and the
direction and velocity of the prevailing wind. Under certain conditions, the
smoke flow through
ventilators
may be enhanced whilst under other
conditions, it may be impaired. Ideally the location of
ventilators
should be
positioned on the
building
in negative pressure zones and inlets in positive
pressure zones however this is difficult to achieve for all wind directions.
Natural smoke ventilation can be provided by either:
•
automatic opening
external wall ventilators
; or
•
smoke shafts.
Every
protected lobby
should be provided with natural smoke
vents
on an
direct to the external air. The
ventilators
should be actuated automatically by
means of smoke detectors in the common space.
Smoke Shafts
A natural smoke shaft uses the natural buoyancy of the smoke together with
the effect of the wind passing over the top of the shaft to help draw the
smoke through the shaft to the outside air. The design of natural smoke
shafts is based on a fire providing a heat output of not more than 2.5
megawatts through an open door of 780 mm wide. This scenario simulates a
maisonette
. Where the fire produces cooler smoke (e.g. a smouldering fire),
the smoke might not escape so readily when subject to adverse wind or stack
effects. The inlet/outlet configuration will vary depending wind direction and
designers should take this into account. For example, a vent cowl could be
installed on the top of the smoke shaft to help draw the smoke out of the
shaft for all wind directions. The full research report ‘Smoke ventilation of
common access areas of
flats
and
maisonettes
(BD 2410) – Final Factual
Report (BRE, 2005)' can be accessed on the BRE website.
The shaft should be closed at the base and replacement air is provided from
the automatic opening
ventilator
in the adjacent stairwell to help the efficiency
of the shaft system. The smoke shaft should have:
•
a minimum cross-sectional area 1.5 m² (minimum dimension 0.85 m in
any direction), opening at roof level at least 0.5 m above any surrounding
structures within a horizontal distance of 2.0 m; and
•
the minimum area of the
ventilator
from the
protected lobby
into the shaft
and at the opening at the head of the shaft and at all internal locations
within the shaft (e.g. safety grilles) should be at least 1 m²; and
•
the smoke shaft should have at least a medium fire resistance duration
2.9.14
—
2.9.15
domestic | fire | escape | 2010
and all
ventilators
should have a short fire resistance duration; and
•
the shaft should be vertical from base to head but may have not more than
4 m at an inclined angle not more than 30º from the vertical plane; and
•
on detection of smoke in the
protected lobby
, the
ventilator
on the fire
floor, the
ventilator
at the top of the smoke shaft and the 1 m²
ventilator
at
the head of the stairway should all open simultaneously. The
ventilators
from the
protected lobbies
on all other
storeys
should remain closed.
2.9.16
Escape routes
- mechanical smoke ventilation
Mechanical smoke ventilation using pressure differentials may be used to
inhibit smoke spread into
escape routes
by means of:
•
depressurisation systems; or
•
pressurisation systems; or
•
heating and ventilation systems.
For more detailed guidance on the design of smoke control systems using
pressure differentials is available in BS EN 12101: Part 6: 2005.
Depressurisation systems
A depressurisation system is based on the principle of extracting smoke to
the outside air. This creates a negative pressure in the space relative to the
adjacent spaces. Where a smoke ventilation depressurisation system is
used, replacement air should be provided for the system to operate
effectively. The volume of air and smoke removed should be replaced with
the equivalent volume of replacement air at a sufficient rate in order to ensure
a smoke flow out of the
building
. Reducing the rate of replacement air can
result in the smoke ventilation system becoming less efficient whereas
increasing replacement air and extraction at high velocities can produce air
pressure conditions which make doors difficult to open. The system should
be balanced to ensure that the forces required to open doors are not greater
than those specified in section 4 Safety.
Pressurisation systems
A pressurisation system is based on the principle of forcing air into the
escape route
which helps to keep smoke out. Forced air can be used to
maintain a positive pressure in the
escape route
which produces an air flow
through gaps around doors preventing the smoke from entering. The system
design should take account of likely pressure reduction when occupants
open doors to escape or when fire-fighters open doors to access the fire. The
system should be balanced to ensure that the forces required to open doors
are not greater than those specified in section 4 Safety.
Heating and ventilation
systems
Ducted
heating and/or
ventilation
systems, including air conditioning
pass through fire resisting
construction
unless the
ducts
have a medium fire
resistance duration or in the case of a
high rise domestic building
, the
ducts
have a long fire resistance duration.
The system installed to maintain interior environment conditions in a
building
should not compromise the function of the mechanical smoke ventilation
system. Therefore, in the event of an outbreak of fire, the system should
automatically either shut off or its function integrated with any smoke
ventilation system that serves the
escape routes
. For more detailed guidance
refer to BS 5588: Part 9: 1999.
2.9.15
—
2.9.16
domestic | fire | escape | 2010
2.9.17
Escape routes
- mixed use
buildings
remain undetected for some time and reach a severe intensity (due to fire
load) before the occupants in the
flats
or
maisonettes
get warning. Therefore,
where a
protected zone
is shared with a non-
domestic building
, a
protected
lobby
should be provided between the non-
domestic building
and the
escape
stair
to provide additional time for the residential occupants to escape. For
additional protected lobbies, see clause 2.9.24.
Where
flats
or
maisonettes
share a
protected zone
with a non-
domestic
building
, the height of the topmost
storey
of the
domestic building
should be
limited to 7.5 m to reduce the number of occupants who might be affected by
a fire originating in the non-
domestic building
.
2.9.18
Escape routes
- fire hazard rooms and services
Fire hazard rooms and services can present a potential source of fire ignition
and fire spread into common
escape routes
.
The following fire hazard rooms and service spaces adjacent to
escape
routes
should be separated from the
escape route
by a
construction
that
provides a medium fire resistance duration:
•
communal room e.g. a communal lounge or laundry in a
sheltered housing
complex
;
•
plant room;
•
solid waste storage room;
•
store room;
•
lift machine room; and
•
service
duct
or cupboard.
Even if the room does not contain an ignition source, the potential for a fire to
be set accidentally or deliberately should be assessed. For example, the door
to a solid waste storage room might be left unlocked. For this reason, any
door accessing a fire hazard room should be a
self-closing fire door
with a
cupboard should be locked to prevent unauthorised entry therefore does not
need be fitted with a self-closing device.
Fuel pipes
Pipes conveying fuel inside
protected zones
and protected lobbies could
accelerate fire growth and under certain conditions, create an explosive
atmosphere within the
building
. Oil and liquefied petroleum gas can produce
pool fires (i.e. a turbulent fire burning above a horizontal pool of vaporising
hydrocarbon fuel). The pool fire can either be static, where the pool is
contained, or a ‘running’ pool.
Fuel pipes carrying oil (other than a pipe conveying oil supplying a hydraulic
lift) should be located outside
protected zones
and protected lobbies.
Fuel pipes carrying natural gas or liquefied petroleum gas (including
associated meters) may be located inside
protected zones
or protected
lobbies provided:
•
the installation is in accordance with the requirements of the Pipelines
Safety Regulations 1996, SI 1996 No 825 and the Gas Safety (Installation
and Use) Regulations 1998 SI 1998 No 2451; and
•
any pipe in a
protected zone
is
constructed
of screwed steel or welded
steel
construction
; and
•
the pipe or pipes are contained within a service shaft having a medium fire
2.9.17
—
2.9.18
domestic | fire | escape | 2010
resistance duration; and
•
the service shaft is ventilated at high and low level in accordance with
BS 8313: 1997.
2.9.19
Escape routes
-
construction
of
escape stairs
Escape stairs
should be protected from the outbreak of fire to allow
occupants to escape and fire-fighters to access the fire. Therefore, every part
of an
escape stair
(including landings) and the floor of a
protected zone
(including the floor of
protected
lobbies), should be
constructed
of
non-combustible
products.
However this does not apply to:
•
•
any handrail, balustrade or protective barrier on an
escape stair
; or
•
a floor finish (e.g. laminate flooring) applied to the
escape stair
(including
landings) or to the floor of a
protected zone
or
protected lobby
.
2.9.20
Escape routes
- openings
Fire and smoke can easily pass through openings in
escape routes
which
could prevent the occupants from escaping in the event of an outbreak of fire
within the
building
. For this reason, the openings should be designed to
inhibit the spread of fire and smoke into the
escape route
. Where fire shutters
or dampers are installed as part of a
ducted
system, they should be activated
by localised smoke detectors.
In order to inhibit the spread of fire and smoke, openings in
separating walls
and floors and openings in protected routes of escape should be protected
and
fire-stopped
in accordance with the guidance to standard 2.2.
2.9.21
Escape routes
- junctions
The junctions between
escape routes
and other parts of the
building
are
vulnerable to fire and smoke. This is because fire and smoke can penetrate
weaknesses at junctions which could compromise the
escape route
. The
designer should consider detailing at junctions to inhibit fire and smoke
spread into
escape routes
.
In order to inhibit the spread of fire and smoke, junctions in
separating walls
and floors and junctions in protected routes of escape should be protected
and
fire-stopped
in accordance with the guidance to standard 2.2.
2.9.22
Escape routes
- external
escape routes
and
escape stairs
Protection of external
route of escape
Escape routes
will normally lead to the final
exit
door of the
building
, which
leads to a safe place in the outside air from which occupants can freely
disperse. An
exit
can also lead to an external
escape stair
giving access to a
In some cases it may not be possible to freely disperse away from the
space). In such cases, where there is only 1 route of escape, the
external
resistance duration for integrity up to 1.1 m above the adjoining ground. This
does not apply to sub-floor vents.
2.9.18
—
2.9.22
domestic | fire | escape | 2010
An external
escape stair
is an unenclosed
escape stair
which is open to the
external air and provides occupants with an
escape route
which leads to a
place of safety
. External
escape stairs
present additional hazards to people
escaping from
buildings
in the case of fire. This is because the
escape stair
may be exposed to inclement weather during the evacuation. For this reason,
an external
escape stair
should not serve a
building
where the topmost
storey
height is more than 7.5 m above the adjacent ground.
In order to protect the occupants from fire and smoke during evacuation, the
external
escape stair
should be protected against the outbreak of fire from
within the
building
. Where the
escape stair
has a total rise of more than
1.6 m, every part of the
external wall
including fixed windows or
glazing
,
self-closing fire doors
(other than a door opening from the top
storey
) or any
other opening not more than 2 m from the
escape stair
, should have a short
fire resistance duration. Fire protection below an
escape stair
should be
extended to the lowest ground level.
An external
escape stair
with a total rise of not more than 1.6 m from which
occupants can freely disperse, is considered to be low enough above the
ground to present minimal risk to occupants leaving the
building
and as a
result, fire protection need not be provided.
2.9.23
Escape routes
- open access balconies
An open access balcony can be used as an
escape route
from
flats
or
maisonettes.
Fire and smoke should ventilate more freely than an enclosed
escape route
. The balcony should be open to the external air and have an
opening that extends over at least four-fifths of its length and at least one
third of its height.
Where only one direction of escape is available, the travel distance along an
open access balcony should be not more than 40 m. However where the
balcony provides 2 directions of escape, the travel distance can be unlimited.
Flames and smoke from a fire may emanate from a window or other opening
in the
external wal
l of a
flat
or
maisonette
. Therefore, where an open access
balcony provides escape in 1 direction only, the
external
wall up to a height
of at least 1.1 m above the level of the balcony should be provided with
a short fire resistance duration to allow evacuees to pass below the level of
windows in relative safety.
In order to protect occupants escaping from
flats
or
maisonettes
on
storeys
above the fire floor, every open access balcony should have a medium fire
resistance duration from the underside. Openings in the floor of the balcony
should be
fire-stopped
in accordance with the guidance to standard 2.2.
Wide balconies above the floor of fire origin could present a risk to occupants
escaping on the fire floor. This is because lateral fire and smoke spread
along the underside of the balcony may compromise the
escape route
.
Therefore, in order to inhibit lateral fire and smoke spread, every balcony
more than 2 m wide should be provided with smoke channels or down-stands
at 90 degrees to the face of the
building
on the same line as the
separating
should be at least 300 mm below the soffit of the balcony.
2.9.22
—
2.9.23
domestic | fire | escape | 2010
2.9.24
Escape routes
- refuge within
building
Research and fire investigation reports from fire and rescue services show
that the incidence of multiple fire deaths and injuries beyond the
dwelling
of
fire origin is uncommon. This is because:
•
fire and smoke spread is contained mainly to the
dwelling
of fire origin by
the
construction
of
separating walls
and
separating floors
(see standard
2.2);
•
occupants in
flats
and
maisonettes
(other than the
flat
or
maisonette
of fire
origin) are protected from fire and smoke by the
construction
of
separating
walls
and
separating floors
; and
•
fire and rescue service intervene and control fire spread.
However there are occasions where the common
escape routes
serving
flats
and
maisonettes
may be compromised by fire and smoke. For example,
where a fire has accidentally or deliberately been set in the
protected zone
or
Where a
domestic building
and a non-
domestic building
share a
protected
zone
(see clause 2.9.17), the occupants in the
domestic building
should be
provided with additional protection. A
protected lobby
is necessary
between an
escape stair
and every:
•
flat
;
•
maisonette
; and
•
ancillary
room
or space.
Occupants who are confronted by fire and smoke in the common space may
retreat back into their
flat
or
maisonette
and contact the emergency services.
Control room personnel will provide helpful advice and attempt to keep
callers calm whilst awaiting arrival of the fire and rescue service.
Occupants should be able to remain safely inside the
building
until the fire
has burnt itself out or until the fire has been contained and it is safe to use
the
escape route
. In most cases, the fire and rescue service will intervene
and commence fire-fighting and rescue operations before all occupants have
made their escape to a
place of safety
(see standard 2.14).
Although a rare event, if the spread of fire and smoke is significant, it may be
necessary to evacuate the entire
building
as a precaution. This will normally
be co-ordinated by the fire and rescue service with assistance from the other
emergency services such as the police and ambulance services.
2.9.24
—
2.9.24


Berkeley DB: DbLog.stat
DbLog.stat
import com.sleepycat.db.*;
public DbLogStat stat()
throws DbException;
Description
The DbLog.stat function creates a statistical structure
and returns it to the caller. The log region statistics are
stored in a DbLogStat object. The following DbLogStat data
fields will be filled in:
- public int st_magic;
- The magic number that identifies a file as a log file.
- public int st_version;
- The version of the log file type.
- public int st_refcnt;
- The number of references to the region.
- public int st_regsize;
- The size of the region.
- public int st_mode;
- The mode of any created log files.
- public int st_lg_max;
- The maximum size of any individual file comprising the log.
- public int st_w_mbytes;
- The number of megabytes written to this log.
- public int st_w_bytes;
- The number of bytes over and above st_w_mbytes written to this log.
- public int st_wc_mbytes;
- The number of megabytes written to this log since the last checkpoint.
- public int st_wc_bytes;
- The number of bytes over and above st_wc_mbytes written to this log
since the last checkpoint.
- public int st_wcount;
- The number of times the log has been written to disk.
- public int st_scount;
- The number of times the log has been flushed to disk.
- public int st_cur_file;
- The current log file number.
- public int st_cur_offset;
- The byte offset in the current log file.
- public int st_region_wait;
- The number of times that a thread of control was forced to wait before
obtaining the region lock.
- public int st_region_nowait;
- The number of times that a thread of control was able to obtain
the region lock without waiting.
The DbLog.stat
method throws an exception that encapsulates an errno on failure.
Errors
If a fatal error occurs in Berkeley DB, the DbLog.stat method may fail and throw a
DbRunRecoveryException, at which point all subsequent database
calls will also fail in the same way.
The DbLog.stat
method may fail and throw an exception
for any of the errors specified for the following Berkeley DB and C library
functions:
abort(3),
fcntl(3),
fprintf(3),
getpid(3),
malloc(3),
and
memset(3).
Class
DbLog
See Also
DbLog.archive,
DbLog.close,
DbLog.compare,
DbLog.file,
DbLog.flush,
DbLog.get,
DbLog.open,
DbLog.put,
DbLog.db_register,
DbLog.stat,
DbLog.unlink
and
DbLog.db_unregister.


VISIONS OF LIGHT: THE ART OF CINEMATOGRAPHY A film review by James Berardinelli Copyright 1993 James Berardinelli
Rating: 8.6 (A-, ***)
Date Released: varies (limited release) Running Length: 1:31 Rated: NR (Nothing offensive)
Directors: Arnold Glassman, Todd McCarthy, and Stuart Samuels Producer: Stuart Samuels Written by Todd McCarthy Released by Kino International
Often, one of the most overlooked elements of a film is its cinematography. Paradoxically, it is also the most important, whether specifically noticed or not. Movies are a visual medium where the pictures shoulder the lion's share of the burden. A movie can have a good director, accomplished actors, and a riveting script, but if the photography is done poorly, the production is doomed.
VISIONS OF LIGHT is a fascinating film that will enthrall lovers of movies and photography buffs alike. For those that happen to fall into both categories, it's a rare and wondrous treat. VISIONS OF LIGHT gives an insider's view to the job of the cinematographer, interviewing dozens of today's most accomplished directors of photography, examining their work, and looking back on the great productions of the past.
I defy anyone who sees this movie to emerge with an unchanged attitude towards the movies and the role of the cinematographer. Likely the next film you see after this one, you'll be far more aware of the role of the camera in the process of creation. As a side benefit, those that go into VISIONS OF LIGHT unclear about why colorizing old films is such a taboo subject among movie-lovers, will come to understand the reasons.
VISIONS OF LIGHT states that cinematography is the art of light - blending it so it enhances the director's vision of the film. Much time is spent discussing this subject as well as various other technical aspects of the craft (the role of close-ups, the importance of showing a performer from a certain angle, and the advantages and disadvantages of certain shots). If all this sounds dry, be assured that it isn't. There are clips from over a hundred movies to revel in--everything from CABINET OF DR. CALIGARI to GOODFELLAS.
The film is roughly divided into three sections. The first, and shortest, traces the early days of Hollywood and the importance of camerawork in silent films. Several of the interview subjects lament the introduction of sound into the movies so early, feeling that another decade of silence could have advanced their craft by leaps and bounds.
The second section deals with the black-and-white era after the introduction of sound. Covering roughly the years between 1930 and 1960, much attention is paid to the role of contrast and shadow (gray versus black, for example) in these movies. CITIZEN KANE is given a lengthy treatment with its many photographic innovations discussed at some length.
Finally, color movies are presented. From GONE WITH THE WIND to films of the 1980s, the various techniques used by color photographers to achieve moods and portray emotions are detailed. During this part, time is spent on movies such as ANNIE HALL, JAWS, BLUE VELVET, and the aforementioned GOODFELLAS, which features a discourse on the genesis of one of that film's most unusual shots.
VISIONS OF LIGHT is somewhat didactic and doesn't attempt any ground breaking documentary techniques. But its mixture of information and film clips keeps the pace reasonable. This film will add a dimension to the knowledge of those familiar with the work of cinematographers, and give an appreciation of a different facet of filmmaking to those who are not.
- James Berardinelli<EMAIL_ADDRESS>.
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


'It’s the most poignant record we’ve ever made' - The Script add Cork gig to European tour
by By Digital Desk staffIrish band The Script have announced that they will come to Cork next year as part of their European tour to promote their Sunsets and Full Moons album.
The trio are playing at Musgrave Park on June 23 with tickets going on sale next Friday (November 8).
“I think it’s the most poignant record we’ve ever made,” said lead singer Danny O’Donoghue.
“Our music was always about being together with the audience, and writing about your own feelings, and sharing them.”
Guitarist Mark Sheehan added that the album is the band doing what they do best.
“No frills, no production, just us playing as a band,” he said.
Before playing in Cork in the summer, The Script play in Belfast in March before three shows at Dublin's 3Arena on March 5, 6, and 7.
English singer-songwriter Becky Hill will be the special guest at Musgrave Park.
READ MORE
'I'm going to make them so special': Dermot Kennedy announces Dublin and Cork gigs


{% extends "layout.html" %} {% block title %}Home{% endblock %} {% block content %}
Book tickets now
Register today to book tickets


Culture Shock
No...seriously, this culture is somethin' else.
** Sterotyping - The Threat you didn't know. ** Sunday, June 7th, 2015


Assembling an Executive Leadership Team is Daunting — Let Thumbtack’s CEO Help - by FirstRound Capital. Takeaway: Constrain the job description, split your interview process to separate skill assessment from fit, backchannel to assess skill, and present results of references and swap 360s.
Being Glue - by Tanya Reilly. Takeaway: “Every senior person in an organisation should be aware of the less glamorous - and often less-promotable - work that needs to happen to make a team successful. Managed deliberately, glue work demonstrates and builds strong technical leadership skills. Left unconscious, it can be career limiting. It can push people into less technical roles and even out of the industry.”
Building a Delivery Team - by Bill DeRusha. Takeaway: How the edX internationalization team spun up quickly—team charter, communication, building a relationship with the product manager, being clear and focused about the project scope, and communicating. Includes links to articles about creating team charters.
Building a First Team Mindset - by Jason Wong. Takeaway: “A First Team mindset is the idea that leaders prioritize supporting their fellow leaders over supporting their direct reports—that they are responsible to their peers more than they are to their individual teams.”
Building and Scaling a Distributed and Inclusive Team (video) - by Mathias Meyer. The founder/CEO of Travis CI talks about how the company has been trying to create a multicultural distributed team, with lots of quotes from team members. Travis pushed for a remote culture to increase diversity.
Building Great Engineering Teams, with Gergely Orosz - by Paulo André. Takeaway: An interview with the author of The Pragmatic Engineer, with lots of personal anecdotes highlighting facets of leadership.
Building Great Teams: Culture and Core Protocols (video) - by Richard Kasperowski. Takeaway: Thoughts on psychological safety and creating authentic trust and connection between people to take the “luck” out of building and working on great teams, and making greatness more intentional.
Creating the Dream Team: Transform Your Engineering Organization to Attract New Talent - by Andrew Hao. Takeaway: Start with evaluating your current culture’s strengths and weaknesses. Be in tune with your org. Make sure you demonstrate that you value employees—whether that is talking up their accomplishments, investing in training, or just being there to talk.
DevOps Tech: Empowering Teams to Choose Tools - by the DORA State of DevOps research program. Takeaway: “[W]hen you combine tool choice with other capabilities—for example, a full view of the system, fast feedback, and the understanding that they are responsible for the code that they write—it helps your technologists make wise decisions about tools they will use and need to support.”
Fear of Process or How to Scale the Team Without Getting “Corporate” - by Avi Revivo. Takeaway: “Finding the sweet spot in the organization where you utilize exactly the right amount of processes is practically impossible. Sometimes you’ll use a process that provides less value than what it cost and sometimes the opposite. It means that you need to remember the 3 questions - Can we achieve the same goal without a process? or with an even simpler one? Is the process ROI positive? What is the chance of a successful adoption of the process and why?…and consider them for each new process but you’ll also need to ask the first 2 questions on exciting processes every now and then to make sure it stands the test of time.”
The Five Dysfunctions of a Team: a Leadership Fable - by Patrick Lencioni. Takeaway: lack of trust and commitment, fear of conflict, avoidance of accountability, and inattention to results will prevent your team from gelling and performing. This book uses a narrative/fictional case study to make its point about overcoming the five dysfunctions.
Fostering Better Collaboration Within Product Teams: An Interview with John Cutler - by Dottie Schrock. Takeaway: “[P]roduct teams must figure out how to regain control over the flywheel of making and keeping promises. It’s easy to talk philosophically about trust and culture, but it is your day-to-day actions that actually build goodwill.”
Great Development Teams Have a Culture of Discipline - by Erran Berger. Takeaway: Value craftsmanship as highly as you value execution; attack each problem you face with a tremendous sense of urgency; instrument everything - you can’t fix what you don’t measure; fewer things done better - the disciplined pursuit of less; be rigorous in prioritization and planning; establish a high hiring bar – you’re creating an enduring culture.
Growing a Feature Team Using Lanes - by Vivian Pennel. Takeaway: using a “fast lane” for handling “small requests, features or bugs that need to be executed quickly” and protecting “the strategic lane,” the high-value work. Also use a tech lane for paying back debt, updating libraries and components.
How a Microsoft Docs Team Increased Openness and Improved Collaboration - by Angela Robertson. Takeaway: An honest account of transforming the technical content team of Microsoft’s Cloud and Enterprise group from closed and uncollaborative to open and transparent. Finding purpose in openness was key.
How to Get Engineering Teams to Eat Their Vegetables - by Duretti Hirpa. Takeaway: Good teams are supportive, have a sense of togetherness and don’t blame their team members for their mistakes but instead learn from them.
How to Improve Team Closeness with Personal Maps - by Jürgen Appelo at M3.0. Takeaway: Personal maps and group exercises to develop them can enable members of teams to get to know each other as humans with interests and hobbies. The article points to tips and case stories for you to get ideas.
How to Run a Successful Team Retreat - by Claire Lew. Takeaway: Define success, share context, create alignment, and build trust. Includes a template for you to use in designing your own retreat.
Incentivize Teams, not People - by Randall Koutnik. Takeaway: “Any programmer worth their salt is willing to help team members out when they’re in a pinch. Software development is a team sport, after all. Unfortunately, management can often completely miss the point and create perverse incentives that wreck a team’s cooperation and communication.”
Managing through the WHY, WHAT and HOW - by Lawrence Ripsher. Takeaway: “To effectively manage less experienced team members, provide a clear explanation of HOW to implement/approach something. For mid-career/experience individuals, provide a clear explanation WHAT needs to be built/implemented. For the most skilled / experienced, you need only explain WHY a solution is important.”
The New Work Order: Team Ingredients and Role Blending - by Heather Fleming. Takeaway: Use “team ingredients” to build teams that achieve maximum productivity and happiness.
The Operating System Canvas - by Aaron Dignan. Takeaway: This framework (available as a PDF) presents a canvas for building your organization, with 12 concepts: purpose, authority, structure, strategy, resources, innovation, workflow, meetings, information, membership, mastery and compensation.
Reorgs Happen - by Camille Fournier. Takeaway: “Reorgs are unlikely to solve all of your problems overnight. They are not a magic bullet exercise that fixes cultural issues or a lack of business strategy. If you aren’t careful, your reorg will feel like rearranging deck chairs on the Titanic, a pointless waste of time for everyone involved. So don’t be afraid to do them as necessary, but be realistic. This is a major disruption that impacts everyone, don’t just do it for fun.”
Re-structuring a Growing Team - by Jean Hsu. Takeaway: Identify why you’re reorganizing, understand what it means, and execute. Includes a plan for conducting a team reorg so you can prepare for your own.
Scaling Your Software Becomes Increasingly Easier, but What About Scaling Your Team? - by Oren Ellenbogen. Takeaway: The five traits of a scalable team are 1. and aligned vision, 2. aligned, core values, 3. core values over individuals, 4. self-balance, and 5. having a sense of accomplishment.
Software Teams: Autonomous or Tightly-Aligned? - by Ian Cackett and Sasha Bilton. Takeaway: “In the longer-term, there can be a lost opportunity for synergy between autonomous squads; opportunities to introduce common structure or shared solutions. Having many solutions to the same problem spells wasted effort, less focus on the quality of each implementation and an increased likelihood of bugs creeping in.”
What Google Learned About Creating Effective Teams - by Matt Sakaguchi. Takeaway: Sakaguchi talks about some of the practical research Google has done around building effective teams. He addresses not only the research, but the insights of a manager who worked with his own team and others, to instill the findings and principles in the real world, along with key insights from Google’s pilot program.
What Google Learned From Its Quest to Build the Perfect Team - by Charles Duhhig. Takeway: The best teams are supportive and team members are sensitive to each others’ feelings and needs.


Index
Rotation 4: Laser Cutting and Engraving and Vinyl Cutting
Project Description:
For the first project, I designed a cardboard box using both raster and vector using the MakerCase software. I choose the globe, pineapple, slice of pizza, my name in a very cool font, a camel, and a palm tree to put on the card board pieces. I used CorelDraw software for this project. The laser printed the designs lightly, but I ended up liking how it turned out.
Project Description:
For the second project, I made three different shapes using CorelDraw to make a press fit. All shapes need to be able to fit together like a puzzle piece which I found not challenging to do. I selected a rectangle, circle, and pentagon for my three shapes. I hairlined all of the shapes so the laser machine can print them out. In the end, I liked how it turned out!
Project Description:
For my third project I decided to do the coaster project. I used the CorelDraw software once again to make this project possible. I decided to put a design of palm tree silhouettes along with several camels. Underneath, I put my name on it with a cool font. After printing the design on the coaster, the design happened to not be in the center or as big as I thought it was going to be, but I'm still happpy with the result.
Project Description:
For my last project I choosed to etch a design on an aluminum bookmark. I sketched a relatively simple design that involved my name and the year I'm graduating Reserve on to the bookmark. I really liked the way my name was engraved on the bookmark, however, I could of centered it to fit the bookmark.
Files:


#include <SBModuleSpec.h>
Detailed Description
Definition at line 18 of file SBModuleSpec.h.
Constructor & Destructor Documentation
| lldb::SBModuleSpec::SBModuleSpec |
( |
| ) |
|
| lldb::SBModuleSpec::SBModuleSpec |
( |
const SBModuleSpec & |
rhs | ) |
|
| lldb::SBModuleSpec::~SBModuleSpec |
( |
| ) |
|
Member Function Documentation
| void lldb::SBModuleSpec::Clear |
( |
| ) |
|
| bool lldb::SBModuleSpec::GetDescription |
( |
lldb::SBStream & |
description | ) |
|
Get const accessor for the module file.
This function returns the file for the module on the host system that is running LLDB. This can differ from the path on the platform since we might be doing remote debugging.
- Returns
- A const reference to the file specification object.
| const char* lldb::SBModuleSpec::GetObjectName |
( |
| ) |
|
Get accessor for the module platform file.
Platform file refers to the path of the module as it is known on the remote system on which it is being debugged. For local debugging this is always the same as Module::GetFileSpec(). But remote debugging might mention a file '/usr/lib/liba.dylib' which might be locally downloaded and cached. In this case the platform file could be something like: '/tmp/lldb/platform-cache/remote.host.computer/usr/lib/liba.dylib' The file could also be cached in a local developer kit directory.
- Returns
- A const reference to the file specification object.
| const char* lldb::SBModuleSpec::GetTriple |
( |
| ) |
|
| const uint8_t* lldb::SBModuleSpec::GetUUIDBytes |
( |
| ) |
|
| size_t lldb::SBModuleSpec::GetUUIDLength |
( |
| ) |
|
| bool lldb::SBModuleSpec::IsValid |
( |
| ) |
const |
| void lldb::SBModuleSpec::SetObjectName |
( |
const char * |
name | ) |
|
| void lldb::SBModuleSpec::SetTriple |
( |
const char * |
triple | ) |
|
| bool lldb::SBModuleSpec::SetUUIDBytes |
( |
const uint8_t * |
uuid, |
|
|
size_t |
uuid_len |
|
) |
| |
Friends And Related Function Documentation
The documentation for this class was generated from the following file:


Conway’s Game of Life is a dramatic illustration of emmergent behavior; that a seemingly complex system, such as cell mitosis can be governed by a set of simple rules. OpenMP is a fantastic set of language extensions which allows one to add dramatic parallelism without complex thread management. As a demonstration of OpenMP’s simplicity I implemented the Game of Life. The code and all analysis is available on bitbucket.org.
In a real program, it common to have swathes of code which cannot be made parallel. OpenMP’s limited perspective on data limits one further. As such, OpenMP is most effective when the data is decomposed into independently manageable chunks. To evaluate the performance affect of OpenMP on my implementation I used a single Base Class to implement the serial portion of the code. Each child class makes small modifications to the generation calculation, decomposing the data in different ways. I made three decompositions:
-
Decomposition by Rows
-
Decomposition by Columns
-
Random Decomposition by Cell
Interestingly, the relative performance of each mechanism was quite volatile. The serial version of the code is quite simple. Basically, calculate each live/die action for every cell then, after all calculations are made, commit the updates in one atomic action.
void GameGrid::CalculateGeneration()
{
list delayedUpdates;
for(size_t col = 0; col < GetGridSize(); ++col)
{
for(size_t row = 0; row < GetGridSize(); ++row)
{
uint32_t livingNeighbors = CountLivingNeighbors(col, row);
#ifdef DEBUG
cout << "Row: " << row
<< "Col: " << col
<< ": " << livingNeighbors << endl;
#endif
Update u;
u.threadId = omp_get_thread_num();
u.position = &(Grid[col][row]);
u.threadPosition = &(GridThreads[col][row]);
if(Grid[col][row]) //If Cell is alive
{
if(livingNeighbors = 4)
{
//Kill Cell
u.updateValue = false;
delayedUpdates.push_back(u);
}
/* else remain alive */
}
else
{
if(livingNeighbors == 3)
{
//ConceiveCell
u.updateValue = true;
delayedUpdates.push_back(u);
}
}
}
}
commitUpdates(delayedUpdates);
}
Even this simple routine can generate incredible emergent behavior.
Your browser does not support the video tag.
Now, we have a serial platform to extend into a parallel one. First we extend the base class with simple inheritance.
class GameGridParallelCol : public GameGrid
{
public:
typedef std::tr1::shared_ptr Ptr; ///@note The Anderson Smart Pointer Idiom
typedef std::tr1::weak_ptr WeakPtr;
static GameGridParallelCol::Ptr construct(string filename, size_t size);
virtual ~GameGridParallelCol();
virtual void CalculateGeneration();
protected:
private:
GameGridParallelCol(string filename, size_t size);
GameGridParallelCol::WeakPtr self;
};
The using OpenMP Directives add col decomposition:
void GameGridParallelCol::CalculateGeneration()
{
vector delayedUpdates[omp_get_max_threads()]; //Create duplicate update lists, to avoid critical sections.
for(size_t row = 0; row < GetGridSize(); ++row)
{
#pragma omp parallel for
for(size_t col = 0; col < GetGridSize(); ++col)
{
uint32_t livingNeighbors = CountLivingNeighbors(col, row);
Here is the power of OpenMP, its simplicity. OpenMP exposes a set of #pragma functions which apply parallelism to the beginning of a scope block, and a barrier at the end of the scope block. Automatic parallelism, it doesn’t get easier than this. However OpenMP’s simplicity does hamper it in a few ways. OpenMP directives for instance, cannot batch C++ iterators. Now we have a thread pool which will run segments of the game of life in parallel.
[caption id="attachment_420” align="aligncenter” width="792” caption="Column Order Decomposition”][/caption]
The right half of the image illustrates each thread, one for each color, as it updates a section of the game grid. (Decomposition into rows is left as an exercise). Extending this we can make a fully parallel version.
#pragma omp parallel for collapse(2) schedule(dynamic)
for(size_t row = 0; row < GetGridSize(); ++row)
{
for(size_t col = 0; col < GetGridSize(); ++col)
{
uint32_t livingNeighbors = CountLivingNeighbors(col, row);
Rendering the following:
[caption id="attachment_422” align="aligncenter” width="792” caption="Full data decomposition with dynamic thread balancing”][/caption]
Now we have a fully parallel version where threads calculate cells at random, as the thread is available. Strangely, this isn’t always the fastest algorithm.
Analysis
No single decomposition wins out. As such there is no generalization such that one threading mechanism is faster than another in all cases. The Full threading model was mst consistant, but the Row and Column decompositions actually got slower as more cores were added.
[caption id="attachment_423” align="aligncenter” width="695” caption="6-core Speedup”][/caption]
[caption id="attachment_424” align="aligncenter” width="695” caption="12-core Speedup”][/caption]
Most interestingly, the row and column performance goes down with more cores, while the full decomposition stays pretty constant. I do not have a reason why this is happening.
Conclusion
OpenMP makes adding parallelism to a serial program easy. The constructs allow one to sprinkle parallel code throughout the program, and the measure the performance boost. Sometimes it may be prudent to dive in deeper and manually thread some section of code, especially when using complex C++ constructs such as iterators, but if OpenMP meets the need, then its a low-cost, cross-platform mechanism. Furthermore, OpenMP is exposed as a set of #pragma functions. Since #pragmas are by definition an extension to the language, if the compiler doesn’t understand the directives, they are simply ignored. This allows one to liberally use OpenMP, and if the compiler of choice doesn’t support the OpenMP directives, OpenMP will not break the build. OpenMP is a fantastic tool.


flixel.FlxG
- type
- class
- metadata
- :allow
- '???'
Global helper class for audio, input, the camera system, the debugger and other global properties.
Static Methods
- metadata
- :noCompletion
- :noUsing
- parameters
ObjectOrGroup1
The first object or group you want to check.
ObjectOrGroup2
The second object or group you want to check. If it is the same as the first, flixel knows to just do a comparison within that group.
NotifyCallback
A function with two FlxObject parameters - e.g. myOverlapFunction(Object1:FlxObject,Object2:FlxObject) - that is called if those two objects overlap.
- returns
- Whether any objects were successfully collided/separated.
- parameters
URL
The address of the web page.
Target
"_blank", "_self", "_parent" or "_top"
- parameters
ObjectOrGroup1
The first object or group you want to check.
ObjectOrGroup2
The second object or group you want to check. If it is the same as the first, flixel knows to just do a comparison within that group.
NotifyCallback
A function with two FlxObject parameters - e.g. myOverlapFunction(Object1:FlxObject,Object2:FlxObject) - that is called if those two objects overlap.
ProcessCallback
A function with two FlxObject parameters - e.g. myOverlapFunction(Object1:FlxObject,Object2:FlxObject) - that is called if those two objects overlap. If a ProcessCallback is provided, then NotifyCallback will only be called if ProcessCallback returns true for those objects!
- returns
- Whether any overlaps were detected.
- parameters
Sprite1
The first FlxSprite to test against
Sprite2
The second FlxSprite to test again, sprite order is irrelevant
AlphaTolerance
The tolerance value above which alpha pixels are included. Default to 255 (must be fully opaque for collision).
Camera
If the collision is taking place in a camera other than FlxG.camera (the default/current) then pass it here
- returns
- Whether the sprites collide
- parameters
Object
An FlxBasic object that will be destroyed if it's not null.
- returns
- Null


LLC_Membranes
0.1
Software Requirements
Preparation of Monomers and Solutes
System Setup
Post-Simulation Trajectory Analysis
LLC_Membranes
Docs
»
Index
Index
_
|
A
|
B
|
C
|
D
|
E
|
F
|
G
|
H
|
I
|
M
|
P
|
Q
|
R
|
S
|
T
|
W
|
X
|
Z
_
__init__() (bcc_build.BicontinuousCubicBuild method)
(correlation_function.Correlation method)
(genmdp.SimulationMdp method)
(gentop.SystemTopology method)
(hbonds.System method)
(hexagonal_build.BuildHexagonal method)
(rdf.System method)
(solvation_equilibration.System method)
(xlink.System method)
(xlink_schemes.DieneScheme method)
(xlink_schemes.XlinkReaction method)
A
add_pull_groups() (genmdp.SimulationMdp method)
add_residue() (gentop.SystemTopology method)
align_plane() (hexagonal_build.BuildHexagonal method)
align_with_x() (hexagonal_build.BuildHexagonal method)
avg_pore_loc() (in module p2p)
B
BicontinuousCubicBuild (class in bcc_build)
bootstrap() (rdf.System method)
build_column() (hexagonal_build.BuildHexagonal method)
build_com() (rdf.System method)
build_spline() (rdf.System method)
BuildHexagonal (class in hexagonal_build)
C
calculate_pore_water() (solvation_equilibration.System method)
Correlation (class in correlation_function)
D
determine_monomer_placement() (bcc_build.BicontinuousCubicBuild method)
determine_reaction_type() (xlink_schemes.DieneScheme method)
Dibrpyr14 (class in xlink_schemes)
DieneScheme (class in xlink_schemes)
E
equilibrate() (solvation_equilibration.System method)
F
full_equilibration() (solvation_equilibration.System method)
G
gen_grid() (bcc_build.BicontinuousCubicBuild method)
grps() (in module rdf)
H
head2tail() (xlink_schemes.DieneScheme method)
hexagonal_build (module)
I
identify_hbonds() (hbonds.System method)
M
make_slice() (correlation_function.Correlation method)
P
p2p (module)
p2p() (in module p2p)
p2p_stats() (in module p2p)
place_monomers() (bcc_build.BicontinuousCubicBuild method)
place_water_tails() (solvation_equilibration.System method)
plot() (rdf.System method)
plot_hbonds() (hbonds.System method)
plot_slice() (correlation_function.Correlation method)
Q
query_database() (solvation_equilibration.System method)
R
radial_distribution_function() (rdf.System method)
radical_c2() (xlink_schemes.DieneScheme method)
rdf (module)
remove_residue() (gentop.SystemTopology method)
reorder() (bcc_build.BicontinuousCubicBuild method)
(hexagonal_build.BuildHexagonal method)
restrict_atoms() (in module p2p)
S
set_eligible() (hbonds.System method)
SimulationMdp (class in genmdp)
System (class in hbonds)
(class in rdf)
(class in solvation_equilibration)
(class in xlink)
SystemTopology (class in gentop)
T
terminate() (xlink_schemes.DieneScheme method)
Topology (class in xlink)
translate_to_origin() (hexagonal_build.BuildHexagonal method)
W
write_em_mdp() (genmdp.SimulationMdp method)
write_final_pore_configuration() (solvation_equilibration.System method)
write_gro() (hexagonal_build.BuildHexagonal method)
write_npt_mdp() (genmdp.SimulationMdp method)
write_nve_mdp() (genmdp.SimulationMdp method)
write_nvt_mdp() (genmdp.SimulationMdp method)
write_top() (gentop.SystemTopology method)
X
XlinkReaction (class in xlink_schemes)
Z
z_correlation() (in module hexagonal_build)


New York's Attorney General has obtained a court order against crypto exchange Bitfinex's operator iFinex as well as stablecoin company Tether.
 Why does New York thoughts on bitfinex matter when Americans are not even allowed to trade on the exchange except through VPN? The thing with tether is their own problem.
ComputerGenie 👴👴👴26-Apr-19 12:01 AM
“OAG has reason to believe that Bitfinex still allows New York-based individual investors to deposit, trade, and withdraw virtual currencies. and engage in other transactions. on the Bitfinex trading platform.”
And we're surprised that a company in China doesn't hold themselves accountable to some random state law in the US, right?(edited)
Kitchen Table26-Apr-19 12:03 AM
Also look at the fact a whole lot of longs were closing hours before this news hit and it looks to be whales playing games.


- Prep: 15 minutes
- Cooking time: 25-27 minutes
- Yield: One 8-inch cake
- Serves: 8 - 12
Recipe courtesy of King Arthur Flour
Ingredients
Cake:
- 1 cup semisweet chocolate chips
- 1/2 cup (8 Tbl.) unsalted butter
- 3/4 cup granulated sugar
- 1/4 tsp. salt
- 1 - 2 tsp. instant espresso (such as Starbucks Via Italian Roast)*
- 1 tsp. Vanilla extract
- 3 large eggs
- 1/2 cup unsweetened Dutch-process cocoa powder
Ganache Glaze:
- 1 cup semisweet chocolate chips
- 1/2 cup heavy whipping cream
Vanilla Mascarpone Whipped Cream (optional):
- 1 cup heavy whipping cream
- 4 oz. Mascarpone
- 1 tsp. Vanilla extract
- Granulated sugar to taste (1 Tbl. or more)
Berry Sauce (optional):
- 1/2 or all of a 16 oz. package of frozen mixed berries
- Granulated sugar to taste (1/2 cup or more)
- 1 cup of water
Method
Cake:- Preheat oven to 375F. Lightly grease an 8-inch round cake pan; cut a piece of parchment to fit, lay it in the bottom of the pan, and grease it.
- Melt chocolate chips and butter in a double-boiler over medium-low heat, then transfer to a mixing bowl.
- Stir in the sugar, salt, instant espresso, and vanilla.
- Add the eggs, beating briefly until smooth. Add the cocoa powder, and mix just to combine.**
- Spoon the batter into the prepared pan.
- Bake the cake for 25 minutes; the top will have formed a thin crust, and it should reach an internal temperature of 200F.
- Remove cake from oven and set on a wire rack (in pan) to cool for 5 minutes.
- Loosen the edges of the cake from the pan and turn it out onto a serving plate. Allow to cool completely before glazing.
- To make the glaze, warm the cream in the double-boiler until hot but not simmering.
- Add the chocolate and stir until melted and combined smoothly with the cream.
- Pour the glaze over the cake starting at the center and then circling outward, until it drips down the sides slightly.
- Allow glaze to cool and set for several hours before serving. May be refrigerated for up to a week, covered, once glaze is cool.
Vanilla Mascarpone Whipped Cream:
- Chill mixing bowl and beaters in freezer until frosty.
- Combine heavy cream, Mascarpone, vanilla, and sugar in chilled bown and beat with stand mixer on medium until soft peaks form.
- Test for sweetness and add more sugar if desired. Continue beating on medium-high until stiff peaks form.
- Refrigerate until ready to use. Top individual slices of cake with a substantial spoonful or two, and drizzle with berry sauce.
- Bring berries, water, and sugar to a simmer in a medium pot over medium heat.
- Simmer until berries have lost their shape and liquid has reduced to a thick syrup. Test periodically for level of sweetness, and add more sugar if desired.
- Citrus zest and/or spices can also be added to taste.
- Cool sauce in the refrigerator, unless serving immediately. Drizzle over cake and whipped cream topping.


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object kdl.prox.model2.rpt.modules.pruning.CostComplexityPruning
public class CostComplexityPruning
CostComplexityPruning implements the pruning algorithm described in the monograph Classification and Regression Trees by Breiman, Friedman, Olshen and Stone.
| Nested Class Summary | |
|---|---|
class |
CostComplexityPruning.CostComplexityWalker
|
| Field Summary | |
|---|---|
TreeSelectionModule |
selectionModule
|
| Constructor Summary | |
|---|---|
CostComplexityPruning(Container testContainer)
This is the constructor to use testSample tree selection. |
|
CostComplexityPruning(RPT parentRPT,
int numFolds)
This is the constructor to use cross validation tree selection Assumes the cross-validation folds are in respective train and test containers nested within the main container e.g., mainContainer - train - fold 0 - fold 1 ... |
| Method Summary | |
|---|---|
PruningRPTNode |
findAndRemoveWeakestLink(PruningRPTNode currTree)
Follow the weakest link algorithm described in BOFS section 3.3 All nodes with tie scores are pruned from the tree. |
java.util.List<PruningRPTNode> |
getPruningSequence(RPTNode root)
This methods returns a sequence of trees in the order of smallest alpha to largest. |
PruningRPTNode |
getT1(RPTNode root,
double totalInstanceCount)
T1 is the smallest minimizing subtree of the learned tree (Proposition 3.7, pg 68) This becomes the starting point for pruning. |
RPTNode |
prune(RPTNode root,
RPTState state)
|
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Field Detail |
|---|
public TreeSelectionModule selectionModule
| Constructor Detail |
|---|
public CostComplexityPruning(Container testContainer)
testContainer
- public CostComplexityPruning(RPT parentRPT, int numFolds)
parentRPT
- numFolds
- | Method Detail |
|---|
public RPTNode prune(RPTNode root, RPTState state)
prune
in interface RPTPruningModule
public java.util.List<PruningRPTNode> getPruningSequence(RPTNode root)
root
-
public PruningRPTNode getT1(RPTNode root, double totalInstanceCount)
root
- totalInstanceCount
-
public PruningRPTNode findAndRemoveWeakestLink(PruningRPTNode currTree)
currTree
-
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Team
Team members
Attributions
Collaboration
Project
Description
Design
Results
Demonstrate
Lab
Experiments
Notebook
Interlab
Parts
Parts Overview
Basic Parts
Human Practices
Human Practices
Integrated Human Practices
Education & Engagement
Attributions
Attributions
Sponsors
Judging Form
Medal Criteria
Safety


Endless Plains [ah70], plain, in Imperia, peasants: 100
Last updated Turn #97
Endless Plains [ah70], plain, in Imperia, peasants: 100
------------------------------------------------------------------------
18: Stefano [t8e], Imperial Empire, the High Priest of the Church of
18: Halon [157], with ten angels, 31 nazgul, arrived from the south,
18: accompanied by:
18: Lord Rodrigo Bane [c8b], Imperial Empire, Bishop of the Church of
18: Dol [153], with five angels, 40 hvy. xbowmen, five nazgul
19: Stefano [t8e], Imperial Empire, the High Priest of the Church of
19: Halon [157], with ten angels, 31 nazgul, went north, accompanied by:
19: Lord Rodrigo Bane [c8b], Imperial Empire, Bishop of the Church of
19: Dol [153], with five angels, 40 hvy. xbowmen, five nazgul
19: Stack of nazgul [ee1u], nazgul, number: 3, arrived from the south.
20: Stack of giant lizards [cs2n], giant lizards, number: 5, arrived from
20: the east.
21: Stack of nazgul [ee1u] attacks Stefano [t8e]!
21:
21: Stack of nazgul [ee1u], nazgul, number: 3
21:
21: Stefano [t8e], Imperial Empire, the High Priest of the Church of
21: Halon [157], with ten angels, 32 nazgul, accompanied by:
21: Lord Rodrigo Bane [c8b], Imperial Empire, Bishop of the Church
21: of Dol [153], behind 3, with five angels, 40 hvy. xbowmen,
21: five nazgul
21:
21: Initial missile round for the defense (Stefano [t8e]):
21: Nine missiles hit!
21: Stack of nazgul [ee1u] loses two nazgul [55].
21:
21: Combat round: one
21: Missile phase:
21: Stefano's forces hit with six missiles.
21: Stack of nazgul [ee1u] suffers a hit!
21:
21: Stefano [t8e] is victorious!
21:
21: Stack of nazgul lost two nazgul.
21: Stack of nazgul [ee1u] was killed.
21:
22: Stack of giant lizards [hh8p], giant lizards, number: 5, went east.
22: Stack of giant lizards [cs2n], giant lizards, number: 5, went east.
26: Horde of rats [ev9f], rats, number: 25, arrived from the north.
27: Princess Tiffany Miffed [l0p], refugee, arrived from the north.
29: Princess Tiffany Miffed [l0p], refugee, went south.
30: Stack of giant lizards [hh8p], giant lizards, number: 5, arrived from
30: the east.
30: Stack of giant lizards [cs2n], giant lizards, number: 5, arrived from
30: the east.
30: It has become quite foggy.
30: It has stopped raining.
Routes leaving Endless Plains:
North, plain, to Endless Plains [ag70], 7 days
East, forest, to Old Forest [ah71], 8 days
South, plain, to Endless Plains [ai70], 7 days
West, plain, to Endless Plains [ah69], 7 days
The province is blanketed in fog.
No one can be seen through the fog.


Sometimes deep packet inspection will stop simple tunneling (ie noticing HTTP going through an SSH connection). Traffic Encapsulation can help fool/bypass this.
Some tools to look at are:
HTTPTunnel
stunnel
These tools usually work in a client/server model and can encapsulate any protocol within their respective tunnels.