Plugin Information |
|---|
View Ivy on the plugin site for more information. |
This plugin automatically configures a build to trigger other builds based on dependency configuration via Apache Ivy.
Please Note
Support for Hudson has now been dropped, only Jenkins will be supported from now on.
Plugin download
Supported Versions
Since Version 1.25 this plugin uses Ivy 2.4.0 internally (but it should work with Ivy 2.+ projects)
Creating An Ivy Project (added in version 1.0 of this plugin)
By using an Ivy project instead of a Freestyle project Jenkins can simplify the job configuration. It will auto-detect all the ivy modules you checked out, create builds for them, and automatically generate the upstream/downstream build triggers based on your Ivy dependencies.
- Click on the "New Job" link
- Enter a project name and choose "Build an Ivy project"
- Fill in your SCM details (you can choose to check out a single ivy module, or an entire branch of ivy modules)
- Choose the Ant version to build with and enter the targets you want run. Most of the options have sensible defaults so you only need to fill them in if your modules are set up differently than the default values expect. If you want to build each module as a separate job, expand the "Advanced" section and check "Build modules as separate jobs". If you are polling for changes from your SCM, you can also optionally choose to only build changed modules.
- Now on your Jenkins job page you will see a "Modules" link
- This will give you a view of all the discovered ivy modules you checked out (Note: you will need to build the project once before the modules show up)
- The upstream/downstream project build triggers will be automatically generated from the dependencies in your ivy files.
- If you chose to build the modules as separate jobs, then you can click on a module in the module view to see all the individual builds, SCM changes, artifacts, etc.
- If you want to run different targets on a certain module then you can override the default targets in the module configuration.
Build Trigger Configuration (for Freestyle Projects)
Upon building, it scans the ivy.xml and fills in the 'build other projects' setting, which results in output on the project page of which projects are upstream (depends on) and which are downstream (is a dependency).
Changelog
Version 1.26 (November 28, 2015)
- Fixed https://issues.jenkins-ci.org/browse/JENKINS-13440 - Ivy.xml scanning (Thanks mbechtol)
- Fixed issue when slave nodes offline at startup (Thanks burghduffkc)
Version 1.25.1 (October 8, 2015)
- Fixed java dependency back to Java 1.5
Version 1.25 (September 27, 2015)
- Note: This release has a unintended dependency on Java 1.7
- Fixed https://issues.jenkins-ci.org/browse/JENKINS-29670JENKINS-29670 - Support Ivy 2.4.0
- Fixed https://issues.jenkins-ci.org/browse/JENKINS-24282JENKINS-24282 - Improved wording (Thanks tfennelly)
- Fixed Build now link (Thanks mcupak)
- Migrated build to gradle
- Increased core version to 1.491
Version 1.24 (April 27, 2014)
- Fixed JENKINS-22447 - Ivy Job builds don't release workspace lock
Version 1.23.2 (July 26, 2013)
- Fixed JENKINS-18848 - Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Version 1.23.1 (July 18, 2013)
- Only parse ivy descriptor files when required.
Version 1.23 (July 18, 2013)
- Fix for Jenkins >= 1.522
- Allow absolute paths to be used for properties files.
- Manage global ivy config file using config-file-provider plugin.
- Fixed JENKINS-10025 - break cycle computing dependency graph
Version 1.22 (March 10, 2013)
- Updated to Ivy 2.3.0
Version 1.21 (Feb 6, 2012)
- Fixed JENKINS-12625 - Java-level deadlock between Disk Usage Plugin and Ivy Plugin
- Fixed JENKINS-12638 - Rebuilding dependency graph slow on large numbers of Ivy Projects
Version 1.20 (November 26, 2011)
- Updated to Ivy 2.2.0
Version 1.19 (Jun 9, 2011)
- Fixed a bug introduced in 1.18 where Freestyle Projects using the Ivy Build Trigger would be unable to locate the cached copy of the ivy.xml file.
Version 1.18 (Jun 7, 2011)
- Warning: bug introduced for Freestyle Projects using Ivy Build Trigger, fixed in version 1.19
- Added support in the Freestyle Project Ivy Build Trigger for loading a property file before parsing ivy xml file (contribution from Ed Burcher).
Version 1.17 (May 9, 2011)
- Implemented JENKINS-9464 - Added support for custom workspaces for Ivy Projects
- Note: requires Jenkins 1.410 or newer (Hudson no longer supported)
Version 1.16 (Apr 18, 2011)
- Fixed a compatibility bug with Jenkins version >= 1.406
Version 1.15 (Feb 7, 2011)
- Fixed a compatibility bug with core Hudson/Jenkins version >= 1.395
Version 1.14 (Nov 16, 2010)
- Fixed JENKINS-8012 - Ivy plugin now bundles jsch and commons-vfs since those classes may have to be loaded when parsing the Ivy settings file. Referencing a settings file with sftp/ssh/vfs resolvers should work now.
Version 1.13 (Nov 1, 2010)
- Added support for using build wrappers when building modules as separate jobs. (patch supplied by Jesse Bexten)
- Now build wrappers like locks and latches and the version number plugin can be configured for an Ivy Project that's configured to build its modules as separate jobs. In this case the build wrappers will be applied to each module individually.
- Fixed several oversights in the Ivy module build logic. Logic now more closely resembles that in the standard Build$RunnerImpl. The BuildWrappers are now torn down properly, and return values from post build actions are checked.
Version 1.12 (Oct 22, 2010)
- Fixed a bug whereby any build triggers manually configured for individual Ivy modules were ignored.
- This only affected Ivy Projects using the "Build modules as separate jobs" option and the "Build other projects" option for individual Ivy modules.
Version 1.11 (Oct 14, 2010)
- Added ability to optionally use Parameters from upstream jobs triggered by their Ivy dependencies (patch supplied by Jesse Bexten)
- This applies to Ivy Projects triggering other Ivy Projects, Ivy Projects triggering their own modules to build when they have been configured to build their modules as separate jobs, and also Freestyle jobs using the Ivy Build Trigger to trigger other Freestyle jobs.
- In all cases, an additional checkbox is provided that will cause the builds to use the same parameters as the jobs that triggered them.
Version 1.10 (Sep 30, 2010)
- Added ability to disable the automatic triggering of downstream Ivy dependencies in other Jenkins projects.
- Fixed JENKINS-7602 - Incremental Ivy builds work on Windows now.
Version 1.9 (Jul 29, 2010)
- Fixed spammy exception logging on startup if the NAnt plugin wasn't installed. The NAnt builder extension is now marked as optional.
- Exposed a couple of environment variables in multi-module Ivy builds. Now when building a multi-module Ivy project as separate builds, IVY_MODULE_NAME and IVY_MODULE_ORGANISATION are available. This is leading up to better integration with the Jenkins SonarQube plugin.
- Fixed JENKINS-7085 - Ivy Projects using multi-module, non-aggregated, incremental build will now always build their modules in the correct order
- Note: requires Jenkins 1.358 or newer
Version 1.8 (Jul 21, 2010)
- Added workaround for issue introduced in Jenkins v1.363 where a self-referential build trigger gets created causing a project to trigger itself endlessly JENKINS-6819.
- Implemented JENKINS-6802 - Refactored project builder logic to allow Ivy Project builders to be pluggable. Implemented the Ant (default) and NAnt builder types.
- Applied a patch from the JFrog guys to support integration with the next release of their Artifactory Plugin.
- Implemented JENKINS-6884 - Added ability to specify property files that need to get loaded before parsing the Ivy settings and Ivy module descriptors. This allows Ivy Projects to work properly when using ant property references in the Ivy settings file or module descriptors.
Version 1.7 (May 13, 2010)
- Fixed JENKINS-6468 - Added an option to specify an ivy settings file for Ivy Projects.
Version 1.6 (Apr 27, 2010)
- Fixed JENKINS-6308 - Ivy Project global ANT_OPTS are now saved properly.
Version 1.5 (Apr 1, 2010)
- Fixed several issues with Ivy Project build dependencies for projects configured to build their modules as separate jobs.
- a project can no longer run again until all its module builds have finished (otherwise the svn changes get out of sync between module builds)
- a project will no longer allow downstream projects of its modules to build when their "Block build when upstream project is building" option is selected. This is done by adding a virtual dependency between the parent project and the downstream project that never actually triggers a build, but makes the project show up in the transitive upstream dependencies
- a project will now correctly set up its own modules' build dependencies when "Build whenever an Ivy dependency is built" is unchecked
Version 1.4 (Mar 22, 2010)
- Fixed regression in 1.3 where the specified ant version is not selected when job configuration page is opened.
Version 1.3 (Mar 19, 2010)
- Fixed JENKINS-5961 - Relative paths to ant build files actually work now.
- Removed the need to have a specific Ant installation configured. If none is now configured, no select box will be shown on the job configuration page and Jenkins will just use the "ant" command on your PATH (just like Freestyle projects do). Mentioned in JENKINS-5961.
Version 1.2 (Mar 16, 2010)
- Fixed JENKINS-5823 - Ivy plugin will no longer throw a NullPointerException if you leave the targets field blank.
Version 1.1 (Feb 26, 2010)
- Made sure Ivy Modules can't be built when their parent is disabled
- Implemented incremental build functionality for aggregated builds
- Added option to disable ivy build triggers between Ivy Project jobs.
- Note: requires Jenkins 1.347 or newer
Version 1.0 (Feb 18, 2010)
- Added support for creating Ivy Projects - see Adding Ivy Project Support for information on the development of this feature.
- Note: requires Jenkins 1.346 or newer
Version 0.6 (Jan 19, 2010)
- Fixed JENKINS-4069 - Downstream builds will no longer be triggered when the current build has failed.
- Note: requires Jenkins 1.341 or newer
Version 0.5 (Jan 18, 2010)
- Fixed NullPointerException introduced in 0.4 when no build with a workspace can be found for an ivy-enabled project
- Fixed issue introduced in 0.4 where the ivy.xml backup file was copied into the build directory instead of the project directory
Version 0.4 (Dec 29, 2009)
- Ivy setting on job config page always came up with first entry instead of saved value
- Update uses of deprecated APIs
Version 0.2
- now version 2.0.0 of ivy is supported
- the ivy plugin can now handle builds run on a slave
Attachments:
hudson_ivy_-_project_associations.png (image/png)
new-job.png (image/png)
new-ivy-project.png (image/png)
ivy-project-configuration.png (image/png)
modules.png (image/png)
modules-view.png (image/png)
upstream-downstream.png (image/png)
ivy-module-configuration.png (image/png)
hudson_ivy_build_trigger.png (image/png)
ivy-project-configuration.png (image/png)


This page shows a few examples. The example JSX code is there to illustrate each example, but please note you'll need to supply the appropriate onChange methods and store the country and region values. See the readme for complete documentation on how to add the component to your pages.


