{% extends "base_generic.html" %} {% load static %} {% block content %}
Welcome to LocalLibrary, a very basic Django website developed as a tutorial example on the Mozilla Developer Network.
The tutorial demonstrates how to create a Django skeleton website and application, define URL mappings, views (including Generic List and Detail Views), models and templates.
An UML diagram of the site's Django model structure is shown below.
The library has the following record counts:


Felicia's Journey (1999)
A Film Review by Mark O'Hara
Visit Online Film Critics Society at http://www.ofcs.org
In FELICIA'S JOURNEY, Canadian director Atom Egoyan has created a quiet and horrifying masterpiece. Lead actor Bob Hoskins has said about his experience shooting the picture, "There are some terrible moments in the film, but I had to play them." Hoskins also described his character, Hilditch the catering manager, as "a mixture of Jack the Ripper and Winnie the Pooh."
Felicia is a young Irish woman who has left her condemning father and set off to England to find the boyfriend who has abandoned her. In her quest to find Johnny, Felicia begins to scour factories where she believes he might be working. Though she is unsuccessful, she finds encouragement in the kind Mr. Hilditch, a quiet and proper man who keeps happening across her in various places.
Viewers catch a hint of a dark side in Hilditch when in a conversation to Felicia, he mentions his wife. Because we have already seen the single man in his empty house, we sense his agenda is twisted. When Egoyan introduces pieces of videotape that Hilditch has made of various girls riding in his car, we begin to trace an unspeakably evil pattern. This man creates scenarios that lure "lost girls" into his life; when they gain some relief from his kindness and begin to depart, Hilditch drugs and murders them.
So we know relatively early that things are amiss within Hilditch's motives. What's fascinating is the way the film studies this repulsive character, bringing out extreme frailty and loneliness within such a maniac. And just as the filmmaker has attended to numerous details in the script and set decoration and character history, Hoskins carries off a masterful depiction of humanity forsaken.
Bob Hoskins is the only actor I can picture playing Hilditch. For this character Hoskins has created a monster who manages to compose himself enough to get through one lonely day after another. Hilditch seems compulsive in everything: hair neatly combed, tie and vest always in their proper place, the man seems the quintessential British gentleman; he even uses the stereotype of endurance as part of his terrible ruse. Talking about his fictional late wife, he tells Felicia he must go on, chin up in the face of hardship. In all the mannerisms he lends to the character, Hoskins is brilliant. Particularly interesting are the moments in which we can see triggers being set off within Hilditch's psyche. In one scene in the hospital where he has told Felicia his wife is dying, Hilditch glimpses an old movie on a television in a waiting room. Suddenly we see Hilditch as a boy, sitting beside his mother in a movie palace. The film shows John the Baptist's head on a platter, the horrible queen examining it. In the balcony Hilditch's mother hands him her opera glasses so that he might see the horrid spectacle more closely. Though he is appalled, the boy watches, fascinated. What a telling scene! An attractive seductress who is cold at heart but who can be immensely charming - this was the woman who inflicted quite a bit of damage on her son. Watch the snatch of old movie, Hilditch freezes in revolting reverie. Although Hilditch's history is a document of premeditated evil, some of his emotions are easier to understand because of the care taken by William Trevor and Atom Egoyan in sketching in Hilditch's backstory.
Elaine Cassidy, a relative newcomer to film, plays Felicia with great understatement. It's almost a tone of passivity caused by innocence and politeness that she creates - a tone that causes her plight in the story to be more frightening. Cassidy works well with Hoskins, both actors knowing when to pause to underscore ideas with just the right intensity. Watching these two work, one never feels an insult to the intelligence.
In the grainy flashbacks - scenes from the cooking show as well as more private shots of little Joey Hilditch discovering a wallet and stealing money - we see a few of the causes of Hilditch's psychosis. The mother, Gala, is played by Egoyan's wife, actress Arsinee Khanjian. Lovely but exploitative, Gala appears to use her boy as an adorable on-camera sidekick. In a memorable scene, she places a chunk of liver in Joey's mouth, and the boy gags; watching a tape of this embarrassment, the adult Hilditch again gags; his sense of history nags that strongly at him. In all of her scenes, Khanjian is the perfect, subtle siren.
In a memorable supporting role, Claire Benedict plays Miss Calligary, a fervent door-to-door evangelist. Her presence adds just a bit of humor to the narrative, as she spouts her flowery Biblical rhetoric. Near the closing of the film her aggression of the spirit causes a sort of epiphany in Hilditch. It's a dark comic moment that could have been written by Flannery O'Connor, the most perverted recesses of the human heart tugged suddenly into the open.
Irish novelist William Trevor penned the book that was adapted by Egoyan. What's original about his adaptation is that Egoyan manages to avoid clichés about serial killers.  One room is dedicated to her image; it's a repository of souvenirs from her television cooking show, photographs of herself, even relics like an old blender that Hilditch resurrects when his blender malfunctions. Attention to detail sets the story going in a very well-developed direction.
FELICIA'S JOURNEY is rated PG-13 for dark subject matter, though there are no real scenes of violence, and no profanity. Because of its unsettling nature, I would not recommend it for children under 12. Its pace is necessarily slow at times, filling out various dimensions of Hilditch's character or Felicia's background. Unfortunately, its status as an art film will not gain it wide release; but it is worth a trip to a nearby city art house. The bottom line: it is a superior character study that will engage you for every minute of its run, but it is a disturbing film you may not go out of your way to watch a second time.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Class Users
Your games will not authenticate users by using their username and password. Instead, users have a token to verify themselves along with their username.
Inherited Members
Namespace: GameJolt.Services
Assembly: GameJolt.dll
Syntax
public sealed class Users : Service
Methods
| Improve this Doc View SourceAuth(String, String, Action<Response<Credentials>>)
Authenticates the user's information. This should be done before you make any calls for the user, to make sure the user's credentials (username and token) are valid. The callback is called with the authenticated user credentials or null if the authentication has failed.
Declaration
public void Auth(string name, string token, Action<Response<Credentials>> callback)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | name | The user's username. |
| System.String | token | The user's token (not his password!) |
| System.Action<Response<Credentials>> | callback | Action that is called on completion or error. |
AuthAsync(String, String)
Authenticates the user's information. This should be done before you make any calls for the user, to make sure the user's credentials (username and token) are valid. When the returned is awaited, the resulting Credentials object can be used to perform user queries.
Declaration
public Task<Response<Credentials>> AuthAsync(string name, string token)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | name | The user's username. |
| System.String | token | The user's token (not his password!) |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<Response<Credentials>> |
Fetch(Int32, Action<Response<User>>)
Returns a user's data, like name, id, avatar, etc.
Declaration
public void Fetch(int id, Action<Response<User>> callback)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Int32 | id | The user's GameJolt id. |
| System.Action<Response<User>> | callback | Action that is called on completion or error. |
Fetch(Int32[], Action<Response<User[]>>)
Returns the data for several user's at once.
Declaration
public void Fetch(int[] ids, Action<Response<User[]>> callback)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Int32[] | ids | Array of user ids. |
| System.Action<Response<User[]>> | callback | Action that is called on completion or error. |
Fetch(String, Action<Response<User>>)
Returns a user's data, like name, id, avatar, etc.
Declaration
public void Fetch(string name, Action<Response<User>> callback)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | name | The user's username. |
| System.Action<Response<User>> | callback | Action that is called on completion or error. |
FetchAsync(Int32)
Returns a user's data, like name, id, avatar, etc.
Declaration
public Task<Response<User>> FetchAsync(int id)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Int32 | id | The user's GameJolt id. |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<Response<User>> |
FetchAsync(Int32[])
Returns the data for several user's at once.
Declaration
public Task<Response<User[]>> FetchAsync(int[] ids)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Int32[] | ids | Array of user ids. |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<Response<User[]>> |
FetchAsync(String)
Returns a user's data, like name, id, avatar, etc.
Declaration
public Task<Response<User>> FetchAsync(string name)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | name | The user's username. |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<Response<User>> |


|
AWS IoT Device SDK C++ v2 1.14.0
AWS IoT Device SDK C++ v2
|
#include <GreengrassCoreIpcModel.h>
Public Member Functions | |
| GetSecretValueResponse () noexcept | |
| GetSecretValueResponse (const GetSecretValueResponse &)=default | |
| void | SetSecretId (const Aws::Crt::String &secretId) noexcept |
| Aws::Crt::Optional< Aws::Crt::String > | GetSecretId () noexcept |
| void | SetVersionId (const Aws::Crt::String &versionId) noexcept |
| Aws::Crt::Optional< Aws::Crt::String > | GetVersionId () noexcept |
| void | SetVersionStage (const Aws::Crt::Vector< Aws::Crt::String > &versionStage) noexcept |
| Aws::Crt::Optional< Aws::Crt::Vector< Aws::Crt::String > > | GetVersionStage () noexcept |
| void | SetSecretValue (const SecretValue &secretValue) noexcept |
| Aws::Crt::Optional< SecretValue > | GetSecretValue () noexcept |
| void | SerializeToJsonObject (Aws::Crt::JsonObject &payloadObject) const noexcept override |
| bool | operator< (const GetSecretValueResponse &) const noexcept |
| Public Member Functions inherited from Aws::Eventstreamrpc::AbstractShapeBase | |
| AbstractShapeBase () noexcept | |
| virtual | ~AbstractShapeBase () noexcept |
Static Public Member Functions | |
| static void | s_loadFromJsonView (GetSecretValueResponse &, const Aws::Crt::JsonView &) noexcept |
| static Aws::Crt::ScopedResource< AbstractShapeBase > | s_allocateFromPayload (Aws::Crt::StringView, Aws::Crt::Allocator *) noexcept |
| static void | s_customDeleter (GetSecretValueResponse *) noexcept |
| Static Public Member Functions inherited from Aws::Eventstreamrpc::AbstractShapeBase | |
| static void | s_customDeleter (AbstractShapeBase *shape) noexcept |
Static Public Attributes | |
| static const char * | MODEL_NAME = "aws.greengrass#GetSecretValueResponse" |
Protected Member Functions | |
| Aws::Crt::String | GetModelName () const noexcept override |
Additional Inherited Members | |
| Protected Attributes inherited from Aws::Eventstreamrpc::AbstractShapeBase | |
| Crt::Allocator * | m_allocator |
|
inlinenoexcept |
|
default |
|
overrideprotectedvirtualnoexcept |
Implements Aws::Eventstreamrpc::AbstractShapeBase.
|
inlinenoexcept |
|
inlinenoexcept |
|
inlinenoexcept |
|
inlinenoexcept |
|
noexcept |
|
staticnoexcept |
|
staticnoexcept |
|
staticnoexcept |
|
overridevirtualnoexcept |
Implements Aws::Eventstreamrpc::AbstractShapeBase.
|
inlinenoexcept |
|
inlinenoexcept |
|
inlinenoexcept |
|
inlinenoexcept |
|
static |


