| java.lang.Object | ||
| ↳ | org.rrd4j.core.XmlTemplate | |
| ↳ | org.rrd4j.core.RrdDefTemplate |
Class used to create an arbitrary number of RrdDef
(RRD definition) objects
from a single XML template. XML template can be supplied as an XML InputSource,
XML file or XML formatted string.
Here is an example of a properly formatted XML template with all available options in it (unwanted options can be removed):
<rrd_def> <path>test.rrd</path> <!-- not mandatory --> <start>1000123456</start> <!-- not mandatory --> <step>300</step> <!-- at least one datasource must be supplied --> <datasource> <name>input</name> <type>COUNTER</type> <heartbeat>300</heartbeat> <min>0</min> <max>U</max> </datasource> <datasource> <name>temperature</name> <type>GAUGE</type> <heartbeat>400</heartbeat> <min>U</min> <max>1000</max> </datasource> <!-- at least one archive must be supplied --> <archive> <cf>AVERAGE</cf> <xff>0.5</xff> <steps>1</steps> <rows>600</rows> </archive> <archive> <cf>MAX</cf> <xff>0.6</xff> <steps>6</steps> <rows>7000</rows> </archive> </rrd_def>Notes on the template syntax:
RrdDef
class methods. If you are not sure what some XML tag means, check javadoc
for the corresponding class.
<some_tag>
and
</some_tag>
) can be replaced with
a variable of the following form: ${variable_name}
. Use
setVariable()
methods from the base class to replace template variables with real values
at runtime.Typical usage scenario:
<rrd_def> <path>${path}</path> <step>300</step> ...
RrdDefTemplate t = new RrdDefTemplate(new File(template.xml));
t.setVariable("path", "demo/test.rrd");
RrdDef def = t.getRrdDef(); RrdDb rrd = new RrdDb(def); rrd.close();
|
[Expand]
Inherited Fields | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
From class
org.rrd4j.core.XmlTemplate
|
| Public Constructors | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Creates RrdDefTemplate object from any parsable XML input source.
| |||||||||||
Creates RrdDefTemplate object from the string containing XML template.
| |||||||||||
Creates RrdDefTemplate object from the file containing XML template.
|
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Returns RrdDef object constructed from the underlying XML template.
|
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
From class
org.rrd4j.core.XmlTemplate
| |||||||||||
|
From class
java.lang.Object
|
Creates RrdDefTemplate object from any parsable XML input source. Read general information for this class to find an example of a properly formatted RrdDef XML source.
| xmlInputSource | Xml input source |
|---|
| IOException | Thrown in case of I/O error |
|---|---|
| IllegalArgumentException | Thrown in case of XML related error (parsing error, for example) |
Creates RrdDefTemplate object from the string containing XML template. Read general information for this class to see an example of a properly formatted XML source.
| xmlString | String containing XML template |
|---|
| IOException | Thrown in case of I/O error |
|---|---|
| IllegalArgumentException | Thrown in case of XML related error (parsing error, for example) |
Creates RrdDefTemplate object from the file containing XML template. Read general information for this class to see an example of a properly formatted XML source.
| xmlFile | File object representing file with XML template |
|---|
| IOException | Thrown in case of I/O error |
|---|---|
| IllegalArgumentException | Thrown in case of XML related error (parsing error, for example) |
Returns RrdDef object constructed from the underlying XML template. Before this method
is called, values for all non-optional placeholders must be supplied. To specify
placeholder values at runtime, use some of the overloaded
setVariable()
methods. Once this method
returns, all placeholder values are preserved. To remove them all, call inhereted
clearValues()
method explicitly.
| IllegalArgumentException | Thrown (in most cases) if the value for some placeholder
was not supplied through setVariable()
method call
|
|---|


- Shopping Cart
- Checkout
- Order Complete
Returning customer? Click here to login
YOUR ORDER
PRODUCT TOTAL
Rocha Sleeve Sweater x1 $140.00
Mauris Tincidunt x6 $140.00
CART SUBTOTAL $140.00
SHIPPING Free Shipping
ORDER TOTAL $140.00
PAYMENT METHODS
Make your payment directly into our bank account. Please use your cleared in our account.


