{% extends 'base.html' %} {% block header_content %}
Torch code for Grad-CAM is available here. Browsers currently supported by the demo: Google Chrome, Mozilla Firefox.
Guided Backprop
Grad-CAM
Guided Grad-CAM


This demo is reproduced from deeplearnjs's fast style tranfer demo originally developed by Reiichiro Nakano in typescript. Tested in Google Chrome.
Last Update: 2018-1-5
DeeplearnJS's Apache License


Genesis 44:11
Then they speedily took down every man his sack to the ground, and opened every man his sack.


FluidSlideDirection
public enum FluidSlideDirection : Int
Enumerations to determine a direction of a slide transition.
-
From top
Declaration
Swift
case fromTop
-
From bottom
Declaration
Swift
case fromBottom
-
From left
Declaration
Swift
case fromLeft
-
From right
Declaration
Swift
case fromRight
-
Undocumented
Declaration
Swift
var isFromTop: Bool { get }
-
Undocumented
Declaration
Swift
var isFromBottom: Bool { get }
-
Undocumented
Declaration
Swift
var isFromLeft: Bool { get }
-
Undocumented
Declaration
Swift
var isFromRight: Bool { get }
-
Undocumented
Declaration
Swift
var isFromVertical: Bool { get }
-
Undocumented
Declaration
Swift
var isFromHorizontal: Bool { get }
-
Declaration
Swift
public var description: String { get }


Articles
-
Night walk+Street Art
May 30, 2008
-
The "spatial" Jazz??
May 29, 2008
-
main Rome!
May 28, 2008
-
First day of course+walk around...
May 27, 2008
-
Last day+Rome
May 24, 2008
-
Regístrate y publica en LaKatxarraka.net
May 13, 2008
-
Rome'08
May 4, 2008


Today, in Ontario, there are over 1,500 people waiting for a lifesaving organ transplant. This is their only treatment option, and every 3 days someone will die because they did not get their transplant in time.
But you can help. When you register your consent for organ and tissue donation, you let those waiting know that you would help them if you could.
The need for organ donors in Ontario
Currently, around 1,600 people in Ontario are waiting for a life-saving organ transplant. And though most of us believe that organ donation is a good thing, just over a quarter of us are registered as donors. Some great strides have been made in Ontario over the past year, but still more needs to be done. You can Spread the Word by encouraging your friends and family to register their consent to become organ and tissue donors.
National Pediatric Transplant Week
This observance is a week at the end of National Donate Life Month that offers donation and transplantation organizations the platform to talk about the powerful message of ending the pediatric waiting list, to engage clinical partners to share their innovative work and patient stories (candidates and recipients), and to honor donor families whose children have saved and healed lives through organ, eye, and tissue donation.
Transplant Games
The Transplant Games are modeled after the Olympics and feature transplant recipients of all ages competing in various athletic events, illustrating the ability of transplantation to extend and enhance life. Athletes receive medals, and living donors and families of deceased donors are honored in special ceremonies for their life-enabling gifts. The National Kidney Foundation started the Games in 1990 and sponsored them every 2 years through 2010.
Read some amazing stories about people whose lives have been affected by organ donation and discover what a difference it can make.
Any information you provide will not be used for other commercial purposes and will not be sold, rented, leased or forwarded to any third party.


The staggeredFile plots wrapper uses a native binding to handle plots in a file with a parametric staggerSize value.
It is a basic implementation of the original file writer (address_offset_number_staggerSize
).
The scoops are stored in a file and are partially optimized in large chunks.
The chunks size is controlled by the staggerSize
parameter.
The plots writers created from this wrapper use a buffer with a length of staggerSize
plots to reorder the generated scoops.
Once the buffer is full, it is written to disk.
The plots readers created from this wrapper generates plotsNumber / staggerSize
input operations on the target disk.