pretty pictures
`Prev `__
P
`Next `__
--------------
**pretty pictures**: n.
[scientific computation] The next step up from
`*numbers* <../N/numbers.html>`__. Interesting graphical output from a
program that may not have any sensible relationship to the system the
program is intended to model. Good for showing to
`*management* <../M/management.html>`__.
--------------
+---------------------------------------+----------------------------+--------------------------------+
| `Prev `__ | `Up <../P.html>`__ | `Next `__ |
+---------------------------------------+----------------------------+--------------------------------+
| prestidigitization | `Home <../index.html>`__ | prettyprint |
+---------------------------------------+----------------------------+--------------------------------+


Congratulations, you have successfully deployed the Yoga demo!
Yoga extends your existing REST implementation to create nested selectors that provide server-side navigation of the object tree.
This project arose out of real-world issues that were not met by standard REST approaches:
The Yoga approach is simple. On top of your RESTful implementation, you can pass a selector which asks the server to return nested or non-default fields with the response.
For instance, here is a traditional REST request that gets the information for a user:
/user/2.json
A mobile developer can create a very simple profile page with this data. Let's say the designers want to display list of the user's favorite artists on the same profile page. We add the selector as a parameter, like this:
/user/2.json?selector=:(favoriteArtists)
You could take this yet a step further, and grab the discography for those artists to display some album information on the same screen:
/user/2.json?selector=:(favoriteArtists:(albums))
... OR maybe you are more social-graph focused, and you want to show the other users that like the same artists as this person. You could do a circular reference back to the fans of that artist, and print out little icons for each one below the artist, filtering out the user from the profile page itself.
/user/2.json?selector=:(favoriteArtists:(fans))
Note that the circular reference does not continue to loop, since a selector has not been added to "fans".
This approach also works with calls that return collections of resources. Here we retrieve a list of all users in the database, and their favorite artists.
/user.json?selector=:(favoriteArtists:(albums))
Finally, here's an example of a deep-dive query that would take a dozen queries in a traditional RESTful API. It returns a list of all the songs by my friends' favorite artists:
/user/1.json?selector=:(friends:(favoriteArtists:(albums:(songs))))
Using the last query above, let's show a race between two simulated mobile clients. They will each try to draw a profile view that shows a user's friends and their favorite artists and corresponding discographies.
The client on the left uses the yoga selector to grab the entire necessary dataset in one query. The client on the right uses traditional object model navigation through multiple requests. To simulate mobile device latency, each response is delayed by 1.5 seconds. Other than that, queries are optimized as much as possible, by running them in parallel.
Ready to look at some code? Head over to the documentation section of our Wiki Page.
This is open source so if you want to help out whether by submitting code, design, suggestions, feedback, or feature requests, we appreciate whatever you can contribute. You can contact us at<EMAIL_ADDRESS>We'll have proper mailing lists and issue tracking available shortly.