Philosophy
Etuaptmumk: Two Eyed Seeing and Architecture
Written in conversation between Elder Dr. Albert Marshall and architect Richard Kroeker
From a Mi’kmaq perspective, language is fundamental to an understanding of place and plays an active role in how things in that place evolve over time. Understanding and expressing Mi’kmaq concepts requires an intimate knowledge of the language, and attempts to express them in English will always be approximate, with all the potential for inaccuracy and lack of nuance that creates. Mi’kmaq words express things in a dynamic and relational sense; verbs predominate over nouns. Things are not understood as discrete, bounded objects, but expressed in all their active, relational capacity. Built into the language and all ways of knowing is the sense that you avoid giving offense to nature. This is a core notion, guiding principle and overarching way of being.
In the Mi’kmaq world, there is no sense of otherness with regard to nature. The Mi’kmaq words “M’st no’Kmaq”(all my relations) is a direct expression of this. Our relations extend to all creatures and all aspects of nature. Language is employed within the context of collective consciousness. Through the focusing of the mind and framing of concepts, language transmits ideas and actively searches for connections across time and space. Built works begin with words, and so language plays a strong role in the formulation of all things.
The response of a building to its cultural context extends beyond graphic visual references. Form and the generative principles from which it arises are fundamental to architecture. In Mi’kmaq terms, form is related to purpose. It’s legibility and authenticity resides in its function. When efficiency is compromised, it is inevitably at a cost. This is the principle of doing more with less; conservation of material and energy is the objective. Meaningful forms emerge from natural processes. MI’kmaq ways of making and knowing have emerged over a long time in a unique environment. The Mi’kmaq word “netulimk” (provisioning) summarizes this principle: we are supported in all our needs by nature, without compromising our surroundings. The consideration of impacts over time extends to seven generations. Natural forms are analyzed and understood in those terms: as being generated by the principle of their suitability to purpose within their environment, shaped by their many relationships over time.
Historically, buildings in a Mi’kmaq cultural context needed to be efficiently assembled and disassembled by a system of articulated components and connections to respond to changing seasons, locations, and varying social situations. Some parts would be more permanent, remain in location while other parts were transported and regularly replaced. Form-giving forces aren’t external to the place and situation: they follow the internal logic of the locale, material, social dynamic, and anticipated impacts over time. Forms can give expression to the cultural significance of a building in terms of the level of articulation and craft employed in their making. The critical framework for assessing a building are rooted in how it performs, in its practicality within the context of its social purpose, and its long-term consequences for the rest of the natural environment.
Like all aspects of creation in the Mi’kmaq context, materials have an inherent animacy: a spiritual as well as a physical aspect. They contain embodied information and energy which can direct their transformation. As reflected in the language: things are regarded as being active, and defined by their active relationships. We exist in relationship to all other things and that relationship extends beyond an external sensory awareness to a spiritual connection. It is these relationships that give definition to things, not their presumed boundaries as objects.
The collection of material for fabrication is accompanied by a ceremony, as with the gathering of food or medicine. The ceremony is one of asking permission, an explanation of purpose, and an act of thanksgiving. In relationships, all partners have a reciprocal agency, and so it is understood that those materials, as they are transformed, in turn have a role in shaping us: how we feel, think and experience the world around us. This deep connection with the environment is maintained through close observation, through ceremony, through intuition, and through dreams.
An important aspect of Mi’kmaq thinking relevant to understanding form generation, is with regard to symbols, their use and meaning. While architects might concentrate on abstract symbols as easy points of identification or reference, from a Mi’kmaq perspective, symbols have meaning by virtue of the consequent actions they bring about. They exert a force that goes beyond being abstract points of association or memory devices. In Mi’kmaq thinking, symbols are understood as active, dynamic forces. The primary intent of symbols is to register and nurture connections within human society and with all of nature. Dakota elder Chris Leith, with whom we have both worked in Dakota territory, once pointed out that the true symbolic meaning of a flag, conventionally thought of as a signifier of nationality, territory, and patriotic allegiance, was in its potential for use as a blanket to nurture someone, to be wrapped around them for warmth and comfort. This example from Dakota culture also illustrates Mi’kmaq thinking about symbols.
The making of space is related to the making of form and the understanding of natural form. Once created, spaces have their own active energy. There is no empty space. When you enter a space, you enter into its energy. An important aspect of space creation is the avoidance of any hierarchies with regard to occupants. The absence of hierarchy is based in a profound sense of mutual respect. All participants in a space are aspects of the same whole to be treated with an equal respect rooted in compassion. Within Mi’kmaq consciousness, we are understood to derive our strength from the deepening of our connections with our natural context, including the human community, not through a perceived independence created by the isolation of constructed boundaries. All our powers as humans derive from the nurturing of relationships. The purpose of form and space making is not to fortify us against the rest of nature and society, but to enable and deepen the connection. Fostering a spirit of community is the overarching dynamic of space.
Consideration of the scale of a space is a matter of empowerment. One must consider how the scale of the space might avoid the alienation of the users of the space, through separation and isolation. All space making has an ethical dimension in that it must foster respect without reference to hierarchies. A space is a place of coming together of disparate cultures and viewpoints. The primary purpose of space becomes inclusion, not exclusion or separation. While spaces will vary to suit them to their purpose, they are not arranged for the purpose of ranking into lesser or greater spaces, or of “served and servant” spaces, as some architects sometimes refer to them. Light, colour, textures, acoustics, legibility, and relationships to other spaces give a space its active capacity. Spaces should accommodate many different occasions and be capable of adapting to the cycles of time.
The circle is the space of meeting and social interaction. Each member of a circle is an equal participant. The speaker or performer remains within the circle, and having begun to speak, is given the full time they require, without interruption. The option to speak passes around the circle to the next person, in a clockwise direction, until each viewpoint has been fully presented. In this way, many viewpoints are brought to the subject under discussion, and these can be expressed in a non-hierarchical setting based on mutual respect. This circular space of meeting, and the accompanying underlying ethos apply no matter what the outer shape of the enclosure in which it takes place.
Curved, circular forms are also made for their inherent structural stability, and for their efficiency in enclosing more useable area with less material than other plan geometries. Curved forms efficiently deflect the forces of wind and precipitation from all directions, distributing directional loads throughout the structure.
Spaces give the occupants a sense of presence and location. Spaces respond to direction, with each direction bringing its own forces to bear on the arrangement of spaces and the resulting form. The path of the sun, the winds, and views orient us within a space, and connect us to the other forces of nature.
This connection to the land and place is established and renewed through ceremonies, often involving music. Those with the ability to understand and gather medicines from the land often speak of the plants singing to them. The Mi’kmaq word for medicine, (“Medideskewey”) is the word which can be literally translated as “something which makes a sound”. If you are attuned to the land, the medicine you are seeking will address you. All medicine acts in this way. Just as we ask permission when collecting building materials, food, or medicines, permission is asked and thanks are offered for use of the land. An expression of deep appreciation engages the singing voice; singing connects to the spirit intrinsic to all things. Certain people are designated as keepers of the songs pertaining to particular places, occasions and events in a discernment process.
Mi’kmaqi consists of seven territories of distinct ecological zones. Leaving the territory in which one lives and entering another territory is done with consideration and with ceremony. The word “Kwe” is shouted to announce a crossing into new territory. There was traditionally a song corresponding to each particular territory. People are welcomed into new territory by being taught the song of that territory. This is another aspect of the concept of consonance with the land.
As with social relationships, relationships within all creation are viewed as non-hierarchical. Humans are not superior beings with respect to each other or to other beings in the natural world. Within the language, there is no sense of ownership or dominance over any aspect of nature. In a language where verbs predominate, there are many verb tenses enabling a subtle understanding and expression of the complex relationships within nature.
The things we make or build are considered a transformed aspect of nature. Built artefacts are not exclusively owned as the property of the maker, but remain as a part of nature at large, taking on their own power to be agents in enacting transformative relationships. Language provides the guiding energy for the initiation of ideas and for their emergence into forms.
Language provides the means for shaping and sharing knowledge. Knowledge is itself alive and dynamic. Transmitting knowledge has an aspect of gardening: when it is tended, it grows. Knowledge will seek and find the place where it is directed or attracted. Initiating the flow of knowledge begins with the framing of a question. The form of the question presents the vessel into which knowledge will flow. Changing the way in which a question is formulated opens new possibilities of learning.
There is no reference point that is outside nature, and so there is no sense of the otherness of nature. Language and knowledge are animate aspects of nature, and not a platform, frame or abstract scaffolding positioned outside nature. This all-encompassing nature is in its essence compassionate and nurturing. When there is disharmony, illness, or need, nature is the source of all remedies, summed up in the Mi’kmaq word “netulimk” . The Mi’kmaq language is oriented toward thankfulness and reverence to nature at all times in all things.
The power of language is in its ability to produce transformation. It gives rise to new forms and new dynamics. It has a direct power to heal, and is used with a consciousness of its power. If an idea comes about as result of an individual dream, vision, or insight, it is activated through language and must enter collective consciousness before coming to realization. It is understood as having emerged from a collective world of active knowledge, so there isn’t a sense of the “originality” or personal ownership of a vision or of ideas. No one owns an idea or has exclusive rights to it. It has emerged from the living body of knowledge that is a part of nature. It takes on its transformative power by being shared.
New ideas are assessed in terms of their effects or potential effects on human society and the rest of nature; the seven-generation time frame applies. The principle of maintaining harmony and attunement applies. For information to be alive and have currency, it must remain in circulation. It can’t be bottled up in a book or kept private amongst a few initiates. To encapsulate information in this way will cause it to stagnate, like a stagnant pool relative to a flowing river. Just as all things are alive, they also have the potential to communicate and partake in the flow of information. All are present in a vast network and flow of relationships.
The colonization experience, with the catastrophic effect on the population, its relentless suppression of all aspects of Mi’kmaq culture, and its polarization of world views, created a schism in architectural continuity. Patterns of living, access to land and resources, and the relationships with the environment changed rapidly and profoundly. The architecture of the colonists was based on European precedents. They aspired to match stylistic precedents from Europe, whose architecture was primarily one of stereotomic elements, the shaping and stacking of relatively massive components. Our academic histories traditionally often have focussed on attempts at architectural permanence. Anything that didn’t aspire to permanence was relegated to the fringes of academic architectural histories. In this tradition, architectural and artistic expressions are often understood as expressions of our individuality, and our spaces and cities are understood as defenses against nature based on the illusory notion that we can achieve independence from the very forces that formed us and nurture us.
Indigenous Mi’kmaq architecture, by contrast, was conscious of its position within the natural cycles.
Mi’kmaq building strategies are essentially tectonic. Building involved a system of often light-weight components and connections that allowed for a response to changing seasons and adapted to differing occasions in ways that created seamless continuity with the natural context. It consisted of articulated components and layers that allowed for mobility as well as adaptation to the seasons. Over time, the colonists found that their largely stereotomic architecture could not respond well to the North Eastern North American climate and material context, often owing more to stylistic preoccupations and an aesthetic agenda than to functionalism. Within this region, current main stream building practices, particularly in housing, have adopted the more Indigenous approach of using light wooden frames strengthened and insulated by the addition of layers, in a composite strategy that responds to available resource, climate, and can accommodate a variety of social and cultural uses.
Like dwellings, canoes were built with an overall understanding of material, connection and information flow. They were lightweight, durable, and efficient. Information required to shape canoes, as well as other structures, did not traditionally require drawings, but is inherent in the construction process itself, where one step becomes the template for the next. As with dwellings, the overall form of the canoe, and its detailed connections respond to the context in which canoe will be used: whether ocean waves, fast streams, windy open lake conditions, or small streams overhung with trees. Regional formal variations are often classified as expressions of culture, but to understand them completely, they need to be analyzed in the context of their response to their material environments, and the functional requirements related to the dynamic context and uses to which they are put within that context.
In any construction project, defined roles were traditionally given to women and to men, for the purpose of ensuring that both male and female energies have a presence in the project, during the work process and in its realization. These are general strategies which involved an understanding of material properties, special connections, and an understanding of both embodied energy and continuing energy needs. The use of thermal mass, attention to air quality, seasonal adaptability, social adaptability, material properties, and life cycle environmental impacts were well understood as the drivers of decisions regarding the form.
In the context of the United Nations Declaration of the Rights of Indigenous People (https://www.un.org/development/desa/indigenouspeoples/declaration-on-the-rights-of-indigenous-peoples.html), officially endorsed by the Canadian Government in May of 2016, represents an appropriate advance in the continuing process of decolonization. Architecture is a major expression of how a society sees itself in relation to surrounding nature and to other societies. There must be an acknowledgement of this in the processes by which buildings are designed, procured and implemented within Indigenous territories.
The dominant contemporary reading of architecture as a cultural practice takes place within an assumed technological context, often regarded as separate from the natural realm. Indigenous approaches can teach us that responding to defined functional and environmental issues can lead to designs that are appropriate, and authentic cultural expressions. Buildings derive their identity and authenticity from the direct, articulated dynamics which shaped them, and an understanding of how they act upon us and the environments in which they exist.
“European based” Science aspires to objectivity, tending to abstract and obscure the human element into issues of economics or politics. Use of the concept of objectivity easily becomes a means to privilege the interests of power elites. Architecture is directly engaged with political and economic processes, often put forward as objective issues. Two Eyed Seeing offers another awareness that puts these charged issues into a more appropriate framework. clarifying to whose benefits the purportedly “objective” issues directing procurement processes, are directed Architecture is always a collective endeavour. In producing architecture, there needs to be an honest assessment of where the economic benefits reside in the procurement processes, and funding structures. Architects are the technicians who are charged with realizing a collective vision. Included is an advocacy for human values including advocacy for nature which gave birth to us and sustains us. The Mi’kmaq perspective grounds architectural practice and critique firmly in the immediate, present reality of ethics and in authenticity. It will lead to original work unique to this place by connecting to our origins: our deep history.
Two Eyed Seeing can move us beyond perceiving ourselves as outside observers from a superior vantage point in a set of hierarchical relationships. It offers a means of communicating between ways of knowing and perceiving in a place of mutual respect.


public class SerialVersionUIDAdder extends ClassVisitor
ClassVisitor
that adds a serial version unique identifier to a
class if missing. Here is typical usage of this class:
ClassWriter cw = new ClassWriter(...); ClassVisitor sv = new SerialVersionUIDAdder(cw); ClassVisitor ca = new MyClassAdapter(sv); new ClassReader(orginalClass).accept(ca, false);The SVUID algorithm can be found http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/class.html:
The serialVersionUID is computed using the signature of a stream of bytes that reflect the class definition. The National Institute of Standards and Technology (NIST) Secure Hash Algorithm (SHA-1) is used to compute a signature for the stream. The first two 32-bit quantities are used to form a 64-bit hash. A java.lang.DataOutputStream is used to convert primitive data types to a sequence of bytes. The values input to the stream are defined by the Java Virtual Machine (VM) specification for classes. The sequence of items in the stream is as follows: 1. The class name written using UTF encoding. 2. The class modifiers written as a 32-bit integer. 3. The name of each interface sorted by name written using UTF encoding. 4. For each field of the class sorted by field name (except private static and private transient fields): 1. The name of the field in UTF encoding. 2. The modifiers of the field written as a 32-bit integer. 3. The descriptor of the field in UTF encoding 5. If a class initializer exists, write out the following: 1. The name of the method, <clinit>, in UTF encoding. 2. The modifier of the method, java.lang.reflect.Modifier.STATIC, written as a 32-bit integer. 3. The descriptor of the method, ()V, in UTF encoding. 6. For each non-private constructor sorted by method name and signature: 1. The name of the method, <init>, in UTF encoding. 2. The modifiers of the method written as a 32-bit integer. 3. The descriptor of the method in UTF encoding. 7. For each non-private method sorted by method name and signature: 1. The name of the method in UTF encoding. 2. The modifiers of the method written as a 32-bit integer. 3. The descriptor of the method in UTF encoding. 8. The SHA-1 algorithm is executed on the stream of bytes produced by DataOutputStream and produces five 32-bit values sha[0..4]. 9. The hash value is assembled from the first and second 32-bit values of the SHA-1 message digest. If the result of the message digest, the five 32-bit words H0 H1 H2 H3 H4, is in an array of five int values named sha, the hash value would be computed as follows: long hash = ((sha[0] >>> 24) & 0xFF) | ((sha[0] >>> 16) & 0xFF) << 8 | ((sha[0] >>> 8) & 0xFF) << 16 | ((sha[0] >>> 0) & 0xFF) << 24 | ((sha[1] >>> 24) & 0xFF) << 32 | ((sha[1] >>> 16) & 0xFF) << 40 | ((sha[1] >>> 8) & 0xFF) << 48 | ((sha[1] >>> 0) & 0xFF) << 56;
| Modifier and Type | Class and Description |
|---|---|
private static class |
SerialVersionUIDAdder.Item |
| Modifier and Type | Field and Description |
|---|---|
private int |
access
Classes access flags.
|
private boolean |
computeSVUID
Flag that indicates if we need to compute SVUID.
|
private boolean |
hasStaticInitializer
Set to true if the class has static initializer.
|
private boolean |
hasSVUID
Set to true if the class already has SVUID.
|
private java.lang.String[] |
interfaces
Interfaces implemented by the class.
|
private java.lang.String |
name
Internal name of the class
|
private java.util.Collection<SerialVersionUIDAdder.Item> |
svuidConstructors
Collection of non-private constructors.
|
private java.util.Collection<SerialVersionUIDAdder.Item> |
svuidFields
Collection of fields.
|
private java.util.Collection<SerialVersionUIDAdder.Item> |
svuidMethods
Collection of non-private methods.
|
api, cv
| Modifier | Constructor and Description |
|---|---|
|
SerialVersionUIDAdder(ClassVisitor cv)
Creates a new
SerialVersionUIDAdder . |
protected |
SerialVersionUIDAdder(int api,
ClassVisitor cv)
Creates a new
SerialVersionUIDAdder . |
| Modifier and Type | Method and Description |
|---|---|
protected void |
addSVUID(long svuid) |
protected byte[] |
computeSHAdigest(byte[] value)
Returns the SHA-1 message digest of the given value.
|
protected long |
computeSVUID()
Computes and returns the value of SVUID.
|
boolean |
hasSVUID()
Returns true if the class already has a SVUID field.
|
void |
visit(int version,
int access,
java.lang.String name,
java.lang.String signature,
java.lang.String superName,
java.lang.String[] interfaces)
Visits the header of the class.
|
void |
visitEnd()
Visits the end of the class.
|
FieldVisitor |
visitField(int access,
java.lang.String name,
java.lang.String desc,
java.lang.String signature,
java.lang.Object value)
Visits a field of the class.
|
void |
visitInnerClass(java.lang.String aname,
java.lang.String outerName,
java.lang.String innerName,
int attr_access)
Handle a bizarre special case.
|
MethodVisitor |
visitMethod(int access,
java.lang.String name,
java.lang.String desc,
java.lang.String signature,
java.lang.String[] exceptions)
Visits a method of the class.
|
private static void |
writeItems(java.util.Collection<SerialVersionUIDAdder.Item> itemCollection,
java.io.DataOutput dos,
boolean dotted)
Sorts the items in the collection and writes it to the data output stream
|
visitAnnotation, visitAttribute, visitOuterClass, visitSource
private boolean computeSVUID
private boolean hasSVUID
private int access
private java.lang.String name
private java.lang.String[] interfaces
private java.util.Collection<SerialVersionUIDAdder.Item> svuidFields
private boolean hasStaticInitializer
private java.util.Collection<SerialVersionUIDAdder.Item> svuidConstructors
private java.util.Collection<SerialVersionUIDAdder.Item> svuidMethods
public SerialVersionUIDAdder(ClassVisitor cv)
SerialVersionUIDAdder
. Subclasses must not use
this constructor. Instead, they must use the
SerialVersionUIDAdder(int, ClassVisitor)
version.cv
- a ClassVisitor
to which this visitor will delegate
calls.protected SerialVersionUIDAdder(int api, ClassVisitor cv)
SerialVersionUIDAdder
.api
- the ASM API version implemented by this visitor. Must be one
of Opcodes.ASM4
.cv
- a ClassVisitor
to which this visitor will delegate
calls.public void visit(int version, int access, java.lang.String name, java.lang.String signature, java.lang.String superName, java.lang.String[] interfaces)
ClassVisitor
visit
in class ClassVisitor
version
- the class version.access
- the class's access flags (see Opcodes
). This parameter
also indicates if the class is deprecated.name
- the internal name of the class (see
getInternalName
).signature
- the signature of this class. May be null if the class
is not a generic one, and does not extend or implement generic
classes or interfaces.superName
- the internal of name of the super class (see
getInternalName
). For
interfaces, the super class is Object
. May be
null, but only for the Object
class.interfaces
- the internal names of the class's interfaces (see
getInternalName
). May be
null.public MethodVisitor visitMethod(int access, java.lang.String name, java.lang.String desc, java.lang.String signature, java.lang.String[] exceptions)
ClassVisitor
MethodVisitor
instance (or null) each time it is called,
i.e., it should not return a previously returned visitor.visitMethod
in class ClassVisitor
access
- the method's access flags (see Opcodes
). This
parameter also indicates if the method is synthetic and/or
deprecated.name
- the method's name.desc
- the method's descriptor (see Type
).signature
- the method's signature. May be null if the method
parameters, return type and exceptions do not use generic
types.exceptions
- the internal names of the method's exception classes (see
getInternalName
). May be
null.public FieldVisitor visitField(int access, java.lang.String name, java.lang.String desc, java.lang.String signature, java.lang.Object value)
ClassVisitor
visitField
in class ClassVisitor
access
- the field's access flags (see Opcodes
). This parameter
also indicates if the field is synthetic and/or deprecated.name
- the field's name.desc
- the field's descriptor (see Type
).signature
- the field's signature. May be null if the field's
type does not use generic types.value
- the field's initial value. This parameter, which may be
null if the field does not have an initial value,
must be an Integer
, a Float
, a Long
, a
Double
or a String
(for int,
float, long or String fields
respectively). This parameter is only used for static
fields. Its value is ignored for non static fields, which
must be initialized through bytecode instructions in
constructors or methods.public void visitInnerClass(java.lang.String aname, java.lang.String outerName, java.lang.String innerName, int attr_access)
visitInnerClass
in class ClassVisitor
aname
- the internal name of an inner class (see
getInternalName
).outerName
- the internal name of the class to which the inner class
belongs (see getInternalName
).
May be null for not member classes.innerName
- the (simple) name of the inner class inside its enclosing
class. May be null for anonymous inner classes.attr_access
- the access flags of the inner class as originally declared in
the enclosing class.public void visitEnd()
ClassVisitor
visitEnd
in class ClassVisitor
public boolean hasSVUID()
protected void addSVUID(long svuid)
protected long computeSVUID() throws java.io.IOException
java.io.IOException
- if an I/O error occursprotected byte[] computeSHAdigest(byte[] value)
value
- the value whose SHA message digest must be computed.private static void writeItems(java.util.Collection<SerialVersionUIDAdder.Item> itemCollection, java.io.DataOutput dos, boolean dotted) throws java.io.IOException
itemCollection
- collection of itemsdos
- a DataOutputStream
valuedotted
- a boolean
valuejava.io.IOException
- if an error occurs


