My Pet
I have a pet cat. I got this cat as a kitten from a friend.
Facts about cats
- The first year of a cat's life is equal to the first 15 years of a human lif
- Cats can rotate their ears 180 degrees
- The hearing of the average cat is at least five times keener than that of a human adult
Things that my cat likes
- Rubbing against people
- Flashing it's belly
- Napping
- Nibbling
Websites with information on cats


---
layout: default
title: Home
---
Hi! My name is {{ site.author }}.
I am a special little snowflake.
Learn more
I enjoy making stuff for people.
Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
View my portfolio
I also like to write things.
Donec mollis. Quisque convallis libero in sapien pharetra tincidunt.
Read my blog
Yes, I'm social.
Donec mollis. Quisque convallis libero in sapien pharetra tincidunt.
Get in touch


Dominic Aguirre
Aspiring Software Engineer
About Me
My name is Dominic Aguirre, and I am a Computer Science student studying at Southern New Hampshire university. I was born and raised in Massachusetts but lived in Rhode Island for a few years before moving to New Hampshire where I have been since. I have started learning several languages such as C++, C#, SQL, HTML, CSS, Bootstrap, Angular and JavaScript. I am always looking for new opportunities for learning and will be undergoing many projects to help further my understanding of Computer Science. I will be using this website to host all my projects for anyone to see and to learn about web development. I will also host a gallery of my paintings if that is what you have come to see.
Info about myself
Education
I'm currently studying at Souther New Hampshire University
Major
Computer Science
Hobbies
- Painting: I enjoy painting often have have ammased a small collection of personal paintings.
- Computer Science: has quickly become a hobbie of mine the challeneges are like fun puzzles to me and overcoming them gives a great feeling of self accomplishment.
- Spending time with friends: Being around friends is what gets me going, nothing like having a good laugh with good friends.


Dear {{ username }},
We have generated a new password for you and now you can sign in using your current Login and this password. If you did not request new password - immediately contact us at
{{ support }}
Your new password:
{{ password }}


AWS::EC2::TransitGatewayRoute
Creates a static route for a transit gateway route table. For more information, see Amazon VPC Transit Gateways.
Topics
Syntax
To declare this entity in your AWS CloudFormation template, use the following syntax:
JSON
{ "Type" : "AWS::EC2::TransitGatewayRoute", "Properties" : { "Blackhole" :
Boolean
, "DestinationCidrBlock" :String
, "TransitGatewayAttachmentId" :String
, "TransitGatewayRouteTableId" :String
} }
YAML
Type: "AWS::EC2::TransitGatewayRoute" Properties: Blackhole:
Boolean
DestinationCidrBlock:String
TransitGatewayAttachmentId:String
TransitGatewayRouteTableId:String
Properties
Blackhole
-
Indicates whether to drop traffic if the target isn't available.
Required: No
Type: Boolean
Update requires: Replacement
DestinationCidrBlock
-
The CIDR range used for destination matches. Routing decisions are based on the most specific match.
Required: No
Type: String
Update requires: Replacement
TransitGatewayAttachmentId
-
The ID of the attachment.
Required: No
Type: String
Update requires: Replacement
TransitGatewayRouteTableId
-
The ID of the transit gateway route table.
Required: Yes
Type: String
Update requires: Replacement
Return Values
Ref
When you pass the logical ID of an AWS::EC2::TransitGatewayRoute
resource to the intrinsic
Ref
function, the function returns the ID of the route table and the destination CIDR,
separated
by an underscore, such as tgw-rtb-0ea209e5dcc99f3a3_<IP_ADDRESS>/0
.
For more information about using the Ref
function, see
Ref.
See Also
-
CreateTransitGatewayRoute in the Amazon EC2 API Reference


