This document describes how to fetch and install Pmw, and how to run the demonstrations and tests.
Pmw.1.3 requires the _tkinter and Tkinter modules. It works with python versions 1.5.2 and greater (tested up to 2.2.1) and Tk versions 8.0 and greater (tested up to 8.3.2).
If the BLT extension to Tk is present, Pmw will use the BLT busy command during modal dialogs to display a clock cursor. Also, the Pmw.Blt interface to the BLT busy, graph, stripchart, tabset and vector commands will be available. BLT versions 2.4i and greater are supported (tested up to 2.4u). You can find BLT at http://www.tcltk.com/blt/.
Releases of the Pmw distribution are available via http from
http://download.sourceforge.net/pmw/
. This release is available
as
Pmw.1.3.tar.gz
, released on 7 August 2007.
This is a compressed tar file.
Under Linux, Unix, etc, you will need to
unpack it using tar
and you may also need to use
gzip
or gunzip
to uncompress it.
Under Microsoft Windows, you will need a program such as WinZip (http://www.winzip.com) that can
unpack the gzipped tar files. You may need to change the suffix of
the file to .tgz for WinZip to recognise it.
This will unpack into a directory named src containing the directory Pmw and the
installation utility setup.py. You now need to put this
directory Pmw somewhere python can find it, preferably in one of the
standard places, such as in the site-packages
directory
(eg: /usr/lib/python2.2/site-packages/Pmw
) or the
sys.prefix
directory (eg: C:\Program
Files\Python\Pmw
or /usr/lib/python2.2
).
One easy way to install the Pmw directory in the site-packages directory of your
installation is to use the setup.py utility.
This is done as follows:
python setup.py install
(as root)
or
sudo python setup.py install
(under Ubuntu or Mac OS X)
Alternatively, to install manually, for example under Unix, assuming you have placed the tar file in the
/tmp
directory, you can simply run the following
commands:
cd /usr/lib/python2.2/site-packages gunzip /tmp/Pmw.1.3.tar.gz (or gzip -d /tmp/Pmw.1.3.tar.gz) tar xvf /tmp/Pmw.1.3.tar
If you do not have write permission for these standard directories,
place the Pmw
directory somewhere on your PYTHONPATH
or
sys.path
. If this is not possible, place the Pmw
directory somewhere else and add the parent directory to your
PYTHONPATH
or sys.path
.
If you have previously installed Pmw version 0.6 or later, then the
new version can share the same Pmw
directory as the
previous versions. You will need to perform the tar
extraction in the directory containing (that is, the parent directory
of) the existing Pmw
directory. By default, your
applications will use the most recent version of Pmw. If required,
the function Pmw.setversion()
can be used to specify a
version to be used. See the reference manual for details. If you are
no longer using the older versions, you can safely remove the
corresponding subdirectories from the Pmw
directory.
If you need assistance in installing BLT under Unix, please contact me<EMAIL_ADDRESS>and I will try to help. For other operating systems, such as Microsoft or Macintosh, you should try asking the python newsgroup. If anyone can give me a description of how to install BLT under other operating systems please contribute it and I will place it here.
The doc
directory for each Pmw version contains all the
documentation for that version of Pmw. See the local home page for a complete list of documents. The
files in this directory are also available from the official Pmw home page.
An excellent tutorial and reference covering the Pmw interface to the powerful Blt graph widget, "A User's Guide to Pmw.Blt" written by Bjørn Ove Thue and Hans Petter Langtangen, is available. You can also download the full HTML document for local viewing.
A good way to get an overview of the functionality provided by Pmw
is to run the demonstrations and tests and look at the demonstration
code. To view a comprehensive demonstration of many of the features
of Pmw run the All.py
script, which can be found in the
demos
subdirectory of each version of Pmw.
You do not have to install Pmw to run the demonstrations and tests,
simply change into the appropriate directory and run the file
All.py
. See Demonstrations and tests for more
information about running the demonstrations and tests and how to
create your own.
Note that there are some bugs in later versions of BLT (at least 2.4t and 2.4u) which cause some tests of Pmw.Blt.Graph to crash with python2.0 under Linux. These tests have been commented out (until BLT is fixed).
If you create some whiz-bang megawidgets and would like to contribute
them to Pmw, they will be most welcome. You should be able to get
some idea of the coding style used in Pmw code by reading How to build Pmw megawidgets and by looking
at the Pmw library code itself in the lib
directory of
each Pmw version.
If you would like to contribute a megawidget, it would be preferable if it also came with a simple demonstration and a test script. See Demonstrations and tests for information about how to create new demonstrations and tests.
Each megawidget should also have a reference manual describing its options, components and methods.
The released reference manuals are
automatically generated by merging specially marked-up text with the
output from megawidget query methods, such as
components()
, options()
and
componentaliases()
, and various other introspective
devices. If you are interested to see how the documentation is generated,
you can fetch the marked-up text and the python script to convert the
text to html from
http://download.sourceforge.net/pmw/Pmw.1.3.docsrc.tar.gz
. Download this
file into the Pmw/Pmw_1_3
directory of the Pmw source
tree. Unzip and untar the file. This will create a
docsrc
sub-directory of Pmw/Pmw_1_3
. If
you want to keep the documentation which came with the Pmw
distribution, rename the old doc
directory. Then change
directory to docsrc
and run createmanuals.py
.
After printing lots of warnings about documentation that has not been
written yet, this will create a new doc
directory
containing all the html documentation.
Here is an example set of commands to unpack the documentation source and regenerate the documentation, assuming you have downloaded the source in the Pmw/Pmw_1_3 directory:
cd Pmw/Pmw_1_3 gunzip Pmw.1.3.docsrc.tar.gz tar xvf Pmw.1.3.docsrc.tar mv doc doc.old cd docsrc ./createmanuals.py
If running under Unix, you will need to run the
createmanuals.py
script with a valid DISPLAY environment
variable, since it creates each megawidget and then queries it for its
options, components, etc. This is because Tk (and hence Tkinter)
requires a connection to an X server to run.
The todo list contains a long list of of suggestions, bugs and enhancements for Pmw. If you are interested in doing any of these, please let the maintainer<EMAIL_ADDRESS>know. Some of the items in the todo list may be considered bugs. There are also some other problems due to idiosyncrasies in the implementation of Tk.
The official Pmw licence (see copyright) basically lets you do anything with Pmw as long as you don't hurt anyone. There is also another licence, the "Postcard Licence":
"I'd like to get a postcard from you! I'm interested in who is using Pmw, where you live and where in the world Pmw is doing it's job"Please send me an e-mail to<EMAIL_ADDRESS>to get my postal address.
The initial ideas for Pmw were blatantly stolen from the itcl extensions [incr Tk] by Michael McLennan and [incr Widgets] by Mark Ulferts. Several of the megawidgets are direct translations from the itcl to python.
The base classes and most megawidgets were written by Greg McFarlane and Peter Munnings. Contributed megawidgets include: Pmw.TimeCounter by Joe VanAndel, Pmw.Group and an early version of Pmw.NoteBook by Case Roole, Pmw.ScrolledCanvas, Pmw.ScrolledFrame and another early version of Pmw.NoteBook by Joe Saltiel and Pmw.OptionMenu by Roman Sulzhyk. A big thank you to the following people for their bug reports, fixes, enhancements and suggestions: David Ascher, Robin Becker, Siggy Brentrup, Mark Colclough, Jerome Gay, Clemens Hintze, Rob Hooft Jack Jansen, Jonathan Kelly, Magnus Kessler, Matthias Klose, Andreas Kostyrka, Fredrik Lundh, Magnus Lycka, Graham Matthews, Dieter Maurer, Michael McLay, Daniel Michelson, Georg Mischler, Rob Pearson, Case Roole, Joe Saltiel, Roman Sulzhyk, Shen Wang, Chris Wright, and Guido van Rossum. Special thanks to Case Roole and Michael McLay for help with getting Pmw to work with python packages and many other nifty features. My deepest apologies if I have forgotten anyone. Please let me know.
The Pmw home page and project site is made available courtesy of SourceForge.
The current maintainer is Greg McFarlane. I monitor the Pmw discussion and announcement mailing list so please send any problems, comments, suggestions or enhancements to the list. You may also contact me directly at<EMAIL_ADDRESS>Pmw 1.3 - 7 Aug 2007 - Home


Watch your favorite movies.
Buy movies at an affordable price with MovieBox
Click to go
bellow.
Go
The Green Mile
Drama, Horror, Mystery
Joker
Thriller, Drama
The Platform
Thriller, Suspense
Dunkirk
Action, History
Silent Hill
Thriller
The film takes place in the near future, with Earth in the grip of The Blight, an airborne disease that causes food crops to turn to grey-brown powder. It rolls and billows across the land, piling up around houses and cars like the dust-drifts in Andrei Tarkovsky’s Stalker, another film in which the characters slip between time’s cogs.
New Releases
Our most recently released movies.
Tenet
Action
The Haunting
Drama, Horror
The Devil All the Time
Thriller, Drama
The Gentlemen
Comedy, Crime
Doctor Sleep
Thriller, Horror
Looking for something else? Search more movies:


Porting a problem from Clawpack 4.6.x to PyClaw¶
The script pyclaw/development/clawdata2pyclaw.py is intended to aid in converting a Clawpack 4.6 problem setup to PyClaw. However, some manual conversion is necessary, especially if the problem includes custom fortran routines.
In PyClaw, the high-level portions of the Fortran routines are reorganized in an object-oriented Python framework, while the low-level ones are bound through the Fortran to Python interface generator f2py. Therefore, for simple problems you won’t need to call f2py directly. However, if you want to reutilize some problem-specific fortran routines that were set up and tested in a Clawpack problem, you can easily do it. Indeed, if those routines are complicated and/or computationally intensive, you should consider directly using the f2py interface in the initialization script (see Setting up your own problem). The example in clawpack/pyclaw/examples/shallow_sphere, which solves the shallow water equations on the surface of a sphere, is a complete example that relies heavily on the use of problem-specific Fortran routines. In that problem setup, a few Fortran routines have been used to provide the following functionality:
- Initialize the solution state.q[:,:,:]
- Provide the mapping from a uniform Cartesian domain to the desired physical domain, i.e. the mapc2p function
- Setup the auxiliary variables state.aux[:,:,:]
- Compute the (non-hyperbolic) contribution of a source term
- Impose custom boundary conditions to both solution and auxiliary variables
The first step to succesfully interface the Fortran functions with PyClaw is to automate the extension module generation of these routines through f2py. You can use clawpack/pyclaw/examples/shallow_sphere/Makefile as a template:
# Problem's source Fortran files
INITIALIZE_SOURCE = mapc2p.f setaux.f qinit.f src2.f
problem.so: $(INITIALIZE_SOURCE)
$(F2PY) -m problem -c $^
The code above, calls f2py to compile a set of Fortran routines and build a module (problem.so) which can then be imported as a function in Python. The argument following the ‘’-m’’ flag is the name the python module should have (i.e. the name of the target). f2py uses the numpy.distutils module from NumPy that supports a number of major Fortran compilers. For more information see http://www.scipy.org/F2py.
After compilation, it is useful to check the signature of each function contained in problem.so, which may be different than that of the original Fortran function, since f2py eliminates dummy variables. One can easily achieve that by using the following commands:
$ ipython
>>> import problem
>>> problem?
The last command queries the content of the module and outputs the functions’ signature that must be used in the initialization script to correctly call the fortran functions. In the shallow water equations on a sphere example, we get the following output:
>>> Type: module
>>> Base Class: <type 'module'>
>>> String Form: <module 'problem' from 'problem.so'>
>>> Namespace: Interactive
>>> File: /Users/../../../clawpack/pyclaw/examples/shallow-sphere/problem.so
>>> Docstring:
This module 'problem' is auto-generated with f2py (version:1).
Functions:
mapc2p(x1,y1,xp,yp,zp,rsphere)
aux = setaux(maxmx,maxmy,num_ghost,mx,my,xlower,ylower,dxc,dyc,aux,rsphere,num_aux=shape(aux,0))
q = qinit(maxmx,maxmy,num_ghost,mx,my,xlower,ylower,dx,dy,q,aux,rsphere,num_eqn=shape(q,0),num_aux=shape(aux,0))
q = src2(maxmx,maxmy,num_ghost,xlower,ylower,dx,dy,q,aux,t,dt,rsphere,num_eqn=shape(q,0),mx=shape(q,1),my=shape(q,2),num_aux=shape(aux,0))
For instance, the function src2, which computes the contribution of the (non-hyperbolic) source term, has the following intent variables:
>>> cf2py integer intent(in) maxmx
>>> cf2py integer intent(in) maxmy
>>> cf2py integer optional, intent(in) num_eqn
>>> cf2py integer intent(in) num_ghost
>>> cf2py integer intent(in) mx
>>> cf2py integer intent(in) my
>>> cf2py double precision intent(in) xlower
>>> cf2py double precision intent(in) ylower
>>> cf2py double precision intent(in) dx
>>> cf2py double precision intent(in) dy
>>> cf2py intent(in,out) q
>>> cf2py integer optional, intent(in) num_aux
>>> cf2py intent(in) aux
>>> cf2py double precision intent(in) t
>>> cf2py double precision intent(in) dt
>>> cf2py double precision intent(in) Rsphere
Note that num_eqn, mx, my num_aux are identified by f2py as optional arguments since their values can be retrieved by looking at the dimensions of other multidimensional arrays, i.e. q and aux.
We are now ready to call and use the Fortran functions in the initialization script. For instance, the src2 function is called in the script by using a fortran_src_wrapper function whose main part reads:
>>> # Call src2 function
>>> import problem
>>> state.q = problem.src2(mx,my,num_ghost,xlowerg,ylowerg,dx,dy,q,aux,t,dt,Rsphere)
A similar approach is used to call other wrapped Fortran functions like qinit, setaux, etc.
An important feature that makes PyClaw more flexible is the capability to replace the standard low-level Fortran routines whith some problem-specific routines. Binding new low-level functions and replacing the standard ones is very easy; the user just needs to modify the problem-specific Makefile. The shallow water equations on a sphere is again a typical example that uses this nice feature. Indeed, to run correctly the problem an ad-hoc step2 function (i.e. the step2qcor) is required. For that problem the interesting part of the Makefile reads:
# Override step2.f with a new function that contains a call to an additional
# function, i.e. qcor.f
# ==========================================================================
override TWO_D_CLASSIC_SOURCES = step2qcor.f qcor.o flux2.o limiter.o philim.o
qcor.o: qcor.f
$(FC) $(FFLAGS) -o qcor.o -c qcor.f
The user has just to override step2.f with the new function step2qcor.f and provide new:
output_filenames : input_filenames
actions
rules to create the targets required by the new Fortran routine. Similar changes to the problem-specific Makefile can be used to replace other low-level Fortran routines.


Gitrob
Initializing...
0
Findings
0
Files
0
Commits
0
Repositories
0
Targets
Open
Users
00:00:00
Duration
Findings
Action
Path
Commit
Repository


I tackled it by going through the task and ticking things off as I went through, it gave me a lot more time focusing on research and playing with features instead of just producing a perfect final product, which I'm still trying to achieve.
I thought of meditation as a way to relax and reflect and be present in the world at a moment in time, a way to create mindfulness by connecting back to your innerself and giving yourself the attention it needs. personally though I've never committed to any form of meditation, let's be honest most of us don't have the time to do it and are just attracted to the idea of it. Only thing close I can think of is I gave yoga a go about 2 years ago and haven't revisited since, I probably should.
“It’s really just mental training”
Understanding mindful meditation is “Breathing as if your life depends on it.”
Three levels of meditation includes: Attention, Meta-attention and Concentration
Reducing stress levels through minful meditation. Also meditation can help cure tangible things as well (who knew)
Sitting down like a majestic mountain and focusing on being present and if I'm up to it my breathing for 10 mins each day.
I enjoyed the scientific research behind it that is explained in the chapter, I really do think this will help justify spending time on practicing mindful meditation and eliminating preconceived notions on the benefits of meditation. From the book this excerpt sums it up really well: “It is remarkable that mindfulness helps improve everything from attention and brain function to immunity and skin disease”


He may not have programmed in Smalltalk and Lisp, but @rentalcustard explains them well. #baruco
9/13/2014, 7:43:21 AM
Favs: 0
Retweets: 0
link--- layout: tweet ---
He may not have programmed in Smalltalk and Lisp, but @rentalcustard explains them well. #baruco
9/13/2014, 7:43:21 AM
Favs: 0
Retweets: 0
link


4.8
domestic | safety | danger from accidents | 2007
Every
building
must be designed and
constructed
in such a way that:
(a)
people in and around the
building
are protected from injury
that could result from fixed
glazing
, projections or moving
elements on the
building
;
(b)
where there is the possibility of impact by people in and
around the
building
;
(c)
both faces of a window and rooflight in a
building
are capable
of being cleaned such that there will not be a threat to the
cleaner from a fall resulting in severe injury;
(d)
a safe and secure means of access is provided to a roof; and
(e)
manual controls for ventilation and for electrical fixtures can
be operated safely.
Limitation:
Standards 4.8(d) does not apply to
domestic buildings
.
4.8.0 Introduction
This standard covers several unrelated safety issues that do not lend
themselves to inclusion in other standards although glass and
glazing
do
figure prominently.
Collision or entrapment accidents result in a significant numbers of deaths
and injuries to people in and around
buildings
every year. The majority of
these accidents occur during normal use and involve
building
features such
as doors, windows and areas of fixed
glazing
, with the risk of injury increased
where vulnerable glass is involved. Collisions with
glazing
are very common
as it can, if transparent, be difficult to see and may create confusing lighting
effects, presenting particular difficulties for a person with a visual or cognitive
impairment.
Falls still result in deaths and serious injury to people while cleaning
windows. Whether windows are cleaned professionally or by the
building
owner, provision should be made to permit
glazing
to be cleaned safely.
Natural ventilation in
dwellings
is provided by openable windows or
rooflights. People may encounter difficulty and a hazard may arise in
operating controls which are poorly sited. Similarly, location of electrical
sockets, switches and other controls can, if not considered carefully, affect
safe and convenient use.
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).
4.8
—
4.8.0
domestic | safety | danger from accidents | 2007
4.8.1 Collision with projections
Fixtures that project into, or open onto any place to which people have
access can be a hazard. Any element of a
building
capable of projecting into
a circulation route or space should be positioned, secured or guarded so that
it does not present a risk to
building
users.
The simple way to avoid risk is to ensure that obstructions do not encroach
into such spaces. However where a
building
element does project into a
circulation route or space, and any part of the obstruction is less than 2.0 m
above the ground, guarding should be provided to both highlight the hazard
and prevent collision with the
building
element.
Guarding should be provided to:
•
any moveable projection, such as a door leaf or window frame, that opens
across a circulation route or into a circulation space; or
•
any permanent projection of more than 100 mm into a circulation route or
space that begins at a height of more than 300 mm above the ground, or
the projection of which increases with height by more than 100 mm; or
•
any accessible area where headroom reduces to less than 2.0 m, such as
beneath a stair
flight
.
Guarding should comprise of a continuous horizontal rail, at a height of
between 900 mm and 1.1 m above ground level and a solid element, such as
kerb upstand or rail, positioned approximately 100 mm above ground level, to
assist in detection by a visually impaired person using a cane.
There should be visual contrast between guarding rails and surrounding
surfaces. Consideration should be given to positioning of guarding to direct a
person away from the hazard, further reducing the risk of a collision.
Additional guarding may be needed to prevent collision with, or entrapment
by, a powered door leaf (see clause 4.1.8).
Within a
dwelling
, guarding is not needed. A door swing may open into a
circulation space provided no obstructions occur within the unobstructed area
on a stair landing (see clause 4.3.6), on a ramp landing or that would prevent
future installation of a stair lift (see clause 4.2.8).
4.8.2 Collision with glazing
Glazing
in certain locations is more vulnerable to human impact. Care should
be taken in the selection of
glazing
at low level in screens, walls and
partitions or in areas surrounding doors, particularly where
glazed
side
panels may be mistaken for doors.
To reduce the risk of injuries from accidental human impact in these
locations, designers should either:
•
fit
glazing
of a type, thickness and pane size that will be resistant to
impact, which either does not break or breaks safely; or
•
provide protection in the form of guarding to vulnerable
glazing
.
Glazing
should be designed to resist human impact as set out in BS 6262:
Part 4: 2005, where all, or part, of a pane is:
•
within 800 mm of floor level; or
•
part of a door leaf; or
•
within 300 mm of a door leaf and within 1.5 m of floor level.
4.8.1
—
4.8.2
domestic | safety | danger from accidents | 2007
Glazing
manifestation
Large areas of transparent
glazing
, in fixed screens or partitions or where
forming doors, can be difficult to identify and may be a particular hazard to a
accidental collision may be likely, should be made apparent by some form of
manifestation (marking). Differences in the design of manifestation used can
also assist in identifying the position of doors within a
glazed
screen.
Manifestation should be of a size and form that is immediately obvious. It
should, as far as is
reasonably practicable
, contrast visually with
backgrounds viewed through the
glazing
by a person approaching from either
side. Forms might include broken or solid lines, patterns or logos and may
be a continuous element or at appropriate horizontal intervals. Manifestation
should be present within 2 height ranges, between 850 mm and 1.0 m, and
between 1.4 m and 1.6 m above floor level. It should be permanent, e.g.
screen printed or opaque etching or a durable applied material which is not
easily removed.
Unframed
glazed
doors
In addition, any unframed
glazed
door which operates on a pivot action
should have any exposed vertical edge highlighted to contrast visually with
surroundings, to assist in identifying the door edge when opening or in an
open position. This is particularly important on powered doors.
Manifestation or highlighting of door edges need only be provided within
patio doors should not usually attract marking.
4.8.3 Cleaning of windows and rooflights
Falls account for most window cleaning accidents, and generally occur from
loss of balance through over-extension of reach or due to breakage of part of
the
building
fabric through improper use or access. It is therefore important
that transparent or translucent
glazing
should be designed so that it may be
cleaned safely.
There is, however no need to provide for the safe cleaning of any
glazed
element that is opaque and does not allow the passage of light.
Any window or rooflight, all or part of which is more than 4 m above adjacent
ground or internal floor level, should be
constructed
so that any external and
internal
glazed
surfaces can be cleaned safely from:
a. inside the
building
in accordance with the recommendations of Clause 8 of
BS 8213: Part 1: 2004; or
b. a loadbearing surface, such as a balcony or catwalk, large enough to
prevent a person falling further; or
c. a window access system, such as a cradle or travelling ladder, mounted
on the
building,
as described in Annex C3 of BS 8213: Part 1: 2004.
Rooflights in
dwellings
However within a
dwelling
, any rooflight, all of which is more than 1.8 m
above both adjacent ground and internal floor level, need not be
constructed
so that it may be safely cleaned.
Glazing in common
areas
In addition to the above three options, any window or rooflight within a
common area of a
domestic building
may be cleaned from a ladder sited on
adjacent ground or from an adjacent loadbearing surface which has
unobstructed space large enough to allow safe use the a ladder and which
will contain a person from falling further. However a ladder should not be
used to access any external or internal
glazed
surface more than 9 m above
the surface on which the ladder is sited. General guidance on the safe use of
4.8.2
—
4.8.3
domestic | safety | danger from accidents | 2007
ladders may be found in HSE information sheet MISC613 'Safety in window
cleaning using portable ladders'.
Roof access hatches
Glazing
within a roof access hatch, located within a
roof space,
need not be
constructed
so that it may be safe cleaned.
Cleaning from inside
When cleaning a window from inside, a person should not have to sit or stand
on a window sill or use other aids to reach the external face of the window.
The criterion of safety is the ability to reach all points on the surface of the
external
glazing
with only the arm projecting outside the line of the window
whilst remaining standing on the floor.
'Safe reach'
Ergonomic statistics on reach capabilities for the UK adult population are
given in Annex A of BS 8213: Part 1: 2004. As reach may safely be
increased to some degree by use of cleaning implements, it would still be
considered reasonable to apply a safe limit to downward reach of 610 mm
and a safe limit to lateral and vertical reach as an arc with a radius of 850 mm
measured from a point not more than 1.3 m above floor level.
Cleaning from a
loadbearing surface
Where the window is to be cleaned from a loadbearing surface listed in
sub-clause b to this clause, there should be:
•
a means of safe access; and
•
a protective barrier not less than 1.1 m high to any edge of the surface or
access to the surface which is likely to be dangerous.
This method of cleaning is only appropriate where no part of the
glazing
is
more than 4 m above the loadbearing surface.
Alternative methods
Where there is a need for safe cleaning of
glazing
, it may be appropriate to
consider alternate methods of cleaning, in addition to those listed
in guidance, where an equivalent level of safety can be demonstrated.
4.8.4 Guarding of windows for cleaning
For openable windows on the ground and first floor of a
building,
or where the
guarding need be provided for the purpose of cleaning
glazing.
However the
general guidance for provision of protective barriers given in clause 4.4.2
should be followed.
At greater heights, 2
storeys
or more above ground level, where it is intended
risk from a fall should be recognised and guarding provided to a height of at
least 1.1 m above floor level.
Where guarding is provided, it should be designed to conform to BS 6180:
1999. All guarding should be permanently fixed, should not be detachable to
permit windows to open and should be designed so that it is not easily
climbable by children.
Guarding to a window is not needed where the open window gives access to
a fully guarded balcony.
4.8.3
—
4.8.4
domestic | safety | danger from accidents | 2007
4.8.5 Access to manual controls
The location of a manual control device can have a significant effect on both
the ease of operation of the device and safety in use. Positions that are
inaccessible present a greater risk of accident when bending or
reaching. Any control that is intended for operation by the occupants of a
building
should be installed in position that allows safe and convenient use.
This guidance is applicable to manual controls to openable
ventilators
,
including windows and rooflights and to controls and outlets of electrical
fixtures located on a wall or other vertical surface. Unless incorporating a
restrictor or other protective device for safety reasons, controls should be
operable with one hand.
Windows, rooflights
and
ventilators
An openable window or rooflight, that provides natural ventilation to meet
standard 3.14, should have controls for opening, positioned at least 350 mm
from any internal corner, projecting wall or similar obstruction and at a height
of:
•
not more than 1.7 m above floor level, where access to controls is
unobstructed; or
•
not more than 1.5 m above floor level, where access to controls is limited
by a fixed obstruction of not more than 900 mm high which projects not
more than 600 mm in front of the position of the controls, such as a
kitchen
base unit. Where obstruction is greater, a remote means of
opening, in an unobstructed location, should be provided; or
•
not more than 1.2 m above floor level, in an unobstructed location, within
accommodation
(see clause 3.12.3) not provided with mechanical
ventilation.
The above guidance does not apply to windows or rooflights openable only
for cleaning or maintenance purposes or that are controlled by an automatic
system, or to
trickle ventilators
.
Electrical Fixtures
Outlets and controls of electrical fixtures and systems should be positioned at
least 350 mm from any internal corner, projecting wall or similar obstruction
and, unless the need for a higher location can be demonstrated, not more
than 1.2 m above floor level. This would include fixtures such as sockets,
switches, fire alarm call points and timer controls or programmers. Within
this height range:
•
light switches should be positioned at a height of between 900 mm and
1.1 m above floor level;
•
standard switched or unswitched socket outlets and outlets for other
services such as telephone or television should be positioned at least
400 mm above floor level. Above an obstruction, such as a worktop,
fixtures should be at least 150 mm above the projecting surface.
Where socket outlets are concealed, such as to the rear of white goods in a
kitchen
, separate switching should be provided in an accessible position, to
allow appliances to be isolated.
4.8.5
—
4.8.5


