This is heading h1
This is heading h2
This is heading h3
This is heading h4
This is heading h5
This is heading h6
Display Styles
This is display-1
This is display-2
This is display-3
This is display-4
Bootstrap 4 Kitchen Sink
This is display-1
This is display-2
This is display-3
This is display-4
.h1 through .h6 classes are also available, for when you want to match the font styling of a heading but cannot use the associated HTML element.
h1. Bootstrap heading class .h1
h2. Bootstrap heading class .h2
h3. Bootstrap heading class .h3
h4. Bootstrap heading class .h4
h5. Bootstrap heading class .h5
h6. Bootstrap heading class .h6
You can use the mark tag to highlighttext.
Use the del tag to show a text as deleted.
This line of text will render as underlined. It uses the u tag.
Use the small tag for fine or small print.
Use the strong tag for bold text.
Use the em tag for italicized text.
This paragraph uses the text-justify class. Ambitioni dedisse scripsisse iudicaretur. Cras mattis iudicium purus sit amet fermentum. Donec sed odio operae, eu vulputate felis rhoncus. Praeterea iter est quasdam res quas ex communi.Cras mattis iudicium purus sit amet fermentum.
Use text-left for Left aligned text on all viewport sizes.
Use text-center for Center aligned text on all viewport sizes.
Use text-right for Right aligned text on all viewport sizes.
Use text-sm-right for right aligned text on viewports sized SM. (small) or wider.
Use text-md-right for right aligned text on viewports sized MD (medium) or wider.
Use text-lg-right for right aligned text on viewports sized LG (large) or wider.
Use text-xl-left for Left aligned text on viewports sized XL (extra-large) or wider.
Transform text in components with text capitalization classes.
Use text-lowercase for Lowercased text.
Use text-uppercase for Uppercased text.
Use text-capitalize to capitalize the first letter in each word.
This paragraph is not inside a container. Lorem ipsum dolor sit amet, consectetur adipisicing elit. Atque molestiae incidunt obcaecati placeat, beatae iure dolores vero earum accusamus ipsum soluta magni ut quasi cumque debitis, ducimus voluptatem architecto est!
This paragraph is inside a container. It resizes based on the responsive breakpoints. Lorem ipsum dolor sit amet, consectetur adipisicing elit. Distinctio omnis minima vitae. Accusamus reprehenderit aspernatur nihil tempora atque voluptas magni, consequatur nostrum odit iste eaque mollitia esse cumque tenetur ad.
This paragraph is inside a container-fluid. Use .container-fluid for a full width container, spanning the entire width of the viewport. Lorem ipsum dolor sit amet, consectetur adipisicing elit. Commodi odit cum assumenda possimus, non, doloribus. Nam odio ut totam repellat, facilis sequi repudiandae ea provident debitis explicabo quibusdam veniam molestias!
-xs Extra small devices (portrait phones, less than 576px) No media query since this is the default in Bootstrap
-sm Small devices (landscape phones, 576px and up) @media (min-width: 576px) { ... }
-md Medium devices (tablets, 768px and up) @media (min-width: 768px) { ... }
-lg Large devices (desktops, 992px and up) @media (min-width: 992px) { ... }
-xl Extra large devices (large desktops, 1200px and up) @media (min-width: 1200px) { ... }
-xs Extra small devices (portrait phones, less than 576px) @media (max-width: 575px) { ... }
-sm Small devices (landscape phones, less than 768px) @media (max-width: 767px) { ... }
-md Medium devices (tablets, less than 992px) @media (max-width: 991px) { ... }
-lg Large devices (desktops, less than 1200px) @media (max-width: 1199px) { ... }
-xl Extra large devices (large desktops) No media query since the extra-large breakpoint has no upper bound on its width
Column 1 of 2: The column class col applies to every device and viewport, from xs to xl and every column will be the same width.
Column 2 of 2: The column class col applies to every device and viewport, from xs to xl and every column will be the same width.
Column 1 of 3: The column class col applies to every device and viewport, from xs to xl and every column will be the same width.
Column 2 of 3: The column class col applies to every device and viewport, from xs to xl and every column will be the same width.
Column 3 of 3: The column class col applies to every device and viewport, from xs to xl and every column will be the same width.
Column 1 of 3: Auto-layout for flexbox grid columns also means you can set the width of one column and the others will automatically resize around it. This column class is just col.
Column 2 of 3: Auto-layout for flexbox grid columns also means you can set the width of one column and the others will automatically resize around it. You may use predefined grid classes (as shown below), grid mixins, or inline widths. Note that the other columns will resize no matter the width of the center column. This column class is col-6
Column 3 of 3: This column class is just col. Note that the other columns will resize no matter the width of the center column.
Column 1 of 3: Auto-layout for flexbox grid columns also means you can set the width of one column and the others will automatically resize around it. This column class is just col.
Column 2 of 3: Auto-layout for flexbox grid columns also means you can set the width of one column and the others will automatically resize around it. You may use predefined grid classes (as shown below), grid mixins, or inline widths. Note that the other columns will resize no matter the width of the center column. This column class is col-6
Column 3 of 3: This column class is just col. Note that the other columns will resize no matter the width of the center column.
Column 1 of 3
This column is using "col col-xl-2" Using the col-{breakpoint}-auto classes, columns can size itself based on the natural width of its content.
Column 2 of 3 is Using "col-12 col-md-auto"
Column3 of 3 is using "col col-xl-2"
This is super handy with single line content like inputs, numbers, etc. This, in conjunction with horizontal alignment classes, is very useful for centering layouts with uneven column sizes as viewport width changes.
Column 1 of 3
This column is using "col" only. Fugiat qui nostrum beatae, quod officiis animi nulla incidunt magni, delectus repellendus tempora saepe consectetur illum ullam facilis voluptates impedit quisquam nesciunt!
Column 2 of 3. This column is using "col-12 col-md-auto"
Column 3 of 3. This column is using "col col-xl-2"
This column uses just "col"
Create equal-width columns that span multiple rows by inserting a .w-100 where you want the columns to break to a new line. Make the breaks responsive by mixing the .w-100 with some responsive display utilities.
This column uses just "col"
Create equal-width columns that span multiple rows by inserting a .w-100 where you want the columns to break to a new line. Make the breaks responsive by mixing the .w-100 with some responsive display utilities.
This column uses "w-100"
Create equal-width columns that span multiple rows by inserting a .w-100 where you want the columns to break to a new line. Make the breaks responsive by mixing the .w-100 with some responsive display utilities.
This column uses just "col"
Create equal-width columns that span multiple rows by inserting a .w-100 where you want the columns to break to a new line. Make the breaks responsive by mixing the .w-100 with some responsive display utilities.
This column uses just "col"
Create equal-width columns that span multiple rows by inserting a .w-100 where you want the columns to break to a new line. Make the breaks responsive by mixing the .w-100 with some responsive display utilities.
With the handful of grid tiers available, you're bound to run into issues where, at certain breakpoints, your columns don't clear quite right as one is taller than the other. To fix that, use a combination of a .clearfix and our responsive utility classes. This column uses "col-6 col-md-3"
With the handful of grid tiers available, you're bound to run into issues where, at certain breakpoints, your columns don't clear quite right as one is taller than the other. To fix that, use a combination of a .clearfix and our responsive utility classes. This column uses "col-6 col-md-3"
Added the extra clearfix for only the required viewport. To do this, we created an empty div with the class of "clearfix d-sm-none-up".
This column uses "col-6 col-md-3"
With the handful of grid tiers available, you're bound to run into issues where, at certain breakpoints, your columns don't clear quite right as one is taller than the other. To fix that, use a combination of a .clearfix and our responsive utility classes. This column uses "col-6 col-md-3"
Level 1: This column uses "col-md-12". To nest your content with the default grid, add a new .row and set of .col-sm-* columns within an existing .col-sm-* column. The background color is "bg-danger"
This is still part of level 1.
Responsive images in Bootstrap are made responsive with img-fluid. The attributes max-width: 100%; and height: auto; are applied to the image so that it scales with the parent element.
This 200x200px image has "img-fluid" class applied. This image will scale with the parent element, col-md-3.
This 400x300px image has "img-fluid" class applied. This image will scale with the parent element, col-md-4.
This 800x400px image has "img-fluid" class applied. This image will scale with the parent element, col-md-2.
200x200px image has "img-fluid" class and the parent element is col-md-2.
200x200px image has "img-fluid" class and the parent element is col-md-4. In addition to the border-radius utilities, you can use img-thumbnail to give an image a rounded 1px border appearance.
This 400x400px image has "img-fluid" class and the parent element is col-md-4.
Align images with the helper float classes or text alignment classes. block-level images can be centered using the .mx-auto margin utility class.
This image has "img-fluid rounded float-left" and it also has the class "mr-2" to add some space to the right of the image.
This image has "rounded float-right". Resize your screen and notice how the image is not responsive and jumps out of the containing element. To make it responsive, you will also need to add the class "img-fluid".
This 300x300px image is centered inside the parent element col-md-6. The classes "img-fluid rounded mx-auto d-block"
This 300x300px image is centered inside the parent element col-md-6 using " text-center" on the containing div. The classes " img-fluid rounded" has been applied.
This 300x300px image is centered inside the parent element "col-md-6 text-center". The classes "img-fluid rounded-circle" have been applied.
This 400x300px image is centered inside the parent element "col-md-6 text-center". The classes "img-fluid rounded-circle" has been applied. Since the image is rectangle, it appears oval when rounded-circle is applied.
This 300x300px image is centered inside the parent element "col-md-6 text-center". The classes "img-fluid rounded-circle mx-auto d-block" have been applied.
This 400x300px image is centered inside the parent element "col-md-6 text-center". The classes "img-fluid rounded-circle mx-auto d-block" has been applied. Since the image is rectangle, it appears oval when rounded-circle is applied.
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry | the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry | the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry | the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry | the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry | the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Mark | Otto | @TwBootstrap |
| 3 | Jacob | Thornton | @fat |
| 4 | Larry the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Mark | Otto | @TwBootstrap |
| 3 | Jacob | Thornton | @fat |
| 4 | Larry the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry the Bird |
| # | First Name | Last Name | Username |
|---|---|---|---|
| 1 | Mark | Otto | @mdo |
| 2 | Jacob | Thornton | @fat |
| 3 | Larry the Bird |
Indicate the current page's location within a navigational hierarchy. Separators are automatically added in CSS through ::before and content.
A card is a flexible and extensible content container. It includes options for headers and footers, a wide variety of content, contextual background colors, and powerful display options. Cards replace our old panels, wells, and thumbnails from Bootstrap 3. Similar functionality to those components is available as modifier classes for cards.
Cards assume no specific width to start, so they'll be 100% wide unless otherwise stated. You can change this as needed with custom CSS, grid classes, grid Sass mixins, or utilities.
Using the grid, wrap cards in columns and rows as needed. The following cards are wrapped in rows and columns:
Some quick example text to build on the card title and make up the bulk of the card's content.
Go somewhereSome quick example text to build on the card title and make up the bulk of the card's content.
Some quick example text to build on the card title and make up the bulk of the card's content.
Card link Another linkSome quick example text to build on the card title and make up the bulk of the card's content.
With supporting text below as a natural lead-in to additional content.
Go somewhereThis card is using the sizing utility w-75 which means its 75%. Resize your screen to see it in action.

