text:
From Stargate Wiki
Climate change research
|Out of universe information|
The planet's Stargate is located in a valley close to a glacier. The atmosphere had succumb to a global warming effect. The Atlantis expedition set up the research outpost further up the valley closer to the glacier.
At some point in 2008 Dr. Nichols had set up a research outpost on this planet to study the effects of global warming. Some time later the glacier on the planet breached and flooded the valley the outpost was located. The research team was unable to make contact with Atlantis and so Woolsey sent Sheppard's team to discover why they had not made contact, exiting the gate underwater and having to seek refuge from the icy waters on top of the gate, while Col. Sheppard had to swim down and dial the Stargate. The team was forced to wait for the gate to deactivate before they could be retrieved by a Puddle Jumper but had to wait several hours for the flood waters to recede before they could return to Atlantis. (ATL: "The Shrine")


text:
Leaping sharks are no bull
Bull sharks' behaviour baffles scientists.
It's a phenomenon with which Brisbane River boaties are familiar, but scientists are at a loss to explain.
Every year as temperatures rise, bull sharks can be seen leaping from the water and spinning through the air, sparking wonder among spectators and researchers alike.
My belief is that they are getting rid of parasites and that's why they spin around so fast
University of Queensland professor in zoology Craig Franklin says despite up to a thousand bull sharks living in the river winding its way through the state capital, much of their behaviour is a mystery.
Particularly confounding is the sight of the sharks getting air time during warmer months.
It is a spectacle ferry drivers say they catch sight of up to four times a week.
Craig Wilkins, who has spent years on the river as a City Cat master and at the helm of the Kookaburra Queen, says the wide stretch of river at Bulimba is a common spot for the behaviour.
"The warmer the water, the more times you will see them jumping," he said. As the sun gets up, that's when you will see them jumping.
"About two years ago the river was a little bit cleaner than usual and everybody was seeing them. You ask any City Cat master, they'll say the same thing. They see them jumping all the time."
As well, their aerials show the sharks are also more active underwater as the river at this time of year.
Sharks found upstream are normally less than 1.5m long and pose little threat to people.
However, dog owners have been warned to keep their pets out of the river at dusk and dawn, when sharks are most active.
There have been numerous reports of dogs being taken from the river's edge and even instances of more ambitious sharks taking on larger prey.
In 2005, Ipswich locals were shocked after a bull shark attacked a race horse being put through its paces in the Brisbane River at Kholo.
The attack came just weeks after a teenager was bitten on the head and finger at Karalee.
One ferry driver recently told of seeing a Chihuahua snapped up in shallow water at the edge of the river and Professor Franklin said small dogs would be attractive to sharks.
"Small snacks like [Chihuahuas] could be within the size range of prey items that a bull shark would take," he said.
"You wouldn't want to let your dog go for a swim around dusk and dawn. That's when they are most likely to be feeding."
A "cosmopolitan" creature found in tropical and sub-tropical waterways around the world, the bull shark has long baffled scientists with its behaviour in Indonesia, Thailand, Fiji and Florida.
In some cases they have been observed leaping for bats, but by and large their motive is a mystery, according to Professor Franklin.
"I've got no idea to tell you the truth," he said. "Whether it's to scare prey out, I've got no idea why they do that.
"I've seen it and it tends to be the small ones."
City Cat and ferry drivers say they often see it during the long hours they spend on the waterway.
They have even ventured theories on why it happens.
Mr Wilkins said the manoeuvre could be a type of housekeeping.
"My belief is, and I don't know if it is accurate, but my belief is that they are getting rid of parasites and that's why they spin around so fast," he said.
"That's what we see as we are driving along occasionally is them jumping up and doing a bit of a spin and hitting the water again. They're usually about four foot long and the biggest I've ever seen was about six foot, I guess."
His theory was echoed by another ferry driver who spoke to brisbanetimes.com.au, but Professor Franklin wasn't sold on the idea.
"I doubt that," he said. "There are external parasites that they can have, but I've never heard that it's a successful strategy to remove parasites."
Professor Franklin said it was possible bull sharks were among those filmed feeding on a school of bait fish off Teewah Beach north of Noosa on Friday and were often found in the open ocean.
But he said what set them apart from other species was their ability to survive in fresh water thanks to being able to retain salt in their bodies.
He said the sharks give birth near the mouth of the river, with the 50cm pups heading upstream, where they would live for up to four years until they venture into the ocean in search of larger prey.
"I think to be in a state capital city and to have bull sharks in our waterways is a wonderful thing. They are undoubtedly an incredible animal to have in our waterways," he said.
Around the world, more fatalities are attributed to bull sharks than any other species.
In the past decade bull sharks have been blamed for deaths in the Gold Coast canal system, and an attack which killed a teenage girl at North Stradbroke Island in 2006.
"You could almost say they are a cosmopolitan shark in that most capital cities are built around river systems, they are circum-global, so right around the globe, so the likelihood of people being injured or killed is higher," said Professor Franklin.
"But they don't target humans. People need to realise that. They are opportunistic feeders. All we have to do is modify our behaviour and be careful where we swim and the time at which we swim.
"You look at the unfortunate incidents on the Gold Coast in the canals where people were taken and they were swimming around at night time or dusk or dawn."

source: HuggingFaceFW/fineweb-edu


text:
The mechanics of a power kick_using soccer as an example_
Final ball velocity depends upon several factors. There are, however, three primary determinants in ball velocity:
If the hip of the kicking leg is not fully extended prior to foot plant, subsequent leg swing velocity will be reduced. This extension ("cocking") of the hip (1) allows greater distance for the leg to increase its velocity on the forward swing, (2) stretches the muscles which cross the hip to facilitate their contraction and recoil of the leg, and (3) permits greater rotation of the hip.
If the supporting leg flexes excessively during foot plant, the velocity of the kicking leg will be reduced.
On the other hand, a firm supporting leg "blocks" the forward motion of its hip and increases the velocity of the swing leg.
Improper coordination and sequencing of movements in the kick will reduce possible ball velocity.
The order of events in the kicking leg, following hip extension, are: (1) hip rotation, (2) forward swing of the thigh, and (3) forward swing of the shank. Each of these movements should increase the velocity of the subsequent segment resulting in maximum velocity at the foot just prior to impact with the ball. The action of the leg should be like a whip "snapped" at the ball.


