The purpose of this plugin is to extend our Sample plugin by making it possible for the user to add two numbers through a dockable window.
i18n └─ SampleWindow_fr.ts res └─ SampleWindow_i18n.qrc.in src ├─ samplewindowplugin.cpp ├─ samplewindowplugin.h ├─ samplewindowplugin.json ├─ samplewindowwindow.cpp ├─ samplewindowwindow.h └─ samplewindowwindow.ui CMakeLists.txt
Our plugin is part of the Sample
category, which means that its code can be found under [OpenCOR]/src/plugins/sample/SampleWindow/
.
Unlike for the Sample plugin, we want our plugin to interact with OpenCOR. This means that it needs to implement some interfaces (click here for some information on interfaces).
More specifically, we want our plugin to be a dockable window, so we need to implement both the plugin and window interfaces. While we are at it, we might as well internationalise our plugin, in which case it means that we also need to implement the internationalisation interface.
As for the Sample plugin, our plugin has a CMakeLists.txt
file, which contents is:
PROJECT(SampleWindowPlugin) # Add the plugin ADD_PLUGIN(SampleWindow SOURCES../../i18ninterface.cpp
../../plugininfo.cpp
src/samplewindowplugin.cpp
src/samplewindowwindow.cpp
HEADERS_MOCsrc/samplewindowplugin.h
src/samplewindowwindow.h
UISsrc/samplewindowwindow.ui
INCLUDE_DIRS src PLUGINS Core Sample )
One of the interfaces our plugin implements comes with a .cpp
file, so we reference it (line 7). Then, our plugin needs both the Core and Sample plugins (the latter, to be able to use its add()
function), so they are referenced (lines 20 and 21) using the PLUGINS
keyword (line 19). Our plugin comes with a dockable window, which is implemented using various files (lines 11, 14 and 16). One of those files is a .ui
file, which is referenced using the UIS
keyword (line 15).
Our plugin information can be found in samplewindowplugin.cpp
, samplewindowplugin.h
and samplewindowplugin.json
. Starting with samplewindowplugin.h
, its contents is:
#include "i18ninterface.h
" #include "plugininfo.h
" #include "plugininterface.h
" #include "windowinterface.h
" //============================================================================== namespace OpenCOR { namespace SampleWindow { //============================================================================== PLUGININFO_FUNC SampleWindowPluginInfo(); //============================================================================== class SampleWindowWindow; //============================================================================== class SampleWindowPlugin : public QObject, public I18nInterface, public PluginInterface, public WindowInterface { Q_OBJECT Q_PLUGIN_METADATA(IID "OpenCOR.SampleWindowPlugin" FILE "samplewindowplugin.json
") Q_INTERFACES(OpenCOR::I18nInterface) Q_INTERFACES(OpenCOR::PluginInterface) Q_INTERFACES(OpenCOR::WindowInterface) public: #include "i18ninterface.inl
" #include "plugininterface.inl
" #include "windowinterface.inl
" private: QAction *mSampleWindowAction; SampleWindowWindow *mSampleWindowWindow; }; //============================================================================== } // namespace SampleWindow } // namespace OpenCOR
As mentioned above, our plugin implements some interfaces, which means that their header file is included (lines 26, 28 and 29). It also means that our plugin class inherits from those interfaces (lines 46-47), as well as make calls to the Q_INTERFACES()
macro to let Qt know which interfaces it implements (lines 53-55). Finally, we include the inline files (lines 58-60) that declare various methods that must be implemented by our plugin (see the next section). (The rest of the class definition is specific to our plugin and is discussed below.)
The C function that is used by OpenCOR to retrieve some basic information about our plugin can be found in samplewindowplugin.cpp
:
PLUGININFO_FUNC SampleWindowPluginInfo() { Descriptions descriptions; descriptions.insert("en", QString::fromUtf8("a plugin that provides an addition window.")); descriptions.insert("fr", QString::fromUtf8("une extension qui fournit une fenêtre d'addition.")); return new PluginInfo(PluginInfo::Sample, true, false, QStringList() << "Core" << "Sample", descriptions); }
As can be seen, our plugin is selectable by the user, but it does not offer direct CLI support (line 44). It also has a direct dependency on both the Core and Sample plugins (line 45).
The implementation of the interfaces' various methods can also be found in samplewindowplugin.cpp
. The methods are grouped by interface and are ordered alphabetically. The interfaces are also ordered alphabetically, making it easier to read and maintain the code.
We start with the internationalisation interface:
//============================================================================== // I18n interface //============================================================================== void SampleWindowPlugin::retranslateUi() { // Retranslate our sample window action retranslateAction(mSampleWindowAction, tr("Sample"), tr("Show/hide the Sample window")); } //==============================================================================
All that we need to do here is to (re)translate mSampleWindowAction
with the actual (French) translations in SampleWindow_fr.ts
(together with some other translations needed in the next section). Note that mSampleWindowAction
is initialised in our implementation of the plugin interface (see below).
Next, we have the plugin interface:
//============================================================================== // Plugin interface //============================================================================== void SampleWindowPlugin::initializePlugin() { // Create an action to show/hide our sample window mSampleWindowAction = Core::newAction(true, Core::mainWindow()); // Create our sample window mSampleWindowWindow = new SampleWindowWindow(Core::mainWindow()); } //============================================================================== void SampleWindowPlugin::finalizePlugin() { // We don't handle this interface... } //============================================================================== void SampleWindowPlugin::pluginsInitialized(const Plugins &pLoadedPlugins) { Q_UNUSED(pLoadedPlugins); // We don't handle this interface... } //============================================================================== void SampleWindowPlugin::loadSettings(QSettings *pSettings) { Q_UNUSED(pSettings); // We don't handle this interface... } //============================================================================== void SampleWindowPlugin::saveSettings(QSettings *pSettings) const { Q_UNUSED(pSettings); // We don't handle this interface... } //============================================================================== void SampleWindowPlugin::handleUrl(const QUrl &pUrl) { Q_UNUSED(pUrl); // We don't handle this interface... } //==============================================================================
The only method of interest to our plugin is initializePlugin()
(lines 66-75), which is where we initialise both mSampleWindowAction
and mSampleWindowWindow
. All the other methods (finalizePlugin()
, pluginsInitialized()
, loadSettings()
, saveSettings()
and handleUrl()
) are left empty.
Finally, we have the window interface:
//============================================================================== // Window interface //============================================================================== Qt::DockWidgetArea SampleWindowPlugin::windowDefaultDockArea() const { // Return our default dock area return Qt::TopDockWidgetArea; } //============================================================================== QAction * SampleWindowPlugin::windowAction() const { // Return our window action return mSampleWindowAction; } //============================================================================== QDockWidget * SampleWindowPlugin::windowWidget() const { // Return our window widget return mSampleWindowWindow; } //==============================================================================
All three methods are implemented since they tell OpenCOR the default dock area for our plugin window (see windowDefaultDockArea()
; lines 124-129), as well as provide the pointer to our action (see windowAction()
; lines 133-138) and window (see windowWidget()
; lines 142-147).
Some extra work is needed to get our plugin to do what it is supposed to be doing, and this is done via the SampleWindowWindow
class in samplewindowwindow.h
:
#include "windowwidget.h
"
//==============================================================================
namespace Ui {
class SampleWindowWindow;
}
//==============================================================================
namespace OpenCOR {
namespace SampleWindow {
//==============================================================================
class SampleWindowWindow : public Core::WindowWidget
{
Q_OBJECT
public:
explicit SampleWindowWindow(QWidget *pParent);
~SampleWindowWindow();
private:
Ui::SampleWindowWindow *mGui;
private slots:
void updateSum();
};
//==============================================================================
} // namespace SampleWindow
} // namespace OpenCOR
SampleWindowWindow
inherits from Core::WindowWidget
, which is defined in the Core plugin and is an extended version of Qt's QDockWidget
(line 41). It also comes with a GUI file, which describes the layout of our plugin window (samplewindowwindow.ui
).
The implementation of SampleWindowWindow
can be found in samplewindowwindow.cpp
:
//============================================================================== // Sample window //============================================================================== #include "sampleutilities.h
" #include "samplewindowwindow.h
" //============================================================================== #include "ui_samplewindowwindow.h" //============================================================================== namespace OpenCOR { namespace SampleWindow { //============================================================================== SampleWindowWindow::SampleWindowWindow(QWidget *pParent) : Core::WindowWidget(pParent), mGui(new Ui::SampleWindowWindow) { // Set up the GUI mGui->setupUi(this); // A couple of connections to update our sum whenever one of the value of // one of our numbers is updated connect(mGui->nb1DoubleSpinBox, SIGNAL(valueChanged(double)), this, SLOT(updateSum())); connect(mGui->nb2DoubleSpinBox, SIGNAL(valueChanged(double)), this, SLOT(updateSum())); // Initialise our sum updateSum(); } //============================================================================== SampleWindowWindow::~SampleWindowWindow() { // Delete the GUI delete mGui; } //============================================================================== void SampleWindowWindow::updateSum() { // Update our sum mGui->sumLabel->setText(QString::number(Sample::add(mGui->nb1DoubleSpinBox->value(), mGui->nb2DoubleSpinBox->value()))); } //============================================================================== } // namespace SampleWindow } // namespace OpenCOR
SampleWindowWindow()
(lines 36-55) initialises the SampleWindowWindow
object, as well as creates a couple of connections (lines 47-50) and initialises our sum by calling updateSum()
(line 54). As can be seen, updateSum()
calls the add()
method from the Sample plugin (lines 68-73).


--- # See https://github.com/allejo/jekyll-anchor-headings/issues/5 --- {% capture markdown %} # Heading 1 # Heading 2 {% endcapture %} {% assign text = markdown | markdownify %}


A Full Week to Explore the Future of Work
Curious what the future of work looks like? Probably a lot like coworking.
Try all of the participating Coworking Spaces for free
During the week of September 17 – 21, Berlin’s Coworking Spaces will open their doors for Coworking Festival – a unique chance to explore modern work spaces and collaboration.
Get free OneCoworking Vouchers


Error!
{{errorMessage}}
Summoner Name
Search
Error!
There was a problem reaching our server! Please try again later.
Retry
Loading Data...


debug context
the result for the dependency evaluation if any
the error
whether there was error thrown during the rule execution
whether dependency is executed successfully for worlkflow, this indicate whether there are exception occurred during the rule execution for validation, in addition to above, this also means the result evaluates to true
metadata provided on the rule
the result returned from the rule action for validation rules, this should be true/false
the name of the rule that has been evaluated
the timestamp in UTC for when the rule execution starts
Generated using TypeDoc
the timestamp in UTC for when the rule execution ends