This card is wrapped within a row and column. This content is a little bit longer.
This is small text-muted.
This card is wrapped within a row and column. This content is a little bit longer.
This is small text-muted.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.
In addition to styling the content within cards, Bootstrap includes a few options for laying out series of cards. For the time being, these layout options are not yet responsive. Use card groups to render cards as a single, attached element with equal width and height columns. Card groups use display: flex; to achieve their uniform sizing.
This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer.
This card has supporting text below as a natural lead-in to additional content.
This is a wider card with supporting text below as a natural lead-in to additional content. This card has even longer content than the first to show that equal height action.
Card decks are a set of equal width and height cards that aren't attached to one another.
This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer.
This is a footer
This card has supporting text below as a natural lead-in to additional content.
This is a footer
This is a wider card with supporting text below as a natural lead-in to additional content. This card has even longer content than the first to show that equal height action.
This is a footer
Media objects can be infinitely nested, though we suggest you stop at some point. Place nested .media within the .media-body of a parent media object.
Vertically centered Add .modal-dialog-centered to .modal-dialog to vertically center the modal.
Tooltip and Popover Within a Modal
Modal with Grid Inside
attr
How to use
HTML


The MkE SDK provides C++ and Python implementations of ROS1 point cloud publisher nodes.
The C++ implementation of ROS1 publisher node is called mkeros1_node
. This node is capable of connecting to a MagikEye sensor via the MkE API and publishing its 3D data via a ROS topic. Note that the code depends on the C++ MkE API client library libmkeclient which is also distributed as a part of this SDK.
The Python implementation of ROS1 publisher node is called pymkeros1_node
. This node is capable of connecting to a MagikEye sensor via the MkE API and publishing its 3D data via a ROS topic. Note that the code depends on the Python MkE API package pymkeapi which is also distributed as a part of this SDK.
© 2016-2021 MagikEye Inc.


There are two different types of connectors. Connectors that allow browsers to
connect directly to the Tomcat and connectors that do it through a Web Server.
The connectors allowing direct connections are distributed as jar files with
the Tomcat binary releases.
The connectors used with a Web Server are made of 2 components. One written
in Java and the other written in C. The Java part is included, as a jar file
,
with the Tomcat binary releases. The C part is released separately and may be
obtained from the
Tomcat Connectors Downloads.
The total number of different operating systems and web servers is sufficiently
large that it is not practical to provide binaries downloads for every
combination. Binaries are provided for most of the popular combinations and if
the one you need is not available do not hesitate to ask for it on the
tomcat-user mailing list but please be patient and accept you may have to build
it yourself with the help of the mailing list.
The source code for the Tomcat Connectors is available from the SVN repository
(Tomcat SVN structure) or as a
bundle (that includes both the Java and the C components) from the
Tomcat Connectors Downloads.


Guarana has been used for thousands of years by the tribes of the Amazon rain forest. The herb has the same benefits of coffee which include helping to sharpen mental focus and an ability to increase stamina and physical endurance. It also has other benefits in terms of sexual health of which the main one is its ability to reduce the symptoms of depression (which causes loss of libido and Erectile dysfunction) and improve overall mood.
A sexual stimulant originally used by native rain forest tribes as a natural aphrodisiac and to improve general health for centuries. Tongkat Ali can naturally and quickly increase one's sex drive and libido while safely increasing the testosterone levels and supports mental alertness.
What agents in maca are responsible for its potent sex-enhancing effects? The plant sterols listed may possibly be some of the chemical agents of desire, as may be isothiocyanates discovered in the root. Though these compounds occur in small amounts, they may enhance fertility. Two other groups of compounds, recently discovered, appear to be the sexual keys to this high altitude root. More importantly, as an adaptogen, it supports your body in creating the enzymes it needs to balance hormones and enhance fertility. It's often touted as an aphrodisiac.
Disclaimer: Not suitable for children, pregnant, planning to be pregnant women, and people with high blood pressure and/or heart conditions.
H.I. Coffee was discovered on a trip to Asia, where founders Eric and Peter discovered a Tongkat Ali coffee that enhanced their libido. They tracked down the manufacturer and found that it was produced locally in the U.S.A. They didn't like the taste and reformulated it enhance the flavor and effects.
Http://www.HICoffeeUSA.com grew a following of online customers that loved the product and continue to refer their friends.
HICO DDS is launched to give back to our loyal customers that continue to refer their friends.
HICO DDS plans to move to it's new headquarters in Newport Beach to support it's growing customer base of loyal fans.


This is a web-app for networks built exclusively for families. You can share daily moments and locations with your family anytime at anywhere.
* Required fields


{% extends "base.mail.html" %}
{% block content %}
Hello {{ voucher.sender_name }},
{{ voucher.receiver_name }} has just used a 1%GIFTCARD you gave.
{% for donation in voucher.donations.all %}
{{ donation.project.title }}
{% endfor %}
YOU MAKE IT WORK!
{% endblock %}


Passengers stuck on bus for 20 minutes as police close road in St George
Traffic was brought to a standstill
by Emma GrimshawMotorists were stuck in standstill traffic for almost half an hour after police closed a St George road during rush hour tonight (Monday, November 18).
A bus passenger said she was trapped in the jams for 20 minutes on Grindell Road near to Netham Road.
Mobile phone footage from the scene shows six police cars blocking the route at around 5pm.
A spokesperson for Avon and Somerset police confirmed officers were carrying out a stop-check in the area.
No arrests were made and the cordon has now been lifted.
A witness told Bristol Live: "Police has recently closed the road at the Netham Road.
"We are all in the bus 36 stuck on the one-way street."
For the latest news in and around Bristol, visit and bookmark Bristol Live's homepage .