~(studentname)
This student is 18+ and has requested to be the primary reciepent of all contact, mailings, and reports regarding his/her progress.


This tests that edited whitespaces aren't all nbsps. When the region becomes non-editable, Hello and World should still be on different lines. This demonstrates a bug: the div's focus halo doesn't go away when it becomes non-editable.


| OLD line(s): 268
<xsd:attribute name="codeSection"> | NEW line(s): 268
<xsd:attribute name="codeSectionTxt"> |
| OLD line(s): 335
<xsd:attribute name="description"> | NEW line(s): 335
<xsd:attribute name="desc"> |
| OLD line(s): 389
<xsd:attribute name="description"> | NEW line(s): 389
<xsd:attribute name="desc"> |
| OLD line(s): 435
<xsd:attribute name="description"> | NEW line(s): 435
<xsd:attribute name="methodOfAccountingOtherDesc"> |
| OLD line(s): 1097
<xsd:attribute name="increaseOrDecreaseIndicator"> | NEW line(s): 1097
<xsd:attribute name="increaseOrDecreaseCd"> |


In POSIX sh, standalone ((..)) is undefined.
variable=1
if ((variable)); then
echo variable is not zero
fi
bash
supports standalone ((..))
natively.
For POSIX compliance, use
variable=1
if [ "${variable}" -ne 0 ]; then
echo variable is not zero
fi