| fkGraphics reference pages |
h=POLARBAR h=POLARBAR(rho) h=POLARBAR(theta,rho) h=POLARBAR(hax,...) h=POLARBAR(...,param1,val1,...)
h=POLARBAR plots a polar bar plot of a sine function. A handle to a polar bar graphics object is returned.
h=POLARBAR(rho) plots a polar bar of radius data at equally spaced angles. If rho is a matrix, multiple bar plots will be created.
h=POLARBAR(theta,rho) plots a polar bar in the current axes using the angle and radius data. Theta and rho can be either vectors or matrices of the same size. Alternatively, theta can be a vector and rho can be a matrix with the same number of rows as the length of theta. In this case the function will create as many polar bar plots as there are columns in rho.
h=POLARBAR(hax,...) will plot in axes with handle hax.
h=POLARBAR(...,param1,val1,...) sets polar bar properties through parameter/value pairs. Execute set(h) to see a list of valid properties that can be modified.
| arrowhead | Toolbox page | ipolyline |


$
Product
Price
Fallen short of free delivery on RedMart? Enter how much more you need to hit $100 ($40 for LiveUp Members), and click Find.
This site uses affiliate marketing links. That means it can make a small amount of money when you click on an item listed here.
This is currently
on
. If you want to turn this
off
, click
here
.