30-June-2019 - 6.16.0
The PMD team is pleased to announce PMD 6.16.0.
This is a minor release.
New and noteworthy
Updated PMD Designer
This PMD release ships a new version of the pmd-designer. For the changes, see PMD Designer Changelog.
PLSQL Grammar Updates
The grammar has been updated to support inline constraints in CREATE TABLE statements. Additionally, the CREATE TABLE statement may now be followed by physical properties and table properties. However, these properties are skipped over during parsing.
The CREATE VIEW statement now supports subquery views.
The EXTRACT function can now be parsed correctly. It is used to extract values from a specified datetime field. Also date time literals are parsed now correctly.
The CASE expression can now be properly used within SELECT statements.
Table aliases are now supported when specifying columns in INSERT INTO clauses.
New Rules
-
The Java rule
DoubleBraceInitialization
(java-bestpractices
) detects non static initializers in anonymous classes also known as “double brace initialization”. This can be problematic, since a new class file is generated and object holds a strong reference to the surrounding class.Note: This rule is also part of the Java quickstart ruleset (
rulesets/java/quickstart.xml
).
Modified Rules
-
The Java rule
UnusedPrivateField
(java-bestpractices
) now ignores by default fields, that are annotated with the Lombok experimental annotation@Delegate
. This can be customized with the propertyignoredAnnotations
. -
The Java rule
SingularField
(java-design
) now ignores by default fields, that are annotated with the Lombok experimental annotation@Delegate
. This can be customized with the propertyignoredAnnotations
. -
The Java rules
UnsynchronizedStaticFormatter
andUnsynchronizedStaticDateFormatter
(java-multithreading
) now prefer synchronized blocks by default. They will raise a violation, if the synchronization is implemented on the method level. To allow the old behavior, the new propertyallowMethodLevelSynchronization
can be enabled. -
The Java rule
UseUtilityClass
(java-design
) has a new propertyignoredAnnotations
. By default, classes that are annotated with Lombok’s@UtilityClass
are ignored now. -
The Java rule
NonStaticInitializer
(java-errorprone
) does not report non static initializers in anonymous classes anymore. For this use case, there is a new rule now:DoubleBraceInitialization
(java-bestpractices
). -
The Java rule
CommentDefaultAccessModifier
(java-codestyle
) was enhanced in the last version 6.15.0 to check also top-level types by default. This created many new violations. Missing the access modifier for top-level types is not so critical, since it only decreases the visibility of the type.The default behaviour has been restored. If you want to enable the check for top-level types, you can use the new property
checkTopLevelTypesa
. -
The Java rule
CloseResource
(java-errorprone
) now by default searches for any unclosedjava.lang.AutoCloseable
resource. This includes now the standardjava.io.*Stream
classes. Previously only SQL-related resources were considered by this rule. The types can still be configured via thetypes
property. Some resources do not need to be closed (e.g.ByteArrayOutputStream
). These exceptions can be configured via the new propertyallowedResourceTypes
. In order to restore the old behaviour, just remove the typejava.lang.AutoCloseable
from thetypes
property and keep the remaining SQL-related classes.
Deprecated Rules
- The Java rule
AvoidFinalLocalVariable
(java-codestyle
) has been deprecated and will be removed with PMD 7.0.0. The rule is controversial and also contradicts other existing rules such asLocalVariableCouldBeFinal
. If the goal is to avoid defining constants in a scope smaller than the class, then the ruleAvoidDuplicateLiterals
should be used instead.
Fixed Issues
- apex
- #1664: [apex] False positive ApexSharingViolationsRule, unsupported Apex feature
- java
- #1848: [java] Local classes should preserve their modifiers
- java-bestpractices
- java-codestyle
- java-design
- #1094: [java] UseUtilityClass should be LombokAware
- java-errorprone
- java-multithreading
- plsql
API Changes
Deprecated APIs
Reminder: Please don’t use members marked with the annotation
InternalApi
, as they will likely be removed, hidden, or otherwise intentionally broken with 7.0.0.
In ASTs
As part of the changes we’d like to do to AST classes for 7.0.0, we would like to hide some methods and constructors that rule writers should not have access to. The following usages are now deprecated in the Java AST (with other languages to come):
- Manual instantiation of nodes. Constructors of node classes are deprecated and marked
InternalApi
. Nodes should only be obtained from the parser, which for rules, means that never need to instantiate node themselves. Those constructors will be made package private with 7.0.0. - Subclassing of abstract node classes, or usage of their type. Version 7.0.0 will bring a new set of abstractions that will be public API, but the base classes are and will stay internal. You should not couple your code to them.
- Setters found in any node class or interface. Rules should consider the AST immutable. We will make those setters package private with 7.0.0.
Please look at net.sourceforge.pmd.lang.java.ast
to find out the full list
of deprecations.
External Contributions
- #1482: [java] Explain the existence of AvoidFinalLocalVariable in it’s description - Karl-Philipp Richter
- #1792: [java] Added lombok.experimental to AbstractLombokAwareRule - jakivey32
- #1808: [plsql] Fix PL/SQL Syntax errors - Hugo Araya Nash
- #1829: [java] Fix false negative in UnsynchronizedStaticFormatter - Srinivasan Venkatachalam
- #1847: [java] Regression in MethodReturnsInternalArray not handling enums - Artem
- #1863: [plsql] Add Table InlineConstraint - Hugo Araya Nash
- #1864: [plsql] Add support for Subquery Views - Hugo Araya Nash
- #1865: [plsql] Add Support for Extract Expression - Hugo Araya Nash
- #1874: [plsql] Add parenthesis equation support for Update - Hugo Araya Nash
- #1876: [plsql] Datetime support for queries - Hugo Araya Nash
- #1883: [plsql] Fix #1873 Expression list not working - Hugo Araya Nash
- #1884: [plsql] fix #1878 Support explicit INNER word for INNER JOIN - Hugo Araya Nash
- #1885: [plsql] Correct case expression - Hugo Araya Nash
- #1886: [plsql] Support table alias for Insert Clause - Hugo Araya Nash


leaf site
`Prev `__
L
`Next `__
--------------
**leaf site**: n.
[obs.] Before pervasive TCP/IP, this term was used of a machine that
merely originated and read Usenet news or mail, and did not relay any
third-party traffic. It was often uttered in a critical tone; when the
ratio of leaf sites to backbone, rib, and other relay sites got too
high, the network tended to develop bottlenecks. Compare `*backbone
site* <../B/backbone-site.html>`__. Now that traffic patterns depend
more on the distribution of routers than of host machines this term has
largely fallen out of use.
--------------
+----------------------------------+----------------------------+-------------------------+
| `Prev `__ | `Up <../L.html>`__ | `Next `__ |
+----------------------------------+----------------------------+-------------------------+
| laser chicken | `Home <../index.html>`__ | leak |
+----------------------------------+----------------------------+-------------------------+


Audio player
@@adsense
Default with one source
Micro Mode
Small Mode
Medium Mode
With a play list, full mode
Scorpions - Return to Forever
- Going Out With A Bang
- We Built This House
- Rock My Car
- House Of Cards
- All For One
- Rock'N'Roll Band
- Catch Your Luck And Play
- Rollin' Home
- Hard Rockin' The Place
- Eye Of The Storm
- The Scratch
- Gypsy Life
- The World We Used To Know
- Dancing With The Moonlight
- When The Truth Is A Lie
- Who We Are
- Crazy Ride
- One And One Is Three
- Delirious
External play list, loaded by function
<div data-role="audio">
<audio>
<source src="http://metroui.org.ua/res/rec.mp3" type='audio/mp3' />
</audio>
</div>


Terminology
Below is some information about the value sets and code systems used in Trifolia exports.
Value Set Members
Trifolia treats value sets as though they are fully expanded. When Trifolia presents a value set that contains another value set, it displays all the members of the value set in an expanded view. This represents a fully expanded view of the value set.
Value Set Status & Date
Each member of a value set contains status and date fields. Date and Status fields are used to determine which members will be exported to XML and MS Word output.
Calculated Date
For each member of a value set, a date is calculated, and this date, along with the status determines whether to include that member in an export. The date is derived using this priority:
- If the constraint includes a value set binding date, it is used.
- If no value set binding date is present, the implementation guide's publish date is used.
- If no implementation guide publish date is available, the XML or MS Word export date is used.
Status
The value set member status can be entered when a new value set member is added. Once the date is calculated, the status (if entered) and date are used to determine whether the member is included in the export as follows:
- The member is included in the export if the status is Unspecified (empty) or the calculated date is prior to the date for the member's active status.
- The member is excluded from the export the calculated date falls on or after the member's Inactive status date.
Example
Given the following value set:
Code |
Display Name |
Code System |
Status |
Date |
Value 1 |
Display 1 |
SNOMED |
Unspecified (blank) |
Unspecified |
Value 2 |
Display 2 |
LOINC |
Active |
1/1/2013 |
Value 3 |
Display 3 |
SNOMED |
Active |
1/1/2013 |
Value 2 |
Display 2 |
LOINC |
Inactive |
3/1/2013 |
For an export generated on 1/15/2013, the resulting list is:
- Value 1
- Value 2
- Value 3
For an export generated on 5/1/2013, the resulting list is:
- Value 1
- Value 3
Code Systems and Value Sets
Trifolia creates a relationship between a code system and a value set member. Code systems are used to reference a name/identifier combination.
A code system is referenced in one of the following ways:
- A value set’s member is a member of a specified code system
- A constraint indicates that an element/attribute in a template/profile must be selected from a code system
- A constraint, in combination with the constraint value, indicates that the value is a member of a specified code system
Vocabulary XML
Vocabulary XML is used for Schematron validation. Value sets are bound to constraints in the Template Editor. Only a value set with a Binding value of static is validated by the Schematron. When you export vocabulary XML, only a value set with a Binding value of static is included. A value set with a Binding value of unspecified (empty) or dynamic is ignored. For more information on binding value sets see Bindings in the Constraints section.


This method assumes that the detection efficiency is unknown, but that the materials are pure such that the alpha value calculated from the isotopic values is correct. The point model multiplicity assay equations [19] given in the section “Conventional Multiplicity Assay” are solved from the efficiency, multiplication, and 240Pu effective mass. The point model multiplicity equations are rewritten in the form:
where
Eliminating m and ε from these equations gives a quadratic equation for M:
where
The solutions for the multiplication are solved with the quadratic equation:
where M+ and M- are the two solutions.
Then the two solutions for the efficiency and 240Pu effective mass are:
The solution with valid ranges for the M, ε, and m is chosen as the answer. The ranges are:
M > 1,
0 < ε < 1,
m > 0.
For cases in which there are two valid solutions, the solution with the efficiency closest to the reported efficiency of the counter will be chosen. Also, it is possible to have cases where there will be no solutions. These may occur when the alpha value is significantly different then the alpha value calculated from the isotopic values. In this case the initial assumptions are violated and the solutions are not valid.
The calculation of the errors is very complicated. To simplify the analysis, only the triples rate will be assumed to contribute to the error. The quadratic equation for the multiplication is rewritten in the form:
where
The error in M due only to T is:
where
The error in ε is:
where
The error in m is:


Stackfindover
Sign in to your account
Email
Password
Forgot your password?
Stay signed in for a week
Continue
Use single sign-on (Google) instead
Don't have an account?
Sign up