The CSS border properties allow you to specify the style, width, and color of an element's border.
This element has a groove border that is 15px wide and green.
The border-style
property specifies what kind of border to display.
The following values are allowed:
dotted
- Defines a dotted borderdashed
- Defines a dashed bordersolid
- Defines a solid borderdouble
- Defines a double bordergroove
- Defines a 3D grooved border. The effect depends on the border-color valueridge
- Defines a 3D ridged border. The effect depends on the border-color valueinset
- Defines a 3D inset border. The effect depends on the border-color valueoutset
- Defines a 3D outset border. The effect depends on the border-color valuenone
- Defines no borderhidden
- Defines a hidden border
The border-style
property can have from one to four values (for the top border, right border, bottom border, and the left border).
p.dotted {border-style: dotted;}
p.dashed {border-style: dashed;}
p.solid {border-style: solid;}
p.double {border-style: double;}
p.groove {border-style: groove;}
p.ridge {border-style: ridge;}
p.inset {border-style: inset;}
p.outset {border-style: outset;}
p.none {border-style: none;}
p.hidden {border-style: hidden;}
p.mix {border-style: dotted dashed solid double;}
Result:
A dotted border.
A dashed border.
A solid border.
A double border.
A groove border. The effect depends on the border-color value.
A ridge border. The effect depends on the border-color value.
An inset border. The effect depends on the border-color value.
An outset border. The effect depends on the border-color value.
No border.
A mixed border.
Note: None of the OTHER CSS border properties described below will have ANY effect unless the border-style property is set! |
The border-width
property specifies the width of the four borders.
The width can be set as a specific size (in px, pt, cm, em, etc) or by using one of the three pre-defined values: thin, medium, or thick.
The border-width
property can have from one to four values (for the top border, right border, bottom border, and the left border).
p.one {
border-style: solid;
border-width: 5px;
}
p.two {
border-style: solid;
border-width: medium;
}
p.three {
border-style: solid;
border-width: 2px 10px 4px 20px;
}
The border-color
property is used to set the color of the four borders.
The color can be set by:
The border-color
property can have from one to four values (for the top border, right border, bottom border, and the left border).
If border-color
is not set, it inherits the color of the element.
p.one {
border-style: solid;
border-color: red;
}
p.two {
border-style: solid;
border-color: green;
}
p.three {
border-style: solid;
border-color: red green blue yellow;
}
From the examples above you have seen that it is possible to specify a different border for each side.
In CSS, there is also properties for specifying each of the borders (top, right, bottom, and left):
p {
border-top-style: dotted;
border-right-style: solid;
border-bottom-style: dotted;
border-left-style: solid;
}
The example above gives the same result as this:
p {
border-style: dotted solid;
}
So, here is how it works:
If the border-style
property has four values:
If the border-style
property has three values:
If the border-style
property has two values:
If the border-style
property has one value:
The border-style
property is used in the example above. However, it also works with border-width
and border-color
.
As you can see from the examples above, there are many properties to consider when dealing with borders.
To shorten the code, it is also possible to specify all the individual border properties in one property.
The border
property is a shorthand property for the following individual border properties:
border-width
border-style
(required)border-color
p {
border: 5px solid red;
}


|
|
|||||||||||
| PREV NEXT | FRAMES NO FRAMES |
| Packages that use org.javasimon | |
|---|---|
| org.javasimon | Core package, contains Simon implementations, with
the SimonManager as the center point of the API. |
| org.javasimon.callback | Callback is an event listener registered with the Manager ,
listening for manager or Simon events. |
| org.javasimon.callback.calltree | CallTreeCallback gathers information
for current thread and displays it subsequent calls like a tree. |
| org.javasimon.callback.lastsplits | LastSplitsCallback retains last
splits in a ring a buffer (fixed size FIFO queue). |
| org.javasimon.callback.logging | LoggingCallback is able to log stopwatch splits and statistics once
in a while (N per millisecond, every N split, when split is longer than N ms, etc.) |
| org.javasimon.callback.quantiles | QuantilesCallback sorts splits to categories
(Bucket s) based on time ranges. |
| org.javasimon.callback.timeline | |
| org.javasimon.console | Java Simon embeddable Web console base package. |
| org.javasimon.console.action | All controllers (aka Action beans in Struts world) are located in this package. |
| org.javasimon.console.html | HTML generation helper classes. |
| org.javasimon.console.plugin | |
| org.javasimon.javaee | Java EE support for Simons contains Java EE components (servlet filter and EJB/CDI interceptor) that can be used or extended. |
| org.javasimon.javaee.reqreporter | Package contains classes reporting slow HTTP requests - interface RequestReporter and various (default) implementations. |
| org.javasimon.jdbc4 | Simon JDBC Proxy Driver for monitoring JDBC drivers through the Java Simon API. |
| org.javasimon.jdbc4.jmx | Work in progress: MX beans specific to Simon JDBC driver. |
| org.javasimon.jmx | JMX capabilities for Simons. |
| org.javasimon.proxy | Provides everything to wrap any class a Proxy generated with java.lang.reflect. |
| org.javasimon.source | MonitorSource is the interface used as function to transform execution context (method invocation,
HTTP request...) into a Simon. |
| org.javasimon.spring | Support classes to automatically monitor Spring beans with the Monitored annotation. |
| org.javasimon.spring.webmvc | MonitoringHandlerInterceptor is a Spring MVC interceptor which can be used to monitor
time spent in Controller and View. |
| org.javasimon.utils | Java Simon supporting utilities and tools. |
| Classes in org.javasimon used by org.javasimon | |
|---|---|
| Counter
Counter tracks the single integer value and watches its max/min values. |
|
| CounterSample
Object holds all relevant data from Counter Simon. |
|
| HasAttributes
Interface that declares support for arbitrary attributes that can be attached to the object (servlet style). |
|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| ManagerConfiguration
Holds configuration for one Simon Manager. |
|
| Sample
Sample contains all relevant values of the Simon that are obtained by the Simon.sample() and Simon.sampleIncrement(Object) methods. |
|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| SimonFilter
Generic filter useful whenever Simons are filtered for some operation. |
|
| SimonPattern
Matches Simon name patterns from configuration. |
|
| SimonState
Status of monitor. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.callback | |
|---|---|
| Counter
Counter tracks the single integer value and watches its max/min values. |
|
| CounterSample
Object holds all relevant data from Counter Simon. |
|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| SimonPattern
Matches Simon name patterns from configuration. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.callback.calltree | |
|---|---|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.callback.lastsplits | |
|---|---|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.callback.logging | |
|---|---|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.callback.quantiles | |
|---|---|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.callback.timeline | |
|---|---|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.console | |
|---|---|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| Sample
Sample contains all relevant values of the Simon that are obtained by the Simon.sample() and Simon.sampleIncrement(Object) methods. |
|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
| Classes in org.javasimon used by org.javasimon.console.action | |
|---|---|
| Sample
Sample contains all relevant values of the Simon that are obtained by the Simon.sample() and Simon.sampleIncrement(Object) methods. |
|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
| Classes in org.javasimon used by org.javasimon.console.html | |
|---|---|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
| Classes in org.javasimon used by org.javasimon.console.plugin | |
|---|---|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
| Classes in org.javasimon used by org.javasimon.javaee | |
|---|---|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
| Classes in org.javasimon used by org.javasimon.javaee.reqreporter | |
|---|---|
| Split
Represents single time split - one Stopwatch measurement. |
| Classes in org.javasimon used by org.javasimon.jdbc4 | |
|---|---|
| Split
Represents single time split - one Stopwatch measurement. |
| Classes in org.javasimon used by org.javasimon.jdbc4.jmx | |
|---|---|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
| Classes in org.javasimon used by org.javasimon.jmx | |
|---|---|
| Counter
Counter tracks the single integer value and watches its max/min values. |
|
| CounterSample
Object holds all relevant data from Counter Simon. |
|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| Sample
Sample contains all relevant values of the Simon that are obtained by the Simon.sample() and Simon.sampleIncrement(Object) methods. |
|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
| Classes in org.javasimon used by org.javasimon.proxy | |
|---|---|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
| Classes in org.javasimon used by org.javasimon.source | |
|---|---|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
| Classes in org.javasimon used by org.javasimon.spring | |
|---|---|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| Split
Represents single time split - one Stopwatch measurement. |
| Classes in org.javasimon used by org.javasimon.spring.webmvc | |
|---|---|
| Manager
Manager provides access to Simons and manages them in a tree structure. |
|
| Split
Represents single time split - one Stopwatch measurement. |
| Classes in org.javasimon used by org.javasimon.utils | |
|---|---|
| Counter
Counter tracks the single integer value and watches its max/min values. |
|
| CounterSample
Object holds all relevant data from Counter Simon. |
|
| Sample
Sample contains all relevant values of the Simon that are obtained by the Simon.sample() and Simon.sampleIncrement(Object) methods. |
|
| Simon
Simon interface contains common functions related to Simon management - enable/disable and hierarchy. |
|
| SimonFilter
Generic filter useful whenever Simons are filtered for some operation. |
|
| Split
Represents single time split - one Stopwatch measurement. |
|
| Stopwatch
Stopwatch Simon measures time spans and holds related statistics. |
|
| StopwatchSample
Object holds all relevant data from Stopwatch Simon. |
|
|
|||||||||||
| PREV NEXT | FRAMES NO FRAMES |