Only 3 days left to fund this project.
Join the 42 other donors who have already supported this project. Every dollar helps.
Why give $50?


This is a clone of one of the first video games ever made: Pong.
I implemented three game modes; single-player with three difficulties of AI, two-player local, and two-player networked (multiplayer). The multiplayer is really horribly done and almost too laggy to even be playable, but it does work once you clear a specified port in your router settings.
As usual, I wanted steer clear of swing, and therefore created my own button class, with the ability to use either a coloured background, or an image.
 Overall I’m pleased with the way it turned out, and other than the horrid state the networking is in, I feel this game is finished.
All games hosted on this website which were added after this one can be played in your browser, but unfortunately this and all games before this require a download to be played. So if you don’t trust me enough to download a suspicious jar file, feel free to try any one of my newer online games on this page
Download the game here
The source code can be found on GitHub (Java)


|
rpc.hpp 0.8.1
Simple RPC Header-Only Library
|
For relative performance benchmarks for the adapters of rpc.hpp
see below
| feature | rpc.hpp | rpclib | gRPC |
|---|---|---|---|
| Get result of remote function call | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
| Bind reference parameters of RPC | :heavy_check_mark: | :x: | :x: |
| Call RPCs without headers from the server | :heavy_check_mark: | :heavy_check_mark: | :x: |
| Doesn't require external compilation | :heavy_check_mark: | :heavy_check_mark: | :x: |
| No external dependencies (outside of networking) | :heavy_check_mark: | :heavy_check_mark: | :x: abseil, c-ares, protobuf, openssl, re2, zlib |
| Header-only | :heavy_check_mark: | :x: | :x: |
| Adaptable via "plugins" | :heavy_check_mark: | :x: | :x: |
| Compile-time type safety | :eight_spoked_asterisk: (if using shared headers and call_header_func ) | :x: | :heavy_check_mark: |
| Serialization method(s) | Any provided by adapters (currently: JSON, bitsery) | msgpack | flatbuffers, protobuffers |
| RPC/IPC methods supported | TCP, Websockets, DLL, shared memory, and more... (Just implement the client and server interfaces to pass messages) | TCP only | HTTP only |
The following tests were performed using nanobench. In each case, the call is done over a TCP socket on the same machine (inter-process call) to reduce noise from network traffic.
For each of these tests, server-side caching was disabled for rpc.hpp
. To see the additional benefits of enabling the function cache, see the caching section.
Each "op" is a call to the defined function on the server.
| relative | ns/op | op/s | err% | total | RPC Method |
|---|---|---|---|---|---|
| 100.0% | 131,292.32 | 7,616.59 | 1.1% | 3.25 | rpc.hpp (asio::tcp, njson) |
| 105.0% | 125,005.46 | 7,999.65 | 2.6% | 3.14 | rpc.hpp (asio::tcp, rapidjson) |
| 110.6% | 118,692.83 | 8,425.11 | 1.6% | 2.90 | rpc.hpp (asio::tcp, Boost.JSON) |
| 127.8% | 102,718.72 | 9,735.32 | 1.2% | 2.48 | rpc.hpp (asio::tcp, bitsery) |
| 61.9% | 212,014.89 | 4,716.65 | 0.8% | 5.14 | rpclib |
| 74.8% | 175,597.70 | 5,694.84 | 1.0% | 4.23 | gRPC |
| relative | ns/op | op/s | err% | total | RPC Method |
|---|---|---|---|---|---|
| 100.0% | 135,644.92 | 7,372.19 | 2.2% | 3.30 | rpc.hpp (asio::tcp, njson) |
| 125.8% | 107,826.49 | 9,274.16 | 2.3% | 2.58 | rpc.hpp (asio::tcp, rapidjson) |
| 118.8% | 114,175.54 | 8,758.44 | 1.3% | 2.81 | rpc.hpp (asio::tcp, Boost.JSON) |
| 181.5% | 74,727.74 | 13,381.91 | 2.7% | 1.86 | rpc.hpp (asio::tcp, bitsery) |
| 72.7% | 186,623.39 | 5,358.38 | 2.2% | 4.48 | rpclib |
| 86.7% | 156,521.63 | 6,388.89 | 2.6% | 3.78 | gRPC |
| relative | ns/op | op/s | err% | total | RPC Method |
|---|---|---|---|---|---|
| 100.0% | 112,864.05 | 8,860.22 | 2.8% | 2.82 | rpc.hpp (asio::tcp, njson) |
| 155.0% | 72,815.62 | 13,733.32 | 0.9% | 1.80 | rpc.hpp (asio::tcp, rapidjson) |
| 148.5% | 75,994.39 | 13,158.87 | 1.0% | 1.87 | rpc.hpp (asio::tcp, Boost.JSON) |
| 189.4% | 59,586.13 | 16,782.43 | 2.7% | 1.45 | rpc.hpp (asio::tcp, bitsery) |
| 66.4% | 169,877.21 | 5,886.60 | 2.0% | 4.17 | rpclib |
| 89.1% | 126,717.13 | 7,891.59 | 3.2% | 3.08 | gRPC |
| relative | ns/op | op/s | err% | total | RPC Method |
|---|---|---|---|---|---|
| 100.0% | 116,881.56 | 8,555.67 | 4.8% | 2.88 | rpc.hpp (asio::tcp, njson) |
| 149.0% | 78,432.09 | 12,749.88 | 4.9% | 2.00 | rpc.hpp (asio::tcp, rapidjson) |
| 133.5% | 87,575.67 | 11,418.70 | 3.0% | 2.11 | rpc.hpp (asio::tcp, Boost.JSON) |
| 176.0% | 66,399.04 | 15,060.46 | 1.8% | 1.64 | rpc.hpp (asio::tcp, bitsery) |
| 67.0% | 174,553.87 | 5,728.89 | 3.8% | 4.30 | rpclib |
| 91.5% | 127,777.78 | 7,826.09 | 3.7% | 3.19 | gRPC |
The "Sequential" benchmark aims to replicate real-world behavior where the input of one function might depend on the result of another:
| relative | ns/op | op/s | err% | total | RPC Method |
|---|---|---|---|---|---|
| 100.0% | 603,869,933.33 | 1.66 | 1.1% | 20.76 | rpc.hpp (asio::tcp, njson) |
| 107.3% | 562,596,833.33 | 1.78 | 2.3% | 19.03 | rpc.hpp (asio::tcp, rapidjson) |
| 107.6% | 561,025,000.00 | 1.78 | 2.2% | 19.14 | rpc.hpp (asio::tcp, Boost.JSON) |
| 110.8% | 545,018,366.67 | 1.83 | 2.2% | 18.59 | rpc.hpp (asio::tcp, bitsery) |
| 89.6% | 673,604,233.33 | 1.48 | 2.2% | 23.03 | rpclib |
| 86.9% | 695,083,500.00 | 1.44 | 2.1% | 23.45 | gRPC |
rpc.hpp
can offer some advantages over other RPC solutions, namely in its flexibility, ease of use, and relative performance.
rpc.hpp
is very similar in design to rpclib. Both provide a way to serialize user types and package functions and a simple interface to both bind function calls to the server and call them from a client.
The main advantage rpc.hpp
provides over rpclib is in its flexibility. While rpclib focuses on its rpc-msgpack
implementation, rpc.hpp
provides a fairly generic way to package functions, allowing for the use of different serialization techniques and formats.
Additionally, rpclib only has one transport method: using asio
to pass messages via TCP. rpc.hpp
allows servers to be customized to use any transport method the developer wants, including virtual transport via something like a DLL boundary or shared memory.
rpc.hpp
also provides a pretty significant performance improvement over rpclib, even without caching enabled (between 10-38% faster in testing when using nlohmann-json, sometimes over 100% faster when using bitsery).
While gRPC provides a very robust client/server design and some impressive tooling to create safe interfaces across many different programming languages, it can also be cumbersome to use and has a pretty restrictive interface (mostly by design).
Unlike gRPC, rpc.hpp
does not require external dependencies or building large libraries and does not require an additional compilation step like gRPC does with its protocol buffers. It can also be used with different message passing techniques, where gRPC is stuck with HTTP/2 requests.
For many, having the stability and proven performance (not to mention the support of Google) that comes with a complete solution like gRPC may be ideal in a production setting. At this time, rpc.hpp
cannot compete with the development resources that gRPC has.
With that being said, the flexibility of rpc.hpp
can be an advantage. Because rpc.hpp
does not provide a default server implementation, developers are free to create their own robust system using other proven libraries and frameworks.