The steemmonster battles are running now almost one day.
The player leaderboard can be seen only on the website https://steemmonsters.com/:
For calculating the statistics, I scanned all custom_json
blocks with sm_find_match
and sm_team_reveal
from 2018-10-14 21:25:00 to 2018-10-15 20:26:18.
Information about the cards can be received by https://steemmonsters.com/cards/find?ids=
.
It is possible to collect information about used cards and decks, but which deck has won cannot be received from the blockchain or from the API.
Results
4980 different decks have been used. 16340 matches have been played.
Most played decks
| N | summoner | monster |
|---|---|---|
| 619 | Alric Stormbringer | Naga Warrior, Medusa, Crustacean King, Mischievous Mermaid |
| 561 | Zintar Mortalis | Screaming Banshee, Haunted Spirit, Twisted Jester, Undead Priest, Haunted Spider |
| 407 | Zintar Mortalis | Haunted Spirit, Skeleton Assassin, Undead Priest, Haunted Spider, Twisted Jester |
| 392 | Selenia Sky | Stone Golem, Earth Elemental, Swamp Thing, Spirit of the Forest |
| 366 | Selenia Sky | Haunted Spirit, Undead Priest, Haunted Spider, Lightning Dragon |
| 362 | Alric Stormbringer | Medusa, Mischievous Mermaid, Magi Sphinx, Enchanted Pixie |
| 349 | Selenia Sky | Haunted Spirit, Undead Priest, Screaming Banshee, Gold Dragon |
| 339 | Zintar Mortalis | Haunted Spirit, Skeleton Assassin, Haunted Spider, Undead Priest, Twisted Jester |
| 311 | Zintar Mortalis | Haunted Spirit, Undead Priest, Haunted Spider, Screaming Banshee, Twisted Jester |
| 266 | Zintar Mortalis | Haunted Spirit, Undead Priest, Screaming Banshee, Haunted Spider, Twisted Jester |
| 241 | Alric Stormbringer | Naga Warrior, Mischievous Mermaid, Medusa, Crustacean King |
| 214 | Alric Stormbringer | Naga Warrior, Medusa, Mischievous Mermaid, Enchanted Pixie |
| 202 | Zintar Mortalis | Haunted Spirit, Twisted Jester, Undead Priest, Screaming Banshee, Haunted Spider |
| 199 | Alric Stormbringer | Frost Giant, Medusa, Enchanted Pixie, Crustacean King |
| 198 | Selenia Sky | Stone Golem, Earth Elemental, Swamp Thing, Lightning Dragon |
| 197 | Tyrus Paladium | Silvershield Paladin, Defender of Truth, Divine Healer, Air Elemental |
| 188 | Selenia Sky | Stone Golem, Swamp Thing, Goblin Sorcerer, Spirit of the Forest |
| 183 | Alric Stormbringer | Naga Warrior, Medusa, Mischievous Mermaid, Crustacean King |
| 181 | Zintar Mortalis | Haunted Spirit, Dark Enchantress, Undead Priest, Twisted Jester |
| 172 | Lyanna Natura | Stone Golem, Swamp Thing, Goblin Sorcerer, Spirit of the Forest |
| 167 | Alric Stormbringer | Crustacean King, Medusa, Mischievous Mermaid, Magi Sphinx |
| 161 | Alric Stormbringer | Naga Warrior, Crustacean King, Medusa, Mischievous Mermaid |
| 158 | Selenia Sky | Haunted Spirit, Haunted Spider, Undead Priest, Lightning Dragon |
| 158 | Zintar Mortalis | Haunted Spirit, Haunted Spider, Screaming Banshee, Undead Priest, Twisted Jester |
| 157 | Selenia Sky | Serpentine Soldier, Kobold Miner, Fire Beetle, Fire Demon, Goblin Shaman |
| 155 | Alric Stormbringer | Naga Warrior, Mischievous Mermaid, Crustacean King, Medusa |
| 119 | Tyrus Paladium | Silvershield Paladin, Divine Healer, Air Elemental, Peacebringer |
| 118 | Alric Stormbringer | Frost Giant, Medusa, Mischievous Mermaid |
| 117 | Lyanna Natura | Rexxie, Swamp Thing, Spirit of the Forest |
| 112 | Selenia Sky | Haunted Spirit, Undead Priest, Haunted Spider, Screaming Banshee, Twisted Jester |
| 112 | Tyrus Paladium | Clay Golem, Divine Healer, Feral Spirit, Air Elemental |
| 110 | Alric Stormbringer | Spineback Turtle, Crustacean King, Medusa, Mischievous Mermaid |
| 105 | Xander Foxwood | Earth Elemental, Spirit of the Forest, Swamp Thing, Goblin Sorcerer, Elven Cutthroat |
| 104 | Zintar Mortalis | Lord of Darkness, Dark Enchantress, Twisted Jester |
Most often used cards
| N | name | mean xp |
|---|---|---|
| 8946 | Undead Priest | 2016 |
| 8798 | Haunted Spirit | 2220 |
| 7619 | Zintar Mortalis | 1087 |
| 6952 | Selenia Sky | 3056 |
| 6803 | Twisted Jester | 1659 |
| 6711 | Haunted Spider | 1380 |
| 6088 | Alric Stormbringer | 1570 |
| 5077 | Medusa | 1885 |
| 5003 | Crustacean King | 1348 |
| 4705 | Mischievous Mermaid | 1965 |
| 4587 | Screaming Banshee | 2099 |
| 3804 | Skeleton Assassin | 1106 |
| 3519 | Malric Inferno | 1474 |
| 3257 | Swamp Thing | 3095 |
| 3156 | Goblin Shaman | 1888 |
| 3151 | Tyrus Paladium | 1803 |
| 2861 | Lyanna Natura | 1082 |
| 2811 | Divine Healer | 1290 |
| 2724 | Fire Beetle | 1502 |
| 2681 | Kobold Miner | 1926 |
| 2331 | Earth Elemental | 3398 |
| 2228 | Enchanted Pixie | 433 |
| 2172 | Naga Warrior | 3229 |
| 2112 | Lightning Dragon | 2868 |
| 2088 | Goblin Sorcerer | 1417 |
| 2003 | Spirit of the Forest | 3373 |
| 1841 | Stone Golem | 3543 |
| 1823 | Fire Demon | 3327 |
| 1765 | Elven Cutthroat | 594 |
| 1747 | Spineback Turtle | 292 |
| 1720 | Magi Sphinx | 242 |
| 1702 | Feral Spirit | 877 |
| 1695 | Cocatrice | 290 |
| 1627 | Centaur | 336 |
| 1503 | Cerberus | 1614 |
| 1460 | Clay Golem | 1045 |
| 1429 | Water Elemental | 1223 |
| 1406 | Gold Dragon | 3125 |
| 1375 | Serpentine Soldier | 3569 |
| 1321 | Pirate Captain | 525 |
| 1321 | Dark Enchantress | 580 |
| 1305 | Lord of Darkness | 449 |
| 1269 | Air Elemental | 1967 |
| 1263 | Magi of the Forest | 1337 |
| 1239 | Pit Ogre | 1068 |
| 1212 | Rexxie | 589 |
| 1212 | Giant Roc | 478 |
| 1206 | Silvershield Paladin | 3180 |
| 1193 | Flesh Golem | 1349 |
| 1136 | Peacebringer | 1087 |
| 1114 | Frost Giant | 945 |
| 1098 | Silvershield Knight | 298 |
| 1016 | Sabre Shark | 922 |
Most often used unique cards
| N | owner | card | xp |
|---|---|---|---|
| 615 | wonsama | Zintar Mortalis | 0 |
| 615 | wonsama | Haunted Spirit | 0 |
| 615 | wonsama | Undead Priest | 0 |
| 556 | wonsama | Screaming Banshee | 0 |
| 556 | wonsama | Twisted Jester | 0 |
| 556 | wonsama | Haunted Spider | 0 |
| 220 | sanchezpuukko | Magi Sphinx | 0 |
| 215 | zerodashonenine | Malric Inferno | 675 |
| 212 | lunaticpandora | Zintar Mortalis | 0 |
| 210 | zerodashonenine | Goblin Shaman | 420 |
| 210 | lunaticpandora | Undead Priest | 0 |
| 209 | abc.love.steemit | Haunted Spirit | 225 |
| 209 | lunaticpandora | Haunted Spirit | 100 |
| 208 | abc.love.steemit | Zintar Mortalis | 450 |
| 207 | abc.love.steemit | Undead Priest | 300 |
| 207 | lunaticpandora | Twisted Jester | 0 |
| 202 | abc.love.steemit | Screaming Banshee | 0 |
| 201 | abc.love.steemit | Twisted Jester | 150 |
| 190 | lunaticpandora | Screaming Banshee | 0 |
| 189 | lunaticpandora | Haunted Spider | 0 |
| 188 | flemingfarm | Zintar Mortalis | 500 |
| 175 | abc.love.steemit | Haunted Spider | 150 |
| 172 | eonwarped | Lyanna Natura | 300 |
| 172 | eonwarped | Spirit of the Forest | 1000 |
| 172 | imperfect-one | Selenia Sky | 7000 |
| 171 | eonwarped | Swamp Thing | 875 |
| 170 | sanchezpuukko | Enchanted Pixie | 0 |
| 165 | eonwarped | Goblin Sorcerer | 160 |
| 165 | onetin84 | Selenia Sky | 7000 |
| 164 | redbikk | Lord of Darkness | 0 |
| 162 | wizardave | Alric Stormbringer | 300 |
| 162 | wizardave | Crustacean King | 60 |
| 161 | jazzhero | Zintar Mortalis | 4500 |
| 161 | jazzhero | Haunted Spirit | 4500 |
| 160 | jazzhero | Undead Priest | 2500 |
| 160 | jazzhero | Twisted Jester | 2500 |
| 160 | sanchezpuukko | Medusa | 3500 |
| 159 | wizardave | Enchanted Pixie | 150 |
| 158 | jazzhero | Skeleton Assassin | 2560 |
| 158 | jazzhero | Haunted Spider | 1560 |
| 157 | the01crow | Selenia Sky | 7000 |
| 156 | wizardave | Medusa | 300 |
| 156 | zerodashonenine | Hydra | 0 |
| 156 | sanchezpuukko | Mischievous Mermaid | 500 |
| 156 | marabara | Selenia Sky | 7000 |
| 156 | rondras | Selenia Sky | 7000 |
| 156 | redbikk | Undead Priest | 750 |
| 155 | sanchezpuukko | Alric Stormbringer | 300 |
| 153 | the.foodini | Zintar Mortalis | 0 |
| 153 | the.foodini | Haunted Spirit | 0 |
| 153 | the.foodini | Twisted Jester | 0 |
| 153 | the.foodini | Undead Priest | 0 |
| 152 | mattclarke | Goblin Sorcerer | 250 |
| 151 | wizardave | Frost Giant | 1000 |
| 151 | eonwarped | Stone Golem | 300 |
| 150 | abdullar | Selenia Sky | 7000 |
| 150 | flemingfarm | Twisted Jester | 500 |
| 150 | redbikk | Screaming Banshee | 0 |
| 147 | cahlen | Tyrus Paladium | 8500 |
| 146 | cahlen | Silvershield Paladin | 8500 |
| 145 | cranium | Alric Stormbringer | 0 |
| 144 | cranium | Mischievous Mermaid | 0 |
| 142 | gunsmithing | Selenia Sky | 3000 |
| 141 | cranium | Medusa | 0 |
| 139 | flemingfarm | Dark Enchantress | 750 |
| 138 | cahlen | Air Elemental | 3750 |
| 138 | zerodashonenine | Fire Beetle | 255 |
| 137 | chrisroberts | Mischievous Mermaid | 7750 |
| 136 | gunsmithing | Gold Dragon | 3000 |
| 135 | chrisroberts | Alric Stormbringer | 8500 |
| 134 | chrisroberts | Crustacean King | 3200 |
| 133 | chrisroberts | Medusa | 8500 |
| 133 | mattclarke | Magi of the Forest | 3750 |
| 132 | wombykus | Selenia Sky | 7000 |
| 132 | xerox-bru | Selenia Sky | 1000 |
| 131 | chrisroberts | Naga Warrior | 7750 |
| 131 | mmckersie | Malric Inferno | 300 |
| 130 | fenrir78 | Selenia Sky | 7000 |
| 129 | mmckersie | Elven Cutthroat | 195 |
| 129 | mmckersie | Kobold Miner | 60 |
| 128 | lec | Selenia Sky | 0 |
| 123 | abh12345 | Fire Demon | 1000 |
| 123 | mmckersie | Goblin Shaman | 90 |
| 122 | nateaguila | Zintar Mortalis | 8550 |
| 122 | nateaguila | Haunted Spirit | 8550 |
| 122 | nateaguila | Undead Priest | 8550 |
| 122 | nateaguila | Haunted Spider | 7560 |
| 122 | abh12345 | Goblin Shaman | 2600 |
| 120 | abh12345 | Fire Beetle | 1200 |
| 120 | beco132 | Tyrus Paladium | 0 |
| 120 | beco132 | Silvershield Knight | 0 |
| 118 | planosdeunacasa | Selenia Sky | 0 |
| 118 | rafalski | Hydra | 0 |
| 118 | cyan2017 | Selenia Sky | 7000 |
| 117 | xunityx | Twisted Jester | 1500 |
| 117 | xunityx | Haunted Spider | 765 |
| 117 | pachu | Alric Stormbringer | 100 |
| 117 | pachu | Medusa | 0 |
| 117 | pachu | Mischievous Mermaid | 0 |
| 117 | beco132 | Elven Cutthroat | 0 |
| 117 | beco132 | Feral Spirit | 0 |
| 116 | abh12345 | Hydra | 1500 |
| 116 | karenmckersie | Selenia Sky | 1000 |
| 116 | rakkasan84 | Selenia Sky | 7000 |
| 116 | nateaguila | Twisted Jester | 8550 |
| 115 | kingtherion | Haunted Spirit | 400 |
| 115 | kingtherion | Twisted Jester | 400 |
| 114 | tr777 | Haunted Spirit | 8500 |
| 113 | pachu | Enchanted Pixie | 0 |
| 113 | agr8buzz | Haunted Spirit | 8500 |
| 113 | tr777 | Undead Priest | 8500 |
| 113 | cahlen | Peacebringer | 2500 |
| 113 | beco132 | Enchanted Pixie | 0 |
| 112 | karenmckersie | Spirit of the Forest | 3000 |
| 112 | zerodashonenine | Kobold Miner | 180 |
| 111 | direwolf | Alric Stormbringer | 8500 |
| 110 | cryplectibles | Divine Healer | 460 |
| 110 | beco132 | Cocatrice | 0 |
| 110 | kingtherion | Undead Priest | 400 |
| 109 | agr8buzz | Selenia Sky | 7000 |
| 109 | clove71 | Selenia Sky | 7000 |
| 109 | onetin84 | Goblin Shaman | 7560 |
| 109 | mattclarke | Lyanna Natura | 2500 |
| 109 | surfknasen | Alric Stormbringer | 1500 |
| 109 | thebluewin | Alric Stormbringer | 1500 |
| 109 | thebluewin | Medusa | 300 |
| 109 | thebluewin | Mischievous Mermaid | 1750 |
| 108 | generausd | Zintar Mortalis | 400 |
| 108 | generausd | Haunted Spider | 80 |
| 108 | generausd | Screaming Banshee | 0 |
| 108 | generausd | Undead Priest | 400 |
| 108 | onetin84 | Serpentine Soldier | 8500 |
| 108 | onetin84 | Kobold Miner | 7560 |
| 108 | onetin84 | Fire Demon | 7750 |
| 107 | generausd | Spineback Wolf | 180 |
| 107 | luxio | Alric Stormbringer | 0 |
| 107 | erodedthoughts | Undead Priest | 2500 |
| 107 | onetin84 | Fire Beetle | 7560 |
| 107 | flauwy | Selenia Sky | 7000 |
| 107 | cranium | Naga Warrior | 0 |
| 107 | mattclarke | Swamp Thing | 4250 |
| 107 | surfknasen | Mischievous Mermaid | 1250 |
| 107 | surfknasen | Medusa | 1100 |
| 107 | cyan2017 | Haunted Spirit | 8500 |
| 107 | cyan2017 | Undead Priest | 8500 |
| 105 | agr8buzz | Undead Priest | 2500 |
| 105 | pachu | Naga Warrior | 0 |
| 105 | encryptdcouple | Selenia Sky | 0 |
| 105 | flemingfarm | Lord of Darkness | 0 |
| 105 | luxio | Mischievous Mermaid | 0 |
| 105 | erodedthoughts | Haunted Spider | 1400 |
| 104 | xunityx | Screaming Banshee | 875 |
| 104 | agr8buzz | Haunted Spider | 380 |
| 103 | xerox-bru | Haunted Spider | 360 |
| 103 | xerox-bru | Skeleton Assassin | 360 |
| 103 | xerox-bru | Twisted Jester | 300 |
| 102 | bafi | Haunted Spider | 1755 |
| 102 | mmunited | Tyrus Paladium | 750 |
| 102 | mulletwang | Undead Priest | 4700 |
| 102 | direwolf | Crustacean King | 2560 |
| 102 | lec | Lightning Dragon | 0 |
| 102 | tr777 | Haunted Spider | 7560 |
| 102 | xerox-bru | Haunted Spirit | 700 |
| 102 | xerox-bru | Undead Priest | 300 |
| 101 | mmunited | Air Elemental | 875 |
| 101 | mulletwang | Haunted Spirit | 9200 |
| 101 | tailcock | Xia Seachan | 1575 |
| 100 | nateaguila | Screaming Banshee | 7875 |
| 100 | kiokizz | Haunted Spider | 440 |
| 100 | chacek | Zintar Mortalis | 150 |
| 100 | chacek | Haunted Spirit | 450 |
This page is synchronized from the post: ‘steemmonsters deck and card statistics for day 1’