Ann Cook Turner, the original Gerber baby, celebrates 93rd birthday
by Johari CantyTAMPA, FLA. (WSVN) - The original Gerber baby is celebrating her 93rd birthday.
Tampa resident Ann Turner Cook was the model for the sketch now used for the Gerber logo.
“I was a happy, healthy baby, and I think that’s why the drawing has been so appealing to people,” Cook told Fox 13 in 2013, “because everybody wants their baby to be happy, healthy looking.”
Cook was born on Nov. 20, 1926, and according to Gerber, was a 4-month-old baby at the time her neighbor, Dorothy Hope Smith, used her likeness for the sketch.
The sketch was then entered into the running to be used on Gerber products, and since then, her baby picture has become one of the most recognizable faces in popular culture.
According to Gerber, Cook went on to become an English teacher and later a mystery novelist. Fox 13 also reported that she had four children, and she now has great-grandchildren.
“That’s my immortality, yes,” she laughed. “I’ve become a symbol for babies, which couldn’t be anything nicer than that.”
Last year, Cook met then-Gerber baby Lucas. Lucas was the first Gerber baby to have Down syndrome.


My Green Thumb
Home
Indoor Plants
(current)
Flowers
Succulent
40% off
Grows only indoors. 39 SEK
Buy
Large Plant
Grows only indoors. 99 SEK.
Buy
Succulent
×
Very low maintainance plants. Perfect for indoors. Minimum water and sunlight is needed.
Large plant
×
Very low maintainance plants. Perfect for indoors. Minimum water and sunlight is needed.


My Family Tree
Me :
Male
Female
Choose file
Parent :
Male
Female
1.
Choose file
Spouse :
Male
Female
Choose file
Children :
Male
Female
1.
Choose file
Next


Hey guys and girls!
After reading a lot on the forum here i bit the bullet and signed up! I have a question for you!
I will describe what i have at this moment. I made a diy board which i can connect to four sct sensors. I can read this with my Arduino nano on four analog inputs. Then I wanted to put this on my nodemcu so i can send these current readings to emoncms. Ofcourse that board only has one analog input and i need to use a ADS to get more analog inputs with I2C.
I have the ADS1115 and i can read the voltage from the current sensors very good. But I want to implement the readings from the ads directly into the emonlib library. I tried to edit the emonlib.ccp file and changed the:
startV = analogRead(inPinV); to startV = ads1115.readADC_SingleEnded(inPinV);
And in the sketch I used emon1.current(0, 30); to create an instance that directs to the right pin.
This is where my mind gets puzzeled. How can i load the library of the ADS into the emoblib library?
If someone wants to point me in the right direction - maybe with an example?
Thanks!
Re: Emonlib and ADS1115 on nodemcu
Afraid I don't have a solution, but I was planning on doing the same. So if you do get a resolution, I'd be interested to see the code.
Simon
Re: Emonlib and ADS1115 on nodemcu
I haven't got time to search out the ADS library, if you tell me where it is, I might find time to look for you. I'm guessing that it does the I2C stuff for you, but remember that in emonLib, the pin is read in more places than just that. And you'll need to drive the multiplexer.
But one concern: although the 16 bits resolution might appeal to you, note that you'll only get a maximum of 17.2 samples per cycle from which to calculate the rms value, and that's using a single channel. If you switch channels to read voltage and current alternately, you'll get less than 8.6 sample pairs per cycle. (Meaning you'll only measure the fundamental 50 Hz and the third harmonic at 150 Hz - anything above will alias badly. That'll be more-or-less OK for voltage and nice resistive loads, anything that draws a distorted current waveform will be seriously in error). I don't think that's a good trade-off against 16 bits resolution.
Re: Emonlib and ADS1115 on nodemcu
Hi Robert. The 1015 does up to 3.3k samples per second, so would be a better choice. I had a look at that ADS library, which seems to be from adafruit, but wasn't impressed. It's been a while since I last looked, but I think you'd need to make some changes to get things running in continuous mode. I think it was OK for single shot mode.
I'm hoping to get back to this some time soon.
Simon.
Re: Emonlib and ADS1115 on nodemcu
If you aren't using all the functions of emonLib, I'd almost suggest you should lift the appropriate sections out and paste them directly into your sketch.
Having had a very quick look, it would appear that you must (obviously) connect the device using the I2C bus, then assuming you've defined an instance with Adafruit_ADS1015 ads, in your sketch's setup() you must initialise the library with ads.begin(), then you need to pick out the bits of emonLib you'll be using, and for all instances change analogRead(inPinV) and analogRead(inPinI) to become ads.readADC_SingleEnded(0) and ads.readADC_SingleEnded(1) respectively - that's reading voltage and CT1 for an emonTx V3.
If you're thinking of adding it to one of the 'continuous' sketches, then life gets very interesting and I'd suggest for speed that you do the getting of the input samples that is in the ISR using the register calls extracted from the ADAfruit library to drive the I2C bus registers directly. In principle, you're still doing the same thing as the original (OEM) code, but you're addressing the external multiplexer and ADC via the bus instead of addressing the internal multiplexer and ADC directly.
If you want to change the gain "on the fly" if say the current is low, you probably need to set a fairly wide band and logic goes like "if the rms current is below 10%, change gain one step up" then "if the rms current is above 80%, change gain one step down" so that there's minimal chance of the gain change putting the new measure anywhere near the other switching point, thus preventing the gain switching continually between two adjacent values.


| GSSvocab {carData} | R Documentation |
This data set illustrates analyis of a multifactor observational study, with response given by subject's score on a vocabulary test, and factors for age group, education level, natality status, gender and year of the survey.
data("GSSvocab")
A data frame with 28867 observations on the following 8 variables.
year
a factor with levels 1978
1982
1984
1987
1988
1989
1990
1991
1993
1994
1996
1998
2000
2004
2006
2008
2010
2012
2014
2016
. Data are included from the GSS for each of these years.
gender
a factor with levels female
male
nativeBorn
Was the respondent born in the US? A factor with levels no
and yes
.
ageGroup
a factor with levels 18-29
30-39
40-49
50-59
60+
, grouped age of the respondent.
educGroup
a factor with levels <12 yrs
12 yrs
13-15 yrs
16 yrs
>16 yrs
, grouped education level of the respondent. 12 years corresponds to high school graduate, 16 years to college graduate.
vocab
Number of words out of 10 correct on a vocabulary test
age
age of the respondent in years
educ
years of education of the respondent
This file includes the years of the GSS for which the vocab
and nativeBorn
items were included.
These data were collected from the GSS data explorer https://gssdataexplorer.norc.org, using the data fields year
, id_
, age
, educ
, sex
, born
and wordsum
. The GSS began in 1972, and has included several thousand data items, some regularly and some only once, on topics of interest to social scientists. Data have been slightly edited to change entires like No answer
and Not applicable
to missing value codes.
data(GSSvocab)


---
layout: page
---
I also happen to consult for startups, on technology. I've always felt that technology is one area where a lot of startups
actually are unable to find great advice or a friendly word, as they could if it were sales or marketing, the like. Sometimes,
you just need to pick someone's brains, or get some code spun up real quick, by someone who knows what he's doing.
Well. That could be me! I specialize in web app engineering as well as cloud infrasutructure management. I've had a fair bit
of experience with mobile apps and mobile backends, although I prefer hybrid approaches using newer tech. I also am a bit of
a mathematician and data scientist, which means I can help you make sense of your data. Couple that with over 4 years of
experience working across different companies and startups on their tech, and you have a win on your hands.
I'm quite at home with Python, Ruby and Javascript. I've worked extensively on Flask, Rails and Express. I love Postgres, but
MongoDB and RethinkDB are my favorites too. To that, add computational math and statistics using Python, R or Julia. However, if
you work on, say Haskell, then I'd love to give it a shot.
Should you be interested in hiring my consulting know-how, click here.