text:
Vancouver, BC -- Roughrider Exploration Limited ("Roughrider" - TSX-V: REL) is pleased to announce it has staked the 6,358.8 hectare Scottie West Property located in the "Golden Triangle", approximately 30 kilometres (km) northwest of Stewart, B.C. and immediately west of the Scottie Gold Mine Property¹. These newly staked claims cover favourable geology, as mapped by the British Columbia Geological Survey, including Jurassic Hazelton volcanic rocks, Jurassic Texas Creek Intrusions and Eocene aged intrusions that are also host to numerous mineral occurrences and past producing mines throughout the Stewart Camp, including Ascot Resources Premier Mine¹ and Scottie Resources Scottie Gold Mine¹ (see Figure 1).
Historical work in the immediate area focused principally on the past producing Scottie Gold gold-silver mine¹ to the east and on the Granduc base metals mine¹ to the west of Roughrider's new Scottie West Property. Very little historical work appears to have been undertaken on Roughrider's property primarily as a result of extensive glacial cover which has been rapidly retreating since the majority of the historical work was completed in the region during the late 1980's.
An assessment report (#33511) filed by Eilat Resources documents a 2012 helicopter-borne magnetic geophysical survey totaling 332.5 line km at a 150 metre line spacing of which approximately the western 15% of the survey is now located within the current Scottie West Property. A smaller subsequent airborne magnetic and spectral survey was flown in 2016 on behalf of Eilat within the current Scottie Gold Mine Property (Assessment Report #36318). These airborne surveys highlighted several prominent north-northwesterly and southwesterly trending features which appear to have a spatial association with mineral occurrences (see Figure 2).
Roughrider's CEO, Adam Travis, comments: "The 2019 discovery of the Domino Gold Zone along a mineralized east-west structure roughly halfway between the Scottie West Property and the historical Scottie Gold mine, as announced by Scottie Resources Corp. on November 14, 2019 verifies the importance of the magnetic features identified by the previous airborne surveys. Equally important, it highlights that new discoveries can be made in areas of previous snow and ice cover. A number of these magnetic features appear to trend onto Roughrider's Scottie West Property based on the partial historical survey coverage. I fully expect to visit the area this summer, Covid-19 permitting, to begin reconnaissance exploration and get a better sense of the extent of glacial retreat and the property's overall prospectivity. In the meantime, we will continue to aggressively explore for advanced gold opportunities."
Roughrider plans to continue compilation of the historical airborne magnetic survey data that was flown over its current property and proposes to complete airborne geophysical coverage across its property and to conduct initial prospecting and geological work this summer.
The scientific and technical information contained in this news release has been prepared, reviewed and approved by David Tupper, P.Geo. (British Columbia), Roughrider Exploration's VP Exploration and a Qualified Person within the context of Canadian Securities Administrators' National Instrument 43-101; Standards of Disclosure for Mineral Projects.
About Roughrider Exploration Limited
Roughrider's current focus is the exploration of its 100% owned Eldorado, Gin and Bonanza Properties located in the Golden Triangle area of northern British Columbia, adjacent to the Red Chris Mine (owned and operated by Newcrest Mining Limited and Imperial Metals Corporation). Additionally, Roughrider will continue to review strategic precious metal acquisition opportunities in western North America. Roughrider also holds a 100% ownership in the Sterling Property located in central BC.
On Behalf of the Board of Directors:
Adam Travis, Chief Executive Officer and Director
For further information, please contact:
Roughrider Exploration Limited
Adam Travis, CEO
625 Howe Street, Suite 420
Vancouver, B.C. V6C 2T6, Canada
1 This news release and maps contain information about adjacent properties on which Roughrider has no right to explore or mine. Readers are cautioned that mineral deposits on adjacent properties are not indicative of mineral deposits on Roughrider's properties.
Neither TSX Venture Exchange nor its Regulation Services Provider (as that term is defined in the policies of the TSX Venture Exchange) accepts responsibility for the adequacy or accuracy of this release.
CAUTIONARY STATEMENT REGARDING FORWARD-LOOKING INFORMATION
Certain information contained or incorporated by reference in this press release, including any information regarding the proposed Transaction, private placement, board and management changes, as to our strategy, projects, plans or future financial or operating performance, constitutes "forward-looking statements." All statements, other than statements of historical fact, are to be considered forward-looking statements. Forward-looking statements are necessarily based on a number of estimates and assumptions that, while considered reasonable by Roughrider, are inherently subject to significant business, economic, geological and competitive uncertainties and contingencies. Although Roughrider believes the expectations expressed in such forward-looking statements are based on reasonable assumptions, such statements are not guarantees of future performance. Known and unknown factors could cause actual results to differ materially from those projected in the forward-looking statements. Such factors include but are not limited to: fluctuations in market prices, exploration and exploitation successes, continued availability of capital and financing, changes in national and local government legislation, taxation, controls, regulations, expropriation or nationalization of property and general political, economic, market or business conditions. Many of these uncertainties and contingencies can affect our actual results and could cause actual results to differ materially from those expressed or implied in any forward-looking statements made by, or on behalf of, us. Readers are cautioned that forward-looking statements are not guarantees of future performance and, therefore, readers are advised to rely on their own evaluation of such uncertainties. All of the forward-looking statements made in this press release, or incorporated by reference, are qualified by these cautionary statements. We do not assume any obligation to update any forward-looking statements.

source: m-a-p/FineFineWeb


ArangoDB v3.5 reached End of Life (EOL) and is no longer supported.
This documentation is outdated. Please see the most recent version here: Latest Docs
SmartGraph Management
This chapter describes the JavaScript interface for creating and modifying SmartGraphs. A SmartGraph is a specialized version of a General Graph, which means all of the General Graph functionality is available on a SmartGraph as well. The major difference of both modules is handling of the underlying collections:
 - General Graphs do not enforce or maintain any sharding of the collections and can therefore combine arbitrary sets of existing collections.
 - SmartGraphs enforce and rely on a special sharding of the underlying collections and hence can only work with collections that are created through the SmartGraph itself. This also means that SmartGraphs cannot be overlapping. A collection can either be sharded for one SmartGraph or for another. If you need to make sure that all queries can be executed with SmartGraph performance, just create one large SmartGraph covering everything and query it stating the subset of edge collections explicitly.
To generally understand the concept of this module please read the chapter about General Graph Management first. In the following we will only describe the overloaded functionality. Everything else works identical in both modules.
Create a Graph
SmartGraphs also require edge relations to be created. The format of the relations is identical. The only difference is that all collections used within the relations to create a new SmartGraph must not exist yet. You have to let the SmartGraph module create the Graph collections for you, so that it can enforce the correct sharding.
graph_module._create(graphName, edgeDefinitions, orphanCollections, smartOptions)
 - graphName (string): Unique identifier of the graph
 - edgeDefinitions (array): List of relation definition objects, may be empty
 - orphanCollections (array): List of additional vertex collection names, may be empty
 - smartOptions (object): A JSON object having the following keys:
 - numberOfShards (number): The number of shards that will be created for each collection. To maintain the correct sharding all collections need an identical number of shards. This cannot be modified after creation of the graph.
 - smartGraphAttribute (string): The attribute that will be used for sharding. All vertices are required to have this attribute set and it has to be a string. Edges derive the attribute from their connected vertices.
The creation of a graph requires the name and some SmartGraph options. Due to the API edgeDefinitions and orphanCollections have to be given, but both can be empty arrays and be added later.
The edgeDefinitions can be created using the convenience method _relation known from the general-graph module, which is also available here.
orphanCollections again is just a list of additional vertex collections which are not yet connected via edges but should follow the same sharding to be connected later on.
All collections used within the creation process are newly created. The process will fail if one of them already exists, unless they have the correct sharding already. All newly created collections will immediately be dropped again in the failure case.
Examples
Create a graph without relations. Edge definitions can be added later:
arangosh> var graph_module = require("@arangodb/smart-graph");
arangosh> var graph = graph_module._create("myGraph", [], [], {smartGraphAttribute: "region", numberOfShards: 9});
arangosh> graph_module._graph("myGraph");
Show execution results
Hide execution results
{[SmartGraph]
}
Create a graph using an edge collection edges and a single vertex collection vertices as relation:
arangosh> var graph_module = require("@arangodb/smart-graph");
arangosh> var edgeDefinitions = [ graph_module._relation("edges", "vertices", "vertices") ];
arangosh> var graph = graph_module._create("myGraph", edgeDefinitions, [], {smartGraphAttribute: "region", numberOfShards: 9});
arangosh> graph_module._graph("myGraph");
Show execution results
Hide execution results
{[SmartGraph]
 "edges" : [ArangoCollection _PHONE_, "edges" (type edge, status loaded)],
 "vertices" : [ArangoCollection _PHONE_, "vertices" (type document, status loaded)]
}
Create a graph with edge definitions and orphan collections:
arangosh> var graph_module = require("@arangodb/smart-graph");
arangosh> var edgeDefinitions = [ graph_module._relation("myRelation", ["male", "female"], ["male", "female"]) ];
arangosh> var graph = graph_module._create("myGraph", edgeDefinitions, ["sessions"], {smartGraphAttribute: "region", numberOfShards: 9});
arangosh> graph_module._graph("myGraph");
Show execution results
Hide execution results
{[SmartGraph]
 "myRelation" : [ArangoCollection _PHONE_, "myRelation" (type edge, status loaded)],
 "female" : [ArangoCollection _PHONE_, "female" (type document, status loaded)],
 "male" : [ArangoCollection _PHONE_, "male" (type document, status loaded)],
 "sessions" : [ArangoCollection _PHONE_, "sessions" (type document, status loaded)]
}
Modify a graph definition at runtime
After you have created a SmartGraph its definition is not immutable. You can still add or remove relations. This is again identical to General Graphs.
However there is one important difference: You can only add collections that either do not exist, or that have been created by this graph earlier. The latter can be achieved if you for example remove an orphan collection from this graph, without dropping the collection itself. Than after some time you decide to add it again, it can be used. This is because the enforced sharding is still applied to this vertex collection, hence it is suitable to be added again.
Remove a vertex collection
Remove a vertex collection from the graph:
graph._removeVertexCollection(vertexCollectionName, dropCollection)
 - vertexCollectionName (string): Name of vertex collection.
 - dropCollection (bool, optional): If true the collection will be dropped if it is not used in any other graph. Default: false.
In most cases this function works identically to the General Graph one. But there is one special case: The first vertex collection added to the graph (either orphan or within a relation) defines the sharding for all collections within the graph. They have their distributeShardsLike attribute set to the name of the initial collection. This collection can not be dropped as long as other collections follow its sharding (i.e. they need to be dropped first).
Examples
Create a SmartGraph and list its orphan collections:
arangosh> var graph_module = require("@arangodb/smart-graph");
arangosh> var relation = graph_module._relation("edges", "vertices", "vertices");
arangosh> var graph = graph_module._create("myGraph", [relation], ["other"], {smartGraphAttribute: "region", numberOfShards: 9});
arangosh> graph._orphanCollections();
Show execution results
Hide execution results
[
 "other"
]
Remove the orphan collection from the SmartGraph and drop the collection:
arangosh> graph._removeVertexCollection("other", true);
arangosh> graph_module._graph("myGraph");
Show execution results
Hide execution results
{[SmartGraph]
 "edges" : [ArangoCollection _PHONE_, "edges" (type edge, status loaded)],
 "vertices" : [ArangoCollection _PHONE_, "vertices" (type document, status loaded)]
}
Attempting to remove a non-orphan collection results in an error:
arangosh> graph._removeVertexCollection("vertices");
Show execution results
Hide execution results
[ArangoError 1928: collection is not in list of orphan collections]
You cannot drop the initial collection (vertices) as long as it defines the sharding for other collections (edges).
arangosh> var graph_module = require("@arangodb/smart-graph");
arangosh> var relation = graph_module._relation("edges", "vertices", "vertices");
arangosh> var graph = graph_module._create("myGraph", [relation], [], {smartGraphAttribute: "region", numberOfShards: 9});
arangosh> graph._deleteEdgeDefinition("edges");
arangosh> graph._removeVertexCollection("vertices");
arangosh> db._


text:
- Simple, yet challenging, drills that stress fundamentals and improved skills
- Develop quick, sharp passing to maintain possession of the puck
- Learn to teach the little things that can mean the difference between a win or a loss
with Mark Carlson,
Cedar Rapids Roughriders (USHL) Head Coach;
2005 Clark Cup Champions;
2x U.S. Junior Select Team Head Coach ('08 and '09),
Back-to-Back World Junior A Challenge Champions ('08 and '09);
2008-09 United States Olympic Committee Development Coach of the Year
In this two-part instructional hockey DVD, Mark Carlson presents simple, yet essential drills that are at the heart of player development and team success.
Drills for Puck Possession
Learn eight drills to develop these critical puck possession skills:
- Quick, player to player puck movement
- Agility skating and passing in tight spaces
- No-handle passing while skating at full speed
- D-to-D rear diagonal passing
- Center support
- Transition skill development
- Indirect passing off the boards
Carlson concludes the segment with a full ice drill that combines these skills in a game-like, high speed setting.
Drills for Improving the Details
Carlson presents seven drills to teach and refine the finer points of the game:
- Stick-in-hand discipline to cut down on stick and hand penalties
- Shot blocking that keeps your players in a ready-to-play position
- Shooting the puck at the optimal height making it difficult to defend
- Stick skills for forwards
- Skills and strategies to screen the goalie
- Small, confined area competitive play to simulate game-like chaos
- Accountability, responsibility and detail
Carlson introduces each drill with a maker board diagram and follows with on-ice demonstration. On the ice, Carlson narrates the drill and offers valuable tips on how to best achieve the goals that each drill presents.
Carlson stresses the simplicity of each drill and how through repetition and reinforcement, each drill can be very beneficial to your player development and team success!
52 Minutes. 2010.Hockey Videos

source: openbmb/Ultra-FineWeb


text:
First of all, a Gcal resource file is a plain ascii text file. This text file may be created by any text editor or by redirecting the standard output channel to a file, e.g.:
|$ echo '_PHONE_ Text'>> resource-file |
A special —but simple— line structure is required so Gcal is able to interpret its contents. Each fixed date entry in a resource file must be split into two parts, namely a date part and an optional text part which must be separated by one whitespace1 character minimum. It is unnecessary to give a whitespace separator character if no text part is specified.
A line must always end with a '\n' (newline) character, except it is the
last line of a resource file. The maximum length of a line is limited to
INT_MAX2 characters. A newline character is
automatically appended to the line if the standard output channel is
directed to a file. A newline character is appended to the typed line in a
text editor window if it is completed by pressing the key. In case
the used text editor does not generate the newline character in this way, it
should be set to this mode of operation, otherwise this text editor is useless
for creating Gcal resource files.
The line structure of fixed date entries is:
date part [ whitespace text part ] newline
or more concrete, e.g.:
yyyy[mm[dd|wwwn]] [ whitespace text ] newline
or much more concrete, e.g.:
_PHONE_ Hi, I'm the text!
Besides fixed date entries, a resource file may contain further entries like:
; A remarked line ; A formatted and multi-line \ remark
_TAG_ _TAG_ "file name"
Date variable assignments respectively operations...
dvar=NOTHING dvar=mmdd dvar=mmwwwn dvar=*dn[www] dvar=*wn[www] dvar=dvar[[+|-]n[www]] dvar++ dvar-- dvar+=[+|-]n dvar-=[+|-]n dvar+=nwww dvar-=nwww
Text variable assignments respectively operations...
tvar=[text] tvar?[command] tvar:[command] tvar++ tvar-- tvar+=[+|-]n tvar-=[+|-]n
Text variable references...
Text variable references at the beginning of a Gcal resource file line may only be used if it is ensured that they are expanded to a valid Gcal resource file line.


BEA Logo BEA WebLogic Server Release 6.1
 BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
 WebLogic Server Doc Home | Security | Previous Topic | Next Topic | Contents | View as PDF
Security Fundamentals
This section describes the following concepts behind WebLogic Server security:
Resources are entities that are accessible from WebLogic Server, such as events, servlets, JDBC connection pools, JMS destinations, JNDI contexts, connections, sockets, files, and enterprise applications and resources, such as databases.
For each resource you want to protect in WebLogic Server, you must specify the following:
For more information, see Managing Security.
Security Realms
A security realm is a logical grouping of Users, Groups, and ACLs. A WebLogic Server resource is protected under only one security realm and by a single ACL in that security realm. A User must be defined in a security realm in order to access any resources belonging to that realm. When a User attempts to access a particular WebLogic Server resource, WebLogic Server tries to authenticate and authorize the User by checking the ACL and permissions assigned the User in the relevant realm. Figure 2-1 illustrates how realms work in WebLogic Server.
Figure 2-1 Users, Groups, and ACLs in a WebLogic Server Realm
The default security realm in WebLogic Server is the File realm. When WebLogic Server is started, the File realm creates User, Group, and ACL objects from properties defined through the Administration Console in WebLogic Server and stored in the file.
Note: The File realm is designed for use with 10,000 or fewer users. If you have more that 10,000 users, we recommend using an alternate security realm.
WebLogic Server also provides support for developers who want or must accommodate special security situations. WebLogic Server allows you to use a security realm other than the File realm by installing an alternate security realm or by writing your own customized security realm. Alternate security realms can support some or all of the authentication and authorization operations WebLogic Server requires of a realm.
There are two possible realm configurations:
Note: If you choose to use an alternate security realm or a custom security realm, you must configure the Caching realm.
In the default scenario, a client request arrives at the WebLogic Server through the Caching realm. The Caching realm forwards the request to the File realm for authorization and authentication. When it receives the results of the realm lookups (whether successful or unsuccessful), the Caching realm stores these results. It maintains separate caches for User, Group, permission, ACL, and authentication look ups. You can selectively enable each type of cache, set the number of objects cached, and specify the number of seconds a cached object is valid. Effectively, the Caching realm makes the authentication and authorization process faster and more efficient.
If you use an alternate security realm or a custom security realm, the Caching realm evaluates the client request, delegates it to the appropriate security realm, and caches the results to make the next lookup faster. For example, you may be using an alternate security realm that supports only authentication operations. When a client request is received by WebLogic Server, the Caching realm contacts the alternate security realm for authentication, and then the File realm for authorization.
Figure 2-2 illustrates how alternate security realms, the Caching realm, and the File realm work together to authenticate and authorize users in a WebLogic Server environment.
Figure 2-2 Alternate Security Realms, the Caching Realm, and the File Realm in WebLogic Server
WebLogic Server provides the following alternate security realms:
For more information, see the following sections in Managing Security:
Users are entities that use WebLogic Server, such as application end users, client applications, and even other WebLogic Servers.
When a user wants to access WebLogic Server, it presents a username and a credential (either a password or a digital certificate) through programmatic means to WebLogic Server. If WebLogic Server can prove the identity of the User based on that username and credential, WebLogic Server associates the User with a thread that executes code on behalf of the User. Before the thread begins executing code, however, WebLogic Server checks pertinent ACLs to make sure the User has the required permissions to continue.
When defining a User in a WebLogic Server realm, you also define a password for that User. In the past, usernames and passwords were stored in clear text in a WebLogic Server security realm. Now WebLogic Server hashes all passwords. When WebLogic Server receives a client request, the password presented by the client is hashed and WebLogic Server compares it to the already hashed password for matching.
For more information, see the following sections in Managing Security:
Groups are logically ordered sets of Users. Managing Groups is more efficient than managing large numbers of Users individually. For example, an administrator may specify permissions for 50 users at one time by specifying a Group. Usually, Group members have something in common. For example, a company may separate their sales staff into two Groups, Sales Representatives and Sales Managers, because staff members have different levels of access to WebLogic Server resources depending on their job descriptions.
WebLogic Server can be configured to assign Users to Groups. Each Group shares a common set of permissions that govern its member users' access to resources. You can mix Group names and User names whenever a list of Users is permitted.
A person can be defined as both an individual User and a Group member. Individual access permissions override any Group member access permissions. WebLogic Server evaluates each user by first looking for a Group, and testing whether the user is a member of the Group, and then looking for the User in the list of defined Users.
For more information, see the "Defining Groups" topic in Managing Security.
ACLs and Permissions
Permissions represent privileges required to access resources. A system administrator protects resources by creating lists of Users and Groups that have the permissions required to access those resources. Such lists are called access control lists (ACLs). ACLs and the functions for which they grant permission are resource-specific. For example, Users with the proper permissions may read, write, send, and/or receive files, load servlets, and link to libraries.
An ACL file is composed of AclEntries, each of which contains a set of permissions for a particular User or Group.
WebLogic Server uses the JavaSoft ACL standard, distributed with the Java Development Kit (JDK) 1.1, to extend the security framework of Java and make it practical for use at the enterprise level. The WebLogic Server implementation of ACLs is based on the package. Because ACLs in WebLogic Server are based on an open-standard, you are not tied to a proprietary solution.
You can set permissions on the following WebLogic Server resources:
Note: Access to EJBs and Web applications is not controlled through ACLs. Rather, security elements in deployment descriptors are used to define access to a particular EJB or Web application.
For more information, see the "Defining ACLs" section in Managing Security.
For information about EJB security, see Programming WebLogic Enterprise JavaBeans.
For more information about Web application security, see Assembling and Configuring Web Applications.
SSL Protocol
The SSL protocol offers security to applications connected through a network. Specifically, the SSL protocol provides the following:
When the SSL protocol is used, the target always authenticates itself to the initiator. Optionally, if the target requests it, the initiator can authenticate itself to the target. Encryption makes data transmitted over the network intelligible only to the intended recipient. An SSL connection begins with a handshake during which the applications exchange digital certificates, agree on the encryption algorithms to be used, and generate the encryption keys to be used for the remainder of the session.
The SSL protocol provides the following security features:
If you are using a Web browser to communicate with WebLogic Server, you can use the Hypertext Transfer Protocol with SSL (HTTPS) to secure network communications.
The SSL protocol is tunneled over an IP-based protocol. Tunneling means that each SSL record is encapsulated and packaged with the headers needed to send the record over another protocol. The use of SSL is signified in the protocol scheme of the URL used to specify the location of WebLogic Server.
WebLogic Server is available with exportableor domestic-strength SSL.
The standard WebLogic Server distribution supports exportable-strength SSL only. The domestic version is available, by request only from your BEA sales representative. Since the United States Government relaxed restrictions on exporting encryption software in early 2000, the domestic version of WebLogic Server can be used in most countries.
During installation, you are prompted to choose which strength of the SSL protocol you want to use.We recommend the domestic WebLogic Server distribution because it allows stronger encryption. If you generate a Certificate Signature Request (CSR) using the exportable WebLogic Server distribution, you cannot support high-strength connections and you cannot authenticate clients that present domestic-strength certificates.
The implementation of the SSL protocol provided by WebLogic Server is a pure-Java implementation. A native library provides faster performance for some SSL operations on the Solaris, Windows NT, and IBM AIX platforms. You can request the use of these native Java libraries for the SSL protocol through the Administration Console.
For more information, see the "Configuring the SSL Protocol" section in Managing Security.
Authentication Mechanisms
WebLogic Server users must be authenticated whenever they request access to a protected WebLogic Server resource. For this reason, each user is required to provide a credential (a username


Aquarius Temporary Tattoo
Aquarius temporary tattoos represent the zodiac eleventh sign symbolized by water bearer. Mostly, Aquarius is depicted as a pot that is spilling water or water alone. The water is usually presented with two horizontal zigzag lines piled on each other. Sometimes, the two lines feature the stars around them to denote an Aquarius constellation design. Furthermore, the water bearer is usually presented as a woman or a man carrying a pot of water.


text:
Siebel Business Process Designer Administration Guide > For Developers: Understanding How Workflow Processes Are Designed > Building Long-Running Workflow Processes >
Assigning Subprocesses to End Users to Create Collaborative Long-Running Workflows
Using the subprocess step, you can configure workflows that assign interactive subprocess workflows to end users to create collaborative workflow processes. An example of a collaborative workflow is one that includes a requirement for approvals; the route the workflow takes as tasks is a route across multiple users.
Use the Step Recipient field on a subprocess step to create collaborative workflows. Assignment occurs based on the login name, not on the Position or User ID. This login name may be a literal value, it may be held in a process property or a buscomp field, or it may be the result of an expression.
NOTE: The Process Designer cannot validate the data supplied to make sure that it represents a valid login name at design time.
To assign subprocesses to end users
- Create a subprocess step.
- Right-click the subprocess step and choose Show Recipients.
- In the WF Step Recipients applet, set the Recipient Name field to the login name of the assignee (the end user who will be assigned the subprocess).


Documentation
Write to Google BigQuery
To write data to Google BigQuery with Flux:
 1. Import the sql package.
 2. Pipe-forward data into sql.to() and provide the following parameters:
 - driverName: bigquery
 - dataSourceName: See data source name
 - table: Table to write to
 - batchSize: Number of parameters or columns that can be queued within each call to Exec (default is 10000)
import "sql"
data
 |> sql.to(
 driverName: "bigquery",
 dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
 table: "exampleTable",
 )
BigQuery data source name
The bigquery driver uses the following DSN syntaxes (also known as a connection string):
bigquery://projectid/?param1=value&param2=value
bigquery://projectid/location?param1=value&param2=value
Common BigQuery URL parameters
 - dataset - BigQuery dataset ID. When set, you can use unqualified table names in queries.
BigQuery authentication parameters
The Flux BigQuery implementation uses the Google Cloud Go SDK. Provide your authentication credentials using one of the following methods:
 - Set the GOOGLE_APPLICATION_CREDENTIALS environment variable to identify the location of your credential JSON file.
 - Provide your base-64 encoded service account, refresh token, or JSON credentials using the credentials URL parameter in your BigQuery DSN.
 Example credentials URL parameter
 bigquery://projectid/?credentials=eyJ0eXBlIjoiYXV0...

Flux to BigQuery data type conversion
sql.to() converts Flux data types to BigQuery data types.
Flux data type BigQuery data type
int INT64
float FLOAT64
string STRING
bool BOOL
time TIMESTAMP
Was this page helpful?
Thank you for your feedback!
Upgrade to InfluxDB Cloud or InfluxDB 2.0!
InfluxDB Cloud and InfluxDB OSS 2.0 ready for production.


text:
A Much Moved People:
Preserving Traditions of the Delaware Indians
On extended view
Main Building - Lower Level Gallery
Delaware Woman's Blouse with Silver Brooches (c.1810-80)
Cotton, cotton thread, silver and dye
Collected by anthropologist Frank G. Speck from the daughter of Chief Wooden Buffalo
Gift of Frank G. Speck
This exhibition offers visitors a glimpse into the lives of the Delaware Indians over a two hundred year time span. From the 1740s to the 1890s, many of New Jersey's Indians moved out of the state ahead of the ever-expanding non-Indian population. Artist and chronicler of American Indians, George Catlin (_PHONE_), noted as early as 1832 that the Delaware were among the most relocated Indians in the United States. This exhibition tells the story of these migrations.
In the late 1800s and into the 1900s, the Indians that remained in New Jersey survived by adapting to a market economy. They developed handcraft industries which produced items desired by non-Indian settlers. The Indians produced baskets and other woven items such as mats and brooms, as well as carved wooden pieces such as mortars and shovels.
The descendents of the Delaware Indians who left New Jersey, as well as those who stayed, continue to follow and adapt their cultural and religious traditions, thus preserving them for future generations and sharing them with all other cultures.
The objects on view, which date from the late 1700s to the early 1900s, include a woman's blouse with silver brooches, splint baskets, a wooden shovel, a leather pipe bag decorated with glass beads, children's moccasins and a child's basket.
The exhibition was made possible through funding support provided by PSEG Foundation, with additional generous support provided by the Friends of the New Jersey State Museum.


text:
The French plant phenomic network (FPPN)
PHENOME will provide France with an up-to-date, versatile, high throughput infrastructure and suite of methods allowing characterisation of panels of genotypes of different species under scenarios associated with climate changes. Phenotyping has become the major limitation in programmes aimed at building genotypes that maintain / increase crop performance under climate change and reduced inputs.
The project objectives are to:
- Build or upgrade highly instrumented platforms in seven French sites able as a whole to deal with the most important crop species, biological questions and environmental stresses
- Develop hardware and software applications with technological jumps, including the development of new sensors, methods, data analysis and databases able to cope with millions of data points
- Disseminate techniques and methods towards the French phenotyping community (seed companies, technical institutes, public research groups),
- Enhance emergence of French SMEs involved in the development of phenotyping methods.


text:
Extreme Simulation of C4ISR Communications and Networking
ULTRA CORP SYRACUSE NY
Pagination or Media Count:
The Internet is viewed by many to be the network of choice for worldwide communications. Indeed, as the Internet proliferates, one will have a global base from which to choose technologies and methods for building intra- and inter- network systems. This emerging information infrastructure comprises wire and wireless networks of vast complexity. A fundamental issue for military users, however, is how to describe the Internet so as to predict its behavior under various conflict scenarios. An unpredictable Internet would certainly contribute to the fog of uncertainty that inevitably accompanies command and control operations. In this paper we describe ongoing research that is focused upon modeling the Internet and simulating its behavior Extreme Simulation of C4ISR Communications and Networking project. Its objective is to demonstrate the feasibility of producing a Global Network Simulator GNS for Air Force C4ISR operations, focusing on the Internet for Air Force Operations within the Global Grid. Our approach employs hierarchical modeling abstraction techniques using object-oriented design and implementation a new parallel, discrete event simulation framework for large, scalable simulations and a database schema to specify input and system constructs at runtime.
- Computer Systems
- Radio Communications
- Command, Control and Communications Systems


text:
Potterton Commercial joins trend to centralised heating plant for residential blocks
Served by hot water from central plant, Potterton Commercial's Sirius 'heat box' is supplied with hot water from central plant and uses two plate heat exchangers to provide heating and hot water for individual dwellings in a residential block.
Potterton Commercial has responded to the trend towards centralised heating and hot-water solutions in multi-occupancy residential development with the launch of the Sirius SAT 'heat box'. These units provide heating and hot water for individual dwellings in a block of flats served by a central plant room. The benefits of this centralised method of providing heating and hot water include reduced installation costs, fewer flues and visible plumage and reduced costs for annual servicing of individual boilers. It is also easier to integrate low- and zero-carbon solutions with central plant, such as the Andrews Solarflo solar thermal system. There are eight sizes of Sirius SAT heat boxes. Their integral heat meters can transmit data wirelessly, enabling the consumption of heating and hot water in each dwelling to be monitored from a single position, reducing reading costs and avoiding potential reading mistakes. The consumption of energy in each dwelling is shown on a digital display to help encourage efficient use. Options include programmable room thermostat, weather-compensation module and DHW/cold-water meter and pipework loop.
For more information on this story, click here: Dec 08, 161


TY - GEN A1 - Polus, Łukasz A1 - Szumigała, Maciej A2 - Kuczyński, Tadeusz - red. PB - Zielona Góra: Oficyna Wydawnicza Uniwersytetu Zielonogórskiego N2 - In this paper a numerical analysis of the resistance and stiffness of the aluminium and concrete composite beam is presented. Composite aluminium and concrete structures are quite new and they have not been thoroughly tested. Composite structures have a lot of advantages. N2 - The composite aluminium and concrete beam is more corrosion-resistant, fire-resistant and stiff than the aluminium beam. The contemporary idea of sustainable buildings relies on new solutions which are more environmentally friendly. Aluminium is lighter and more resistant to corrosion than steel, which is often used in composite structures. L1 - _URL_ L2 - _URL_ KW - belka zespolona KW - belka betonowo-aluminiowa KW - analiza numeryczna KW - aluminium and concrete beam KW - composite beam KW - numerical analysis T1 - A numerical analysis of the resistance and stiffness of the aluminium and concrete composite beam = Analiza numeryczna nośności i sztywności belki zespolonej aluminiowo - betonowej UR - _URL_ ER -


text:
Образ судьи как риторическая категория и его отражение в решениях европейского суда по правам человека
The ancient rhetorical canon and the Russian rhetorical tradition, including pre-Soviet tradition of judicial rhetoric, considered 'orator/rhetor's character' as a central part of the ethical appeal, according to which the rhetor achieves the consent and adherence of the audience to his decisions when he possesses outstanding intellectual and moral characters. This is especially true when rhetors are persons who are vested with powers and authority, and thus can influence people due to their high position in the society. Judges inherently are influential rhetors, and they must be the epitome of the rhetorical ideal. The rhetorical character of a judge as a person of sound sense, high morals and benevolence found its reflection in the decisions of the European Court of Human Rights. More frequently the ECtHR refers to 'judge's discretion'. As far as it poses restrictions on public presentations made by a judge and prevents him from commenting the on-going trial proceedings, the equality of the participants in the act of communication is secured by the imposing restrictions also on other participants of communicative exchange – journalists, lawyers and parties to a case, who should restrain from insulting words and unsubstantiated personal attacks on judges, as well as avoid putting pressure on judges through formation of public opinion about how a certain case must be resolved by the court. The analysis of the judge's image from the point of view of the rhetorical ideal, where the judge is included in the communicative act of decision-making, stresses the importance of the positive image of judges and judiciary for the legitimization of the judicial decisions and support of public confidence in judicial power. However, the judge's image of vir bonus – a respected, honest and discreet person - should be supported not by silencing the cases of judge's wrongful behavior, but by judge's support of his image of vir bonus by his high morals and good behavior both inside and outside the courtroom. A judge must be a man of high ethical standards, not just seem to be the epitome of the rhetorical ideal.


text:
Every word you create becomes a clue that gets you one step closer to the mystery word!
How to Play WordSpector
Click on letters to create words; click Submit when you're done creating a word.
When your word appears on the board, the tiles will be colored to indicate how close you are to guessing the mystery word:
Green = The letter is correct & in the correct place.
Orange = The letter is in the mystery word, but in a different place.
Tan = The letter is not in the mystery word at all.
The fewer guesses it takes you to guess the mystery word, the more points you get.


text:
Section 7 - people from an ethnic minority
People from an ethnic minority are defined as those from an ethnic group other than 'white British'. They are treated as a particular group for the JSNA because it is important to ensure that the experiences and opportunities that affect people's health and well-being are not dependent on their ethnic background.
The key points from the 2011 JSNA relating to people from an ethnic minority in Herefordshire are as follows:
- Herefordshire has a relatively small, but growing, Black, Asian and Minority Ethnic (BAME) population: only 6% of residents were from a ethnic group other than 'white British' in 2009, but this is nearly one and a half times as many as in 2001 (compared to a growth of just 3% in the total population). By far the largest minority group (4,300) is 'white other than British or Irish'; which will include some of the county's estimated 800-900 Gypsies, Roma and Travellers as well as migrants who have settled in the county from Eastern Europe. See the ethnicity topic page for more details.
- Increasing numbers of births (200 in 2009) are to mothers born outside the UK, mainly in Poland and other Eastern European countries.
- Herefordshire continues to host several thousand temporary seasonal workers every spring and summer, mainly young men from Bulgaria, Romanian and Poland. Most are accommodated on the farms where they work, and many return year after year.
- Although the educational achievement of Herefordshire pupils is good overall, there are still significant attainment gaps between pupils from different ethnic groups, notably Gypsy, Roma and Traveller (GRT) children.
- A potential need for additional authorised pitches for Gypsies, Roma and Travellers in Herefordshire during the next ten years will require continued working with local communities.
Other relevant findings are:
- A survey of the health needs of over 200 seasonal migrant workers in 2008, mainly young adult males from Poland, Bulgarian and Romania, found that the vast majority (89%) felt they were in good or very good health. Only 5% said they had a disability, long-term illness or health problem which limited their daily activities or the work they could do - although 28% said they had back pain. 20% felt they faced barriers to healthcare - see the full report for more details.
- A similar survey of the health needs of just under 50 Gypsies, Roma and Travellers in Herefordshire found that a third felt their health was bad or very bad, which is much higher than for the general population. Just under half said they had a disability, long-term illness or health problem which limited their daily activities or work. Just over a third felt they faced barriers to healthcare. See the full report for more details.
Last updated: 21 September 2011


text:
Commercial Law Dissertation Proposal
The Retention of Title Clauses - 'a maze if not a minefield.'
Aims of commercial law
- To evaluate the effectiveness of the use Retention of Title (ROT) Clauses under UK Commercial Law and ask whether the proposed harmonization throughout the EU is necessary.
- To determine whether there are better systems of law that promotes the protection of the seller from non-payment through the use of ROT clauses, for example a codified system such as the US, Canada and New Zealand.
- To propose that there needs to be a reform of ROT clause under UK Commercial Law through a statutory system of protection for both the buyer and seller. Objectives:
- To explore the ROT clause decisions made by the UK courts in order to understand how the system of Commercial Law works in the UK. In order to determine the validity and effectiveness of the UK system in respect to protecting both the interests and rights of both the buyer and the seller.]
- To compare the UK's ROT clause case law with that of the ECJ's. In addition to considering the possibility of reform proposed in the UK and throughout the EU.
- To examine the different systems of Commercial Law to examine the most effective protection of ROT clauses. It will explore codified systems of law, such as Canada, the USA and New Zealand, and compare them with common law systems, such as the UK and Australia. The main objective of this examination is to determine which type of system is most effective in protecting the rights and interests of both the buyer and the seller.
'A maze if not a minefield' means that the law is so confusing that it is very hard to determine the rights of the buyer and the seller and even if a ROT clause seems valid it does not necessarily mean that the seller's interests will be upheld by the courts. Therefore the UK law seems to create a series of pitfalls for the seller when enforcing Retention of Title (ROT) clauses therefore this exploration will ask the central question:
"Is the UK's system of Commercial Law effective in protecting/enforcing ROT clauses?"
In order to do this the discussion will also consider the following questions:
- Whether there is a better system of law?
- Whether there is consistency in the current UK case law in comparison to other systems of law?
- Does the current UK in comparison to other systems of law overprotect the buyer or the seller?
- Finally should ROT clauses be upheld when there are other routes for the financial interests of the seller to be protected?
A Retention of Title (ROT) clause is used to protect the seller from buyers who do not pay for goods received. This is a clause for sellers to recover their goods if they do not pay, where the clause has to be within the terms and conditions of sale. They are also known as Rompala Clauses after the case of Aluminum Industrie Vassen BV v Rompala Aluminum Ltd . The main problem with ROT clauses is that when the seller comes to enforce them in many cases they are not upheld. The ROT must be expressly held in the terms and conditions and cannot be implied like many clauses in sales of goods, e.g. quality of goods or previous dealings. The ROT must be expressly written in the terms of sale and can be as simple as the title of the goods does not pass on to the seller until the goods are paid in full. The ROT is usually very detailed and the courts interpret them on a sentence to sentence basis to ensure that the buyer's rights are not being adversely affected.
The ROT clause is not used in all industries because with perishable items because the goods are no longer of use, whereas with large or expensive non-perishable items, such as cars or electronics an ROT clause is much more sensible. This is usually seen in instances of hire-purchase agreements, where in lieu of payment of good the company can reclaim the sold goods. The ROT must be part of the contract and therefore follow the valid form of a contractual clause and must be a part of a valid contract. Therefore the best route of action is to have the buyer to acknowledge the clause and sign in confirmation of the clause, rather than having it as a mere term and condition that is available on request and the buyer never sees the clause. It needs to be clear and express where both parties understand that if the goods are not paid in full then the seller can retain the goods. The problem of ROT clauses is whether they can be upheld only when follow the strict rules concerning whether they are express and the buyer had certain knowledge of their existence and are determined fair. If they are determined to be valid then in the case of insolvency they are the head of the distribution chain as per the SOGA 1979 Part V, which was confirmed in Borden v Scottish Timber Mills .
There are problems with ROT clauses is that if the goods are not identifiable and traceable in their original form then the goods cannot be reclaimed under the common law ; however under equity mixed goods can be reclaimed. This creates confusion under UK law in respect to what goods can be reclaimed by the reseller because under common law as opposed to equitable actions there is contradicting precedents. This contradiction points towards a need for there to be reform. Under the US, Canadian and New Zealand systems of law they have set up codified system of ROT clauses, for example Article 9 of the Uniform Commercial Code in the USA. In the UK there is the added problem of Article 220 of the Treaty of Rome which subjects UK law to the precedent of EU law and the moves towards harmonization of ROT clause throughout the EU. There is a need for reform especially in respect to recent developments in security law and the protection of interests, especially in respect to recent changes in insolvency law. This has been highlighted in Ireland's 1989 Law Commission Report also that common law system's need to be reformed to coincide with a more codified system of law otherwise the law is a confused mess, i.e. a maze if not a minefield.
This exploration will be concerned with the practical application of law to theory in the first three chapters this exploration will explore the history and use ROT Clauses in the UK. The first Chapter will consider ROT's - History and Use in the UK. The Second Chapter will consider the use of the ROT in the Modern Era in the UK. The third Chapter will consider the Problems and Benefits of the ROT in the Current UK system. It will then focus on four case studies, which will consider the case-law and differing judicial system's approach to ROT clauses. The first case study will compare the Use of the ROT in the UK and the EU in which this chapter (Chapter 4) will explore the supremacy of the EU law and the propositions for harmonization throughout the EU. The second case-study will explore ROT Cases in Codified Systems of Law, in Chapter 5 ROT cases in the US; Canadian; and New Zealand judicial arenas will be discussed in comparison to the UK. This third case-study in Chapter Six will be a Comparative Case Study of ROT Law in different Judicial Systems, i.e. what approach have other common law systems taken, c.f. Ireland and Australia. This case-study will conclude with a consideration of the different approaches of ROT case law in codified and common-law systems; as well as reform in common-law systems to determine the most effective approach of reform. The final two chapters will consider the theoretical need for reform in respect to the protection of the buyer and seller. Chapter Seven will discuss the current movements to protect the buyer as well as reforms in Insolvency law within the EU and ask the question ask Are ROT Clauses Necessary in UK law, especially when there are other forms of seller protection. The final chapter will conclude whether ROT Clause Reform is Necessary under UK Law by evaluating the theoretical problems and the comparative research of other jurisdictions to determine the effectiveness of ROT clauses in the UK and asking whether they are a maze if not a minefield.
- Young, 2002, Protecting and Registering Company Charges and Other Securities Part 1 & Part 2, 152 NLJ 1353 & 152 NLJ 1389
- Singleton, 1999, In Focus - The Passing of Risk and Title, CLT 22 10
- Rawlings, 2005, Recognition of Administration Proceedings Under EC Regulation, 21 IL and P 159
- Beale, 2004, Reform of the Law of Security, Journal of International Banking and Financial Law 117
- Burton, 2005, A Summary of some Key Points in R3's Response to the Law Commissions Proposals on Security Interests, 21 IL and P 69
- Ireland's Law Commission, 1989, Report on Debt Collection and Retention of Title, Law Reform Commission


Documentation Center
 - Trial Software
 - Product Updates
Laser Tracking
This example shows how to track a moving laser dot.
Using the Image Acquisition Toolbox™, image data streams from a camera are acquired directly into MATLAB®. These images are used to track objects in the camera's view. For this example, the object being tracked is the dot produced by a laser pointer.
The monitor of a computer running MATLAB is placed in the camera's view while a laser pointer shines a red dot on a MATLAB figure window. The camera is used to acquire images of the MATLAB figure window while the laser pointer moves around. By tracking the movement of the laser dot, the laser pointer can be used as a pointer device similar to a mouse.
The first task involves calibrating the data to establish a relationship between the acquired image pixels and the MATLAB figure axes. Once this relationship is established, the laser dot can be tracked as it moves around within the MATLAB figure window.
This example uses a set of utility functions that aid in the processing of images. These utility functions require the Image Processing Toolbox™ and can be found in the following directory:
 - MATLABROOT\toolbox\imaq\imaqdemos\html\laserTracking
Physical Setup
Focus a camera onto the screen of a computer that MATLAB is running on.
It is best to have the ambient light in the room minimized. This example has been successfully run in auditoriums using a projector.
Configure the Acquisition
An image acquisition device will be used to acquire image data to perform the calibration and laser tracking. The device used will be a generic Windows® video WebCam.
% Add the directory containing the utility functions to the MATLAB path.
utilpath = fullfile(matlabroot, 'toolbox', 'imaq', 'imaqdemos',...
 'html', 'applications', 'laserTracking');
% Access and configure a device.
vid = videoinput('winvideo', 1, 'RGB24_320x240');
set(vid, 'FramesPerTrigger', 1);
set(vid, 'TriggerRepeat', Inf);
Create the Calibration Screen
The calibration screen created is purposely set to black to get the best contrast for the laser pointer. Some systems work better when the window's colors are set dark for the title bars.
Since a red laser will be used, the red plane of the image is the only color plane of interest. The calibration square is made blue in order to make it appear "invisible" in the red plane.
% Create the laser figure window.
laserFig = figure;
hBox = plot([0 0 1 1 0], [0 1 1 0 0], 'b-');
hold on
% Set up calibration screen. Modify the cursor so it does not
% interfere with the calibration.
hTarget = plot(0, 0, 'yo');
set(gca, 'Color', [0, 0, 0]);
set(laserFig, 'Color', [0, 0, 0], 'Menubar', 'none',...
 'DoubleBuffer', 'on', 'Pointer', 'custom',...
 'PointerShapeCData', repmat(NaN, 16, 16));
Position the Camera
Position the camera such that only the blue square is visible.
% Display positioning information.
posText = sprintf('%s\n%s',...
 'Position the camera and ensure the blue box',...
 'is the only thing in the camera''s view.');
infoText = text(0, -0.2, posText, 'Color', [1 1 1]);
axis([-0.2 1.2 -0.2 1.2])
% Using the preview window, request that the camera be positioned such
% that the view is of the blue box and little else.
smallFigPos = get(laserFig, 'Position');
set(laserFig, 'Position', get(0, 'ScreenSize'));
disp('Waiting for camera to be any key to continue.')
Waiting for camera to be any key to continue.
Perform Image Calibration
Now that the camera is focused on the right area, a target is drawn at each of the four corners of the box. The calibration is performed by aiming the laser on each corner of the blue square, allowing a relationship to be established between the camera pixel coordinates (the image) and MATLAB axis coordinates (the square). For each target displayed:
 - output a sound indicating the laser should be aimed
 - output a sound indicating a frame is about to be acquired
 - trigger the acquisition device
 - access the acquired image frame and determine the laser position in pixel coordinates
The laser position is determined by thresholding the red plane and looking for high intensity values. Some additional processing is performed to make sure the laser is not obscured by ghost images caused by poor optics in some WebCams. It is also verified that a laser dot was actually present on the screen.
% Provide calibration instructions.
calibText = sprintf('%s\n%s',...
 'Aim the laser pointer on each target as it appears.',...
 'Hold the laser on the target until the target moves.');
set(infoText,'string', calibText);
% Start the acquisition and create a new figure to display
% calibration results in a MATLAB SPY plot.
spyFig = figure;
% Target 1...
set(hTarget, 'Xdata', 0, 'Ydata', 0);
sound(1), pause(2)
sound(1), trigger(vid);
acqResults{1} = getdata(vid, 1);
[xCalib(1), yCalib(1), laserSights] = util_findlaser(acqResults{1});
title('Target 1: Suspected Laser Sighting')
% Target 2...
set(hTarget, 'Xdata', 0, 'Ydata', 1);
sound(1), pause(2)
sound(1), trigger(vid);
acqResults{2} = getdata(vid, 1);
[xCalib(2), yCalib(2), laserSights] = util_findlaser(acqResults{2});
title('Target 2: Suspected Laser Sighting')
% Target 3...
set(hTarget, 'Xdata', 1, 'Ydata', 1);
sound(1), pause(2)
sound(1), trigger(vid);
acqResults{3} = getdata(vid, 1);
[xCalib(3), yCalib(3), laserSights] = util_findlaser(acqResults{3});
title('Target 3: Suspected Laser Sighting')
% Target 4...
set(hTarget, 'Xdata', 1, 'Ydata', 0);
sound(1), pause(2)
sound(1), trigger(vid);
acqResults{4} = getdata(vid, 1);
[xCalib(4), yCalib(4), laserSights] = util_findlaser(acqResults{4});
title('Target 4: Suspected Laser Sighting')
% Close the SPY plot and stop the acquisition.
Calibration Results
Plot the acquired image and the calculated laser pointer coordinates for each target. Since the yellow crosshairs are positioned at the proper location in each image, the processing results are validated.
% Target 1 results...
calibFig = figure;
util_plotpos(acqResults{1}, xCalib(1), yCalib(1));
% Target 2 results...
util_plotpos(acqResults{2}, xCalib(2), yCalib(2));
% Target 3 results...
util_plotpos(acqResults{3}, xCalib(3), yCalib(3));
% Target 4 results...
util_plotpos(acqResults{4}, xCalib(4), yCalib(4));
% Close the figure illustrating calibration results.
Laser Tracking
Start the acquisition and process the acquired data a set number of times. The processing consists of locating the laser in the acquired image and determining the laser positions in pixel and MATLAB axis coordinates.
In order to make things interesting, using the laser pointer, attempt to "draw" the letter 'M' (for MATLAB) within the blue box.
% Update instructions on laser screen.
set(infoText,'string', 'Move the laser pointer within the blue box.');
% Start the acquisition. For each iteration:
% * output a sound to indicate a frame is about to be acquired
% * trigger the device
% * process the acquired image and locate the laser
% * convert pixel coordinates to MATLAB axis coordinates
laser.x = [];
laser.y = [];
for i = 1:100,
 % Acquire an image frame and determine the
 % camera pixel coordinates.
 sound(1), trigger(vid);
 frame = getdata(vid, 1);
 [x, y] = util_findlaser(frame);
 if ~isnan(x) && ~isnan(y),
 % If coordinates were valid, ensure the camera pixel coordinate
 % was in the calibration range.
 x = max([x min(xCalib([1 2]))]);
 x = min([x max(xCalib([3 4]))]);
 y = min([y max(yCalib([1 4]))]);
 y = max([y min(yCalib([2 3]))]);
 % Determine spatial transformation from the unit square calibration points.
 tform = cp2tform([xCalib(:) yCalib(:)], [0 0; 0 1; 1 1;


d to sqleventlog_sp could be a value in this table, more about this later.
lcid is the language id. LCID ("Locale ID") is a Windows concept, and the LCID I use here are the same as in Windows. Yes, above I said that I use the language setting in SQL Server, but I still use Windows LCIDs, and this part you should keep. The only question is whether you should use the full LCID, or only the lower part. To wit, an LCID in Windows consists of two bytes. The lower byte identifies the language, for instance 9 is English and 29 is Swedish. The upper byte identifies the variety. E.g., 1033 (0x0409) is English (United States) and 2057 (0x0809) is English (United Kingdom). In our system, we use only the lower byte, but if you think that it is important that right-ponders see colour and left-ponders see color, you will need to use the full LCID. In this article I have opted to use the latter, but that is mainly because it made my code simpler.
msgtext is the message to present to the user for the language in question. The message can have parameter markers %1 to %6 just like the @msgtext parameter to sqleventlog_sp.
When you pass a value for the @msgid parameter to sqleventlog_sp, the procedure retrieves the current language for the session (which is returned by the system function @@langid) and translates it to an LCID is sys.syslanguages. (And again, in real life, the LCID would be read from a users table.) Since there may not be translations for all languages for a message id, the procedure also looks up the default language for the server from sys.configurations to use this as a fallback. Ah, yes, the fallback, this is worth dwelling on for a few moments. In our system, the fallback language is installation-dependent and defined in our system-parameter table. You may want to do something like that. Or simply hardcode to always use English, Russian or whatever depending on your market. You can also have multiple fallbacks. Say that you install a system in Barcelona, and you don't (yet) have all Catalan translations in place, so for Catalan users, you first fall back to Spanish and then to English which is your own base language.
sqleventlog_sp looks up the message text in usermessages, and this message, with parameters expanded, is presented to the user. Note that sqleventlog_sp always stores what is in @msgtext in the sqleventlog table; @msgid only matters for the message raised by sqleventlog_sp. If @msgid yields no hit in usermessages for neither language, sqleventlog_sp uses @msgtext as the error message. That is, sqleventlog_sp never returns a navel-gazing error message saying that the message id was not found, but @msgtext is the ultimate fallback. sqleventlog_sp always stores what you pass in @msgid in the msgid column in the sqleventlog table, even if @msgid is absent from usermessages. (That is, there is no foreign-key constraint to usermessages.) This permits you to use msgid for aggregation or other analysis of the log, even if you don't use the usermessages table.
Here are a couple of examples, using the two sample messages included in usermessages_tbl.sql. Of these the first message has five translations, including English, Italian and French, whereas the second message exists in English and Italian only. The last message uses a message id which is not among the sample messages:
SET LANGUAGE us_english
EXEC slog.sqleventlog_sp @@procid,
 'This is my right hand in English', @msgid = 'RightHand'
SET LANGUAGE Italian
EXEC slog.sqleventlog_sp @@procid,
 'This is my right hand in Italian', @msgid = 'RightHand'
SET LANGUAGE Français
EXEC slog.sqleventlog_sp @@procid,
 'This is my right hand in French', @msgid = 'RightHand'
SET LANGUAGE us_english
EXEC slog.sqleventlog_sp @@procid,
 'Customer "%1" not found (English)', @msgid = 'NoCust',
 @p1 = 'Ricky Lancelotti'
SET LANGUAGE Italiano
EXEC slog.sqleventlog_sp @@procid,
 'Customer "%1" not found (Italian)', @msgid = 'NoCust',
 @p1 = 'Ricky Lancelotti'
SET LANGUAGE French
EXEC slog.sqleventlog_sp @@procid,
 'Customer "%1" not found (French)', @msgid = 'NoCust',
 @p1 = 'Ricky Lancelotti'
EXEC slog.sqleventlog_sp @@procid,
 'This is our extra undefined message', @msgid = 'Extra'
SELECT TOP (7) logid, msgid, msgtext
FROM slog.sqleventlog
ORDER BY logid DESC
The output is:
Changed language setting to us_english.
Msg 50000, Level 16, State 1, Procedure sqleventlog_sp, Line 183
This is my right hand
L'impostazione della lingua è stata sostituita con Italiano.
Msg 50000, Level 16, State 1, Procedure sqleventlog_sp, Line 183
Questo è la mia mano destra
Le paramètre de langue est passé à Français.
Msg 50000, Level 16, State 1, Procedure sqleventlog_sp, Line 183
Ceci est ma main droite
Changed language setting to us_english.
Msg 50000, Level 16, State 1, Procedure sqleventlog_sp, Line 183
Customer "Ricky Lancelotti" not found.
L'impostazione della lingua è stata sostituita con Italiano.
Msg 50000, Level 16, State 1, Procedure sqleventlog_sp, Line 183
Cliente "Ricky Lancelotti" non c'è.
Le paramètre de langue est passé à Français.
Msg 50000, Level 16, State 1, Procedure sqleventlog_sp, Line 183
Customer "Ricky Lancelotti" not found.
Msg 50000, Level 16, State 1, Procedure sqleventlog_sp, Line 183
This is our extra undefined message
logid msgid msgtext
-------- ----------- ----------------------------------------
7 Extra This is our extra undefined message
6 NoCust Customer "Ricky Lancelotti" not found (French)
5 NoCust Customer "Ricky Lancelotti" not found (Italian)
4 NoCust Customer "Ricky Lancelotti" not found (English)
3 RightHand This is my right hand in French
2 RightHand This is my right hand in Italian
1 RightHand This is my right hand in English
In these examples, @msgtext was close to the English text for the message id. But this does not always have to be the case. You may have a generic message id for which the text in usermessages reads Internal error. Call the support desk in various languages, while the real error message is passed in @msgtext so that developers and support staff can see what happened, while the user is saved from what may be incomprehensible mumbo-jumbo to them.
Note also the last two messages in the example. The message NoCust is not available in French, which is why the English version is displayed. There is no message Extra at all in usermessages, but the id is stored in the msgid column nevertheless.
The localisation part of SqlEventLog includes one more table. Say that you have a function where users can monitor the table sqleventlog to see errors in the system. The same thing may apply here: users want to see a message in their own language, not whatever the developer used in the call to sqleventlog_sp. But obviously, they want to see the message with %1 etc replaced by the actual parameter values. To this end, SqlEventLog stores the parameter values in this table:
CREATE TABLE slog.sqleventlogparameters(
 logid bigint NOT NULL,
 paramno tinyint NOT NULL,
 value nvarchar(400) NOT NULL,
 CONSTRAINT pk_sqleventlogparameters PRIMARY KEY (logid, paramno),
 CONSTRAINT fk_sqleventlogparameters
 FOREIGN KEY (logid) REFERENCES slog.sqleventlog(logid)
)
logid is of course a reference to the message


JSONObject) to link it all together.

Tapestry packages up all those addInitializerCall() initializations into one big block that executes at the bottom of the page (and does something similar for Ajax-oriented partial page updates).
Whew! To make this works requires that elements have unique ids (which can be a challenge when there are Ajax updates to the page). On top of that, the typical behavior is to create controller objects and attach event handlers directly to the elements; that works fine for small pages, but if there are hundreds (or thousands) of elements on the page, it turns into quite a burden on the JavaScript environment: lots of objects.
 There isn't a specific name for this approach, beyond perhaps "crufty". Let's call it active initialization.
 A more modern approach is more passive. In this style, the extra behavior is defined primarily in terms of events an element may trigger, and a top-level handler for that event. The events may be DOM related such as "click", "change", or "focus", or application-specific one triggered on the element directly. The top-level handler, often attached to the document, handles the event when it bubbles up from the element to the top level; it often distinguishes which elements it is interested using a CSS selector that includes references to a data- attribute.
For example, in the core/forms module, we need to track clicks on submit and image buttons as part of the form (this is related to supporting Ajax form submissions).


8
In the file app/code/core/Mage/Eav/Model/Entity/Collection/Abstract.php, there is a function named joinField and there is another joinTable.
If fields are actually columns in the flat tables, what does it mean to join them? An in what circumstance I should use joinTable instead? Can they both be used interchangeably?
5
Both methods are almost identical, the difference is that joinField() only selects a single column from the joined table, while you can specify an array of columns in joinTable'.
So you can always use joinTable instead of joinField. The example
 joinField('country_name', 'directory/country_name', 'name', 'country_id=shipping_country', "{{table}}.language_code='en'", 'left')
is the same as
 joinTable('directory/country_name', 'country_id=shipping_country', ['country_name' => 'name'], "{{table}}.language_code='en'", 'left')
But joinField() should not be used if you need more than one column of the joined table.
|improve this answer|||||
Your Answer
By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy
Not the answer you're looking for? Browse other questions tagged or ask your own question.


text:
Measure, Assess, and Improve Your Performance
JCI standards serve as the foundation of an evaluation process that can help health care organizations like yours measure, assess, and improve performance.
It's our goal to develop standards that promote quality and ensure patient safety. JCI standards set clear expectations for organizations that are reasonable, achievable, and measurable. The standards are developed and organized around important functions common to all health care organizations.
JCI develops standards with input and information from:
- Health care organizations
- Subject matter experts
- Scientific literature and industry guidelines
- Technical Advisory Panels
- Other key stakeholders
Joint Commission International standards specify that organizations must collect data as part of their quality improvement system. To comply with these standards, the organization's leadership selects well-defined, evidence-based measures that are applicable to the organization's patient populations and services. With the retirement of Joint Commission International's Library of Measures, JCI accredited hospitals could consider using The Joint Commission's performance measures for guidance on collecting data.
Learn about performance measure resources by visiting The Joint Commission's (TJC) performance measurement page.


text:
Legislation Governing Skip Permits
The placement of skips and containers on the highway is governed by the Highways Act 1980 Section 139.
Within this a local authority is given discretion to determine the following:
- The siting of the skip:
- Its dimensions.
- The manner in which it is to be coated with paint and other material for the purpose of making it immediately visible to oncoming traffic;
- The care and disposal of its contents;
- The manner in which it is to be lighted or guarded;
This means that each local authority does have its own interpretation of what constitutes a skip, how it should be marked, located and lighted.
Specification of a builders skip
Within the regulations A Builders Skip means a container designed to be carried on a road vehicle and to be placed on a highway or other land for the storage of builders materials or the removal and disposal of builders rubble, waste, household and other rubbish or earth and shall when carried on a road vehicle comply with the appropriate Motor Vehicle Construction and Use Regulations.
In Bradford for example a skip is defined as a container that shall not exceed 5m in length and 2m in width.Whereas in Newcastle for example a 20ft storage container will be managed under a skip permit.Some Councils have a scale of charges depending on the size of the skip and others have a single price for any size.
As a minimum:
- The builders' skip shall be clearly and permanently marked with the owner's name and with his telephone number or address.
- The container should be clearly visible at all times with vertical red and yellow fluorescent reflective markings at each end in accordance with the Builders Skips (Markings) Regulations 1984 (SI 1984/1933) (effective 1 January 1986) and BSS All _PHONE_.
- If on a highway then cones and lights are required to comply with Chapter 8 of the Traffic Signs Manual and the ends shall be painted yellow. During the hours of darkness the owner shall provide, maintain and light four yellow lamps, fixed securely to the skip(s), one to each corner.
- The skip(s) shall be placed in such a position as to be clearly visible to traffic approaching from either side at a distance of not less than 100m (330ft)
- It shall neither be placed within a distance of 30m (100ft) from a road junction nor in such a position to block any sight line at an entrance, junction or bend nor to impede surface water drainage not obstruct access to property, fire hydrants, gullies, manholes and apparatus of any
- Statutory Undertaker, nor be placed in such a position as to contravene any Traffic Order or regulation made under the Road Traffic Acts. It/they shall, when sited in the carriageway, be placed near the edge of the carriageway with the longer side parallel thereto.
- It/they shall not be placed in such a position as to partly or wholly obstruct a footway without the express permission of the Strategic Director for Environment & Infrastructure or his representative, to be granted only after consultation and agreement with the Police and conditional upon a 1m. wide pedestrian walkway being provided in the carriageway properly protected and signed and with yellow lights lighted at night.
If a local authority deems that the skip falls outside of their interpretation of section 139 for a builders skip then they will often cite Highways Act 1980 section 169 which can be summarised:
A license is required where building, demolition work or the alteration, repair, maintenance or cleaning of any building, requires to erect or retain on the highway any scaffolding or other structure which obstructs the highway (hereafter in this section referred to as a "relevant structure").
The container is being considered as a 'Relevant structure'. The requirements of this Relevant Structure vary dependent on the local authority. Some may treat this as a construction site requiring hoarding, cones and illumination. Others may simply require a hoarding license.
What To Do
For every site we need to establish the ownership of the land upon which skips or containers are placed. Housing association land is most likely to be owned by the council and will require a permit.
Please notify Red Kite Recycling of any intended site at least a week in advance in order to determine ownership with the council, provide quotes for Purchase order, apply for any permits and order skips.


text:
In places where access is needed to the space above the suspended ceiling modular suspended ceiling systems are often chosen. Today a wide range of materials and designs are available. The traditional visible system is only one of the many possibilities. Typical for most systems are the modular dimensions, multiples of 30cm in most cases 60 cm .
There are suspension systems suited for a variety of panels allowing to create ceilings with specific appearances and properties. There are panels available with specific properties as for example sound absorption, sound insulation or impact resistance made out of a variety of materials as mineral wool, gypsum, wood, metal or wood-based materials each having their specific appearances.
In line with the chosen ceiling panel the appropriate suspension system has to be chosen.
It has to be suited for the load, should have sufficient stability and dimensional accurate. A system for concealed installation for example has to be more stable and needs to be more accurate than a system for lay-in panels
When a suspension system is selected and designed attention should be paid to both system and suspension load bearing capacity. Sufficient safety needs to be guaranteed.
Depending the type of application it may be necessary to select a system with specific properties as for example additional corrosion protection or impact resistance.


text:
In the evolving world of design, Figma has emerged as a powerhouse. With its collaborative capabilities and robust features, it's no surprise that Figma has become the go-to tool for many web designers. However, due to some limitations of the tool, designers often find themselves creating artworks outside of Figma, typically in software like Adobe Illustrator CC or Affinity Designer. This then requires the artwork to be imported back into Figma, making the seamless compatibility of these platforms crucial.
Round 01: Vector Objects with Gradient Color
The process of transferring vector objects adorned with gradient colors across these platforms is straightforward and accurate. Whether moving from Adobe Illustrator CC to Affinity Designer or Figma, the fidelity of the gradients, including the color codes, is impeccably maintained. Similarly, Affinity Designer proves its compatibility with Figma in this regard.
However, an interesting observation is the difference in layer complexity when importing from Adobe Illustrator CC and Affinity Designer into Figma. It seems that Affinity Designer tends to generate slightly more intricate layer structures.
Round 02: Live Text
When it comes to live text, Adobe Illustrator CC and Affinity Designer have proved to be compatible. However, if you're copying live text from Adobe Illustrator CC to Figma, the text converts into a bitmap image, making it uneditable in Figma. Conversely, copying live text from Affinity Designer to Figma poses no such issue.
Round 03: Stroke with Different Weights
The compatibility of stroke weights across these platforms is excellent. Whether you're copying and pasting from Adobe Illustrator CC to Affinity Designer or Figma, or from Affinity Designer to Figma, the color and stroke weight remain exactly the same.
Important Points to Note
Unfortunately, it's currently not possible to copy anything from Figma to Adobe Illustrator or Affinity Designer. This is a limitation that hopefully will be addressed in future updates.
The compatibility between Figma, Adobe Illustrator CC, and Affinity Designer plays a significant role in the design process, and understanding these nuances can aid in a smoother, more efficient workflow. With continuous software updates and improvements, we can look forward to even more seamless design collaborations in the future.


ICBA - Online Education Courses - Online: Introduction to Consumer Lending
Online: Introduction to Consumer Lending
Consumer lending is a cornerstone of the U.S economy. Customers need access to credit to purchase goods such as cars and services such as education. When goods and services are purchased, jobs are created and the economy grows.
This course will provide you with an introduction consumer lending in the United States by discussing the history of consumer credit, different types of consumer loan and credit criteria.
This program containes1 module(s)
1 CPE Credit(s)
Category: Compliance - Bank Specific
Please log in to view course prices
Add to Cart
Find more courses


text:
April 19, 2006 - Refuge fire crew assists Stillwater NWR with emergency prescribed burn
Heavy rains and increasing snow melt resulted in pressure for quick measures to move large quantities of water through Stillwater National Wildlife Refuge. The refuge has a series of canals designed to facilitate just such an effort, however a major section was thickly overgrown with tule reeds and posed a risk of clogging and potential flooding. A crew from Klamath Basin traveled to Fallon, NV, and burned nearly 10 miles of canals, significantly reducing the thick vegetation and increasing flow ability. Weather and holding conditions permitted the crew only two days of burning before new rains inundated roads and limited access. Refuge managers report the burns increased their ability to safely deliver water through the refuge.
See pictures from the burn on the Stillwater NWR Stills page.


text:
Hydraulic Calculation for Pigging System for Fluid Transfer
FPEC has developed a PC program to calculate the pressure required for pigging system, pipe cleaning by use of a pig, oil transfer, washing with water etc., The fluid transfer pattern as shown in the figure below can deal with. For example, liquid/liquid is corresponding to oil transfer by different kind of oil, gas/liquid to oil drain out by N2 gas, etc.
Furthermore, it can be used when controlling the pressure of receiver. Please contact us if you need to calculate the pressure for pigging system.
Applicable Flow Patterns
Our program can applicable for all of the below flow patterns.
Liquid discharge from pig receiver
When discharge fluid from the pig receiver, it may discharge to the atmosphere or store in a tank. Also, when discharging, two cases may be considered. First one is that pressure of the receiver is adjusted by its outlet valve in order to control the discharge volume, and the second is direct discharge to the atmosphere without controlling the pressure. The pressure required for the pig system differs depending on the discharge method. Our program supports any release method.


text:
Comparison of prevalence of schizophrenia among residents of hostels for homeless people in 1966 and 1992.
OBJECTIVE: To determine whether the prevalence of schizophrenia among the homeless population of Edinburgh resident in hostels has changed between 1966 and 1992. DESIGN: Comparison of two cross sectional surveys. SETTINGS: Hostels for homeless people in Edinburgh. SUBJECTS: In 1966 a random sample of 98 residents of three common lodging houses. In 1992 a random sample of 198 residents of nine hostels. MAIN OUTCOME MEASURE: Prevalence of schizophrenia. RESULTS: The prevalence of schizophrenia...Expand abstract
- Publication status:
- Publisher copy:
- Copyright date:


Click here to view the latest version of this page.
C++ Boost
Chrobak-Payne Straight Line Drawing
template
void chrobak_payne_straight_line_drawing(const Graph& g,
 PlanarEmbedding perm,
 ForwardIterator ordering_begin,
 ForwardIterator ordering_end,
 PositionMap drawing,
 VertexIndexMap vm
A straight line drawing of a planar graph is a plane drawing where each edge is drawn using a straight line segment. Since all edges are line segments, the drawing is completely determined by the placement of vertices in the plane. chrobak_payne_straight_line_drawing uses an algorithm of Chrobak and Payne [71] to form a straight line drawing of a planar graph by mapping all n vertices in a planar graph to integer coordinates in a (2n - 4) x (n - 2) grid.
The input graph passed to chrobak_payne_straight_line_drawing must be a maximal planar graph with at least 3 vertices. Self-loops and parallel edges are ignored by this function. Note that the restriction that the graph be maximal planar does not mean that this function can only draw maximal planar graphs (the graph pictured above is not maximal planar, for example). If you want to draw a graph g, you can create a copy g' of g, store a mapping m of vertices in g' to vertices in g, triangulate g', and then send g' in as the input to chrobak_payne_straight_line_drawing. The drawing returned can then be applied to g using m to translate vertices from one graph to another, since g contains a subset of the edges in g'.
If the vertex index map provides constant-time access to indices, this function takes time O(n + m) for a planar graph with n vertices and m edges. Note that in a simple planar graph with f faces, m edges, and n vertices, both f and m are O(n).
Where Defined
IN: Graph& g
IN PlanarEmbedding embedding
A Readable Property Map that models the PlanarEmbedding concept.
IN ForwardIterator
A ForwardIterator that has value_type equal to graph_traits::vertex_descriptor.
OUT: PositionMap
A Writable LValue Property Map that models the Position Map concept. The Position Map concept requires that the value mapped to be an object that has members x and y. For example, if p models PositionMap and v is a vertex in the graph, p[v].x and p[v].y are valid expressions. The type of x and y must be implicitly convertable to std::size_t.
IN: VertexIndexMap vm
Default: get(vertex_index,g)
See Also
Copyright © 2007 Aaron Windsor (