Aerosol Distribution Class
|
Define an aerosol distribution. |
AerosolDistribution Methods
|
Add a mode to the distribution as defined using N, GM, and GSD. |
|
Evaluate and return the probability distribution function at particle diameter dp. |
|
Evaluate and return the cumulative probability distribution function between dmin and dmax. |
OPC Class
|
Define an Optical Particle Counter (OPC) with unique properties for wavelength, bins, and viewing angle. |
OPC Methods
|
Calibrate the OPC assuming a specific material. |
|
Return the total number of particles in each bin for a given AerosolDistribution. |
|
Return a histogram containing the [weight] of particles in each OPC bin. |
|
Integrate the distribution according to the OPC for any [weight]. |
Nephelometer Class
|
Define a Nephelometer by its wavelength and range of viewing angles. |
Nephelometer Methods
|
Calibrate a Nephelometer using any AerosolDistribution. |
|
Evaluate a Nephelometer for an AerosolDistribution at a given relative humidity. |
|
Plot the particle size distribution as a histogram/bar chart. |
|
Plot the PDF of an aerosol size distribution. |
|
Plot the CDF of a particle size distribution. |
|
Assess the ability of an OPC to assign particles to their correct bin. |
|
Load sample distributions as described by Seinfeld+Pandis Table 8.3. |
|
Returns a 3xn array of bin diameters. |
|
Returns a 3xn array of bin diameters. |
|
Calculate the wet diameter of a particle based on the hygroscopic growth parameter, kappa (k-Kohler theory). |
|
Calculate the effective density of a particle by calculating the wet and dry percentages and taking the weighted sum. |
|
Calculate the effective k-kohler coefficient from an array of kappa values and their weights. |
|
Calculate the effective refractive index for an array of refractive indices and their respective weights. |
|
Compute the angle-dependant functions (pi and tau) using upward recurrence. |
|
Compute the external field coefficients using the logarithmic derivative. |
|
Compute the complex scattering amplitudes S1 and S2 at angle theta. |
|
Compute the scattering cross section between two angles according to Jaenicke and Hanusch (1993). |
|
Evaluate the number distribution as a lognormal PDF. |
|
The surface-area weighted PDF of a lognormal distribution as calculated using equation 8.4 from Seinfeld and Pandis. |
|
The volume weighted PDF of a lognormal distribution as calculated using equation 8.6 from Seinfeld and Pandis. |
|
The PDF of a lognormal distribution as calculated using equation 8.33 by way of 8.21 from Seinfeld and Pandis. |
|
The surface-area weighted PDF of a lognormal distribution as calculated using equation 8.10 from Seinfeld and Pandis. |
|
The volume weighted PDF of a lognormal distribution as calculated using equation 8.10 from Seinfeld and Pandis. |
|
The PDF of a lognormal distribution on a log10 basis as calculated using equation 8.18 from Seinfeld and Pandis. |
|
The surface-area weighted PDF of a lognormal distribution as calculated using equation 8.19 from Seinfeld and Pandis. |
|
The volume weighted PDF of a lognormal distribution as calculated using equation 8.20 from Seinfeld and Pandis. |
|
Evaluate the total number of particles between two diameters. |
|
Evaluate the total surface area of the particles between two diameters. |
|
Evaluate the total volume of the particles between two diameters. |


* Photographer Martin Adolfsson shows us how suburbia is conquering the world with his new book project, Suburbia Gone Wild.
today’s Very Short List:
culture 24 Jul 2013
Tina Essmaker is a Michigan born, NYC smitten writer and a cofounder of The Great Discontent
Subscribe
* Two Minutes with TGD
* What happens when good friends decide to date? Find out in 40 Days of Dating
http://link.nyobserver.com/516ca68465217dc6e1b9a3a6135t8.hej/Uea0-sJSJmZl97pQD35b8
delightful e-mail that shares
cultural gems from a
different curator every day.
If you have any problems reading this e-mail, click here
http://link.nyobserver.com/516ca68465217dc6e1b9a3a6135t8.hej/Uea0-sJSJmZl97pQFb59e
Subscribe
Forward
My Account
Unsubscribe
tech 22 Jul 2013
food 19 Jul 2013
Wesley Verhoeve on the perfect picnic.
culture 17 Jul 2013
Editorial Policy
Privacy Policy
Contact Us
Press
Terms + Conditions
very fine print: ©2013
Observer VSL LLC.
321 West 44th Street, 6th Floor
New York, NY 10036 USA
All rights reserved.
Questions?<PHONE_NUMBER>.
This message was intended for<EMAIL_ADDRESS>If you believe this has been sent to you in error, please safely unsubscribe


Beowulf
by Francis Barton Gummere
Chapter 39
Additional Information
- Year Published: 1910
- Language: English
- Country of Origin: England
- Source: Gummere, F.B. (1910) Beowulf New York: P.F. Collier and Son
-
Readability:
- Flesch–Kincaid Level: 11.2
- Word Count: 909
- Genre: Epic
- Keywords: british literature
- ✎ Cite This
Downloads
"THE bloody swath of Swedes and Geats
and the storm of their strife, were seen afar,
how folk against folk the fight had wakened.