TYPEs¶
TYPE
is a property of an OBJECT
but in practice it is defined as a separate
node within the database to allow us to improve the flexibility of the underlying data model. TYPE
nodes are defined either as part of the w3C Annotation model (e.g., {type:'TextualBody'}
or using other schema, for example {type:'schema:CodeRepository'}
.
| type | n |
|---|---|
| schema:Grant | 467,000 |
| TextualBody | 356,000 |
| schema:Article | 159,000 |
| schema:CodeRepository | 74,000 |
| schema:DataCatalog | 2,300 |
| Dataset | 390 |
Matching Objects by Type¶
Using the TYPE
element we can find (for example) a database using:
MATCH (tdb:TYPE {type:'schema:DataCatalog'})
MATCH (tdb)<-[:isType]-(n:OBJECT)
RETURN n
LIMIT 3
The TYPE
defining an object also defines some of the properties that the object may have, although these are not embedded as constraints.
Various TYPEs¶
schema:DataCatalog¶
Objects defined as data catalogs were initially scraped from re3data.org using a
script that has been stored on GitHub in a code repository <http://https://github.com/throughput-ec/throughputdb/tree/master/Re3Databases>
_.
The object has properties:
id
, which come from the unique identifier (DOI) assigned by re3data.name
is the official name of the database.url
is the URL link for the database.keywords
is an array of terms associated with the database (although seekeywords
)description
is the description given to the database.
An object is represented by the cypher statement:
(ob:OBJECT {id: "10.17616/R3PD38",
name: "Neotoma Paleoecology Database",
url: "http://neotomadb.org",
keywords: ["paleoenvironments", "fossil mammals (FAUNMAP)"],
description: "Neotoma is a multiproxy paleoecological database that
covers the Pliocene-Quaternary . . ."})
Individual databases have keywords associated with them. In some cases keywords may be misspelled, or may be either too general ("science") or too specific ("holocene fossils"). To ensure that keywords can be used effectively we want to add them to the graph.
We do this by creating a special node type (KEYWORD), with the constraint that each keyword is unique. Keywords may be related using the :implies relationship.
Each KEYWORD
is related to an OBJECT
through annotations.
schema:CodeRepository¶
Objects of type schema:CodeRepository
were originally scraped from GitHub, with code that is found in the
github_scrapers repository.
The objects have the properties:
id
which is the repository assigned ID (a numeric identifier in the case of GitHub)name
The name of the repository is a combination of the repository owner and the repository name.description
A user provided description for the repository.url
The URL for the repository.
MERGE (ob:OBJECT {id: 1234456,
url: "http://github.com/SimonGoring/myrepo",
description: "This repo is the bomb of bombs.",
name: "SimonGoring/myrepo"})
Code repositories may have keywords assigned, or have keywords defined (topics in the terminology of GitHub). These are linked to KEYWORD objects in the database through an ANNOTATION.
schema:Article¶
A scientific journal article type is a simplification of the CrossRef data schema v0.1.1.
The schema for OBJECTs of type schema:Article
provides fields for journal, title, author, and URL. The field id
is used for the DOI, to keep a standard of unique IDs in the id
field.
id
- Unique identifier for grants (assumes NSF grants)journal
title
author
url
MERGE (award:OBJECT {"journal": "Risk Analysis",
"id": "10.1111/risa.13567",
"title": "Protecting From Malware Obfuscation Attacks Through Adversarial Risk Analysis",
"url": "https://onlinelibrary.wiley.com/doi/abs/10.1111/risa.13567",
"authors": "Redondo, Alberto; Insua, David Ríos"})
schema:Grant¶
The structure of a grant is (currently) based on the NSF Award schema. The code to obtain the NSF awards and add them to the graph is located within the Throughput database nsf_award module.
AwardID
- Unique identifier for grants (assumes NSF grants)name
amount
ARRAAmount
AwardInstrument
description
MERGE (award:OBJECT {AwardID: 1234567,
name: "Award name",
amount: 12345,
ARRAAmount: 12345,
AwardInstrument = "Award Thing",
description = "The abstract of our grant proposal."})
Constraints and Indices¶
There are no constraints or indices on TYPE
nodes.


The Outer Worlds Is Launching On Switch "Some Time" Before The End Of March 2020
Take-Two updates investors
by Liam DoolanWhen Obsidian Entertainment launched its anticipated action RPG The Outer Worlds last month, there was no sign of the Switch release.
Not long after this, a press release from the game's publisher Private Division revealed the hybrid version would be arriving at some point in 2020, leading to the belief the game would launch on Nintendo's platform before the end of Take-Two's fiscal year (Private Division's parent company).
Take-Two's latest update to investors has now revealed The Outer Worlds will launch on the Switch "some time" within the first three months of 2020. So that's before the end of March, as originally suggested.
Our colleagues over at Push Square gave The Outer Worlds nine out of ten stars and said it was a "role-playing triumph" thanks to its brilliantly crafted sci-fi adventure, witty writing, great characters, solid combat and rewarding exploration.
Have you been holding out for the Switch release of this game? Tell us below.
[via kotaku.com]


Create new domain
Help with creating a new domain
- Domain name
- Enter your domain name in the format of name.tld (eg. powerdns-admin.com). You can also enter sub-domains to create a sub-root zone (eg. sub.powerdns-admin.com) in case you want to delegate sub-domain management to specific users.
- Type
- The type decides how the domain will be replicated across multiple DNS servers.
- Native - PowerDNS will not perform any replication. Use this if you only have one PowerDNS server or you handle replication via your backend.
- Master - This PowerDNS server will serve as the master and will send zone transfers (AXFRs) to other servers configured as slaves.
- Slave - This PowerDNS server will serve as the slave and will request and receive zone transfers (AXFRs) from other servers configured as masters.
- SOA-EDIT-API
- The SOA-EDIT-API setting defines how the SOA serial number will be updated after a change is
made to the domain.
- DEFAULT - Generate a soa serial of YYYYMMDD01. If the current serial is lower than the generated serial, use the generated serial. If the current serial is higher or equal to the generated serial, increase the current serial by 1.
- INCREASE - Increase the current serial by 1.
- EPOCH - Change the serial to the number of seconds since the EPOCH, aka unixtime.
- OFF - Disable automatic updates of the SOA serial.
Find more details at https://docs.powerdns.com/md/


Instructions
- Click "Choose Files" below
- Select the folder that the RTDose and CT files are in
- Wait. Your browser may freeze while the files are being written
Purpose
In the 21st century, delivery of radiation is mostly image guided, however, not all of this image information is retained. Vital information on the location of the radiation doses cannot be stored in PACS databases. Without this information, physicians must make their “best guess” on the location of the dose, based on written notes, rather than making informed decisions based on high precision, computer-generated dose information. This lack of precision can have far-reaching consequences. For example, with only written notes, doctors could misdiagnose a patient, such as mistaking pneumonia for pneumonitis.
RTForDR is the solution to this consequential problem. RTForDR converts radiation dose information from DICOM-RT to the DICOM format, so that it can be stored in PACS databases and viewed with conventional DICOM viewing software.
Privacy of Information
RTForDR respects the privacy of private health information. All data manipulation is done locally, on your computer. None of the files leave your computer, or can be viewed by anyone else during the conversion process.


The Mystery of Edwin Drood
by Charles Dickens
The Mystery of Edwin Drood, Dickens's final novel was left unfinished before his death in 1871. Edwin Drood’s uncle, John Jasper, a choirmaster, is in love with his pupil and Drood’s fiancee Rosa Bud. She has also caught the eye of high-spirited and ill-tempered Neville Landless (who came from Ceylon with his twin sister Helena). When Drood is murdered, the killer must be found...that is if Drood is really dead.
Source: Dickens, C. (1870). The Mystery of Edwin Drood. London, England: Chapman and Hall.
- Chapter 1: The Dawn
- A confused Jasper exits the opium den before proceeding to the cathedral.
- Chapter 2: A Dean, and a Chapter Also
- Following the service, the Dean and Mr. Crisparkle discuss the current state of Mr. Jasper's health. Edwin Drood pays a visit to his uncle to discuss his impending nuptials with Rosa Bud.
- Chapter 3: The Nuns’ House
- Edwin Drood and Rosa Bud discuss their relationship. The sound of Jasper's voice from the cathedral frightens Rosa.
- Chapter 4: Mr. Sapsea
- Mr. Sapsea asks for Jaspers "opinion as a man of taste".
- Chapter 5: Mr. Durdles and Friend
- While proceeding home, Jasper encounters Durdles and a boy named called Deputy.
- Chapter 6: Philanthropy in Minor Canon Corner
- The home life of the Reverend Septimus Crisparkle is introduced to the reader. Mr. Crisparkle plans a dinner party.
- Chapter 7: More Confidences Than One
- Neville confides his past to the Reverend, openly admitting to feelings of "bitter hatred". Neville and the Reverend Crisparkle briefly discuss the situation between Edwin and Rosa.
- Chapter 8: Daggers Drawn
- After escorting the ladies home, Edwin and Neville have a heated discussion. Jasper, emerging from behind the two men, helps to establish a temporary truce between Edwin and Neville. After seeing Neville's reaction, Jasper begins to fear for his nephew's life.
- Chapter 9: Birds in the Bush
- With rumors of the previous nights events spreading throughout the town, Helena goes to her brother to find out the truth. Mr. Grewgious pays a visit to Rosa in order to discuss pertinent legal matters.
- Chapter 10: Smoothing the Way
- Reverend Crisparkle and his mother discuss Neville's behavior the night before. The Reverend encounters Neville and Helena by the river. Reverend Crisparkle is determined to bring a peaceful end to the current feud.
- Chapter 11: A Picture and a Ring
- Edwin Drood visits the Staple Inn, where he is invited to stay for dinner. Grewgious bestows a valuable gift upon Edwin.
- Chapter 12: A Night with Durdles
- While proceeding to the Cathedral late at night, Jasper and Durdles secretly observe the behavior of Crisparkle and Neville. Jasper recalls an odd experience he had at the crypt while Durdles later experiences something strange himself.
- Chapter 13: Both at Their Best
- With the arrival of the Christmas recess, Edwin and Rosa come to an agreement in regards to their relationship. Edward devises a plan to break the news to Jasper.
- Chapter 14: When Shall These Three Meet Again?
- Christmas Eve and the dinner party to make peace between Neville and Edwin is at hand. Edwin has a strange and troubling conversation with a woman on the streets of Cloisterham. A great storm descends upon the town.
- Chapter 15: Impeached
- Neville is questioned in regards to Edwin's whereabouts. Mr. Grewgious' delivers the news of Edwin and Rosa's decision not to wed to Jasper.
- Chapter 16: Devoted
- Jasper tells Grewgious about the previous evening's dinner party. Reverend Crisparkle makes some alarming discoveries at Cloisterham Weir. Evidence in the case against Neville continues to mount.
- Chapter 17: Philanthropy, Professional and Unprofessional
- The Reverend Crisparkle visits with Mr. Honeythunder before stopping by the Staple Inn to see Neville. Grewgious questions Crisparkle about Jasper's whereabouts. Neville becomes acquainted with Tartar.
- Chapter 18: A Settler in Cloisterham
- Dick Datchery, a new arrival to Cloisterham, talks to number of the townspeople about the Drood disappearance.
- Chapter 19: Shadow on the Sun-Dial
- Jasper's visit to Rosa leaves her feeling terrified.
- Chapter 20: A Flight
- Rosa departs the garden hastily in search of more secure surroundings.
- Chapter 21: A Recognition
- Grewgious and Crisparkle both visit with Rosa, who is impressed with Tartar's courage. Grewgious comes up with a plan to maintain communication between Rosa, Neville and Helena.
- Chapter 22: A Gritty State of Things Comes On
- Miss Twinkleton pays a visit to London.
- Chapter 23: The Dawn Again
- Jasper, having arrived in London, returns to his old haunts. Datchery has an interesting conversation with the "Royal Highness the Princess Puffer."


MATHS FOR PHYSICS
Complex Numbers
LITERATURE II
Home Sweet Home
OCEANOGRAPHY
Introduction to Oceanography
FORTRAN II
Arrays and Dimensions
ELECTRONICS II
Field Effect Transistors
WEATHER FORECASTING AND OBSERVATION
Lecture 1
Lecture 2
Lecture 3
Lecture 4
,
INTRODUCTION TO METEOROLOGY II
Introduction to Meteorology II


| HYTOOL Function Reference |
Calculate the transmissivity with Thiem formula
T = thiem( q, s1, s2, r1, r2) q = pumping rate s1 = drawdown in piezometer 1 s2 = drawdown in piezometer 2 r1 = distance piezometer 1 to pumping well r2 = distance piezometer 2 to pumping well
Thiem function compute the transmissivity with the Thiem (1906) solution. The Thiem method requires to know the pumping rate and the drawdown in two observation wells located at different distances from the pumping well.
T= thiem(q,s1,s2,r1,r2)
thiem_dmo Published output in the Help browser showdemo thiem
| Hytool |
© 1998-2017 Philppe Renard and Co. Terms of Use Acknowledgments


s6
Software
skarnet.org
How to convert systemd unit files to an s6 installation
Converting a set of services managed by systemd
to a set of services managed by s6 is
a recurring question on our support channels, and having an automated conversion tool
parsing a set of systemd
unit files and outputting a set of s6
service directories or
s6-rc service
definition directories would be useful to people who want to migrate to
s6 but have an existing base of services running under systemd.
 The main
reason for this is that systemd and s6 are architectured in very different ways:
how they view a set of services, how they modelize a machine, what kind of solution
they bring to a given problem, and the extent of what they're supposed to manage
— there are few similarities between how systemd and s6 operate. As a
consequence, the way systemd maps a set of services into unit files is not
isomorphic to the way s6 does, so translating a setup between systemd and s6
requires intelligence. It is not possible to write an automated tool that converts
a set of services accurately and idiomatically without doing a full, deep system
analysis - and writing such a tool would be a huge undertaking.
Fortunately, in practice, most unit files only use a small subset of all the
theoretically supported directives: most services that run under systemd can be
converted to run under s6 without too much trouble. So, depending on the exact
nature of the set of services, it may be possible to write a reasonable converter,
that is limited in what it supports but does not require a full understanding
of systemd (or even s6).
This document targets people who think about writing a tool to automatically
convert a set of unit files to a set of s6 services and are trying to assess
its feasability and difficulty. We analyze all the directives that may appear
in a unit file for their services, and rate the difficulty of translating the
directive, i.e. the amount of complexity that would need to go into the
converter tool if that directive were to be supported.
We rate difficulty on a scale from 0 to 10.
A 0 means that the directive is irrelevant to s6 and can
be ignored. A 1 means that there is a straightforward,
one-for-one way of translating the systemd directive into s6 parlance. A
10 means that the directive is so systemd-specific that it
is impossible to express it on an s6 system and the unit file cannot be
converted as is. A 9 means that it is theoretically possible
to convert, given infinite time and manpower to write a tool that analyzes
the systemd-managed system holistically and outputs an equivalent system
managed by s6, but in practice nobody's ever going to write such a tool.
We only address directives that can appear in service units, which
are the ones that can reasonably be expected to translate to s6 or s6-rc
services. We do not address directives that can only appear in other kinds
of unit files such as slices, timers, sockets, etc.
Difficulty by directive
Use this section to answer the question: "I have this directive in my unit file,
how hard would it be to write a converter tool that processes this file?"
[Unit] section
- Description= : 0.
- Documentation= : 0.
- Wants= : 3. Dependencies between services
are implemented via s6-rc; in order
to implement Wants=. the converter needs to target s6-rc, which is a
reasonable requirement for a complete set of services. However, Wants=
expresses weak dependencies, which are not supported by the current version of
s6-rc, so the exact nature of the dependency needs to be checked by hand.
- Requires= : 2. The converter needs to
target s6-rc, but Requires=
dependencies map well to the s6-rc dependency model.
- Requisite= : 3. systemd supports a lot of
weird types of dependencies that the current version of s6-rc does not (by
design).
- BindsTo= : 3. Same.
- PartOf= : 3. Same.
- Upholds= : 0. In s6, services are upheld by
the supervisor, not by other services.
- Conflicts= : 5. There are no negative
dependencies in the s6 world, and a converter tool would have to implement it
on top of the existing system.
- Before= : 2. systemd loves to have a
zillion of keywords to express slightly different kinds of dependencies, and
only a small subset of all the possible combinations are useful.
- After= : 2.
- OnFailure= : 5. Permanent failure is
a very exceptional state in s6, there are no hooks to do something when
permanent failure occurs; so a converter would need to add scripting around that.
- OnSuccess= : 2. These are oneshot
dependencies.
- PropagatesReloadTo= : 0. Under s6-rc
you can either reload a single service or the whole dependency chain that
starts at the service. Other configurations just make no sense.
- ReloadPropagatedFrom= : 0. Same.
- PropagatesStopTo= : 0. Same with stopping
a single service or a dependency chain of services.
- StopPropagatedFrom= : 0. Same.
- JoinsNamespaceOf= : 8. There are no
native s6 tools to manage namespaces.
- RequiresMountsFor= : 4. Mounts are
not handled in a special way in s6, the converter would have to know
what service mounts what filesystem.
- OnFailureJobMode= : 6. This is what
happens when you mix layers.
- IgnoreOnIsolate= : 0.
- StopWhenUnneeded= : 0.
- RefuseManualStart= : 4. Would need
some scripting around. There's no reason to ever use that directive though.
- RefuseManualStop= : 1.
- AllowIsolate= : 0.
- DefaultDependencies= : 2.
- CollectMode= : 0.
- FailureAction= : 3. Anything involving
permanent failure need to be scripted around, because s6 considers that
it is an extreme state that requires administrator attention and will
stop making automatic decisions.
- SuccessAction= : 3. That's a oneshot
dependency, but systemd doesn't realize that.
- FailureActionExitStatus= : 1.
- SuccessActionExitStatus= : 1.
- JobTimeoutSec= : 9. s6 has no
concept of jobs.
- JobRunningTimeoutSec= : 9. Same.
- JobTimeoutAction= : 9. Same.
- JobTimeoutRebootArgument= : 9. Same.
- StartLimitIntervalSec= : 3. s6 does
not limit start rate. It can stop a service that has a high death
rate: that's the configuration knob that makes sense. That directive can
be converted to check death interval instead.
- StartLimitBurst= : 3. Same.
- StartLimitAction= : 3. Same.
- RebootArgument= : 5. Any "system mode"
action such as a reboot has no place in an s6 set of services anyway;
systemd obviously likes to mix unrelated layers. In the s6 world, the only
place where a reboot should occur is
s6-linux-init, and the
related scripting in rc.init files.
- SourcePath= : 0.
- Conditions and Asserts: 9. Most of these are tied to the
global machine state and absolutely not local to a given set of services. And
even for those that are not, what they do is change the whole service manager's
behaviour depending on some external dynamic state such as the existence of a
file in the filesystem — and that is entirely contrary to the s6
philosophy of making services predictable and reproducible.
[Install] section
Any directive under [Install] can be ignored, since it has no
meaning on the run-time behaviour of the service. So the difficulty is
0. However, an automatic converter would need to
analyze the whole installed service configuration, e.g. the links in
/etc/systemd/system/multi-user.target.wants/, in order to
understand the dependencies between services. systemd targets can
typically be converted into s6-rc bundles.
[Service] section
- Type= : depending on its type, a systemd "service"
can translate to wildly different things under s6.
- simple : 1.
- exec : 1.
- forking : 2. This type is strongly discouraged.
- oneshot : 1.
- dbus : 5. This type requires implementing dbus
management programs for s6.
- notify : 7. This type requires an implementation
of a compatibility server for
sd_notify(),
which is heavily tied to the monolithic systemd architecture and is difficult to support
in a modular system such as s6. It is much easier to modify the services themselves so
they use the s6 readiness
notification mechanism instead of sd_notify.
- idle : 0. This type is meaningless under s6 and
should be treated like simple.
- ExitType= : again, it depends on the value.
- main : 1.
- cgroup : 3. This requires implementing, or
having access to, command-line cgroup tools.
- RemainAfterExit= : 0.
- GuessMainPid= : 0. But don't use forking
if you can avoid it.
- PIDFile= : 2. Same.
- BusName= : 5. Avoid type dbus if possible.
- ExecStart= : 2, with caveats. This is the bread and
butter of service definitions; all your services will likely have such a directive, and
the contents of ExecStart= will typically go into a run script (for longruns) or
an up file (for oneshots). However, since systemd hates simplicity, there are a number
of transformations that have to happen to the command line before it can be used in a
script, and in particular if the command has a special executable prefix.
Implementing these has its own difficulty ratings:
- @ : 1.
- - : 1.
- : : 2.
- + : 5.
- ! : 3.
- !! : 3.
- ExecStartPre= : 2. In order to have a strict
semantic equivalence with their systemd version, ExecStartPre= lines must
be implemented as s6-rc oneshots, and the whole unit file must be implemented as
a bundle.
- ExecStartPost= : 2. Same.
- ExecCondition= : 2.
- ExecReload= : 0. A reloading command that
does not involve restarting the service does not need the service manager as
a third-party. systemd cannot help inserting itself where it does not belong.
- ExecStop= : 5. s6 only supports terminating
services via signals, so if a service needs a specific command to be stopped,
the converter needs to target an interface layer on top of s6 with a repository
of stop commands; such a layer would likely need to be on top of s6-rc as well
and a lot of complexity would ensue. Fortunately, a huge majority of services
support termination via signals and it is often easy to avoid relying on
ExecStop=.
- ExecStopPost= : 2. These are the
down scripts of the ExecStartPre= oneshots.
- RestartSec= : 2. s6 has no setting for that,
because it aims for maximum uptime; but there are still ways to implement that
bad idea.
- TimeoutStartSec= : 1.
- TimeoutStopSec= : 1.
- TimeoutAbortSec= : 7. This would need a
watchdog implementation, in the server implementation of sd_notify().
- TimeoutSec= : 1.
- TimeoutStartFailureMode= : 0 for
terminate and kill, 7 for abort.
- TimeoutStopFailureMode= : 0 for
terminate and kill, 7 for abort.
- RuntimeMaxSec= : 4. This is the exact
opposite of what you need a process supervisor for, so s6 does not
implement it. It is best to run such a process (not a service)
outside of any kind of supervision framework.
- RuntimeRandomizedExtraSec= : 4. Same.
- WatchdogSec= : 7. Requires a watchdog
implementation in the very specific systemd way.
- Restart= : depends on the value.
- no : 2, but why use a process supervisor
in the first place?
- on-success : 2.
- on-failure : 2.
- on-abnormal : 2.
- on-watchdog : 7. Again, this requires
a watchdog implementation.
- on-abort : 2.
- always : 1.
- SuccessExitStatus= : 3. This can be easily
scripted, but supporting all the systemd formats is annoying.
- RestartPreventExitStatus= : 1. This is
exactly what s6-permafailon
is for.
- RestartForceExitStatus= : 2.
- RootDirectoryStartOnly= : 2.
- NonBlocking= : 5. This requires an
emulation of systemd's socket activation. s6 provides the useful parts of
it, like a process
to hold file descriptors, but the systemd-specific API around socket
activation, sd_listen_fds(3),
still needs to be implemented.
- NotifyAccess= : 1 if none, 7
otherwise, because it needs an implementation of sd_notify().
- Sockets= : 5. Requires an implementation
of systemd's socket activation.
- FileDescriptorStoreMax= : 7. Requires an implementation
of sd_notify(); the fd store itself is native to s6.
- USBFunctionDescriptors= : 9. This is
low-level machine management, not service management.
- USBFunctionStrings= : 9. Same.
- OOMPolicy= : 9. Same.
Paths
- ExecSearchPath= : 1.
- WorkingDirectory= : 2.
- RootDirectory= : 1.
- RootImage= : 6. I am discovering these
options in real time and shaking my head - systemd still manages to baffle me
with the amount of gratuitous ad-hoc that went into it. Still, this is
regular low-level programming for Linux, this is less difficult to implement than
systemd-specific stuff, that's why it only gets a 6.
- RootImageOptions= : 6. Same.
- RootHash= : 9. Please.
- RootHashSignature= : 9.
- RootVerity= : 9.
- MountAPIVFS= : 6.
- ProtectProc= : 6.
- ProcSubset= : 6.
- BindPaths= : 6.
- BindReadOnlyPaths= : 6.
- MountImages= : 6.
- ExtensionImages= : 6.
- ExtensionDirectories= : 6. It's a full low-level
userspace implementation at this point. It's not very complex, the 6 feels
accurate, but it's a whole lot of work. This is how systemd maintains its
hegemony: not because it does incredible, awe-inspiring magic, but because it
substitutes its monolithic self to a whole ecosystem, imposes its own API, and
locks users in — people who want to smoothly transition away from systemd need
to implement the whole shtick, which is obviously a huge undertaking, as
the author of uselessd
can confirm.
User/group identity
- User= : 3. This looks very simple, but is
treacherous, because User= is a mash of two very different features:
setting users statically (via numeric ID, which don't change meanings
between two invocations) and setting users dynamically (via user name,
which needs to be interpreted by
getpwnam(3)
on every invocation of the service. s6 supports both, but since these are two
different things, the way to do them in s6 is different (statically setting the
UID and GID variables and calling
s6-applyuidgid -U,
or calling s6-setuidgid).
This is the exact kind of small detail that makes writing an automatic converter more difficult
than it should be: the systemd unit file syntax is rife with semantic pitfalls, and managing
your way across it requires very close attention.
- Group= : 3. Same.
- DynamicUser= : 5. Of course this flag has an
entirely different meaning from setting users statically or dynamically, or
else it would be too easy to understand. No, this flag is about allocating temporary
new users, which is a prime example of overengineering.
- SupplementaryGroups= : 1. Same.
- PAMName= : 4. Requires PAM command-line
utilities.
Capabilities
- CapabilityBoundingSet= : 4. This requires
command-line tools implementing capabilities.
- AmbientCapabilities= : 4. Same.
Security
- NoNewPrivileges= : 4. Similar to capabilities,
this requires a command-line tool controlling the Linux-specific
prctl(2) system
call.
- SecureBits= : 4. Same.
Mandatory access control
- SELinuxContext= : 5. This requires
command-line tools managing SELinux.
- AppArmorProfile= : 5. Same, with AppArmor.
- SmackProcessLabel= : 5. Same, with SMACK.
systemd needs to know and understand all the Linux security modules in order
to interact with them. s6 does not - it expects a service's run script to
perform all the needed process state changes and controls before executing
into the daemon.
Process properties
- LimitCPU= : 1.
- LimitFSIZE= : 1.
- LimitDATA= : 1.
- LimitSTACK= : 1.
- LimitCORE= : 1.
- LimitRSS= : 1.
- LimitNOFILE= : 1.
- LimitAS= : 1.
- LimitNPROC= : 1.
- LimitMEMLOCK= : 1.
- LimitLOCKS= : 2. This resource limit
isn't natively supported by
s6-softlimit, but
it could appear in a future s6 version - and it's easy to add in any case.
- LimitSIGPENDING= : 2. Same.
- LimitMSGQUEUE= : 2. Same.
- LimitNICE= : 2. Same.
- LimitRTPRIO= : 2. Same.
- LimitRTTIME= : 2. Same.
- UMask= : 1.
- CoredumpFilter= : 4. Requires a
command-line tool around prctl(2).
- KeyringMode= : 5. Requires
interaction with PAM and an understanding of keyrings. Fortunately,
practically nothing will need that.
- OOMScoreAdjust= : 2.
- TimerSlackNSec= : 4. Requires a
command-line tool around prctl(2).
- Personality= : 3. Requires a
command-line tool around personality(2).
- IgnoreSIGPIPE= : 2.
Scheduling
- Nice= : 1.
- CPUSchedulingPolicy= : 3. Requires a
command-line tool around sched_setscheduler(2).
- CPUSchedulingPriority= : 3. Same.
- CPUSchedulingResetOnFork= : 3. Same.
- CPUAffinity= : 3. Requires a
command-line tool around sched_setaffinity(2).
- NUMAPolicy= : 3. Requires a
command-line tool around set_mempolicy(2).
- NUMAMask= : 3. Same.
- IOSchedulingClass= : 3. Requires a
command-line tool around ioprio_set(2).
- IOSchedulingPriority= : 3. Same.
Sandboxing
systemd gracefully turns off the sandboxing options on systems that
do not support the necessary functionality, so all these options can
be ignored (difficulty 0) and the services will still
work. However, in order to actually implementing the sandboxing, it is
necessary to pair s6 with command-line tools that perform the required
process state changes by interfacing with namespaces, cgroups, seccomp,
or any other relevant feature of the Linux kernel, so for all these
directives the difficulty is somewhere between 2, if
the tool already exists, and 8, if it requires writing
a full container implementation from scratch. The following numbers are
only a rough guess.
- ProtectSystem= : 6.
- ProtectHome= : 6.
- RuntimeDirectory= : 1.
- StateDirectory= : 1.
- CacheDirectory= : 1.
- LogsDirectory= : 1.
- ConfigurationDirectory= : 1.
- RuntimeDirectoryMode= : 1.
- StateDirectoryMode= : 1.
- CacheDirectoryMode= : 1.
- LogsDirectoryMode= : 1.
- ConfigurationDirectoryMode= : 1.
- RuntimeDirectoryPreserve= : 3.
- TimeoutCleanSec= : 3.
- ReadWritePaths= : 5.
- ReadOnlyPaths= : 5.
- InaccessiblePaths= : 5.
- ExecPaths= : 5.
- NoExecPaths= : 5.
- TemporaryFileSystem= : 5.
- PrivateTmp= : 5.
- PrivateDevices= : 5.
- PrivateNetwork= : 8.
- NetworkNamespacePath= : 8.
- PrivateIPC= : 5.
- IPCNamespacePath= : 5.
- PrivateUsers= : 5.
- ProtectHostname= : 5.
- ProtectClock= : 7.
- ProtectKernelTunables= : 7.
- ProtectKernelModules= : 7.
- ProtectKernelLogs= : 7.
- ProtectControlGroups= : 7.
- RestrictAddressFamilies= : 7.
- RestrictFilesystems= : 7.
- RestrictNamespaces= : 7.
- LockPersonality= : 7.
- MemoryDenyWriteExecute= : 7.
- RestrictRealtime= : 7.
- RestrictSUIDSGID= : 7.
- RemoveIPC= : 5.
- PrivateMounts= : 5.
System call filtering
- SystemCallFilter= : 8.
- SystemCallErrorNumber= : 8.
- SystemCallArchitectures= : 8.
- SystemCallLog= : 8.
Environment
- Environment= : 1.
- EnvironmentFile= : 1.
- PassEnvironment= : 1.
- UnsetEnvironment= : 1.
Logging and standard input/output
- StandardInput= : 1.
- StandardOutput= : 1, except
for journal which cannot be supported (10).
- StandardError= : same.
- StandardInputText= : 2.
- StandardInputData= : 2.
- LogLevelMax= : 3.
- LogExtraFields= : 10.
- LogRateLimitIntervalSec= : 10.
- LogRateLimitBurst= : 10.
- LogFilterPatterns= : 4.
- LogNamespace= : 10.
- SyslogIdentifier= : 2.
- SyslogFacility= : 2.
- SyslogLevel= : 2.
- SyslogLevelPrefix= : 4.
- TTYPath= : 1.
- TTYReset= : 3.
- TTYVHangup= : 3.
- TTYRows= : 3.
- TTYColumns= : 3.
- TTYDisallocate= : 3.
Credentials
systemd implements its own credentials store mechanism, for no obvious
benefit. The whole credentials system needs to be reimplemented outside
of systemd in order for credentials-related directives to be supported
by s6. Consequently, all these directives are rated 6.
System V compatibility
The utmp directives can be made significantly easier to implement if the target
system is using utmps,
because the directives then become a single call to
utmps-write
with the relevant options. If utmps
cannot be used, then the utmp calls need to be reimplemented.
- UtmpIdentifier= : 4.
- UtmpMode= : 4.
- KillMode= : depends on the kill mode.
control-group and mixed are 3,
because they require cgroup control commands (that can be implemented
in shell). process is 1. none is
2.
- KillSignal= : 1.
- RestartKillSignal= : 5. s6
doesn't use a different signal for restarting; implementing this
requires an outer layer. (This is overengineering.)
- SendSIGHUP= : 5. Same.
- SendSIGKILL= : 1.
- FinalKillSignal= : 5. (This
is absolute overengineering.)
- WatchdogSignal= : 7. Only meaningful
with an implementation of systemd's watchdog system.
All these directives relate to cgroups, so implementing them means
having access to at least some cgroups commands (difficulty at least
3. Others are even more involved, requiring tight
service integration with the system. Generally, seeing these directives
in your unit files is a bad sign; despite some of them only having
3 or 4 listed, we do not recommend
implementing systemd.resource-control(5)
without having a full holistic view of the system.
- CPUAccounting= : 3.
- CPUWeight= : 4.
- StartupCPUWeight= : 9. Involves
startup and shutdown.
- CPUQuota= : 4.
- CPUQuotaPeriodSec= : 4.
- AllowedCPUs= : 3.
- StartupAllowedCPUs= : 9. Involves
startup and shutdown.
- AllowedMemoryNodes= : 3.
- StartupAllowedMemoryNodes= : 9.
Involves startup and shutdown.
- MemoryAccounting= : 3.
- MemoryMin= : 3.
- MemoryLow= : 3.
- MemoryHigh= : 3.
- MemoryMax= : 3.
- MemorySwapMax= : 3.
- MemoryZSwapMax= : 3.
- TasksAccounting= : 3.
- TasksMax= : 3.
- IOAccounting= : 3.
- IOWeight= : 3.
- StartupIOWeight= : 9. Involves
startup and shutdown.
- IODeviceWeight= : 5.
- IOReadBandwidthMax= : 5.
- IOWriteBandwidthMax= : 5.
- IOReadIOPSMax= : 5.
- IOWriteIOPSMax= : 5.
- IODeviceLatencyTargetSec= : 4.
- IPAccounting= : 7.
- IPAddressAllow= : 7.
- IPAddressDeny= : 7.
- IPIngressFilterPath= : 8.
- IPEgressFilterPath= : 8.
- BPFProgram= : 8.
- SocketBindAllow= : 6.
- SocketBindDeny= : 6.
- RestrictNetworkInterfaces= : 4.
- DeviceAllow= : 6.
- DevicePolicy= : 6.
- Slice= : 9. Slices are a systemd concept,
and fully implementing them requires a holistic system analysis.
- Delegate= : 4.
- DisableControllers= : 3.
- ManagedOOMSwap= : 8. Out-of-memory
management is an entire systemd subsystem; instead of implementing that,
we recommend provisioning your machines correctly, and freeing up more
resources for your applications by using s6.
- ManagedOOMMemoryPressure= : 8.
- ManagedOOMMemoryPressureLimit= : 8.
- ManagedOOMPreference= : 8.
Directives rated by difficulty
Use this section to answer the question: "If I were to write a converter tool
from systemd to s6, what subset of the unit file syntax should I focus on
first?"
Take this classification with a grain of salt: for instance, it does not
make sense to implement an easy directive if it's only used in the context
of a larger subsystem that's much harder to implement - typically, most
cgroups-related resource control directives.
Difficulty: 0 — directives that can be ignored
- Description=
- Documentation=
- Upholds=
- PropagatesReloadTo=
- PropagatesStopTo=
- StopPropagatedFrom=
- IgnoreOnIsolate=
- StopWhenUnneeded=
- AllowIsolate=
- CollectMode=
- SourcePath=
- Type=idle
- RemainAfterExit=
- GuessMainPid=
- ExecReload=
- TimeoutStartFailureMode=
- TimeoutStopFailureMode=
Difficulty: 1 — direct functionality mapping
- RefuseManualStop=
- FailureActionExitStatus=
- SuccessActionExitStatus=
- Type=simple, exec or oneshot
- ExitType=main
- TimeoutStartSec=
- TimeoutStopSec=
- TimeoutSec=
- Restart=always
- RestartPreventExitStatus=
- NotifyAccess=none
- ExecSearchPath=
- RootDirectory=
- SupplementaryGroups=
- LimitCPU=
- LimitFSIZE=
- LimitDATA=
- LimitSTACK=
- LimitCORE=
- LimitRSS=
- LimitNOFILE=
- LimitAS=
- LimitNPROC=
- LimitMEMLOCK=
- UMask=
- Nice=
- RuntimeDirectory=
- StateDirectory=
- CacheDirectory=
- LogsDirectory=
- ConfigurationDirectory=
- RuntimeDirectoryMode=
- StateDirectoryMode=
- CacheDirectoryMode=
- LogsDirectoryMode=
- ConfigurationDirectoryMode=
- Environment=
- EnvironmentFile=
- PassEnvironment=
- UnsetEnvironment=
- StandardInput=
- StandardOutput= (except journal)
- StandardError= (except journal)
- TTYPath=
- KillMode=process
- KillSignal=
- SendSIGKILL=
Difficulty: 2 — straightforward implementation
- Requires=
- Before=
- After=
- OnSuccess=
- DefaultDependencies=
- Type=forking
- PIDFile=
- ExecStart= (omitting some prefixes)
- ExecStartPre=
- ExecStartPost=
- ExecCondition=
- ExecStopPost=
- RestartSec=
- Restart= except on-watchdog
- RestartForceExitStatus=
- RootDirectoryStartOnly=
- WorkingDirectory=
- LimitLOCKS=
- LimitSIGPENDING=
- LimitMSGQUEUE=
- LimitNICE=
- LimitRTPRIO=
- LimitRTTIME=
- OOMScoreAdjust=
- IgnoreSIGPIPE=
- StandardInputText=
- StandardInputData=
- SyslogIdentifier=
- SyslogFacility=
- SyslogLevel=
- KillMode=none
Difficulty: 3 — requires easy additional programming
- Wants=
- Requisite=
- BindsTo=
- PartOf=
- FailureAction=
- SuccessAction=
- StartLimitIntervalSec=
- StartLimitBurst=
- StartLimitAction=
- ExitType=cgroup
- SuccessExitStatus=
- User=
- Group=
- Personality=
- CPUSchedulingPolicy=
- CPUSchedulingPriority=
- CPUSchedulingResetOnFork=
- CPUAffinity=
- NUMAPolicy=
- NUMAMask=
- IOSchedulingClass=
- IOSchedulingPriority=
- RuntimeDirectoryPreserve=
- TimeoutCleanSec=
- LoglevelMax=
- TTYReset=
- TTYVHangup=
- TTYRows=
- TTYColumns=
- TTYDisallocate=
- KillMode=control-group and mixed
- CPUAccounting=
- AllowedCPUs=
- AllowedMemoryNodes=
- MemoryAccounting=
- MemoryMin=
- MemoryLow=
- MemoryHigh=
- MemoryMax=
- MemorySwapMax=
- MemoryZSwapMax=
- TasksAccounting=
- TasksMax=
- IOAccounting=
- IOWeight=
- DisableControllers=
Difficulty: 4 — requires medium additional programming
- RuntimeMaxSec=
- RuntimeRandomizedExtraSec=
- RequiresMountsFor=
- RefuseManualStart=
- PAMName=
- CapabilityBoundingSet=
- AmbientCapabilities=
- NoNewPrivileges=
- SecureBits=
- CoredumpFilter=
- TimerSlackNSec=
- LogFilterPatterns=
- SyslogLevelPrefix=
- UtmpIdentifier=
- UtmpMode=
- CPUWeight=
- CPUQuota=
- CPUQuotaPeriodSec=
- IODeviceLatencyTargetSec=
- RestrictNetworkInterfaces=
- Delegate=
Difficulty: 5 — requires complex additional programming
- Conflicts=
- OnFailure=
- RebootArgument=
- Type=dbus
- BusName=
- ExecStop=
- NonBlocking=
- Sockets=
- DynamicUser=
- SELinuxContext=
- AppArmorProfile=
- SmackProcessLabel=
- KeyringMode=
- ReadWritePaths=
- ReadOnlyPaths=
- InaccessiblePaths=
- ExecPaths=
- NoExecPaths=
- TemporaryFilesystem=
- PrivateTmp=
- PrivateDevices=
- PrivateIPC=
- IPCNamespacePath=
- PrivateUsers=
- ProtectHostname=
- RemoveIPC=
- PrivateMounts=
- RestartKillSignal=
- SendSIGHUP=
- FinalKillSignal=
- IODeviceWeight=
- IOReadBandwidthMax=
- IOWriteBandwidthMax=
- IOReadIOPSMax=
- IOWriteIOPSMax=
Difficulty: 6 — requires a full independent implementation
of a Linux subsystem and/or a part of the systemd architecture
- OnFailureJobMode=
- RootImage=
- RootImageOptions=
- MountAPIVFS=
- ProtectProc=
- ProcSubset=
- BindPaths=
- BindReadOnlyPaths=
- MountImages=
- ExtensionImages=
- ExtensionDirectories=
- ProtectSystem=
- ProtectHome=
- All credentials-related directives
- SocketBindAllow=
- SocketBindDeny=
- DeviceAllow=
- DevicePolicy=
Difficulty: 7 — requires a full independent implementation
of a complex Linux subsystem and/or a significant part of the
systemd architecture
- Type=notify
- TimeoutAbortSec=
- TimeoutStartFailureMode=abort
- TimeoutStopFailureMode=abort
- WatchdogSec=
- Restart=on-watchdog
- NotifyAccess=
- FileDescriptorStoreMax=
- ProtectClock=
- ProtectKernelTunables=
- ProtectKernelModules=
- ProtectKernelLogs=
- ProtectControlGroups=
- RestrictAddressFamilies=
- RestrictFilesystems=
- RestrictNamespaces=
- LockPersonality=
- MemoryDenyWriteExecute=
- RestrictRealtime=
- RestrictSUIDSGID=
- WatchdogSignal=
- IPAccounting=
- IPAddressAllow=
- IPAddressDeny=
Difficulty: 8 — requires a complete implementation of complex
Linux-specific tooling
- JoinsNamespaceOf=
- PrivateNetwork=
- NetworkNamespacePath=
- SystemCallFilter=
- SystemCallErrorNumber=
- SystemCallArchitectures=
- SystemCallLog=
- IPIngressFilterPath=
- IPEgressFilterPath=
- BPFProgram=
- ManagedOOMSwap=
- ManagedOOMMemoryPressure=
- ManagedOOMMemoryPressureLimit=
- ManagedOOMPreference=
Difficulty: 9 — requires a full system analysis and remodelization
- JobTimeoutSec=
- JobRunningTimeoutSec=
- JobTimeoutAction=
- JobTimeoutRebootArgument=
- Conditions and Asserts
- USBFunctionDescriptors=
- USBFunctionStrings=
- OOMPolicy=
- RootHash=
- RootHashSignature=
- RootVerity=
- StartupCPUWeight=
- StartupAllowedCPUs=
- StartupAllowedMemoryNodes=
- StartupIOWeight=
- Slice=
Difficulty: 10 — implementing this basically means reimplementing systemd
- StandardOutput=journal
- StandardError=journal
- LogExtraFields=
- LogRateLimitIntervalSec=
- LogRateLimitBurst=
- LogNamespace=


Garret Christensen is an economist
with the Berkeley Initiative for
Transparency in the Social Sciences and
the Berkeley Institute for
Data Science. He has conducted public health research in Kenya
for Emory University and taught economics at Swarthmore
College. He has also run more than 50 ultramarathons and walked
from border to border across the entire United States four
complete times.


Label 1
Label 2
Description 1
Description 2
Flow To Target 1
Flow To Target 2
Owns Target 1
Owns Target 2
Controls Target 1
Controls Target 2


clippy.io Needs JavaScript
Lol this is definitely a react app so you aren't going to get far without javascript enabled.
Project on GitHub


A channel to discuss trading. For useful links and more info click the pinned messages to the right.
100 messages
Before 05-Dec-19 12:00 AM
jl777c05-Nov-19 11:24 PM
seems more likely as everybody knows all alts are dead
Neko05-Nov-19 11:24 PM
yep
nSPV is really something elese
seems like something satoshi himself was trying to do
thats real scaling
jl777c05-Nov-19 11:26 PM
he wrote a lot about SPV, but for equihash coins just doing headers sync is not practical
10x faster blocktimes and 20x bigger headers, makes for 200x more bandwidth/storage for SPV on KMD vs BTC
so nSPV was born
dont even need the headers at all, well just the 10 blocks in the notarized segment, or 20kb
Neko05-Nov-19 11:29 PM
he didn't imagined notary nodes
jl777c05-Nov-19 11:29 PM
true, BTC has no need for them
Neko05-Nov-19 11:31 PM
@jl777c I'm just a noob with these technical terms but I know a big coin when I see one
Neko05-Nov-19 11:50 PM
my god,clean your scren
Neko06-Nov-19 12:02 AM
wow
its tempting to take some profits here but wth I rode all the way to .50c
SHossain06-Nov-19 12:08 AM
KMD $0.77 ฿0.00008191
6
Buddz199306-Nov-19 12:09 AM
above 8.1 k
top 60 is ours for now
polycryptoblog06-Nov-19 12:46 AM
@Neko yea it needs it my bad
Novo06-Nov-19 12:46 AM
nice to see kmd moving up a little
jspook1606-Nov-19 12:47 AM
We're catching up to waves on price... What's going on?
Neko06-Nov-19 12:48 AM
justice
tolken06-Nov-19 12:48 AM
richardt06-Nov-19 01:23 AM
Hoping mostly just hodlers left in KMD
Otherwise, this will be shortlived
tolken06-Nov-19 02:42 AM
wait, isn’t it the lack of non-holdlers that got us here?
Wake me up when we’re at least 100% up from here.
It would only be short lived only because fundamentally nothing has changed. KMD still remains one of the most compelling blockchain projects out there. It’s just going through the motions. it’s time will come.
jspook1606-Nov-19 03:51 AM
Possibilities are endless. I think kmd chips pangea etc can capture a big chunk of online gambling
And dex trading
Don King06-Nov-19 04:14 AM
Looks like Sasha has finally decided to NOT honour the Coinomat asset swaps from the NXT era, his minion reports they are now done, 'on a case by case basis', but looks like nobody got anything.
https://bitcointalk.org/index.php?topic=5198933.0;topicseen
Sasha is one of the most dishonest crypto founders, fraud of his earliest investors, dragged out for nearly 4 years, done in broad daylight, shame on him!
In order to offer users a better experience and wider range of tools, the DEX will now be developed by a dedicated team and renamed Waves…
 Lower trading fees if you hold the token. The Waves coin will just be a trading pair for all other coins.
Flint06-Nov-19 06:41 AM
binance blocked komodo funds deposit and withdrawal
Flint06-Nov-19 06:50 AM
this is the manipulation of the market - to force to take profits at the current price and force to sell KMD since it is impossible to withdraw! The bloody exchanges didn’t even bother to notify coin holders that their funds would be blocked for any reason and you just go into your account and see that you cannot withdraw or deposit funds - they will push people into the arms of DEX
CHMEX06-Nov-19 07:00 AM
There is a KMD update coming out. So its reasonable
Crabby Paddy06-Nov-19 07:12 AM
I looked up komodo in the main crypto groups on fb and saw it mentioned like 3 times since 2017 hopefully we as a community can grow komodo in 2020
Crabby Paddy06-Nov-19 07:22 AM
Are there any social media bounties currently?
Cryptoon06-Nov-19 07:31 AM
There was a form with all the bounties
But mostly if a strong community makes a big push, everyone wins
Crabby Paddy06-Nov-19 07:38 AM
Agreed, I mean it’s not needed. But it would be good and might bring the right talent into Komodo too
Oszy06-Nov-19 08:19 AM
there was a twitter post, or an announcement here encouraging people to share the love on social media for rewards
Cryptoon06-Nov-19 08:28 AM
Yeah there was a form with a list of bounties, if you look in #official📢 you could probably find it
Could this now be bitcoin's next critical and important levels? Has bitcoin likely bottomed? We look at the charts. #Bitcoin #BTCUSD #AlessioRastani For Paul...
Mark8106-Nov-19 09:55 AM
@Cryptoon yes the were. Satinders mined coins went to airdrop to everyone thst participated to give ARRR address for drop.

An airdrop technically is done to all addresses, but as you dont know if a zaddr exists its hard to do an airdrop
jorian06-Nov-19 10:05 AM
at the time, we were giving out quite some ARRR, dollar wise
I've published a post detailing the 5 alts I expect to significantly outperform Bitcoin in 2020: https://t.co/2wEHmbXSkp
I've given an overview of fundamentals, price-histories and speculative prospects.
Spoiler: The 5 alts are $KMD, $NKN, $FTM, $DAG and $VIDT
Enjoy th...
Dear Bilaxy Users,
Komodo (KMD) was listed on https://bilaxy.com/. Bilaxy will support Komodo ecosystem.
KMD listing details as followed:
Trading market: KMD/BTC
Deposit/Withdrawal:enabled
Trad...
Bilaxy will support Komodo ecosystem.
Gordon Komodo06-Nov-19 10:48 AM
kmd base pair incoming , hopefully
hyperDEX06-Nov-19 11:10 AM
Another binance clone/chinese exchange it seems
siu - Chainmakers06-Nov-19 11:12 AM
Chinese exchange?
Will volume from china start pouring in kmd?
Taking into account chinese stats has us in the top 20 rank i can see its plausible
hyperDEX06-Nov-19 11:14 AM
Need USDT pair i think
siu - Chainmakers06-Nov-19 11:14 AM
Is USDT pair a big thing in china?
hyperDEX06-Nov-19 11:14 AM
Our old mate CZ could help
Yes, that is most of the trading volume there
siu - Chainmakers06-Nov-19 11:15 AM
Can someone text CZ and let him know we need USDT pair
Markus06-Nov-19 11:16 AM
I think that guy on twitter is over hyping things, he is writing that those coins will slightly outperform bitcoin 2020 and then u read this
Prediction: 30,000 satoshis in 2020
siu - Chainmakers06-Nov-19 11:16 AM
Who?
Markus06-Nov-19 11:16 AM
what JL linked above
Nik Patel
siu - Chainmakers06-Nov-19 11:16 AM
Oh
hyperDEX06-Nov-19 11:16 AM
30k sats is a lot?
I can remember the days where i thought bloody hell this has been trading sideways at 30k for a few weeks now......not at 8k lol
1
Markus06-Nov-19 11:17 AM
meh we were at 30k during bear market mini alt season early 2019
but sure if kmd will reach 30k and btc 20k, thats also good
hyperDEX06-Nov-19 11:18 AM
Would rather 100k sats at 10k
Markus06-Nov-19 11:19 AM
ye ofc
hyperDEX06-Nov-19 11:19 AM
We can all dream
Markus06-Nov-19 11:19 AM
at all i think it will be very hard to predict how things will go, crypto is maturing in rapid speed
hyperDEX06-Nov-19 11:19 AM
Bitcoin diamond still worth more.....that is how i know we are under valued
yep, futures killed volatility basically and the more products we have the harder for whales to push it up or down
Pretty cool of @Bilaxy_exchange to list @KomodoPlatform on their own!
Giving credit to the $KMD ecosystem, wonder which projects in the ecosystem they are eyeing as well? $ARRR $VRSC $OOT?
https://t.co/6n2bBADvJE


R package to compute Incoming Solar Radiation (insolation) for palaeoclimate studies. Features three solutions: Berger (1978), Berger and Loutre (1991) and Laskar et al. (2004). Computes daily-mean, season-averaged and annual means for all latitudes.
| Version: | 0.93 |
| Depends: | R (≥ 2.10), stats, gsl |
| Published: | 2016-03-05 |
| Author: | Michel Crucifix |
| Maintainer: | Michel Crucifix <michel.crucifix at uclouvain.be> |
| License: | file LICENSE |
| URL: | https://bitbucket.org/mcrucifix/insol |
| NeedsCompilation: | no |
| Materials: | README |
| CRAN checks: | palinsol results |
| Reference manual: | palinsol.pdf |
| Package source: | palinsol_0.93.tar.gz |
| Windows binaries: | r-devel: palinsol_0.93.zip, r-release: palinsol_0.93.zip, r-oldrel: palinsol_0.93.zip |
| OS X binaries: | r-release: palinsol_0.93.tgz, r-oldrel: palinsol_0.93.tgz |
| Old sources: | palinsol archive |
Please use the canonical form https://CRAN.R-project.org/package=palinsol to link to this page.


public class Controller
extends java.lang.Object
| Constructor and Description |
|---|
Controller(Game_Profile game_Profile,
Base_Component base_Component)
Construct a game_Profile and update with Base_Component class
|
| Modifier and Type | Method and Description |
|---|---|
void |
AnimalAllowance()
AnimalAllowance A set of algorithm that calculate animal allowance and get called in every new Day
Allowance for Animals {cow, goat, chicken}:({150,100,50}*happiness)
Update Inventory, Stats, Dialog if action is performed
|
void |
chopTree()
chopTree A set of algorithm that allow user to perform chop tree action if they meet the condition
Then update Dialog to show message, update Inventory and stats if data is changed
|
void |
FarmerType_advantage()
FarmerType_advantage A set of algorithm to check farmer type and provide advantage respectively
Type {0, 1, 2, 3} ; {Extra energy daily, Extra happiness daily, Extra 30G for selling crops, Challenge mode - None}
|
void |
feedAnimal() |
void |
fertilizer()
fertilizer Allow user to perform fertilizing to all crops which update the daily Watering status to true
Fertilizing consume energy and need to be bought from supermarket
|
void |
MorningMessage()
MorningMessage Display a message in Dialog to show it's the Next day
Update Dialog
|
void |
relicChair() |
void |
setDialog(java.lang.String text) |
public Controller(Game_Profile game_Profile, Base_Component base_Component)
game_Profile
- Access the data (model class) from Game_Profilebase_Component
- Access to update stats ,energy ,inventorypublic void chopTree()
public void feedAnimal()
public void AnimalAllowance()
public void FarmerType_advantage()
public void MorningMessage()
public void relicChair()
public void fertilizer()
public void setDialog(java.lang.String text)


| Total net profit | -402.05 | Gross profit | 423.16 | Gross loss | -825.21 |
| Profit factor | 0.51 | Expected payoff | -4.06 | ||
| Absolute drawdown | -436.53 | Maximal drawdown (%) | 398.85 (-1058.52%) | ||
| Total trades | 99 | Profit trades (% of total) | 45 (45.45%) | Loss trades (% of total) | 54 (54.55%) |
| Long positions (won %) | 46 (45.65%) | Short positions (won %) | 53 (45.28%) | ||
| Largest | profit trade | 40.21 | loss trade | -37.68 | |
| Average | profit trade | 9.4 | loss trade | -15.28 | |
| Minimum | profit trade | 1.23 | loss trade | -0.56 | |
| Maximum | take profit in pips | 3860.0 | stop loss in pips | -3400.0 | |
| Average | take profit in pips | 910.6 | stop loss in pips | -1482.1 | |
| Minimum | take profit in pips | -60.0 | stop loss in pips | -450.0 | |
| Maximum | Reward-Risk | 8.6 | Duration in minutes | 4151 | |
| Average | Reward-Risk | 0.8 | Duration in minutes | 306.8 | |
| Minimum | Reward-Risk | 0.0 | Duration in minutes | 0 | |
| Maximum | consecutive wins (profit in money) | 7.0 (49.78) | consecutive losses (loss in money) | 6.0 (-106.69) | |
| Average | consecutive wins | 2.0 | consecutive losses | 2.0 |
| Total net profit | -198.23 | Gross profit | 189.24 | Gross loss | -387.47 |
| Profit factor | 0.49 | Expected payoff | -4.31 | ||
| Absolute drawdown | -203.97 | Maximal drawdown (%) | 209.83 (3580.72%) | ||
| Total trades | 46 | Profit trades (% of total) | 21 (45.65%) | Loss trades (% of total) | 25 (54.35%) |
| Largest | profit trade | 40.21 | loss trade | -37.58 | |
| Average | profit trade | 9.01 | loss trade | -15.5 | |
| Minimum | profit trade | 1.81 | loss trade | -0.56 | |
| Maximum | take profit in pips | 2570.0 | stop loss in pips | -3320.0 | |
| Average | take profit in pips | 825.7 | stop loss in pips | -1684.3 | |
| Minimum | take profit in pips | -60.0 | stop loss in pips | -700.0 | |
| Maximum | Reward-Risk | 2.5 | Duration in minutes | 3896.0 | |
| Average | Reward-Risk | 0.6 | Duration in minutes | 260.6 | |
| Minimum | Reward-Risk | 0.0 | Duration in minutes | 0.0 | |
| Maximum | consecutive wins (profit in money) | 5.0 (27.79) | consecutive losses (loss in money) | 5.0 (-66.08) | |
| Average | consecutive wins | 2.0 | consecutive losses | 2.0 |
| Total net profit | -203.82 | Gross profit | 233.92 | Gross loss | -437.74 |
| Profit factor | 0.53 | Expected payoff | -3.85 | ||
| Absolute drawdown | -255.58 | Maximal drawdown (%) | 217.9 (-578.29%) | ||
| Total trades | 53 | Profit trades (% of total) | 24 (45.28%) | Loss trades (% of total) | 29 (54.72%) |
| Largest | profit trade | 26.46 | loss trade | -37.68 | |
| Average | profit trade | 9.75 | loss trade | -15.09 | |
| Minimum | profit trade | 1.23 | loss trade | -4.98 | |
| Maximum | take profit in pips | 3860.0 | stop loss in pips | -3400.0 | |
| Average | take profit in pips | 984.3 | stop loss in pips | -1306.6 | |
| Minimum | take profit in pips | 70.0 | stop loss in pips | -450.0 | |
| Maximum | Reward-Risk | 8.6 | Duration in minutes | 4151.0 | |
| Average | Reward-Risk | 1.0 | Duration in minutes | 347.0 | |
| Minimum | Reward-Risk | Duration in minutes | 3.0 | ||
| Maximum | consecutive wins (profit in money) | 7.0 (50.38) | consecutive losses (loss in money) | 6.0 (-106.69) | |
| Average | consecutive wins | 1.0 | consecutive losses | 2.0 |