This is the game of Dots and Boxes. Two players take turns clicking and dragging to create lines between dots. The player that completes the last side of a box earns a point and an extra turn. When the grid is filled up, the player with the most boxes wins.
Note: This project uses my Polygon project for dot locations and collision detection. For more information, check out my Polygon project under the "Useful Tools" category.
This game is quite simple, but many cases need to be accounted for. For example, a line cannot be drawn on top of another line, after completing a box, that player takes another turn, or a box can only be counted towards one player. Given that such cases can be dealt with with a few if statements, there are still some major game mechanics that require some explanation. These mechanics include: lines can only be drawn between orthogonally adjacent dots, and when a new line completes a box, the box should be colored in.
Let's tackle the first mechanic: lines can only be drawn between orthogonally adjacent dots. To be orthogonally adjacent means to be directly above, below, to the right, or the left of something. In other words, two dots must be directly next to each other, excluding diagonally, for a line to be drawn between them. My first instinct when tackling this problem was to take an array of dots and use the dots' indices to determine whether or not two dots are orthogonally adjacent. However, we can cleverly use the physical distance between the dots to determine this. A dot has to be within a certain distance of another dot for them to be orthogonally adjacent.
The next mechanic to cover is how to detect when a newly created line completes a box. For this to be done, we need to keep a record of all lines previously created. A newly created line can only complete a box in two possible locations depending on whether the line is horizontal or vertical.
To determine if a line is horizontal, we can check if the difference between the indicies of the connected dots is 1. Once we know if the line is horizontal or vertical, we can check the two possible box locations to see if all sides of the box are present. If so, we can color in that box and award a point to the player that created the last line.


Halle Berry injured on set of MMA film 'Bruised'
by Nate DayOscar-winning actress Halle Berry was injured on the set of her latest movie on Monday, according to a new report.
Per the NJ Advance Media, the "Monster's Ball" star, 53, wwas beginning to work on "Bruised" -- a drama set in the world of mixed martial arts -- on Monday, but production was delayed after Berry was injured during a fight scene.
The film's executive producer, Brian Pitt, told the outlet that the injury was "nothing serious."
WHY CHRISTIAN BALE TURNED DOWN A FOURTH 'BATMAN' FILM
“Halle got slightly injured in the fight,” he said. "She’s tired. She needed a break.”
Pitt says that production will likely resume Friday, per actor availability.
Representatives for neither the film or for Berry immediately responded to Fox News' request for comment.
According to Deadline, "Bruised" follows Berry as Justice, a disgraced MMA fighter forced to confront her demons when the six-year-old son she walked out on returns to her doorstep.
Berry is also directing the film, marking her feature directorial debut.
CLICK HERE TO GET THE FOX NEWS APP
No release date for "Bruised" has been announced.


↑
↑
↑
Test Suite
Current Test
Control Panel
Selenium
by
ThoughtWorks
and
friends
For more information on Selenium, visit
http://seleniumhq.org


WOLFGANG K. GILOI and REINHOLD GUETH
Old school paper describing established methods for firmware design, although the scope of firmware at the time was very different.
Unread


This will overwrite "{{ $ctrl.fileModel.name }}". Continue?
Could not parse this Spec. The underlying JavaScript may have been modified.
This Spec was created with plugin version {{ $ctrl.fileModel.version }}
Try running tractor upgrade to automatically upgrade this file.
tractor upgrade


This topography shows how close* a street is to every other street.
Higher - the street is more central. Lower - the street is less central. *"closeness centrality" for you graph theory nerds