A package for simulation of queueing systems.
In the package, we use three important concepts:
- Jobs (
interface SimJob
): a job represents an amount of work to be carried out by one or more queueing
systems, abbreviated as queues;
- Queues (
interface SimQueue
): a queue is an abstract waiting line holding jobs
to be served by one or more servers associated with the queue;
- Entities (
interface SimEntity
):
the common part of jobs and queues (naming, event list, notifications, etc).
The so-called queue discipline determines in what order jobs are served by the server(s).
Notes:
- This package depends on the
jsimulation
package.
- This package focuses exclusively on modeling and simulation of the queueing systems themselves;
it currently does not feature adequate random-number and stochastic-process generation
and only basic statistics
(mostly because we believe there are extremely good Java libraries for that already).
- This top-level package contains the essential interfaces of a simulation entity,
and a partial implementation. The sub-packages contain extensions to the basis entity interfaces (including for
jobs and queues), and (concrete) implementations.
Author: Jan de Jongh, TNO
Copyright (C) 2005-2017 Jan de Jongh, TNO
This file is covered by the LICENSE file in the root of this project.


Payment form example
Card #
CVC #
Amount
$
First name
Last name
City
State
Choose...
San José
Alajuela
Heredia
Cartago
Puntarenas
Guanacaste
Limón
Postal Code
We accept:
Message
Comments
Add any notes here.
Cancel
Send


Avalanche
Download
Avalanche. Remastered for the iPhone.
Download
Coming soon
January 2018
This button does nothing. Sorry about that. I promise it will go somewhere soon.