CrimPapers
Articles published on 5 March 2018
On 5 March 2018, 7 new articles were published in 6 journals.
The Role of “Problematic” and “Improved” Indicators of Risky Lifestyles in the Self-Control/lifestyle Framework of Victimization Among Filipino Adolescents
Police Officers’ Perceptions of Statement Inconsistency by Haneen Deeb, Aldert Vrij, Lorraine Hope, Samantha Mann, Pär Anders Granhag, Leif A. Strömwall
The Murder Epidemic: A Global Comparative Study by Simplice A. Asongu, Paul N. Acha-Anyi
Impacts of the School Context on Victimization in A Sample of Chinese Adolescents: A Multilevel Approach by Ruohui Zhao
Understanding the Link Between Discrimination and Juvenile Delinquency Among Chinese Migrant Children by Spencer D. Li, Yiwei Xia
Community Interpreters’ Experiences of Police Investigative Interviews: How Might Interpreters’ Insights Contribute to Enhanced Procedural Justice? by Loene M. Howes
Differentiating Adults With Mixed Age Victims From Those Who Exclusively Sexually Assault Children Or Adults by Jenna Rice, Raymond A. Knight


Concept
Transport Analyst enables the measurement of access to spatially distributed variables (people, jobs, schools, etc.) via public transport, walking, biking or driving. Common applications include measuring access to jobs, workforce, or key locations as an indicator of transport effectiveness. Indicators can be combined to create composite regional measures, such as a population-weighted average job access for a neighborhood or an entire city.
The application does not prescribe specific research questions. It accepts data in standard Shapefile (spatial) and GTFS (public transport) formats. Users may import and analyze any data set matching these formats.
Before continuing this tutorial be sure to login or create an account using the links above. You can jump directly to sections of the application using the links embedded in this tutorial. The demo data for Mexico City, included by default in your account, is read-only. To experiment with creating new data sets, create new a project.
Data management
Shapefiles
Shapefiles provide the basis for all measurements within Transport Analyst. Upload spatial variables either as a point or thematic data set. The numeric attributes within the data set can be summed as part of the accessibility measure (e.g. total job access from location x).
Use the Shapefile data manager, found under the "Data" menu, to upload new Shapefiles and enter easily read names and descriptions of the data set and attributes. You can also select a color for different attributes and visualize as a map overlay.
Before uploading a Shapefile be sure the file is in a common projection and datum (e.g. WGS84 or UTM) and zip the entire collection of files, including the .prj projection metadata, into a single zip archive. Upload only the zipped collection of files.
Transport Data
Public transport routes and schedules are imported from GTFS data sets using the Transport Data interface under the "Data" menu. Simply upload a valid, zipped GTFS archive and Transport Analyst will automatically create a transport model for the area included in the feed. You can view the routes in the GTFS data set by clicking the "eye" button in the feed listing.
Create as many different transport scenarios as you wish. Each scenario can be analyzed separately or compared against the others to measure accessibility impact of different transport systems, either existing or hypothetical.
When uploading GTFS data you either create a new layer containing only the data uploaded or augment an existing layer.
Creating GTFS
If GTFS is not already available an approximate transit network and schedule can be derived from a GIS data set containing route alignments and, optionally, stop locations. Export the GIS layer as a Shapefile, and zip it as before. Include a small metadata file in the zipped Shapefile. This metadata defines critical information about timing and speed. For more information on the metadata files see the documentation for geom2GTFS.
Alternatively you can use GTFS Editor, a web-based visual tool for creating and maintaining transit schedules.
OpenStreetMap
Data for pedestrians, bicycles and cars is imported directly from OpenStreetMap. To make corrections or updates visit the OSM website to learn more. Note that OSM data does not contain reliable speed information. By default Transport Analyst uses free-flow travel speeds for North American roadway classifications. To accurately model car travel speeds, data must be incorporated from a third-party source (e.g. roadway loop detectors or a regional traffic model). This data does not exist in a standard format and at present must be manually imported.
Accessibility Analysis
Single-point Analysis
The basis for all analysis in Transport Analyst is the access to or from a given point location (or origin) as a measure or what can be reached in a given time window. Single-origin analysis can be conducted by selecting the variable to measure (e.g. jobs) and clicking on the map to define a start location. A travel time and access plot is created showing the distribution of travel times to the selected location and variable.
Settings allow selection of the transport scenario, travel mode, date, time window, and variable to measure accessibility to. Travel times are reported as best case, worst case or average for the given time window. This data can be exported as a Shapefile or a tabular data set for use in external analysis applications.
Regional Analysis
Regional Analysis functions allow the automation of many single-point queries, one from each potential origin location (for example, every Census block). Once computed, regional analysis outputs show variation in travel accessibility for potential users at any location within the study area. Due to the number of queries involved these may take from minutes to hours to compute.
Aggregation and Bertaud Measure
Once analysis has been conducted at a regional scale it often makes sense to aggregate data to a larger spatial unit. For example, job access at a block-level might be aggregated to a neighborhood or even city scale.
For example, one useful and easily calculated measure is defined in Alain Bertaud's paper Cities as Labor Markets. This measures the average number of jobs that can be accessed within 60 minutes weighted by population. This enables fine-grain calculation of job access at a block level to be summed and converted to an average metric of access at a municipal scale.
To create the Bertaud measure, first calculate regional job access at the smallest spatial resolution possible (e.g. block-level job access). Next upload a Shapefile containing population figures, if not already included in the job data set, and a Shapefile with the larger geographic area you wish to aggregated up to. Then select the larger area as what you are "aggregating to" and the shapefile and attribute name containing the population figures. Then click calculate. Depending on the size of the study area and the number of points included, this may take a few minutes. The results will then be displayed on the map.


Thailand: Krabi & Koh Lanta - Part 1
Airport
Since our flight was landing in Krabi around 3:00 PM local time and we would require another one hour to get Visa on Arrival, immigration, car collection, etc, we decided to stay in Krabi on the first day and then travel to Koh Lanta on the next day.
We picked up a DTAC Prepaid SIM, (50 Baht more than BKK Price) for data and navigation purpose.
First stop - Lunch at Tesco Lotus food court on the way to Krabi. We had a nice time communicating in Thai(!) with the locals.
Hotel
Day 1 being a stop over for our main destination, we directly headed to our hotel - Thip Residence Boutique Hotel. Nice clean and spacious rooms and away from the crowd (actually 6KMs from Ao Nang). Usually everyone avoids to stay away from Ao Nang beach but it is not a concern when you make your own travel arrangements and are not dependent on taxis or public transport!
We roamed around Krabi town and Ao Nang area in the evening, had dinner at a restaurant near the Ao Nang beach and retired for the day!
Our hotel was located near Ao Nam Mao Pier, the pick up point for some of the super luxury resorts located at Railey Beach which is accessible only through the sea. We did not go to Railey but decided to check out the local attractions near the hotel.
Fossil Beach
(Thai Su-san Hoi, literally “Seashell Graveyard”). Some 7 km west of Ao Nang, this mildly tourist trap-like attraction has slates of compressed, 40 million year old shellfish, which bear a small resemblance to concrete. There’s also a small grubby museum and a huge slew of gift shops. Entry is a steep 200 baht for foreigners, but only 20 baht for Thais. This tourist trap is simply not worth the 200 baht you have to pay as tourists unless maybe you are a geology student. As the official Krabi tourism website (rather honestly) states “most are either engrossed in this or totally indifferent”.
Susaan Hoi, or Fossil Shell Beach (literally Seashell Graveyard), is located at Ban Laem Pho in Krabi, in the vicinity of Hat Noppharat Thara - Mu Ko Phi Phi National Park.
It is an unremarkable site, with nothing much to do or see. Tourists are charged 200 Baht per person for entry and get to go down 20 more steps than the non-paying tourists. Since we were there early in the morning and the place was not yet open, we just took few photographs and left.
We had thai style breakfast (rice, chicken and soup) at a local shop which seemed to be popular with the locals and the drove over to Ao Nang Beach to check the area in daylight.
Krabi - Driving Around
A short video: This is what Krabi (Ao Nang) looks like from inside a car!
We checked out from the hotel and drove towards the ferry to cross over to Koh Lanta. (approximately 2 hours drive).
Ferry
There are multiple ways to reach Koh Lanta - Passenger Ferry which departs twice a day from Ao Nang, Speed Boats from Ao Nang and Vehicle Ferry which is operational throughout the year from around 7:00 AM to 10:00 PM.The passenger ferry and speed boats stop operation during the monsoon season due to rough seas.
There are two ferries to be taken to reach the main Koh Lanta Island(marked in the screen-shot below). The total time to reach the island takes around 1 to 2 hours after you reach the first ferry point. (depending on the length of queue)
The Sun was playing its part by trying to roast whatever was outside at this time!
All Photographs are copyrighted.