| Projects -Oracle 9iAS |
|
Oracle 9iApplication Server (Year 2001-2003)
Yes I know Oracle 9iAS was never the best horse Oracle had. It was
primarily an attempt to have a complete iSuites (########add name here)
instead of best of breed solution( pioneered by Ray Lane ). Oracle has
tried to do some good work by having Orions OC4J for the development of
WebForms and Reports.. and having an EM to manage instances and
configuration settings (even in 11i) instead of changing the
configuration files like httpd.conf manually.
I still feel this needs more tuning from Oracle part to make it
perfect. Especially when i have seen WebLogic and WebSphere.
Coming back to the Oracle 9iAS I still get mails requesting help for implementing the File Upload through Web Forms on Mid tier (something from my archives for 2001-2003 while my stint in Nucleus Software ) Anyway I have kept my notes and binary copy of files I used at this (##########put files here ) place. People can download this and implement it Apart from it there were numerous troubleshooting that was needed for different patchsets Upgrading the oracle Installations and resolving the bugs that came along with it.
Ø Installation of 9i Application Server on NT and UNIX
Ø maintainance of 9i Application Servers
Ø Execution of forms through Listener servlet on 9i Application servers
Ø Implementation of Javabeans/ EJB on 9iAS
Ø File Upload using 9iApplication Server /D2k forms
Ø Font Upload utility on 9iApplication server
You might have come here cursing Oracle 9iAS You can bug me to get a second
opinion on issues you are facing while working on Oracle Application
servers. I will try to help unless I am really very busy.


Try writing in the input field:
The input's valid state is:
Try writing an E-mail address in the input field:
Note that the state of the input field is "true" before you start writing in it, even if it does not contain an e-mail address.
Try leaving the first input field blank:
Name: The name is required.
Address:
We use the ng-show directive to only show the error message if the field has been touched AND is empty.
The input field requires content, and will therefore become green when you write in it.
The form gets a "ng-dirty" class when the form has been modified, and will therefore turn pink.
The input field must contain the character "e" to be consider valid.


Forest of the Lost [ap62], forest, in Imperia, peasants: 140
Last updated Turn #127
Forest of the Lost [ap62], forest, in Imperia, peasants: 140
------------------------------------------------------------------------
23: Pack of wolves [fv4b], wolves, number: 4, went west.
23: Agravain [s7b], refugee, with one skirmisher, went south.
27: Ryzin [k6c], refugee, with one peasant, arrived from the west.
30: Ryzin [k6c], refugee, with one peasant, went east.
30: Wild men [hd9i], savages, number: 23, arrived from the west.
30: The population grows by one peasant.
Routes leaving Forest of the Lost:
North, forest, to Forest of the Lost [ao62], 8 days
East, forest, to Forest of the Lost [ap63], 8 days
South, forest, to Forest of the Lost [aq62], 8 days
West, forest, to Forest of the Lost [ap61], 8 days
Seen here:
Stack of nazgul [hk8n], nazgul, number: 4
Stack of wights [hq0p], wights, number: 36
Stack of giants [ez2u], giants, number: 4
Stack of nazgul [fa0r], nazgul, number: 2
Ryzin [k6c], refugee, with one peasant


For info on exporting click
here
Upload your chat logs here:
(.txt files only)
Choose a file
or drag it here
.
Upload
Uploading…
Done!
Error!
.
×


Examples¶
See Aequitas in action with the following demos.
- COMPAS Analysis using Aequitas
- Pre-Aequitas: Exploring the COMPAS Dataset
- Putting Aequitas to the task
- What biases exist in my model?
- How do I visualize bias in my model?
- What levels of disparity exist between population groups?
- How do I visualize disparities in my model?
- Visualizing disparities between groups in a single user-specified attribute for a single user-specified disparity metric
- Visualizing disparities between all groups for a single user-specified disparity metric
- Visualizing disparities between groups in a single user-specified attribute for default metrics
- Visualizing disparities between groups in a single user-specified attribute for all calculated disparity metrics
- Visualizing disparity between all groups for multiple user-specified disparity metrics
- How do I assess model fairness?
- How do I visualize bias metric parity?
- How do I visualize parity between groups in my model?
- Visualizing parity between groups in a single user-specified attribute for all calculated disparity metrics
- Researcher Check: Could the unfairness I am seeing be related to small group sizes in my sample?
- Visualizing parity between groups in a single user-specified attribute for all calculated disparity metrics
- Visualizing parity between all groups for multiple user-specified disparity metrics
- Visualizing parity between groups in multiple user-specified attributes
- The Aequitas Effect


|
RFC 5234 |
| TOC |
|
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the “Internet Official Protocol Standards” (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order- independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.
|
RFC 5234 |
| TOC |
1.
Introduction
2.
Rule Definition
2.1.
Rule Naming
2.2.
Rule Form
2.3.
Terminal Values
2.4.
External Encodings
3.
Operators
3.1.
Concatenation: Rule1 Rule2
3.2.
Alternatives: Rule1 / Rule2
3.3.
Incremental Alternatives: Rule1 =/ Rule2
3.4.
Value Range Alternatives: %c##-##
3.5.
Sequence Group: (Rule1 Rule2)
3.6.
Variable Repetition: *Rule
3.7.
Specific Repetition: nRule
3.8.
Optional Sequence: [RULE]
3.9.
Comment: ; Comment
3.10.
Operator Precedence
4.
ABNF Definition of ABNF
5.
Security Considerations
6.
References
6.1.
Normative References
6.2.
Informative References
Appendix A.
Acknowledgements
Appendix B.
Core ABNF of ABNF
B.1.
Core Rules
B.2.
Common Encoding
| TOC |
Internet technical specifications often need to define a formal syntax and are free to employ whatever notation their authors deem useful. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. It balances compactness and simplicity with reasonable representational power. In the early days of the Arpanet, each specification contained its own definition of ABNF. This included the email specifications, [RFC733] (Crocker, D., Vittal, J., Pogran, K., and D. Henderson, “Standard for the format of ARPA network text messages,” November 1977.) and then [RFC822] (Crocker, D., “Standard for the format of ARPA Internet text messages,” August 1982.), which came to be the common citations for defining ABNF. The current document separates those definitions to permit selective reference. Predictably, it also provides some modifications and enhancements.
The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. Appendix B (Core ABNF of ABNF) supplies rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. It is provided as a convenience and is otherwise separate from the meta language defined in the body of this document, and separate from its formal status.
| TOC |
| TOC |
The name of a rule is simply the name itself, that is, a sequence of characters, beginning with an alphabetic character, and followed by a combination of alphabetics, digits, and hyphens (dashes).
- NOTE:
- Rule names are case insensitive.
The names <rulename>, <Rulename>, <RULENAME>, and <rUlENamE> all refer to the same rule.
Unlike original BNF, angle brackets ("<", ">") are not required. However, angle brackets may be used around a rule name whenever their presence facilitates in discerning the use of a rule name. This is typically restricted to rule name references in free-form prose, or to distinguish partial rules that combine into a string not separated by white space, such as shown in the discussion about repetition, below.
| TOC |
A rule is defined by the following sequence:
name = elements crlf
where <name> is the name of the rule, <elements> is one or more rule names or terminal specifications, and <crlf> is the end-of-line indicator (carriage return followed by line feed). The equal sign separates the name from the definition of the rule. The elements form a sequence of one or more rule names and/or value definitions, combined according to the various operators defined in this document, such as alternative and repetition.
For visual ease, rule definitions are left aligned. When a rule requires multiple lines, the continuation lines are indented. The left alignment and indentation are relative to the first lines of the ABNF rules and need not match the left margin of the document.
| TOC |
Rules resolve into a string of terminal values, sometimes called characters. In ABNF, a character is merely a non-negative integer. In certain contexts, a specific mapping (encoding) of values into a character set (such as ASCII) will be specified.
Terminals are specified by one or more numeric characters, with the base interpretation of those characters indicated explicitly. The following bases are currently defined:
b = binary d = decimal x = hexadecimal
Hence:
CR = %d13 CR = %x0D
respectively specify the decimal and hexadecimal representation of [US‑ASCII] (American National Standards Institute, “Coded Character Set -- 7-bit American Standard Code for Information Interchange,” 1986.) for carriage return.
A concatenated string of such values is specified compactly, using a period (".") to indicate a separation of characters within that value. Hence:
CRLF = %d13.10
ABNF permits the specification of literal text strings directly, enclosed in quotation marks. Hence:
command = "command string"
Literal text strings are interpreted as a concatenated set of printable characters.
- NOTE:
- ABNF strings are case insensitive and the character set for these strings is US-ASCII.
Hence:
rulename = "abc"
and:
rulename = "aBc"
will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC", and "ABC".
To specify a rule that is case sensitive, specify the characters individually.
For example:
rulename = %d97 %d98 %d99
or
rulename = %d97.98.99
will match only the string that comprises only the lowercase characters, abc.
| TOC |
External representations of terminal value characters will vary according to constraints in the storage or transmission environment. Hence, the same ABNF-based grammar may have multiple external encodings, such as one for a 7-bit US-ASCII environment, another for a binary octet environment, and still a different one when 16-bit Unicode is used. Encoding details are beyond the scope of ABNF, although Appendix B (Core ABNF of ABNF) provides definitions for a 7-bit US-ASCII environment as has been common to much of the Internet.
By separating external encoding from the syntax, it is intended that alternate encoding environments can be used for the same syntax.
| TOC |
| TOC |
A rule can define a simple, ordered string of values (i.e., a concatenation of contiguous characters) by listing a sequence of rule names. For example:
foo = %x61 ; a bar = %x62 ; b mumble = foo bar foo
So that the rule <mumble> matches the lowercase string "aba".
Linear white space: Concatenation is at the core of the ABNF parsing model. A string of contiguous characters (values) is parsed according to the rules defined in ABNF. For Internet specifications, there is some history of permitting linear white space (space and horizontal tab) to be freely and implicitly interspersed around major constructs, such as delimiting special characters or atomic strings.
NOTE:
This specification for ABNF does not provide for implicit specification of linear white space.
Any grammar that wishes to permit linear white space around delimiters or string segments must specify it explicitly. It is often useful to provide for such white space in "core" rules that are then used variously among higher-level rules. The "core" rules might be formed into a lexical analyzer or simply be part of the main ruleset.
| TOC |
Elements separated by a forward slash ("/") are alternatives. Therefore,
foo / bar
will accept <foo> or <bar>.
- NOTE:
- A quoted string containing alphabetic characters is a special form for specifying alternative characters and is interpreted as a non-terminal representing the set of combinatorial strings with the contained characters, in the specified order but with any mixture of upper- and lowercase.
| TOC |
It is sometimes convenient to specify a list of alternatives in fragments. That is, an initial rule may match one or more alternatives, with later rule definitions adding to the set of alternatives. This is particularly useful for otherwise independent specifications that derive from the same parent ruleset, such as often occurs with parameter lists. ABNF permits this incremental definition through the construct:
oldrule =/ additional-alternatives
So that the ruleset
ruleset = alt1 / alt2 ruleset =/ alt3 ruleset =/ alt4 / alt5
is the same as specifying
ruleset = alt1 / alt2 / alt3 / alt4 / alt5
| TOC |
A range of alternative numeric values can be specified compactly, using a dash ("-") to indicate the range of alternative values. Hence:
DIGIT = %x30-39
is equivalent to:
DIGIT = "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9"
Concatenated numeric values and numeric value ranges cannot be specified in the same string. A numeric value may use the dotted notation for concatenation or it may use the dash notation to specify one value range. Hence, to specify one printable character between end-of-line sequences, the specification could be:
char-line = %x0D.0A %x20-7E %x0D.0A
| TOC |
Elements enclosed in parentheses are treated as a single element, whose contents are strictly ordered. Thus,
elem (foo / bar) blat
matches (elem foo blat) or (elem bar blat), and
elem foo / bar blat
matches (elem foo) or (bar blat).
- NOTE:
- It is strongly advised that grouping notation be used, rather than relying on the proper reading of "bare" alternations, when alternatives consist of multiple rule names or literals.
Hence, it is recommended that the following form be used:
(elem foo) / (bar blat)
It will avoid misinterpretation by casual readers.
The sequence group notation is also used within free text to set off an element sequence from the prose.
| TOC |
The operator "*" preceding an element indicates repetition. The full form is:
<a>*<b>element
where <a> and <b> are optional decimal values, indicating at least <a> and at most <b> occurrences of the element.
Default values are 0 and infinity so that *<element> allows any number, including zero; 1*<element> requires at least one; 3*3<element> allows exactly 3; and 1*2<element> allows one or two.
| TOC |
A rule of the form:
<n>element
is equivalent to
<n>*<n>element
That is, exactly <n> occurrences of <element>. Thus, 2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters.
| TOC |
Square brackets enclose an optional element sequence:
[foo bar]
is equivalent to
*1(foo bar).
| TOC |
A semicolon starts a comment that continues to the end of line. This is a simple way of including useful notes in parallel with the specifications.
| TOC |
The various mechanisms described above have the following precedence, from highest (binding tightest) at the top, to lowest (loosest) at the bottom:
Rule name, prose-val, Terminal value
Comment
Value range
Repetition
Grouping, Optional
Concatenation
Alternative
Use of the alternative operator, freely mixed with concatenations, can be confusing.
Again, it is recommended that the grouping operator be used to make explicit concatenation groups.
| TOC |
- NOTES:
- This syntax requires a formatting of rules that is relatively strict. Hence, the version of a ruleset included in a specification might need preprocessing to ensure that it can be interpreted by an ABNF parser.
- This syntax uses the rules provided in Appendix B (Core ABNF of ABNF).
rulelist = 1*( rule / (*c-wsp c-nl) ) rule = rulename defined-as elements c-nl ; continues if next line starts ; with white space rulename = ALPHA *(ALPHA / DIGIT / "-") defined-as = *c-wsp ("=" / "=/") *c-wsp ; basic rules definition and ; incremental alternatives elements = alternation *c-wsp c-wsp = WSP / (c-nl WSP) c-nl = comment / CRLF ; comment or newline comment = ";" *(WSP / VCHAR) CRLF alternation = concatenation *(*c-wsp "/" *c-wsp concatenation) concatenation = repetition *(1*c-wsp repetition) repetition = [repeat] element repeat = 1*DIGIT / (*DIGIT "*" *DIGIT) element = rulename / group / option / char-val / num-val / prose-val group = "(" *c-wsp alternation *c-wsp ")" option = "[" *c-wsp alternation *c-wsp "]" char-val = DQUOTE *(%x20-21 / %x23-7E) DQUOTE ; quoted string of SP and VCHAR ; without DQUOTE num-val = "%" (bin-val / dec-val / hex-val) bin-val = "b" 1*BIT [ 1*("." 1*BIT) / ("-" 1*BIT) ] ; series of concatenated bit values ; or single ONEOF range dec-val = "d" 1*DIGIT [ 1*("." 1*DIGIT) / ("-" 1*DIGIT) ] hex-val = "x" 1*HEXDIG [ 1*("." 1*HEXDIG) / ("-" 1*HEXDIG) ] prose-val = "<" *(%x20-3D / %x3F-7E) ">" ; bracketed string of SP and VCHAR ; without angles ; prose description, to be used as ; last resort
| TOC |
Security is truly believed to be irrelevant to this document.
| TOC |
| TOC |
| [US-ASCII] | American National Standards Institute, “Coded Character Set -- 7-bit American Standard Code for Information Interchange,” ANSI X3.4, 1986. |
| TOC |
| [RFC733] | Crocker, D., Vittal, J., Pogran, K., and D. Henderson, “Standard for the format of ARPA network text messages,” RFC 733, November 1977. |
| [RFC822] | Crocker, D., “Standard for the format of ARPA Internet text messages,” STD 11, RFC 822, August 1982. |
| TOC |
The syntax for ABNF was originally specified in RFC 733. Ken L. Harrenstien, of SRI International, was responsible for re-coding the BNF into an Augmented BNF that makes the representation smaller and easier to understand.
This recent project began as a simple effort to cull out the portion of RFC 822 that has been repeatedly cited by non-email specification writers, namely the description of Augmented BNF. Rather than simply and blindly converting the existing text into a separate document, the working group chose to give careful consideration to the deficiencies, as well as benefits, of the existing specification and related specifications made available over the last 15 years, and therefore to pursue enhancement. This turned the project into something rather more ambitious than was first intended. Interestingly, the result is not massively different from that original, although decisions, such as removing the list notation, came as a surprise.
This "separated" version of the specification was part of the DRUMS working group, with significant contributions from Jerome Abela, Harald Alvestrand, Robert Elz, Roger Fajman, Aviva Garrett, Tom Harsch, Dan Kohn, Bill McQuillan, Keith Moore, Chris Newman, Pete Resnick, and Henning Schulzrinne.
Julian Reschke warrants a special thanks for converting the Draft Standard version to XML source form.
| TOC |
This appendix contains some basic rules that are in common use. Basic rules are in uppercase. Note that these rules are only valid for ABNF encoded in 7-bit ASCII or in characters sets that are a superset of 7-bit ASCII.
| TOC |
Certain basic rules are in uppercase, such as SP, HTAB, CRLF, DIGIT, ALPHA, etc.
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z BIT = "0" / "1" CHAR = %x01-7F ; any 7-bit US-ASCII character, ; excluding NUL CR = %x0D ; carriage return CRLF = CR LF ; Internet standard newline CTL = %x00-1F / %x7F ; controls DIGIT = %x30-39 ; 0-9 DQUOTE = %x22 ; " (Double Quote) HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F" HTAB = %x09 ; horizontal tab LF = %x0A ; linefeed LWSP = *(WSP / CRLF WSP) ; Use of this linear-white-space rule ; permits lines containing only white ; space that are no longer legal in ; mail headers and have caused ; interoperability problems in other ; contexts. ; Do not use when defining mail ; headers and use with caution in ; other contexts. OCTET = %x00-FF ; 8 bits of data SP = %x20 VCHAR = %x21-7E ; visible (printing) characters WSP = SP / HTAB ; white space
| TOC |
Externally, data are represented as "network virtual ASCII" (namely, 7-bit US-ASCII in an 8-bit field), with the high (8th) bit set to zero. A string of values is in "network byte order", in which the higher-valued bytes are represented on the left-hand side and are sent over the network first.
| TOC |
| Dave Crocker (editor) | |
| Brandenburg InternetWorking | |
| 675 Spruce Dr. | |
| Sunnyvale, CA 94086 | |
| US | |
| Phone: | +1.408.246.8253 |
| EMail: |<EMAIL_ADDRESS>|
| Paul Overell | |
| THUS plc. | |
| 1/2 Berkeley Square, | |
| 99 Berkeley Street | |
| Glasgow G3 7HR | |
| UK | |
| EMail: |<EMAIL_ADDRESS>|
| TOC |
Copyright © The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.


Recording with Firefox 48 / Camera 53
Start Camera
Stop Camera
Start Recording
Stop Recording
Download


Free abelian monoids#
AUTHORS:
David Kohel (2005-09)
Sage supports free abelian monoids on any prescribed finite number
\(n\geq 0\) of generators. Use the
FreeAbelianMonoid
function to create a free abelian
monoid, and the gen
and gens
functions to obtain the corresponding generators. You can print the
generators as arbitrary strings using the optional
names
argument to the
FreeAbelianMonoid
function.
EXAMPLE 1: It is possible to create an abelian monoid in zero or more variables; the syntax T(1) creates the monoid identity element even in the rank zero case.
sage: T = FreeAbelianMonoid(0, '')
sage: T
Free abelian monoid on 0 generators ()
sage: T.gens()
()
sage: T(1)
1
EXAMPLE 2: A free abelian monoid uses a multiplicative representation of elements, but the underlying representation is lists of integer exponents.
sage: F = FreeAbelianMonoid(5,names='a,b,c,d,e')
sage: (a,b,c,d,e) = F.gens()
sage: a*b^2*e*d
a*b^2*d*e
sage: x = b^2*e*d*a^7
sage: x
a^7*b^2*d*e
sage: x.list()
[7, 2, 0, 1, 1]
- sage.monoids.free_abelian_monoid.FreeAbelianMonoid(index_set=None, names=None, **kwds)#
Return a free abelian monoid on \(n\) generators or with the generators indexed by a set \(I\).
We construct free abelian monoids by specifing either:
the number of generators and/or the names of the generators
the indexing set for the generators (this ignores the other two inputs)
INPUT:
index_set
– an indexing set for the generators; if an integer, then this becomes \(\{0, 1, \ldots, n-1\}\)names
– names of generators
OUTPUT:
A free abelian monoid.
EXAMPLES:
sage: F.<a,b,c,d,e> = FreeAbelianMonoid(); F Free abelian monoid on 5 generators (a, b, c, d, e) sage: FreeAbelianMonoid(index_set=ZZ) Free abelian monoid indexed by Integer Ring sage: FreeAbelianMonoid(names='x,y') Free abelian monoid on 2 generators (x, y)
- class sage.monoids.free_abelian_monoid.FreeAbelianMonoidFactory#
Bases:
UniqueFactory
Create the free abelian monoid in \(n\) generators.
INPUT:
n
- integernames
- names of generators
OUTPUT: free abelian monoid
EXAMPLES:
sage: FreeAbelianMonoid(0, '') Free abelian monoid on 0 generators () sage: F = FreeAbelianMonoid(5,names = list("abcde")) sage: F Free abelian monoid on 5 generators (a, b, c, d, e) sage: F(1) 1 sage: (a, b, c, d, e) = F.gens() sage: mul([ a, b, a, c, b, d, c, d ], F(1)) a^2*b^2*c^2*d^2 sage: a**2 * b**3 * a**2 * b**4 a^4*b^7
sage: loads(dumps(F)) is F True
- create_key(n, names)#
- create_object(version, key)#
- class sage.monoids.free_abelian_monoid.FreeAbelianMonoid_class(n, names)#
Bases:
Parent
Free abelian monoid on \(n\) generators.
- Element#
alias of
FreeAbelianMonoidElement
- cardinality()#
Return the cardinality of
self
, which is \(\infty\).EXAMPLES:
sage: F = FreeAbelianMonoid(3000, 'a') sage: F.cardinality() +Infinity
- gen(i=0)#
The \(i\)-th generator of the abelian monoid.
EXAMPLES:
sage: F = FreeAbelianMonoid(5,'a') sage: F.gen(0) a0 sage: F.gen(2) a2
- gens()#
Return the generators of
self
.EXAMPLES:
sage: F = FreeAbelianMonoid(5,'a') sage: F.gens() (a0, a1, a2, a3, a4)
- ngens()#
The number of free generators of the abelian monoid.
EXAMPLES:
sage: F = FreeAbelianMonoid(3000, 'a') sage: F.ngens() 3000
- sage.monoids.free_abelian_monoid.is_FreeAbelianMonoid(x)#
Return True if \(x\) is a free abelian monoid.
EXAMPLES:
sage: from sage.monoids.free_abelian_monoid import is_FreeAbelianMonoid sage: is_FreeAbelianMonoid(5) False sage: is_FreeAbelianMonoid(FreeAbelianMonoid(7,'a')) True sage: is_FreeAbelianMonoid(FreeMonoid(7,'a')) False sage: is_FreeAbelianMonoid(FreeMonoid(0,'')) False


West Ham youngster facing axe from Pellegrini despite impressive loan spell
by Ron CarneIt’s been reported that West Ham boss Manuel Pellegrini doesn’t see a future for youngster Sead Haksabanovic with the Hammers.
The 20-year-old joined West Ham in 2017 but having made just two appearances for the senior side, he has since been shipped out on loan to Malaga and Norrkoping.
SEE MORE: Journalist reveals West Ham transfer plans in January and insight on Pellegrini future
While his brief stint in Spain didn’t work out, he’s seemingly showing the quality now that first attracted the Hammers to make their move.
With six goals and eight assists in 29 appearances, it could be argued that the midfield ace is worth giving a shot to in the Premier League.
However, as reported by Hammers News, via Claret and Hugh, it has been suggested that Pellegrini doesn’t see a future in England for Haksabanovic, and so he will either be sent out on loan again next season or be allowed to search for a permanent move elsewhere.
That will be a bitter disappointment for the player himself as he will undoubtedly have been hoping that if he had impressed while out on loan, it would be enough to convince the West Ham boss to give him an opportunity to impress in his squad.
Unfortunately for him, that doesn’t seem likely, and so he’ll now perhaps have to hope that his form for Norrkoping has attracted attention from elsewhere around Europe and he can still have a chance of a big move further down the line.


self._norm_epsilon = norm_epsilon
def __call__(self, inputs, is_training=None):
with backend.get_graph().as_default():
model = SpineNet(
input_specs=self._input_specs,
min_level=self._min_level,
self._norm_epsilon = norm_epsilon
def __call__(self, inputs, is_training=None):
with keras_utils.maybe_enter_backend_graph():
model = SpineNet(
input_specs=self._input_specs,
min_level=self._min_level,


Notebooks
Story: About the Daybreak Star
About the Daybreak Star
Title
About the Daybreak Star
Collection
Summary
About the Daybreak (Day's Heart or Dawn's Heart) Star which has a heart (that is red and 'flesh'). The Daybreak Star has a Daybreak Star Heart child when it is an old Daybreak Star Heart. Besides a short statement of the nature of the Dawn’s–Heart, and of his child (L II.-2. 292 and 293), we have two long pieces.


Explore creative projects and help bring bold new ideas into the world
Our mission is to share your creative ideas, help you find resources and make your dreams a reality.


{% extends 'django_imager/base.html' %} {% block title %}Hooray!{% endblock %} {% block content %}
Thank you {{ user }}! You are activated! This means you are an active user of this site. Please continue to be so.


{% if not active_subscription %}
Thanks for trying JestFlix!
Click below for 31 days of unlimited ad-free Premium Access.
→ Subscribe ←
{% endif %}


The Solar System is the gravitationally bound system of the Sun and the objects that orbit it, either directly or indirectly. Of the objects that orbit the Sun directly, the largest are the eight planets, with the remainder being smaller objects, the dwarf planets and small Solar System bodies. Of the objects that orbit the Sun indirectly—the natural satellites—two are larger than the smallest planet, Mercury.
The Solar System formed 4.6 billion years ago from the gravitational collapse of a giant interstellar molecular cloud. The vast majority of the system's mass is in the Sun, with the majority of the remaining mass contained in Jupiter. The four smaller inner planets, Mercury, Venus, Earth and Mars, are terrestrial planets, being primarily composed of rock and metal. The four outer planets are giant planets, being substantially more massive than the terrestrials. The two largest planets, Jupiter and Saturn, are gas giants, being composed mainly of hydrogen and helium; the two outermost planets, Uranus and Neptune, are ice giants, being composed mostly of substances with relatively high melting points compared with hydrogen and helium, called volatiles, such as water, ammonia and methane. All eight planets have almost circular orbits that lie within a nearly flat disc called the ecliptic.


Guide to the Hunt
Start Here!
Thought 2020 was bad? You've now been transported to an alternate reality, Alt-NUS, where magic exists. The university seems the same, except that different subjects are taught in the faculties now. You need to solve puzzles on your quest to unlock the enigma (an interdimensional portal) to get back to the actual NUS. Visit each faculty to solve puzzles and learn new spells. Prove your worth to the wizards and find your way back to reality! Head over to the map to start your journey!
Events
You will need to attend these events to obtain clues for the relevant puzzles.
- QET Briefing - 4 July 2 p.m.
- CCA Sharing - 9 July 2 p.m.
Submissions
After logging in, you will able to submit the answer for each puzzle on the respective puzzle pages.
Please contact your OGL for the Team Name and Password.
Some important points to note:
- Only one person from each team needs to submit the answer for each puzzle.
- Submit your answer using only the characters a-zA-Z, and spaces.
- After each submission, you should receive one of 2 responses. ("Correct" or "Incorrect")
- You can go to the puzzle list for an overview of your team's progress.
Hints
Each team will be given 10 hint credits at the start of the hunt.
You can earn extra hint credits through exchanging friendship leaderboard (FSL) points.
- You can exchange 10 FSL points for 1 hint credit (max 10 credits). Please ask your OGL to contact Sean to update your credits.
- You can exchange 30 FSL points to know the puzzles related to a metapuzzle (no cap on this). Please ask your OGL to contact Sean for this.
- Hints for all puzzles cost 1 credit, except for metapuzzle hints which cost 2 credits.
- You can be assured that if more than 1 team requests a hint for the same puzzle, they will receive the same hint.
Scoring
We use a simple scoring system for this puzzle hunt.
The leaderboard can be found here .
Details are as follows:
- Each team starts with 10 base points.
- Each puzzle is worth 1-5 points, depending on the difficulty.
- Each metapuzzle is worth 8 points.
- The final puzzle (metametapuzzle) is worth 15 points.
Technical Issues
The features of this site have primarily been tested with Chrome.
It is best viewed on a laptop/desktop PC and not a phone.
If you've found an error in a puzzle or a link is broken, contact us at this email.
You can also email us for clarifications.
IMPORTANT
- For urgent matters regarding the hunt, please PM Sean or Ren Jie.
- Voiding puzzles and requesting for hints through the system are irreversible options, we will not entertain requests to revert these actions.
Updates
- If there are any changes to the puzzles (due to any errors), it will be announced at the errata page.


BloodSpell Press
We've been lucky enough to garner quite a bit of press attention over the past few years - here are all the articles and comments we know of!
If you're looking for materials you can use in an article, head right on over to our Press Release and our Print and Web-Ready Images
Press Articles
- The Making Of Machinima (The Guardian)
- BloodSpell on Wikipedia
- BloodSpell on Boingboing.net and More BoingBoing.net
- BoingBoing on our MPAA/FACT pisstake.
- Profile of BloodSpell on Bioware.com - interview with Hugh on the release.
- WIP report on BloodSpell at Bioware.com
- The Making of BloodSpell part 1, part 2, part 3 at Bioware.com - interviews with the crew.
- Des Machinima-Filmepos erster Teil zum freien Download on Gulli.com
- BloodSpell: Abend füllender Fantasy-Film in Spielegrafik on Netzwelt.de
- BloodSpell on SuicideGirls (boy, were we pleased about this one!)
- BloodSpell on URLWire
- Great big group project - BloodSpell on USAToday's TechSpace blog
- BloodSpell Spotlight on NWVault
- Numerous articles on BloodSpell over at 3dFilmmaker
- BloodSpell on OpenBusiness.cc
- Propping Up Some Successes on Paul Marino's blog
- BloodSpell: Machinima-Animationsfilm unter CC on Netzpolitik.de
- Indie fantasy movie 'Bloodspell' released on Regional Film and Video
- BloodSpell Machinima Goth Funks It Up on GameSetWatch
- Profile of Hugh and BloodSpell writeup
- Making Machinima on Filmmaker Magazine's blog
- Review of BloodSpell over at RPG.net
- BloodSpell reviews on Episodes 8 and 9 of Machinima Live.
- Review of BloodSpell Episode 1 on SciFi UK.
- Part 1, Part 2 and Part 3 of ArsGeek's HOW-TO on burning BloodSpell to DVD.
- BloodSpell - The Machinima You Wish You Could Make on GayGamer.net
- BloodSpell on the Forbidden Planet blog
- Author Alan Campbell on BloodSpell.
- Review of BloodSpell Ep 1-6 on The English Assassin and follow-up review of Ep 7 and 8.
- BloodSpell: Bigger Than Jesus, according to The Overcast.
- The Leipzig Controversy: BoingBoing, Greg Costikyan, Blue's News, 3D Filmmaker, Yigg.de, Xirdalium, Digg, Machinima Premiere (oddly, Machinima.com didn't report), Sorcerer's Place, and more.
- The Daily Telegraph on BloodSpell
- Animation World Network on BloodSpell's release
- BloodSpell Episode 8 reviewed on, er, The Machinima Review.
- Hugh and BloodSpell are quoted and referenced, respectively, in The Escapist
- We were featured on Creativecommons.org, although I seem to have lost the link.
- Ricky Grove writes a retrospective on the work of Phil Rice, BloodSpell sound designer and Machinima genius, including quite a bit on BloodSpell.
- 3D Filmmaker on Episodes 12 and 13.
- iCommons talked about us in their round-up of Creative Commons feature films.
- We got Dugg.
- Regarde.org also said some very nice things that I can nearly understand.
- Belligerati described us as Machinima Worth Watching
- Gulli wrote up a piece on us, which has been very popular.
- Cory at BoingBoing wrote up our final episode, describing now as "the perfect time" to watch BloodSpell. Thanks, Cory!
- SimonC over at GameSetWatch reported that BloodSpell has splattered to an end.
- Joe Gordon at Forbidden Planet reported on our final ep - and I'll get round to that interview soon, Joe, I promise!
- And the final episode is reviewed (and very nice things said) in the latest episode of The Machinima Review.
- BloodSpell on the Neverwinter Nights Podcast
- French blogger Pickiboon raved about BloodSpell.
- Matt "Swarm of Angels" Hanson said some very nice things about us over at Eternal Gaze.
- BloodSpell on Italian site Cinetma.org.
- Ben King, writer for More Four, introduces Machinima with BloodSpell as his top example.
- Channel 4's More Four features BloodSpell.
- Free Pixel talks about cultural influences in Machinima, citing BloodSpell.
- Hrej.cz on BloodSpell.
- The infamous drunken Overcast podcast, this being Part 1 discussing BloodSpell.
- WowInsider interview with Johnnie and Hugh talking about BloodSpell, Machinima for Dummies and more.
- BBC.co.uk article on Machinima for the Machinima Europe festival including a pretty extensive mention of BloodSpell
- Digital Planet Podcast including an interview with Hugh and Johnnie.
Other Offline Press
- CNN Europe, September 2005
- The List Edinburgh, September 2005
- Radio Cafe, BBC Radio, May 2005
- SFX Magazine, June 2006
- Hi-Tech Scotland, August 2006
- PC Plus Magazine, September 2006
- Imagine Magazine, September 2006
- The Daily Telegraph, September 2006
- Digital Planet, BBC World Service, October 2007
Shows and Appearances
- Cameo Edinburgh, October 2005
- Bradford Animation Festival, November 2005
- Machinima Film Festival, November 2005
- FMX, May 2006 (Audioblog)
- Edinburgh Interactive Entertainment Festival, August 2006
- RvBTO, Toronto, August 2006
- Leipzig Games Conference, August 2006
- Medienwoche Berlin, August 2006
- Spectrum Festival, Edinburgh, October 2006
- Savannah Film Festival, November 2006
- Bitfilm Festival, Hamburg, November 2006
- Machinima Film Festival, New York, November 2006
- Brazilian International Free Software Forum, April 2007
- Art In Games at Abertay University, May 2007
- Pompidou Center, Paris, May 2007
- Annecy International Animated Film Festival, June 2007
- SiliCon San Jose, October 2007
- Machinima Europe Festival, Leicester, October 2007
- Arcadia, Montreal,November 2007
- Glasgow Games Society Convention, February 2008
Awards and nominations
- Nomination: Best Machinima Movie - GameShadow Innovation In Games Awards
- Nominations: Best Series, Best Technical Achievement - Machinima Film Festival 2006
- Best Machinima July 2006 - Sims 99
- Movie of the Month, July 2006 - Machinima Premiere
- Movie of the Month, August 2006 - Machinima Premiere
- Movie of the Month, October 2006 - Machinima Premiere
- Movie of the Month, December 2006 - Machinima Premiere
- Movie of the Season, Q4 2006 - Machinima Premiere
- Movie of the Year (Bronze), 2006-2007 - Machinima Premiere
- Nominations: Best Series, Best Technical Achievement - Machinima Europe
- Gold Medal Winner, Best Technical Achievement, Online Machinima Film Festival 2007.
- Gold Medal Winner, Best Custom Content, Online Machinima Film Festival 2007.
- Silver Medal Winner, Best Series, Online Machinima Film Festival 2007.


view all words
add a word
find a specific word
remove a specific word
replace a specific word
search within the words
clear all words


Section 10.3 Ocean temperatures
Sea Surface Temperature (SST)
The temperature of the ocean is reported as Sea Surface Temperature (SST), typically measured a 1-3 meters below the surface (but as deep as 20 meters). Three distinct layers can be recognized in the thermal profile of the oceans:
the surface zone or mixed layer (top 100 meters) that has the highest temperatures, and the largest variations in temperature as a function of altitude;
the thermocline, a zone of rapidly decreasing temperatures with depth;
the deep zone (below 1000 meters depth) where the temperature is consistently 1-3 C regardless of latitude
Sea Surface Temperature Anomaly (SSTA)
Another measure of ocean temperature is the Sea Surface Temperature Anomaly (SSTA): which the difference between the nightime SST and the monthly mean nighttime SST based on climate observations over several years. In other words, the SSTA compares the current temperature to "normal" or expected temperatures for a given time of year. Unusually high SSTA values can lead to thermal stress of coral reefs and coral bleaching events.
SST patterns
A number of persistent SST patterns emerge from ocean observations:
-
middle latitudes (and subtropics):
western coasts are bordered by cool water
eastern coasts are bordered by warm water
tropical latitudes: western coasts bordered by warm water
polar latitudes: eastern coasts bordered by cold water
These temperature patterns can be explained by ocean circulation more generally:
ocean current patterns generally resemble wind patterns
global-scale wind patterns blow over large regions and push the ocean in the same direction as the wind
a gyre is an ocean circulation that forms a closed loop across an ocean basin; these spin in the same direction as anticyclones, sending warm water poleward and cool water equatorward
winds of subtropical highs tend to cause cold water to flow toward the equator along western coasts
Ocean currents and the Ekman spiral
friction between the air and the sea surfaces causes the air to move
the Coriolis effect creates a tendency for the water to veer to the right (in the northern hemisphere) or the left (in the southern hemisphere)
the movement of water influences the next layer of water underneath; this underlying layer will also experience a Coriolis tendency to turn
over the column of water, a pattern emerges in the shape of a spiral
the net result: water tends to move to the right (NH) or left (SH) in Ekman transport
Circulation and upwelling
Ocean currents can act to push surface water toward or away from the coast, which will tend to lead to downwelling or upwelling, respectively. This upwelling plays an important role in primary (biological) production, by bringing cold, nutrient-rich water to surface waters (where photosynthesis can play a larger role).
Good examples of circulation-induced upwelling is along the coast of California, where cold water moving down the coast has a tendency to veer right (west) and promote upwelling, or the Humboldt current along the west coast of South America, where the cold water moving along the coast has a tendency to veer left (west), promoting upwelling and (under normal conditions) maintaining a westward flow of cold water along the equatorial zone.


STDC Level Creator Tool
After you have set up the level with the tools below, copy and paste this:
into a new issue.
- Find a lifeguard saving lives on YouTube.
Copy and paste the video url: https://www.youtube.com/watch?v=
Click at the appropriate times while video is playing:
Watch video again, confirm swimmer status changes:
Move and scale the red box over the drowning swimmer.


Please input the csv file to upload for the application.
Below is the information for the selected user.
| ID | Name | Age | Address | Team |
|---|---|---|---|---|
| {{selected_person.id}} | {{selected_person.name}} | {{selected_person.age}} | {{selected_person.address}} | {{selected_person.team}} |


About Me
| Full Name | Eileen K. Ruiz |
|---|---|
| Skill | Graphic Design, Font-End Development, Web Development |
| Date of Birth | 19th January 2017 |
Biography
Hello ! I’m Eileen K. Ruiz. Senior web developer of themelooks.com from last 5 years many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing
Work Experience
-
Graphic Designer 2010 - 2012
Graphicriver.net at Sydney
-
There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour which don't look even slightly believable.
-
Font-End Developer 2012 - 2014
Themeforest.net at Australia
-
There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour which don't look even slightly believable.
-
Web Developer 2014 - Still Now
Codecanyon.net at Sydney
-
There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour which don't look even slightly believable.
Contact
| Phone | +1610-559-8246 |
|---|---|
| [email protected] | |
| Website | example.com |
| Address | 123 Lorem St., California, United States |


LOYALTY HAS ITS PERKS
Get in on the loyalty program where you can earn points and unlock serious perks.
Starting with these as soon as you join:
- 15% off welcome offer
- Free shipping, returns and exchanges on all orders
- $10 off a purchase on your birthday
- Early access to products
- Exclusive offers & rewards


| Interface | Description |
|---|---|
| Clock |
An interface through which system clocks can be read.
|
| MediaClock |
Tracks the progression of media time.
|
| Predicate<T> |
Determines a true of false value for a given input.
|
| Class | Description |
|---|---|
| Assertions |
Provides methods for asserting the truth of expressions and properties.
|
| AtomicFile |
A helper class for performing atomic operations on a file by creating a backup file until a write
has successfully completed.
|
| CodecSpecificDataUtil |
Provides static utility methods for manipulating various types of codec specific data.
|
| ColorParser |
Parser for color expressions found in styling formats, e.g.
|
| ConditionVariable |
A condition variable whose
ConditionVariable.open() and ConditionVariable.close() methods return whether they
resulted in a change of state. |
| FlacStreamInfo |
Holder for FLAC stream info.
|
| LibraryLoader |
Configurable loader for native libraries.
|
| LongArray |
An append-only, auto-growing
long[] . |
| MimeTypes |
Defines common MIME types and helper methods.
|
| NalUnitUtil |
Utility methods for handling H.264/AVC and H.265/HEVC NAL units.
|
| NalUnitUtil.PpsData |
Holds data parsed from a picture parameter set NAL unit.
|
| NalUnitUtil.SpsData |
Holds data parsed from a sequence parameter set NAL unit.
|
| ParsableBitArray |
Wraps a byte array, providing methods that allow it to be read as a bitstream.
|
| ParsableByteArray |
Wraps a byte array, providing a set of methods for parsing data from it.
|
| ParsableNalUnitBitArray |
Wraps a byte array, providing methods that allow it to be read as a NAL unit bitstream.
|
| PriorityHandlerThread |
A
HandlerThread with a specified process priority. |
| PriorityTaskManager |
Allows tasks with associated priorities to control how they proceed relative to one another.
|
| ReusableBufferedOutputStream |
This is a subclass of
BufferedOutputStream with a ReusableBufferedOutputStream.reset(OutputStream) method
that allows an instance to be re-used with another underlying output stream. |
| SlidingPercentile |
Calculate any percentile over a sliding window of weighted values.
|
| StandaloneMediaClock |
A standalone
MediaClock . |
| SystemClock |
The standard implementation of
Clock . |
| TimestampAdjuster |
Offsets timestamps according to an initial sample timestamp offset.
|
| TraceUtil |
Calls through to
Trace methods on supported API levels. |
| UriUtil |
Utility methods for manipulating URIs.
|
| Util |
Miscellaneous utility methods.
|
| XmlPullParserUtil |
XmlPullParser utility methods. |
| Exception | Description |
|---|---|
| PriorityTaskManager.PriorityTooLowException |
Thrown when task attempts to proceed when another registered task has a higher priority.
|


Working with CSS
If you're more comfortable working in CSS, you can modify the main.css
stylesheet in the dist
> css
directory.
Adjusting Settings
- Page Width
- The
.container
class sets the width for page content. Adjust themax-width
property to set the maximum width of the page.
- Font Stack
- The
body
element sets the typeface for the entire set. By default, the font stack is Helvetica Neue, Arial, and sans-serif. The two exceptions arepre
andcode
elements, which use a monospace stack. Adjust as desired.
- Typographic Scale
- Kraken uses a fluid typographic scale. You can scale the size of all site elements proportionately by adjusting the
font-size
property on the body element, which is set to 100% by default (and 125% on screens above 80em).
- Colors (used throughout)
- Primary:
#0088cc
Black:#272727
White:#ffffff
Dark Gray:#808080
Light Gray:#e5e5e5
- Breakpoints (used throughout)
- Extra Small: 20em
Small: 30em
Medium: 40em
Large: 60em
Extra Large: 80em


Progress
| concept and wireframe |
design |
backend |
caching |
|
|
|
|
|
|
10% wireframe; 20% design; 40% backend and database; 50% caching; 70% javascript; 80% content;
90% cookies, security and analytics;
95% mobile friendly; 100% domain and lunch
back to frontpage
Goals
Develop a meaningful blog like zen habit
Remember, keep it clean and simple and it will be easy
To do
- Domain name and domain registration
- First blog post
- Html/css design
- social network references
- cv
- Dynamic content (javascript)
- Setup google analytics
- Managing cookies
- Security:
- spam comments, bot comments
- backup development data on github
- Caching: - blogposts, guestbookcomments
- Build the portfolio
- Language issue
- Make it mobile friendly
Deadlines
Going Online until 2015/12/31
- Mobile friendly and the rest - 2015/12/13
- Cookies and analytics - 2015/11/30
- Add with content (this also includes the first blog post as a draft!) until 2015/11/18
- Convert static design and add first javascript until 2015/11/10
- Caching and security - 2015/10/31
- Backend development and databse until 2015/10/21
- Think through wireframe again until 2015/09/27
- Static design for front page, blog, slag, contact and guestbook until 2015/09/26
- Create shell until 2015/09/18 (2015/09/21)
- Make development page with project status visualized, goals, to do list, deadlines until 2015/09/15
Lern or read
- Current web standards for
- Testing javascript examples for web sites
Sources of web site development process


I recently encountered troubling issues with MMM for MySQL deployments, leading me to the decision to cease using it on production.
At the very same day I started writing about it, Baron published What's wrong with MMM?. I wish to present the problems I encountered and the reasons I find MMM is flawed. In a period of two weeks, two different deployments presented me with 4 crashes, in 3 different scenarios.
In all the following scenarios, there is an Active/Passive Master-Master deployment, with one VIP (virtual IP) set for writer role, one VIP set for reader role.
Problem #1: unjustified failover, broken replication
Unjustified failover must be the common scenario. It's also a scenario I can live with. A few seconds of downtime are OK with me once in a couple of months.
But on two different installations, a few days apart, I had two seemingly unjustified failovers followed by a troubling issue: replication got broken.
How broken? The previously active master, now turned inactive, suddenly changed master position to a roughly 10 days old position. I don't keep master logs for 10 days, so this led to an immediate replication fail.
Now, I cannot directly point my finger at MMM, but:
- There was no power failure
- MySQL daemon did not go down
- Replication was just fine both ways up to the failover moment
- There was no human intervention on this (myself and once more person had access at that time).
I know the above since I've got it all monitored. So I can't blame it on “replication not synching master.info file to disk when power went down”. I confess, this is very suspicious; but, twice, on two different deployments...
So much for suspicions. Now for the smoking guns.
Problem #2: hanging master, no failover
The active master went down. Either hardware or software problem caused it to freeze. It was not executing its chores; it became inaccessible by TCP/IP.
But not just inaccessible: freezing inaccessible. If you were to attempt an SSH connection, the connection would just hang; not refused. The SSH client would not terminate in any reasonable time.
Ahem, time to do failover?
Apparently not. Phones start ringing. Emails sent. Time for manual intervention. But, what does the MMM monitor have to say? Nothing. It's frozen. Now, I didn't read the source code; I'm not even competent with PERL; but is seems to me like the monitor daemon works single threaded: it attempts to connect all hosts on the same thread. But, connecting to active master makes for hanging connection, so the entire monitor goes down. Impossible to stop it gracefully, I had to kill it. I had the choice of reconfiguring it to ignore active master, but decided to try starting it up again. I had to do it twice before it started acting sanely again, and realized it was time for failover.
Why is this bad? Assuming my analysis is correct, this is a major design flaw. You must never do a single threaded monitoring on a multiple-machine deployment.
Problem #3: no servers
System is down! No access to the database. What does MMM monitor have to say?
Both machines are HARD_OFFLINE.
Ahem. Both machines are up and running; they are both replicating each other. They are both accessible. MySQL is accessible.
But neither machine has any VIP associated with.
Does it matter whether both agents fail to realize their associated MySQL servers were actually up and running, or whether the monitor fail to receive that information? It does not. MMM should not have removed all VIPs. OK, suppose it believes the two machines are down. So what? Just throw all VIPs on one of the machines. If it's inaccessible, then what's wrong with that? (assuming the previous problem never existed, that is).
You should always have some machine associated with the VIPs.
Temper down
None of the above is meant as offense to the creators of MMM, whom I greatly respect. This isn't an easy problem to solve, and it should be obvious there's no 100% guaranteed solution. But, for myself, I will not be using MMM as it stands right now anymore.
comments powered by Disqus


| Class | Description |
|---|---|
| BaseActivity |
Abstract base class for common features across multiple activities throughout the entire
application life-cycle.
|
| BitmapUtils |
This is a Bitmap utility class which is used to load a Bitmap File into an ImageView with
com.squareup.picasso.
|
| ColorPickerPreference |
This is a custom Preference to pick the font color for either question or answer.
|
| ContinueBoxPreference |
This is a custom Preference for the
QNAPreferencesFragment ,
to allow the user to start the quiz from the saved progress remaining
from the previous quiz; composed of:
|
| CustomDialogFragment |
An abstract CustomDialog class which, rather than extending the Dialog base class directly, uses the
AlertDialog sub-class with a custom layout.
|
| CustomExpandableListAdapter |
A custom adapter that links an ExpandableListView with the underlying data in order
to provide access to the data of the children (categorized by groups),
and also instantiate Views for the children and groups.
|
| CustomFontCache |
Loads a custom font from the assets folder.
|
| CustomFontHelper |
Sets a custom font based on the cached font from
CustomFontCache . |
| CustomFontTextView |
This class is the extended version of AppCompatTextView with only one difference:
a custom text font.
|
| CustomValueFormatter |
Formats data set with BarData in
QNASummaryBarChartBuilder . |
| CustomXAxisValueFormatter |
X-axis IAxisValueFormatter for the
QNASummaryBarChartBuilder class. |
| CustomYAxisValueFormatter |
Y-axis IAxisValueFormatter for the
QNASummaryBarChartBuilder class. |
| EnviromentalConstants |
Defines the environmental constants for the entire app.
|
| ExpandableListHandler |
Sets and gets the ExpandableListView group and child data for the answer and question quiz types,
as well as adjusts the ExpandableListView height.
|
| ExpandableListViewPreference |
Shows a Preference in the PreferenceScreen, in the
QNAPreferencesFragment , composed of:
two ExpandableListViews for question and answer type selection
an ImageView swap icon in-between the two ExpandableListViews to interchange their values
isDuplicate TextView notification to show that duplicate QNA type selection is not possible,
which is made visible when ExpandableListViewPreference.isChildSelectorValid(int, int) returns false.
|
| LanguageSelectorPreference |
This is a custom Preference to select the UI language.
|
| PreferenceHelper |
Helper class which contains methods common to all Preferences.
|
| SeekBarPreference |
This is a custom Preference for a SeekBar, used to:
In order to avoid extending two separate classes from this class for each of i-ii, XML attributes are used to handle the differences. |
| SharedPreferencesKeys |
This class contains common static public constants that are compiled into bytecode (unlike the
Android Resources) for easy access within the global scope.
|
| SingleFragmentActivity |
Generic abstract class to re-use fragments.
|
| ToastHelper |
Helper class to set up and show a custom Toast.
|
| TogglePreference |
This is a custom Switch Preference, used in the
AppPreferencesFragment class. |
| ToolBarActivity |
This is a common class for a Toolbar which is extended for all activities that display a Toolbar
with a NavigationView Drawer.
|


Getting Started
ImpactView Philadelphia uses an intuitive interface, combining maps, data visualization, and search functionality.
Search for Organizations
Explore the map by searching for an organization, zip code, or address within the city of Philadelphia. If you select a zip code or address, the map will show that location with a list of organizations within that area. If you select an organization from the search list, you can then use the analysis tools to visualize important data or you can click on any organization on the map and use the ‘Analyze’ link.
Analyzing Organizations and Communities
Once you have selected an organization, the map will identify that organization on the map with a data visualization below comprising important measures of households and individuals using a default radius of 0.5 miles surrounding the organization.
Use the tool to change the radius or draw a custom area for which the data is visualized.
Use the tool to filter by the type of nonprofit organization.
Use the tool to view important demographics on the map.
Use the tool to maximize the view of the map for improved interaction.


Texas Hottie Hope Beel Rocks Cascading Curls & Revealing Floral Bikini On Instagram
November 18, 2019
Texas Hottie Hope Beel Rocks Cascading Curls & Revealing Floral Bikini On Instagram
Hope Beel is starting off the week in a black floral bikini. The Texas model looked like a total smokeshow in her latest Instagram photo, which she shared with her fans on Monday morning.
In the sexy snapshot, Hope is seen rocking the bikini with pink and white flowers on it. The skimpy top flaunted her ample cleavage and toned arms, while the model tugged at the high-cut bottoms and flashed her flat tummy, rock-hard abs, curvy hips, and lean legs for the camera.
Hope wore her long, brown hair halfway up and styled in stunning curls that cascaded over her shoulders and fell down her back. She also opted for a full face of makeup that included defined eyebrows, long lashes, and a bronzed glow. She added pink blush to bring out her cheekbones, a shimmering highlighter on her face, and nude lips to complete the glam look.
In the background of the photo, a faint ocean view can be seen as Hope revealed in the caption of the snap that she was waiting for the sun to come out while vacationing in Turks and Caicos.
Of course, Hope’s 1.2 million fans went wild for the bikini shot, clicking the like button over 7,000 times and leaving more than 100 comments all within the first hour after it was posted to the network.
“That look you give is custom made to melt a man where he stands. And a body that can stop hearts.  (Guess that means I have a death wish tho…) Nothing but love for you,” one of Hope’s Instagram followers wrote in the comments section of the post.
“One of the prettiest women I have ever seen simply beautiful,” another fan gushed over the model.
“You look super sexy. You’re bikini is fantastic!!” a third comment read.
Loading...
“Perfect shape looking gorgeous beautiful princess,” a fourth social media user said.
As previously reported by The Inquisitr, Hope rocked her followers just one day prior to her floral bikini snap when she posed in front of the ocean wearing nothing by a white string two-piece.
In the photo, the model gushed over the gorgeous, crystal clear water on the island, and gave fans a peek at all of her sculpted curves.
That post also proved to be a popular update for Hope Beel, as it has gained over 24,000 likes and more than 250 comments in the first 24 hours after it was shared.


STEP 1: Fill In The Text Submission Form
Your Name*
Email Address*
Text*(NB: you can skip this step if you already loaded the text before and go directly to STEP 3)
STEP 3: Enter A Date* (format: YYYYMMDD) If You Loaded The Texts Before
STEP 2: Generate The Databases For The Text You've Just Loaded
Back
STEP 4: Generate The Databases For The Data Entry Date You've Just Entered And Start The App


Four Amazing places you should visit in Japan
Japan is an amazing country and it is the combination of both the world on one side you will see an advanced, developed country with amazing cities and lots of technical development and on the other hand, you will experience wonderful natural sites and sceneries. So let's start our Journey to see 7 most amazing places you must visit while traveling to Japan.
Tokyo
As a Capital city, Tokyo offers you a variety of things to visit and have a sense of being in Japan, it gives you a picture of modern Japan, and also you could find plenty of traditional temples. It is basically an ultramodern-traditional city. Where you can experience overcrowded streets, trains, hectic lifestyles, Skyscrapers, and on the other hand chilled places like Traditional Temples made up of wooden roofs, gates, and so on..
Osaka
Osaka is known as the kitchen of Japan. It's a modern Japanese city and the center of food and drinks and also for its nightlife. You can enjoy eating traditional Japanese food and try some drinks and also experience some amazing markets.
Gujo Hachiman: The water city of Japan.
The perfect place to experience natural sites in Japan. This city is famous for its natural water system. Water is an essential part of the people of this city and it also plays a significant role in attracting tourists. The river water to canals the water flows in the entire city. You can see people enjoying this nature's gift as swimming, fishing, sitting relaxed at along the water canals and you will see fishes everywhere even in the drainage. Other than that the city uses this water for Drink, Cook, clean and passage as well.
Kyoto
The Holy City, A perfect city to experience Japanese traditional temples, natural beauty. It's one of the peaceful places on earth that attracts thousands of visitors every month. A beautiful area called Gion, located in Kyoto is famous for stone payments and traditional Japanese houses and you will see lots of people in traditional Japanese outfits which is so amazing to see. Kiyomizu temple is the most popular temple of Kyoto and it's also the world heritage site and in autumn this place looks so amazing.


--- author: admin categories: app date: '2011-06-21 01:27:30' permalink: /2011/06/21/building-the-diary-com-ios-app-using-pg-sencha-touch/ slug: building-the-diary-com-ios-app-using-pg-sencha-touch status: publish title: Building the Diary.com iOS App using PG & Sencha Touch type: post format: html ---
We have recently got our app, Diary Mobile, approved by Apple. It was under review for 6 days and it took one more day until we were in the App Store. We actually used PhoneGap to replace a previously built native app developed by a third party and decided to bring development in house for agility.
We wanted to share and give confidence that PhoneGap apps are getting approved by Apple. We were pretty anxious. Some points I am sure you will all ask is what we used and how it was. The app was built with PhoneGap 0.9.2 and Sencha Touch 1.0.1a, it uses Flurry for analytics via a PhoneGap plugin. We've upgraded both PhoneGap and Sencha Touch to the latest and greatest for a future release, currently on a development branch.
Some points of interest...
We built a Flurry API PhoneGap plugin for iOS (to be released open source in the near future). It goes to show that PhoneGap makes it very easy for us to extend the code if something is missing. Especially if the Objective-C only native option is open source. Even if you have no knowledge of Objective-C, there are plenty of examples of PhoneGap plugins over at PhoneGap's Github page to get you started.
We also built another PhoneGap plugin to use the Local Notifications on iOS (also to be open sourced soon).
We are looking at using the core codebase to create an Android version for the next release, then Blackberry.
Performance was the biggest challenge, Sencha Touch is quite a beast and we've had to patch quite a lot of it to make it more performant and apply bug fixes.
The app uses a lot of Ajax calls and stores everything in HTML5 Local Storage.
We built an entirely REST API for which the app communicates with to make it as efficient and fast as possible.
When we were first building this App, we were always looking for affirmation of what to build it with (rejection worries,etc). So we hope this post helps relieving some of those worries and prove a combination of a Javascript Framework with PhoneGap works well.
We have to say it wasn't easy, performance was tricky at times. Here are some tips...
Initialize variables outside of FOR loops.
For Sencha Touch, actually look at the source code, it's a lot more readable than it seems.
Cache using Global variables.
Keep Ajax calls efficient and minimize starting of asynchronous calls all at once by making them to be action based. Similar to techniques when caching a normal website.
It's javascript, you will need to get your hands dirty using hacks with setTimeout() once in a while.
The App is free but needs you to sign up as it compliments our web application at Diary.com. You can download the app at http://itunes.apple.com/gb/app/diary-mobile/id357481953?mt=8
We hope to share more of our journey and battles as our app grows. Good luck with your PhoneGap development!


| DOSE: T+ 0:00 |
1.75 g |
oral |
Mushrooms |
(cookie / food) |
| T+ 3:00 |
1 bowl |
smoked |
Cannabis |
(plant material) |
Well, my first experience with mushrooms was a little less than a week ago, and I'm still trying to wrap my head around it. I'm a freshman in College, and my friend and I had been talking about trying mushrooms for quite some time now, and, he finally found some. So, we came back to his apartment around 12:30 at night and ingested some of the mushrooms in the form of chocolates. We sat around until about 1, and we weren't feeling all that much, so, we split what we still had between three people - my friend and I and one of my friend's roomates.
The first thing I began to notice when it kicked it was that all of us were getting extremly giddy - I couldn't stop laughing. My body also seemed to feel like it was being tickled from the inside. We sat around for a while, feeling pretty good, and the roomate decided to put in the movie 'Altered States' - which is one hell of a trippy movie. After we watched that for a while, we turned off the TV and just enjoyed the experience.
Things seemed to shift around the room on their own. I stepped out onto their porch, and it left like I was 'bending' everything with my mind. After that, I came back inside and sat down. I became very philosophical - I remember thinking about the relationship of order to chaos, and how seemingly miniscule, insignificant choices in your life actually changed the entire course of it. I thought about the concept of Fate VS. the concept of Free will.
I felt the intense desire to try to explain what I was thinking about/feeling to someone else, and, I tried on many occassions to explain the concepts to my 'trippin' buddies' without success. Words and language seemed so inadequate at the time (and they still do). Next time, I'm bringing a notepad and pen. I also felt as if I could step back and see the world/society as it truly was - without the automatic bias that sets in from being human.
I also thought that I could see chunks of my own future - I remember the intense joy I felt when I realized that one day, I will be someone's father. Life seemed to be amazingly simple and beautiful at the same time. I don't think I've ever been so overjoyed to be alive. Then, my friend's other roomate came home at about 2-3, and we smoked a bowl (my friend abstained).
At about this point, my friend started to have a bad trip. He went alone into his room (bad idea) and turned the lights off and tried to sleep (worse idea). I tried to calm him down a bit, but it didn't seem to work. I talked to him later and he said that he thought that the trip should have been 'over' by that point (about 4-4:30), and he had it set in his mind that he was going to be like this forever, no matter what anyone else said. He also said he was hallucinating quite a bit. He was puking into the toilet at about 5 A.M. when I was done tripping and started walking home. He said he's never touching shrooms again, while I on the other hand, can't wait to go back on another 'trip'.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Sample Projects
| BC7 Compression |
| BC6H Compression |
Recent Projects
New 3.0 Features
- Mesh Optimization
- Supports gltf and obj file optimization for improved GPU performance
- Mesh Compression
- Supports obj file compression
- Image View
- View original, processed and image differences in the same view panel


|
GPGPU-Sim
|
#include <XML_Parse.h>
Definition at line 203 of file XML_Parse.h.
| double system_core::ALU_cdb_duty_cycle |
Definition at line 331 of file XML_Parse.h.
| double system_core::ALU_duty_cycle |
Definition at line 328 of file XML_Parse.h.
| int system_core::ALU_per_core |
Definition at line 227 of file XML_Parse.h.
| double system_core::archi_float_regfile_reads |
Definition at line 287 of file XML_Parse.h.
| double system_core::archi_float_regfile_writes |
Definition at line 293 of file XML_Parse.h.
| double system_core::archi_int_regfile_reads |
Definition at line 286 of file XML_Parse.h.
| double system_core::archi_int_regfile_writes |
Definition at line 292 of file XML_Parse.h.
| int system_core::archi_Regs_FRF_size |
Definition at line 237 of file XML_Parse.h.
| int system_core::archi_Regs_IRF_size |
Definition at line 236 of file XML_Parse.h.
| double system_core::BR_duty_cycle |
Definition at line 324 of file XML_Parse.h.
| double system_core::branch_instructions |
Definition at line 258 of file XML_Parse.h.
| double system_core::branch_mispredictions |
Definition at line 259 of file XML_Parse.h.
| BTB_systemcore system_core::BTB |
Definition at line 353 of file XML_Parse.h.
| double system_core::busy_cycles |
Definition at line 267 of file XML_Parse.h.
| dcache_systemcore system_core::ccache |
Definition at line 350 of file XML_Parse.h.
| double system_core::cdb_alu_accesses |
Definition at line 308 of file XML_Parse.h.
| double system_core::cdb_fpu_accesses |
Definition at line 310 of file XML_Parse.h.
| double system_core::cdb_mul_accesses |
Definition at line 309 of file XML_Parse.h.
| int system_core::clock_rate |
Definition at line 205 of file XML_Parse.h.
| int system_core::collector_units |
Definition at line 340 of file XML_Parse.h.
| int system_core::commit_width |
Definition at line 222 of file XML_Parse.h.
| double system_core::committed_fp_instructions |
Definition at line 262 of file XML_Parse.h.
| double system_core::committed_instructions |
Definition at line 260 of file XML_Parse.h.
| double system_core::committed_int_instructions |
Definition at line 261 of file XML_Parse.h.
| double system_core::context_switches |
Definition at line 302 of file XML_Parse.h.
| double system_core::core_clock_ratio |
Definition at line 341 of file XML_Parse.h.
| dcache_systemcore system_core::dcache |
Definition at line 349 of file XML_Parse.h.
| char system_core::Dcache_dual_pump[20] |
Definition at line 246 of file XML_Parse.h.
| int system_core::decode_width |
Definition at line 219 of file XML_Parse.h.
| int system_core::decoded_stream_buffer_size |
Definition at line 231 of file XML_Parse.h.
| char system_core::divider_multiplier[20] |
Definition at line 226 of file XML_Parse.h.
| dtlb_systemcore system_core::dtlb |
Definition at line 348 of file XML_Parse.h.
| int system_core::fetch_width |
Definition at line 217 of file XML_Parse.h.
| double system_core::float_regfile_reads |
Definition at line 295 of file XML_Parse.h.
| double system_core::float_regfile_writes |
Definition at line 297 of file XML_Parse.h.
| double system_core::fp_inst_window_reads |
Definition at line 282 of file XML_Parse.h.
| double system_core::fp_inst_window_selections |
Definition at line 285 of file XML_Parse.h.
| double system_core::fp_inst_window_wakeup_accesses |
Definition at line 284 of file XML_Parse.h.
| double system_core::fp_inst_window_writes |
Definition at line 283 of file XML_Parse.h.
| int system_core::fp_instruction_window_size |
Definition at line 234 of file XML_Parse.h.
| double system_core::fp_instructions |
Definition at line 257 of file XML_Parse.h.
| int system_core::fp_issue_width |
Definition at line 248 of file XML_Parse.h.
| double system_core::fp_rename_accesses |
Definition at line 273 of file XML_Parse.h.
| double system_core::fp_rename_reads |
Definition at line 276 of file XML_Parse.h.
| double system_core::fp_rename_writes |
Definition at line 277 of file XML_Parse.h.
| char system_core::FPU[20] |
Definition at line 225 of file XML_Parse.h.
| double system_core::fpu_accesses |
Definition at line 304 of file XML_Parse.h.
| double system_core::FPU_cdb_duty_cycle |
Definition at line 333 of file XML_Parse.h.
| double system_core::FPU_duty_cycle |
Definition at line 330 of file XML_Parse.h.
| double system_core::FPU_per_core |
Definition at line 228 of file XML_Parse.h.
| double system_core::function_calls |
Definition at line 301 of file XML_Parse.h.
| bool system_core::gpgpu_clock_gated_lanes |
Definition at line 252 of file XML_Parse.h.
| double system_core::ialu_accesses |
Definition at line 303 of file XML_Parse.h.
| icache_systemcore system_core::icache |
Definition at line 347 of file XML_Parse.h.
| double system_core::idle_cycles |
Definition at line 266 of file XML_Parse.h.
| double system_core::IFU_duty_cycle |
Definition at line 323 of file XML_Parse.h.
| double system_core::inst_window_reads |
Definition at line 278 of file XML_Parse.h.
| double system_core::inst_window_selections |
Definition at line 281 of file XML_Parse.h.
| double system_core::inst_window_wakeup_accesses |
Definition at line 280 of file XML_Parse.h.
| double system_core::inst_window_writes |
Definition at line 279 of file XML_Parse.h.
| double system_core::instruction_buffer_reads |
Definition at line 268 of file XML_Parse.h.
| int system_core::instruction_buffer_size |
Definition at line 230 of file XML_Parse.h.
| double system_core::instruction_buffer_write |
Definition at line 269 of file XML_Parse.h.
| int system_core::instruction_length |
Definition at line 213 of file XML_Parse.h.
| int system_core::instruction_window_scheme |
Definition at line 232 of file XML_Parse.h.
| int system_core::instruction_window_size |
Definition at line 233 of file XML_Parse.h.
| double system_core::int_instructions |
Definition at line 256 of file XML_Parse.h.
| double system_core::int_regfile_reads |
Definition at line 294 of file XML_Parse.h.
| double system_core::int_regfile_writes |
Definition at line 296 of file XML_Parse.h.
| int system_core::internal_datapath_width |
Definition at line 215 of file XML_Parse.h.
| int system_core::issue_width |
Definition at line 220 of file XML_Parse.h.
| itlb_systemcore system_core::itlb |
Definition at line 346 of file XML_Parse.h.
| double system_core::load_buffer_cams |
Definition at line 313 of file XML_Parse.h.
| double system_core::load_buffer_reads |
Definition at line 311 of file XML_Parse.h.
| int system_core::load_buffer_size |
Definition at line 244 of file XML_Parse.h.
| double system_core::load_buffer_writes |
Definition at line 312 of file XML_Parse.h.
| double system_core::load_instructions |
Definition at line 263 of file XML_Parse.h.
| double system_core::LSU_duty_cycle |
Definition at line 325 of file XML_Parse.h.
| char system_core::LSU_order[20] |
Definition at line 242 of file XML_Parse.h.
| int system_core::machine_bits |
Definition at line 208 of file XML_Parse.h.
| int system_core::machine_type |
Definition at line 214 of file XML_Parse.h.
| double system_core::main_memory_access |
Definition at line 318 of file XML_Parse.h.
| double system_core::main_memory_read |
Definition at line 319 of file XML_Parse.h.
| double system_core::main_memory_write |
Definition at line 320 of file XML_Parse.h.
| double system_core::MemManU_D_duty_cycle |
Definition at line 327 of file XML_Parse.h.
| double system_core::MemManU_I_duty_cycle |
Definition at line 326 of file XML_Parse.h.
| int system_core::memory_ports |
Definition at line 245 of file XML_Parse.h.
| int system_core::micro_opcode_width |
Definition at line 212 of file XML_Parse.h.
| double system_core::mul_accesses |
Definition at line 305 of file XML_Parse.h.
| double system_core::MUL_cdb_duty_cycle |
Definition at line 332 of file XML_Parse.h.
| double system_core::MUL_duty_cycle |
Definition at line 329 of file XML_Parse.h.
| int system_core::MUL_per_core |
Definition at line 229 of file XML_Parse.h.
| double system_core::non_rf_operands |
Definition at line 298 of file XML_Parse.h.
| double system_core::num_idle_cores |
Definition at line 335 of file XML_Parse.h.
| int system_core::number_hardware_threads |
Definition at line 216 of file XML_Parse.h.
| int system_core::number_instruction_fetch_ports |
Definition at line 218 of file XML_Parse.h.
| int system_core::number_of_BPT |
Definition at line 251 of file XML_Parse.h.
| int system_core::number_of_BTB |
Definition at line 250 of file XML_Parse.h.
| int system_core::opcode_width |
Definition at line 211 of file XML_Parse.h.
| bool system_core::opt_local |
Definition at line 206 of file XML_Parse.h.
| int system_core::peak_issue_width |
Definition at line 221 of file XML_Parse.h.
| double system_core::phy_float_regfile_reads |
Definition at line 289 of file XML_Parse.h.
| double system_core::phy_float_regfile_writes |
Definition at line 291 of file XML_Parse.h.
| double system_core::phy_int_regfile_reads |
Definition at line 288 of file XML_Parse.h.
| double system_core::phy_int_regfile_writes |
Definition at line 290 of file XML_Parse.h.
| int system_core::phy_Regs_FRF_size |
Definition at line 239 of file XML_Parse.h.
| int system_core::phy_Regs_IRF_size |
Definition at line 238 of file XML_Parse.h.
| int system_core::physical_address_width |
Definition at line 210 of file XML_Parse.h.
| int system_core::pipeline_depth[20] |
Definition at line 224 of file XML_Parse.h.
| double system_core::pipeline_duty_cycle |
Definition at line 321 of file XML_Parse.h.
| int system_core::pipelines_per_core[20] |
Definition at line 223 of file XML_Parse.h.
| int system_core::prediction_width |
Definition at line 249 of file XML_Parse.h.
| predictor_systemcore system_core::predictor |
Definition at line 345 of file XML_Parse.h.
| int system_core::RAS_size |
Definition at line 247 of file XML_Parse.h.
| int system_core::register_windows_size |
Definition at line 241 of file XML_Parse.h.
| double system_core::rename_accesses |
Definition at line 272 of file XML_Parse.h.
| double system_core::rename_reads |
Definition at line 274 of file XML_Parse.h.
| int system_core::rename_scheme |
Definition at line 240 of file XML_Parse.h.
| double system_core::rename_writes |
Definition at line 275 of file XML_Parse.h.
| int system_core::rf_banks |
Definition at line 338 of file XML_Parse.h.
| double system_core::ROB_reads |
Definition at line 270 of file XML_Parse.h.
| int system_core::ROB_size |
Definition at line 235 of file XML_Parse.h.
| double system_core::ROB_writes |
Definition at line 271 of file XML_Parse.h.
| double system_core::sfu_average_active_lanes |
Definition at line 307 of file XML_Parse.h.
| dcache_systemcore system_core::sharedmemory |
Definition at line 352 of file XML_Parse.h.
| int system_core::simd_width |
Definition at line 339 of file XML_Parse.h.
| double system_core::sp_average_active_lanes |
Definition at line 306 of file XML_Parse.h.
| double system_core::store_buffer_cams |
Definition at line 316 of file XML_Parse.h.
| double system_core::store_buffer_forwards |
Definition at line 317 of file XML_Parse.h.
| double system_core::store_buffer_reads |
Definition at line 314 of file XML_Parse.h.
| int system_core::store_buffer_size |
Definition at line 243 of file XML_Parse.h.
| double system_core::store_buffer_writes |
Definition at line 315 of file XML_Parse.h.
| double system_core::store_instructions |
Definition at line 264 of file XML_Parse.h.
| dcache_systemcore system_core::tcache |
Definition at line 351 of file XML_Parse.h.
| double system_core::total_cycles |
Definition at line 265 of file XML_Parse.h.
| double system_core::total_instructions |
Definition at line 255 of file XML_Parse.h.
| int system_core::virtual_address_width |
Definition at line 209 of file XML_Parse.h.
| int system_core::warp_size |
Definition at line 342 of file XML_Parse.h.
| double system_core::windowed_reg_accesses |
Definition at line 299 of file XML_Parse.h.
| double system_core::windowed_reg_transports |
Definition at line 300 of file XML_Parse.h.
| bool system_core::x86 |
Definition at line 207 of file XML_Parse.h.