Author:
James Clark (Thai Open Source Software Center<EMAIL_ADDRESS>Date:
2003-01-31
Copyright © 2003 Thai Open Source Software Center Ltd
The XML Namespaces Recommendation allows an XML document to be composed of elements and attributes from multiple independent namespaces. Each of these namespaces may have its own schema. The problem then arises of how the schemas can be composed in order to allow validation of the complete document.
In RELAX Namespace, Murata Makoto pioneered the idea of dividing the document into islands, with each island containing a single namespace, and validating each island separately against the schema for its namespace. RELAX Namespace formed the basis for the recently published Committee Draft of Document Schema Definition Languages (DSDL) -- Part 4: Selection of Validation Candidates.
This document presents a language named Modular Namespaces (MNS), which is an evolution of the ideas in RELAX Namespace and DSDL Part 4. RELAX Namespace was designed to work well with RELAX Core. RELAX Core cannot deal with documents that use multiple namespaces, nor does it provide any namespace-based wildcards. These limitations of RELAX Core are reflected in the design of RELAX Namespace. MNS is designed to be able to take advantage of more recent schema languages, such as RELAX NG, that are not limited in this way.
A sample implementation of MNS is included in Jing.
It is hoped that this will be a useful contribution to the future development of DSDL Part 4.
In its simplest form, a MNS schema consists of a mapping from namespace URIs to schema URIs. An MNS schema is written in XML. Here is a RELAX NG compact syntax schema for this simplest form of MNS schema:
default namespace = "http://www.thaiopensource.com/ns/mns" start = element rules { schemaType?, element validate { schemaType?, attribute ns { xsd:anyURI }, attribute schema { xsd:anyURI } }* } schemaType = attribute schemaType { mediaType } mediaType = xsd:string
Validity of an instance with respect to a MNS schema is determined as follows. First, a set of validation subjects is identified. Each validation subject is an element in the instance. Associated with each validation subject is a schema. If all the validation subjects are valid with respect to their associated schemas, then the instance is considered valid with respect to the MNS schema.
It is important to understand that when a validation subject is validated with respect to its schema, then it is validated along with all its descendants and attributes. One validation subject may have other validation subjects as ancestors. In this case, a validation subject will be validated with respect to more than one schema. Not only will it be validated with respect to its schema, but it will also be validated as part of validation of ancestor validation subjects with respect to their schemas.
An element is a validation subject if it has no parent or if its
namespace URI is different from that of its parent. A validation
subject must have a validate
rule for its namespace URI:
there must be a validate
element whose ns
attribute is the same as the validate subject's namespace URI. The
value of the ns
attribute of the validate
element can be the empty string to specify the absent namespace URI.
The associated schema is specified by the schema
attribute of the validate
element. The schema can be in
any language supported by the particular implementation. When the
schema is XML, the language of the schema is detected from the
namespace URI of the document element.
When the schema is not XML, then MNS relies on the MIME type
of the result of fetching the URI;
the schemaType
attribute can be used
to specify the MIME type explicitly. A MIME type of
application/x-rnc
can be used for RELAX NG compact
syntax. The schemaType
attribute on the
rules
element specifies the default value of of the
schemaType
on validate
element. Note that
the schema
attribute may refer to another MNS schema.
MNS has additional features that provide further control over the selection of validation subjects and their associated schemas.
Should it be possible to put the schema inline in the
MNS wrapped in, say, a schema
element? How does this
impact extensibility?
Should MNS have an include
element? The
ability to recursively reference MNS maybe makes this unnecessary.
Sometimes it may be desirable to allow elements from namespaces for
which there are no validate
rules. This can be done by
adding an empty lax
element to the rules
element:
default namespace = "http://www.thaiopensource.com/ns/mns" start = element rules { schemaType?, (validate* & lax?) } validate = element validate { schemaType?, attribute ns { xsd:anyURI }, attribute schema { xsd:anyURI } } lax = element lax { empty } schemaType = attribute schemaType { mediaType } mediaType = xsd:string
We will refer to an element that could be a validation subject if
there is an applicable validate
element as a
potential validation subject. In the absence of a
lax
element, there must be an applicable
validate
element for every potential validation subject;
with a lax
element, there need not be.
Attributes can also be validation subjects:
default namespace = "http://www.thaiopensource.com/ns/mns" start = element rules { schemaType?, (validate* & lax?) } validate = element validate|validateAttributes { schemaType?, attribute ns { xsd:anyURI }, attribute schema { xsd:anyURI } } lax = element lax { attribute allow { "attributes" | "elements" }? } schemaType = attribute schemaType { mediaType } mediaType = xsd:string
If an element has attributes that are namespace qualified with a
namespace URI other than the namespace URI of the element itself, then
the set of all attributes on that element with that namespace URI is a
potential validation subject. If there is a
validateAttributes
element for that namespace URI, then
it becomes a validation subject. The associated schema is specified
by the schema
attribute of the
validateAttributes
element. Unqualified attributes are
never validation subjects.
Lax processing for elements means that a potential validation
subject that is an element need not have an applicable
validate
element. Lax processing for attributes means
that a potential validation subject that is an attribute need not have
an applicable validateAttributes
element. In the absence
of a lax
element, neither attributes nor elements are
processed laxly. By default, the lax
element enables lax
processing for both elements and attributes. If
allow="attributes"
is specified, then lax processing is
enabled for attributes only; if allow="elements"
is
specified, then lax processing is enabled for elements only.
Normally, schema languages (including RELAX NG) validate an element
rather than a set of attributes. To work around this, MNS performs
parallel transformations on the set of attributes and on the schema.
The set of attributes is transformed by attaching the attributes to an
element with a particular namespace name and namespace URI. The schema
identified by a validateAttributes
element is transformed
to match. In the case of RELAX NG, when a
validateAttributes
element specifies a schema of
s
, MNS actually uses a schema of:
element * { external "s" }
By default, an element is a potential validation subject if its
namespace URI is different from its parent. This behavior can be
changed by adding one or more cover
children to
validate
elements. With the introduction of
cover
elements, the rule is that an element is a
potential validation subject if it is not
covered by an ancestor validation subject. Each validation
subject has a set of namespace URIs that it covers. A validation
subject always covers it own namespace URI. In addition, it covers
the namespace URIs specified by the cover
elements in its
validate
element. One obvious case where it is useful
for a schema to cover more than one namespace is when a
validate
refers recursively to an MNS schema.
default namespace = "http://www.thaiopensource.com/ns/mns" start = element rules { schemaType?, (validate* & lax?) } validate = element validate { validateModel, element cover { nsAtt }* } | element validateAttributes { validateModel } validateModel = nsAtt, attribute schema { xsd:anyURI }, schemaType? lax = element lax { attribute allow { "attributes" | "elements" }? } nsAtt = attribute ns { xsd:anyURI } schemaType = attribute schemaType { mediaType } mediaType = xsd:string
The set elements covered by a validation subject is determined from the set of namespace URI that it covers by the following two rules:
The rule for attributes is very similar. A set of attributes is a potential validation subject if and only if:
Just as with elements, an attribute is covered by an validation subject if its parent element and its namespace URI are covered by that validation subject.
Note that a validate
element is applicable to
a potential validation subject only if the namespace URI of the
potential validation subject is as specified by the ns
attribute. Any cover
child elements do not affect
this.
Should there be separate sets of namespaces that cover elements and cover attributes?
Should it be possible to cover all namespaces except a particular (possibly empty) finite set of namespaces?
The selection of validation subjects and associated schemas may need to be context dependent. For example, not all namespace URIs may be acceptable for the document element, or the document element may need to be validated against a different schema from that used for subtrees with the same namespace URI.
Context dependence is specified by means of modes.
default namespace = "http://www.thaiopensource.com/ns/mns" start = element rules { schemaType?, attribute startMode { mode }?, (validate|lax)* } validate = element validate { validateModel, attribute useMode { mode }?, element cover { nsAtt }* } | element validateAttributes { validateModel } lax = element lax { attribute allow { elementsOrAttributes }?, inModesAtt? } validateModel = nsAtt, attribute schema { xsd:anyURI }, inModesAtt?, schemaType? nsAtt = attribute ns { xsd:anyURI } schemaType = attribute schemaType { mediaType } mediaType = xsd:string inModesAtt = attribute inModes { list { mode+ } } mode = xsd:NCName | "#default" elementsOrAttributes = list { ("elements", "attributes") | ("attributes", "elements") | "elements" | "attributes" | empty }
The selection of validation subjects takes place with respect to a
named mode. A mode is named by an NCName. In addition, there is a
default mode named #default
. The
validate
and validateAttributes
elements have an optional inModes
attribute, which
specifies the modes in which the elements are applicable. The default
value of the inModes
attribute is the default mode. It is an
error if there is a mode and a namespace URI for which more than one
validate
or validateAttributes
element is applicable. Thus, when an element is selected as a
validation subject there is a unique applicable
validate
element.
The mode used to select whether a particular element or set of
attributes is a validation subject is specified by the
useMode
attribute of the validate
element applicable to the nearest ancestor validation subject. The
default value of the useMode
attribute is the default
mode. If an element or set of attributes has no ancestor validation
subject, then the mode used is determined by the
startMode
attribute on the rules
element;
the default value of the startMode
attribute is also the
default mode. Looking at this more procedurally, processing is
top-down; the starting mode is specified by the startMode
attribute. Within each validation subject element, processing
switches to the mode specified by the useMode
attribute.
Whether processing is lax also depends on the mode. The
lax
element has an inModes
attribute that
specifies the modes in which they apply. There can be multiple
lax
elements specifying lax processing for different
modes. As usual, the default value of the
inModes
attribute is the default mode.
For every mode named in a useMode
attribute other than
the default mode, there must be at least one validate
,
validateAttribute
or lax
element that
includes that mode in its inModes
attribute. For a mode
that allows nothing, either the default mode can be used or a
<lax allow="" inModes="m"/>
rule can be
added. The allowed value of the allow
attribute is, in
fact, a list of between zero and two distinct tokens from the set
elements
and attributes
.
We can distinguish between schemas that are open and
schemas that are closed. Open schemas allow attributes and
elements in other namespaces; closed schemas are not. Sometimes it is
necessary to treat a closed schema as open. This can be done by
adding a prune
attribute to validate
. This
has the effect of removing all potential validation candidates that
are elements or attributes from the subtree before validating the
subtree with respect to the schema specified by the
validate
, according as the value of the
prune
attribute contains the token elements
or attributes
.
attribute prune { elementsOrAttributes }?
Sometimes the processing mode to be used for an element may need to
depend on the name of the parent of that element. For example, we
might wish to allow elements of a particular namespace only within the
XHTML head
element and not anywhere else. To do this,
one or more context
elements are added to the
validate
element. The content of the
context
element identifies a context; the
useMode
attribute identifies a mode to be applied to
potential validation subjects in that context. The default value of
the useMode
attribute is the default mode as usual.
The context relates to the ancestry of the potential validation
subject starting with its parent element and continuing up and
including its nearest ancestor validation subject. The context
identified by a context
element is the union of the
contexts identified by each of its children. An element
element specifies a parent whose local name is equal to the value of
the name
attribute and whose namespace is equal to the
value of the ns
attribute. The namespace must the same as
that specified on the validate
element or one of its
cover
elements. The ns
attribute is
inherited and so it is unnecessary to specify it except when there are
cover
elements.
A context of the form:
<element name="x"> <element name="y"> <element name="z"/> </element> </element>
applies to a potential validation subject with a parent
z
, a grandparent y
and
a great grandparent x
. A context of the
form:
<root> <element name="x"/> </root>
applies to a potential validation subject with a parent element
x
such that that parent element is the nearest
ancestor validation subject of that potential validation subject.
The children of the context
elements of a particular
validate
element must all identify distinct contexts. It
is possible for a single potential validation subject to match
multiple distinct context children. A context child containing more
element
elements takes precedence over one containing
fewer element
elements. Amongst context children
containing the same number of element
elements, one that
has a root
element takes precedence over one that does
not.
default namespace = "http://www.thaiopensource.com/ns/mns" start = element rules { schemaType?, attribute startMode { mode }?, (validate|lax)* } validate = element validate { validateModel, useModeAtt?, attribute prune { elementsOrAttributes }?, element cover { nsAtt }*, context* } | element validateAttributes { validateModel } context = element context { useModeAtt?, nsAtt?, (rootContext|elementContext)+ } rootContext = element root { nsAtt?, elementContext } elementContext = element element { attribute name { xsd:NCName }, nsAtt?, elementContext? } lax = element lax { attribute allow { elementsOrAttributes }?, inModesAtt?, } validateModel = nsAtt, attribute schema { xsd:anyURI }, schemaType?, inModesAtt? nsAtt = attribute ns { xsd:anyURI } schemaType = attribute schemaType { mediaType } mediaType = xsd:string useModeAtt = attribute useMode { mode } inModesAtt = attribute inModes { list { mode+ } } mode = xsd:NCName | "#default" elementsOrAttributes = list { ("elements", "attributes") | ("attributes", "elements") | "elements" | "attributes" | empty }
Just as with RELAX NG, foreign elements and attributes can be added to MNS schemas. Thus, the complete MNS schema is as follows:
namespace local = "" default namespace mns = "http://www.thaiopensource.com/ns/mns" start = element rules { schemaType?, attribute startMode { mode }?, ((validate | lax)* & foreign) } validate = element validate { validateModel, useModeAtt?, attribute prune { elementsOrAttributes }?, ((cover*, context*) & foreign) } | element validateAttributes { validateModel, foreign } cover = element cover { nsAtt, foreign } context = element context { useModeAtt?, nsAtt?, ((rootContext|elementContext)+ & foreign) } rootContext = element root { nsAtt?, (elementContext & foreign) } elementContext = element element { nsAtt?, attribute name { xsd:NCName }, (elementContext? & foreign) } lax = element lax { attribute allow { elementsOrAttributes }?, inModesAtt?, foreign } validateModel = nsAtt, attribute schema { xsd:anyURI }, schemaType?, inModesAtt? nsAtt = attribute ns { xsd:anyURI } schemaType = attribute schemaType { mediaType } mediaType = xsd:string useModeAtt = attribute useMode { mode } inModesAtt = attribute inModes { list { mode+ } } mode = xsd:NCName | "#default" elementsOrAttributes = list { ("elements", "attributes") | ("attributes", "elements") | "elements" | "attributes" | empty } foreign = (attribute * - (mns:* | local:*) { text } | element * - mns:* { anything })* anything = (text | attribute * { text } | element * { anything })*
Suppose we want to validate an XHTML document that uses RDF within its
head
element. The following would do the job:
<rules xmlns="http://www.thaiopensource.com/ns/mns" startMode="xhtml"> <validate ns="http://www.w3.org/1999/02/22-rdf-syntax-ns#" schema="rdfxml.rng" inModes="rdf" useMode="anything"/> <validate ns="http://www.w3.org/1999/xhtml" schema="xhtml.rng" inModes="xhtml" prune="elements"> <context useMode="rdf"> <element name="head"/> </context> </validate> <lax inModes="anything"/> </rules>
Note the following points:
head
element. We
therefore specify an appropriate context in the
validation
element for the XHTML namespace.useMode
attribute on the
validate
element for the XHTML, the useMode
attribute will default to the default mode. Since none of our rules
apply in the default mode, the default mode will not allow
anything.anything
mode, for which processing is lax and which does
not have any validate
or
validateAttributes
rules.W3C XML Schema (XSD) includes features for namespace modulariy that are similar in some ways to MNS. Like MNS, XSD validation uses a mapping from namespace URIs to schemas. However, there are important differences.
xsi:schemaLocation
attributes in the instance, or it may
be supplied by the user. With MNS, the mapping is explicit and
implementation independent.


Woops! This interactive will not work for you
Looks like you are using Windows XP or older and an older version of Internet Explorer.
We recommend you use if you are using Windows XP or below, please activate Google
Chrome Frame (below), which will be a wonderful addition to your browser and enable
you to use this interactive.
Please restart your browser when download is complete.
You may also use one of these other great, updated and secure browsers!
PLEASE UPDATE YOUR BROWSER:
WOOPS! It looks like you are using an older version of Internet Explorer. (Internet Explorer 7 or Internet Explorer 8)
This interactive will not work for you.
Please upgrade to a more modern and secure browser. Browsers like Internet Explorer 9, Firefox or Google Chrome


This page shows the status of services available to the MIT community.
General services: OK
The IS&T Help Desk phones are back in full operation. We apologize to anyone... more... (2/14 13:42:12)
Network: OK
The network is operating normally. (1/30 18:56:14)
E-mail: Warning
***IMPORTANT*** Do *NOT* Reply to a message telling you that you need to... more... (2/14 07:19:34)
Telephone service: OK
The network is operating normally. (1/30 18:56:14)
Academic services: Alert
The AFS fileserver aegisthus crashed and automatically restarted at 3:42am... more... (2/15 07:33:57)
Library services: OK
The network is operating normally. (1/8 11:58:59)
Administrative services: Critical
All Admissions applications (admissions.mit.edu and startgate.mit.edu)... more... (2/15 11:17:21)
Report phone/cable outage
(617-253-4357)
Report other problems
(617-253-1101)
Campus emergency information
3DOWN Help


SEM images of the as-prepared powders prepared from the spray solutions without and with dextrin: (a) without dextrin and (b) with dextrin.
Figure 1
SEM, TEM, and elemental mapping images of the ZnFe 2O 4 powders post-treated at various temperatures: (a) without dextrin, 450°C, (b) with dextrin, 350°C, (c) with dextrin, 400°C, (d–f) with dextrin, 450°C, and (g) elemental mapping images.
Figure 2
Electrochemical properties of the ZnFe 2O 4 powders prepared from the spray solutions with and without dextrin: (a) initial charge and discharge curves, (b) cyclic voltammogram curves, and (c) cycling performances at a current density of 500 mA g −1.
Figure 3
Impedance analysis of the ZnFe 2O 4 powders prepared from the spray solutions with and without dextrin: (a) Nyquist impedance plots before cycle, (b) Nyquist impedance plots after 50 cycles, and (c) relationship between Z re and ω −1/2 in the low-frequency region.


Particulate Matter in Los Angeles
What are some observations of particulate matter that have been made in LA?
{% for value in filtered %}
{{value}}
{% endfor %}


Note: The correct solution is obviously a dumb way to do it. This exercise is merely trying to give an example of a Parson's puzzle with js-parsons, not teach you Python :)
New instance Get feedback Save progess


Events - Hunger for Salt Book Tour
June 2, 2017 @5:00-7:00pm
Launch Party and Book Signing
Full Circle Studio
113 Herman Melville Ave.
Newport News, VA 23606
www.fullcirclestudio.com
June 8, 2017 @7:00pm
Why There Are Words Reading Series
Studio 333
333 Caledonia St.
Sausalito, CA
www.whytherearewords.com
June 27, 2017 @7:00pm
Eastern Shore Reading:
Elaine Fletcher Chapman and Alex Joyner
10 Langley Rd.
Newton Center
Newton, MA 02459
www.newtonvillebooks.com
July 7, 2017 @7:00pm
Eastern Shore Reading:
Elaine Fletcher Chapman and Alex Joyner
Kerr Place
69 Market Street
Onancock, VA 23417
www.shorehistory.org/ker-place
July 15, 2017 @3:00pm
The Writer’s Studio Reading Series
with Elaine Fletcher Chapman, Renee Olander, Tracy Rice Weber, Julie Walls, Joanne Hunter
Prince Books
Corner of Main and Martins Lane
Norfolk, VA
www.prince-books.com
September 25, 2107 @7:00pm
Bennington Writers
Cornelia Street Café
Corner of Main and Martins Lane
NYC, NYC
www.corneliastreetcafe.com/


Manage nodes in a swarm
Estimated reading time: 7 minutesAs part of the swarm management lifecycle, you may need to view or update a node as follows:
List nodes
To view a list of nodes in the swarm run docker node ls
from a manager node:
$ docker node ls
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS
46aqrk4e473hjbt745z53cr3t node-5 Ready Active Reachable
61pi3d91s0w3b90ijw3deeb2q node-4 Ready Active Reachable
a5b2m3oghd48m8eu391pefq5u node-3 Ready Active
e7p8btxeu3ioshyuj6lxiv6g0 node-2 Ready Active
ehkv3bcimagdese79dn78otj5 * node-1 Ready Active Leader
The AVAILABILITY
column shows whether or not the scheduler can assign tasks to
the node:
Active
means that the scheduler can assign tasks to the node.Pause
means the scheduler doesn’t assign new tasks to the node, but existing tasks remain running.Drain
means the scheduler doesn’t assign new tasks to the node. The scheduler shuts down any existing tasks and schedules them on an available node.
The MANAGER STATUS
column shows node participation in the Raft consensus:
- No value indicates a worker node that does not participate in swarm management.
Leader
means the node is the primary manager node that makes all swarm management and orchestration decisions for the swarm.Reachable
means the node is a manager node participating in the Raft consensus quorum. If the leader node becomes unavailable, the node is eligible for election as the new leader.Unavailable
means the node is a manager that can’t communicate with other managers. If a manager node becomes unavailable, you should either join a new manager node to the swarm or promote a worker node to be a manager.
For more information on swarm administration refer to the Swarm administration guide.
Inspect an individual node
You can run docker node inspect <NODE-ID>
on a manager node to view the
details for an individual node. The output defaults to JSON format, but you can
pass the --pretty
flag to print the results in human-readable format. For example:
$ docker node inspect self --pretty
ID: ehkv3bcimagdese79dn78otj5
Hostname: node-1
Joined at: 2016-06-16 22:52:44.9910662 +0000 utc
Status:
State: Ready
Availability: Active
Manager Status:
Address: <IP_ADDRESS>:2377
Raft Status: Reachable
Leader: Yes
Platform:
Operating System: linux
Architecture: x86_64
Resources:
CPUs: 2
Memory: 1.954 GiB
Plugins:
Network: overlay, host, bridge, overlay, null
Volume: local
Engine Version: 1.12.0-dev
Update a node
You can modify node attributes as follows:
Change node availability
Changing node availability lets you:
- drain a manager node so that only performs swarm management tasks and is unavailable for task assignment.
- drain a node so you can take it down for maintenance.
- pause a node so it can’t receive new tasks.
- restore unavailable or paused nodes available status.
For example, to change a manager node to Drain
availability:
$ docker node update --availability drain node-1
node-1
See list nodes for descriptions of the different availability options.
Add or remove label metadata
Node labels provide a flexible method of node organization. You can also use node labels in service constraints. Apply constraints when you create a service to limit the nodes where the scheduler assigns tasks for the service.
Run docker node update --label-add
on a manager node to add label metadata to
a node. The --label-add
flag supports either a <key>
or a <key>=<value>
pair.
Pass the --label-add
flag once for each node label you want to add:
$ docker node update --label-add foo --label-add bar=baz node-1
node-1
The labels you set for nodes using docker node update apply only to the node entity within the swarm. Do not confuse them with the docker daemon labels for dockerd.
Therefore, node labels can be used to limit critical tasks to nodes that meet certain requirements. For example, schedule only on machines where special workloads should be run, such as machines that meet PCI-SS compliance.
A compromised worker could not compromise these special workloads because it cannot change node labels.
Engine labels, however, are still useful because some features that do not affect secure orchestration of containers might be better off set in a decentralized manner. For instance, an engine could have a label to indicate that it has a certain type of disk device, which may not be relevant to security directly. These labels are more easily “trusted” by the swarm orchestrator.
Refer to the docker service create
CLI reference
for more information about service constraints.
Promote or demote a node
You can promote a worker node to the manager role. This is useful when a manager node becomes unavailable or if you want to take a manager offline for maintenance. Similarly, you can demote a manager node to the worker role.
Note: Regardless of your reason to promote or demote a node, you must always maintain a quorum of manager nodes in the swarm. For more information refer to the Swarm administration guide.
To promote a node or set of nodes, run docker node promote
from a manager
node:
$ docker node promote node-3 node-2
Node node-3 promoted to a manager in the swarm.
Node node-2 promoted to a manager in the swarm.
To demote a node or set of nodes, run docker node demote
from a manager node:
$ docker node demote node-3 node-2
Manager node-3 demoted in the swarm.
Manager node-2 demoted in the swarm.
docker node promote
and docker node demote
are convenience commands for
docker node update --role manager
and docker node update --role worker
respectively.
Install plugins on swarm nodes
If your swarm service relies on one or more
plugins, these plugins need to be available on
every node where the service could potentially be deployed. You can manually
install the plugin on each node or script the installation. In Docker 17.07 and
higher, you can also deploy the plugin in a similar way as a global service
using the Docker API, by specifying a PluginSpec
instead of a ContainerSpec
.
Note: There is currently no way to deploy a plugin to a swarm using the Docker CLI or Docker Compose. In addition, it is not possible to install plugins from a private repository.
The PluginSpec
is defined by the plugin developer. To add the plugin to all Docker nodes, use
the service/create
API, passing
the PluginSpec
JSON defined in the TaskTemplate
.
Leave the swarm
Run the docker swarm leave
command on a node to remove it from the swarm.
For example to leave the swarm on a worker node:
$ docker swarm leave
Node left the swarm.
When a node leaves the swarm, the Docker Engine stops running in swarm mode. The orchestrator no longer schedules tasks to the node.
If the node is a manager node, you receive a warning about maintaining the
quorum. To override the warning, pass the --force
flag. If the last manager
node leaves the swarm, the swarm becomes unavailable requiring you to take
disaster recovery measures.
For information about maintaining a quorum and disaster recovery, refer to the Swarm administration guide.
After a node leaves the swarm, you can run the docker node rm
command on a
manager node to remove the node from the node list.
For instance:
$ docker node rm node-2


VICTIM SUPPORT
Scots criminals forced to pay towards victim support in bid to help victims move on with their lives
by Conor RiordanCRIMINALS across Scotland will be forced to support their victims to 'move on with their lives', according to Justice Secretary Humza Yousaf.
The new financial penalty will be imposed on crimes which take place as of Monday, seeking to make thugs contribute to the cost of supporting victims.
It imposed on all offenders who are sentenced to pay a court fine, with the money going to the Victim Surcharge Fund.
This fine will be levied on top of Scottish Court fines, and the money raised will be accessible by organisations who seek to help victims.
Payments from the fund will begin being made in six to 12 months' time.
According to the Scotsman, under the plan, victim surcharges would range from £10 on fines up to £200, to £350 on fines between £5,000.01 and £10,000, while court-ordered fines of more than £10,000 would incur a charge of £7.5 per cent of the fine.
Justice Secretary Humza Yousaf stressed the importance of the victim in receiving support and aid to get back on their feet after an ordeal.
He said: "Experiencing crime can be an isolating and frightening experience and we are committed to improving the experiences of victims in our justice system.
"It's only right that criminals should pay towards helping victims to recover and move on with their lives.
"The money raised through the surcharge will pay for practical support that will make a real difference to victims and their families.
"While Scotland's long-term fall in crime means fewer people fall prey to criminals, we are continuing to invest £18 million annually to improve support, advice and information for victims.
"This new fund will be a valuable addition to support available.
"Over the coming year, we will also be carrying out further work to better understand where the gaps are in how Scotland supports victims and witnesses."
The new policy was passed by the Scottish Parliament in early September.
The Liberal Democrats had raised concerns and outrage at the lengthy time it took to introduce the anew charges.


Applies an R function to a Spark object (typically, a Spark DataFrame).
spark_apply( x, f, columns = NULL, memory = TRUE, group_by = NULL, packages = NULL, context = NULL, name = NULL, barrier = NULL, fetch_result_as_sdf = TRUE, partition_index_param = "", arrow_max_records_per_batch = NULL, auto_deps = FALSE, ... )
| x | An object (usually a |
|---|---|
| f | A function that transforms a data frame partition into a data frame.
The function Can also be an |
| columns | A vector of column names or a named vector of column types for
the transformed object. When not specified, a sample of 10 rows is taken to
infer out the output columns automatically, to avoid this performance penalty,
specify the column types. The sample size is configurable using the
|
| memory | Boolean; should the table be cached into memory? |
| group_by | Column name used to group by data frame partitions. |
| packages | Boolean to distribute Defaults to For clusters using Yarn cluster mode, For offline clusters where For clusters where R packages already installed in every worker node,
the |
| context | Optional object to be serialized and passed back to |
| name | Optional table name while registering the resulting data frame. |
| barrier | Optional to support Barrier Execution Mode in the scheduler. |
| fetch_result_as_sdf | Whether to return the transformed results in a Spark
Dataframe (defaults to NOTE: |
| partition_index_param | Optional if non-empty, then NOTE: when |
| arrow_max_records_per_batch | Maximum size of each Arrow record batch, ignored if Arrow serialization is not enabled. |
| auto_deps | [Experimental] Whether to infer all required R packages by
examining the closure |
| ... | Optional arguments; currently unused. |
spark_config()
settings can be specified to change the workers
environment.
For instance, to set additional environment variables to each
worker node use the sparklyr.apply.env.*
config, to launch workers
without --vanilla
use sparklyr.apply.options.vanilla
set to
FALSE
, to run a custom script before launching Rscript use
sparklyr.apply.options.rscript.before
.
if (FALSE) { library(sparklyr) sc <- spark_connect(master = "local[3]") # creates an Spark data frame with 10 elements then multiply times 10 in R sdf_len(sc, 10) %>% spark_apply(function(df) df * 10) # using barrier mode sdf_len(sc, 3, repartition = 3) %>% spark_apply(nrow, barrier = TRUE, columns = c(id = "integer")) %>% collect() }


curl_init
(PHP 4 >= 4.0.2, PHP 5, PHP 7)
curl_init — 初始化一个cURL会话
说明
resource curl_init ([ string $url = NULL ] )
初始化一个新的会话，返回一个cURL句柄，供curl_setopt(), curl_exec()和curl_close
() 函数使用。
参数
url
如果提供了该参数，CURLOPT_URL 选项将会被设置成这个值。你也可以使用
curl_setopt()函数手动地设置这个值。
返回值
如果成功，返回一个cURL句柄，出错返回 FALSE。
范例
Example #1 初始化一个新的cURL会话并获取一个网页
参见
• curl_close() - 关闭一个cURL会话
• curl_multi_init() - 返回一个新cURL批处理句柄
User Contributed Notes 9 notes
===============================================================================
Just to clarify:
Spaces in the URL need to be replaced with a %20.
Spaces in the querystring need to be replaced with a +
===============================================================================
Regarding spaces in URLs;
Please read
http://php.net/manual/en/function.urlencode.php
===============================================================================
curl_init() has undefined behavior if you pass 'false' to it and can crash when
you try to copy the resulting handle using curl_copy_handle(). Keep this in
mind if you create a wrapper object for CURL.
===============================================================================
Curl_init as well as CURLOPT_URL don't like to have static strings as
parameter.
I came across this by accident and it took me very long to find out. curl_exec
will throw error 3 (Malformed) and you tipple check the URL in it's variable
only to find by trial and error that it's declaration is the culprit.
So never do this:
static $someurl = "http://www.example.com/interfacce.php";
....
$ch=curl_init($someurl);
....
$return=curl_exec($ch);
Cheers
===============================================================================
For some reason on some webservers it may not be able to understand what cURL
is doing. If you're getting unexpected results (like getting no output when the
URL is valid) while using curl_init(). Add a trailing slash '/' after the url
if you haven't done so already.
===============================================================================
e.g. you can check how many characters are on test_1.php
or you can it use for more, i have used this function for a nagios check.
" ;
if ($load == 1){
function webcheck ($url) {
$ch = curl_init ($url) ;
curl_setopt ($ch, CURLOPT_RETURNTRANSFER, 1) ;
$res = curl_exec ($ch) ;
curl_close ($ch) ;
return ($res) ;
}
echo "url = $url
" ;
$erg = webcheck("my_page.php/test_1.php") ;
$zahl = strlen ($erg) ;
echo "length = $zahl " ;
?>
===============================================================================
Bu kodlar http://gencbilgin.net/curl-kutuphanesi-ve-kullanimi.html adresinden
alınmıştır...
===============================================================================
Here you have a function that I use to get the content of a URL using cURL:
function getUrlContent($url){
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_USERAGENT, 'Mozilla/4.0 (compatible; MSIE 6.0; Windows
NT 5.1; .NET CLR 1.1.4322)');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 5);
curl_setopt($ch, CURLOPT_TIMEOUT, 5);
$data = curl_exec($ch);
$httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
return ($httpcode>=200 && $httpcode<300) ? $data : false;
}
The source comes from this website:
http://softontherocks.blogspot.com/2014/11/
descargar-el-contenido-de-una-url.html
===============================================================================
... And the text file stand in the server in the same folder that the script.
This is the function code.-
';
echo 'Average speed download == ' . $sAverageSpeedDownload . '
';
echo 'Average Speed upload == ' . $sAverageSpeedUpload . '
';
echo '
';
$aCURLinfo = curl_getInfo( $sh );
print_r( $aCURLinfo );
echo '';
curl_close( $sh );
FClose ( $hFile );
echo '(See the file "'.$sTxtfile.'" in the same path of the hosting'.
' to where this script PHP).
';
}
?>


Commentality is not a commenting system, but it does keep your audience engaged and it does measure public opinion.
manipulating public opinion
measuring public opinion
hatred and intolerance
safe space
advertisers
people
third party trackers
fast web
Commentality is now in private beta.
If you want to give it a try on your website, drop us a line!
Thank you for your message, it will be processed by a faulty human, but we will definitely get back to you.


--- ---
Dear Attendees,
Register for the Zoom Webinar at 1pm on June 19th: https://ucla.zoom.us/webinar/register/WN_dlX3cldoQwe0kcm0UwW1Tw
UCLA PhD Students helping to coordinate include Pradyumna Chari and Yunhao Ba. Thank you and look forward to seeing you on zoom!
--- the organizers
Abstract: The early days of computer vision used "physics-inspired algorithms" to detect contours, edges, faces, and other features. Over the past decade, these structured algorithms have been superseded by deep learning algorithms with superior performance. This tutorial discusses an increasingly popular class of hybrid methods that blend physics and learning. In a unique virtual format, we feature 5 faculty members who provide a joint opening panel and closing panel, with a flipped classroom style reading group in the middle break. A happy hour will conclude the tutorial.
Visual Physics: Discovering Physical Laws from Videos
Phase-Based Video Motion Processing
Turning Corners into Cameras: Principles and Methods
Physics-Based Learned Design: Optimized Coded-Illumination for Quantitative Phase Imaging
Learning Spatial Common Sense with Geometry-Aware Recurrent Networks
Training Image Estimators without Image Ground-Truth
Learning visual predictive models of physics for playing billiard
Use the Force, Luke! Learning to Predict Physical Forces by Simulating Effects
A theory of fermat paths for non-line-of-sight shape reconstruction
TossingBot: Learning to Throw Arbitrary Objects with Residual Physics
Interaction networks for learning about objects, relations and physics
Learning Spatial Common Sense with Geometry-Aware Recurrent Networks
Learning from Unlabelled Videos Using Contrastive Predictive Neural 3D Mapping
Auto-Tuning Structured Light by Optical Stochastic Gradient Descent
How to Do Physics-based Learning
Integrating Physics-Based Modeling with Machine Learning: A Survey
Heavy Rain Image Restoration: Integrating Physics Model and Conditional Adversarial Learning
AI Feynman: A physics-inspired method for symbolic regression
Integration of Neural Network-Based Symbolic Regression in Deep Learning for Scientific Discovery
Discovering Symbolic Models from Deep Learning with Inductive Biases
Learning Topology From Synthetic Data for Unsupervised Depth Completion
Blending Diverse Physicsl Priors With Neural Networks
Learning From Synthetic Data: Addressing Domain Shift for Semantic Segmentation


Appearance
It resembles a medium-sized bird covered in white fluff. It has a crest similar to its earlier forms of Togepi and Togetics, with blue and red feathers. There are two legs that are close together. Spots are located along the chest, resembling small red and blue triangles, similar to those that were before evolution. Its general shape resembles a flying wing of an airplane.


Presentations
- Green Light Year presentation, 2021
- FECO on biodiversity, 2020
- Leaving WCMC, 2020
- ProtectedPlaent, esri UK conference, 2019
- IBAT Governance meeting Dec, 2018
- Jupyter notebook is great, 2018
- IBAT Governance meeting Sep, 2018
- IBAT redevelopment-beta, 2018
- IBAT redevelopment, 2018
- Digital belt and road training workshop on space technologies and World Heritage, Beijing, China, 2017
- Yichuan's work, for WCMC's informatics programme, Cambridge, UK, 2017
- World Heritage Analyses Launch, Krakow, Poland, 2017
- Guest lecture on data analysis - Birkbeck College, London, UK, 2017
- Introduction: Knowledge Lab for World Heritage, Gland, Switzerland, 2016
- Discussion on the effect of buffered points in the calculation of PA coverage, Cambridge, UK, 2016
- Introduction on World Heritage for high school students, Cambridge, UK, 2016


Reg ex example
Username
password must contain at least 1 capital and 1 lower letter and 1 digit
Password
password must contain at least 1 capital and 1 lower letter and 1 digit
Password confirmation


Functions | |
| int MITAB_STDCALL | mitab_c_getlibversion () |
| Returns the version of the library. | |
| int MITAB_STDCALL | mitab_c_getlasterrorno () |
| Fetch the last error number. | |
| const char *MITAB_STDCALL | mitab_c_getlasterrormsg () |
| Get the last error message. | |
| int MITAB_STDCALL | mitab_c_getlasterrormsg_vb (char *errormsg, int l) |
| Get the last error message (VB Version). | |
| mitab_handle MITAB_STDCALL | mitab_c_open (const char *pszFilename) |
| Open an existing .TAB or .MIF dataset for read access. | |
| void MITAB_STDCALL | mitab_c_close (mitab_handle handle) |
| Close a dataset previously opened using mitab_c_open() or created using mitab_c_create(). | |
| mitab_handle MITAB_STDCALL | mitab_c_create (const char *filename, const char *mif_or_tab, const char *mif_projection, double north, double south, double east, double west) |
| Create a new .TAB or .MIF dataset. | |
| int MITAB_STDCALL | mitab_c_add_field (mitab_handle dataset, const char *field_name, int field_type, int width, int precision, int indexed, int unique) |
| Add a new field to the dataset's schema. | |
| void MITAB_STDCALL | mitab_c_destroy_feature (mitab_feature feature) |
| Destroy a mitab_feature object and release all memory associated with it. | |
| int MITAB_STDCALL | mitab_c_next_feature_id (mitab_handle handle, int last_feature_id) |
| Iterator to get the next valid feature id when reading a dataset opened with mitab_c_open(). | |
| mitab_feature MITAB_STDCALL | mitab_c_read_feature (mitab_handle handle, int feature_id) |
| Read a mitab_feature object from the file. | |
| int MITAB_STDCALL | mitab_c_write_feature (mitab_handle handle, mitab_feature feature) |
| Write a new feature to a dataset. | |
| mitab_feature MITAB_STDCALL | mitab_c_create_feature (mitab_handle handle, int feature_type) |
| Create a new mitab_feature object to be written to a dataset created using mitab_c_create(). | |
| void MITAB_STDCALL | mitab_c_set_field (mitab_feature feature, int field_index, const char *field_value) |
| Set the value of specified field in a feature object. | |
| void MITAB_STDCALL | mitab_c_set_points (mitab_feature feature, int part, int vertex_count, double *x, double *y) |
| Set the feature's coordinates. | |
| void MITAB_STDCALL | mitab_c_set_arc (mitab_feature feature, double center_x, double center_y, double x_radius, double y_radius, double start_angle, double end_angle) |
| Set an arc or ellipse feature parameters. | |
| void MITAB_STDCALL | mitab_c_set_text (mitab_feature feature, const char *text) |
| Set the text string on a TABFC_Text object. | |
| const char *MITAB_STDCALL | mitab_c_get_text (mitab_feature feature) |
| Get the text string on a TABFC_Text object. | |
| int MITAB_STDCALL | mitab_c_get_text_vb (mitab_feature feature, char *text, int l) |
| Get the text string on a TABFC_Text object (VB Version). | |
| void MITAB_STDCALL | mitab_c_set_text_display (mitab_feature feature, double angle, double height, double width, int fg_color, int bg_color, int justification, int spacing, int linetype) |
| Set a TABFC_Text object's display properties. | |
| double MITAB_STDCALL | mitab_c_get_text_angle (mitab_feature feature) |
| Fetch a TABFC_Text object's angle property. | |
| double MITAB_STDCALL | mitab_c_get_text_height (mitab_feature feature) |
| Fetch a TABFC_Text object's MBR height property. | |
| double MITAB_STDCALL | mitab_c_get_text_width (mitab_feature feature) |
| Fetch a TABFC_Text object's MBR width property. | |
| int MITAB_STDCALL | mitab_c_get_text_fgcolor (mitab_feature feature) |
| Fetch a TABFC_Text object's foreground color property. | |
| int MITAB_STDCALL | mitab_c_get_text_bgcolor (mitab_feature feature) |
| Fetch a TABFC_Text object's background color property. | |
| int MITAB_STDCALL | mitab_c_get_text_justification (mitab_feature feature) |
| Fetch a TABFC_Text object's justification property. | |
| int MITAB_STDCALL | mitab_c_get_text_spacing (mitab_feature feature) |
| Fetch a TABFC_Text object's spacing property. | |
| int MITAB_STDCALL | mitab_c_get_text_linetype (mitab_feature feature) |
| Fetch a TABFC_Text object's linetype property. | |
| void MITAB_STDCALL | mitab_c_set_font (mitab_feature feature, const char *fontname) |
| Set the font name in a a TABFC_Text or TABFC_FontPoint object, or set the symbol name in a TABFC_CustomPoint. | |
| const char *MITAB_STDCALL | mitab_c_get_font (mitab_feature feature) |
| Get the font name from a TABFC_Text or TABFC_FontPoint object, or the symbol name from a TABFC_CustomPoint. | |
| int MITAB_STDCALL | mitab_c_get_font_vb (mitab_feature feature, char *font, int l) |
| Get the font name from a TABFC_Text or TABFC_FontPoint object, or the symbol name from a TABFC_CustomPoint. | |
| void MITAB_STDCALL | mitab_c_set_brush (mitab_feature feature, int fg_color, int bg_color, int pattern, int transparent) |
| Set an object's brush properties. | |
| int MITAB_STDCALL | mitab_c_get_brush_fgcolor (mitab_feature feature) |
| Get an object's brush foreground color property. | |
| int MITAB_STDCALL | mitab_c_get_brush_bgcolor (mitab_feature feature) |
| Get an object's brush background color property. | |
| int MITAB_STDCALL | mitab_c_get_brush_pattern (mitab_feature feature) |
| Get an object's brush pattern property. | |
| int MITAB_STDCALL | mitab_c_get_brush_transparent (mitab_feature feature) |
| Get an object's brush transparency property. | |
| void MITAB_STDCALL | mitab_c_set_pen (mitab_feature feature, int width, int pattern, int color) |
| Set an object's pen properties. | |
| int MITAB_STDCALL | mitab_c_get_pen_color (mitab_feature feature) |
| Get an object's pen color property. | |
| int MITAB_STDCALL | mitab_c_get_pen_width (mitab_feature feature) |
| Get an object's pen width property. | |
| int MITAB_STDCALL | mitab_c_get_pen_pattern (mitab_feature feature) |
| Get an object's pen pattern property. | |
| void MITAB_STDCALL | mitab_c_set_symbol (mitab_feature feature, int symbol_no, int symbol_size, int symbol_color) |
| Set an object's symbol properties. | |
| int MITAB_STDCALL | mitab_c_get_symbol_color (mitab_feature feature) |
| Get an object's symbol color property. | |
| int MITAB_STDCALL | mitab_c_get_symbol_no (mitab_feature feature) |
| Get an object's symbol number property. | |
| int MITAB_STDCALL | mitab_c_get_symbol_size (mitab_feature feature) |
| Get an object's symbol size property. | |
| int MITAB_STDCALL | mitab_c_get_type (mitab_feature feature) |
| Return a mitab_feature's object type. | |
| int MITAB_STDCALL | mitab_c_get_parts (mitab_feature feature) |
| Return the number of parts (rings or polyline segments) in an object. | |
| int MITAB_DLL MITAB_STDCALL | mitab_c_is_interior_ring (mitab_feature feature, int requestedringindex) |
| Return a false if te ring is the first of a polygon. | |
| int MITAB_STDCALL | mitab_c_get_vertex_count (mitab_feature feature, int part) |
| Return the number of points in a part of a mitab_feature object. | |
| double MITAB_STDCALL | mitab_c_get_vertex_x (mitab_feature feature, int part, int vertex) |
| Return the X coordinate of a point in a part of a mitab_feature object. | |
| double MITAB_STDCALL | mitab_c_get_vertex_y (mitab_feature feature, int part, int vertex) |
| Return the Y coordinate of a point in a part of a mitab_feature object. | |
| int MITAB_STDCALL | mitab_c_get_field_count (mitab_handle handle) |
| Return the number of attribute fields in a dataset's schema. | |
| int MITAB_STDCALL | mitab_c_get_feature_count (mitab_handle handle) |
| Return the number of features in a dataset. | |
| int MITAB_STDCALL | mitab_c_get_field_type (mitab_handle handle, int field) |
| Return the type of an attribute field in a dataset's schema. | |
| const char *MITAB_STDCALL | mitab_c_get_field_name (mitab_handle handle, int field) |
| Return the name of an attribute field in a dataset's schema. | |
| int MITAB_STDCALL | mitab_c_get_field_name_vb (mitab_handle handle, int field, char *name, int l) |
| Return the name of an attribute field in a dataset's schema (VB version). | |
| int MITAB_STDCALL | mitab_c_get_field_width (mitab_handle handle, int field) |
| Return the width of an attribute field in a dataset's schema. | |
| int MITAB_STDCALL | mitab_c_get_field_precision (mitab_handle handle, int field) |
| Return the precision of an attribute field in a dataset's schema. | |
| const char *MITAB_STDCALL | mitab_c_get_field_as_string (mitab_feature feature, int field) |
| Fetch an attribute field value in a mitab_feature as a string. | |
| int MITAB_STDCALL | mitab_c_get_field_as_string_vb (mitab_feature feature, int field, char *value, int l) |
| Fetch an attribute field value in a mitab_feature as a string (VB Version). | |
| double MITAB_STDCALL | mitab_c_get_field_as_double (mitab_feature feature, int field) |
| Fetch an attribute field value in a mitab_feature as a double. | |
| mitab_projinfo MITAB_STDCALL | mitab_c_get_projinfo (mitab_handle dataset) |
| Get the projinfo handle from an opened dataset. | |
| int MITAB_STDCALL | mitab_c_set_projinfo (mitab_handle dataset, mitab_projinfo projinfo) |
| Set the projinfo on a newly created dataset. | |
| const char *MITAB_STDCALL | mitab_c_get_mif_coordsys (mitab_handle dataset) |
| Get the MIF CoordSys string from an opened dataset. | |
| int MITAB_STDCALL | mitab_c_get_mif_coordsys_vb (mitab_handle dataset, char *coordsys, int l) |
| Get the MIF CoordSys string from an opened dataset (VB Version). | |
| int MITAB_STDCALL | mitab_c_load_coordsys_table (const char *filename) |
| Load a Coordsys bounds lookup table from an external file. |
The C wrapper functions contained in mitab_capi.cpp provide a much simpler interface than the OGR-based C++ classes to the MITAB library to read and write .TAB and .MIF files.
To use the C API, simply include "mitab_capi.h" and use the functions defined in mitab_capi.cpp.
See also mitabc_test.cpp which for examples of use of the C API.
See contrib/README_VB.TXT in the MITAB source code distribution for informations on using the MITAB C API from VB, Pascal, or MapBasic.
|
|
Add a new field to the dataset's schema. Adding fields MUST be done immediately after creating a new dataset and BEFORE creating the first feature.
|
|
|
Close a dataset previously opened using mitab_c_open() or created using mitab_c_create().
|
|
|
Create a new .TAB or .MIF dataset. Note that it is not possible to open a file for update (i.e. read+write) with the current version of the library.
|
|
|
Create a new mitab_feature object to be written to a dataset created using mitab_c_create().
|
|
|
Destroy a mitab_feature object and release all memory associated with it.
|
|
|
Get an object's brush background color property. Applies to region, ellipse and rectangle objects.
|
|
|
Get an object's brush foreground color property. Applies to region, ellipse and rectangle objects.
|
|
|
Get an object's brush pattern property. Applies to region, ellipse and rectangle objects.
|
|
|
Get an object's brush transparency property. Applies to region, ellipse and rectangle objects.
|
|
|
Return the number of features in a dataset.
|
|
|
Fetch an attribute field value in a mitab_feature as a double.
|
|
|
Fetch an attribute field value in a mitab_feature as a string. The function returns a reference to an internal string buffer that contains the string representation of the attribute field's value (integer and floating point values are converted to string using sprintf()).
|
|
|
Fetch an attribute field value in a mitab_feature as a string (VB Version). The function returns a reference to the string representation of the attribute field's value (integer and floating point values are converted to string using sprintf()).
|
|
|
Return the number of attribute fields in a dataset's schema.
|
|
|
Return the name of an attribute field in a dataset's schema.
|
|
|
Return the name of an attribute field in a dataset's schema (VB version).
|
|
|
Return the precision of an attribute field in a dataset's schema.
|
|
|
Return the type of an attribute field in a dataset's schema.
|
|
|
Return the width of an attribute field in a dataset's schema.
|
|
|
Get the font name from a TABFC_Text or TABFC_FontPoint object, or the symbol name from a TABFC_CustomPoint.
|
|
|
Get the font name from a TABFC_Text or TABFC_FontPoint object, or the symbol name from a TABFC_CustomPoint. (VB Version)
|
|
|
Get the MIF CoordSys string from an opened dataset.
|
|
|
Get the MIF CoordSys string from an opened dataset (VB Version).
|
|
|
Return the number of parts (rings or polyline segments) in an object.
|
|
|
Get an object's pen color property. Applies only to polyline, region, rectangle, arc and ellipse objects.
|
|
|
Get an object's pen pattern property. Applies only to polyline, region, rectangle, arc and ellipse objects.
|
|
|
Get an object's pen width property.  Applies only to point and multipoint objects.
|
|
|
Get an object's symbol number property. Applies only to point and multipoint objects.
|
|
|
Get an object's symbol size property. Applies only to point and multipoint objects.
|
|
|
Get the text string on a TABFC_Text object.
|
|
|
Fetch a TABFC_Text object's angle property.
|
|
|
Fetch a TABFC_Text object's background color property.
|
|
|
Fetch a TABFC_Text object's foreground color property.
|
|
|
Fetch a TABFC_Text object's MBR height property.
|
|
|
Fetch a TABFC_Text object's justification property.
|
|
|
Fetch a TABFC_Text object's linetype property.
|
|
|
Fetch a TABFC_Text object's spacing property.
|
|
|
Get the text string on a TABFC_Text object (VB Version).
|
|
|
Fetch a TABFC_Text object's MBR width property.
|
|
|
Return a mitab_feature's object type.
|
|
|
Return the number of points in a part of a mitab_feature object.
|
|
|
Return the X coordinate of a point in a part of a mitab_feature object.
|
|
|
Return the Y coordinate of a point in a part of a mitab_feature object.
|
|
|
Get the last error message. Fetches the last error message posted with CPLError(), that hasn't been cleared by CPLErrorReset(). The returned pointer is to an internal string that should not be altered or freed.
|
|
|
Get the last error message (VB Version). Fetches the last error message posted with CPLError(), that hasn't been cleared by CPLErrorReset(). The returned pointer is to an internal string that should not be altered or freed.
|
|
|
Fetch the last error number. This is the error number, not the error class.
|
|
|
Returns the version of the library.
|
|
|
Return a false if te ring is the first of a polygon.
|
|
|
Load a Coordsys bounds lookup table from an external file. The entries from that table will be looked up in priority BEFORE the default bounds predefined for each coordsys inside the MITAB library. This allows users to override the default bounds for existing projections, and to define bounds for new projections not already supported by MITAB. The format of the file is a simple text file with one CoordSys string per line. The CoordSys lines should follow the MIF specs, and MUST include the optional Bounds definition at the end of the line. e.g. CoordSys Earth Projection 8, 24, "m", -63, 0, 0.9996, 500000, 0 Bounds \ (-7746230.6469039, -9998287.383889269) (8746230.6469039, 9998287.383889269)
|
|
|
Iterator to get the next valid feature id when reading a dataset opened with mitab_c_open().
|
|
|
Open an existing .TAB or .MIF dataset for read access. The function automatically detects the format (.MIF or .TAB) of the specified file. Note that it is not possible to open a file for update (i.e. read+write) with the current version of the library.
|
|
|
Read a mitab_feature object from the file. Works only with datasets opened with mitab_c_open().
|
|
|
Set an arc or ellipse feature parameters.
|
|
|
Set an object's brush properties. Applies to region, ellipse and rectangle objects. See the MIF specs for more details on the meaning and valid values of each parameter.
|
|
|
Set the value of specified field in a feature object.
|
|
|
Set the font name in a a TABFC_Text or TABFC_FontPoint object, or set the symbol name in a TABFC_CustomPoint.
|
|
|
Set an object's pen properties. Applies only to polyline, region, rectangle, arc and ellipse objects. See the MIF specs for more details on the meaning and valid values of each parameter.
|
|
|
Set the feature's coordinates.
|
|
|
Set the projinfo on a newly created dataset. Should be called immediately after creating the dataset and before adding features to it.
|
|
|
Set an object's symbol properties. Applies only to point objects and multipoint. See the MIF specs for more details on the meaning and valid values of each parameter.
|
|
|
Set the text string on a TABFC_Text object.
|
|
|
Set a TABFC_Text object's display properties. See the MIF specs for more details on the meaning and valid values of each parameter.
|
|
|
Write a new feature to a dataset. Works only with datasets created using mitab_c_create(). The feature to write should have been created using mitab_c_create_feature() and its attributes and coordinate information set prior to calling this function. Also note that the mitab_feature object will NOT be owned by the dataset after this call and it is still the responsibility of the caller to destroy it.
|


Warning: Your current browser has not been tested extensively with this website, which may result in some some errors with functionality. The following browsers are fully supported:
Please use a different browser.


| DOSE: T+ 0:00 |
2 tsp |
oral |
Wormwood |
(tea) |
| T+ 0:00 |
1 tsp |
oral |
Nutmeg |
(tea) |
| T+ 0:35 |
270 mg |
smoked |
Kava |
(ground / crushed) |
About three days ago I had purchased a 200 gram back of wormwood, with the hopes of brewing some absinthe. At the same time, I also purchased 60 kava soft-gel tablets with 30% kava lactones. The following day, I woke up at 10:30 and felt a strong desire to test the wormwood by making a tea. I don't know why, but that's just the way I felt. So at 10:15, I opened a bag of mint tea and added 2 tsp of wormwood, and 1 tsp of nutmeg for flavour. I then boiled this in a kettle containing ~2 cups of water for 15-20 minutes. After this I allowed the tea to steep for an additional 10 minutes. During this time, I emptied out 6-150 mg capsules of Kava at 30% kavalactones, which gave me roughly 270 mg of kavalactones. This gunk was then placed between 2 pieces of wax paper and put into the freezer. By then, my tea was ready so I poured it into the glass I had ready. I started drinking it at about 10:45, and slowly sipped it until 11:20.
The tea was slightly bitter, but I added some honey, which went lovely with the mint and nutmeg. All in all, not too bad. Half way through drinking the tea, I started to feel slightly sedated, and found laying down on my couch extremely comfortable. By the time I was done, I was fully relaxed and didn't have a care in the world. Then I remembered the kava in the fridge, so I gathered all of my will power and got up, then walked to the freezer. After taking out the gunk, I couldn't decide how to take it, but then an excellent idea hit me. I went downstairs (which took quite long because I was moving incredibly slow) and grabbed my hookah and Lebanese molasses tobacco, which one of my Lebanese friends had given to me for my birthday. I mixed the kava and tobacco together in the large bowl, filled the hookah with water, and lit up a special coal that burns on top.
I prefer doing any smoking this way (definitely hashish) because the coal on top acts like a vaporiser would, and the water cools the smoke. The kava had an interesting flavor, which strongly overpowered the apple flavoured tobacco. It was very natural and earthy tasting, which is the only way I can describe it. Well, if I was really mellow before, then after a half hour of smoking, I was almost in a haze. Everything I did was drastically slowed down, and I felt lazy, relaxed, yet not too tired. I would have these funny ideas pop into my head and giggle over them for some time. Anything involving concentration lost my interest, and I would go through periods of absolutely no thought, to vivid ideas and clear thought. This lasted about 1 ½ – 2 hours and was then followed by the best sleep I ever had, with lucid dreams and virtually no interruptions. I found this to be very pleasant and will definitely try it again sometime.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Web Worker: Inline worker example
This is an example for inline worker that we creating 'on the fly' without the need to fetch
our JavaScript code of the worker from another file.
It is useful method to create a self-contained page without having to create separate worker file.
With the new BlobBuilder interface, you can "inline" your worker in the same HTML file as your
main logic by creating a BlobBuilder and appending the worker code as a string.


Selected Publications
ORCiD: 0000-0002-9077-6026
Wilkie, J., Carville, K., Fu, S. C., Kerr, R., Finlayson, K., Tuffrey, T., Lenzo, J. C., Geelhoed, G. (2023) Determining the Actual Cost of Wound Care in Australia, Wound Practice and Research, https://doi.org/10.33235/wpr.31.1.7-18
Kutzer, Y., Whitehead, L., Quigley, E., Fu, S. C., Stanley, M. (2023). Subjective versus Objective Sleep Outcomes in Older Adults with and without Uncoupled Sleep Following Online Cognitive Behavioural Therapy for Insomnia, Psychogeriatrics, https://doi.org/10.1111/psyg.12931
Rees, J., Fu, S. C., Lo, J., Sambell, R., Lewis J. R., Christophersen, C. T., Byrne, M. F., Newton, R. U., Boyle, S., Devine, A. (2022). How a 7-Week Food Literacy Cooking Program Affects Cooking Confidence and Mental Health: Findings of a Quasi-Experimental Controlled Intervention Trial, Frontiers in Nutrition, Volume 9, March. https://doi.org/10.3389/fnut.2022.802940
Maisey, G., Cattani, M., Devine, A., Lo, J., Fu, S. C., Dunican, I. C. (2022). Digging for data: How sleep is losing out to roster design, sleep disorders, and lifestyle factors, Applied Ergonomics, Volume 99, February. https://doi.org/10.1016/j.apergo.2021.103617
Reyes, A., Bartlett D. M., Rankin T. J., Zaenker P., Turner K., Teo W-P., Fu S. C., et al. (2021). Clinical Determinants of Dual Tasking in People With Premanifest Huntington Disease. Physical Therapy, January. https://doi.org/10.1093/ptj/pzab016
Baddeley, A., Brown, W., Milne, R. K., Nair, G., Rakshit, S., Lawrence, T., Phatak, A., Fu, S. C. (2020). Optimal thresholding of predictors in mineral prospectivity analysis. Natural Resources Research. https://doi.org/10.1007/s11053-020-09769-2
Trott, C. M., Fu, S. C., Murray, S. G., Jordan, C. H., Line, J. L. B., Barry, N., … Walker, M. (2019). Robust statistics towards detection of the 21 cm signal from the Epoch of Reionization. Monthly Notices of the Royal Astronomical Society, 486(4), 5766–5784. https://doi.org/10.1093/mnras/stz1207
Holden, E. J., Fu, S. C., Kovesi, P., Dentith, M., Bourne, B., & Hope, M. (2011). Automatic identification of responses from porphyry intrusive systems within magnetic data using image analysis. Journal of Applied Geophysics, 74(4), 255–262. https://doi.org/10.1016/j.jappgeo.2011.06.016
Fu, S. C., & Kovesi, P. (2010). Robust extraction of optic flow differentials for surface reconstruction. Proceedings - 2010 Digital Image Computing: Techniques and Applications, DICTA 2010, 468–473. https://doi.org/10.1109/DICTA.2010.85
Holden, E. J., Kovesi, P., Dentith, M. C., Wedge, D., Wong, J. C., & Fu, S. C. (2010). Detection of regions of structural complexity within aeromagnetic data using image analysis. International Conference Image and Vision Computing New Zealand, 1–8. https://doi.org/10.1109/IVCNZ.2010.6148856
Fu, S. C., & Milne, G. (2004). A Flexible Automata Model for Disease Simulation. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 3305, pp. 642–649). https://doi.org/10.1007/978-3-540-30479-1_66
“Don’t forget that statisticians are the free-est of all scientists - they can work on anything.”
– David R. Brillinger


Tahoma Robotics Club
Bear Metal, FRC Team 2046
Design Lead
September 2012 - June 2017 // Maple Valley, WA
Since 2007, Bear Metal has participated in FIRST Robotics Competition. FRC is an engineering sport where teams from around the world are given six weeks to strategize, design, fabricate, assemble, wire, program, and practice a human-sized robot. These robots are then pitted against each other by playing a game that changes every year. My brother joined Bear Metal for their 2009 season. Every chance I got, I would visit their shop and learn how to build robots. In 2012, I was finally old enough, despite being in middle school, to help the high school team.
2017, Hindenbearg: Senior year for me meant this had to be the best robot I’ve designed. Spoiler: it was. Steamworks, a steampunk theme, meant the robot had to collect fuel, wiffle balls, to put them in a boiler then climb onto an airship once the propellers had enough gears to spin up. Our robot's chassis was fast by having the maximum number of high-power motors attached. Both the fuel collector and the gear collector were incredibly effective. The double wide shooter, guided by camera, could propel 10 fuel every second into the 8 feet tall boiler. The climber’s spinning hook side Velcro drum fastened to fibrous rope and lifted the entire robot to reveal my Easter egg: the bottom of the robot was the team’s logo which could only revealed with a successful climb.
At least 2000 parts, from frame members to motors to bolts to electronics to zip ties, were CADed in Autodesk Inventor. 90% of that work was my doing over the first 18 days of build season. Once the design started being fabricated by our in-house CNC mills, I moved to rendering a preview. I spent countless hours adjusting materials, lighting, and settings to achieve the photorealistic render. Except as my worst critic, I see areas for improvement now two years later.
2016, Xcalibear: FIRST decided to make every game themed. 2016 was the first and they picked medieval times. The robots had to scramble over moats, across rubble, and through a portcullis to reach a castle then throw boulders to destroy the tower. Our response had a fitting name: a pun of Excalibur whilst dropping the E to accent that it was our tenth robot. I had initial trouble designing the chassis, but the final version was excellent at traversing any obstacles with its 8 inch pneumatic wheels and dual speed gearboxes.
The collector was fun to design. It articulated up, down, and middle with its triple position pneumatic cylinders. It had a separately articulated set of wheels and conveyor belts which swiftly grabbed any boulder in the vicinity. At the world competition, we figured out how to climb using a telescopic arm and a hook. This was another time where we could always climb in practice but rarely could during the matches. This was my first year spending significant time on photorealistic rendering. Albeit my first time, the resulting image turned out better than expected.
2015, Maverick: My first robot as the design lead, also our first powdered coated robot. Coincidence? I think not. This attractive robot played an interesting game that involved stacking totes and filling recycling containers with pool noodles. I did say interesting. I had fun with the chassis, it was our first robot that could drive sideways! By utilizing an H drive, it could precisely position to align with the totes quickly. The lift made Maverick the one of the tallest robots we have made. Plus, with a pneumatic actuated rake that slammed down on the recycling containers, it was our longest robot. In my opinion, the rake (not pictured) made this robot the most dangerous and intimidating machine in our collection.
2014, Bearium: Sort of like volleyball but with exercise balls: Aerial Assist. Our approach resulted in one of our scariest robots, but also so cool. The catapult was my task as the assistant design lead. It had massive springs, winched back by a gearbox with a pneumatic clutch, and adjustable range control using over-centered cams. Its performance was excellent, but the overall robot suffered from its poor collector and intermittent electrical faults. This robot taught me that the electronics need to be designed robustly and have easy access for fault troubleshooting, which I have followed ever since.
2013, Bearodactyl: This was an exciting game with an enlightening robot. The goal was to throw frisbees into boxes on the wall and to climb a 10 feet tall pyramid. Our robot’s strategy was to do every task possible in the game. My main contribution was on the climber which gave the robot its name by climbing with claws. I designed various components and after many hours of troubleshooting, it climbed. Check out a video of it working in practice. Somehow successful practice did not result in successful matches. Poor performance in competition taught the team about how the “do all” strategy isn’t always the best.
2012, Bearmageddon: Rebound Rumble, a basketball game with tilting bridges. As this was my first official year, I did the usual first year duties: deburring, sanding, cutting stock, etc. It was a while ago, so I don’t remember exactly what I did; though, I do remember designing part of the robot’s turret and machining out some parts on the CNC mill.
tags: CAD, manufacturing, mechanical, rendering, robotics, technical drawings


pg-execute-query
Async parameters binding and query execution using pg.
Install
$ npm install pg-execute-query
Usage
var execute = require('pg-execute-query')
Examples
var execute = require('pg-execute-query')
var connection = process.env.DATABASE_URL
var queryString = 'select $1::int as num'
var queryParameters = ['1']
execute.executeQuery(connection, queryString, queryParameters, callback)
function callback (res) {
console.log(res[0].num)
// 1
}
The queryParameters and the callback are optional
var execute = require('pg-execute-query')
var connection = process.env.DATABASE_URL
var queryString = 'select 1::int as num'
execute.executeQuery(connection, queryString, callback)
function callback (res) {
console.log(res[0].num)
// 1
}
var execute = require('pg-execute-query')
var connection = process.env.DATABASE_URL
var queryString = 'select 1::int as num'
execute.executeQuery(connection, queryString, queryParameters)
// nothing
var execute = require('pg-execute-query')
var connection = process.env.DATABASE_URL
var queryString = 'select 1::int as num'
execute.executeQuery(connection, queryString)
// nothing
License
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Introduction
'From fitbit to apple watch, self tracking activities, movements, calories intake,... is becoming increasingly popular. The tracking self investigates the concept of self tracking, with a critical view towards quantified self. The tracking self project explores the possibility of designing personal wearable devices or apps that allow a better understanding of self, and create an opportunity for reflecting on personal behaviours such as physical activity, or self-regulating emotions.'
Ever since we are living in the information era and smartphones became the communication device nr. 1, with a range of sensors and integrated circuits miniaturised to the point that every single, seemingly trifling data may be captured, the potential to form a larger picture and contribute to understanding oneself opens up, provided by the graduating openness of platforms and their willingness to share database resources via API, I am curious as to explore how a collective of datasets could potentially visualise, inform and in consequence educate and drive the enrichment of anyone's life.


Brand Logo
4:02 PM
Carrier
Achievements
Punched In Weight
3x
Ate Healthy
1x
3 Consecutive Gym Days
3x
Went to the Gym
10x
2 Consecutive Gym Days
3x
Tracked Weight
3x
Started a Mission
3x


{% load wagtailcore_tags wagtailimages_tags %} {# Individual event item in a list - used on event index and home page #}
{{ resource.short_description }}


| Package | Description |
|---|---|
| org.deeplearning4j.spark.impl.repartitioner | |
| org.deeplearning4j.spark.parameterserver.training |
| Modifier and Type | Class and Description |
|---|---|
class |
DefaultRepartitioner
DefaultRepartitioner: Repartition data so that we exactly the minimum number of objects per partition, up to a
specified maximum number of partitions
|
class |
EqualRepartitioner
Equal repartitioner.
|
class |
NoOpRepartitioner
No-op repartitioner.
|
| Modifier and Type | Field and Description |
|---|---|
protected Repartitioner |
SharedTrainingMaster.repartitioner |
protected Repartitioner |
SharedTrainingMaster.Builder.repartitioner |
| Modifier and Type | Method and Description |
|---|---|
SharedTrainingMaster.Builder |
SharedTrainingMaster.Builder.repartitioner(Repartitioner repartitioner)
Repartitioner to use to repartition data before fitting.
|
| Constructor and Description |
|---|
SharedTrainingMaster(@NonNull VoidConfiguration voidConfiguration,
Integer numWorkers,
RDDTrainingApproach rddTrainingApproach,
org.apache.spark.storage.StorageLevel storageLevel,
boolean collectTrainingStats,
RepartitionStrategy repartitionStrategy,
Repartition repartition,
ThresholdAlgorithm thresholdAlgorithm,
ResidualPostProcessor residualPostProcessor,
int rddDataSetNumExamples,
int batchSizePerWorker,
long debugLongerIterations,
int numWorkersPerNode,
int workerPrefetchBatches,
Repartitioner repartitioner,
Boolean workerTogglePeriodicGC,
Integer workerPeriodicGCFrequency,
boolean encodingDebugMode) |
Copyright © 2020. All rights reserved.


2020-02-16
pbb
is now producing something that’s not quite as much
saying “90s HTML” any longer. I took some inspiration from the “satire”
(debatable) websites that started with the mothereffing website1. I’d say the original
pbb
output was very close to that (i.e., no styling at
all), but thanks to sane pandoc defaults, it didn’t even look all that
bad, also on mobile devices. Only the super long lines weren’t all that
great on bigger displays.
As it turns out, the m-effing website inspired a whole slew of improvements, each more assertive than the other: better, even better, best, the best, perfect, and (unoriginally) another the best one.
There’s even one of these “awesome” lists on GitHub, and from there, I found a paper about the original one. Academic and all.
The different improvements revolve mostly around styling, security, accessibility and the like, but the overall idea stays the same. I took the styling of the first better one and tweaked it a tiny little bit:
body {color: #333;
font-size: 18px;
line-height: 1.6;
margin: 40px auto;
max-width: 650px;
padding: 0 10px;
}
, h2, h3 {
h1line-height:1.2;
}
img {max-width: 100%;
}
I didnt know that there’s a whole war out there regarding contrast and if it is bad or not. I settled on the same dark grey as the New York Times uses. They probably know how to do this.
The other change I did was for images, to prevent that they’d be wider than the text column.
All in all, the result looks like this (on the date this post was written):
I’ll look into a nicer font and different styling for links, but other than that, I feel like that’s a pretty good ROI. Well, the font in code blocks feels a bit large now. Still. Good ROI.


First day of the month:
DATEADD(dd,-(DAY(DATEADD(mm,1,GETDATE()))-1),DATEADD(mm,0,GETDATE()))
First day of the week:
DATEADD(yyyy, DATEPART(yyyy, DATEADD(weekday, 1-DATEPART(weekday, GETDATE()),GETDATE()))-1900, 0) + DATEADD(dy, DATEPART(dy, DATEADD(weekday, 1-DATEPART(weekday, GETDATE()), GETDATE()))-1,0)
Last day of the month:
DATEADD(ms, -3, DATEADD (m,DATEDIFF(m,0,DATEADD(m,1,GETDATE())),0))
Last Business Day of the Month: (buckle up for this one)
CASE WHEN DATEPART(DW, DATEADD(ms, -3, DATEADD (m,DATEDIFF(m,0,DATEADD(m,1,GETDATE())),0)))=7
THEN DATEADD(DAY,-2, DATEADD(ms, -3, DATEADD (m,DATEDIFF(m,0,DATEADD(m,1,GETDATE())),0)))
WHEN DATEPART(DW, DATEADD(ms, -3, DATEADD (m,DATEDIFF(m,0,DATEADD(m,1,GETDATE())),0)))=6
THEN DATEADD(DAY,-1, DATEADD(ms, -3, DATEADD (m,DATEDIFF(m,0,DATEADD(m,1,GETDATE())),0)))
ELSE DATEADD(ms, -3, DATEADD (m,DATEDIFF(m,0,DATEADD(m,1,GETDATE())),0)) END AS Last_Business_day_of_month
What can I do with this you ask? Well, You can put it in a procedure for SSRS reports to get a dynamic date on subscriptions with a hidden parameter.
ALTER PROCEDURE usp_CommonDates_Report
AS
BEGIN
SET DATEFIRST 1
DECLARE @Now DATETIME
,@LDOTM DATETIME --Last Day Of The Month
SET @Now= GETDATE()
SET @LDOTM = DATEADD(ms, -3, DATEADD (m,DATEDIFF(m,0,DATEADD(m,1,@Now)),0))
SELECT
@Now AS Today
, DATEADD(yyyy, DATEPART(yyyy, DATEADD(weekday,1-DATEPART(weekday, @Now),@Now))-1900, 0) + DATEADD(dy, DATEPART(dy, DATEADD(weekday,1-DATEPART(weekday, @Now),@Now))-1,0) AS Week_Start
, @LDOTM AS Last_day_of_month
, CASE WHEN DATEPART(DW, @LDOTM)=7 THEN DATEADD(DAY,-2, @LDOTM)
WHEN DATEPART(DW, @LDOTM)=6 THEN DATEADD(DAY,-1, @LDOTM)
ELSE @LDOTM END AS Last_Business_day_of_month
END


The purpose of this challenge is to demonstrate the MITRE Top 25 programming flaw: 'Missing Authorization'.
The developer of the vulnerable application has simply not implemented authorization checks. You have the vulnerable code below. See if you can spot the programming error.The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
<!--contents of administration page cwe862admin.jsp--> <% if(session.getAttribute("cwe862loggedin")==null || !(boolean)session.getAttribute("cwe862loggedin")){ response.sendRedirect("cwe862.jsp?loggedin=false"); } %> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>CWE862 - Missing Authorization - Admin</title>


Documentation
Emulation name:
Distribution name:
x
-
Run
locally
on
Start time (s from beginning):
Emulator:
?
Distribution:
?
Resource:
Add Distribution
Enable logging
Frequency:
Level:
info
debug
error
Enable message queue
vhost:
exchange:
user:
password:
host:
topic:
Total Duration:
Run now
Run at:
Current Emulations:
Enable Job List
Refresh Job list