He had tested Hygelac's hardihood,
the proud one's prowess, would prove it no longer,
defied no more those fighting-wanderers
nor hoped from the seamen to save his hoard,
his bairn and his bride: so he bent him again,
old, to his earth-walls. Yet after him came
with slaughter for Swedes the standards of Hygelac
o'er peaceful plains in pride advancing,
till Hrethelings fought in the fenced town. [footnote 1]
Then Ongentheow with edge of sword,
the hoary-bearded, was held at bay,
and the folk-king there was forced to suffer
Eofor's anger. In ire, at the king
Wulf Wonreding with weapon struck;
and the chieftain's blood, for that blow, in streams
flowed 'neath his hair. No fear felt he,
stout old Scylfing, but straightway repaid
in better bargain that bitter stroke
and faced his foe with fell intent.
Nor swift enough was the son of Wonred
answer to render the aged chief;
too soon on his head the helm was cloven;
blood-bedecked he bowed to earth,
and fell adown; not doomed was he yet,
and well he waxed, though the wound was sore.
Then the hardy Hygelac-thane, [footnote 2]
when his brother fell, with broad brand smote,
giants' sword crashing through giants'-helm
across the shield-wall: sank the king,
his folk's old herdsman, fatally hurt.
There were many to bind the brother's wounds
and lift him, fast as fate allowed
his people to wield the place-of-war.
But Eofor took from Ongentheow,
earl from other, the iron-breastplate,
hard sword hilted, and helmet too,
and the hoar-chief's harness to Hygelac carried,
who took the trappings, and truly promised
rich fee 'mid folk, — and fulfilled it so.
For that grim strife gave the Geatish lord,
Hrethel's offspring, when home he came,
to Eofor and Wulf a wealth of treasure,
Each of them had a hundred thousand [footnote 3]
in land and linked rings; nor at less price reckoned
mid-earth men such mighty deeds!
And to Eofor he gave his only daughter
in pledge of grace, the pride of his home.
"Such is the feud, the foeman's rage,
death-hate of men: so I deem it sure
that the Swedish folk will seek us home
for this fall of their friends, the fighting-Scylfings,
when once they learn that our warrior leader
lifeless lies, who land and hoard
ever defended from all his foes,
furthered his folk's weal, finished his course
a hardy hero. — Now haste is best,
that we go to gaze on our Geatish lord,
and bear the bountiful breaker-of-rings
to the funeral pyre. No fragments merely
shall burn with the warrior. Wealth of jewels,
gold untold and gained in terror,
treasure at last with his life obtained,
all of that booty the brands shall take,
fire shall eat it. No earl must carry
memorial jewel. No maiden fair
shall wreathe her neck with noble ring:
nay, sad in spirit and shorn of her gold,
oft shall she pass o'er paths of exile
now our lord all laughter has laid aside,
all mirth and revel. Many a spear
morning-cold shall be clasped amain,
lifted aloft; nor shall lilt of harp
those warriors wake; but the wan-hued raven,
fain o'er the fallen, his feast shall praise
and boast to the eagle how bravely he ate
when he and the wolf were wasting the slain."
So he told his sorrowful tidings,
and little [footnote 4] he lied, the loyal man
of word or of work. The warriors rose;
sad, they climbed to the Cliff-of-Eagles,
went, welling with tears, the wonder to view.
Found on the sand there, stretched at rest,
their lifeless lord, who had lavished rings
of old upon them. Ending-day
had dawned on the doughty-one; death had seized
in woful slaughter the Weders' king.
There saw they, besides, the strangest being,
loathsome, lying their leader near,
prone on the field. The fiery dragon,
fearful fiend, with flame was scorched.
Reckoned by feet, it was fifty measures
in length as it lay. Aloft erewhile
it had revelled by night, and anon come back,
seeking its den; now in death's sure clutch
it had come to the end of its earth-hall joys.
By it there stood the stoups and jars;
dishes lay there, and dear-decked swords
eaten with rust, as, on earth's lap resting,
a thousand winters they waited there.
For all that heritage huge, that gold
of bygone men, was bound by a spell, [footnote 5]
so the treasure-hall could be touched by none
of human kind, — save that Heaven's King,
God himself, might give whom he would,
Helper of Heroes, the hoard to open, —
even such a man as seemed to him meet.
Footnotes
1. The line may mean: till Hrethelings stormed on the hedged shields, — i.e. the shield-wall or hedge of defensive war — Hrethelings, of course, are Geats.
2. Eofor, brother to Wulf Wonreding.
3. Sc. "value in" hides and the weight of the gold.
4. Not at all.
5. Laid on it when it was put in the barrow. This spell, or in our days the "curse," either prevented discovery or brought dire ills on the finder and taker.


All configured at developer portal
Run code without provisioning servers. Functions as a service. Only get charged for time executing function.
via GIPHY


{% extends 'primary.html' %} {% block content %}
Note: uploading files works best in the Chrome, Microsoft Edge or Firefox browser.
Uploading also uses JavaScript to let you know whether an upload was successful or not.
If you do not get an instant acknowledgement after clicking the "Start upload" button, please wait to receive an confirmation email before moving off the page.
{% if preupload %}
We will send you a confirmation email when your file has been processed.
Upload another file Back to start


NCS (short for Neo-Cortical Simulator) is an open-source neural simulation tool. Like other neural simulators such as NEURON, GENESIS, PyNEST, and BRIAN, it allows neuroscientists to to accurately perform experiments on biologically-realistic neural networks without going in vivo or in vitro. The simulator lets users build, test, and visualize models using a comprehensive set of web-based tools.
What makes it different?
NCS has many features that distinguish it from other neural simulators. Unlike simulators such as NEURON and GENESIS, NCS focuses on simulating large-scale neural networks: on the order of millions of neurons, while still maintaining biological accuracy. NCS also includes a wide-array of tools to help in the development of these large models, such as an easy-to-use web interface, an integrated model database that lets you share models with other researchers, and the ability to deploy a simulation on the Amazon Cloud if you don't have your own cluster.
What can it do?
NCS can run on one computer, or a cluster of over a hundred. It runs on both the CPU and NVIDIA GPU's (using CUDA) to generate maximum computational power. Using a sufficient number of machines and NVIDIA GPU's, the simulator can run a million-cell model in real time. The simulator also offers different neuron models within the same simulation, including Leaky-Integrate and Fire, Izhikivich, and Hodgkin-Huxley to provide neuroscientists the ability to select either detail or performance in different parts of the simulation.


V.V.R. Raj Satyen has rich Entrepreneurial, Operational and Managerial experience earned in diverse business,and Combines technical know - how of enterprises with shrewd business acumen.
His capabilities to lead and translate vision and strategy to successful execution are worth mentioning . He possesses vast experience in managing diverse Organizations , applying best practises,rallying cross functional team participation.
Satyen believes in people and can create a dynamic climate of work.Satyen is an exceptional leader and developer of highly skilled and loyal service teams.He has strong conceptul skills and the ability to carry ideas and concepts through to achieve objectives and business goals.


Step 1. Create an event
Provide the details corresponding to your event / leaderboard.
Event name
Event Link
Leaderboard title
Leaderboard type
Ranking
Hall of fame
Submit