org-mode 结构
Table of Contents
org-mode structure
Text in org is structured by headings, denoted by lines starting with one or more * so we are currently in a section!
A subheading
Starts with an extra * and so on
navigation
Headings can be expanded or collapsed by moving to the (sub)heading and pressing TAB. S-TAB cycles all headings. You can jump to next and previous headings with C-c C-n and C-c C-p respectively.
You can move headings up and down to reorder them with the arrow keys, using M-up or M-down. You can change the level of headings with M-left and M-right (and use M-S-left and M-S-right to also change the levels of and subheadings).
lists
bullet lists
- bullet lists can be created like this (start a line with one or more space and a -
- pressing M-RET gives you a new bullet
- we might also like nested bullets
- like this one (I pressed M-RET TAB to indent it)
- and another (M-RET now indents to the new level)
- the nice thing is that for long lines of text, emacs wraps them so that they line up with the bullet
- you can also reorder list items and change indentation using M-up or M-down just like with section headings
- you can change bullet style using S-left and S-right
numbered lists
- numbered lists are also possible
- M-RET gives me a new number
checklists [0/5]
[ ]
we can even have check lists[ ]
M-S-RET gives a new item with a check box[ ]
C-c C-c check/unchecks a box[ ]
you can have sub items[ ]
like this[ ]
that can be checked off individually
[ ]
and you can track the number of items by adding[0/0]
to the end of a line above a checklist - this updates when you check items off
definition lists
- definition lists
- these are useful sometimes
- item 2
- M-RET again gives another item, and long lines wrap in a tidy way underneath the definition


{% extends "core/layout.html" %} {% block custom_head %} {% endblock %} {% block main %}
Visualize routes using a graph. Basically we're using a D3 force layout but arranged as a force-directed tree as shown here. This way you can track the network packages within several paths.
Check out the CSS file to see the circles color legend.
You'll need some data to visualize. Open a shell and paste this into it (make sure you adapt the command line to your system, e.g. change the NIC interface name):
$ stdbuf -oL traceroute dornea.nu | egrep -w --line-buffered '^ [0-9]{1,3} [^*\].*ms.*' | stdbuf -oL awk -f web/mod_traceroute/scripts/traceroute.awk | stdbuf -oL sed 's/"/\\"/g' | xargs -n 1 -I % sh -c "echo '%' | nc localhost 8081"


| |||||||
| FRAMES NO FRAMES |
For more information, see the Animation Wiki Documentation.
| Tag Information | |
| Tag Class | None |
| TagExtraInfo Class | None |
| Body Content | JSP |
| Display Name | None |
| Attributes | ||||
| Name | Required | Request-time | Type | Description |
| duration | no | false | java.lang.Double | Length of effect in milliseconds. The default value is 500 for free-form animations and varies for pre-defined effects. |
| easing | no | false | java.lang.String | Specifies the variation of the rate at which an animation progresses. Possible values are swing, easeInQuad, easeOutQuad, easeInOutQuad, easeInCubic, easeOutCubic, easeInQuart, easeOutQuart, easeInOutQuart, easeInQuint, easeOutQuint, easeInOutQuint, easeInSine, easeOutSine, easeInOutSine, easeInExpo, easeOutExpo, easeInOutExpo, easeInCirc, easeOutCirc, easeInOutCirc, easeInElastic, easeOutElastic, easeInOutElastic, easeInBack, easeOutBack, easeInOutBack, easeInBounce, easeOutBounce, easeInOutBounce. |
| effectObject | no | false | org.icefaces.ace.component.animation.Effect | The Effect object that contains the effect specifications to apply. |
| event | no | false | java.lang.String | Name of the event that will trigger the animation (e.g. 'click'). The event must be supported by the component. The TLD documentation of each standard JSF component lists which events are supported, which usually map to standard DOM events. The event name must be entered without the 'on' prefix (e.g. for 'onmousemove' the value of this attribute must be 'mousemove'). |
| from | no | false | java.lang.String | CSS properties to transition from (e.g. {height:20, color:'#222'}). |
| iterations | no | false | java.lang.Integer | Number of times the animation is to be repeated. |
| name | no | false | java.lang.String | The name of the effect, when using pre-defined effects like 'fade' and 'highlight'. Use 'anim' for free-form animations or simply omit this attribute. |
| run | no | false | boolean | (Deprecated) Boolean value that specifies whether to run the application or not. |
| to | no | false | java.lang.String | CSS properties to transition to (e.g. {height:100, color:'#CCC'}). |
| Variables | No Variables Defined. |
| |||||||
| FRAMES NO FRAMES |


A B C D E F G H I J K L M N O P Q R S T U V W _
All Classes All Packages
All Classes All Packages
All Classes All Packages
R
- R1 - Static variable in class org.apache.hive.common.util.Murmur3
- R1_32 - Static variable in class org.apache.hive.common.util.Murmur3
- R2 - Static variable in class org.apache.hive.common.util.Murmur3
- R2_32 - Static variable in class org.apache.hive.common.util.Murmur3
- R3 - Static variable in class org.apache.hive.common.util.Murmur3
- read() - Method in class org.h2.util.ScriptReader
- readAsText(Path) - Static method in class org.fbsql.servlet.StringUtils
- readBuffer() - Method in class org.h2.util.ScriptReader
- reader - Variable in class org.h2.util.ScriptReader
- readSqlScriptToList(String, List<String>) - Static method in class org.fbsql.servlet.SqlParseUtils
-
Parse SQL script by splitting it on SQL statements Standard semicolon character «;» is used as statement separator.
- readStatement() - Method in class org.h2.util.ScriptReader
-
Read a statement from the reader.
- readStatementLoop() - Method in class org.h2.util.ScriptReader
- ReadyResult - Class in org.fbsql.servlet
-
DTO (Data Transfer Object) that represents cached result of SQL statement execution
- ReadyResult() - Constructor for class org.fbsql.servlet.ReadyResult
- registerJdbcDriver(String, List<String>) - Static method in class org.fbsql.servlet.ClassLoaderUtils
-
Register JDBC driver DriverManager will refuse to use a driver not loaded by the system ClassLoader The workaround for this is to use a shim class that implements java.sql.Driver.
- REJECT - Static variable in class org.fbsql.antlr4.generated.FbsqlLexer
- REJECT - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- REJECT() - Method in class org.fbsql.antlr4.generated.FbsqlParser.Connect_to_stmtContext
- REJECT(int) - Method in class org.fbsql.antlr4.generated.FbsqlParser.Connect_to_stmtContext
- releaseConnection(DbConnection) - Method in class org.fbsql.connection_pool.ConnectionPoolManager
-
Release connection
- remarkStart - Variable in class org.h2.util.ScriptReader
-
The position in buffer of start of comment
- REQUEST_ATTRIBUTE_SESSION_ID - Static variable in class org.fbsql.servlet.DbServlet
-
Custom HttpServletRequest attribute name to store session ID
- REQUEST_ATTRIBUTE_USER - Static variable in class org.fbsql.servlet.DbServlet
-
Custom HttpServletRequest attribute name to store user name
- RESULT_FORMAT_ARRAY_OF_ARRAYS - Static variable in class org.fbsql.servlet.QueryUtils
-
Format results as JSON array of arrays 2D-array (this format may be useful in case you want to hide ResultSet column names from client)
- RESULT_FORMAT_ARRAY_OF_OBJECTS - Static variable in class org.fbsql.servlet.QueryUtils
-
Format results as JSON array of objects Default format
- resultSetFormat - Variable in class org.fbsql.servlet.StaticStatement
-
Result set JSON format
- resutlSetToListOfMaps(ResultSet) - Static method in class org.fbsql.servlet.QueryUtils
-
Converts ResutlSet to list of maps
- resutlSetToListOfMapsJsonValues(ResultSet, Base64.Encoder) - Static method in class org.fbsql.servlet.QueryUtils
- RhinoUtils - Class in org.fbsql.servlet
- RhinoUtils() - Constructor for class org.fbsql.servlet.RhinoUtils
- role_name() - Method in class org.fbsql.antlr4.generated.FbsqlParser.Declare_statement_stmtContext
- role_name() - Method in class org.fbsql.antlr4.generated.FbsqlParser
- role_name(int) - Method in class org.fbsql.antlr4.generated.FbsqlParser.Declare_statement_stmtContext
- Role_nameContext(ParserRuleContext, int) - Constructor for class org.fbsql.antlr4.generated.FbsqlParser.Role_nameContext
- roles - Variable in class org.fbsql.antlr4.parser.ParseStmtDeclareStatement.StmtDeclareStatement
- ROLES - Static variable in class org.fbsql.antlr4.generated.FbsqlLexer
- ROLES - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- ROLES() - Method in class org.fbsql.antlr4.generated.FbsqlParser.Declare_statement_stmtContext
- ROLES(int) - Method in class org.fbsql.antlr4.generated.FbsqlParser.Declare_statement_stmtContext
- RULE_compression_level - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_connect_to_stmt - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_connection_alias - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_connection_pool_size_max - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_connection_pool_size_min - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_cron_expression - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_declare_procedure_stmt - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_declare_statement_stmt - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_include_script_file_stmt - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_jar_file - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_jdbc_connection_properties - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_jdbc_driver_class_name - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_jdbc_url - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_json - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_json_file - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_native_sql - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_native_stmt - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_parameter - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_password - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_procedure - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_procedure_name - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_role_name - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_schedule_stmt - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_sql_script_file - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_statement_alias - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_switch_to_stmt - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_trigger_after_procedure_name - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_trigger_before_procedure_name - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- RULE_user - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- ruleNames - Static variable in class org.fbsql.antlr4.generated.FbsqlLexer
- ruleNames - Static variable in class org.fbsql.antlr4.generated.FbsqlParser
- run() - Method in class org.fbsql.servlet.DbRequestProcessor
-
Implementation of Runnable.run() method Overview of request processor logic - Parse request body - Check SQL statement against white list (list of allowed SQL statements) - Execute SQL statement if allowed
- RunnableJob - Class in org.fbsql.servlet
-
Represent a 'job' to be performed.
- RunnableJob() - Constructor for class org.fbsql.servlet.RunnableJob
All Classes All Packages


Campaign Definition
Target Groups
Campaign Details
Incentives
Targets
You can define as many target groups or edit existing ones
Target Group
Young tier2 males
Young tier3 males
Young tier4 males
Young tier5 males
Target Group Definition
Total Population: 1.2 Million
Gender
Male
Female
Age
Geo
Metros
Tier 2
Tier 3
Create your own..
Employer
IT
Banking
Fortune 500
Create your own..
Interests
Online Shopper
Working Moms
Housewives
Create your own..
Relationship
Single
Married
Divorcee
Parent
Engaged


Points from test: {{ points }}
Rounded points are: {{ points | pointsRoundedUp }}
Final grade: A
Final grade: B
Final grade: C
Final grade: D
Final grade: E
Final grade: F


Use the button above to generate network logs for diagnosis purpose. This will only generate network logs for the current tab.
Important : The network logs could contain credentials to the websites you will visit with this tab. Treat the generated logs as if it contained your passwords and ony send it to trusted contacts.


UNISA responds to latest exam leaks
by Algoa FMThe University of South Africa (UNISA) said on Wednesday that it had introduced additional control measures at all examination centers after reports of papers being leaked.
This is the second time this year that exam leaks have affected the distance learning institute.
In the latest incident, 17 modules were compromised by being leaked just before students sit for their final examinations.
UNISA has, however, insisted that its assessments can still be trusted.
UNISA announced that it would stop the in-house printing of exam papers in an effort to avoid leaks.
Spokesperson Martin Ramotshela says they are of the firm view that the overall examination process remains reliable and intact.
There were 2077 question papers being written by 298 662 students.
Ramotshela said on Monday that the institution was on the trail of an individual implicated in the leaks.
"The university wishes to assure all stakeholders that it takes this matter very seriously and that its investigation into the leakages, conducted jointly with the police since the May/June 2019 exam, is at an advanced stage and a breakthrough in this regard should be imminent," he said
The university said it would continue to pay close attention to the examination sessions until the last day of writing to prevent any further leaks.
Anyone with information on the leaks is urged to contact the police or toll-free Whistleblower Hotline on 0860 00 5050, or send an email to<EMAIL_ADDRESS>- African News Agency (ANA)


out.remove(line)
// Check output.
if out != _OUT_EXPECTED:
raise SystemExit("Subprocess did not print ONE, TWO, THREE in correct order.")
if out != _OUT_EXPECTED:
print(" +++++++ SUBPROCESS ERROR OUTPUT +++++++")
print(err)
raise SystemExit("Subprocess did not print ONE, TWO, THREE in correct order. "
"(output was %r, return code was %s)" % (out, proc.returncode))


Jack Koppa
Web Developer
|
Cleantech Advocate
Featured Work
Chanje
http://chanje.us
FrackMented
https://github.com/jackkoppa/FrackMented
PixBox
http://jackkoppa.com/work/pixbox/


Label: D1. Importance of refugees,asylum seekers
Name: D1REFUGE
Numcats: 5
Val Range Max: 4.0
Val Range Max: 1.0
complete: true
creationDate: 2010-07-01 10:22:18.0
name: D1REFUGE
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
width: 2
numCats: 5
isKey: false
isWeight: false
noInvalidResponses: 79
decimalPlaces: 0
valRangeMax: 4.0
valRangeMin: 1.0
questionText: 8. Refugees and asylum seekers
missingValues: -1
intervl: discrete
format: numeric
formatSchema: other
varID: V145
noValidResponses: 1931
position: 145
preQuestionText: D.1. Here is a list of important issues that were discussed during the election campaign. When you were deciding about how to vote, how important was each of these issues to you personally?
sections_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V145@sections
measures_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V145@measures
statistics_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V145@statistics
datafile_attribute_resource: http://palo.anu.edu.au:80/obj/fDatafile/au.edu.anu.assda.ddi.01048_F1
groups_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V145@groups
factsheets_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V145@factsheets
tables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V145@tables
weightVariables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V145@weightVariables
section_attribute_resource: http://palo.anu.edu.au:80/obj/fSection/au.edu.anu.assda.ddi.01048_VG26F1
Label: D1. Importance of defence,national security
Name: D1DEFENC
Numcats: 5
Val Range Max: 4.0
Val Range Max: 1.0
decimalPlaces: 0
complete: true
creationDate: 2010-07-01 10:22:18.0
name: D1DEFENC
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
width: 2
numCats: 5
isKey: false
isWeight: false
noInvalidResponses: 77
valRangeMax: 4.0
valRangeMin: 1.0
questionText: 9. Defence and national security
missingValues: -1
intervl: discrete
format: numeric
formatSchema: other
varID: V146
noValidResponses: 1933
position: 146
preQuestionText: D.1. Here is a list of important issues that were discussed during the election campaign. When you were deciding about how to vote, how important was each of these issues to you personally?
sections_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V146@sections
measures_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V146@measures
statistics_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V146@statistics
datafile_attribute_resource: http://palo.anu.edu.au:80/obj/fDatafile/au.edu.anu.assda.ddi.01048_F1
groups_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V146@groups
factsheets_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V146@factsheets
tables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V146@tables
weightVariables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V146@weightVariables
section_attribute_resource: http://palo.anu.edu.au:80/obj/fSection/au.edu.anu.assda.ddi.01048_VG26F1
Label: D2. Party closest to own view refugees,asylum seekers
Name: D2REFUGE
Numcats: 5
Val Range Max: 4.0
Val Range Max: 1.0
complete: true
creationDate: 2010-07-01 10:22:18.0
name: D2REFUGE
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
width: 2
numCats: 5
isKey: false
isWeight: false
noInvalidResponses: 121
decimalPlaces: 0
valRangeMax: 4.0
valRangeMin: 1.0
questionText: 8. Refugees and asylum seekers
missingValues: -1
intervl: discrete
format: numeric
formatSchema: other
varID: V157
noValidResponses: 1889
position: 157
preQuestionText: D.1. Here is a list of important issues that were discussed during the election campaign. When you were deciding about how to vote, how important was each of these issues to you personally? D.2. Still thinking about these same issues, whose policies-the Labor Party's or the Liberal-National Coalition's-would you say come closer to your own views on each of these issues?
sections_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V157@sections
measures_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V157@measures
statistics_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V157@statistics
datafile_attribute_resource: http://palo.anu.edu.au:80/obj/fDatafile/au.edu.anu.assda.ddi.01048_F1
groups_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V157@groups
factsheets_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V157@factsheets
tables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V157@tables
weightVariables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V157@weightVariables
section_attribute_resource: http://palo.anu.edu.au:80/obj/fSection/au.edu.anu.assda.ddi.01048_VG27F1
Label: D2. Party closest to own view defence,national security
Name: D2DEFENC
Numcats: 5
Val Range Max: 4.0
Val Range Max: 1.0
decimalPlaces: 0
isWeight: false
noInvalidResponses: 125
complete: true
creationDate: 2010-07-01 10:22:18.0
name: D2DEFENC
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
width: 2
numCats: 5
isKey: false
valRangeMax: 4.0
valRangeMin: 1.0
questionText: 9. Defence and national security
missingValues: -1
intervl: discrete
format: numeric
formatSchema: other
varID: V158
noValidResponses: 1885
position: 158
preQuestionText: D.1. Here is a list of important issues that were discussed during the election campaign. When you were deciding about how to vote, how important was each of these issues to you personally? D.2. Still thinking about these same issues, whose policies-the Labor Party's or the Liberal-National Coalition's-would you say come closer to your own views on each of these issues?
sections_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V158@sections
measures_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V158@measures
statistics_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V158@statistics
datafile_attribute_resource: http://palo.anu.edu.au:80/obj/fDatafile/au.edu.anu.assda.ddi.01048_F1
groups_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V158@groups
factsheets_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V158@factsheets
tables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V158@tables
weightVariables_attribute_resource: http://palo.anu.edu.au:80/obj/fVariable/au.edu.anu.assda.ddi.01048_V158@weightVariables
section_attribute_resource: http://palo.anu.edu.au:80/obj/fSection/au.edu.anu.assda.ddi.01048_VG27F1
• Label: G6. Truely Australian-born in Aust
Name: G6P1
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:19.0
name: G6P1
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
Label: G6. Truely Australian-Aust citizenship
Name: G6P2
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G6P2
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
• Label: G6. Truely Australian-live Aust most of life
Name: G6P3
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G6P3
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
• Label: G6. Truely Australian-speak English
Name: G6P4
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G6P4
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
Label: G6. Truely Australian-being Christian
Name: G6P5
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G6P5
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
• Label: G6. Truely Australian-respect Aust laws
Name: G6P6
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G6P6
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
Label: G6. Truely Australian-feeling Australian
Name: G6P7
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G6P7
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
Label: G10. Important for Aust Aboriginies recognised
Name: G10P6
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G10P6
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
Label: G11. Racial prejudgice against Asians
Name: G11
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G11
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
Label: G22. Quiz: 75 membs House of Reps
Name: G22P2
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G22P2
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048
• Label: G22. Quiz: Stand for Parli must pay deposit
Name: G22P5
Numcats:
Val Range Max:
Val Range Max:
creationDate: 2010-07-01 10:22:20.0
name: G22P5
study_attribute_resource: http://palo.anu.edu.au:80/obj/fStudy/au.edu.anu.assda.ddi.01048


Usage: sxx [options] [ FILE.x [ arguments for FILE.x ] ]
Run from a Windows Terminal window (wt.exe).
If sxx is run without a FILE parameter, sxx starts the System X shell (sh.x).
sxx
| long option | short option | description | notes |
|---|---|---|---|
| ‑‑help | ‑h | Print help and exit. | |
| ‑‑verbose | ‑v | Be verbose. | |
| ‑‑debug=MODE | ‑d=MODE | Set kernel debug mode to MODE (1-63). | When kernel is started in debug mode != 0 kernel debug messages show up in a 'cmlog' command-line application if it is started. Mode should be the sum of the following values: MODE=1: show system errors MODE=2: show terminal input messages MODE=4: show message queue messages MODE=8: show shell messages MODE=16: show lexer messages MODE=32: show application messages |
If --verbose option is given, the executor prints execution statistics after a command has been run:
sxx --verbose fibonacci.x running '.../fibonacci.x'... 21 '.../fibonacci.x' exited with code 0 user time: 00:00:00.000.885 (59.5118%) sleep time: 00:00:00.000.000 (0%) system time: 00:00:00.000.602 (40.4882%) total time: 00:00:00.001.487 child user time: 00:00:00.000.000 (0%) child sleep time: 00:00:00.000.000 (0%) child system time: 00:00:00.000.000 (0%) child total time: 00:00:00.000.000
| value | description |
|---|---|
| user time | the duration that the virtual machine processor threads has executed the user process |
| sleep time | the duration that the user process has been asleep waiting for I/O or exit of a child process |
| system time | the duration that the virtual machine processor threads has executed kernel interrupts |
| child user time | user time of the direct child processes of the top level process (child processes of the children not accounted) |
| child sleep time | sleep time of the direct child processes of the top level process (child processes of the children not accounted) |
| child system time | system time of the direct child processes of the top level process (child processes of the children not accounted) |


This module is written to use the new Lua 5.1 package system. To use this module, you need to do:
local srv = require("OpenID.server")
This will put the OpenID.server package namespace into the srv table. To use the server you must set and call:
srv.auth_func = your_auth_function
srv.setup = your_setup_URL
srv.srv_secret = your_server_secret
srv.process_query()
Note that this package is not a complete stand-alone server implementation. In particular, you must provide the user login system via a custom auth_function and setup page that you provide to the server. For more details see the API description and the example implementation.
This property must be set to your custom authorization function. This function must accept a single parameter that will contain a table with the parsed identity URL. The URL is parsed using LuaSocket, and the resultant table will look like:
parsed_url = {
url = string,
scheme = string,
authority = string,
path = string,
params = string,
query = string,
fragment = string,
userinfo = string,
host = string,
port = string,
user = string,
password = string
}
The function must decide if the currently logged-in user (presumably determined via session-cookies or whatever) owns the identity URL provided. The function should return a true value if the user owns the identity, or false otherwise. The function may also return a second result, which should be a table, that includes extra parameters to provide to your setup URL, if neeeded.
This property should be set to the full, canonical URL for your setup page. This is the page to which the user agent will be forwarded in the event that you cannot assert their ownership of the identity being checked. This may be because they are not logged in or because they have not yet given permission for the consumer to authenticate this identity. In addition, this setup page should preserve any openid parameters that are provided and pass them on to the return_to URL if it is provided.
The server secret property should be set to a string value to use for generating shared secrets. This value should be unique and truly secret; anyone that knows your server secret can spoof your identity server's authentications. The more often this is changed, the more often existing assoc_handles will have to be invalidated.
The log path property indicates where to write a server log file, if any.
The log level property indicates at what level of detail to log server information. The default is 0, which is no logging at all. For maximum detail, use level 3.
The adpage property provides the full, canonical URL for an ad page to display if someone hits the server URL directly with no parameters. If set to nil (the default), a simple OpenID notice page will be generated.
This function handles all OpenID server processing. It should generally be called from a stand-alone script that does very little except set the required server properties before making this call.
This module only provides OpenID server functionality; it does not provide a fully functional user management system. To demonstrate how this module would interact with a full implementation, an example implementation has been provided with the source code. This example uses a trivial and insecure user login sytem to demonstrate the basic concepts.
To setup the example implementation, update the files "alice.html", "bob.html", and "users.lua" with your site-specific details. The configuration section in "users.lua" contains these settings:
The OpenID server URLs in the pages "alice.html" and "bob.html" must also be updated to match your site setup. You may also need to update the shebang (#!) lines in the "setup.cgi" and "server.cgi" files to reference your local lua binary if it is in a non-standard location. Finally, you of course must have installed the OpenID.server module in a library path accessible to your Lua interpreter.
To test it, simple hit the "index.html" page provided and follow the directions. If you have not set the required parameters, a "400 Bad Request" page will be generated when you hit the server script. If there are any Lua issues you will probably get a "500 Internal Server Error", and your web-server logs will be your best source of information. Any other issues can probably be identified by enabling logging in the OpenID.server module and setting the logging detail to the maximum level.
The example implementation has several components. The first is the "server.cgi" script which sets the basic server properties and runs the server processing query. This script provides the entry point for all OpenID requests using the OpenID.server module for most of its functionality. The "setup.cgi" script provides a trivial user login system that uses a simple (and insecure) cookie to maintain state. Finally, the "users.lua" library provides an auth function for the server module and basic user management and configuration details for the entire implementation.


Translations
Theme localization guide.
The built-in themes that are included with MkDocs provide support for translations. This is a guide for translators, which documents the process for contributing new translations and/or updating existing translations. For guidance on modifying the existing themes, see the Contributing Guide. To enable a specific translation see the documentation about the specific theme you are using in the User Guide. For translations of third-party themes, please see the documentation for those themes. For a third-party theme to make use of MkDocs’ translation tools and methods, that theme must be properly configured to make use of those tools.
!!! note
Translations only apply to text contained within a theme's template, such
as "next" and "previous" links. The Markdown content of a page is not
translated. If you wish to create multilingual documentation, you need to
combine theme localization with a third-party
internationalization/localization plugin.
Localization tooling prerequisites
Theme localization makes use of the babel project for generation and
compilation of localization files. Custom commands are available from the
MkDocs’ setup.py
script as described below to assist with the process of
updating and contributing translations. You will need to be working from the
git working tree on your local machine to make use of the helper scripts.
See the Contributing Guide for direction on how to Install for Development and Submit a Pull Request. The instructions in this document assume that you are working from a properly configured development environment.
Make sure translation requirements are installed in your environment:
pip install mkdocs[i18n]
Adding language translations to themes
If your favorite language locale is not yet supported on one (or both) of the
built-in themes (mkdocs
and readthedocs
), you can easily contribute a
translation by following the steps below.
Here is a quick summary of what you’ll need to do:
- Initialize new localization catalogs for your language (if a translation for your locale already exists, follow the instructions for updating theme localization files instead).
- Add a translation for every text placeholder in the localized catalogs.
- Locally serve and test the translated themes for your language.
- Update the documentation about supported translations for each translated theme.
- Contribute your translation through a Pull Request.
!!! note
Translation locales are usually identified using the [ISO-639-1] (2-letter)
language codes. While territory/region/county codes are also supported,
location specific translations should only be added after the general
language translation has been completed and the regional dialect requires
use of a term which differs from the general language translation.
Initializing the localization catalogs
The templates for each theme contain text placeholders that have been extracted
into a Portable Object Template (messages.pot
) file, which is present in each
theme’s folder.
Initializing a catalog consists of running a command which will create a
directory structure for your desired language and prepare a Portable Object
(messages.po
) file derived from the pot
file of the theme.
Use the init_catalog
command on each theme (-t <theme>
) and provide the
appropriate language code (-l <language>
). For example, to add a translation
for the Spanish es
language to the mkdocs
theme, run the following command:
python setup.py init_catalog -t mkdocs -l es
The above command will create the following file structure:
mkdocs/themes/mkdocs/locales
├── es
│ └── LC_MESSAGES
│ └── messages.po
You can now move on to the next step and add a translation for every text placeholder in the localized catalog.
Updating a theme translation
If a theme’s messages.pot
template file has been updated
since the messages.po
was last updated for your locale, follow the steps
below to update the theme’s messages.po
file:
- Update the theme’s translation catalog to refresh the translatable text placeholders of each theme.
- Translate the newly added translatable
text placeholders on every
messages.po
catalog file language you can. - Locally serve and test the translated themes for your language.
- Contribute your translation through a Pull Request.
Updating the translation catalogs
This step should be completed after a theme template have been updated for each language that you are comfortable contributing a translation for.
To update the fr
translation catalog of the mkdocs
theme, use the following
command:
python setup.py update_catalog -t mkdocs -l fr
You can now move on to the next step and add a translation for every updated text placeholder in the localized catalog.
Translating the MkDocs themes
Now that your localized messages.po
files are ready, all you need to do is
add a translation in each msgstr
item for each msgid
item in the file.
msgid "Next"
msgstr "Siguiente"
!!! Warning
Do not modify the msgid
as it is common to all translations. Just add
its translation in the msgstr
item.
Once you have finished translating all of the terms listed in the po
file,
you’ll want to test your localized theme.
Testing theme translations
To test a theme with translations, you need to first compile the messages.po
files of your theme into messages.mo
files. The following command will compile
the es
translation for the mkdocs
theme.
python setup.py compile_catalog -t mkdocs -l es
The above command results in the following file structure:
mkdocs/themes/mkdocs/locales
├── es
│ └── LC_MESSAGES
│ ├── messages.mo
│ └── messages.po
Note that the compiled messages.mo
file was generated based on the
messages.po
file that you just edited.
Then modify the mkdocs.yml
file at the root of the project to test the new
and/or updated locale:
theme:
name: mkdocs
locale: es
Finally, run mkdocs serve
to check out your new localized version of the theme.
!!! Note
The build and release process takes care of compiling and distributing
all locales to end users so you only have to worry about contributing the
actual text translation messages.po
files (the rest is ignored by git).
After you have finished testing your work, be sure to undo the change to
the `locale` setting in the `mkdocs.yml` file before submitting your
changes.
Updating theme documentation
Update the lists of supported translations for each translated theme located at
Choosing your theme
(docs/user-guide/choosing-your-theme.md
), in their locale
options.
Contributing translations
It is now time for you to contribute your nice work to the project. Thank you!


In this blog post we’ll build an autoencoder in Pytorch from scratch, and have you encoding and decoding your first images! Hop over to google colab and open a blank notebook. To begin, we’ll want to install pytorch and torchvision, since we’ll rely on them for the components that make up our dataset. To install them into our colab notebook:
!pip install torch torchvision
And then we also need to import them:
import torch, torchvision
from torch import nn, optim
DDD
DDDD
Encoder and Decoder
DDDdd
dddDD
Creating the network is also relatively easy, we create two classes, one that represents the encoder and another that represents the decoder. These classes need to a have a very specific format and should always inherit the nn.Module base class. Inheriting from the nn.Module class will automatically give our class some useful and essential properties.
In python, to inherit in from another class we simply pass the class name into the parenthesis of the class that we’re creating and calling the super() function in the constructor, such as follows:
class Encoder(nn.Module):
def __init__(self, **kwargs):
super().__init__()
self.layer = nn.Linear(784, 16)
def forward(self, x):
x = self.layer(x)
return x
The two other things that are noteworthy here are the layer attribute that we’re creating and the forward function. Creating a class and making it inherit from nn.Module is only half the work, we also need to declare the number of layers and what kind of layers our network will have. In the case of the simple encoder, we are just going to create a single fully connected layer, that can take as input some tensor of a specific shape and outputs another tensor with a different shape. In our case we’re creating a layer that takes as input a tensor with 784 dimensions and outputs a tensor with 16 dimensions.
Next up is the forward method. The forward method specifies how our neural network is connected, or ‘wired’ internally if you will. You can imagine the input to the forward method as the input to our neural network, here the input is designated by the variable ‘x’. x is then immediately passed as an input to the layer that we declared in our constructor, this means that we’re passing it through that layer and receive the output of that layer in x again, and we return it. Whatever we return from the forward method, will be the output of our neural network.
We rinse and repeat the same steps for the decoder, except that the layer in the decoder has the input and output shapes reversed. This essentially means that we’re creating two separate neural networks, one that is the encoder and another that is the decoder.
class Decoder(nn.Module):
def __init__(self, **kwargs):
super().__init__()
self.layer = nn.Linear(16, 784)
def forward(self, x):
x = self.layer(x)
return x
Stringing encoder and decoder together
Now we have two separate nets that should ultimately comprise our entire pipeline, in this manner we need to chain them together. We can do this by creating a 3rd class, that also inherits nn.Module, and which holds two member variables, that are instances of the Encoder and Decoder that we just created. This showcases the amazing modularity of pytorch, which allows us to integrate one network as a part of another network. You can also see the forward function, which again as before will pass the input x through the encoder, pass it on to the decoder and then ultimately output it.
class AE(nn.Module):
def __init__(self, **kwargs):
super().__init__()
self.encoder = Encoder()
self.decoder = Decoder()
def forward(self, x):
x = self.encoder(x)
x = self.decoder(x)
return x
Training Setup
We’ve created and wired our network, now we still need to set up some stuff before we can begin training. Ideally we want to train on a GPU to accelerate this process, and since we’re on google colab, we can run our model on the provided GPU with following statements:
# use gpu if available
device = torch.device("cuda" if torch.cuda.is_available() else "cpu")
# create a model from `AE` autoencoder class
# load it to the specified device, either gpu or cpu
model = AE().to(device)
Next up we need to specify an optimizer and a criterion. The optimizer is the procedure by which we improve our neural network during training, the criterion is the metric that calculates how well or how badly we performed each training step. We’ll utilize the most standard optimizer and criterion, which are the Adam optimizer and the Mean Square Error Loss:
# create an optimizer object
# Adam optimizer with learning rate 1e-3
optimizer = optim.Adam(model.parameters(), lr=1e-3)
# mean-squared error loss
criterion = nn.MSELoss()
The mean square error loss essentially compares the pixel values of the output to those of the input.
Preparing the Dataset
To train our network we also still need some data. We’ll train our dataset on the good old MNIST dataset that consists of greyscale images of handwritten digits that are 28x28 in dimension. Downloading it is also straightforward,
transform = torchvision.transforms.Compose([torchvision.transforms.ToTensor()])
train_dataset = torchvision.datasets.MNIST(
root="~/torch_datasets", train=True, transform=transform, download=True
)
test_dataset = torchvision.datasets.MNIST(
root="~/torch_datasets", train=False, transform=transform, download=True
)
You can see that we’re actually downloading two datasets, one for training and another for testing. We also need to declare two data loaders, which will allow us to conveniently feed our dataset to our network:
train_loader = torch.utils.data.DataLoader(
train_dataset, batch_size=128, shuffle=True, num_workers=4, pin_memory=True
)
test_loader = torch.utils.data.DataLoader(
test_dataset, batch_size=32, shuffle=False, num_workers=4
)
The training Loop
Now we’ve completed all the setup and can start training. The training loop is the most integral component of our code and we’ll go through it step by step. Firstly, we’ll create a main loop that will specify the number of epochs that we’ll train for. Every epoch our network will see the entire dataset, not all at once, but rather in small portions. The small portions are called batches. This is where the data-loaders, that we previously created, come into play. We create a loop statement that gets a batch of ‘features’ (input images), to pass to the auto encoder.
epochs = 5
for epoch in range(epochs):
loss = 0
for batch_features, _ in train_loader:
#training loop steps go here
These batches of data need to be flattened such that they have the exact shape that we specified earlier when we constructed our encoder layer. In this manner we flatten the 28x28 pixel images into a linear tensor of 784 dimensions. We can do this with the view() function in pytorch. We also need to make sure that we send this batch of data to device that we’re training on (GPU, same as network):
# reshape mini-batch data to [N, 784] matrix
# load it to the active device
batch_features = batch_features.view(-1, 784).to(device)
Another important function call that should generally be made before we feed the batch to our network, depending on the type of neural network you’re training and what you’re trying to achieve, is ‘zero_grad()’ on the optimizer. This function call resets the gradients to zero before backpropagation. Otherwise we would be accumulating the gradients, which is useful when training RNNs for example.
# reset the gradients back to zero
# PyTorch accumulates gradients on subsequent backward passes
optimizer.zero_grad()
Next, we pass the batch to our network such that we perform a forward pass, and receive what comes out on the other end in the outputs variable. After that we need to obtain the training loss by comparing input and outputs with our specified criterion. Note that train_loss here, is not just a number but rather a tensor that has functionality:
# compute reconstructions
outputs = model(batch_features)
# compute training reconstruction loss
train_loss = criterion(outputs, batch_features)
After obtaining the training loss for a specific batch, we perform backpropagation and perform an optimizer step.
# compute accumulated gradients
train_loss.backward()
# perform parameter update based on current gradients
optimizer.step()
We also have a variable that accumulates the loss over every batch, which we then average outside the inner loop and print to screen to verify that the network is improving and that the overall loss is decreasing:
# add the mini-batch training loss to epoch loss
loss += train_loss.item()
### Outside the batch loop ###
# compute the epoch training loss
loss = loss / len(train_loader)
# display the epoch training loss
print("epoch : {}/{}, loss = {:.6f}".format(epoch + 1, epochs, loss))
The training loop in it’s entirety will look like this:
epochs = 5
for epoch in range(epochs):
loss = 0
for batch_features, _ in train_loader:
# reshape mini-batch data to [N, 784] matrix
# load it to the active device
batch_features = batch_features.view(-1, 784).to(device)
# reset the gradients back to zero
# PyTorch accumulates gradients on subsequent backward passes
optimizer.zero_grad()
# compute reconstructions
outputs = model(batch_features)
# compute training reconstruction loss
train_loss = criterion(outputs, batch_features)
# compute accumulated gradients
train_loss.backward()
# perform parameter update based on current gradients
optimizer.step()
# add the mini-batch training loss to epoch loss
loss += train_loss.item()
# compute the epoch training loss
loss = loss / len(train_loader)
# display the epoch training loss
print("epoch : {}/{}, loss = {:.6f}".format(epoch + 1, epochs, loss))
Testing the model
Lastly, we also want to see how well our model performs qualitatively, we can do this by looking at some of the outputs that our model outputs and compare them with the original input. We’ll need to import the matplotlib library for that and use our test_loader, which holds data that was not included in the training dataset. This will give us a good idea how well our model can generalize to new data:
import matplotlib.pyplot as plt
for batch_features, _ in test_loader:
batch_features = batch_features.view(-1, 784).to(device)
outputs = model(batch_features)
#print(outputs.shape)
print('IMAGE')
plt.subplot(211)
plt.imshow(batch_features[0].cpu().detach().view(28, 28).numpy())
plt.subplot(212)
plt.imshow(outputs[0].cpu().detach().view(28, 28).numpy())
plt.show()


# Form-Data [![Join the chat at https://gitter.im/form-data/form-data](http://form-data.github.io/images/gitterbadge.svg)](https://gitter.im/form-data/form-data) [![Build Status](https://img.shields.io/travis/form-data/form-data/master.svg)](https://travis-ci.org/form-data/form-data) [![Dependency Status](https://img.shields.io/david/form-data/form-data.svg)](https://david-dm.org/form-data/form-data)
A library to create readable `"multipart/form-data"`
streams. Can be used to submit forms and file uploads to other web applications.
The API of this library is inspired by the [XMLHttpRequest-2 FormData Interface][xhr2-fd].
[xhr2-fd]: http://dev.w3.org/2006/webapi/XMLHttpRequest-2/Overview.html#the-formdata-interface [streams2-thing]: http://nodejs.org/api/stream.html#stream_compatibility_with_older_node_versions
## Install
`
npm install form-data
`
## Usage
In this example we are constructing a form with 3 fields that contain a string, a buffer and a file stream.
``` javascript var FormData = require(‘form-data’); var fs = require(‘fs’);
var form = new FormData(); form.append(‘my_field’, ‘my value’); form.append(‘my_buffer’, new Buffer(10)); form.append(‘my_file’, fs.createReadStream(‘/foo/bar.jpg’)); ```
Also you can use http-response stream:
``` javascript var FormData = require(‘form-data’); var http = require(‘http’);
var form = new FormData();
- http.request(‘http://nodejs.org/images/logo.png‘, function(response) {
- form.append(‘my_field’, ‘my value’); form.append(‘my_buffer’, new Buffer(10)); form.append(‘my_logo’, response);
});¶
Or @mikeal’s [request](https://github.com/request/request) stream:
``` javascript var FormData = require(‘form-data’); var request = require(‘request’);
var form = new FormData();
form.append(‘my_field’, ‘my value’); form.append(‘my_buffer’, new Buffer(10)); form.append(‘my_logo’, request(‘http://nodejs.org/images/logo.png‘)); ```
In order to submit this form to a web application, call `submit(url, [callback])`
method:
``` javascript form.submit(‘http://example.org/‘, function(err, res) {
// res – response object (http.IncomingMessage) // res.resume();
});
For more advanced request manipulations `submit()`
method returns `http.ClientRequest`
object, or you can choose from one of the alternative submission methods.
### Alternative submission methods
You can use node’s http client interface:
``` javascript var http = require(‘http’);
- var request = http.request({
- method: ‘post’, host: ‘example.org’, path: ‘/upload’, headers: form.getHeaders()
});
form.pipe(request);
- request.on(‘response’, function(res) {
- console.log(res.statusCode);
});¶
Or if you would prefer the ‘Content-Length’ header to be set for you:
``` javascript form.submit(‘example.org/upload’, function(err, res) {
console.log(res.statusCode);
});¶
To use custom headers and pre-known length in parts:
``` javascript var CRLF = ‘rn’; var form = new FormData();
- var options = {
- header: CRLF + ‘–’ + form.getBoundary() + CRLF + ‘X-Custom-Header: 123’ + CRLF + CRLF, knownLength: 1
};
form.append(‘my_buffer’, buffer, options);
- form.submit(‘http://example.com/‘, function(err, res) {
- if (err) throw err; console.log(‘Done’);
});¶
Form-Data can recognize and fetch all the required information from common types of streams (`fs.readStream`
, `http.response`
and `mikeal's request`
), for some other types of streams you’d need to provide “file”-related information manually:
``` javascript someModule.stream(function(err, stdout, stderr) {
if (err) throw err;
var form = new FormData();
- form.append(‘file’, stdout, {
- filename: ‘unicycle.jpg’, contentType: ‘image/jpg’, knownLength: 19806
});
- form.submit(‘http://example.com/‘, function(err, res) {
- if (err) throw err; console.log(‘Done’);
});
});¶
For edge cases, like POST request to URL with query string or to pass HTTP auth credentials, object can be passed to form.submit() as first parameter:
``` javascript form.submit({
host: ‘example.com’, path: ‘/probably.php?extra=params’, auth: ‘username:password’
- }, function(err, res) {
- console.log(res.statusCode);
});¶
In case you need to also send custom HTTP headers with the POST request, you can use the headers key in first parameter of form.submit():
``` javascript form.submit({
host: ‘example.com’, path: ‘/surelynot.php’, headers: {‘x-test-header’: ‘test-header-value’}
- }, function(err, res) {
- console.log(res.statusCode);
});¶
### Integration with other libraries
#### Request
Form submission using [request](https://github.com/request/request):
```javascript var formData = {
my_field: ‘my_value’, my_file: fs.createReadStream(__dirname + ‘/unicycle.jpg’),
};
- request.post({url:’http://service.com/upload’, formData: formData}, function(err, httpResponse, body) {
- if (err) {
- return console.error(‘upload failed:’, err);
} console.log(‘Upload successful! Server responded with:’, body);
});¶
For more details see [request readme](https://github.com/request/request#multipartform-data-multipart-form-uploads).
#### node-fetch
You can also submit a form using [node-fetch](https://github.com/bitinn/node-fetch):
```javascript var form = new FormData();
form.append(‘a’, 1);
- fetch(‘http://example.com‘, { method: ‘POST’, body: form })
- .then(function(res) {
- return res.json();
- }).then(function(json) {
- console.log(json);
});
## Notes
`getLengthSync()`
method DOESN’T calculate length for streams, use`knownLength`
options as workaround.- If it feels like FormData hangs after submit and you’re on
`node-0.10`
, please check [Compatibility with Older Node Versions][streams2-thing]
## License
Form-Data is licensed under the MIT license.


Generates a Catmull-Rom spline from a series of 2D or 3D coordinates.
Input Ports
Name Type Description in float array coordinates of nodes to be used to generate spline Parameters
The following lists all of the parameters found in the parameter block CatmullParams, which are accessed by the module CatmullRomSpline and the UI Macro CatmullUI.
Name Type Description UI Control steps int numbers of steps in spline Edit Box line_type enum whether the spline is closed or open Radio Buttons Output Ports
Name Type Description out float array coordinates of spline nodes out_mesh mesh spline represented as a polyline mesh obj DataObject Default Renderable Object
catmull is a user module that takes a series of either 2D or 3D floating point coordinates and generates a spline that passes through all the points with C1 continuity. The spline is then output as a similar series of coordinates, a polyline mesh and a directly renderable DataObject. The number of connecting steps between two points and whether the curve is closed or open can be specified through the user interface.
&in
Reference to an array of floating point coordinates which are to be used as the nodes that the spline curve connects. Coordinates can be either 2 or 3 dimensional and should be represented by arrays of the form [n][2] and [n][3] respectively, where n is the number of nodes. A spline curve is then generated that connects the nodes together in the order given.
steps
A member of the CatmullParams parameter block group, this int value is used to specify the number of steps that should be used to create the spline curve connecting two points.
line_type
A member of the CatmullParams parameter block group, this enumeration is used to specify whether the spline curve should be a complete closed curve or whether the curve should be left open. The enumeration is of the form shown below:
enum line_type { choices => {"closed","open"}; } = "closed";
out
The most primitive output field of the catmull macro. This contains the generated spline represented as a floating point array of coordinates. The resultant array is of the same form as the input array. Therefore for a 3D spline the resultant array would have the following dimensions [spline_n][3] where spline_n is the number of coordinate points generated by the spline calculation.
out_mesh
The spline curve represented as a polyline mesh.
obj
The directly renderable output field of the catmull macro. This contains a DataObject object that can be rendered by the standard data viewers. The Data Object is generated within the same module as the polyline mesh output.
The low-level CatmullRomSpline module is used in this User Macro catmull.
An example application CatmullEg is provided, which takes an array of 8 3D coordinates and smoothes the polyline between them by calculating a Catmull-Rom spline curve.
xp_comm_proj/catmull/ctmlmacs.v contains the catmull User Macro, the CatmullUI UI Macro, and the example application CatmullEg V definitions.
The CatmullMacs library inherits its process. As this library contains no procedural code, the process is not important. The low-level CatmullRomSpline module, executes under the process specified in its library, not the process defined in the high-level library.
Mario Valle
Andrew Dodd Paul G. Lever
CatmullParams, CatmullUI, CatmullEg and CatmullRomSpline.