Configuration
Guide to all available configuration settings.
Introduction
Project settings are always configured by using a YAML configuration file in the
project directory named mkdocs.yml
.
As a minimum, this configuration file must contain the site_name
and
site_url
settings. All other settings are optional.
Project information
site_name
This is a required setting, and should be a string that is used as the main title for the project documentation. For example:
site_name: Marshmallow Generator
When rendering the theme this setting will be passed as the site_name
context
variable.
site_url
Set the canonical URL of the site. This will add a link
tag with the
canonical
URL to the head
section of each HTML page. If the ‘root’ of the
MkDocs site will be within a subdirectory of a domain, be sure to include that
subdirectory in the setting (https://example.com/foo/
).
This setting is also used for mkdocs serve
: the server will be mounted onto a
path taken from the path component of the URL, e.g. some/page.md
will be
served from http://<IP_ADDRESS>:8000/foo/some/page/
to mimick the expected remote
layout.
default: null
repo_url
When set, provides a link to your repository (GitHub, Bitbucket, GitLab, …) on each page.
repo_url: https://github.com/example/repository/
default: null
repo_name
When set, provides the name for the link to your repository on each page.
default: 'GitHub'
, 'Bitbucket'
or 'GitLab'
if the repo_url
matches
those domains, otherwise the hostname from the repo_url
.
edit_uri
The path from the base repo_url
to the docs directory when directly viewing a
page, accounting for specifics of the repository host (e.g. GitHub, Bitbucket,
etc), the branch, and the docs directory itself. MkDocs concatenates repo_url
and edit_uri
, and appends the input path of the page.
When set, and if your theme supports it, provides a link directly to the page in
your source repository. This makes it easier to find and edit the source for the
page. If repo_url
is not set, this option is ignored. On some themes, setting
this option may cause an edit link to be used in place of a repository link.
Other themes may show both links.
The edit_uri
supports query (‘?’) and fragment (‘#’) characters. For
repository hosts that use a query or a fragment to access the files, the
edit_uri
might be set as follows. (Note the ?
and #
in the URI…)
# Query string example
edit_uri: '?query=root/path/docs/'
# Hash fragment example
edit_uri: '#root/path/docs/'
For other repository hosts, simply specify the relative path to the docs directory.
# Query string example
edit_uri: root/path/docs/
!!! note
On a few known hosts (specifically GitHub, Bitbucket and GitLab), the
edit_uri
is derived from the ‘repo_url’ and does not need to be set
manually. Simply defining a repo_url
will automatically populate the
edit_uri
configs setting.
For example, for a GitHub- or GitLab-hosted repository, the `edit_uri`
would be automatically set as `edit/master/docs/` (Note the `edit` path
and `master` branch).
For a Bitbucket-hosted repository, the equivalent `edit_uri` would be
automatically set as `src/default/docs/` (note the `src` path and `default`
branch).
To use a different URI than the default (for example a different branch),
simply set the `edit_uri` to your desired string. If you do not want any
"edit URL link" displayed on your pages, then set `edit_uri` to an empty
string to disable the automatic setting.
!!! warning
On GitHub and GitLab, the default “edit” path (edit/master/docs/
) opens
the page in the online editor. This functionality requires that the user
have and be logged in to a GitHub/GitLab account. Otherwise, the user will
be redirected to a login/signup page. Alternatively, use the “blob” path
(blob/master/docs/
) to open a read-only view, which supports anonymous
access.
default: edit/master/docs/
for GitHub and GitLab repos or
src/default/docs/
for a Bitbucket repo, if repo_url
matches those domains,
otherwise null
site_description
Set the site description. This will add a meta tag to the generated HTML header.
default: null
site_author
Set the name of the author. This will add a meta tag to the generated HTML header.
default: null
copyright
Set the copyright information to be included in the documentation by the theme.
default: null
remote_branch
Set the remote branch to commit to when using gh-deploy
to deploy to GitHub
Pages. This option can be overridden by a command line option in gh-deploy
.
default: gh-pages
remote_name
Set the remote name to push to when using gh-deploy
to deploy to GitHub Pages.
This option can be overridden by a command line option in gh-deploy
.
default: origin
Documentation layout
nav
This setting is used to determine the format and layout of the global navigation for the site. A minimal navigation configuration could look like this:
nav:
- 'index.md'
- 'about.md'
All paths must be relative to the mkdocs.yml
configuration file. See the
section on configuring pages and navigation for a more detailed breakdown,
including how to create sub-sections.
Navigation items may also include links to external sites. While titles are optional for internal links, they are required for external links. An external link may be a full URL or a relative URL. Any path which is not found in the files is assumed to be an external link. See the section about [Meta-Data] on how MkDocs determines the page title of a document.
nav:
- Introduction: 'index.md'
- 'about.md'
- 'Issue Tracker': 'https://example.com/'
In the above example, the first two items point to local files while the third points to an external site.
However, sometimes the MkDocs site is hosted in a subdirectory of a project’s site and you may want to link to other parts of the same site without including the full domain. In that case, you may use an appropriate relative URL.
site_url: https://example.com/foo/
nav:
- Home: '../'
- 'User Guide': 'user-guide.md'
- 'Bug Tracker': '/bugs/'
In the above example, two different styles of external links are used. First,
note that the site_url
indicates that the MkDocs site is hosted in the /foo/
subdirectory of the domain. Therefore, the Home
navigation item is a relative
link that steps up one level to the server root and effectively points to
https://example.com/
. The Bug Tracker
item uses an absolute path from the
server root and effectively points to https://example.com/bugs/
. Of course, the
User Guide
points to a local MkDocs page.
default: By default nav
will contain an alphanumerically sorted, nested
list of all the Markdown files found within the docs_dir
and its
sub-directories. Index files will always be listed first within a sub-section.
Build directories
theme
Sets the theme and theme specific configuration of your documentation site. May be either a string or a set of key/value pairs.
If a string, it must be the string name of a known installed theme. For a list of available themes visit Choosing Your Theme.
An example set of key/value pairs might look something like this:
theme:
name: mkdocs
locale: en
custom_dir: my_theme_customizations/
static_templates:
- sitemap.html
include_sidebar: false
If a set of key/value pairs, the following nested keys can be defined:
!!! block “”
#### name:
The string name of a known installed theme. For a list of available themes
visit [Choosing Your Theme].
#### locale:
A code representing the language of your site. See [Localizing your theme]
for details.
#### custom_dir:
A directory containing a custom theme. This can either be a relative
directory, in which case it is resolved relative to the directory containing
your configuration file or it can be an absolute directory path from the
root of your local file system.
See [Customizing Your Theme][theme_dir] for details if you would like to tweak an
existing theme.
See the [Theme Developer Guide] if you would like to build your own theme
from the ground up.
#### static_templates:
A list of templates to render as static pages. The templates must be located
in either the theme's template directory or in the `custom_dir` defined in
the theme configuration.
#### (theme specific keywords)
Any additional keywords supported by the theme can also be defined. See the
documentation for the theme you are using for details.
default: 'mkdocs'
docs_dir
The directory containing the documentation source markdown files. This can either be a relative directory, in which case it is resolved relative to the directory containing your configuration file, or it can be an absolute directory path from the root of your local file system.
default: 'docs'
site_dir
The directory where the output HTML and other files are created. This can either be a relative directory, in which case it is resolved relative to the directory containing your configuration file, or it can be an absolute directory path from the root of your local file system.
default: 'site'
!!! note “Note:”
If you are using source code control you will normally want to ensure that
your build output files are not committed into the repository, and only
keep the source files under version control. For example, if using git
you might add the following line to your .gitignore
file:
site/
If you're using another source code control tool, you'll want to check its
documentation on how to ignore specific directories.
extra_css
Set a list of CSS files in your docs_dir
to be included by the theme. For
example, the following example will include the extra.css file within the
css subdirectory in your docs_dir.
extra_css:
- css/extra.css
- css/second_extra.css
default: []
(an empty list).
extra_javascript
Set a list of JavaScript files in your docs_dir
to be included by the theme.
See the example in extra_css for usage.
default: []
(an empty list).
extra_templates
Set a list of templates in your docs_dir
to be built by MkDocs. To see more
about writing templates for MkDocs read the documentation about [custom themes]
and specifically the section about the [available variables] to
templates. See the example in extra_css for usage.
default: []
(an empty list).
extra
A set of key-value pairs, where the values can be any valid YAML construct, that will be passed to the template. This allows for great flexibility when creating custom themes.
For example, if you are using a theme that supports displaying the project version, you can pass it to the theme like this:
extra:
version: 1.0
default: By default extra
will be an empty key-value mapping.
Preview controls
use_directory_urls
This setting controls the style used for linking to pages within the documentation.
The following table demonstrates how the URLs used on the site differ when
setting use_directory_urls
to true
or false
.
| Source file | use_directory_urls: true | use_directory_urls: false |
|---|---|---|
| index.md | / | /index.html |
| api-guide.md | /api-guide/ | /api-guide.html |
| about/license.md | /about/license/ | /about/license.html |
The default style of use_directory_urls: true
creates more user friendly URLs,
and is usually what you’ll want to use.
The alternate style can be useful if you want your documentation to remain properly linked when opening pages directly from the file system, because it creates links that point directly to the target file rather than the target directory.
default: true
strict
Determines how warnings are handled. Set to true
to halt processing when a
warning is raised. Set to false
to print a warning and continue processing.
default: false
dev_addr
Determines the address used when running mkdocs serve
. Must be of the format
IP:PORT
.
Allows a custom default to be set without the need to pass it through the
--dev-addr
option every time the mkdocs serve
command is called.
default: '<IP_ADDRESS>:8000'
See also: site_url.
Formatting options
markdown_extensions
MkDocs uses the Python Markdown library to translate Markdown files
into HTML. Python Markdown supports a variety of extensions
that customize how pages are formatted. This setting lets you enable a list of
extensions beyond the ones that MkDocs uses by default (meta
, toc
, tables
,
and fenced_code
).
For example, to enable the SmartyPants typography extension, use:
markdown_extensions:
- smarty
Some extensions provide configuration options of their own. If you would like to
set any configuration options, then you can nest a key/value mapping
(option_name: option value
) of any options that a given extension supports.
See the documentation for the extension you are using to determine what options
they support.
For example, to enable permalinks in the (included) toc
extension, use:
markdown_extensions:
- toc:
permalink: True
Note that a colon (:
) must follow the extension name (toc
) and then on a new
line the option name and value must be indented and separated by a colon. If you
would like to define multiple options for a single extension, each option must be
defined on a separate line:
markdown_extensions:
- toc:
permalink: True
separator: "_"
Add an additional item to the list for each extension. If you have no configuration options to set for a specific extension, then simply omit options for that extension:
markdown_extensions:
- smarty
- toc:
permalink: True
- sane_lists
In the above examples, each extension is a list item (starts with a -
). As an
alternative, key/value pairs can be used instead. However, in that case an empty
value must be provided for extensions for which no options are defined.
Therefore, the last example above could also be defined as follows:
markdown_extensions:
smarty: {}
toc:
permalink: True
sane_lists: {}
This alternative syntax is required if you intend to override some options via inheritance.
!!! note “See Also:” The Python-Markdown documentation provides a list of extensions which are available out-of-the-box. For a list of configuration options available for a given extension, see the documentation for that extension.
You may also install and use various [third party extensions][3rd]. Consult
the documentation provided by those extensions for installation instructions
and available configuration options.
default: []
(an empty list).
plugins
A list of plugins (with optional configuration settings) to use when building the site. See the Plugins documentation for full details.
If the plugins
config setting is defined in the mkdocs.yml
config file, then
any defaults (such as search
) are ignored and you need to explicitly re-enable
the defaults if you would like to continue using them:
plugins:
- search
- your_other_plugin
To define options for a given plugin, use a nested set of key/value pairs:
plugins:
- search
- your_other_plugin:
option1: value
option2: other value
In the above examples, each plugin is a list item (starts with a -
). As an
alternative, key/value pairs can be used instead. However, in that case an empty
value must be provided for plugins for which no options are defined. Therefore,
the last example above could also be defined as follows:
plugins:
search: {}
your_other_plugin:
option1: value
option2: other value
This alternative syntax is required if you intend to override some options via inheritance.
To completely disable all plugins, including any defaults, set the plugins
setting to an empty list:
plugins: []
default: ['search']
(the “search” plugin included with MkDocs).
Search
A search plugin is provided by default with MkDocs which uses lunr.js as a search engine. The following config options are available to alter the behavior of the search plugin:
separator
A regular expression which matches the characters used as word separators when
building the index. By default whitespace and the hyphen (-
) are used. To add
the dot (.
) as a word separator you might do this:
plugins:
- search:
separator: '[\s\-\.]+'
default: '[\s\-]+'
min_search_length
An integer value that defines the minimum length for a search query. By default searches shorter than 3 chars in length are ignored as search result quality with short search terms are poor. However, for some use cases (such as documentation about Message Queues which might generate searches for ‘MQ’) it may be preferable to set a shorter limit.
plugins:
- search:
min_search_length: 2
default: 3
lang
A list of languages to use when building the search index as identified by their ISO 639-1 language codes. With Lunr Languages, the following languages are supported:
ar
: Arabicda
: Danishnl
: Dutchen
: Englishfi
: Finnishfr
: Frenchde
: Germanhu
: Hungarianit
: Italianja
: Japaneseno
: Norwegianpt
: Portuguesero
: Romanianru
: Russianes
: Spanishsv
: Swedishth
: Thaitr
: Turkishvi
: Vietnamese
You may contribute additional languages.
!!! Warning
While search does support using multiple languages together, it is best not
to add additional languages unless you really need them. Each additional
language adds significant bandwidth requirements and uses more browser
resources. Generally, it is best to keep each instance of MkDocs to a single
language.
!!! Note
Lunr Languages does not currently include support for Chinese or other Asian
languages. However, some users have reported decent results using Japanese.
default: The value of theme.locale
if set, otherwise [en]
.
prebuild_index
Optionally generates a pre-built index of all pages, which provides some
performance improvements for larger sites. Before enabling, confirm that the
theme you are using explicitly supports using a prebuilt index (the builtin
themes do). Set to true
to enable.
!!! warning
This option requires that [Node.js] be installed and the command `node` be
on the system path. If the call to `node` fails for any reason, a warning
is issued and the build continues uninterupted. You may use the `--strict`
flag when building to cause such a failure to raise an error instead.
!!! Note
On smaller sites, using a pre-built index is not recommended as it creates a
significant increase is bandwidth requirements with little to no noticeable
improvement to your users. However, for larger sites (hundreds of pages),
the bandwidth increase is relatively small and your users will notice a
significant improvement in search performance.
default: False
indexing
Configures what strategy the search indexer will use when building the index for your pages. This property is particularly useful if your project is large in scale, and the index takes up an enormous amount of disk space.
plugins:
- search:
indexing: 'full'
Options
| Option | Description |
|---|---|
full |
Indexes the title, section headings, and full text of each page. |
sections |
Indexes the title and section headings of each page. |
titles |
Indexes only the title of each page. |
default: full
Environment Variables
In most cases, the value of a configuration option is set directly in the
configuration file. However, as an option, the value of a configuration option
may be set to the value of an environment variable using the !ENV
tag. For
example, to set the value of the site_name
option to the value of the
variable SITE_NAME
the YAML file may contain the following:
site_name: !ENV SITE_NAME
If the environment variable is not defined, then the configuration setting
would be assigned a null
(or None
in Python) value. A default value can be
defined as the last value in a list. Like this:
site_name: !ENV [SITE_NAME, 'My default site name']
Multiple fallback variables can be used as well. Note that the last value is not an environment variable, but must be a value to use as a default if none of the specified environment variables are defined.
site_name: !ENV [SITE_NAME, OTHER_NAME, 'My default site name']
Simple types defined within an environment variable such as string, bool, integer, float, datestamp and null are parsed as if they were defined directly in the YAML file, which means that the value will be converted to the appropriate type. However, complex types such as lists and key/value pairs cannot be defined within a single environment variable.
For more details, see the pyyaml_env_tag project.
Configuration Inheritance
Generally, a single file would hold the entire configuration for a site. However, some organizations may maintain multiple sites which all share a common configuration across them. Rather than maintaining separate configurations for each, the common configuration options can be defined in a parent configuration while which each site’s primary configuration file inherits.
To define the parent for a configuration file, set the INHERIT
(all caps) key
to the path of the parent file. The path must be relative to the location of the
primary file.
For configuration options to be merged with a parent configuration, those
options must be defined as key/value pairs. Specifically, the
markdown_extensions and plugins options must use the alternative syntax
which does not use list items (lines which start with -
).
For example, suppose the common (parent) configuration is defined in base.yml
:
theme:
name: mkdocs
locale: en
highlightjs: true
markdown_extensions:
toc:
permalink: true
admonition: {}
Then, for the “foo” site, the primary configuration file would be defined at
foo/mkdocs.yml
:
INHERIT: ../base.yml
site_name: Foo Project
site_url: https://example.com/foo
When running mkdocs build
, the file at foo/mkdocs.yml
would be passed in as
the configuration file. MkDocs will then parse that file, retrieve and parse the
parent file base.yml
and deep merge the two. This would result in MkDocs
receiving the following merged configuration:
site_name: Foo Project
site_url: https://example.com/foo
theme:
name: mkdocs
locale: en
highlightjs: true
markdown_extensions:
toc:
permalink: true
admonition: {}
Deep merging allows you to add and/or override various values in your primary configuration file. For example, suppose for one site you wanted to add support for definition lists, use a different symbol for permalinks, and define a different separator. In that site’s primary configuration file you could do:
INHERIT: ../base.yml
site_name: Bar Project
site_url: https://example.com/bar
markdown_extensions:
def_list: {}
toc:
permalink:
separator: "_"
In that case, the above configuration would be deep merged with base.yml
and
result in the following configuration:
site_name: Bar Project
site_url: https://example.com/bar
theme:
name: mkdocs
locale: en
highlightjs: true
markdown_extensions:
def_list: {}
toc:
permalink:
separator: "_"
admonition: {}
Notice that the admonition
extension was retained from the parent
configuration, the def_list
extension was added, the value of
toc.permalink
was replaced, and the value of toc.separator
was added.
You can replace or merge the value of any key. However, any non-key is always replaced. Therefore, you cannot append items to a list. You must redefine the entire list.
As the nav configuration is made up of nested lists, this means that you
cannot merge navigation items. Of course, you can replace the entire nav
configuration with a new one. However, it is generally expected that the entire
navigation would be defined in the primary configuration file for a project.
!!! warning
As a reminder, all path based configuration options must be relative to the
primary configuration file and MkDocs does not alter the paths when merging.
Therefore, defining paths in a parent file which is inherited by multiple
different sites may not work as expected. It is generally best to define
path based options in the primary configuration file only.


A string of attacks: a strike with the left elbow before Kyo does a right low kick, then twists right around to do a left sobat kick before rearing back and performing a heavy shoulder slam to, as the name suggests, 'blow back' his opponent. The combo brings him slightly forward upon execution, and the final part of it can be charged for a delay and has priority over other normals.
UppercutQuite literally an uppercut in which Kyo quickly drops to a knee before bringing his fist flying straight up when he rises again.
Crouching Low KickA simple kick made when Kyo is crouching. Recovers fast enough for him to combo into any normal or Smash attack.
Geshiki: Gofu YoA simple axe kick that brings his body weight forward to give more 'kick'(lol) to the blow.
R.E.D KickKyo leaps across a considerable distance with a combustion-fueled propulsion that sends him into an arcing kick. A precision move that can be used to leap right over a projectile or thrown item to attack the pitcher directly.
Jumping Light KickAn aerial knee that knocks the opponent downward when hit.
Jumping Heavy KickKyo does a mid-air spin into an aerial axe kick. Can hit enemy above him as well as enemy below him, making it functionally a two-hit attack.
Jumping Heavy PunchFunctions much like the aerial knee with the exception of knocking the enemy more diagonally.
Naraku OtoshiA powerful airbound hammerfist that smashes the enemy straight downward. Outright comparable to Captain Falcon's lower body variation.
101 Shiki: OborogurumaKyo propels himself forward with a combustion propulsion into a triple flying kick.
75 Shiki: KaiA jumping, rising double kick. This move also brings him slightly forward.
88 ShikiKyo drops to his left hand and brings his feet swinging low for a double kick. The move only smashes if both hits connect.
Kyo will lift his opponent by their very neck or head and blow them away with a flaming explosion that continues to burn their being for a few seconds afterward.
Issetsu Seoi NageKyo throws his enemy over his shoulder and straight into the ground before following up immediately with an elbow drop to their neck or head.
Knee SmashKyo just keeps smashing his knee into his opponent's gut.
Kyo flicks out a fast-moving fireball right across the ground. Though it is easy to simply jump over, its grounded state allows it to run right past projectiles or thrown items and hit the user directly. When cast in the air it travels diagonally from where Kyo is, and unlike Orochinagi it does not force him back from 'recoil'.
Saishuu Kessen Ougi "Mu Shiki"Essentially a stronger but slower fist version of Marth/Lucina's Dancing Blade with only three hits to it. Each hit adds another tick of 'burn' to the opponent thus making it functionally a six-hit attack. The final hits of the combo special will knock the opponent towards the final directional input: up sends them directly upward, forward sends them flying forward, down sends them crashing into the ground to stun them long enough to follow up with another attack.
100 Shiki: OniyagiKyo twists around and smashes the back of his fist into an opponent before bringing them up with him in a spiral of fire before effectively blasting them away with the updrafts from his flames. The opponent can still be burned by the fire but it is very mild in comparison to his other specials along with lacking the smashing power of the others. Its greatest use is its horizontal recovery due to the flames affecting the direction of wind.
Ura 180 Shiki: OrochinagiKyo lets loose the normal innate compression of his fire as a full sheet of offensive and defensive inferno before him; the aerial version pushes him back a bit, giving him just a bit more air time. Unlike his other specials it has a noticeable pause at it's fastest, and continuing on with its uniqueness he can charge it to make it more damaging - however, the more it is charged the faster it dissipates.
The EX Variant travels near-instantly along the ground and leaves behind a trail of fire that persists for several seconds after it is used. Kyo himself is immune to these flames. The aerial version is a straight diagonal shot that explodes on impact. The fireball in both versions sets the opponent ablaze for a few seconds.
Saishuu Kessen Ougi "Mu Shiki"The EX Variant has Kyo outright exploding into fire and attacking viciously with every single variation of the attack at crazy speed; a pillar of fire has a soft 'vacuum' effect on the opponent to keep them from escaping the barrage of punches. The final blow sends them flying with 100%-level regardless of damage.
100 Shiki: OniyagiThe EX Variant is a significant upgrade in that there are two chances to hit with it fully: at the beginning and at the zenith. The flames have a slight vacuum effect much like the fire pillar in "Mu Shiki", and upon connecting at the zenith of the Oniyagi Kyo unleashes a three-hit S.K.O. "M.U" before knocking them straight forward and away. Connecting this zenith attack allows Kyo to cast the move a second time, including the EX Variant if he has the proper amount of meter.
Ura 180 Shiki: OrochinagiThe EX Variant is instantly cast and at full strength, as well as persisting longer than it does at its weakest. It also fully revolves around him as a more defensive ability along with incinerating those that continue to molest him.
Kyo casually lifts his left hand up and throws a small flame forward - upon connecting, a massive roar of inferno screams forward from behind him to completely engulf the opponent and the part of the stage he’s on (in the air it just goes straight a certain distance). Enemies that are hit at any point in the inferno is continuously sent along with what bursts of fire remain to be cast until hitting the end of the portion of stage (last explosion while cast mid-air). Causes a full 100% damage on contact; being hit by the last gout of fire KOs the opponent.
Kyo depletes all three gauges into a single punch. He then launches himself forward to smash his fist into the opponent. Upon connecting the entire screen is engulfed in a massive blooming inferno that heavily damages all opponents and destroys all destructible objects and items on the stage. The one hit with the punch is completely KO’d regardless of where on the stage they are; their body is left in a knockdown state before disappearing.


The following there/their mistakes have been found:
{% for words in grammar_check.there_their %}
- {{ words }}
{% endfor %}
The difference between there and their is:
- There does not show possession. Only the word their (not there) shows possession.
- Their is almost always followed by a noun. That is not true of the word "there".


Modern Web development one jump at the time
Photo by Denny Luan on Unsplash
The ungap project was born after years of attempts to always fix the same issue, but never in a modular way and, most importantly, never in a single, 100% code covered, organization.
Each module is written in ES5 compatible syntax to avoid both unnecessary transpilers bloat and potentially unexpected behaviors. Each module is also 100% code-covered through tests able to verify the whole API both as native and polyfilled version. The constrains per module are the following:
[1] as example: stripped out features detections
There are parts of the specifications that are very hard, if not impossible, to polyfill. The main purpose of this project is to help developers move forward, and possibly without unnecessary bloat. This basically means that polyfills are written to support 99% of the use cases, without granting 100% spec compliance.
If you need that, which again is basically impossible in most of the cases, feel free to keep using whatever monolithic polyfill or approach you were using before.
Every single module is made available as ESM, through the package.json
's module
field, CJS via package.json
's main
field, and browser script polyfill / patch via package.json
's unpkg
field so that you can use directly the unpkg CDN.
// as ECMAScript module
import WeakSet from '@ungap/weakset';
// as CommonJS module
const WeakSet = require('@ungap/weakset');
// as Browser global patch
<script src="https://unpkg.com/@ungap/weakset"></script>
Essentials modules covers most common use cases without going full bloated API.
As example, the essential-map exposes only get
, set
, delete
, and has
which is most of the time everything one needs, as opposite of going full map.
The main benefit of the essential modules is their size, simplicity, or even performance.
Symbol
.Symbol
.CustomEvent
.\u2028|9
in all JS engines with a JSON
global.Class.new(...args)
instead of new Class(...args)
Element.contains
compatible with all JS engines with a DOM env.Function.prototype.once
compatible with modern JS engines.Reflect.ownKeys
compatible with all JS engines.WeakRef
and FinalizationGroup
compatible with any engine that already has a WeakMap
(i.e. IE11+).WeakMap
(i.e. IE11+).Ungap utilities are meant to simplify cross browser development without the bloat of a whole polyfill.
CustomElement.new()
instead of new CustomElement()
due WebKit/Safari built-in extends caveat.If you are targeting modern browsers only, you might want to exclude some unnecessary code from various ungapped APIs.
Following a list of plugins which aim is to address those cases:
Each module is under the npm default ISC license.
You are welcome to join the organization after your first module is published.
In order to do so, please take any already available module as example of how to create and test any code you need.
The main guideline though, can be summarized as such:
./index.js
../esm/index.js
../cjs/index.js
.I have personally no interest in enforcing any specific linting rule or code style, as long as common sense and good practices are part of the code.
If these basic constrains are good enough for you, please do help this project grow, allowing the community to leave all monolithic polyfills part of the past.
If you have further questions, you can DM me @webreflection [1]
[1] my DMs are open


UX Researcher | UX Designer | Team Size: 5
User ResearchUX Design WebsiteCHI Design Competition
Thunder OS is a ROM based on android that is free to download and install through 360 PC Security software.
It provides solution for low price smart phones to maintain fast speed and long battery life.
Goal: Design a system contact app that provides users with better user experience and performance.
This is a product targeting low-end smart phones that are already slow in performance and our product should be a solution but not a burden as compared to their current system contacts app.
Due to the high cost in developing from scratch, we are required to work with an existing product that was designed as a third party contact app, so our design in features was restrainted by this.
The product was projected to launch in a month, which includes design, development, testing, and adaptation to multiple device modals.
Competetive Analysis: MIUI, Color OS, EMUI, Android L, iOS
Research: 3 focus group interview & 100+ Marketing Research Surveys
Insight 1: Chinese android phone users who are interested in customized ROM are early adaptors of new things. They want an avant-garde interface that differentiates them from regular users.
Insight 2: They are people who work under high pressure, so an ideal contact app need to have advance features and simple interactions to ensure productivity.
Main Features: Dailer, Contacts, Message, Spam-blocker, Multiple Sim Card Support
Information Architecture: Present only the most relevant information upfront, and hide all additional features into hidden menu and long press action.
Wireframe: Simplifying the information structure, highlighting only the important information.
Interface: Adapting material design but include more viewable signifiers to avoid confusion.
Animation: Smooth but simple animation to enhance the sense of high quality.


Watch the animation below to learn the basic steps of a systematic review. Then head to our courses to learn more.


Cost models for TJob
job
.
euro_symbol
SETUP COST
125
METER LIST
Shows summary of all meters defined by this service.
Name
Type
Unit
Cost
meter
Dynamically computed costs for TJob
job
based on execution data.
At page load, the remote server time was:
time
.
warning
No data was received from emp for calculation.
Charts if shown are meaningful only if this dialog does not appear.
COST BREAKUP
Actual cost breakdown by individual service components.
euro_symbol
TOTAL COMPUTED COST
125
125
USAGE VALUES USED
These are the resource consumption value used in the true cost computation.
Go back


Hello!
Leaderboard
Report
Success Stories
Discussion Forum
Your Investments report.
Check out the trends
Check Out!


{% extends "base.html" %} {%- block app_content %}
Certificate Link for {{ workshop.title }} ({{ workshop.topic }}) held on {{ workshop.date_format }}
{{ workshop.url }}


{% extends "admin/filer/base_site.html" %} {% load i18n %} {% load admin_urls %} {% block breadcrumbs %} {% include "admin/filer/breadcrumbs.html" with instance=object breadcrumbs_action="Delete" %} {% endblock %} {% block content %} {% if perms_lacking or protected %} {% if perms_lacking %}
{% blocktrans with escaped_object=object %}Deleting the {{ object_name }} '{{ escaped_object }}' would result in deleting related objects, but your account doesn't have permission to delete the following types of objects:{% endblocktrans %}
{% blocktrans with escaped_object=object %}Deleting the {{ object_name }} '{{ escaped_object }}' would require deleting the following protected related objects:{% endblocktrans %}
{% blocktrans with escaped_object=object %}Are you sure you want to delete the {{ object_name }} "{{ escaped_object }}"? All of the following related items will be deleted:{% endblocktrans %}


/* create Isaac */ var person = { firstName:"Isaac", lastName:"Watts", fullName : function() { return this.firstName + " " + this.lastName; } }; /* create list of employees */ var employees = []; /*set company success*/ var companySuccess = null; /* Check list of employees */ for(var i = 0; i < employees.length; i++) { /* Check if Isaac is employee */ if (employees[i].fullName != "Isaac Watts") { /* Push Isaac to employee */ employees.push(person); companySuccess = true; }; };
Isaac Watts
I possess more than 3 years of progressive experience in the web development field. My professional history includes positions such as Junior Developer at EKR Agency as well as a variety of independent work.
My responsibilities have included creation of emails, custom WordPress template development, and styling mobile versions of client sites.


{# todo(issue_#24) - Add link to the overview page. #}
{% if profile_info is none or profile_info is undefined %}
Sign up
Log in
{% else %}
{{ profile_info['username'] }}
person
Organizations map
Add new receiver station
My profile
Log out
{% endif %}
{% block main %} {% endblock %}


Hey there, today's tech post will cover a particular enumerable method called cycle. It's a very simple yet useful method that actually allows you to in-line script iteration over an array as many times as you like. With this method for-loops, which I will always love and hold in special place, have virtually no reason to be in your code. This method is easy to call with remarkably very little syntax. Let's just start by recalling what our code would look like without it and build our way up from the basic for loop. In the code block below, an example is shown with an array of 5 elements that we wish to iterate over and print each element 3 times:
a = [1,2,3,4,5]
for i in 1..3
for j in 1..5
puts "printing element #{a[j]}"
end
end
Equivalent to:
3.times { a.each {|e| puts "printing element #{e}" }}
Which is equivalent to:
a.cycle(3) { puts "printing element #{e}"}
As you can see in the code block above, it's very short and serves well to cut down the syntax required for iteration of any type. What's more is that you can actually call cycle without any argument to loop indefinitely. If cycle completes its specified loops over the array without interuption it will return nil.


pyqt-demo¶
The pyqtdeploy
source package contains
a demo application called pyqt-demo which can be found in the
demo
sub-directory.
The demo consists of:
pyqt-demo.py
which is the source code of the demosysroot.toml
which is the sysroot specification used by pyqtdeploy-sysroot to build a target-specific sysrootpyqt-demo.pdt
which is the pyqtdeploy project file describing the application and its componentsbuild-demo.py
which is a simple script to run pyqtdeploy-sysroot and pyqtdeploy-build to create the demo executable
Note that executables can be created for all supported targets without requiring any changes to any of the above.
When run, the demo displays a GUI table of interesting values including a copy of the source code itself.
Throughout the rest of this documentation the demo will be used as a working example which we will look at in detail.
Note
It is recommended that, at first, you use the same versions (as specified
in sysroot.toml
) of the different component packages shown above.
Only when you have those working should you then use the versions that you
really want to use. This will require you to modify sysroot.toml
and/or pyqt-demo.pdt
.
Building the Demo¶
To build the demo for the native target, run:
python build-demo.py
The sysroot that will be created will contain the following components:
Python
Qt
OpenSSL
zlib
SIP
PyQt
PyQt3D
PyQtChart
PyQtDataVisualization
PyQtNetworkAuth
PyQtPurchasing
QScintilla
If you don’t want to build all of these then edit sysroot.toml
and
remove the ones you don’t want. (The Python, Qt, SIP and PyQt components are
required.)
Note that, on Linux, macOS and Windows, Qt will be built from source which can take a significant amount of time.
If you are building the demo for either Android or iOS then you must also
install an appropriate version of Qt from an installer from The Qt Company as
pyqtdeploy-sysroot does not support building Qt from source for
those platforms. The --qmake
option must be used to specify the full path
name of the qmake executable.
build-demo.py
has a number of other command line options. To see them all,
run:
python build-demo.py --help
Note
You must ensure that the target-specific development environment (e.g. Android Studio, MSVC, Xcode) is installed and properly configured on your system. With a Linux target you must also ensure that the development packages required to build Qt are installed. The names of these packages vary depending on the Linux distribution - please see the Qt documentation.
Android¶
Host platform used: macOS Monterey (v12.6.1)
Development tools used: NDK r21d, SDK build tools v33.0.0
Python SSL support implemented: dynamically linked bundled OpenSSL.
Qt SSL support implemented: dynamically linked bundled OpenSSL.
Environment: ANDROID_NDK_PLATFORM=android-24
iOS¶
Host platform used: macOS Monterey (v12.6.1)
Development tools used: Xcode v13.2.1
Python SSL support implemented: none.
Qt SSL support implemented: dynamically linked Secure Transport.
Linux¶
Host platform used: Ubuntu 20.04.5 LTS
Development tools used: gcc v9.4.0
Python SSL support implemented: dynamically linked system OpenSSL
Qt SSL support implemented: dynamically linked system OpenSSL
macOS¶
Host platform used: macOS Monterey (v12.6.1)
Development tools used: Xcode v12.4
Python SSL support implemented: statically linked OpenSSL.
Qt SSL support implemented: statically linked OpenSSL.
Windows¶
Host platform used: Windows 10 Pro (22H2)
Development tools used: Visual Studio Build Tools 2019 (v16.11.14)
Python SSL support implemented: statically linked OpenSSL.
Qt SSL support implemented: statically linked OpenSSL.


|
Battleships
1.0
|
Game class used to display and connect all the sub classes. More...
#include <Game.h>
Public Slots | |
| void | play () |
| Slot to start playing. | |
| void | quit () |
| Slot to quit playing. | |
| void | restartGame () |
| Slot to restart game. | |
Public Member Functions | |
| Game (QWidget *parent=NULL) | |
| void | mainMenu () |
| Fuction to display main menu. | |
Public Attributes | |
| QGraphicsScene * | scene |
| Battleships::MouseController * | mouseController |
| Battleships::Computer * | computer |
| Battleships::Board * | boardLeft |
| Battleships::Board * | boardRight |
| Battleships::Board * | boardShips |
| Battleships::Ship * | bigShip |
| Battleships::Ship * | mediumShip |
| Battleships::Ship * | mediumShip_2 |
| Battleships::Ship * | smallShip |
| Battleships::Ship * | smallShip_2 |
| QGraphicsTextItem * | text |
| Battleships::GameButton * | button |
| QPushButton * | buttonStart |
| QPushButton * | buttonExit |
Game class used to display and connect all the sub classes.


|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
| Class Summary | |
|---|---|
| BoolValueConstruct | GData schema extension describing a node with a boolean value. |
| CrawlIssueCrawlType | Type of crawl of the crawl issue. |
| CrawlIssueDateDetected | Detection date for the issue. |
| CrawlIssueDetail | Detail of the crawl issue. |
| CrawlIssueEntry | Describes a crawl issue entry. |
| CrawlIssueIssueType | Type of crawl issue. |
| CrawlIssueLinkedFromUrl | Source URL that links to the issue URL. |
| CrawlIssuesFeed | Feed of crawl issues for a particular site. |
| CrawlIssueUrl | URL affected by the crawl issue. |
| CrawlRateConstruct | GData schema extension describing a node with a crawl rate. |
| DateTimeValueConstruct | GData schema extension describing a node with a DateTime value. |
| DomainPreferenceConstruct | GData schema extension describing a node with a domain preference. |
| IntValueConstruct | GData schema extension describing a node with an integer value. |
| Keyword | A keyword in a site or in a link to a site. |
| Keyword.Source | Source. |
| KeywordEntry | Describes a keyword entry. |
| KeywordsFeed | Feed of keywords for a particular site. |
| MessageEntry | This class represents a message entry. |
| MessageEntry.BodyExtension | Value construct to represent field. |
| MessageEntry.DateExtension | DateTimeValueConstruct to represent |
| MessageEntry.LanguageExtension | Value construct to represent |
| MessageEntry.ReadExtension | BoolValueConstruct to represent |
| MessageEntry.SubjectExtension | Value construct to represent |
| MessagesFeed | The MessagesFeed class extends the BaseFeed class to define a feed of messages. |
| Namespaces | Webmaster Tools XML namespace definitions. |
| RegionCodeValueConstruct | GData schema extension describing a node with a region code value. |
| SitemapMobile | Represents list of available markup languages for mobile sitemap. |
| SitemapNews | Represents list of available publication labels for News sitemap. |
| SitemapsEntry<E extends SitemapsEntry<E>> | Defines an abstract base class for sitemap entry. |
| SitemapsEntry.LastDownloaded | Represents a single |
| SitemapsEntry.SitemapStatus | Represents |
| SitemapsEntry.UrlCount | Represents a single |
| SitemapsFeed | The SitemapsFeed class customizes the generic BaseFeed class to define a feed of sitemaps that Webmaster Tools user has for a given site. |
| SitemapsMobileEntry | This represents a single Mobile sitemap entry in a list of sitemaps. |
| SitemapsMobileEntry.MarkupLanguage | Represents a single |
| SitemapsNewsEntry | This represents a single News sitemap entry in a list of sitemaps. |
| SitemapsNewsEntry.PublicationLabel | Represents |
| SitemapsRegularEntry | This represents a single regular sitemap entry in a list of sitemaps. |
| SitemapsRegularEntry.SitemapType | Represents a single |
| SitesEntry | This represents a single web site entry. |
| SitesEntry.Crawled | Deprecated. This class is not used any more. |
| SitesEntry.CrawlingRate | Crawl Rate construct to represent |
| SitesEntry.EnhancedImageSearch | Boolean value construct to represent |
| SitesEntry.Geolocation | Region code value construct to represent |
| SitesEntry.Indexed | Deprecated. This class is not used any more. |
| SitesEntry.PreferredDomain | Domain Preference construct to represent |
| SitesEntry.Verified | Boolean value construct to represent |
| SitesFeed | The SitesFeed class customizes the generic BaseFeed class to define a feed of web sites that Webmaster Tools user has. |
| VerificationMethod | GData schema extension describing a node specifying verification method. |
| Enum Summary | |
|---|---|
| CrawlIssueCrawlType.CrawlType | Value. |
| CrawlIssueIssueType.IssueType | Value. |
| CrawlRate | CrawlRate is an enumerated type that indicates the desired crawl rate to use for a concrete site. |
| DomainPreference | DomainPreference is an enumerated type that indicates the preferred domain to use for a concrete site for Webmaster tools. |
| VerificationMethod.MethodType | Enumerates supported verification method types. |
|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


3 writes to _throttleManager
System.Management.Automation (3)
engine\remoting\client\Job.cs (3)
2772
_throttleManager
= throttleManager;
2806
_throttleManager
= throttleManager;
3500
_throttleManager
= null;
2 references to _throttleManager
System.Management.Automation (2)
engine\remoting\client\Job.cs (2)
2876
_throttleManager
.StopOperation(Helper);
3499
UnregisterThrottleComplete(
_throttleManager
);


Parker's holding food drive
by Colin DacreA local car dealership is holding a food drive in support of the food bank this holiday season.
Parker’s Chrysler is inviting the public to drop off non-perishable food items by Dec. 15 for the Salvation Army.
“This can be a difficult time of year for many, so we have decided to support the Salvation Army Food Bank with donations of non-perishable items and monetary donations, states Jim Tabler, general manager of Parker’s Chrysler.
Those that donate will be entered in a draw to win one of three prizes: a $200 service credit, $175 detail package or $500 off the purchase of a vehicle.
“We are excited about this community drive and are also hoping to raise some much-needed monetary donations. Bring your cash or cheque for the Salvation Army to Parkers and we are going to match all donations up to $1000,” added Tabler.
The dealership is hoping to raise at least $2,000.


When I need a little inspiration to remind me of why I spend my days in the classroom, I just remember what Lee Iococca said:
In a completely rational society, the best of us would be teachers and the rest of us would have to settle for something else.


--- layout: default group: 'navigation' title: FAQ bodyclass: faq headline: 'Frequently Asked Questions' ---
We want to be a framework that provides an infrastructure and connects so to say “service” parts of applications with their “brains” — business logic. Find out how following industry trends we were inspired to create Spine.
Because Protocol Buffers are implemented in a variety of languages, they make interoperability between polyglot applications in your architecture that much simpler. If you’re introducing a new service with one in Ruby or Go, or even communicating with a backend written in Node, or Clojure, you simply have to hand the proto file to the code generator written in the target language and you have some nice guarantees about the safety and interoperability between those architectures.
The finer points of platform specific data types should be handled for you in the target language implementation, and you can get back to focusing on the hard parts of your problem instead of matching up fields and data types in your ad hoc JSON encoding and decoding schemes.
Have a look the comparison matrix created by Kenton Varda, the author of Protobuf v2 and Cap'n Proto. The main features that make Protobuf best choice for our framework are:
Also, the experience Google gained through years of using this technology internally is a major factor of preferring Protobuf over alternatives.
The framework is based on and supports only proto3 dialect.


This example simply blits tile graphics to the screen from a 1 dimensional tile map array.You can view the page source with your browser's developer tools.


| División |
Equipo |
Ciudad |
| American Football Conference |
| Este |
Buffalo Bills |
Orchard Park, NY2 |
| Miami Dolphins |
Miami Gardens, FL |
| New England Patriots |
Foxborough, MA |
| New York Jets |
East Rutherford, NJ |
| Norte |
Baltimore Ravens |
Baltimore, MD |
| Cincinnati Bengals |
Cincinnati, OH |
| Cleveland Browns |
Cleveland, OH |
| Pittsburgh Steelers |
Pittsburgh, PA |
| Sur |
Houston Texans |
Houston, TX |
| Indianapolis Colts* |
Indianápolis, IN |
Lucas Oil Stadium |
1953 |
Chuck Pagano |
| Jacksonville Jaguars |
Jacksonville, FL |
EverBank Field |
1995 |
Gus Bradley |
| Tennessee Titans* |
Nashville, TN |
LP Field |
1960 |
1970 |
Ken Whisenhunt |
| Oeste |
Denver Broncos |
Denver, CO |
Sports Authority Field at Mile High |
1960 |
1970 |
Gary Kubiak |
| Kansas City Chiefs* |
Kansas City, MO |
Arrowhead Stadium3 |
1960 |
1970 |
Andy Reid |
| Oakland Raiders* |
Oakland, CA |
O.co Coliseum |
1960 |
1970 |
Jack Del Rio |
| San Diego Chargers* |
San Diego, CA |
Qualcomm Stadium |
1960 |
1970 |
Mike McCoy |
| National Football Conference |
| Este |
Dallas Cowboys |
Arlington, TX |
AT&T Stadium |
1960 |
Jason Garrett |
| New York Giants |
East Rutherford, NJ |
MetLife Stadium |
1925 |
Tom Coughlin |
| Philadelphia Eagles |
Filadelfia, PA |
Lincoln Financial Field |
1933 |
Chip Kelly |
| Washington Redskins* |
Landover, MD |
FedExField |
1932 |
Jay Gruden |
| Norte |
Chicago Bears* |
Chicago, IL |
Soldier Field |
1919 |
1920 |
John Fox |
| Detroit Lions* |
Detroit, MI |
Ford Field |
1929 |
1930 |
Jim Caldwell |
| Green Bay Packers |
Green Bay, WI |
Lambeau Field |
1919 |
1921 |
Mike McCarthy |
| Minnesota Vikings |
Minneapolis, MN |
TCF Bank Stadium4 |
1961 |
Mike Zimmer |
| Sur |
Atlanta Falcons |
Atlanta, GA |
Georgia Dome |
1966 |
Dan Quinn |
| Carolina Panthers |
Charlotte, Carolina del Norte |
Bank of America Stadium |
1995 |
Ron Rivera |
| New Orleans Saints |
Nueva Orleans, LA |
Louisiana Superdome |
1967 |
Sean Payton |
| Tampa Bay Buccaneers |
Tampa, FL |
Raymond James Stadium |
1976 |
Lovie Smith |
| Oeste |
Arizona Cardinals* |
Glendale, AZ |
University of Phoenix Stadium |
1898 |
1920 |
Bruce Arians |
| St. Louis Rams* |
St. Louis, MO |
Edward Jones Dome |
1936 |
1937 |
Jeff Fisher |
| San Francisco 49ers |
Santa Clara, CA |
Levi's Stadium |
1946 |
1950 |
Jim Tomsula |
| Seattle Seahawks |
Seattle, WA |
CenturyLink Field |
1976 |
Pete Carroll |


Hi ${user.firstName},
A request was made to update your email address to a new email address. All communication from Crossroads will go to this new email address.
Click the following link to confirm [New_Email_Address] is your new, correct address:
If you did not make this request, contact us at<EMAIL_ADDRESS>immediately.
If you’re having difficulty confirming your new email address, check out the help page.


Table of Contents
Resources:
- A Thorough Introduction to Boltzmann Machines
- RBMs Developments (Hinton Talk)
- A Tutorial on Energy-Based Learning (LeCun)
- DBMs (paper Hinton)
- Generative training of quantum Boltzmann machines with hidden units (paper)
- Binary Stochastic Neurons in TF
- Geometry of the Restricted Boltzmann Machine (paper)
Preliminaries
- The Boltzmann Distribution:
The Boltzmann Distribution is a probability distribution (or probability measure) that gives the probability that a system will be in a certain state as a function of that state’s energy and the temperature of the system:$$p_{i} = \dfrac{1}{Z} e^{-\frac{\varepsilon_{i}}{k_B T}}$$
where \(p_{i}\) is the probability of the system being in state \(i\), \(\varepsilon_{i}\) is the energy of that state, and a constant \(k_B T\) of the distribution is the product of Boltzmann’s constant \(k_B\) and thermodynamic temperature \(T\), and \(Z\) is the partition function.
The distribution shows that states with lower energy will always have a higher probability of being occupied.
The ratio of probabilities of two states (AKA Boltzmann factor) only depends on the states’ energy difference (AKA Energy Gap):{: #bodyContents92BF}$$\frac{p_{i}}{p_{j}}=e^{\frac{\varepsilon_{j}-\varepsilon_{i}}{k_B T}}$$
Derivation:
The Boltzmann distribution is the distribution that maximizes the entropy:$$H\left(p_{1}, p_{2}, \cdots, p_{M}\right)=-\sum_{i=1}^{M} p_{i} \log_{2} p_{i}$$
subject to the constraint that \(\sum p_{i} \varepsilon_{i}\) equals a particular mean energy value.
This is a simple Lagrange Multipliers maximization problem (can be found here).
Applications in Different Fields:
- Statistical Mechanics
The canonical ensemble is a probability distribution with the form of the Boltzmann distribution.
It gives the probabilities of the various possible states of a closed system of fixed volume, in thermal equilibrium with a heat bath. - Measure Theory
The Boltzmann distribution is also known as the Gibbs Measure.
The Gibbs Measure is a probability measure, which is a generalization of the canonical ensemble to infinite systems. - Statistics/Machine-Learning
The Boltzmann distribution is called a log-linear model. - Probability Theory/Machine-Learning
The Boltzmann distribution is known as the softmax function.
The softmax function is used to represent a categorical distribution. - Deep Learning
The Boltzmann distribution is the sampling distribution of stochastic neural networks (e.g. RBMs).
- Statistical Mechanics
-
Asynchronous:
- Asynchronous:
Boltzmann Machines
-
Boltzmann Machines (BMs):
A Boltzmann Machine (BM) is a type of stochastic recurrent neural network and Markov Random Field (MRF).Goal - What do BMs Learn:
Boltzmann Machines were originally introduced as a general “connectionist” approach to learning arbitrary probability distributions over binary vectors.
They are capable of learning internal representations of data.
They are also able to represent and solve (difficult) combinatoric problems.Structure:
- Input:
BMs are defined over a \(d\)-dimensional binary random vector \(\mathrm{x} \in\{0,1\}^{d}\). - Output:
The units produce binary results. - Units:
- Visible Units: \(\boldsymbol{v}\)
- Hidden Units: \(\boldsymbol{h}\)
- Probabilistic Model:
It is an energy-based model; it defines the joint probability distribution using an energy function:$$P(\boldsymbol{x})=\frac{\exp (-E(\boldsymbol{x}))}{Z}$$
where \(E(\boldsymbol{x})\) is the energy function and \(Z\) is the partition function.
- The Energy Function:
- With only visible units:
$$E(\boldsymbol{x})=-\boldsymbol{x}^{\top} \boldsymbol{U} \boldsymbol{x}-\boldsymbol{b}^{\top} \boldsymbol{x}$$
where \(U\) is the “weight” matrix of model parameters and \(\boldsymbol{b}\) is the vector of bias parameters.
- With both, visible and hidden units:
$$E(\boldsymbol{v}, \boldsymbol{h})=-\boldsymbol{v}^{\top} \boldsymbol{R} \boldsymbol{v}-\boldsymbol{v}^{\top} \boldsymbol{W} \boldsymbol{h}-\boldsymbol{h}^{\top} \boldsymbol{S} \boldsymbol{h}-\boldsymbol{b}^{\top} \boldsymbol{v}-\boldsymbol{c}^{\top} \boldsymbol{h}$$
- With only visible units:
Approximation Capabilities:
A BM with only visible units is limited to modeling linear relationships between variables as described by the weight matrix1.
A BM with hidden units is a universal approximator of probability mass functions over discrete variables (Le Roux and Bengio, 2008).Relation to Hopfield Networks:
A Boltzmann Machine is just a Stochastic Hopfield Network with Hidden Units.
BMs can be viewed as the stochastic, generative counterpart of Hopfield networks.It is important to note that although Boltzmann Machines bear a strong resemblance to Hopfield Networks, they are actually nothing like them in there functionality.
- Similarities:
- They are both networks of binary units.
- They both are energy-based models with the same energy function
- They both have the same update rule/condition (of estimating a unit’s output by the sum of all weighted inputs).
- Differences:
- Goal: BMs are NOT memory networks. They are not trying to store things. Instead, they employ a different computational role; they are trying to learn latent representations of the data.
The goal is representation learning. - Units: BMs have an extra set of units, other than the visible units, called hidden units. These units represent latent variables that are not observed but learned from the data.
These are necessary for representation learning. - Objective: BMs have a different objective; instead of minimizing the energy function, they minimize the error (KL-Divergence) between the “real” distribution over the data and the model distribution over global states (marginalized over hidden units).
Interpreted as the error between the input data and the reconstruction produced by the hidden units and their weights.
This is necessary to capture the training data probability distribution. - Energy Minima: energy minima were useful for Hopfield Nets and served as storage points for our input data (memories). However, they are very harmful for BMs since there is a global objective of finding the best distribution that approximates the real distribution.
This is necessary to capture the training data probability distribution “well”. - Activation Functions: the activation function for a BM is just a stochastic version of the binary threshold function. The unit would still update to a binary state according to a threshold value but with the update to the unit state being governed by a probability distribution (Boltzmann distribution).
This is necessary (important\(^{ * }\)) to escape energy minima.
- Goal: BMs are NOT memory networks. They are not trying to store things. Instead, they employ a different computational role; they are trying to learn latent representations of the data.
Relation to the Ising Model:
The global energy \(E\) in a Boltzmann Machine is identical in form to that of the Ising Model.Notes:
- Factor Analysis is a Causal Model with continuous variables.
- Input:
- Unit-State Probability:
- The units in a BM are binary units.
- Thus, they have two states \(s_i \in \{0,1\}\) to be in:
- On: \(s_i = 1\)
- Off: \(s_i = 0\)
- The probability that the \(i\)-th unit will be on (\(s_i = 1\)) is:
$$p(s_i=1)=\dfrac{1}{1+ e^{-\Delta E_{i}/T}}$$
where the scalar \(T\) is the temperature of the system.
- The RHS is just the logistic function. Rewriting the probability:
$$p(s_i=1)=\sigma(\Delta E_{i}/T)$$
- Using the Boltzmann Factor (ratio of probabilities of states):
$$\begin{align} \dfrac{p(s_i=0)}{p(s_i=1)} &= e^{\frac{E\left(s_{i}=0\right)-E\left(s_{i}=1\right)}{k T}} \\ \dfrac{1 - p(s_i=1)}{p(s_i=1)} &= e^{\frac{-(E\left(s_{i}=1\right)-E\left(s_{i}=0\right))}{k T}} \\ \dfrac{1}{p(s_i=1)} - 1 &= e^{\frac{-\Delta E_i}{k T}} \\ p(s_i=1) &= \dfrac{1}{1 + e^{-\Delta E_i/T}} \end{align} $$
where we absorb the Boltzmann constant \(k\) into the artificial Temperature constant \(T\).
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
- Asynchronous:
Restricted Boltzmann Machines (RBMs)
-
Restricted Boltzmann Machines (RBMs):
Restricted Boltzmann Machines (RBMs) -
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
Deep Boltzmann Machines (DBNs)
-
Deep Boltzmann Machines (DBNs):
Deep Boltzmann Machines (DBNs) -
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Asynchronous:
-
Specifically, the probability of one unit being on is given by a linear model (logistic regression) from the values of the other units. ↩


Database Tables
DataMapper is implemented with Database normalization Fifth normal form in mind. In short, that means every table is aware only of itself, with fields relevant only to itself. If a table has a relationship with another table, it is represented by a special joining table. These joining tables hold all the relationships between records of other tables.
Lets take a look at the below example.
countries
| id | code | name |
|---|---|---|
| 12 | AM | Armenia |
| 13 | AW | Aruba |
| 14 | AU | Australia |
| 15 | AT | Austria |
countries_users
| id | country_id | user_id |
|---|---|---|
| 1 | 14 | 7 |
| 1 | 12 | 8 |
users
| id | username | password | |
|---|---|---|---|
| 7 | Foo | ec773c1da6f96b0265d76fa0a53db697e66a8eea |<EMAIL_ADDRESS>|
| 8 | Baz | 383f27f548397ea123ec444505ef4c7cd993dbf6 |<EMAIL_ADDRESS>|
Here we have 3 tables. Tables countries and users are normal tables. Table countries_users is the joining table that stores the relations between the records of countries and users.
The joining table shows that country ID 14 (Australia) has a relationship with user ID 7 (Foo). Country ID 12 (Armenia) has a relationship with user ID 8 (Baz).
Rules
- Every table must have a primary key named id.
- Normal tables must be named the lowercase, pluralised version of the object name. So for a user object of User, the table would be named users. For Country, it would be countries.
- A joining table must exist between each related normal tables, regardless of the type of relationship.
- Joining tables must be named with both of the table names it is joining, in alphabetical order, separated by an underscore (_). For example, the joining table for users and countries is countries_users.
- Joining tables must have a specially name id field for each of the tables it is joining, named as the singular of the table name, followed by an underscore (_) and the word id. For example, the joining id field name for table users would be user_id. The joining id field name for table countries would be country_id.
Special rules for Self Referencing Relationships
If you have a self referencing relationship (read Relationship Types for more information), the joining tables have a slightly different set of rules.
- Joining tables must be named with both of the model names it is joining, in lowercase alphabetical order, separated by an underscore (_). For example, if you have an employees table with models such as Manager and Supervisor both using employees as their table and having a relationship between each other, the joining table is managers_supervisors (the normal way would have been employees_employees which is too restrictive for self referenching relationships, as it would only allow one, and why the model names are used for this instead).
- Joining tables must have a specially name id field for each of the models it is joining, named as the lowercase singular of the model name, followed by an underscore (_) and the word id. For example, the joining id field name for model Manager would be manager_id. The joining id field name for model Supervisor would be supervisor_id.
Here's a example of self referencing tables:
employees
| id | first_name | last_name | position |
|---|---|---|---|
| 1 | Fred | Smith | Manager |
| 2 | Jayne | Doe | Supervisor |
| 3 | Joe | Public | Underling |
| 4 | Sam | Rogers | Underling |
managers_supervisors
| id | manager_id | supervisor_id |
|---|---|---|
| 1 | 1 | 2 |
supervisors_underlings
| id | supervisor_id | underling_id |
|---|---|---|
| 1 | 2 | 3 |
| 1 | 2 | 4 |
From the above, we can see that employees is a normal table and that managers_supervisors and supervisors_underlings are our self referencing joining tables. Looking at the data, we find:
Fred Smith is a Manager who manages Jayne Doe who is a Supervisor that supervises Joe Public and Sam Rogers (both Underlings).
That's pretty much it as far as your tables go. The setting to signify if tables are joined with a One to One, One to Many, or Many to Many relationship is setup in the DataMapper models.


Edward Cullen
Résumé
— For almost ninety years I’ve walked among my kind, and yours… all the time thinking I was complete in myself, not realizing what I was seeking. And not finding anything, because you weren’t alive yet. You are the only one who has ever touched my heart. It will always be yours…
*In case you want to catch the
Experience
Working Experience
-
My star career
I need a producer, 'cause I ain't getting any younger...
-
Twilight New Moon Eclipse Breaking Dawn: Part 1 Breaking Dawn: Part 2
-
What I've been through
-
1918
- In September, the Spanish influenza epidemic kills my parents; I was later saved and turned into a vampire by Carlisle, thus forming the Olympic coven.
-
2005
- March 18th - Bella Swan and I first meet at Forks High School.
- March 25th - Bella is saved by me in a near-fatal car crash.
-
2006
- March 19 - St. Marcus Day: I tried to reveal the existence of vampires in Volterra, Italy.
- June 13th - I proposed to Bella.
- August 13th - Me and Bella are married; during their honeymoon in Isle Esme, we conceived a daughter.
- September 11th - My daughter Renesmee is born.
- December 31 - The Cullens, along with our allies, confront the Volturi.
-
2007
- January 1st - Bella lowers her mental shield for the first time, allowing me to read her thoughts.
Personal life
It's my and Bella's lovestory, obviously 👄
-
Twilight
"And so the lion fell in love with the lamb."

"What a sick, masochistic lion."
―Bella and I realize our feelings for one another. -
Midnight Sun
In Midnight Sun, I describe how I became frustrated with my inability to read Bella's thoughts, my relentlessly overwhelming desire for her blood and my eventual discovery of love for her.
-
New Moon
"This is the last time you'll ever see me. I won't come back. And you can go on with your life without any interference from me. It'll be like I never existed, I promise."
―My goodbye to Bella. -
Eclipse
In the next few months, I visit Bella through curfew hours and then sneak into her room at night. When Eclipse begins, Bella receives a letter from Jacob, saying that he misses her too, but that it doesn't change anything. She is saddened by this, but I visit her, and her mood greatly improves.
-
Breaking Dawn
"How many times had I stared at Edward and marveled over his beauty? How many hours―days, weeks, of my life had I spent dreaming about what I then deemed to be perfection? I thought I'd known his face better than my own. I'd thought this was the one sure physical thing in my whole world: the flawlessness of Edward's face. I may as well have been blind. For the first time, with the dimming shadows and limiting weakness of humanity taken off my eyes, I saw his face. I gasped and then struggled to find the right words. I needed better words."
―Bella, upon seeing Edward for the first time after she became a vampire.
Languages
Skills
Likes😃
Dislikes😞
Wants🍯
Character
KIND PRINCE CHARMING POLITE PROTECTIVE A BIT STUBBORN, BUT LOVING GENTLEMAN


Another interesting block/inline hybrid is the value run-in, introduced in CSS2, which has the ability to take block-level elements and make them an inline part of a following element.
run-in


|
"I SLEUTH DEAD PEOPLE"
- NBC's MEDIUM
by Christine Alice Corcos
NBC has launched a new weekly
series from Glenn Gordon Caron featuring Patricia Arquette as
Allison Dubois, an Arizona housewife and former law office intern,
who claims to communicate with the dead. In the pilot, Allison's
husband Joe (Jake Weber) an aerospace engineer and skeptic, tries
to help her come to terms with her odd abilities. She is unhappy
with the way her life is developing. Approaching the ancient
age of thirty, she feels too old to go to law school, the original
plan, even though she has secured an internship at the local
DA's office, where they seem to like her, and where apparently
she can continue to work after she begins her law school career.
After Allison tells Joe about
her latest visions, which come to her in a disturbing dream,
he faxes an account of them to the Texas Rangers and they respond,
saying they'd like to talk to her. Apparently, her vision is
pretty close to a recent incident, and the Rangers think she
"knows something."
The major creative problems with Medium are that is the
writing and plotting are trite, and creator Caron leaves absolutely
no mystery about whether Allison will actually finger the guilty
party. Of course she will; she knows whodunit. That's the trouble
with having a psychic as your detective. Indeed, in an interview
with People magazine, the real-life Joe says, "When you're
married to a medium, you don't lie." Anyone who has seen
more than a few "psychic detective" or "medium"
movies or television shows know that the psychic, if s/he is
"genuine" is often disbelieved by the police, who think
she has inside information; thus s/he loses valuable time while
s/he establishes his or her bona fides. Real life psychic detectives
claim they undergo the same scrutiny.
In order to make Medium palatable, and interesting, to
the audience, developer Caron (Moonlighting) has to give
the television Allison many more powers than any real life psychic
could ever deliver. For one thing the tv Allison has the ability
to dream or picture very clear images. Real life psychic mediums
(and not all psychics claim to be mediums) almost never claim
to do so. Instead they tend to assert that their visions are
figurative, partial, and must be interpreted. In the episode
"Night of the Wolf" (aired January 24, 2005) Allison
actually picks up and comforts a little boy who materializes
as a physical being, and whom her six year old daughter can see
though he has been dead for five years. Until now we have not
seen either television or films make the claim that materialization
or "trance" mediums could do such a thing. John Edward,
James van Praagh, Sylvia Browne, and Rosemary Altea certainly
don't. Yet here is the fictionalized Allison Dubois touching,
holding a six year old ghost as material as her own daughter.
Ectoplasm went out with the trance mediums of the fifties, but
for purposes of Allison's credibility with the D.A.'s office
we need to see truly supernatural abilities on Allison's part.
As another medium tells Allison in the pilot, we need to see
that Allison is a rare medium indeed.
And credibility is the point. Prosecutor Manuel Devalos (Miguel
Sandoval) constantly bemoans the fact that he employs a psychic,
even as he exploits her talents. He hides her away in a broom
closet sized office, which she shares with a police sketch artist.
Devalos cautions her not to tell anyone precisely what kind of
consulting she does for him. That would spell doom, since he
would lose all bona fides with his staff, with the judges, with
the juries, with the press, with the public-it would certainly
be a disaster. Yet every episode thumps us over the head with
Allison's gifts, with her honesty, with her reliability, and
with her ability to come through in a crisis. Her visions are
dead on (sorry). Let's get some of those skeptical scientists
in from the local University to test her. In real life, the nearest
scientist available is Gary Schwartz, of the University of Arizona,
who has actually tested the real Allison DuBois and considers
her genuine. However, others who have examined the results of
his tests consider his protocols flawed, partly because of researcher
bias (see references, below).
In my own research into the work of psychics and trance mediums,
and their interactions with the law, I have yet to come across
contemporary practitioners who claim to have visions of nearly
the quality that the tv Allison has, especially when she is awake.
She talks to dead people constantly.
They have substance. Their messages are amazingly clear. If real
life mediums could deliver on such claims, they need never fear
fraud charges and we need never worry that our police departments
might hire them to solve cold cases. Indeed, we'd never have
cold cases at all. We'd never have mistaken verdicts. We'd never
have innocent people on death row. We might not need lawyers
or judges or courtrooms, or Innocence Projects. But, according
to the People magazine interview cited below, the Texas Rangers
refuse to "confirm they even worked with DuBois." Not
exactly a ringing endorsement. Compare the insights TV Allison
has with the ones People magazine quotes. TV Allison works with
spirits who appear in specific places who point her toward actual
clues. But according to that People magazine piece, when she
worked with the Texas Rangers, she described the suspect and
accomplices and predicted the body would be found within 5 years;
it was found 4 years and 10 months later. Many bodies do eventually
turn up, given enough time. Psychics aren't the only people able
to predict such eventualities.
The big legal roadblock Allison's employer has is finding an
independent source for some, if not all, of her clues. The need
for "proof", that is, real life evidence, as opposed
to what we see through Allison's eyes, once again holds the legal
system, the defense bar, and sometimes the protections of the
Constitution, up to ridicule. In one episode, DA Devalos tells
Allison that he can't get a search warrant based on her certain
knowledge that a witness is describing the wrong suspect. Of
course he is correct, but he goes ahead, obtains the search warrant,
citing an anonymous and completely fictitious informant (probably
trading on his own credibility with the local neutral and detached
magistrate), and the case proceeds to trial. The defense attorney
attacks Allison on the stand, since she is the person who provided
the information justifying the warrant. The attorney asks her
who was her "anonymous source", since she has only
been working in the DA's office a few months. How could she have
developed a trusting relationship with anyone to the extent that
that person would give her such information? In a low tone of
voice, Allison speaks a name from his past-the name of the person
he paid to take his bar exam for him. She blackmails him into
ceasing his line of questioning. Hooray! A victory for the saintly
prosecution and a defeat for the evil defense. The real killer
is eventually convicted, we assume. But the D.A. should never
have gotten his search warrant to begin with, and the defense
attorney was right to try to get the evidence suppressed. Is
this the message we really want to see promulgated? More bashing
of the Fourth Amendment? The heroine's blackmail of opposing
counsel? The prosecuting attorney's lies? Should psychics be
putting their gifts to use by any means possible for the ends
they identify? Are they the sole judges of what is best?
This problem is only one of the legal and policy issues I see
imbedded within Medium. Another is the active promotion
of the notion that tax money might profitably be spent on the
use of psychic detectives and psychic consultants on crime solving.
Might viewers, watching this show, be led to believe that psychics
could actually help the police solve crimes by visiting crime
scenes and handling evidence? Some current psychics claim to
do so and those claims are the basis for at least some of the
activities presented on this program. But law enforcement officials
who allow non-law enforcement trained personnel to participate
as Allison does are putting both the cases and their jobs at
risk. The fact is that few, if any, police departments actually
admit to using psychics. Most officials that psychics simply
waste time predicting that bodies or missing persons will be
found near water, or trees, or buildings with red roofs. Experienced
detectives combing particular areas, can do as well, and will
not raise false hopes among the families and friends of the victims.
Medium is moderately well-acted, adequately written and
will be around in Fall, 2005 for a second season. Its success
indicates psychic phenomena and magical thinking continues to
fascinate the U. S. public. I continue to despair.
References
Allison DuBois website
Encounters with the Paranormal
(Kendrick Frazier, ed., Prometheus Press, 1998).
Carla McClain, Varied
Readings on Arizona Psychic, Arizona Daily Star, January
17, 2005
Medium website
Gary Schwartz, The Afterlife
Experiments (2002).
Alex Tresniowski, Natasha Stoynoff,
and Rebecca Paley, She Sees Dead People, People, January 31,
2005 at 81.
Posted March 4, 2005
|


(2021-10-27 02:59:51 UTC)
# Packages matching: installed # Name # Installed # Synopsis base-bigarray base base-threads base base-unix base conf-findutils 1 Virtual package relying on findutils conf-gmp 3 Virtual package relying on a GMP lib system installation coq dev Formal proof management system dune 2.9.1 Fast, portable, and opinionated build system ocaml 4.12.0 The OCaml compiler (virtual package) ocaml-base-compiler 4.12.0 Official release 4.12.0 ocaml-config 2 OCaml Switch Configuration ocaml-options-vanilla 1 Ensure that OCaml is compiled with no special options enabled ocamlfind 1.9.1 A library manager for OCaml zarith 1.12 Implements arithmetic and logical operations over arbitrary-precision integers # opam file: opam-version: "2.0" maintainer<EMAIL_ADDRESS>homepage: "https://github.com/thery/coqprime" bug-reports: "https://github.com/thery/coqprime/issues" dev-repo: "git+https://github.com/thery/coqprime.git" license: "LGPL-2.1-only" authors: ["Laurent Théry"] build: [ [make "-j%{jobs}%"] ] install: [ [make "install"] ] depends: [ "ocaml" "coq" {>= "8.12~"} "coq-bignums" ] synopsis: "Certifying prime numbers in Coq" url { src: "https://github.com/thery/coqprime/archive/v8.12.zip" checksum: "md5=bb5bf2a2ed624fecd6701926d585a9a8" }
true
Dry install with the current Coq version:
opam install -y --show-action coq-coqprime.1.0.6 coq.dev
Dry install without Coq/switch base, to test if the problem was incompatibility with the current Coq/OCaml version:
true
opam list; echo; ulimit -Sv 4000000; timeout 4h opam install -y --deps-only coq-coqprime.1.0.6 coq.dev
opam list; echo; ulimit -Sv 16000000; timeout 4h opam install -y -v coq-coqprime.1.0.6 coq.dev
# Packages matching: installed # Name # Installed # Synopsis base-bigarray base base-threads base base-unix base conf-findutils 1 Virtual package relying on findutils conf-gmp 3 Virtual package relying on a GMP lib system installation coq dev Formal proof management system coq-bignums dev Bignums, the Coq library of arbitrary large numbers dune 2.9.1 Fast, portable, and opinionated build system ocaml 4.12.0 The OCaml compiler (virtual package) ocaml-base-compiler 4.12.0 Official release 4.12.0 ocaml-config 2 OCaml Switch Configuration ocaml-options-vanilla 1 Ensure that OCaml is compiled with no special options enabled ocamlfind 1.9.1 A library manager for OCaml zarith 1.12 Implements arithmetic and logical operations over arbitrary-precision integers [NOTE] Package coq is already installed (current version is dev). The following actions will be performed: - install coq-coqprime 1.0.6 <><> Gathering sources ><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Processing 1/1: [coq-coqprime.1.0.6: http] [coq-coqprime.1.0.6] downloaded from https://github.com/thery/coqprime/archive/v8.12.zip Processing 1/1: <><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><><><> Processing 1/2: [coq-coqprime: make] + /home/bench/.opam/opam-init/hooks/sandbox.sh "build" "make" "-j4" (CWD=/home/bench/.opam/ocaml-base-compiler.4.12.0/.opam-switch/build/coq-coqprime.1.0.6) - /home/bench/.opam/ocaml-base-compiler.4.12.0/bin//coq_makefile -f _CoqProject -o Makefile.coq - COQDEP VFILES - COQC src/Coqprime/Tactic/Tactic.v - COQC src/Coqprime/N/NatAux.v - COQC src/Coqprime/Z/ZCmisc.v - COQC src/Coqprime/Z/Zmod.v - COQC src/Coqprime/Z/Ppow.v - File "./src/Coqprime/Z/ZCmisc.v", line 31, characters 0-85: - Warning: The default value for rewriting hint locality is currently "local" - in a section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding rewriting hints outside of sections - without specifying an explicit locality attribute is therefore deprecated. It - is recommended to use "export" whenever possible. Use the attributes - #[local], #[global] and #[export] depending on your choice. For example: - "#[export] Hint Rewrite foo : bar." - [deprecated-hint-rewrite-without-locality,deprecated] - File "./src/Coqprime/Z/ZCmisc.v", line 46, characters 0-44: - Warning: The default value for rewriting hint locality is currently "local" - in a section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding rewriting hints outside of sections - without specifying an explicit locality attribute is therefore deprecated. It - is recommended to use "export" whenever possible. Use the attributes - #[local], #[global] and #[export] depending on your choice. For example: - "#[export] Hint Rewrite foo : bar." - [deprecated-hint-rewrite-without-locality,deprecated] - COQC src/Coqprime/num/Bits.v - COQC src/Coqprime/num/montgomery.v - COQC src/Coqprime/List/ListAux.v - COQC src/Coqprime/Z/ZCAux.v - =<PHONE_NUMBER> :: 343969132 :: 6812243 :: nil - : number - = 0 :: 1 :: nil - : number - =<PHONE_NUMBER>5897932384626433%Z - : Z - COQC src/Coqprime/Z/Pmod.v - COQC src/Coqprime/List/Permutation.v - File "./src/Coqprime/Z/ZCAux.v", line 188, characters 0-9: - Error: No product even after head-reduction. - - make[1]: *** [Makefile.coq:764: src/Coqprime/Z/ZCAux.vo] Error 1 - make[1]: *** Waiting for unfinished jobs.... - File "./src/Coqprime/List/Permutation.v", line 428, characters 0-37: - Warning: The default value for hint locality is currently "local" in a - section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding hints outside of sections without - specifying an explicit locality attribute is therefore deprecated. It is - recommended to use "export" whenever possible. Use the attributes #[local], - #[global] and #[export] depending on your choice. For example: "#[export] - Hint Unfold foo : bar." [deprecated-hint-without-locality,deprecated] - File "./src/Coqprime/List/Permutation.v", line 429, characters 0-37: - Warning: The default value for hint locality is currently "local" in a - section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding hints outside of sections without - specifying an explicit locality attribute is therefore deprecated. It is - recommended to use "export" whenever possible. Use the attributes #[local], - #[global] and #[export] depending on your choice. For example: "#[export] - Hint Unfold foo : bar." [deprecated-hint-without-locality,deprecated] - File "./src/Coqprime/List/Permutation.v", line 430, characters 0-41: - Warning: The default value for hint locality is currently "local" in a - section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding hints outside of sections without - specifying an explicit locality attribute is therefore deprecated. It is - recommended to use "export" whenever possible. Use the attributes #[local], - #[global] and #[export] depending on your choice. For example: "#[export] - Hint Unfold foo : bar." [deprecated-hint-without-locality,deprecated] - File "./src/Coqprime/List/Permutation.v", line 431, characters 0-41: - Warning: The default value for hint locality is currently "local" in a - section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding hints outside of sections without - specifying an explicit locality attribute is therefore deprecated. It is - recommended to use "export" whenever possible. Use the attributes #[local], - #[global] and #[export] depending on your choice. For example: "#[export] - Hint Unfold foo : bar." [deprecated-hint-without-locality,deprecated] - File "./src/Coqprime/List/Permutation.v", line 452, characters 0-36: - Warning: The default value for hint locality is currently "local" in a - section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding hints outside of sections without - specifying an explicit locality attribute is therefore deprecated. It is - recommended to use "export" whenever possible. Use the attributes #[local], - #[global] and #[export] depending on your choice. For example: "#[export] - Hint Unfold foo : bar." [deprecated-hint-without-locality,deprecated] - File "./src/Coqprime/Z/Pmod.v", line 505, characters 0-68: - Warning: The default value for rewriting hint locality is currently "local" - in a section and "global" otherwise, but is scheduled to change in a future - release. For the time being, adding rewriting hints outside of sections - without specifying an explicit locality attribute is therefore deprecated. It - is recommended to use "export" whenever possible. Use the attributes - #[local], #[global] and #[export] depending on your choice. For example: - "#[export] Hint Rewrite foo : bar." - [deprecated-hint-rewrite-without-locality,deprecated] - make: *** [Makefile.coq:387: all] Error 2 [ERROR] The compilation of coq-coqprime failed at "/home/bench/.opam/opam-init/hooks/sandbox.sh build make -j4". #=== ERROR while compiling coq-coqprime.1.0.6 =================================# # context 2.0.8 | linux/x86_64 | ocaml-base-compiler.4.12.0 | file:///home/bench/run/opam-coq-archive/released # path ~/.opam/ocaml-base-compiler.4.12.0/.opam-switch/build/coq-coqprime.1.0.6 # command ~/.opam/opam-init/hooks/sandbox.sh build make -j4 # exit-code 2 # env-file ~/.opam/log/coq-coqprime-1760-865888.env # output-file ~/.opam/log/coq-coqprime-1760-865888.out ### output ### # [...] # #[global] and #[export] depending on your choice. For example: "#[export] # Hint Unfold foo : bar." [deprecated-hint-without-locality,deprecated] # File "./src/Coqprime/Z/Pmod.v", line 505, characters 0-68: # Warning: The default value for rewriting hint locality is currently "local" # in a section and "global" otherwise, but is scheduled to change in a future # release. For the time being, adding rewriting hints outside of sections # without specifying an explicit locality attribute is therefore deprecated. It # is recommended to use "export" whenever possible. Use the attributes # #[local], #[global] and #[export] depending on your choice. For example: # "#[export] Hint Rewrite foo : bar." # [deprecated-hint-rewrite-without-locality,deprecated] # make: *** [Makefile.coq:387: all] Error 2 <><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> +- The following actions failed | - build coq-coqprime 1.0.6 +- - No changes have been performed # Run eval $(opam env) to update the current shell environment 'opam install -y -v coq-coqprime.1.0.6 coq.dev' failed.
No files were installed.
true


This type of chart isn't supported natively but is quite easy to achieve with two canvas tags that are positioned so that one is on top of the other (the HTML code for this is shown below).
The rear canvas draws the same Bar chart as the front one but without any data - so you can just see the grid.
The front canvas draws the Bar
chart - and then a custom draw
event uses the standard canvas clearRect()
function to return bits of the top canvas back to transparency. So
the grid on the rear canvas then shows through.
There's detailed information in the sample code that's shown below.
Because there's actually two canvas tags in use along with two RGraph objects, there are two
responsive()
definitions - one to resize the background grid and one to resize
the chart.
The responsive()
function on the background grid RGraph object just resizes the
canvas tag.
The responsive()
function on the other RGraph object changes the
marginInner
setting and moves the Y axis text up a little.
<script src="RGraph.common.core.js"></script> <script src="RGraph.bar.js"></script>Put this where you want the chart to show up:
<div style="padding: 15px; display: inline-block; position: relative; width: 600px; height: 250px; float: right"> <canvas id="cvs1" width="600" height="250" style="position:absolute; top: 0; left: 0">[No canvas support]</canvas> <canvas id="cvs2" width="600" height="250" style="position:absolute; top: 0; left: 0">[No canvas support]</canvas> </div>This is the code that generates the chart:


CHAPTER 225M
STATE PLANNING
Section
225M-1 Purpose
225M-2 Office of planning, establishment; responsibilities
225M-3 Cooperation
225M-4 Allocation of funds
225M-5 to 7 Repealed
Note
Carbon farming task force; report to 2023 and 2025 legislature (ceases to exist on June 30, 2025). L 2017, c 33.
State goal for affordable rental housing units; special action team (terminated December 31, 2019); annual report to 2017-2019 legislature. L 2016, c 127; L 2017, c 96, §2.