Hi... this is a bit of an odd one - just assembled the V1.4 emonGLCD, all working fine on the test sketch but the screen contrast is very low. I have run it with default contrast/brightness settings in the test code as well as changing them in both directions but not really getting a good display. I then left it running for about 20 mins and the screen slowly but surely faded away (not the backlight - just the pixels) - I can still just about see that the text is there but I need to look very hard, restarting the GLCD doesn't't change anything....
Wondering if this is anything to do with the change to 3V3 on the display? Thanks for any thoughts.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
That happens to me when:
a) the voltage regulator is damaged / defective
b) the voltage regulator can't supply enough power
c) input voltage is out of specs
d) resistors aren't properly dimensioned
e) some pin(s) of the LCD aren't properly connected - which is difficult because this isn't a breadboard.
Can't think of other probable reasons.
Did you test the LCD before soldering?
Maybe someone can tell you what voltages / resistance values to expect when measuring some of the pins on v1.4
Now, I could suggest you put the regulator to the test. But the way things are soldered it's not that simple. This is one of the reasons why I didn't solder the LCD directly to the PCB.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Thanks footswitch....I ran the suggested test on the LCD before soldering but I'm just starting to see why keeping the LCD removable might have been a good idea :-)
All voltages on the board look good and the soldering is usually pretty reliable.
I will try another power supply.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Hey! I have emonGLCD v1.3, assembled just yesterday, and right now it's doing the very same thing!
At least you're not alone... :p
I can't yet figure out what's the root cause, but the main problem for me is that I have done too much to this PCB already (desoldered the LCD), so I wouldn't know if it's not entirely my fault.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Iv increased in the contrast to glcd.begin(0x19); Just for info.. The display is only slightly dimmer for me at 3.3v over 5v
I would check the voltage at pins 14 - 15 as these are the power pins on the GLCD.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Thanks Rob, I'm getting 3.1V between pins 14-15... hmmm.
Also, assuming you are on V1.4, may I ask what value resistors you popped into R7 & R8 ? I'm guessing these are something to do with the switches?
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Sorry iv got the v1.3 was not even aware that V1.4 was out yet..
3.1 does seem down on what i was seeing i see bang on 3.3v on these pins. How have you got these connected. EG the fly lead or some other way.. (this will only make sence if you have V1.3)
R7 & R8 ? You can have a look at the solder map here http://solderpad.com/openenergymon/emonglcd/
Could you take some photos of both sides to see if there is a component in the wrong place.. (You may only be able to do one side..
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Just built the V1.4 emon GLCD and getting the same problem. I have the 10k resistors in R7&R8. I've tried on a number of different power sources (laptop usb and desktop with ftdi cable) and am getting 3.3v to the LCD. I have not yet tried the optional 100r 0.5w resistor on the back of the board.
Are you sure pins 14 and 15 of the lcd are power, they look like they are connected together on mine. I get 3.3v between 14 & 13.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I left it running overnight and it seems to be working fine this morning...?
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Hi Tim, yes odd - mine settled down too when left on for a few hours.
Do you have slight vertical banding on your screen? If I look closely I can see the the columns of pixels go something like 4 light & 2 darker. Not a huge problem but strange.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Precisely the same here.
Mine (v1.3) is either fading or getting too dark (contrast?), sometimes returning to normal operation. When the screen gets dark, the vertical bars that you mention above aren't just visible: in fact most of the screen becomes black. But everything's working underneath, you can see it from an angle.
Note: v1.4 shouldn't have a 100 ohm resistor between PWR and GND for the LCD, since it's already powering the LCD with 3.3 V.
At least everything I've read up until now confirms this.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Yes Rob, I too have the fainter vertical columns. I have not seen the screen getting too dark (yet!).
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I wonder what's going on with this screen, seems to be a common problem - I'm puzzled.
This is what my screen looks like with a JeeLabs demo.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I also get this but increasing the contrast and decreasing the PWM of the backlight seem to make it almost dissapear..
Saying this iv got v1.3 but it is running at 3.3v
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Hello, sorry to hear about the trouble, I will ask Glyn to see if he has any ideas. I've just uploaded the schematics for version v1.4 here and detailed firmware changes to do with the switches:
http://openenergymonitor.org/emon/node/761
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I just made my 1.4 kit today and get the same problem. It is fine with the test scetch but with the regular scetch makes the display so dim it is almost impossibe to read. I've left it on while I'm away for a while so I'll see if that makes any difference.
I have installed R7&8 but have left out the 100R for the back.
Also the build guide needs to be updated for 1.4, but I was able to figure it out with the schematic.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I just left it switched on. The dislay faded off almost completely and then came back to full contrast over a couple of hours. Looks fine now. Maybe the displays were manufactured a long time ago and need time to "re-activate" I know old tech LCD's did have issues with image burn which could be mitigated by exercising the display. Anyone else have any ideas. Can't see how anything to do with the driver could cause (or magically cure) this kind of issue?
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I've had a similar experience with a new emonGLCD 1.4 build over the weekend. The LCD display starts off so feint you can barely read it. After leaving it on for a couple of hours, the display becomes easily readable. There are still a number of lighter vertical strips though. When I switch mode to show the time, the pixels are much bolder. I tested the voltage into the LCD display between pins 13 and 14 and I get 3.3v. I'm baffled!
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I've just done a blog post on the emonGLCD V1.4, better late than never! Sorry if your having contrast issues, we have found that after being switches on a while the LCD seems to resolve it's self. There may be somesort of 'bedding-in' period when powering up the LCD for the first time due to the LCD now running at a
lowercorrect voltage. Please post on this thread if you find the problem persists.Here's the blog post: http://openenergymonitor.blogspot.com/2012/07/emonglcd-v14.html
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Same here - capacitors?
Exactly the same for me. New 1.4 EmonGLCD kit arrived yesterday, and I spent the evening building it.
LCD tested ok prior to soldering as suggested, but contrast was rather poor. After soldering in, the contrast faded even more to become totally blank. Seeing this thread, I left it running overnight, and today the test sketch displays fine. Power to LCD measures 3.3 volts.
I was wondering whether perhaps one of the 10uF capacitors has reversed polarity? Would that not cause it to gradually change into a resistor over several minutes as the dielectic disolves, and then start working again as the dielectric slowly re-forms on the other plate? It's only a hypothosis, but the requirement for a new LCD screen to 'bed in' seems nonsense to me.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
The 'bedding-in' period does indeed seem like a strange phenomenon, I cannt explain it at the moment. The 10uF capacitors are connected identically as they were in the previous version of the emonGLCD (V1.3) and no such phenomenom was exhibited. A possible explination is that we are currently going through a sub-optimal batch of LCD units....
You can view the schematic for youreslf here: solderpad.com/openenergymon/emonglcd
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I recon that two capacitors are backwards!
Comparing this:http://jeelabs.net/attachments/1019/glcd-info.png (which gives the pin-out of the module)
with this:http://openenergymonitor.org/emon/sites/default/files/emonGLCD_V1.4.png suggests that both C13 and C14 are backwards!
For example pin 11 is labelled as CAP3P on the first drawing, but the schematic has this as a -ve end of C14.
Martin
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
 Well spotted. I've just double checked myself againsed the datasheet.
The design was based on the JeeLabs graphics board, it seems this also has the same error. I've just read the build guide for the graphics board and there is a note stating "The next step needs some care, because these two electrolytic caps are marked the wrong way on the silkscreen – they should be placed as follows:".
Thanks a lot for spotting this error, its suprising it has not caused more issues than it has. It seems that when the LCD was ran at 5V as in the case with the V1.3 (this is actually out of spec for the unit, another bug inherited from the Graphics Card) the contrast seemed to be fine. I have had a V1.3 running for about 12 months continuously without any contrast issues or resets.
Tomorrow I will build up a new emonGLCD V1.4 with C14 and C13 in the correct orientation and post results....
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
You could always put an analogue moving coil multimeter across them and find out for sure! (That will fairly reliably respond to the average voltage).
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I would have checked with a multimeter, except that once the LCD is soldered in, the capacitor feet are totally inaccessible.
I'm a bit puzzled too why it worked without any obvious issues when fed from a 5v spply. Maybe on 1.3, the contrast too faded for a while, but not to the extent that anyone really got bothered by it.
I was trying to find some reference somewhere about whether electrolytics can be 'reversed' in this way and how they behave when mall-treated. All I could find is they tend to overheat and explode! Well, clearly, these ones don't.
Martin
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
How electrolytics behave when reverse biassed depends on the current. If it is limited to a small value, then as far as I know they'll just sit there conducting, and what heat there is will be dissipated and nobody notices. I think they tend to look like a resistance in the order of tens of ohms. You can certainly reverse bias an electrolytic with a very small voltage and get away with it for a short time, but it's not recommended. If the current is large, the electrolyte boils and then you tend to have boiling electrolyte, paper and aluminium splattered everywhere - it can be extremely nasty stuff.
This paper http://www.ken-gilbert.com/images/pdf/lytic_voltage_limit.pdf explains the mechanism and gives a reverse voltage limit of 1-3 V.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I've had some nasty experiences with tantalum beads being inserted reversed. A nice minature flame thrower. And they can sit there for months or years before exploding.
Lloyd
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Iv'e just built up an emonGLCD V1.4 with C13 and C14 inserted the opposit way round. The LCD powerd up immediately wtih no fading of contrast. I'll keep it powered up for a long term test.
I've added a note to the build guide to state that C13 and C14 should be inserted the opposite way round to the markings on the PCB.
Thanks again for spotting this!
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Just measured the voltage across the capcaitors when the LCD is powered up (displaying the clock page). There is 8V across C14 and 0V across C13. This was measured on an older emonGND where the capacitors were reversed polarity.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Does this mean we should remove them and swap them round even on the old boards (v1.3)..
Would we see any improvement on contrast also?
Not too keen on the thought it could go pop..
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Exactly what I was thinking!
Since the GLCD is designed to run 24*7, should we all be concerned?
The prospect of desoldering the LCD panel to gain access to the caps' solder pads is a little daunting!
I'm hoping that:
a) the chance of going 'Pop' is small. If they didn't explode during the initial bedding-in, then all is fine.
b) even if they do go POP the worst that can happen is that the LCD stops working and we have to build another kit.
If I do decide to replace the caps, then how to do it? By far the easiest way to remove the LCD panel to gain access would be to cut all the legs then desolder one by one. Where can one get replacement LCD panels from? Perhaps Glyn could post somewhere the actual make and model of these? (I've already folded my panel up and down a couple of times - not sure how many more times I can do this before the pins start breaking).
Martin
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Lloyd
A nice minature purple flame thrower. Fixed that for you
robinsmh
If they didn't explode during the initial bedding-in, then all is fine. I would not trust that. The electro-chemical reactions going on inside mean that they are increasingly likely to fail over time.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
My hypothosis is that during that initial bedding in period, the caps actually did fail, then gradually reformed with a dielectric layer building up on the cathode (now used as the anode). If they survived that without exploding, then the circuit they are connected to is unable to deliver enough current to overheat them, so it should all be safe. However - don't quote me on that! I'm just a software engineer who knows almost nothing about the inner workings of capacitors.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
The display is a DOGL128x EA-6. Manufactured by these guys in Germany, MMS Electronics is the UK distributor. We can provide the LCD on it's own if required. It is possible to access the capacitors by just de-soldering the top legs of the LCD then bending it back to gain access. It's still quite a fiddly job though and there is a risk of damaging the LCD.
We have 20-25 emonGLCD units installed in our lab, houses and other local houses these have been running without issue 24/7 since the end of last year.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I suggested this to Glyn and he seems to think it is practical, though great care would be needed:
Take the capacitors out of circuit by cutting the LCD pins leaving as much as possible on the LCD, then solder replacement capacitors to the cut-off stubs.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Yep - capasitors C13 and C14 are wrong way round on v 1.4 leading to low contrast. Suggest that there is a clear message of reversing the polarity added with BOLD and BIG RED to the build instructions. (of course its there but I just missed it as building the board is so mechanical excersise)
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
You must watch these little points!
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Ah....ha - thanks for the cap info - looks like this sorted the issue nicely :-)
One way to do this (without taking the LCD off) is snip off the caps to be replaced, pop a dob of solder on each of the 4 pads and the in turn use a £3 (or more if you fancy) de-solder pump to suck up the solder and hopefully the remaining cap leg at the same time. 2 of my cap legs needed persuasion with a pair of tweezers but all in all a fairly painless removal. When you put the new caps back you will need to keep the cap body off the PCB by about 3mm (to get the solder tip in) so either use a more compact cap so the tops line through with the other 2 caps or fold the new caps back down onto the PCB... so you can get the back cover on again :-) Its about a 5-10 minute job.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
b***x got the same problem and thought it was me - this is the first project I've done in about 10 years and was very careful to follow the instructions! I built the board about two weeks ago and was just getting round to loading the scripts up, I now see that the text is there, Can you make it in RED please, then I might not have missed it :(
If I'm feeling brave I might follow robur's advice otherwise I'll leave it on overnight, and see if the contrast improves --- else if it ain't broke don;t fix it comes to mind..
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Hello!
I've just built up an emonGLCD V1.4 with C13 and C14 inserted the opposite way round as suggested in step 7. At first there was a low contrast with vertical bands of more visible columns of pixels. As I experiment more, I get less and less contrast. Now I can barely see the pixels. I'll try to leave it overnight and see if that helps.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
You could try adjusting the contrast - it's the 0x20 (the maximum) in the line "glcd.begin(0x20);" at the top of setup( ).
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
I changed contrast but with no visible difference. As I told yesterday I left it working all night long, and today it looks completely dead. I can't see anything. While writing this message I've seen a second or two of increased contrast (with more contrast vertical stripes) but then it went back to clear screen. Everything seems soldered well. Any ideas how to debug this? Thank you!
P.S. Voltage on LCD is exactly 3.3 V. (measured 14-15 pins)
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
It does sound to me like a voltage regulator problem. The LCD has a voltage boost circuit (the Sitronix ST7565R data sheet explains - pages 31 onwards) and I think there is the first place to look. Make sure all the capacitors are present and correct (and look again for bad joints!). We're using the circuit of diagram 1.1 on P.38.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Robert, thanks for answering. All the capacitors are present, C13 and C14 are rotated 180° as suggested. I am attaching a photo of my PCB.
Does 3.3 V on LCD look wrong to you?
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Yours looks exactly the same as mine - even the resistors and the non-polarised capacitors are the same way round! The only difference I can see is I've got a black aerial. So there's nothing obvious there.
Here are the voltages for mine. (All d.c. measured with a DMM)
1 - 8.53
2 - 7.34
3 - 6.09
4 - 2.48
5 - 1.24
7 - 1.63
8 - 7.07
9 - 4.44
10 - 1.65
11 - 9.68
12 - 10.96
14 - 3.27
15 - 3.27
I'm not certain, I think the pins relate to the Sitronix data thus:
Pin Symbol Level Function
1 V0 - LC Drive
2 V1 - LC Drive
3 V2 - LC Drive
4 V3 - LC Drive
5 V4 - LC Drive
6 VSS L Power Supply 0V (GND)
7 CAP2N - Voltage Converter
8 CAP2P - Voltage Converter
9 CAP1P - Voltage Converter
10 CAP1N - Voltage Converter
11 CAP3P - Voltage Converter
12 VOUT - Voltage Output about +12V
13 VSS L Power Supply 0V (GND)
14 VDD2 H Power Supply Booster
15 VDD H Power Supply +1.8..3,3V
16 SI H / L Serial Data In
17 SCL H / L Serial Clock
18 A0 H / L L= Command, H= Data
19 RST L Reset (active low)
20 CS1B L Chip Select (active low)
I suggest you check against this and we'll take it from there.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Hi, Robert.
Thanks for taking your time.
Here are my results:
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
It's obvious that all your voltages on the LCD are somewhat lower - some quite a lot lower, your pin 12 is only a little more than half mine - and I think that is probably the cause. But at the moment I can't think of a good reason why, as the supply voltage is correct. My thoughts are along the lines of it could be the driver IC or a faulty component around the voltage multiplier, or something dragging it down.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
One more observation:
If it stays off for a while, when I switch it on, I can see a picture. It has vertical stripes and rather low contrast but it is readable. Then it starts to degrade to almost invisible. While writing this message I glanced on the screen and saw it in a perfect contrast. It stayed like that about half a minute and then began to turn low and back high contrast rapidly like there was a loose contact somewhere. I checked and pressed every part but it's definitely not a contact issue.
Maybe I should try to replace the C8-C12 capacitors as they are still accessible. Or should I invent how to unsolder LCD panel and check C13-C16?
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Hi Ababak,
Sorry to hear your having trouble. It sounds like you might have a faulty LCD. I've looked at the photo of your assembled emonGLCD and all look well.
Robert: thanks a lot for helping to debug this.
We're happy to send you another emonGLCD kit free for charge, including all components accept at ATmega328 microcontroller and plywood fascia as these can be easily swapped from the faluty unit.
Please could you email me your origional order number to<EMAIL_ADDRESS>All the best,
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Thanks, Glyn, I appreciate this very much. Sent you an e-mail.
Re: RESOLVED - GLCD on V1.4 - low contrast & fading screen?
Sorry to dig this old post up again but does anyone know why 10uF electrolytics were used in the first place?
The datasheet for the display shows 1uF unpolarized capacitors, which seem like a better choice if they work.
I'm just about to build another emonGLCD so I'm going to try 1uF capacitors in this one.