Paste your completed documentation here. This application is in its
infant stages, and works in a specific way for now. Your documentation
must be using Markdown. It also must have its section headers using
starting with the ##
prefix (it will ignore the top level
#
prefix to be reserved for the documentation's main header).
These will act as the main section links for each section. Any
subsequent headers in that section can be set using ###
,
####
, and #####
. ######
is not
supported. The application will parse these as sub-sections of the
main section.


Fairy Tales and Other Traditional Stories
by FCIT
This compilation includes well-known classics, such as "Sleeping Beauty", "The Three Bears", and "The Ugly Duckling", along with many lesser-known stories. This collection includes stories from a variety of cultural traditions.
Source: This book was compiled by the Florida Center for Instructional Technology and includes passages from multiple sources. Please refer to the passage pages for further source information.
- Billy Beg and His Bull
- Billy Beg and His Bull encounter many adventures in their escape from the king’s new queen.
- “Blue Beard”
- A frightening fairy tale about a cruel man named Blue Beard who won over his wives with his riches and murdered them if they disobeyed his orders.
- “The Cake”
- A short fable about a boy who beat his brother because he stole his cake.
- “The Cat and the Mouse”
- A cat bites the tail off of the mouse. The mouse is led on a merry chase attempting to bring back cream for the cat who will then return the mouse’s tail.
- “The Cat and the Parrot”
- A fairy tale about a cat that eats all who disagree with him.
- “A Child’s Dream of a Star”
- A folk tale about the connection between death and the afterlife, in this case, heaven.
- “The Dun Horse”
- A lame and sad-looking dun horse brings good luck to a poor Indian boy.
- “Epaminondas”
- Epaminondas has a difficult time knowing how to carry his grammy’s gifts home to his mammy. Each time he tries what his mammy told him, but things keep turning out wrong for him.
- “The Fair One with the Golden Locks”
- Avenant is sent to win over The Fair One with the Golden Locks for the king in his land. He is set to a number of tasks and because of his good nature he is able to complete them. The princess falls in love with Avenant instead of the king, but is only able to marry him after the king’s death.
- “Fire! Fire! Burn Stick!”
- An old lady buys a pig. Then she cannot get the pig to jump over a fence so she can get home. She asks for help but is refused until at last she finds a cow who will give her milk. This begins chain of events which leads to getting home with the pig.
- “The Golden Goose”
- The youngest and silliest of three sons finds good fortune in sharing his meal with a poor old man.
- “The Golden River”
- A story about an abused brother that gets his reward for his kind-hearted nature through magic.
- “The Hare and the Hedgehog”
- Written as a play, this is a story about neighbors who do not get along. The hedgehog challenges the hare to a contest. The contest is used to settle the differences between the neighbors. However, is the means fair?
- “Jack and the Bean-Stalk”
- An adventurous fairy tale about a boy Jack and his encounter with giants.
- “Jack the Giant Killer”
- A fairy tale about a boy Jack, known as the Giant Killer, and his adventures of escape from giants, magicians, and other horrendous monsters.
- “The Lion and the Gnat”
- The story of a gnat that was able to overcome a lion despite his small size. However, as the gnat gloats about his victory he is beaten by a spider’s web.
- “Little Daylight”
- A princess is born to a queen and king and upon her christening she is cursed by a bad fairy. Her curse is intercepted twice by two good fairies so the fate of the princess is not quite so harsh. The princess is doomed to sleep through the day to wake at night and wane and wax with the moon until kissed by a prince who knows nothing of her story.
- “The Little Hero of Haarlem”
- A fairy tale about a young boy named Hans that saved a town from drowning by plugging up the water in a bank with his finger.
- “One Eye, Two Eyes, Three Eyes”
- The sister named Little Two Eyes is put down by her sisters who think she is common. However, she gets magical assistance and has a happy ending.
- “The Origin of Rubies”
- How rubies were discovered in the ocean.
- “Philemon and Baucis”
- A village is preparing for a visit from Zeus. Everyone is too busy or too tired to extend any kindness to two beggars except Philemon and Baucis. This poor old couple has time for the strangers and are rewarded in a very unusual way for their generosity. This story is a translation of "Philemon and Baucis" from Metamorposes by the Roman poet Ovid.
- “The Pig Brother”
- A fairy tale that teaches children to be tidy or they will be doomed to play with pigs in the mud.
- “The Purple Jar”
- Rosamond needed new shoes, but as she window-shopped she found she desired less prudent things. She was unwise in her decisions and paid the price for it when she was unable to participate in much because she did not have the proper shoes.
- “Raggylug”
- A short story about Raggylug, a baby rabbit, that lives with his mother and doesn’t heed her warning about hiding in the nest. After an encounter with a snake and a sudden escape, Raggylug learns his lesson.
- “The Sailor Man”
- A folk tale that teaches children not to daydream, but work for their reward.
- “Sleeping Beauty”
- An angry fairy casts a spell on a lovely princess. The spell is made less frightening by another fairy. In spite of all efforts to avoid the spell, the princess falls prey to it’s power. The spell can only be broken by the kiss of a handsome prince charming.
- “The Story of Little Tavwots”
- This Indian legend explains the size of rabbits. A rabbit named Tavwots caught the sun in his snare and had to release him. However, he melted to a quarter of his size with the exception of his feet.
- “The Story of Wylie”
- A story about a sheepdog named Wylie that helped farmers in the market with her expert herding skills.
- "The Three Bears"
- The story of the three bears and a girl named Silver-hair who breaks into their house.
- “The Twelve Brothers”
- The twelve sons of the king would be killed if the queen had a daughter.

- “Why Brother Bear Has No Tail”
- Uncle Remus tells a story about Brer Bear.
- “Why the Evergreen Trees Keep Their Leaves in Winter”
- A fairy tale about a little bird with a broken wing and the trees that offered him shelter. The fairy tale is used to describe the nature of dying in winter.
- “The Wise Men of Gotham”
- Twelve fishermen think one of them has drowned. When they count to see if everyone is there they always count eleven.
- The Emperor's New Clothes
- The very vain Emperor in this fairy tale is tricked by a pair of thieves.
- Year Published: 2012
- Language: English
- Country of Origin: United States of America
-
Readability:
- Flesch–Kincaid Level: 4.6
- Word Count: 62,411
- Genre: Fairy Tale/Folk Tale
- Keywords: animals, awaiting the afterlife, beauty, brothers grimm, chain story, cleanliness, compromise, consequence, consideration, determination, dragon, emperor, evil fairies, fairy tales, finding treasure, folk tales, generosity, giant, good fairies, good vs. evil, greed, grimm brothers, helping others, heroism, humility, humor, kindess, kindness, king, magic, merit, nature, obediance, obedience, penance, prince, princess, problem solving, repetition, rewards for not being greedy, shoe, sword, the dangers of arrogance, the importance of prudency, timeline, triumph, vanity


Update the Event Calendar on raleighhog.com
General notes, terminology and policies
- Please note that prior to doing anything in the production environment, you can test in the sandbox environment first. This environment is used for testing and is not seen by members.
- Your webmaster will also help with any questions you may have.
- There are two Event Calendars
- Chapter Event Calender - the main calendar, anyone on our website can see all events
- Road Captain Event Calendar - viewable only by Raleigh NC Chapter Road Captains after successful login to their account
- 'Event' is a ride, meeting or activity that is posted on the Raleigh NC Chapter Event Calendar. Throughout this document they will all be referred to as event.
- Most of our events are 'closed', meaning members may invite a guest but the event can only take place if there is greater than 51% current Raleigh NC Chapter members. This is a HOG national policy and is due to insurance concerns.
- LOH 'open to all' events are closed events. The 'open to all' statement means the event is not just for LOH members but is open to all Raleigh NC Chapter members, National HOG members and other guests as desired.
- Consistancy is key. Do not use different terminology for the same event. For example, throughout the website and in campaigns our monthly meeting is referred to as "Monthly Chapter meeting". It should be referred to as such in the Event Calendar so the naming convention is consistant throughout and transparent to end users.
- Last names, phone numbers and/or member personal email addresses are not to be displayed in any forward facing document so they are not put in any event. The Raleigh NC Chapter Event Calendar is forward facing.
- 'Forward facing' means any page that a non-authenticated user has access to. A non-authenticated user is one that has not successfully logged in.
- The policy of maintaining privacy by not exposing last names, phone numbers, personal email addresses, personal motorcycle information, etc is from HOG national.
- National discourages HOG chapters from publishing any photographs of minor children, even with permission from a parent or guardian.
Create an Event
- Login to your account and there will be a smaller Navigational Bar (navbar) on top of the Chapter navbar. See image below
- Click Add content to go to the following screen... See image below
- Article - creates a blog entry, not used here and a different document
- Event - this is how Event Calender entries are made and is the purpose of this document
- Event checkin - the check-in process uses the HOG[SCAN] app, this is not used
- Forum topic - forum has been turned off for the website, this is not used
- Gallery - you have access to add to the Gallery but this will be done by the Photographer, not used here and a different document
- Click Event and the Create Event page opens
- There are four required fields. These fields, designated with a red asterisk, must be populated prior to saving the event.
- Title - A short, descriptive title
- EVENT DATE - Includes Date and Time, Show End Date is only checked if the event is an over-nighter. The second Date / Time fields are populated with the last day of the event.
- Date - Event date formatted as mm/dd/yyyy
- Time - Event time formatted as hh:mm followed by am or pm
- Event type - our events (rides / meetings) are closed events
- Note: If Event type is Road Captain Events or RC pre-rides, the event will only appear on the Road Captain Event Calendar. (The RC Event Calendar can only be viewed by RC's after they've logged in.)
- Ride Mileage - we do not use this field, it can be left blank
- Points - used only to identify newer members, leave at the default of 10
- Event Coordinator - select from the dropdown. If the name isn't in the list leave it blank
- Image - leave blank. An image, if available, will be included in the Body area. (If populated here it messes with the copy flow and the map.)
- Body (Edit summary) - this is where the destination image and the event details are placed
- The image below shows the Body toolbar
- Hover over an icon to see a tooltip pop-up of the function of that icon. The icons highlighted in red are ones that are of use. The rest can be ignored as there is no need to use HTML/CSS to style the copy.
Link
icon - e.g. used to provide a link to a hotel to make reservations for overnight trips
Image
icon - e.g. used to include an image of the destination in the copy. Images for frequent ride destinations and dealer events have been preloaded and are currently available.
Bold
icon - e.g. used to make text stand out. For instance, Login and click RSVP to repond
Italic
icon - e.g. the name of the restaurant or destination is usually in italics to make it stand out from the rest of the copy
Size
icon - e.g. the font size defaults to 14px. It reads easier if you choose 16 from the dropdown.
- Click the
image
icon to add an image to the copy and the following pop-up appears. See image below
- Click the Browse Server button. The following window opens...
- Click either dealer-event-images or destination-images to open it
- Select the image you wish to use. NOTE: single click the name to see a preview of the image. Double click the name to select it.
- You are brought back to the Image Properties pop-up and you can now see a preview of the image you chose.
- Tip: You do not want users to scroll through a large image to see the details of the event. In either the Width or Height boxes change the larger of the two to 400. The images aspect ratio will be maintained and users will appreciate seeing a smaller image.
- Click the OK button
- You can continue editing the Body to add text about the event.
Tip: hit the spacebar so the text starts on the line below the image.
- Editing tip for the Body (Edit summary) section.
- Use the
Shift+Enter
keys to have a break in the line.
- Use the
Enter
key to start a new paragraph.
- Note that in the copy, the times listed match the format of the website timestamp. You want to keep things consistant.
- See image below for demonstraton
- EVENT LOCATION section
- Does not have to be filled in
- If known, fill in Street, City, State and Postal code
- Click the "Find Address on Map" button to populate the map
- Scroll to the bottom of the page and click the "Save" button
- The event has been added to the appropriate calendar


Definitions
Leading dimensions
Many algorithms can be applied exactly the same to a variable even though it may have different dimension dependencies. For instance, a density conversion can be the same algorithm for either density {}, density {time}, density {latitude,longitude}, density {time,vertical}, etc. The algorithm is just applied element-wise for each element in the dimensions that density depends on. Such leading dimensions that can be handled element-wise are captured by a ‘:’ in the variable reference in the definitions below. Any dimensions that are significant for the conversion (for instance, the vertical dimension when integrating a vertical profile to a total column) will still be mentioned explicitly and will map to an index in the symbol used for the quantity (e.g. \(\nu(:,i)\)). If an algorithm has variables with a ‘:’ in the dimension specification then the algorithm will contain a description of which combination of dimensions are supported for ‘:’.
Constants
symbol |
name |
unit |
value |
|---|---|---|---|
\(a\) |
WGS84 semi-major axis |
\(m\) |
\(6378137.0\) |
\(b\) |
WGS84 semi-minor axis |
\(m\) |
\(6356752.314245\) |
\(c\) |
speed of light |
\(\frac{m}{s}\) |
\(2.99792458\cdot10^{8}\) |
\(\frac{1}{f}\) |
WGS84 inverse flatting |
\(298.257223563\) |
|
\(g_{0}\) |
mean earth gravity |
\(\frac{m}{s^2}\) |
\(9.80665\) |
\(g_{e}\) |
earth gravity at equator |
\(\frac{m}{s^2}\) |
\(9.7803253359\) |
\(g_{p}\) |
earth gravity at poles |
\(\frac{m}{s^2}\) |
\(9.8321849378\) |
\(GM\) |
WGS84 earth’s gravitational constant |
\(\frac{m^3}{s^2}\) |
\(3986004.418\cdot10^{8}\) |
\(k\) |
Boltzmann constant |
\(\frac{kg m^2}{K s^2}\) |
\(1.38064852\cdot10^{-23}\) |
\(N_A\) |
Avogadro constant |
\(\frac{1}{mol}\) |
\(6.022140857\cdot10^{23}\) |
\(p_{0}\) |
standard pressure |
\(Pa\) |
\(101325\) |
\(R\) |
universal gas constant |
\(\frac{kg m^2}{K mol s^2}\) |
\(8.3144598\) |
\(T_{0}\) |
standard temperature |
\(K\) |
\(273.15\) |
\(\omega\) |
WGS84 earth angular velocity |
\(rad/s\) |
\(7292115.0\cdot10^{-11}\) |
Molar mass
The following table provides for each species the molar mass \(M_{x}\) in \(\frac{g}{mol}\).
See the documentation on the HARP data format for a description of all species.
name |
molar mass |
|---|---|
dry air |
28.9644 |
BrO |
95.9034 |
BrO2 |
111.9028 |
CCl2F2 |
120.9135 |
CCl3F |
137.3681 |
CCl4 |
153.822 |
CF4 |
88.00431 |
CHClF2 |
86.4684 |
CH3Cl |
50.48752 |
CH3CN |
41.05192 |
CH3OH |
32.04186 |
CH4 |
16.0425 |
CO |
28.0101 |
COF2 |
66.0069 |
COS |
60.0751 |
CO2 |
44.0095 |
C2H2 |
26.0373 |
C2H2O2 |
58.036163 |
C2H6 |
30.0690 |
C2H3NO5 |
121.04892 |
C3H8 |
44.09562 |
C5H8 |
68.11702 |
ClNO3 |
97.4579 |
ClO |
51.4524 |
HCHO |
30.026 |
HCOOH |
46.0254 |
HCN |
27.0253 |
HCl |
36.4609 |
HF |
20.006343 |
HNO2 |
47.013494 |
HNO3 |
63.0129 |
HNO4 |
79.0122 |
HOCl |
52.4603 |
HO2 |
33.00674 |
H2O |
18.0153 |
H2O_161 |
1.00782503207 + 15.99491461956 + 1.00782503207 |
H2O_162 |
1.00782503207 + 15.99491461956 + 2.0141017778 |
H2O_171 |
1.00782503207 + 16.99913170 + 1.00782503207 |
H2O_181 |
1.00782503207 + 17.9991610 + 1.00782503207 |
H2O2 |
34.01468 |
IO |
142.903873 |
NH3 |
17.03056 |
NO |
30.00610 |
NOCl |
65.4591 |
NO2 |
46.00550 |
NO3 |
62.0049 |
N2 |
28.01340 |
N2O |
44.0129 |
N2O5 |
108.0104 |
OClO |
67.4518 |
OH |
17.00734 |
O2 |
32.000 |
O3 |
47.99820 |
O3_666 |
15.99491461956 + 15.99491461956 + 15.99491461956 |
O3_667 |
15.99491461956 + 15.99491461956 + 16.99913170 |
O3_668 |
15.99491461956 + 15.99491461956 + 17.9991610 |
O3_686 |
15.99491461956 + 17.9991610 + 15.99491461956 |
O4 |
63.9976 |
SF6 |
146.0554 |
SO2 |
64.0638 |


COMING SOON
Our mission is to raise awareness about and diminish the stigma and expectations that surround Asian Americans in modern society
COMING SOON
Our mission is to raise awareness about and diminish the stigma and expectations that surround Asian Americans in modern society


"As a copywriter, it is very exciting to get to work with someone like Matt — because you get to watch the numbers climb with every project he touches. Matt is always dreaming up ways to make the user experience better, easier, and more effective. Along with using data to drive results, Matt has an uncanny ability to put himself in the audience's shoes to figure out what affects their decisions. He's also a strong leader, advocating for the team, making sure all voices feel heard, and leading brainstorming sessions.
Matt is a joy to work with, and anyone would be lucky to have him on their team."
-Thea Weiss
"Matt is a knowledgeable, self-starter and hard-working individual. I worked directly with Matt and was a part of a site optimization task force that he started for our company. This task force was a much needed effort to unite cross-functional teams through experimentation, Matt saw and opportunity and didn't hesitate to take action. By creating a singular process for website experimentation, he reduced the duplicate work that was happening and created a collaborative environment to improve our conversions. Aside from that, Matt is a pleasure to be around and a team player, any organization would be lucky to have him!"
-Geraldine Dagen
"'Action-Oriented' comes to mind when I think of Matt. I had the pleasure of working with Matt during my time with AB Tasty. He is truly passionate about improving the customer journey through improved UX, testing, and personalization. Matt successfully built an experimentation and optimization program at Evolve Vacation Rental with tremendous results in increasing qualified visitor conversion rates. Matt has dedicated his time to research conversion rate optimization tools, UX principals and use cases with the goal of turning insights into data-driven decisions. What is particularly admirable about Matt is that he is willing to share his research and experiences with the broader professional community."
-Peenaz Devani


PCASC educates and mobilizes community members, workers and students around struggles for human rights and social justice throughout the Americas.
The Portland Central America Solidarity Committee (PCASC) was founded in 1979 by a group of activists concerned about US military and economic policy in Central America. In 1982, PCASC volunteers organized and successfully passed a county ballot measure calling on the federal government to end military support to the government of El Salvador, engaging and educating hundreds of thousands of voters.
In 1987, Portland resident Ben Linder was murdered by Contras in Nicaragua, and activists including Ben’s family members organized on a national level to draw attention to Ben’s death and US foreign policy towards Nicaragua.
In the 1990s, PCASC’s work shifted focus to work on ending corporate globalization. PCASC organized over 400 union members to participate in the Seattle WTO protests in 1999.
In 2005, PCASC coordinated a community campaign, involving communities of faith, student organizations, and unions to stop passage of the Central America Free Trade Agreement (CAFTA). This campaign was successful in pressuring Representative Earl Blumenauer (an avowed believer in free trade agreements) to vote no. In 2006, PCASC helped organize a historic May Day march for immigrant rights, with over 12,000 mostly Latino participants.
PCASC values building a sustainable progressive movement. We believe that education, action, and leadership are key components of building our movement. It is vital to invest in strengthening the political analysis and organizing skills of our members and volunteers.
PCASC supports communities in their struggles to control their own lives. Our emphasis is on building direct relationships in the communities that we support and respond to their needs. We use our resources to amplify community voices.
PCASC creates a space for those with anti-capitalist, anti-imperialist, and anti-racist values to build community and foster conversations about these values with other members of our community.
1.
PCASC raises resources to send to social movements in the Americas.
We believe we have access to resources due to the exploitation of Latin American peoples and their environment, so we should use our access to provide resources whenever we can.
2.
PCASC builds organizers and movement leaders through a decentralized, member-run organization, with support from skilled peers.
We believe that the movement must be built from the ground up and that there's strength in collective power. We believe that anti-oppression is critical to systemic change. We believe in developing and strengthening the political analysis and organizing skills of all PCASC members.
3.
PCASC offers analysis and solutions that target the root causes of problems and demands systemic change while building power from the bottom towards a more just world.
We believe capitalism and oppression are the root causes of injustice.
4.
PCASC directly connects community members, students, and workers with their counterparts in the Americas.
We believe that relationships and common struggles are critical foundations of solidarity.
5.
PCASC brings an international and solidarity-based perspective to Portland organizing.
We believe that oppression in the Americas affects our own communities and that we need to be in alliance with other people’s movements in order to build the broad movement needed to WIN.
6.
PCASC educates its community about struggles for justice in the Americas by elevating the voices and the organizing of those on the front lines and making space for alternative solutions.
We believe people’s movements speak for themselves. Our role is to amplify, in the U.S., those voices, while changing consciousness here. People’s movements from the Americas offer community based solutions that we can learn from and share.
7.
PCASC opposes U.S. and corporate imperialism in the Americas.
Transnational corporations and the U.S. government impose policies that exploit and oppress communities throughout the Americas. It is our responsibility to fight these policies from within.


Radius:
Pan Angle:
Horizontal FOV:
Source height:
Target height:
Tilt Angle:
Vertical FOV:
Your browser does not support the HTML5 canvas tag.
Your browser does not support the HTML5 canvas tag.


Feature Flags is not available for the loaded tab, please check your site config and try again
{flag.description}


Professional, creative and innovative Licensed Architect with 15 years of experience working with well established firms as Hartshorne Plunkard Architecture, Tria Architecture, and Healy Bender Architects, designing high-rise, educational, commercial, and residential projects.
Marco Graduated as an Architect from the University of Illinois in 2006.
Besides his acquired knowledged working with architecture firms, Marco has developed projects for restaurants, schools and residential real estates.
Marco has ample capabilites to manage a project through its development cycle from conception to full completion. He's attention to detail when complying with city codes, regulations and policies, will assure the project a successful fulfillment.


We will first prepare our environment to run calm-dsl. We will run calm-dsl on Docker for this lab.
Make sure you have Docker running on your laptop. To verify that Docker engine is running, run the following command:
$ docker --version
If you don’t have Docker installed, please refer to the installation instructions here: MacOS: Windows:
calm-dsl image is already available on docker hub ntnx/calm-dsl, pull the image and run the container
$ docker pull ntnx/calm-dsl
Create a folder to hold you blueprint files for this lab.
$ mkdir basic_blueprint
$ cd basic_blueprint
$ docker run -it -v $PWD:/root/blueprint ntnx/calm-dsl
If everything is ok, you should be presented with container cli.
Run calm init dsl on the cli to initialize calm-dsl with the correct settings.
To validate the settings you can check the status of the PC connecitivty:
$ calm get server status
Optionally you can integrate the running container with Visual Studio Code to allow lenting, follow the steps on this blog: https://www.nutanix.dev/2020/04/24/nutanix-calm-dsl-remote-container-development-part-1/


Published:
del
vs role=deletion
Text to be removed
Text to be removed
ARIA + HTML exposed as:
Role: AXGroup
Subrole: AXDeleteStyleGroup
ins
vs role=insertion
Text to be added
Text to be added
ARIA + HTML exposed as:
Role: AXGroup
Subrole: AXInsertStyleGroup
sub
vs role=subscript
Subbed
Subbed
ARIA + HTML exposed as:
Role: AXGroup
Subrole: AXSubscriptStyleGroup
sup
vs role=superscript
Supped
Supped
ARIA + HTML exposed as:
Role: AXGroup
Subrole: AXSuperscriptStyleGroup
time
vs role=time
July 30 2019
ARIA + HTML exposed as:
Role: AXGroup
Subrole: AXTimeGroup


This topic provides information about developing and deploying Java applets. Java applets use Java Plug-in technology to run in a browser.
This topic contains the following sections:
Java Plug-in technology (hereafter the "Java Plug-in"), which is included in the Java Runtime Environment (JRE), enables Java applets to run in web browsers on the desktop. The Java Plug-in provides powerful capabilities to applets in the web browser, while improving the overall reliability and functionality of applets in a backward-compatible manner.
The Java Plug-in runs one or more Java virtual machine instances (JVMs) that connect back to the browser for full interoperability with the surrounding web page. This architectural change offers many advantages and features:
The JVM running the applet is isolated from the web browser at the operating system level. If something should go wrong while running the applet, or if an uncooperative applet refuses to shut down, the Java Plug-in detects and handles the error condition gracefully; the web browser is unaffected.
The Java Plug-in starts applets in the background, so the web browser always remains responsive. Applets appear on the web page as they become ready to run.
The Java Plug-in offers the capability to launch applets directly from JNLP files, unifying deployment of Java content both in the browser and out of the browser (via Java Web Start). Developers can reuse JNLP extensions for advanced functionality. Applets can access JNLP APIs for persistent data storage, local file system access, and other useful functionality from sandboxed code.
The bridge between the JavaScript engine in the web browser and the Java programming language is backward-compatible and features reliability, performance, and cross-browser portability for both Java applets calling JavaScript code as well as JavaScript code calling Java applets.
Applets can utilize as much heap space as command-line applications.
JVM command-line arguments may be specified in the HTML of the web page on a per-applet basis, providing fine-grained control over options such as the heap size and Java 2D hardware acceleration features.
Each applet instance can request a different JRE version on which to run. Both selection of a specific JRE version, or any in a particular family, are supported in the Java Plug-in.
See the Applet Development Tutorial, a comprehensive Java Tutorial that explains various aspects of applet development and deployment.
This section describes how the Java Plug-in controls the execution of applets and interactions between applets and the browser.
With the Java Plug-in, applets are not run in the JVM inside the browser. Instead, they are executed in a separate process. The same JVM process can be shared between multiple applets, or applets can be placed into different processes depending on whether the existing JVMs match the applet requirements and have enough resources to execute the applet. An applet can request a specific version of the JRE to be used and can specify what options to pass to the JVM. An applet can also request to be executed in the separate JVM.
The browser and the applet can still communicate with one another, however. Existing APIs have been re-engineered to use process sockets, so everything continues to work as it did before, only better. This architecture provides a number of benefits:
Applets that require different versions of the JRE can run simultaneously.
Applets can specify JRE start-up parameters such as heap size. (A new applet uses an existing JRE if it's requirements are a subset of an existing JRE, otherwise, a new JRE instance is launched.);
The message-passing interfaces are written in Java, so they run on all supported platforms, in the same way, so cross-browser compatibility is enhanced.
With that architecture, a new JRE can be launched whenever it is needed. However, an applet runs in an existing JRE when the following conditions are met:
The JRE version required by the applet matches an existing JRE.
The launch parameters for the JRE satisfy the applet's requirements.
|
Note:
|
On all platforms, the Java Plug-in locates JREs to use from the entries listed in the Java Control Panel ("Java" tab, "View" button). The available JREs in this list are encoded in the deployment.properties
file whose location is platform-dependent. On the Windows platform, it is generally located in C:\Users\[username]\AppData\LocalLow\Sun\Java\Deployment
. On Solaris, Linux, and OS X platforms, it is generally located in ~/.java/deployment/deployment.properties
.
On Windows platforms, both the Java Control Panel and the Java Plug-in automatically detect the installed JREs and add them to the available set. On Solaris, Linux, and OS X platforms, auto-detection of installed JREs is not supported. The Java Runtime Environment Settings dialog, which is accessed by clicking View in the Java tab of the Java Control Panel, can be used to manually add JREs to the known list for the Java Plug-in.
By default, the Java Plug-in executes all applets in the latest JRE version named in this list. The Java Plug-in executes an applet on an earlier JRE version only if explicitly requested.
When considering a request to launch an applet on a specific JRE version (for example, a particular update release like "1.5.0_11"):
The list of available JREs is consulted. If there is an exact match of the version string, that JRE version is selected. Otherwise, if there are one or more installed JREs in the same family, the latest version is selected. Otherwise, the latest available JRE on the machine is selected.
The selected JRE version is compared against the security baseline for the family. (See Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer for more information.) If it is equal to or more recent than that version, no further prompting is done and the applet is launched.
Otherwise, the code for the applet is downloaded in a JVM instance of the selected JRE version. If the applet is signed and the user accepts the security dialog for the applet (or the code source has already been trusted), no further prompting is done and the applet is launched.
Otherwise, we are dealing with an unsigned applet on an "older" JRE version. A dialog box is presented indicating that this applet is requesting to run on top of an older JRE release, and asks the user whether he or she wants to allow it to. If the user clicks "yes", the applet is launched. If the user clicks "no", the applet is re-launched on top of the latest available JRE version.
When considering a request to launch an applet on a particular family, the most recent JRE from that family will be selected and the above steps starting from (2) will be followed.
When considering a request to launch an applet on a particular family or any later family, the latest available JRE will be used to launch the applet.
A web browser's JavaScript interpreter engine is single thread. The Java Plug-in is capable of managing multiple threads. The Java Plug-in creates a separate worker thread for every applet. Applets themselves may be multi-threaded. Applets making JavaScript to Java calls and vice versa should be designed with the thread related issues in mind.
The following figure shows the thread interactions between the JavaScript Interpreter, Java Plug-in, and an applet.
When the JavaScript interpreter is idle, the Java Plug-in executes a JavaScript to Java call on the per applet worker thread (JavaScript Interpreter Not Busy scenario).
When a Java to Javascript call is in progress and a JavaScript to Java call is made, the latter is executed on the same thread that made the Java to JavaScript call (Round Trip scenario).
When a thread is executing a Java to JavaScript call, another thread wanting to do the same will be blocked till the first thread has received its result and is done (JavaScript Interpreter Busy scenario)
In order to avoid thread related issues especially when multiple applets are running simultaneously, keep both Java to JavaScript and JavaScript to Java calls short and avoid round trips, if possible.
Normally, if two applets have the same codebase
and archive
parameters, they will be loaded by the same class loader instance. This behavior is required for backward compatibility, and is relied on by several real-world applications. The result is that multiple applets on the same web page may access each others' static variables at the Java language level, effectively allowing the multiple applets to be written as though they comprised a single application.
While this feature enables certain kinds of applications to be conveniently written, it has certain drawbacks. It interferes with termination of applets, in particular when multiple instances of the same applet are active. It makes the programming model for applets more complex, since it is under specified exactly when the static fields of an applet will be re-initialized, and when they will be maintained from run to run of the same applet. It causes imprecise behavior of certain user interface operations within the Java Plug-in due to the inability to identify exactly which applet initiated a particular request.
For this reason, the Java Plug-in provides a way to opt out of the use of the Section 12.3.5, "Class Loader Caching" on an applet by applet basis.
 The garbage collection applies to all memory acquired by the applet, except for static variables. Statics are preserved in the classloader cache, along with the classes themselves, for as long as the class loader is present.
So when does the class loader go away? That behavior is not specified. It's up to the implementation of the Java virtual machine and its interactions with the operating system. You can expect it be retained for as long as possible, but to be discarded when the memory is needed for other purposes.
Sign all applets with a valid certificate from a recognized certificate authority to provide a better user experience. An applet runs in a secure sandbox that prevents it from interacting with the user's system, unless authorized. To obtain that authorization, the applet must request permissions when it is launched and the user must agree to run the applet. Permissions are needed to:
Access the file system
Access browser cookies
Access other system resources
The basic applet security model is an all or nothing proposition. An applet with permissions has full access to the user's system. Without permissions, the applet has virtually no access at all.
Deployment of applets using JNLP gives the applets access to JNLP APIs similar to Java Web Start applications, which gives the applet controlled access to a user's system, under control of the user. For example, using JNLP provides the ability to save or open a file selected by the user and the ability to print.
Applets can be deployed by hand-coding the applet
, object
or embed
tags with the required parameters. This section describes these parameters. However, to assure cross-browser compatibility, it is recommended that the Deployment Toolkit be used to deploy applets. See Chapter 19, "Deployment in the Browser" for information on using the Deployment Toolkit.
The file containing information for the plug-in to use to launch the applet.
The Java Plug-in offers better customization of the image that is displayed before the applet is loaded. Animated GIFs are supported as the target of the image
parameter. Additionally, the following parameters are supported:
A boolean parameter indicating whether a one-pixel border should be drawn around the edge of the applet's area while displaying the image shown before the applet is loaded. Defaults to true
. We recommend setting this value to false
, in particular when using an animated GIF as the loading image, to avoid the possibility of flicker.
A boolean parameter indicating whether the loading image should be centered within the area of the applet instead of originating at the upper left corner. Defaults to false
.
Example using the boxborder
and centerimage
parameters:
<APPLET archive="large_archive.jar" code="MyApplet" width="300" height="300"> <!-- Use an animated GIF as an indeterminate progress bar while the applet is loading --> <PARAM NAME="image" VALUE="animated_gif.gif"> <!-- Turn off the box border for better blending with the surrounding web page --> <PARAM NAME="boxborder" VALUE="false"> <!-- Center the image in the applet's area --> <PARAM NAME="centerimage" VALUE="true"> </APPLET>
Specifies an additional set of standard and non-standard virtual machine arguments that the application prefers the JNLP client to use when launching Java. When both java_arguments
and java-vm-args
are present, the java-vm-args
arguments take precedence.
Specifies JVM command-line arguments to be used when executing this applet instance. Nearly all JVM command-line arguments are supported, though there are certain rules and restrictions. When both java_arguments
and java-vm-args
are present, the java-vm-args
arguments take precedence.
The java_arguments
option is primarily for the purpose of avoiding a client Java VM relaunch during applet startup. As a good practice, if both java_arguments
and java-vm-args
are specified, they should contain the same values.
A boolean parameter specifying that a particular applet should run in its own JVM instance. This supports certain powerful desktop applets which can not tolerate any interference from other applets running in the same JVM and potentially consuming heap space or other resources.
<APPLET archive="my_applet.jar" code="MyApplet" width="300" height="300"> <PARAM name="java_arguments" value="..."> <PARAM name="separate_jvm" value="true"> </APPLET>
Scenario 1:: Both parameters are defined and their values are different.
java_arguments = -Xmx256m java-vm-args = -verbose
Expected behavior on all platforms: -verbose
The JVM first launches using the value specified by the java_arguments
tag. The client JVM detects the mismatch and relaunches with -verbose
only. A warning is printed to the Java console.
Scenario 2: Both parameters are defined, and the values specified in java-vm-args
are a subset of those specified in java_arguments
.
java_argument = -Xmx256m -verbose java-vm-args = -verbose
Expected behavior on all platforms: -verbose
The JVM first launches with the full set of arguments as specified by java_arguments
. The client JVM detects the mismatch, and relaunches the smaller set of argument as specified by java-vm-args
only. A warning about the parameter mismatch is printed in the Java console.
Scenario 3: The java_arguments
tag is defined in the HTML file, but the java-vm-args
tag is not defined in the JNLP file.
java_arguments = -Xmx256m java-vm-args = [not defined]
Expected behavior on all platforms: [no jvm params]
The JVM first launches with the values specified in java_arguments
. The client JVM detects the mismatch and relaunches the JVM with no params. A warning about the parameter mismatch is printed in the Java console.
Scenario 4: The java_arguments
tag is not defined in the HTML file, but the java-vm-args
tag is defined in the JNLP file.
java_arguments = [not defined] java-vm-args = -Xmx256m
Expected behavior on all platforms: -Xmx256m
The JVM first launches with no JVM arguments, as there are none specified in the java_arguments
tag. The client JVM detects the mismatch and relaunches the JVM using the values specified in java-vm-args
.
Specifying a larger-than-default maximum heap size:
<APPLET archive="my_applet.jar" code="MyApplet" width="300" height="300"> <PARAM name="java_arguments" value="-Xmx128m"> </APPLET>
Specifying a non-default heap size and a Java 2D hardware acceleration option typically used for applets using OpenGL via Java Binding for the OpenGL API (JOGL):
<APPLET archive="my_applet.jar" code="MyApplet" width="300" height="300"> <PARAM name="java_arguments" value="-Xmx256m -Dsun.java2d.noddraw=true"> </APPLET>
Enabling verbose output of the garbage collector, and the assertion facility in the Java programming language:
<APPLET archive="my_applet.jar" code="MyApplet" width="300" height="300"> <PARAM name="java_arguments" value="-verbose:gc -ea:MyApplet"> </APPLET>
A set of "secure" JVM command-line arguments and system properties is defined in the JNLP File Syntax section of the Java Web Start Developers' Guide. In the Java Plug-in, as long as all of the JVM command-line arguments specified via the java_arguments
parameter are secure, then the applet, or any classes it loads, may run without permissions.
Insecure JVM command-line arguments (in other words, those not on the secure list) may also be specified via the java_arguments
parameter. In this case, there is the potential for a security risk, so the Java Plug-In enforces the rule that no unsigned classes may be loaded. In other words, only trusted code, for which the user has accepted the security dialog, may be loaded by such a JVM instance. If an attempt is made to load an unsigned or untrusted class in a JVM instance for which insecure system properties have been specified, a ClassNotFoundException
will be thrown indicating that the given class could not be loaded because it was not signed.
There are relatively few restrictions on what command-line arguments may be passed via the java_arguments
parameter. In general, the -Xbootclasspath
argument is forbidden, as well as any command-line argument used to specify a path, such as -classpath
or -jar
. All other command-line arguments, present and future, should be supported, with the caveat about secure and insecure command-line arguments described above.
The command-line arguments passed via the java_arguments
parameter are added to any specified via the Java Runtime Environment Settings dialog in the Java Control Panel. The command-line arguments from the control panel are used for all JVM instances of the version for which they are specified; the java_arguments
parameters do not completely replace them.
When JVM command-line arguments are specified, it is likely that the Java Plug-in will need to launch another JVM instance in order to satisfy them. In other words, it is unlikely that a preexisting JVM instance will have been started with the correct set of command-line arguments to satisfy the request. The rules for exactly when a new JVM instance is launched to start a given applet are deliberately left unspecified and may need to change in subsequent releases. Here is a rough set of guidelines for the sharing and creation of new JVM instances:
If the command-line arguments used to start a preexisting JVM instance are a superset of the requested arguments, the preexisting JVM instance will be used.
If a JVM instance is launched for the "default" set of command-line arguments (i.e., those specified in the Java Control Panel, with no java_arguments
specified), then this JVM instance will never be used to launch any applet that has even one command-line argument specified via java_arguments
.
-Xmx
is handled specially: if a preexisting JVM instance was started with for example -Xmx256m
via java_arguments
, and a new applet requests -Xmx128m
, then new applet will very likely be run in the preexisting JVM instance. In other words, -Xmx
specifications are matched with a greater-than-or-equal test.
There is no way to "name" a JVM instance used to launch a particular applet and "force" subsequent applets into that JVM instance.
See the section on the separate_jvm
parameter to isolate a particular applet in its own JVM instance, separate from all other applets.
Specifies a JRE version upon which to launch a particular applet.
Use the Deployment Toolkit to specify an older version of the JRE, if needed. In an enterprise environment, the preferred method of requesting an older version of the JRE is to use the Deployment Rule Set feature.
The Java Plug-in provides a way to opt out of the use of the class loader cache on an applet by applet basis.
<APPLET archive="my_applet.jar" code="MyApplet" width="300" height="300"> <PARAM name="classloader_cache" value="false"> </APPLET>
For applets, the default value of the classloader_cache
parameter is true
; which indicates that class loader caching is enabled. For JNLP applets, class loader caching is disabled.
Specifies the level of permissions that the applet needs to run. The following values are valid:
sandbox
- The applet runs in the security sandbox.
all-permissions
- The applet requires access to resources on the user's system.
default
- The level of permissions is determined by the Permissions
attribute in the manifest for the main JAR file.
<APPLET archive="my_applet.jar" code="MyApplet" width="300" height="300"> <PARAM name="permissions" value="sandbox" /> </APPLET>
If this parameter is omitted, default
is assumed. If the parameter is present and not set to default
, the value must match the value of the Permissions
attribute in the manifest for any JAR file that has the Permissions
attribute, otherwise the applet is blocked.
Files you use in Java applications are stored in a special folder for quick execution later; this folder is also called the Java cache. The subpanel Temporary Internet Files in the General tab of the Java Contro Panel, which is described in Section 20.1, "General," enables you to view which files are stored in the Java cache and control how much disk space the cache can take up in your computer.
The cache_archive
attribute contains a list of the files to be cached:
<param name="cache_archive" VALUE="a.jar,b.jar,c.jar">
Like the archive attribute in the applet tag, the list of jar files in the cache_archive attribute do not contain the full URL, but are always downloaded from the codebase specified in the embed
or object
tag.
Beginning in the Java SE 7 release, you can check the value of the status
variable of an applet while it is being initialized. This check is non-blocking and immediately returns the status of the applet. You can explicitly check the status of the applet while it is loading and perform relevant actions or register event handlers that are automatically invoked during various stages of applet initialization. To use this functionality, deploy the applet with the java_status_events
parameter set to true
. See the Handling Initialization Status With Event Handlers lesson in the Java Tutorials for step by step instructions and an example.
Table 12-1 explains the meaning of values returned by the status
method of the applet.
You can register event handlers for various events. The Java Plug-in software invokes these event handlers at various stages of the applet loading process. Table 12-2 describes applet events for which event handlers can be registered.
Table 12-2 Applet Events
| Applet Event | When Event Occurs |
|---|---|
|
|
Applet status is READY. Applet has finished loading and is ready to receive JavaScript calls. |
|
|
Applet has stopped. |
|
|
Applet status is ERROR. An error has occurred while loading the applet. |
You can register or determine an event handler in the JavaScript code of a web page as shown in the following code examples:
// use an anonymous function applet.onLoad(function() { //event handler for ready state } // use a regular function function onLoadHandler() { // event handler for ready state } // Use method form applet.onLoad(onLoadHandler); // Use attribute form applet.onLoad = onLoadHandler; // get current event handler var handler = applet.onLoad
This section describes how to migrate existing Java Plug-in applets to the Java Network Launching Protocol (JNLP). You have the following options:
Migrate your applet to a Java Web Start application.
Use JNLP with your applet
Advantages and considerations for migrating to JNLP are described in the following sections.
Using JNLP with your applet provides the applet with access to the same resources that Java Web Start applications can access.
Migrating to a Java Web Start application provides the ability to launch the application independent of a Web browser. A user can be off-line or unable to access the browser. Desktop shortcuts can also launch the application, providing the user with the same experience as that of a native application.
Applets that are deployed with the applet tag can use JNLP. The JNLP file is specified in the jnlp_href
attribute. Parameters to configure deployment can be specified as attributes and parameters. For example:
<applet code="java2d.Java2DemoApplet" jnlp_href="dynamictree_applet.jnlp" width="710" height="540" > <param name="param1" value="value1"/> </applet>
Java Web Start technology has built-in support for applets. It is possible to run your applet directly with Java Web Start technology without any re-compilation of the applet. All you need do is to convert your applet HTML tags to a Java Network Launching Protocol (JNLP) file, using the JNLP applet-desc
element. For example:
<resources> <jar href="SwingSet2.jar"/> </resources> <applet-desc main-class="SwingSet2Applet" name="SwingSet" width="625" height="595"> <param name="param1" value="value1"/> <param name="param2" value="value2"/> </applet-desc>
The best way to migrate your applet is to re-write it as a standalone Java application, and then deploy it with Java Web Start technology. Re-writing your applet and testing the resulting application ensures that your converted applet works fully as expected, and your application can take advantage of the Java Web Start features.
The major work needed is to convert your applet
class to the main
class of the application. The applet init
and start
methods are no longer present, instead, initialize the application at the beginning of the application's main
method.
To quickly begin the migration, add the main
method to your original applet
class, and then start calling your applet initialization code where it normally gets called from the applet's init
and start
methods. When there is a main
method in the applet
class, you can begin launching it by means of Java Web Start technology, and then slowly remove the dependency on the Applet
class and convert it completely to your application's main
class.
For more information, refer to JNLP File Syntax.
The following items are things to consider when migrating:
A Java Web Start application does not run within the web browser. If your applet has any dependency on the browser (for example, Java-to-JavaScript or JavaScript-to-Java communications by means of the browser), the communication code will no longer work. The APIs that are affected include:
JSObject
API (netscape.javascript.JSObject.*
) for Java-to-JavaScript communication does not work for Java Web Start applications.
Common Document Object Model (DOM) APIs (com.sun.java.browser.dom.*
and org.w3c.dom.*
) available for Java Plug-in applets are not available to Java Web Start applications.
Similar to Java Plug-in technology, Java Web Start technology caches your application JARs for faster start-up performance. However, resources downloaded by your own application code are not cached by Java Web Start technology.
Java Web Start technology provides permanent cookie support on Windows using the cookie store in Internet Explorer, and the cookie-handling behavior is determined by the cookie control in IE. On Linux and Solaris, Java Web Start technology provides permanent cookie support using its own cookie store implementation. For more information, see Cookies in the Java Tutorials.
If you deploy an applet with the JNLP applet-desc
element, your applet is created using the AppletContainer
provided by Java Web Start technology. When your applet calls Applet.getAppletContext()
, it returns the AppletContainerContext
provided by Java Web Start technology. The following list describes minor differences in implementation between the Java Plug-in AppletContext
and the Java Web Start AppletContext
:
The following Applet Persistence API methods are not implemented by Java Web Start technology:
AppletContext.getStream(String key) AppletContext.getStreamKeys() AppletContext.setStream(String key, InputStream s)
For Java Web Start applications, you can use the JNLP Persistence Service API for storing data locally on the client's system. For more information, see the PersistenceService
interface.
For AppletContext.showDocument(URL url, String target)
, the target argument is ignored by Java Web Start technology.
For AppletContext.showStatus(String status)
, when launched with Java Web Start technology, this sets the JLabel
text that is below the applet, hosted by the Java Web Start AppletContainer
.
Similar to AppletContext.showDocument
, Java Web Start applications are capable of showing an HTML page using the system's default web browser by using the BasicService.showDocument
API.
For a Java Plug-in applet:
AppletContext.showDocument(URL url) AppletContext.showDocument(URL url, String target)
For a Java Web Start application:
BasicService.showDocument(URL url)
For more information, see the BasicService
interface.
In an applet, if you obtain a resource using the following calls:
Applet.getImage(URL url) Applet.getImage(URL url, String name) Applet.getAudioClip(URL url) Applet.getAudioClip(URL url, String name) AppletContext.getAudioClip(URL url) AppletContext.getImage(URL url)
Then in Java Web Start technology, the best practice is to include the resources in your application JAR files, and access the resources using the JNLPClassLoader
:
ClassLoader cl = this.getClass().getClassLoader(); URL url = cl.getResource(url); Image im = Toolkit.getDefaultToolkit().createImage(url);
For more information, see Retrieving Resources from JAR Files.
The pack200 JAR packing tool is supported by both the Java Web Start and the Java Plug-in technologies. If you are already deploying your applet JARs with pack200, no change should be needed when migrating to Java Web Start technology. For more information, see Section 30.2, "Deploying JAR Files Compressed with Pack200."
By using the OBJECT
tag in Java Plug-in technology, you can detect whether Java is available on the client's machine with the Plug-in CLSID
and then auto-download Java if necessary. The same support is available with Java Web Start technology by using the Java Web Start CLSID
. For more information, see Ensuring the Presence of the JRE Software in the Java Tutorials.
If you want to deploy extensions for your Java Web Start application, use the JNLP extension protocol mechanism. For more details, refer to the JSR 56: Java Network Launching Protocol and API, section 3.8 "Extension Descriptor."
One advantage of the JNLP extensions mechanism over Java Plug-in technology is that the installed extensions are available to all Java Web Start applications running on the system, no matter what version of JRE the application is running with. For Java Plug-in technology, only applets running in the same JRE version can make use of the installed extensions.
For signed JAR files, similar to Java Plug-in technology, you can sign your application JAR files and request your application to be run with all-permissions by means of the JNLP file. In Java Plug-in technology, your applet JARs can be signed by different certificates. In Java Web Start technology, the same certificate must be used to sign all JAR files (jar
and nativelib
elements) that are part of a single JNLP file. This simplifies user management because only one certificate must be presented to the user during a launch per JNLP file. If you need to use JARs signed with different certificates, you can put them in a component extension JNLP file, and reference it from the main JNLP file. For more details, refer to the JSR 56: Java Network Launching Protocol and API, section 5.4 "Signed Applications" and section 4.7 "Extension Resources."


Monthly Statistics
02/10/2012 - 02/11/2012
1.324.996
Visits
+13%
12.894.765
Pageviews
+17%
432.980
Visitors
-33%
11.324
New Visitors
+3%


Missions Statement
"Never put off until tomorrow what you can do the day after tomorrow." -Ben Franklin
My goal is to meet standards by the skin of my teeth by being the laziest, most unmotivated
barely functional procrastinator in existence.
Summary of Skillsets
- Advanced proficiency at highly efficient task avoidance, even under tight deadlines and peer pressure
- Easily pulled into time wasting dramas, games, and other forms of entertainment
- Always sleep deprived, running on an average of 4 hours of sleep despite accomplishing near nothing while awake
Experience
Swim Instructor/Lifeguard
Wave Aquatics...............May 2015 to Feb 2017
Used minimal movement and energy to teach children how to float and move forward in water, and was able to sometimes teach without getting in the water at all due to my dislike of getting wet (showering is a hassle). Made sure to take as little shifts as possible that would still earn a passing performance review.
Peer Tutor
Private Employer...............Oct 2017 to June 2017
Sat next to students and zoned out in their direction so they would think an eye was being kept on them as they did homework--a highly efficient and energy-saving system. Very occasionally gave helpful tips about the content that was supposed to be learned.
Education
B.A. in Procrastination Theory, 2018
The Putting Things Off College, San Deadlinessuck, NO
- 3.97 GPA
- Honors Board Member as being one of the laziest of the student body


--- permalink: /staff/overlays/ ---
Remember that you can have multiple of the same overlay on the same Scene, e.g. with different parameters set.
Do not put the banner permanently on screen during gameplay. This overlay is for special scenes such as a "starting soon" splash screen.


1 write to from
System.Management.Automation (1)
engine\LanguagePrimitives.cs (1)
4319
from
= fromType;
3 references to from
System.Management.Automation (3)
engine\LanguagePrimitives.cs (3)
4329
return
from
.GetHashCode() + 37 * to.GetHashCode();
4339
return this.
from
== ctp.
from
&& this.to == ctp.to;


The key fossil proxy data from the Sokli Eemian sequence, including pollen and spores, stomata, non-pollen palynomorphs, and plant macrofossils, are summarised in Fig. 2. The fossil sequence is divided into seven local pollen zones using a multivariate regression tree (Supplementary Fig. 3).
Fossil data (pollen, spores, stomata, non-pollen palynomorphs, and plant macrofossils) from the Eemian sequence at Sokli. The end of the Eemian is recorded in a parallel core, shown on top. The parallel core is shown with 3× exaggeration of the depth scale. Abrupt climate events are indicated with coloured bars (yellow = Tunturi event, pink = Värriö event). Lithology is from ref. 16. Selected taxa are shown. The full pollen and macrofossil data and the multivariate regression tree defining the pollen zonation are shown in Supplementary Figs. 1– 3
In Zones I (28.41–25.17 m) and II (25.17–24.65 m), pollen percentage values of Betula up to 80% (including B. pubescens/pendula (downy birch/silver birch; deciduous tree) and B. nana (dwarf birch; deciduous shrub)) indicate the presence of pioneering birch vegetation. Abundant pollen of Juniperus and the presence of a variety of light-demanding herbs ( Artemisia, Chenopodiaceae, Polygonum bistorta type, and Saxifraga oppositifolia type) suggest the forest remained relatively open. The sandy/silty sediments of Zone I and early Zone II are interpreted to represent a deglacial ice-lake stage. Zone III (24.65–23.40 m) saw dynamic forest development, from open pine forest ( Pinus pollen up to 75%) to mixed boreal forest with spruce ( Picea abies) and then back to relatively open larch ( Larix sp.) and pine dominated forest.
Zone IV (23.40–22.51 m) corresponds with the Tunturi cooling event defined in ref. 16. In the pollen record, the event is manifested by a sudden increase of B. pubsescens/pendula pollen from 20 to 50%, and increased Juniperus and lycopods, indicating the replacement of boreal forest by sub-arctic, open birch–pine forest.
The onset of Zone V (22.51–17.98 m) represents the abrupt return of mixed boreal forest with spruce and larch. Corylus becomes near continuously recorded, with relative pollen abundances (ca. 1%) only seen in Finnish surface-lake sediments samples within the modern occurrence limits of hazel 25, suggesting local presence. The sparse pollen of Quercus and Ulmus were most probably long-distance transported. Pinus pollen reaches maximum values (ca. 75%) about halfway through the zone, followed by a gradual decline at the expense of spruce. In Zone VI (17.98–15.98 m and 20.60–20.47 m in parallel core) the forest composition remains generally similar, however with gradual increases in Poaceae and Cyperaceae pollen, and overall increased values for B. pubsescens/pendula, indicating the start of the Late-Eemian climatic cooling. Noteworthy about Zone VI are the numerous finds of both pollen and stomata of Larix indicating its local presence. Larch is absent from modern-day Finland, with nearest natural occurrences of L. sibirica found at the shores of the White Sea in NW Russia 26. In Zone VII (20.47–20.38 m in parallel core), the boreal forest is replaced by birch forest in response to continued cooling.
Between depths 17.40–17.05 m, i.e., within Zone VI, shifts are recorded in the examined proxies. This abrupt cooling and drying event is here defined the Värriö event. This event has a relatively muted signal in the terrestrial pollen record, however the initial peak (two samples at 17.37–17.39 m) is seen as a sharp minimum in total tree pollen, with the ratio of arboreal to non-arboreal pollen (mean = 2.9) below the lowest value reached during the Tunturi event (4.8) indicating the opening of tree cover, while a maximum in Sphagnum suggests the extension of the wetland zone. A more distinct and longer lasting signal for the Värriö event is found in the aquatic proxy record (see Discussion).
The pollen-based reconstructions for Tjul and Tjan are presented in Fig. 3. After a noisy interval during the pioneer vegetation of Zones I–II, the Tjul curves (Fig. 3a) show two distinct warm stages. The individual reconstructions peak at ca. 2–3 °C above present during Zones III and V, with highest Tjul recorded during the early part of Zone V. The Tunturi event (Zone IV) is clearly seen, with an extremely rapid onset and gradual, stepwise recovery. The peak cooling of the Tunturi event (mean Tjul during the largest dip at 23.33–23.37 m vs. mean Tjul during preceding warm interval (Zone III)) varies between methods at 2.3–3.5 °C, with a mean magnitude of 2.7 °C. During Zone VI a gradual decrease starts in Tjul. This temperature decline is further interrupted by the Värriö event, where the abrupt onset represents a distinct fall in the median Tjul reconstruction during the otherwise stable warm interval following the Tunturi event. During the initial sharp cooling peak (17.37–17.39 m) the individual reconstructions show a temperature fall of 0.7–2.7 °C compared to the preceding half-metre interval, with a mean magnitude of 1.8 °C, followed by a recovery to near pre-event temperatures. Zone VII sees a return to pre-interglacial Tjul values.
Climate reconstruction based on the Eemian pollen data from Sokli. Reconstructions are prepared for ( a) Tjul and ( b) Tjan, using six different pollen–climate calibration models (see Methods for details), and summarised as a median of all six reconstructions (black curve). Abrupt climate events are indicated with coloured bars. The parallel core covering the end of the Eemian is shown with 3× exaggeration of the depth scale. c Analogue quality (squared chord distance 68) between each fossil pollen sample and the best matching modern pollen calibration sample. The dashed line indicates the mean analogue quality found for Late-Holocene samples from a nearby lake core 69. d Geographic locations of best modern analogues found for each fossil pollen sample. Fossil samples use symbols based on their pollen zone, and are positioned at the mean latitude and longitude (weighted by the analogue quality) of the five most compositionally similar modern pollen samples. For clarity, only fossil samples with relatively good modern analogues are shown (compositional distance to best modern analogue less than 2× the mean analogue distance found for Late-Holocene samples; see panel c). Locations of the available modern samples and the Sokli fossil site are also indicated
The Tjan reconstruction (Fig. 3b) shows a muted variability for Zones I–IV but generally parallels the major features of the Tjul reconstruction. However in Zones V–VI, Tjan takes a distinct, opposite trend compared to Tjul, with all but one reconstruction showing a gradual rise in Tjan by ca. 5 °C and ending at 2–3 °C above present.
The modern pollen analogue distances for fossil pollen samples are short for the warm stages of the Eemian, being similar or lower compared to the mean distance for Late Holocene samples (Fig. 3c). This suggests a robust reconstruction with small errors due to non-analogue palaeoclimate or climate–vegetation disequilibrium. The lack of wetland elements in the microfossil record, and the general scarcity of macrofossils, suggest that the coring site was situated in the central part of a lake. This is likely to help the pollen-based reconstruction as there is little non-climatic noise caused by local azonal vegetation, and the sequence rather samples the atmospherically mixed pollen of regional vegetation. Thus strong pollen analogues are found in the lake-based modern calibration data. However, the pollen analogue distances increase during the Early-Eemian pioneer vegetation stage and during the abrupt events characterised by rapid species turnover. This is reflected as noise and poor between method robustness in reconstructed temperature within these depth intervals.
The geographic locations of the modern pollen analogues are plotted in Fig. 3d. For Zones I–II, characterised by semi-open pioneer Betula vegetation (Fig. 2) and generally large analogue distances (Fig. 3c), the best modern analogues are found from various sectors of the modern forest–tundra ecotone of NE Europe. During the first warm stage (Zone III), best analogues are located in north-central Finland, south of Sokli, while a distinct shift towards northwest occurs during the Tunturi event (zone IV). Zone V reveals a shift in the analogue locations from south-central Finland to the southwest, which continues during zone VI when the best analogues end up in central Sweden. This parallels the trend towards warmer winters reconstructed with most methods (Fig. 3b).
In significance testing using a redundancy analysis permutation test 27 (see Methods for details), the Tjul reconstruction is significant ( p = 0.001), while for the Tjan reconstruction a significant result ( p = 0.011) is yielded for pollen Zones V and VI. This covers the long and stable Tjan increase across the upper ~60% of the sequence, but leaves out the relatively noisy Tjan reconstruction from Zones I–IV (Fig. 3b), possibly biased by the poor modern pollen analogues (Fig. 3c).
To compare our results with regional palaeoclimate datasets and climate forcing time series (Fig. 4), we assign an absolute time scale to the Sokli sequence. The age model is constrained by an event-stratigraphic correlation to U/Th-dated speleothem records from Sweden, Belgium and the Northern Alps 28– 30, and further supported by Greenland ice cores 31, 32 and Norwegian Sea marine data 33 (see Methods for further details). Our age model suggests start of interglacial warm conditions at ca. 130 ka and end of the interglacial at ca. 117.5 ka.
Sokli data compared against other proxy and forcing time series. The coloured bars indicate intervals of cool climate at Sokli (solid bars) and their suggested counterparts in other datasets (hatched bars). a, b Reconstructions for Tjan and Tjul based on the Sokli pollen sequence. The reconstructions are expressed as the multi-method median curves (grey curve) with local regression (LOESS; span 0.03, one robustifying iteration) smoothers (red and blue curves) fitted. Black arrows indicate the tie points of the absolute chronology used for Sokli. December and June insolation at 60°N 5 are also shown (orange curves). c– e Marine proxy data from the Nordic and Labrador Seas, including sea-surface temperature proxy data (% Neogloboquadrina pachyderma) from the central Nordic Seas 19, 70 ( c), δ 13C proxy data for North Atlantic Deep Water formation 15 ( d), and planktic δ 18O data from East Greenland Margin 19 ( e). In e, green arrows indicate interpreted locations of glacial meltwater pulses. All marine data are shown aligned 19 with the AICC2012 ice-core chronology 71, 72. f Ice δ 18O records from NEEM 31 and NGRIP 32 ice cores from Greenland, displayed on the AICC2012 chronology 10, 71, 72. g, h Pollen and macrofossil based reconstructions for Tjan and Tjul from the European mid-latitudes. Reconstructions are shown based on the Gröbern (Germany) fossil sequence 41 and for Amsterdam (Netherlands) interpolated from Eemian palaeo-isotherms reconstructed based on fossil data from multiple sites (adapted from ref. 50). The time scales used are floating chronologies based on estimated pollen zone durations 41, shown here anchored at 129 ka. Pollen zones are shown for Central Germany 41. i Speleothem stable isotope data underlying the chronology for Sokli, including δ 18O data for SCH-5 and HÖL-10 speleothems from the Northern Alps 28 and the TKS series from the Entrische Kirche cave in the Eastern Alps 46, as well as δ 13C data for the Han-9 speleothem from Belgium 29. The cross and an error bar indicate the age and associated 2σ uncertainty for the onset of speleothem growth at Korallgrottan, northern Sweden


--- layout: page title: About header-img: "img/about-bg.png" ---
Ghost is a coding wannabe. Full of zeal and charisma. Loves IPA beer, cognac, and an occasional karaoke bar. Also, he only haunts in code .


{% extends "users/topic/detail/top-info.html" %} {% block alt_topic %} {% include 'common/there-is-no-data.html' %}


ccbrowse is an open source web application for browsing data from the CloudSat and CALIPSO satellites. Please see the
GitHub repository
for more information.
cc
browse
About
Layers
…
Keyboard shortcuts
↩
Pan left
↩
Pan right
↑
Pan up
↓
Pan down
+
Zoom in
–
Zoom out
PgUp
Jump left
PgDown
Jump right
,