This module integrates PMD's Copy/Paste Detector (CPD) tool.
CPD can find duplicate code in your project. Read more about CPD at the PMD's homepage:
For code duplicates do the following steps:
For text, and xml output formats the lines specifying files having code duplication are hyperlinked. Clicking the line opens the file.
In output window you can navigate to the next file by Navigate|Next Error (F12), and to the previous file by Navigate|Previous Error (Shift+F12).
The CPD results are shown in the output window:
Selecting a line/file reference shows the source file, having an annotation, like:
You can set following options
You can set these options via Tools|Options|Miscellaneous|PMD's Copy/Paste Detector.
The CPD Options dialog window:


@(messages: Messages) @views.html.main("Reservando") { @ownerNav(messages) @languageSelector(messages)
| @Messages("owner.my.reservations.date") | {{getDate(reservation.date)}} | @Messages("owner.my.reservations.address") | {{reservation.local.address.completeAddress}} |
| @Messages("owner.my.reservations.time") | {{getTime(reservation.date)}} | @Messages("owner.my.reservations.amount.of.people") | {{reservation.amount}} |
| @Messages("owner.my.reservations.discount.code") | {{reservation.discount.code}} - {{reservation.discount.discount}}% |


|
Simple Problem
|
Parameterised Problem
|
|
Write a simple, multiple choice problem in any subject area.
|
Write a dynamic problem with variables that can take a list of values.
Write a dynamic problem with variables that can take a range of values (Math problems)
|
|
Summative Problem
|
Domain Specific Problem
|
|
Grouping previously authored problems to form a bundle of random problems
|
Write a problem that can be rendered into the Khan Academy Exercise format
|


This is built using the Play! framework.
Getting to Philosophy! Some Wikipedia links are case-sensitive so we'll consider links as is. Rules that our crawler is following:
- Clicking on the first non-parenthesized, non-italicized link
- Ignoring external links, links to the current page, or red links (links to non-existent pages)
- Stopping when reaching "Philosophy", a page with no links or a page that does not exist, or when a loop occurs
Notes: Noticed that Xfer's site has a slight different when traversing the first links. Xfer's site actually goes to the next link if current link has been visited. Decided to follow the rules defined in the Getting to Philosophy article. So we actually stop traversing if we come across a link we've seen before to prevent loops.
@helper.form(routes.PhilController.GetToPhil()) { @helper.CSRF.formField @helper.inputText(form("url"), '_label -> "Wikipedia URL") }@if(result != null) {
Looks like you got some results! If you don't see philosophy at the end, that usually means there was a loop so we stopped crawling!
@result }


Notebooks
Story: The Makoba
The Makoba
Title
The Makoba
Collection
Summary
Tamme provides a short account concerning a Makoba who goes to his country when it rains. The Makoba say they see a rainbow and the rain falls.
Comments
1) This story is found in Book XI & XII-12
Contributors
Date
10 October 1881
Categories
Keywords
Makoba (and Tamme's people) , Makoba (and the rain) , Makoba (say that they see a rainbow and its rains) , Makoba (in Tamme's country) , Makoba (a Makoba man and his dog) , Makoba (returns to his country) , Makoba (their interactions with the !kun) , rain (and the Makoba) , rain (the Makoba say they see a rainbow) , rain (and rainbows) , rainbow (what the Makoba say when they see one and the rain falls) , Tamme (his people and the Makoba) , country (the Makoba in Tamme's and the rain)
Story Pages
10 020-10 021


| Market Cap | 0 | P/E | 0 | EPS | 0 | Shs Outstand | 0 |
| Income | 0 | PEG | 0 | Shs Float | 0 | Short Float | 0 |
| Sales | 0 | P/FCF | 0 | ROE | 0 | Target Price | 0 |
| Book/Sh | 0 | Quick Ratio | 0 | Gross Margin | 0 | RSI(14) | 0 |
| Cash/Sh | 0 | Current Ratio | 0 | Oper. Margin | 0 | Beta | 0 |
| Dividend | 0 | Debt/Eq | 0 | Profit Margin | 0 | ATR | 0 |
| Dividend % | 0 | LT Debt/Eq | 0 | Volatility | 0 | Price | 0 |


Settings
Settings in UI widgets are any part of a widget definition which is mutable. Most UI widgets have a set of common settings which are useful across all plugins.
Common Settings
| Name | Usage | |
|---|---|---|
| name | Name used in debug logs to differentiate this widget from other debug statements. | |
| debug | Provides standard debug output to console. | |
| performance | Provides performance logging to console of internal method calls. | |
| verbose | Provides extra debug output to console | |
| namespace | Namespace used for DOM event and metadata namespacing. Allows module's destroy method to not affect other modules. | |
| metadata | An object containing any metadata attributes used. | |
| selectors | An object containing all selectors used in the module, these are usually children of the module. | |
| classNames | An object containing all classnames used in the module. | |
| errors | A javascript array of error statements used in the plugin. These may sometimes appear to the user, but most often appear in debug statements. |
Changing Settings
- A settings object can be passed in when initializing the plugin
$('.foo') .module({ moduleName: 'Godzilla', verbose: true }) ; - Default settings for the module can be overridden by modifying $.fn.module.settings.
$.fn.module.settings.moduleName = 'Godzilla';
- Settings can be changed after a module is initialized by calling the 'settings' method on the module with either a settings object or a name, value pair.
$('.foo') // lets initialize that! .module() // oh wait forgot something .module('setting', 'moduleName', 'Godzilla') ;
Reading Settings
Settings can also be read programmatically:
$('.foo').module('setting', 'moduleName');
// outputs godzilla


JPanel
class provides general-purpose containers for lightweight components.
By default, panels do not add colors to anything except their own background;
however, you can easily add borders to them
and otherwise customize their painting.
Details can be found in
Performing Custom Painting.
In many types of look and feel, panels are opaque by default.
Opaque panels work well as content panes
and can help with painting efficiently,
as described in
Using Top-Level Containers.
You can change a panel's transparency
by invoking the setOpaque
method.
A transparent panel draws no background,
so that any components underneath show through.
The following picture
shows a colored version of the Converter
application,
which is discussed in more detail in
Using Models.
Converter
example uses panels in several ways:
JPanel
instance
— colored red
in the preceding snapshot —
serves as a content pane
for the application's frame.
This content pane uses a top-to-bottom
BoxLayout
to lay out its contents,
and an empty border
to put 5 pixels of space around them.
See Using Top-Level Containers
for information about content panes.
JPanel
subclass
named ConversionPanel
—
colored cyan —
are used to contain components
and coordinate communication between components.
These ConversionPanel
panels also have titled borders,
which describe their contents and enclose the contents with a line.
Each ConversionPanel
panel uses a left-to-right
BoxLayout
object to lay out its contents.
ConversionPanel
,
a JPanel
instance —
colored magenta —
is used to ensure the proper size and position of the combo box.
Each of these JPanel
instances uses a top-to-bottom
BoxLayout
object
(helped by an invisible space-filling component)
to lay out the combo box.
ConversionPanel
,
an instance of an unnamed JPanel
subclass —
colored blue —
groups two components (a text field and a slider)
and restricts their size.
Each of these JPanel
instances uses a top-to-bottom
BoxLayout
object to lay out its contents.
Converter
application normally looks like.
As the Converter
example demonstrates, panels are useful for
grouping components,
simplifying component layout,
and putting borders around groups of components.
The rest of this section gives hints on
grouping and laying out components.
For information about using borders, see
How to Use Borders.
FlowLayout
,
which places the panel's contents in a row.
You can easily make a panel use any other layout manager
by invoking the setLayout
method
or by specifying a layout manager when creating the panel.
The latter approach is preferable for performance reasons,
since it avoids the unnecessary creation
of a FlowLayout
object.
Here is an example of how to set the layout manager when creating the panel.
JPanel p = new JPanel(new BorderLayout()); //PREFERRED!
This approach does not work with BoxLayout
,
since the BoxLayout
constructor requires
a pre-existing container.
Here is an example that uses BoxLayout
.
JPanel p = new JPanel(); p.setLayout(new BoxLayout(p, BoxLayout.PAGE_AXIS));
add
method.
Exactly which arguments you specify to the add
method
depend on which layout manager the panel uses.
When the layout manager is FlowLayout
, BoxLayout
,
GridLayout
,
or SpringLayout
,
you will typically use the one-argument add
method, like this:
aFlowPanel.add(aComponent); aFlowPanel.add(anotherComponent);
BorderLayout
,
you need to provide an argument
specifying the added component's position within the panel.
For example:
aBorderPanel.add(aComponent, BorderLayout.CENTER); aBorderPanel.add(anotherComponent, BorderLayout.PAGE_END);
GridBagLayout
you can use either add
method,
but you must somehow specify
grid bag constraints for each component.
For information about choosing and using the standard layout managers, see Using Layout Managers.
JPanel
class itself is minimal.
The methods you are most likely to invoke on
a JPanel
object are those it inherits from its superclasses —
JComponent
,
Container
, and
Component
.
The following tables list the API
you are most likely to use,
with the exception of methods
related to
borders and
layout hints.
For more information about the API that all JComponent
objects
can use, see
The JComponent Class.
| Constructor | Purpose |
|---|---|
|
JPanel() JPanel(LayoutManager) |
Creates a panel.
The LayoutManager parameter provides a
layout manager for the new panel.
By default, a panel uses a FlowLayout
to lay out its components.
|
| Method | Purpose |
|---|---|
|
void add(Component) void add(Component, int) void add(Component, Object) void add(Component, Object, int) void add(String, Component) |
Adds the specified component to the panel.
When present, the int
parameter is the index of the component
within the container.
By default, the first component added is at index 0,
the second is at index 1, and so on.
The Object parameter
is layout manager dependent and typically provides
information to the layout manager regarding positioning
and other layout constraints for the added component.
The String parameter
is similar to the Object parameter.
|
| int getComponentCount() | Gets the number of components in this panel. |
|
Component getComponent(int) Component getComponentAt(int, int) Component getComponentAt(Point) Component[] getComponents() |
Gets the specified component or components. You can get a component based on its index or x, y position. |
|
void remove(Component) void remove(int) void removeAll() |
Removes the specified component(s). |
| Method | Purpose |
|---|---|
|
void setLayout(LayoutManager) LayoutManager getLayout() |
Sets or gets the layout manager for this panel. The layout manager is responsible for positioning the panel's components within the panel's bounds according to some philosophy. |
JPanel
objects.
The following table lists a few.
| Example | Where Described | Notes |
|---|---|---|
Converter
|
This section | Uses five panels, four of which use BoxLayout
and one of which uses GridLayout .
The panels use borders and, as necessary,
size and alignment hints to affect layout.
|
ListDemo
|
How to Use Lists | Uses a panel, with its default FlowLayout
manager, to center three components in a row.
|
ToolBarDemo
|
How to Use Tool Bars | Uses a panel as a content pane.
The panel contains three components,
laid out by BorderLayout .
|
BorderDemo
|
How to Use Borders | Contains many panels that have
various kinds of borders.
Several panels use BoxLayout .
|
BoxLayoutDemo
|
How to Use BoxLayout | Illustrates the use of a panel with
Swing's BoxLayout manager.
|


BREAKING: Late Aliu Mahama’s Mafara Hotel burnt to ashes [Photos]
by MyNewsGHFire has razed down one of the top hotels in the Tamale metropolis belonging to late Vice President Alhaji Aliu Mahama, the Mafara Hotel.
The late Alhaji Aliu Mahama’s son, Farouk Mahama, who confirmed the accident to MyNewsGH said it happened this evening and while there were extensive damages to properties worth thousands of cedis, “thankfully, no life was lost”.
Although not confirmed, the cause of the fire is believed to have been a power surge.
The top 3.5 Star hotel is located at Russian Bungalows in Tamale.
Sources: MyNewsGH.com/Stephen Zoure


Project: Kos - Crete - The Blue Island
Client: TUI
Producer: Laura Authier
Director: NOMO Films
DP: NOMO Films
The director's cut for one of a series of three promotional videos filmed and edited for the popular European travel brand TUI.
Blue is everywhere. Blue skies, blue water, blue flag, but when you visit Crete you will discover so much more. Our land is rich in culture, tradition, flavour and most of all hospitality. We are proud of our island and we are proud to welcome you.


docker
Manage Docker containers and images.
Some subcommands such as `docker run` have their own usage documentation.
More information: home page
- List all docker containers (running and stopped):
docker ps --all
- Start a container from an image, with a custom name:
docker run --name container_name image
- Start or stop an existing container:
docker start|stop container_name
- Pull an image from a docker registry:
docker pull image
- Display the list of already downloaded images:
docker images
- Open a shell inside a running container:
docker exec -it container_name sh
- Remove a stopped container:
docker rm container_name
- Fetch and follow the logs of a container:
docker logs -f container_name


| DOSE: T+ 0:00 |
20 mg |
sublingual |
Methoxetamine |
(powder / crystals) |
| T+ 0:50 |
20 mg |
sublingual |
Methoxetamine |
(powder / crystals) |
| T+ 1:15 |
1 bowl |
smoked |
Cannabis |
(plant material) |
Ever since my first marijuana experience at 17, trying every drug became one of the items on my bucket list. It has been 20 months since then and so far I have done salvia, shrooms, lsd, mdma, 25i-nbome, meth, coke, mdpv, lorazepam, and hydrocodone. The only drug I have done consistently (more than 3 times) is marijuana. I came across MXE when my dealer offered it as a free sample. After a lot of research on several websites, I was ready.
0:00 - After measuring out 20mg, I wet my finger tips, scoop up the pile, and apply it sublingually. It tastes very salty.
0:05 - My mouth starts to fill with saliva. It starts to feel uncomfortable - I'll insufflate from now on.
0:10 - Nothing noticeable yet, but the saliva build up proves itself to be annoying so I swallow.
0:30 - After 30 minutes, a feeling of drunkenness is unmistakeable. I try to walk around my house but it feels like I just took 5 shots of liquor. I notice that I'm hungry despite only eating a meal a couple hours earlier. I go downstairs and cook up some ramen. Oddly, it was somewhat difficult preparing such an easy meal.
0:50 - The ramen tasted better than it usually did. I'm a little disappointed with the trip's strength so I redose with another 20mg (insufflated this time). Note - I almost NEVER redose. This is quite uncharacteristic of me and my health is usually a big concern of mines whenever I do drugs. I refuse to do any drugs more than twice a week including alcohol and caffeine. The only exception I have is cannabis.
1:10 - The redose hits me. I'm feeling really heavy and happy at this point. All the worries in my life drifted away. I felt extremely content. Funnily enough, a feeling of motivation waves over me. I run a website that I've been trying to make part time money off of and suddenly I felt like writing more articles.
1:15 - I decide to smoke a bowl from my huge bong (2 feet tall). I haven't smoked since classes started 2 weeks ago so today was the day to treat myself. It's been a long week.
1:25 - My friend's homegrown Jack Herrer mixes with the mxe. Wow, the feelings from the cannabis and mxe were clearly differentiable. This felt like the first time I had ever smoked pot.
1:40 - Movies and games drew me in, but I felt like I was wasting my trip on them. I lay down on my bed and close my eyes.
1:55 - HOLY SHIT. I can't come up with words to describe the CEVs and how AWESOME I felt. It surpassed any other drugs that I've experimented with in the past. 100mg of MDMA doesn't come close, LSD was a joke compared to the psychedelic mindset I was in.
At the time, I put my hand up to my chest to check my heart rate. This is something I always do with new drugs. I can't read my heart rate at all and I get a little anxious about it. One side of me was worried with my health and the other side was enjoying the trip. Note - I've never taken more than 1.5 blotters (prob 120ug) of LSD.
2:10 - My mind was blown when I looked over at the clock and only 15 minutes had passed. I had been thinking at the speed of light. My 'consciousness' felt disconnected from all my body parts except from the warmth coming from my blankets. I was so far away from my body... like being blasted hundreds of miles up into the cosmos. At the same time, however, I could move my body. It just felt like very tiny body parts. While I was thinking, I couldn't even comprehend why anybody could ever feel sad. The universe was so beautiful and I felt great being alive.
2:20 - I probably plateau'd at this time.
2:50 ~ 3:30 - Sometime at this point I pulled up my laptop and posted on a forum I frequent about how great I was feeling.
3:30 - The trip wasn't as strong anymore. The weed has mostly worn off and I was back to feeling the mxe again. I am now able to get back on my computer.
5:00 - Mostly sober, but I still felt slightly disconnected.
From now on, I'll either have a trip sitter or at least a heart watch so I don't have to worry about that anymore. Also, I'll probably keep my dosing to once a month. I've found some concerning health effects with dissociatives.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


top
| up
| prev
| next
TypeDerivationRec Struct
Definition at line 19
of DerivedTypeSymbol.hpp
Member Functions
Member Variables
Member Function Details
IsEmpty Member Function
bool
cmajor::symbols::TypeDerivationRec::IsEmpty() const
Definition at line 22
of DerivedTypeSymbol.hpp
:
22 { return derivations.empty(); }
Called by: cmajor::symbols::SymbolTable::MakeDerivedType
top
| up
| prev
| next


In Peru, independent small grocery stores are called ‘bodegas’.
There are 2+ million stores only in Latin America and they are considered a natural solution for unemployment.
Turbodega is a software management tool that builds a network of small grocers in emerging countries and tracks their daily-sales in real time.
We are an integral solution that will work with partners in making life easier for our bodegueras.


The only metrics that we save about the visitors of our site are the pages that are viewed and HTTP referrers.
We built our own open source analytics platform,
Infinity Analytics, so that we could still get site usage metrics while respecting the privacy of our users.
Information Not Collected
We do not collect or log data about the individual users who access this website. This means that we do not
log IP addresses or user-agent strings. We also do not use cookies at all, which is one the most
common ways that other websites attempt to track you online, even after you have left their site.
Information Shared
Since we are using third-party APIs to gather the search results, those services can view the
searches that we make. They cannot see, however, who made the search because it
appears to them as our service making the search. This is the same way that
DuckDuckGo works as well.
How We Value Your Privacy
We value your privacy here by simply never straying away from the privacy policy described
above. Our model is designed to respect the privacy of all our users.
{% endblock %}


Feedback page
First name:
Last name:
Password:
Gender:
male
female
Email:
Age:
19
20
22
23
24
Feedback:


Payment Successful
Your booking was successful. Please find your booking details below:
Booking Details
Price:
Rs.10
Quantity:
1
Tokens Redeemed:
0
Discount:
Rs.10
Total Amount:
Rs.10
Back To Home