The TrenchantCompetitor Application project is a system for youths/students, and all other people who would like to use the app.
The feature of the application contains educational information, quizzes, trivia, current updates, general knowledge of psychology for the study of behaviourism of individuals and recommendations for the users who needed counselling that are under emotional distress.
The symptoms of depression can appear during adolescence and may include changes in sleep patterns, appetite, and weight. Feelings of despair, hopelessness, sadness, and worthlessness may also appear. Other signs include social withdrawal , trouble concentrating or remembering, suicidal thoughts or actions, and medically unexplained symptoms. When mental health professionals suspect depression, they usually look for groups of symptoms that persist for weeks and that disrupt a person's everyday life.
According to WHO, "depression results from a complex interaction of social, psychological and biological factors." These include the following:
Depression often runs in families, suggesting that genetics can play a role, perhaps affecting chemical activity in the brain. Other physical risk factors include cardiovascular disease and changing hormone levels, as well as ongoing substance abbuse, which may intesify depression, if not give rise to it.
While a little stress can be healthy, chronic or excesssive stress can be physically and psychologically harmful, sometimes to the point of plunging a susceptible, or biologically vulnerable, teen into depression. That said, the exact causes of depression remain unclear and may involve a combination of factors, as mentioned earlier.
Stress-related factors linked to depression may include parental divorce or separation, the death of a loved one, physical or sexual abuse, a serious accident, illness, or learning disability --especially if a child feels rejected as a result. A related factor may be unrealistically high parental expectations, perhaps in regard to scholastic achievement. Other possible causes are bullying, uncertainty about the future, emotional estrangement by a depressed parent, and parental unpredictability. If depression results, what may help each individual to cope?


Knoblomat
Home
Help
Config
About
Error
4
0
4
Sorry, an error has occured, the requested resource has not been found!
Take Me Home


Class links.Network.Node
Node
A node. A node can be connected to other nodes via one or multiple links.
Defined in: network.js.
| Constructor Attributes | Constructor Name and Description |
|---|---|
|
links.Network.Node(properties, imagelist, grouplist, constants)
|
| Method Attributes | Method Name and Description |
|---|---|
|
discreteStep(interval)
Perform one discrete step for the node
|
|
|
draw(ctx)
Draw this node in the given canvas
The 2d context of a HTML canvas can be retrieved by canvas.getContext("2d");
|
|
|
getDistance(x, y)
Calculate the distance from the nodes location to the given location (x,y)
|
|
|
getTextSize(ctx)
|
|
|
getTitle()
get the title of this node.
|
|
|
getValue()
Retrieve the value of the node.
|
|
|
isFixed()
Check if this node has a fixed x and y position
|
|
|
isMoving(vmin)
Check if this node is moving
|
|
|
isOverlappingWith(obj)
Check if this object is overlapping with the provided object
|
|
|
check if this node is selecte
|
|
|
select()
select this node
|
|
|
setProperties(properties, constants)
Set or overwrite properties for the node
|
|
|
setValueRange(min, max)
Adjust the value range of the node.
|
|
|
unselect()
unselect this node
|
Class Detail
links.Network.Node(properties, imagelist, grouplist, constants)
- Parameters:
- {object} properties
- An object containing properties for the node. All properties are optional, except for the id. {number} id Id of the node. Required {string} text Title for the node {number} x Horizontal position of the node {number} y Vertical position of the node {string} style Drawing style, available: "database", "circle", "rect", "image", "text", "dot", "star", "triangle", "triangleDown", "square" {string} image An image url {string} title An title text, can be HTML {anytype} group A group name or number
- {links.Network.Images} imagelist
- A list with images. Only needed when the node has an image
- {links.Network.Groups} grouplist
- A list with groups. Needed for retrieving group properties
- {Object} constants
- An object with default values for example for the color
Method Detail
discreteStep(interval)
Perform one discrete step for the node
- Parameters:
- {number} interval
- Time interval in seconds
draw(ctx)
Draw this node in the given canvas
The 2d context of a HTML canvas can be retrieved by canvas.getContext("2d");
- Parameters:
- {CanvasRenderingContext2D} ctx
{Number}
getDistance(x, y)
Calculate the distance from the nodes location to the given location (x,y)
- Parameters:
- {Number} x
- {Number} y
- Returns:
- {Number} value
getTextSize(ctx)
- Parameters:
- ctx
{string}
getTitle()
get the title of this node.
- Returns:
- {string} title The title of the node, or undefined when no title has been set.
{Number}
getValue()
Retrieve the value of the node. Can be undefined
- Returns:
- {Number} value
{boolean}
isFixed()
Check if this node has a fixed x and y position
- Returns:
- {boolean} true if fixed, false if not
{boolean}
isMoving(vmin)
Check if this node is moving
- Parameters:
- {number} vmin
- the minimum velocity considered as "moving"
- Returns:
- {boolean} true if moving, false if it has no velocity
{boolean}
isOverlappingWith(obj)
Check if this object is overlapping with the provided object
- Parameters:
- {Object} obj
- an object with parameters left, top, right, bottom
- Returns:
- {boolean} True if location is located on node
{boolean}
isSelected()
check if this node is selecte
- Returns:
- {boolean} selected True if node is selected, else false
select()
select this node
setProperties(properties, constants)
Set or overwrite properties for the node
- Parameters:
- {Object} properties
- an object with properties
- {Object} constants
- and object with default, global properties
setValueRange(min, max)
Adjust the value range of the node. The node will adjust it's radius
based on its value.
- Parameters:
- {Number} min
- {Number} max
unselect()
unselect this node


All data currently shown is entirely fictitious, for demonstration purposes only.
The Ebola Dashboard is a tool for viewing and analyzing real-time data collected in the field pertaining to Ebola deaths and suspected infection. This is a Fulcrum Gives Back initiative, which is supported as resources will allow. The system functions will change and develop as individuals in the field provide feedback. If you are in West Africa and need this collection tool, please consider joining us.
How to join:
- Send us the names and emails of your organization's field collectors. Identify a point of contact. Team members will receive an invite to join.
- Have team members download the Fulcrum app on their Android or iOS devices.
- Once your team has logged in there will be two apps: Live Data & Sandbox. Familiarize yourself within the Sandbox and start collecting Ebola case data in Live Data.


Growing up in northern Minnesota life traveled at a snails pace, I however never have. Starting from a young age, I grew up in a garage. I began taking apart anything I could get my hands on, sometimes I would even manage to get back together correctly. This curiosity stuck throughout life as I moved from pedal bikes to snowmobiles and ATVs. Ultimately it brought me into the career path of construction and I loved building.
You see, I am a builder at heart, but I got injured and can no longer do that type of work. So I began the process of figuring out my next step in life, then I found coding… What a match made in heaven! I can still be a builder. I can still use my creativity to solve the worlds problems one at a time. Most importantly, I can still be passionate about what I do everyday.
My coding journey began thanks to the help from The Coding Bootcamp @ UMN_Bootcamp!
What We OfferLooks great on any screen size!
Freshly redesigned for Bootstrap 4.
Millions of users Start Bootstrap!
I mustache you a question...


|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
| Class Summary | |
| ProcAllocateElectronicGood | This processor allocates softgood shipping group by allocating all its item relationships |
| ProcAllocateItemRelationship | This processor allocates all hardgood itemRelationships in the shipping group |
| ProcAllocateShippingGroup | This processor allocates the hardgood shipping group by calling the corresponding chain |
| ProcCancelRemoveOrder | This processor cancels removing an order because of one or more its shipping groups `* or other components could not be removed |
| ProcCreateElectronicGood | This processor allocates an electronic item by calling the ClaimableManager |
| ProcCreditOrder | This processor will credit the order |
| ProcDeliverElectronicGoodByListener | This processor delivers an electronic item by the email Listener action |
| ProcDeliverElectronicGoodByTemplate | This processor delivers an electronic item by the email template |
| ProcExecuteFulfillOrderFragment | This processor will execute the chain to delegate the FulfillOrderFragment messages to the fulfiller systems. |
| ProcExtractOrderId | This processor uses the ClientLockManager to guarrantee that only one thread dealing with a message for a given key is running through the system at any moment in time. |
| ProcExtractShippingGroupIds | This processor extracts shipping groups ids from the modification object |
| ProcFailOrder | This processor will fail the order |
| ProcFinishOrder | This processor will finish the order processing |
| ProcFinishRemoveOrder | This processor will finish removing the order |
| ProcFinishShippingGroup | This processor will "ship" the shipping group by setting its states to completion |
| ProcHandleElectronicSenderType | This processor routes the electronic item delivery procedure |
| ProcHandleItemRelationshipState | This processor routes the item allocation procedure based on the relationship's state |
| ProcHandleMessageType | This processor determines the message type received by the Fulfiller router and calls to multiple chains to process the message |
| ProcHandleModificationClassType | This processor will route the modification execution based on the modification class type Works for both ModifyOrder and ModifyOrderNotification JMS messages |
| ProcHandleModificationTargetType | This processor routes the execution of the id target modification. |
| ProcHandleModificationType | This processor will route the modification execution based on the modification `* operation type like add, remove, update |
| ProcHandleNewType | This method is called to handle all messages other than the other handle methods. |
| ProcHandleOrderPendingShipMap | This processor iterates through the Hashmap object with orders whose shipping groups are ready to ship. |
| ProcHandleOrderWaitingShipMap | This processor handles the HashMap object that contains the orders with shipping groups whose items could not be allocated from the repository in the former allocation procedures. |
| ProcHandleRelationshipState | This processor will route the execution resulted in a change of a relationship's state |
| ProcHandleRetrievingOrder | This processor loads the order by the id. |
| ProcHandleShippingGroupState | This processor routes the execution resulted in an update of a shipping group based on the shipping group's new state value. |
| ProcHandleShippingGroupUpdateModification | This processor executes the shipping group update modification sent in the modify order notification message to the OrderFulfiller. |
| ProcLoadOrderRepository | This processor loads the order by the id. |
| ProcLoadSaveOrderRepository | This processor loads the order by the id. |
| ProcLockMessage | This processor uses the ClientLockManager to guarrantee that only one thread dealing with a message for a given key is running through the system at any moment in time. |
| ProcModificationUnsupported | This processor simply fails the modification due its unsupported reasons. |
| ProcPerformRelationshipModification | This processor executes the relationship id target modification passed to the OrderFulfiller in the modifyOrder message. |
| ProcPerformShippingGroupModification | This processor executes the shipping group modification passed in the modifyOrder message to the OrderFufiller |
| ProcProcessShippingGroups | This processor processes (fulfills) shipping groups for both hardgood and softgood fulfillers It will call to the corresponding fulfillers' chains to actually process the groups. |
| ProcPurchaseBackOrder | This processor allocates a backordered item from the inventory |
| ProcPurchaseConfigurableItem | Handles allocating the items from inventory for a configurable commerce item. |
| ProcPurchaseItem | This processor allocates in stock item |
| ProcPurchasePreOrder | This processor allocates a preordered item from the inventory |
| ProcRemoveOrder | This processor will execute the chain to remove an order |
| ProcRemoveShipItemRelationship | This processor removes the item relationship from the shipping group by reallocating its quantity in the inventory. |
| ProcRemoveShipItemRelFromItem | This processor will remove the relationship's quantity from the CommerceItem's quantity |
| ProcRemoveShipItemRelsFromShippingGroup | This processor removes item Relationships from the shipping group. |
| ProcRetrieveItemRelQuantity | This processor gets the itemRelationship's quantity to allocate it from the inventory |
| ProcRetrieveOrderPendingShipMap | This processor is executed as part of the HardgoodShipper to ship shipping groups that are in a PENDING_SHIPMENT state. |
| ProcRetrieveOrderWaitingShipMap | This processor is called on a reception of a UpdateInventory JMS Message. |
| ProcRetrieveShippingGroupsToBeSplit | This processor finds all shipping groups in an order that need to be split across multiple fulfillers (shipping groups that are to be fulfilled by more than one fulfiller) |
| ProcSendFulfillOrderFragment | This processor sends the FulfillOrderFragment messages to the fulfillers. |
| ProcSendModifyOrderForRemoval | This processor executes removing of an order by setting the order's and its components states to PENDING_REMOVE and sending the modifyOrder message to the fulfiller |
| ProcSendModifyOrderNotification | This processor sends the ModifyOrderNotification message with the changes that have been done to the order. |
| ProcSettleOrder | This processor will settle the order by calling the PaymentManager for each PaymentGroup |
| ProcShipAsItemsAreAvailable | Check with the special instructions of the shipping group to see what the behavior should be if only part of the group has been allocated. |
| ProcShippingGroupHasShipped | This processor will call to the chain to ship a shipping group that is in a PENDING_SHIPMENT state |
| ProcSplitShippingGroupForAvailableItems | This processor splits the shipping group into two shipping groups, one with items PENDING_DELIVERY and one with items that aren't PENDING_DELIVERY |
| ProcSplitShippingGroupsForFulfillment | This processor splits the shipping groups passed in the order if the shipping groups are to be fulfilled by more than one fulfiller |
| ProcSwitchOnCommerceItemType | This processor returns 1 if the given CommerceItem is not a ConfigurableCommerceItem, 2 if it is. |
| ProcUpdateOrderRepository | This processor saves the order back to the repository after it has been processed. |
| ProcVerifyItemRelationshipForRemoval | This processor verifies if the item relatioship is in a state that allows it to be removed |
| ProcVerifyOrderForFulfillment | This processor verifies that the order to be fulfilled is in a state which allows it to be fulfilled. |
| ProcVerifyOrderForRemoval | This processor verifies if the order is in a state that allows it to be removed |
| ProcVerifyShippingGroupForCompletion | This processor verifies if the shipping group is in a state that allows it to be shipped (PENDING_SHIPMENT) |
| ProcVerifyShippingGroupForFulfillment | This method verifies that the shipping group to be fulfilled is in a state which allows it to be fulfilled. |
| ProcVerifyShippingGroupForRemoval | This processor verifies if the shipping group is in a state that allows it to be removed |
| ProcVerifyShippingGroupsForFulfillers | This processor will verify if the shipping groups passed in the order can be handled by their fulfillers. |
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


With its stark beauty this place lures many people to their deaths
This place can be as beautiful as it is deadly
Yep, many have died here.


About me
An Andrew Peacock Production
Thanks for playing my guessing game, folks! Hope it helped you learn a little about who I am!
The Questions!
- First Statement: In high school, Andrew could box squat over 800lbs!
- Second Statement: Andrew released a rap mixtape on Soundcloud last year, and one of the tracks went viral in June.
- Third Statement: Andrew has been playing the popular fighting game Street Fighter for years and netted a sponsorship in November 2016!
- Fourth Statement: Andrew spent multiple years as a bouncer in a Montana bar!
- Fifth Statement: Andrew hates dogs but loves cats!
- Sixth Question: 310lbs! Never quite got to three plates, sadly.
- The possible answers were boxing, kickboxing, swordfighting, Jiu Jitsu, Karate, and Muay Thai! Andrew has always loved the cerebral side of fighting and participating in consensual fisticuffs has long been one of his favorite pasttimes.
- !This is my first time coding
- .Although I love fighting, I've never fought anyone that wasn't wearing gloves! I'm a teddy bear at heart
- !I listen to rap music nigh exclusively
- .I've never worked in an office environment before
- .I've had two major ankle surgeries...on the same ankle
- !But I've never 'broken' a bone...
- !I love cooking and dogs more than most things on this Earth
- This is Our Science- Astronautalis
- Castor, The Twin- Dessa
- No Kings- Doomtree
- Stunt- Barenaked Ladies
- Broken Bone Ballads- Ceschi
- Cannonball!!!- Bleubird
- The Calling-Hilltop Hoods
- The Hard Road- Hilltop Hoods
- Li(f)e- Sage Francis
- Skelethon- Aesop Rock


Hi, I'm Olivia Reichley
I absolutely love all things music, lifestyle, and fitness! Im a 21 year old college student and have a lot of fun making music and editing! I hope you enjoy my videos, don't forget to subscribe:)
Business email: livreichley@gmail.com


Last week I had the pleasure of visiting the headquarters of Rackspace, an innovative and leading cloud hosting provider to discuss some of their newer product offerings and iron out implementation details for a large client of Acquity Group. The agenda included a tour of their facilities by an early employee who goes by Sugar Bear. There’s a great story as to how he got his name but we’re already straying off-course…
Based out of Texas, the company welcomes the Cowboy persona to the workplace. I don’t mean Cowboy in the sense that there is little to no preparation with everyone shooting from the hip. By keeping the organization very flat, a large pool of decision makers are hands-on and aren’t afraid to dwelve into the technical details.
The company also prides itself in providing the best customer service, a trait not too far from the state’s Southern Hospitality
The work area also has flags hanging from above the range from various national flags to sports teams. The company also awards tenured Rackers with milestone flags (‘X Year Racker’). Having everybody (including the CEO) sit in an open area cube, there is a very egalitarian atmosphere and Executive Management seemed very open and easy to approach.
If you’re not familiar with Rackspace, their main headquarters used to be Mervyn’s Department Store. One of the employees had rented out his prom tux from a store that is currently a conference room.
After Mervyn’s closed its doors, Rackspace purchased the property, split it into segments and began construction. Precaution was taken to minimize waste and donate any materials over to the community.
Nicknamed “The Castle” by Rackers, their relocation to the HQ was tagged “Storm the Castle”. There are entertaining videos of the CEO, Lanham Napier, giving a pep rallies to his employees to get ready for the battle.
But what’s the point of a castle without breaking any world records, right?
The Castle is LEED Gold Certified. If that doesn’t mean much to you, think energy efficient lights everywhere, greener building materials and toilets that have two settings to flush.
They also have a wicked cool fan - the “Big Ass Fan”
Because cool tech companies realize their employees miss their younger days. As in way younger days.
One of the newer areas of the castle has a dedicated area for a museum. How about that? :)
A lot of employees were wearing different Rackspace t-shirts and there was a nice display of the past t-shirt campaigns by the HR area. Their internal marketing team seems to have gotten the memo about avoiding terrible bland t-shirts.
The day I visited, the Company was hosting a celebration in their outdoor area (which looked like it used to be the loading dock for the mall) for ranking #74 on the ‘Forbes Best companes to work for’ list. There was a whiteboard congratulating the Rackers and somebody had scrawled on “We’re #1, no matter what”.
Their enthusiasm was contagious :)


This site is using IMA.js
This site is not using IMA.js
Detecting presence of IMA.js...
Reload the page to take effect.


|
FloatingMeasure
class API for phyiscal calculations
|
a Singleton class for a generic SingletonObject More...
#include <Utils.h>
Public Member Functions | |
| virtual | ~CSingleton () |
| virtual destructor More... | |
Static Public Member Functions | |
| static SingletonObject * | instance () |
| allocates instance for member CSingleton< SingletonObject >::_instance More... | |
Protected Member Functions | |
| CSingleton () | |
| protected default constructor: avoids allocation like "SingletonObject MySingleton" More... | |
Static Private Attributes | |
| static SingletonObject * | _instance = nullptr |
| private "reflexive" pointer of SingletonObject: will be instantiated by CSingleton::instance() More... | |
a Singleton class for a generic SingletonObject
|
inlinevirtual |
|
inlineprotected |
|
inlinestatic |
allocates instance for member CSingleton< SingletonObject >::_instance
|
staticprivate |
private "reflexive" pointer of SingletonObject:
will be instantiated by CSingleton::instance()
global definition and initialization of CSingleton::_instance


I Need Help
Report Disaster
×
Close
Generate a help request
Name:
Emergency:
Contact Info:
Submit
×
Close
Generate a Danger report
Name
Type of danger
Submit