{ name: "optional string", format: function(str), // required method that returns value parse: function(value), // required method that returns string invalid: function(value), // optional helper function for `parse` expectation: 'optional error message describing expected syntax' }As you can see, the minimum required interface is the
format
and parse
methods.
Formatting grid cell values is purely a text string manipulation. Any other graphical effects are the purview of cell renderers (not covered here). Cell editors can include fancy controls for manipulating the string, but the result needs to be a formatted string, parsable into a serializable value for storing into the data model.
The parse method is only invoked by Hypergrid when a formatted cell is edited.
If cell editing on the target cells is disabled, the `parse` function will never be invoked.
While it may be tempting to supply a no-op function in such a case,
it is always a good practice to code a functional parse
method.
Can you be certain it will never be made editable in the future?
Consider also that sorting and filtering plug-ins will want to invoke this method to parse their input.
RegExp
. For example (replace regex
with an actual regex):
invalid: function(str) { return !/^regex$/.test(); }Should be implemented when parse is not bulletproof (when it would jam unexpectedly on bad syntax). When implemented, invalid is called first; parse is only called if the syntax is valid (invalid returns falsy; that is, “not invalid”).


Study subjects. A total of 1176 patients were enrolled in the present study. Of these, 306 and 183 patients were allocated to SVR (+) and SVR (−) subgroups, respectively, and 687 patients were allocated to the no-treatment group. SVR = sustained virologic response.


For Researchers
For Organizations
About
Help
SIGN IN
Register for an ORCID iD
Learn more
Funders
Research Organizations
Publishers
Associations
Integrators
What is ORCID
The ORCID Team
The ORCID Community
Events
News
FAQ
Give Feedback
Contact us
Knowledge Base
Resources
OUTREACH RESOURCES
Ambassadors
USE CASES
Membership
THE ORCID API
REGISTER A CLIENT APPLICATION
CURRENT INTEGRATIONS
INTEGRATION CHART
BETA TESTERS
Our Mission
Our Principles
OUR GOVERNANCE
OUR POLICIES
Working Groups
Sponsors
Launch Partners
Members
OPEN SOURCE
PARTNERS
ADOPTION AND INTEGRATION PROGRAM
ORCID GEAR
MEMBERSHIP COMPARISON
Standard Member Agreement
Our Members
STANDARD CREATOR MEMBER AGREEMENT
BLOG
SUBSCRIBE!
SIGN OUT
DISPUTE PROCEDURES
privacy policy
Public Client Terms of Service
PUBLIC DATA FILE USE POLICY
Trademark and iD Display Guidelines
registry
website
Search...
Search the ORCID registry
Search Results
Account Settings
Developer tools
Manage members
Admin page
Member Tools
Learn more
ORCID Record
My ORCID Record
Inbox
affiliation or organization ID
First page
Items per page:
Last page
Next page
Previous page
of
Oh no! An error occurred
We couldn't recover your account details. Please try again, and if the error
persists please
We couldn't complete your registration. Please try again, and if the error
persists please
Please try again, and if the error persists please
Could this be you?
visit our knowledge base.
We found some accounts with your name, which means you may have already
created an ORCID iD using a different email address. Before creating an
account, please confirm that none of these records belong to you. Not sure if
any of these are you?
Contact us.
First Name
Last Name
Affiliations
Date Created
View Record
I ALREADY HAVE AN ID, GO BACK TO SIGN IN
NONE OF THESE ARE ME, CONTINUE WITH REGISTRATION
Password must not be the same as your email address
Membership
Documentation
News & Events
footer
orcid mini logo
main menu
language
Maintenance message
Search
statistics
Warning, testing website
Institution
Clear
News
info about names
close
delete email
info about emails
info about password
info about two factor authentication
Close
YOUR RECORD
PERMISSIONS
ANNOUNCEMENT
has made changes to your ORCID record
Connecting your
account with your ORCID record
Affiliations
Bio
Distinction
Education
Employment
External Identifiers
Funding
Invited Position
Membership
Peer Review
Preferences
Qualification
Service
Research Resource
Work
unknown
Added
Updated
Deleted
Other
archive
Reactivating your account
We couldn't reactivate your ORCID account. Please try again, and if the error
persists please
Get your ORCID iD
Add/update other information about you (country, keywords, etc.)
Add/update your research activities (works, affiliations, etc)
Read your information with visibility set to Trusted Organizations
Allow this organization or application to get your 16-character ORCID iD and
read information on your ORCID record you have marked as public.
Allow this organization or application to add information about you (for
example, your country, key words, other identifiers - but not your biography)
that is stored in their system(s) to the lefthand section of your ORCID
record. They will also be able to update this and any other information they
have added, but will not be able to edit information added by you or by
another trusted organization.
Allow this organization or application to add information about your research
activities (for example, works, affiliations) that is stored in their
system(s) to your ORCID record. They will also be able to update this and any
other information they have added, but will not be able to edit information
added by you or by another trusted organization.
Allow this organization or application to read any information from your
record you have marked as limited access. They cannot read information you
have marked as private.
Your Oauth request is invalid
Show advanced search form
Hide advanced search form
paginator
bottom paginator
Cookies Policy
contact support.
Show details
Hide details
Edit
Add your biography
Add given name
Add family name
Add a published or credit name
Add other name
Link Title
Link URL
Keyword
Peer review
Funding
Add Item
Sort Items
Add Employment
Sort Employments
Add Education
Sort Education
Add Invited Position
Sort Invited Positions
Add Membership
Sort Memberships
Add Funding
Sort Fundings
Add Work
Sort Works
Sort Research Resources
Add Peer Review
Sort Peer Reviews
Total funding amount
Contributors
Description
Funding subtype
Translated title
Research resources


Alara's five shards are one again, igniting new magics and mayhem. It's all as Nicol Bolas planned. But can he be stopped before this plane is destroyed?
The five shards of Alara were separate worlds for centuries, each one flowing with only three colors of mana. Their worlds and cultures evolved independently: Bant, an orderly, sunlit kingdom; Esper, a hegemony of wizards and sphinxes; Grixis, an undead-infested hellscape; Jund, a primordial hunting-ground ruled by dragons; and Naya, a lush jungle paradise.
But now they have converged into one, and the rejoined plane flows with all five colors of mana once more. Waves of raw power crash across the former planar boundaries, bringing long-forgotten magics to all the shards and mingling them in unprecedented ways.
As the boundaries between the shards dissolve, cultures clash and wars ensue.
The forces of Esper invade the other shards looking for carmot, an element necessary to create more of their dwindling etherium. Hordes of Grixis undead mount an assault to maim, enslave, and drain the life energy from other shards. The warriors of Jund extend their "life hunts" to the newfound game throughout Alara's vast hunting grounds. Naya's forces follow the elves' decrees and march out of the jungle, searching for answers to the Anima's prophetic visions. And the armies of Bant clash with the horrors swarming over their borders, defending their homeland in the name of their guardian angels.
At each front, the shards' legions pummel one another with powerful magics, calling on every spell they know to defeat the other shards.
Nicol Bolas, the ancient dragon Planeswalker, planned this all along. He came to Alara to feed on its rich mana and, in one massive ritual, restore its lost power as part of his multiplanar plan. Only a fellow Planeswalker has hope of discovering his schemes—but even a Planeswalker would likely die trying to stop him.
Alara has become a single plane once more.
The Esper shard of Alara strives to augment all living things with etherium, an aether-infused alloy. Esperites believed the etherium supply was finite. But, while exploring Jund, Breya discovered carmot, the red stone necessary to create etherium. Breya replaced most of her body with etherium she created. Then her etherium was influenced by the wild magic of Jund and she gained powerful abilities.
The House of Renn is one of the most influential families among the elite of Esper, and Silas is its heir. A gifted mage, Silas trained to join the Seekers of Carmot, an order of mages who claim to know the true nature of etherium and how to create more of the precious metal. Silas rose quickly through their ranks, and he was honored with the first etherium heart ever produced.
An ogre from the Grixis shard of Alara, Yidris was afflicted with unstable mutations that threatened to shatter his mind. No magic could relieve his curse. After Grixis collided with the other shards during the Conflux, knights from Bant drove Yidris into a volatile storm of raw mana. The unpredictable power of this Maelstrom stabilized his mutations and made Yidris a conduit for its own chaos.
In the predator-filled land of Jund, Karrthus was the mightiest there was. Admired by Sarkhan Vol, Karrthus was captured by Nicol Bolas and forced into servitude. This desecration of Karrthus's power planted a seed of dissatisfaction Sarkhan, who started questioning his own commitment to Bolas.
This minion to Nicol Bolas helped orchestrate the great conflux. Malfegor later led the forces of Grixis in destroying much of Esper—until those forces began spilling into Bant, where he was slain by Elspeth Tirel’s army.
Rakka Mar is a shaman highly skilled at manipulating fire and rage. During Sarkhan Vol's stay on Jund, Rakka Mar became impressed by Sarkhan’s combat prowess and survival instincts, resulting in a fated introduction to Rakka’s master, Nicol Bolas.
A powerful shaman and leader of all the Cylian elves on Naya, Mayael is still young by elven standards. After communing with the soul of the world, she became devoted to amassing an army to defend Naya from an imminent dragon invasion of the Jund.
The soul of the Alara plane, Progenitus took the form of a massive five-headed hydra. But when the original splitting of the shards severed the connection to blue and black on Naya, Progenitus fell into a deep slumber. Only when the conflux occurred, reuniting Alara, did he awake.
Honorable to a fault, the humans of Bant build massive castles and pristine marvels of architectural beauty. Conflicts on Bant are resolved by single combat, with each side choosing a champion to fight for them.
Cold metallic perfection defines all things in Esper. Humans here strive to join the Seekers of Carmot on their quest to unlock the secrets of etherium. Once the rare element can be supplied in mass, they hope to finally achieve their goal: creating the perfect etherium-augmented beings.
Surrounded by demons and horrors of all kinds, humans are hunted mercilessly on Grixis. Amid the stagnant life energy permeating the plane, humans are only able to stay alive by keeping one step ahead of their pursuers and relying on pure inventiveness.
On Jund, only the strongest survive—and none are stronger then the primal dragons that number in the thousands. Humans on Jund persist by hunting together. The hunter with the most kills leads the tribe in battle as well as all other matters of community.
Humans on Naya band together to track, hunt, and work in harmony with the massive beasts of the forest. Acknowledging the beasts’ power and capacity for widespread destruction, humans have learned to herd them away from their encampments… or into enemy territory.
With their calculated thinking and level heads, the vedalken often rise to lead the Seekers of Carmot, directing them to search for ever more etherium. Under the care and advice of the vedalken, Esper was transformed piece by piece into the perfection only achieved through etherium augmentation.
Forced to not waste a scrap of life, there is little that dies in Grixis that is not animated by a necromancer seeking power and security. Within this stagnant lifelessness, zombies roam a raw, flesh-soaked landscape.
The dragons of Jund are massive, majestic creatures. They rule the land fully knowing their position at the top of the food chain—and they take every opportunity to reinforce that fact to any other creatures that dare cross them.
Goblins survive on Jund by sheer force of numbers and accepting their low position on the food chain. This acceptance has led to huge ceremonies, where goblins willingly offer up one of their own as a tasty sacrifice to appease the mighty dragons.
The leonin hunt Naya’s massive beasts for sustenance. Planeswalker Ajani is one of their own, though an outcast for his white albino fur. After his fight with Nicol Bolas, Ajani returned to his pride with a renewed sense of authority, becoming their leader.
The elves of Naya live in harmony with nature and the many gargantuan beasts that surround them. They follow the visions of their current anima, Mayael, whose guidance helps ensure their survival.
Elder dragon and tyrant of worlds, Nicol Bolas is one of the oldest known beings in the Multiverse. His malevolence is matched only by his boundless intellect.
Ajani Goldmane is torn between his leonin ferocity and his sense of justice. He was born on Naya and became an outcast within his own family, an albino leonin never accepted by the rest of his pride.
White knight of community and fortification, Elspeth left her embattled homeland in search of a new place to call home.
A red-green shaman, Sarkhan is from a plane where warlords hunted dragons to extinction. He now searches the Multiverse for a dragon worthy of his worship.
This artificer’s body is enhanced by the magical alloy etherium. Enslaved by one Planeswalker and mind-wasted by another, he continues to seek perfection of body and mind.


YUI Test Coverage
YUI Test Coverage is a code coverage tool for JavaScript. It is designed for use with the YUI Test JavaScript library to track the parts of your code that are being tested.
What is Code Coverage?
Code coverage analysis is a process where code that is being tested is also tracked. Once all tests are complete, a code coverage report tells you which lines of code were executed during the test (some coverage tools also tell you which functions were called). In effect, you're seeing which parts of your code have been "covered" by the tests. You should always aim for a high code coverage rate (around 90%) to ensure that your code is being fully exercised.
Installation
The YUI Test Coverage utility requires Java 5 (1.5) or higher. There are two JAR files:
yuitest-coverage-x.y.z.jar
- used to instrument JavaScript code.yuitest-coverage-report-x.y.z.jar
- used to generate reports from the JSON code coverage output.
IMPORTANT: In order to use this tool, you'll need to use the following YUI Test versions:
- YUI Test Standalone 1.0.0+
- YUI Test for YUI 2.8.1+
- YUI Test for YUI 3.1.1+
Other versions of YUI Test are not supported.
General Usage
There are four steps to using YUI Test Coverage. These must be executed in order for coverage statistics to be generated.
Step 1 - Instrument Your Code
The first step is to instrument your JavaScript files using yuitest-coverage-x.y.z.jar. The coverage instrumenter uses a JavaScript parser to evaluate JavaScript code and insert code used to track coverage information. The use of a parser ensures that the instrumented code will still execute and not fundamentally change the structure of the original code.
There are two ways to instrument code: one file at a time or a directory at a time. To instrument a single file, use the following command:
java -jar yuitest-coverage.jar -o <output_filename> <input_filename>
This command takes the <input_filename>
, instruments it, and places the result in <output_filename>
.
To instrument an entire directory, including subdirectories, use the following command:
java -jar yuitest-coverage.jar -d -o <output_directory> <input_directory>
This command looks in <input_directory>
and all of its subdirectories for files ending in .js
. Those files are then instrumented and a mirror of the directory structure is created in <output_directory>
with all of the instrumented JavaScript files.
Step 2 - Include Instrumented Code in Tests
In order to gather code coverage data, the instrumented code must be run through a series of tests. You can create YUI Test tests as normal, just be sure to include the instrumented JavaScript files instead of the originals. As the tests are executed, code coverage data is collected and stored by YUI Test.
Step 3 - Extract Code Coverage Data
When all tests have been concluded, you can retrieve the code coverage results in JSON format using:
- YUI Test Standalone:
YUITest.TestRunner.getCoverage(YUITest.CoverageFormat.JSON);
- YUI Test for YUI 2.x:
YAHOO.tool.TestRunner.getCoverage(YAHOO.tool.CoverageFormat.JSON);
- YUI Test for YUI 3.x:
Y.Test.Runner.getCoverage(Y.Coverage.Format.JSON);
This JSON structure represents all of the coverage data for the tests. You can either manually take this data and save it to a file, or submit this data to a server.
Step 4 - Generate Coverage Report
With the JSON coverage data saved in a file, you can use the coverage report tool to generate a report, using the following command:
java -jar yuitest-coverage-report.jar -o <output_directory> <input_filename>
This takes all of the coverage information from <input_filename>
(oftentimes, the file contains data for more than one JavaScript file) and creates an HTML report in <output_directory>
. You can then open index.html
to view all of the results.
If you'd prefer to have LCOV formatted-files for import into other coverage tools, you can specify this using the --format
option:
java -jar yuitest-coverage-report.jar --format LCOV -o <output_directory> <input_filename>
This will output LCOV files into <output_directory>
.
Note on Automation
If you're using the Selenium Driver, steps 3 and 4 are done automatically. The Selenium Driver looks for coverage data and, if available, extracts it and exports into the specified format.
Command Line Interfaces
File Instrumenter
Used to instrument JavaScript files.
Usage: java -jar yuitest-coverage-x.y.z.jar [options] [file|dir]
Global Options
-h, --help Displays this information.
--charset <charset> Read the input file using <charset>.
-d, --dir Input and output (-o) are both directories.
-v, --verbose Display informational messages and warnings.
-o <file|dir> Place the output into <file|dir>. Defaults to stdout.
The options are:
- The
--charset
option specifies the character set of the input files. - The
-d
or--dir
option specifies that the input and output are directories rather than files. - The
-o
option specifies the output file or output directory for the instrumented code. - The
-v
or--verbose
option specifies that additional debugging messages should be output to the console.
Coverage Report
Used to create reports from JSON coverage data.
Usage: java -jar yuitest-coverage-report-x.y.z.jar [options] [file]
Global Options
-h, --help Displays this information.
--format <format> Output reports in <format>. Defaults to HTML.
-v, --verbose Display informational messages and warnings.
-o <file|dir> Place the output into <file|dir>.
The options are:
- The
--format
option specifies the coverage format to produce. Values areLCOV
,GCOV
, andHTML
(default). - The
-o
option specifies the output directory for the report files. - The
-v
or--verbose
option specifies that additional debugging messages should be output to the console.
Troubleshooting
Unsupported Class Version Error
You may end up seeing an error such as:
Exception in thread "main" java.lang.UnsupportedClassVersionError:
com/yahoo/platform/yuitest/coverage/YUITestCoverage (Unsupported major.minor
version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
If you get this message, it means that you're using a version of Java older than 1.5. Upgrade your JDK/JRE to 1.5 and try again.


The english version of this page has been generously translated from french by Anna Mondeteguy.
jQuery Superbox! is a script which allows you display windows with the lightbox effect.
This script is a plugin for jQuery (1.3.x).
Why create a new script of this kind, when many exist already?
rel
attribute is used to launch the script. The href
attribute is therefore coherent: it targets the address of a picture, of a page, or an element identifier (anchor).jQuery Superbox! can display pictures, pictures galleries, external pages, a page element or even AJAX loaded content.
The minified version of Superbox is 2kb when using GZip compressing, 5.4kb otherwise.
Donwload jQuery Superbox! 0.9.1 (zip)
You want to participate? Don't hesitate to visit the Bittbucket project webpage; there you can report bugs, suggest improvements and contribute to the code: http://bitbucket.org/bpierre/jquery-superbox/
To install this script, you must include on your page jQuery, as well as the files jquery.superbox-min.js (minified version) and jquery.superbox.css:
<link rel="stylesheet" href="jquery.superbox.css" type="text/css" media="all" />

By default, the superbox is generated from the rel
attribute of a link. It must contain the word superbox
, followed by the display mode in square brackets: rel="superbox[display_mode]"
.
The code name will eventually be associated to an id
and one or several class
(CSS syntax) which will be applied to the generated window: rel="superbox[type#my_id.my_class]"
.
The parameters specific to the display mode will then be put behind, in square brackets.
The windows is placed in position:fixed
, except if its height exceeds the display area. In that case, it will go in position:absolute
, which will allow to see the whole zone using the browser's scroll bars.
To activate jQuery Superbox!, the $.superbox()
method must be executed at the page's loading:
$(function(){
$.superbox();
});
Some parameters can be defined; all are optional. The default values are as follow:
$.superbox.settings = {
boxId: "superbox", // Id attribute of the "superbox" element
boxClasses: "", // Class of the "superbox" element
overlayOpacity: .8, // Background opaqueness
boxWidth: "600", // Default width of the box
boxHeight: "400", // Default height of the box
loadTxt: "Loading...", // Loading text
closeTxt: "Close", // "Close" button text
prevTxt: "Previous", // "Previous" button text
nextTxt: "Next" // "Next" button text
};
Displays a box containing a picture.
Superbox picture (auto dimensions)
Superbox picture (defined width)
Superbox picture (defined height)
By default, the dimensions take those of the picture (it's possible to add a padding with css):
SuperBox
But it is also possible to specify the dimensions :
SuperBox
Width only:
SuperBox
Height only:
SuperBox
If the picture's height exceeds the box's height, the specified height is ignored.
If a title
attribute exists on the link, it will be transfered over to the picture. If not, it's the text of this link which will be taken for the title
attribute of the picture.
Displays a picture gallery. It is possible to navigate using the buttons or the arrow keys.
The second parameter will be the gallery's name. All links wearing this name will be part of the same galley.
By default, the dimensions take those of the picture (it's possible to add a padding with css):
SuperBox
But it is also possible to specify the dimensions:
SuperBox
Width only:
SuperBox
Height only:
SuperBox
If the picture's height exceeds the box's height, the specified height is ignored.
Generates a box containing an iframe.
Iframe Superbox (default dimensions)
Iframe Superbox (defined dimensions)
SuperBox
Generates a box containing an element of the page.
The link will be external, and will point to an element of the page using its id
attribute.
This element will be copied to appear in Superbox.
SuperBox
Generates a box containing an HTML fragment loaded with AJAX.
The link point to a complete HTML document (non-intrusive version), while the AJAX URL takes place in second parameter.
SuperBox


Changelog
- Auto-complete cell editor.
- Batch edit improvements.
- Vscroll improvements.
- Copy/paste selection to excel.
- Live data plugin.
- Float Row Navigation.
- Group keyboard navigation improvements.
6.2.1 - 2018-08-20
Added
- Edit form support.
- Travis CI.
- Cucumber specs infrastructure.
- Edit cell validation support.
Fixed
- Blanks position in the column filter.
6.2.0 - 2018-08-02
Fixed
- Column filter
blanks
is removed when reset clicked.
Added
- Column hierarchy and dnd support in the column chooser.
- Cohort column dnd support.
BREAKING
model.columnList().index
now contains tree of columns, not a column key list.
6.1.5 - 2018-07-03
Fixed
- Row highlight in details modes.
- Mark q-grid for check on invalidate, that allows to have basic functionality when q-grid host has onPush strategy.
Added
- Basic theme array, url and email support.
6.1.4 - 2018-06-28
Fixed
- Time cell editor.
- Fix q-grid-embedded array cell look.
- Percent width are aware of pad column padding.
- Show horizontal scroll-bar if there are no data rows, but some columns are present.
- Observables in dropdown editors.
Added
- Beta version of row virtual scrolling.
- Tab-trap component for the url and email editors.
- Column groups manipulation through the structural directives.
- Import from csv, pdf, xlsx, json.
- Export to csv, pdf, xlsx, json.
Changed
- Improve performance of Style API using dom bags directly.
6.1.3 - 2018-06-21
Fixed
- Fixed AOT compilation.
- Fixed time editor value assign.
- Dark theme for plugins and cell handler.
- Textarea editor now shows length of the input text.
6.1.1 - 2018-06-15
Fixed
- Highlight on drag and drop.
- Pager target should be closed after enter hit.
Changed
- Column Filter, Column Chooser, Query Builder, Persistence Plugins became responsible.
6.1.0 - 2018-06-15
BREAKING
- Need to change theme import from
import { ThemeModule } from 'ng2-qgrid'
to import { ThemeModule } from 'ng2-qgrid/theme/material
Deprecated
- Use
FetchContext
serach
property instead of filter
property.
- Use
<q-grid caption="My Grid">
instead of <q-grid header="My Grid">
.
Added
- Support of custom themes, we are not linked tight with angular/material any more.
- 113+ Examples.
- Readonly strategies
<q-grid interactionMode="full | readonly | detached">
.
- Spanned headers and column groups.
- Group summaries.
PluginServices
that allows to write own plugins for q-grid.
- Better caching strategies for renders.
- New
rowspan
mode for groups.
- New
rowList
model.
- Drag and drop column support in
column chooser
.
- Initial basic theme.
- Float(fixed) rows support through the
model.row()
pin
property.
- New column generation mode
cohort
.
- Action trigger template support.
Changed
- Live
drag and drop
for rows and columns.
- Use
Model Proxy
for resource utilization.
- New
Dom matrix
engine for rendering.
- Reference column API.
- Pin columns are highlighted when scroll horizontal.
Fixed
- Better row details rendering.
- Fixed focus position on scene render (e.g. sort, filter etc.).
- Column sort algorithm became more predictable.
- Array cell editor doesn’t work with keyboard.
5.3.10 - 2018-05-21
Added
ToggleAll
command that can be override to intersect toggle all groups action.
Changed
- Clicking on group header leads to collapse/expand of all nodes in the view.
- By default child node label is empty.
Fixed
Group pipe
index calculation - the root cause of invalid filtering.
5.3.9 - 2018-05-18
Added
- Focus method to the grid service.
Changed
- AOT Compatible.
- Angular CLI as app starter.
- Rollup scripts to build the library.
Fixed
- FocusAfterRender service.
- Column filter IsBlank is displayed in chips.
- Legend template syntax.
- TypeScript defenitions.
- Async pipe for rows property.
5.3.7 - 2018-07-08
Added
- Template support of column filter items.
Fixed
- Column sort plugin uses
FocusAfterRender
only on click.
5.3.6 - 2018-04-20
Added
Persistence
plugin - added groups.
5.3.5 - 2018-04-19
Added
Query builder panel
component styles are standalone.
5.3.4 - 2018-04-18
Added
Query builder
plugin.
- Cell batch update.
5.3.3 - 2018-04-13
Added
Persistence
plugin.
Status bar
plugin.
- Selected chips in
column filter
plugin.
- Focus cell when after sort or filter column.
Fixed
5.3.2 - 2018-03-23
Added
- Supporting of custom fetch in the column filter.
- Virtual scroll module.
- Pager target menu.
Changed
- Added grid core pipes under ther
ng2-qgrid
namespace.
- Remove
popup
module.
Fixed
- Pager custom size and sizeList not being honored/rendered correctly.
- Rename
action-bar-core
to action-bar
.
5.2.4 - 2018-02-16
Changed
- Renamed
action-bar-core
to action-bar
.
layout="row"
refactored to class="layout-row"
.
- Export q-grid
common module
to make q-grid-position
directive available for the end user.
Fixed
- Url editor.
- Text alignment in the file editor.
- Navigation should trigger detect changes.
5.2.3 - 2018-02-12
Fixed
- Embed style for
row-options
column type.
- TypeScript declarations.
5.2.2 - 2018-02-12
Fixed
- Remove
BrowserModule
from componentns to allow lazy loading.
- Fix column filter and column chooser styles.
5.2.0 - 2018-02-09
Added
- Column viewWidth property.
- Filter
by
property blanks
option support.
Changed
- Show (Blanks) checkbox in column filter if there is empty string, null or undefined in the list.
- Explicitly set
display: inline
for label in column sort plugin.
- Change q-grid-embed styles.
Fixed
- Better layout of column filter and column sort icons.
5.1.2 - 2018-01-03
Added
- Possibility to change row size
<q-grid-row [canResize]="true"
.
- Possibility to drag and drop rows
<q-grid-row [canMove]="true"
.
- Style queue to the style Api, accessible through style model cells/rows props.
- Rows property to the layout property.
Changed
- Improve performance through change detection strategy.
- Improve performance through reducing number of change detections.
- Improve performance through adding track by index.
- Improve performance through invoking drang and drop out of ng zone.
- Layout columns property changed type form object to map.
5.1.1 - 2017-12-28
Added
- Legend plugin.
- Bool cell editor.
- File cell editor.
- Image cell editor.
Changed
- Theme module should be explicitly added to the user application.
- Backdrop triggers close event on mouse wheel click.
- Change dependencies to peer in prod package.json.
Fixed
- Array cell editor improvements.
- Fix minification in release script.
- Grid in grid support.
[5.0.2] - 2017-12-22
Added
- Theme support.
- Material theme that is used angular material inside.
- Grid service that allows to create grid model and get more control on the grid itself.
- Make grid header and footer sticky.
- Sticky footer.
- Top, left, right, bottom toolbars.
- Embed flex css framework, that was extracted from angular-material.
- Auto generation modes for columns.
- Allow to reorder columns.
- Allow to resize columns.
- Allow to setup width of column in percents.
- Allow to have custom templates for cells in html.
- Column multi-sort support
- Column sort modes: single, multiple
- Column sorting depends on position
- Frozen columns.
- Custom.
- Array column type.
- Bool column type.
- Date column type.
- Email column type.
- Group column type.
- Number column type.
- Pad column type.
- Password column type.
- Pivot column type.
- Row indicator column type.
- Row number column type.
- Select column type.
- File column type.
- Time column type.
- Image column type.
- Url column type.
- Currency column type.
- Row options column type.
- Row expand column type.
- Row details column type.
- Reference column type.
- Id column type.
- Row details.
- Cell inline editing.
- Cell navigation with keyboard.
- Mouse navigation.
- Style API to apply runtime style to the cells and rows.
- Row and cell highlighting.
- Focus cell API.
- Range selection.
- Row selection.
- Cell selection.
- Mix selection, when user can select row by clicking on row-indicator column or cell.
- Selection key that allows to reduce data row to some valuable thing.
- Selection modes: single and multiple.
- Keyboard editing support.
- Edit API.
- Dropdown editor.
- Textarea editor.
- Column filter plugin.
- Initial filter row implementation.
- Filter API for custom filters.
- Column grouping.
- Custom hierarchy for grouping.
- Column pivoting.
- Import/Export to csv, excel and pdf.
- Column aggregation.
- Plugin system.
- Column chooser plugin.
- Pager plugin.
- Progress plugin.


public class MockDirectoryWrapper extends Directory
LuceneTestCase.newDirectory()
are tracked
to ensure they are closed by the test.
| Modifier and Type | Class and Description |
|---|---|
static class
|
MockDirectoryWrapper.Failure
Objects that represent fail-able conditions.
|
static class
|
MockDirectoryWrapper.Throttling
|
isOpen
,
lockFactory
| Constructor and Description |
|---|
MockDirectoryWrapper
(
Random
random,
Directory
delegate)
|
| Modifier and Type | Method and Description |
|---|---|
void
|
clearCrash
()
|
void
|
clearLock
(
String
name)
Attempt to clear (forcefully unlock and remove) the
specified lock.
|
void
|
close
()
Closes the store.
|
void
|
copy
(
Directory
to,
String
src,
String
dest)
Copies the file
src
to
Directory
to
under the new
file name
dest
.
|
void
|
crash
()
Simulates a crash of OS or machine by overwriting
unsynced files.
|
IndexOutput
|
createOutput
(
String
name)
Creates a new, empty file in the directory with the given name.
|
void
|
deleteFile
(
String
name)
Removes an existing file in the directory.
|
void
|
failOn
(
MockDirectoryWrapper.Failure
fail)
add a Failure object to the list of objects to be evaluated
at every potential failure point
|
boolean
|
fileExists
(
String
name)
Returns true iff a file with the given name exists.
|
long
|
fileLength
(
String
name)
Returns the length of a file in the directory.
|
long
|
fileModified
(
String
name)
Returns the time the named file was last modified.
|
boolean
|
getCheckIndexOnClose
()
|
int
|
getInputCloneCount
()
|
LockFactory
|
getLockFactory
()
Get the LockFactory that this Directory instance is
using for its locking implementation.
|
String
|
getLockID
()
Return a string identifier that uniquely differentiates
this Directory instance from other Directory instances.
|
long
|
getMaxSizeInBytes
()
|
long
|
getMaxUsedSizeInBytes
()
Returns the peek actual storage used (bytes) in this
directory.
|
boolean
|
getNoDeleteOpenFile
()
|
Set
<
String
>
|
getOpenDeletedFiles
()
|
double
|
getRandomIOExceptionRate
()
|
long
|
getRecomputedActualSizeInBytes
()
Like getRecomputedSizeInBytes(), but, uses actual file
lengths rather than buffer allocations (which are
quantized up to nearest
RAMOutputStream.BUFFER_SIZE (now 1024) bytes.
|
long
|
getRecomputedSizeInBytes
()
Provided for testing purposes.
|
boolean
|
isOpen
()
|
String
[]
|
listAll
()
Returns an array of strings, one for each file in the directory.
|
Lock
|
makeLock
(
String
name)
Construct a
Lock
.
|
IndexInput
|
openInput
(
String
name)
Returns a stream reading an existing file.
|
void
|
removeIndexInput
(
IndexInput
in,
String
name)
|
void
|
removeIndexOutput
(
IndexOutput
out,
String
name)
|
void
|
resetMaxUsedSizeInBytes
()
|
void
|
setAssertNoUnrefencedFilesOnClose
(boolean v)
|
void
|
setCheckIndexOnClose
(boolean value)
Set whether or not checkindex should be run
on close
|
void
|
setFailOnCreateOutput
(boolean v)
|
void
|
setFailOnOpenInput
(boolean v)
|
void
|
setLockFactory
(
LockFactory
lockFactory)
Set the LockFactory that this Directory instance should
use for its locking implementation.
|
void
|
setMaxSizeInBytes
(long maxSize)
|
void
|
setNoDeleteOpenFile
(boolean value)
Emulate windows whereby deleting an open file is not
allowed (raise IOException).
|
void
|
setPreventDoubleWrite
(boolean value)
If set to true, we throw an IOException if the same
file is opened by createOutput, ever.
|
void
|
setRandomIOExceptionRate
(double rate)
If 0.0, no exceptions will be thrown.
|
void
|
setThrottling
(
MockDirectoryWrapper.Throttling
throttling)
|
void
|
setTrackDiskUsage
(boolean v)
|
long
|
sizeInBytes
()
|
void
|
sync
(
Collection
<
String
> names)
Ensure that any writes to these files are moved to
stable storage.
|
void
|
sync
(
String
name)
Deprecated.
|
String
|
toString
()
|
void
|
touchFile
(
String
name)
Deprecated.
|
copy
,
ensureOpen
,
openInput
public int getInputCloneCount()
public void setTrackDiskUsage(boolean v)
public void setPreventDoubleWrite(boolean value)
@Deprecated public void sync( String name) throws IOException
Directory
sync
in class
Directory
IOException
public void setThrottling( MockDirectoryWrapper.Throttling throttling)
public void sync( Collection < String > names) throws IOException
Directory
sync
in class
Directory
IOException
public final long sizeInBytes() throws IOException
IOException
public void crash() throws IOException
IOException
public void clearCrash() throws IOException
IOException
public void setMaxSizeInBytes(long maxSize)
public long getMaxSizeInBytes()
public long getMaxUsedSizeInBytes()
public void resetMaxUsedSizeInBytes() throws IOException
IOException
public void setNoDeleteOpenFile(boolean value)
public boolean getNoDeleteOpenFile()
public void setCheckIndexOnClose(boolean value)
public boolean getCheckIndexOnClose()
public void setRandomIOExceptionRate(double rate)
public double getRandomIOExceptionRate()
public void deleteFile( String name) throws IOException
Directory
deleteFile
in class
Directory
IOException
public void setFailOnCreateOutput(boolean v)
public IndexOutput createOutput( String name) throws IOException
Directory
createOutput
in class
Directory
IOException
public void setFailOnOpenInput(boolean v)
public IndexInput openInput( String name) throws IOException
Directory
openInput
in class
Directory
IOException
public final long getRecomputedSizeInBytes() throws IOException
IOException
public final long getRecomputedActualSizeInBytes() throws IOException
IOException
public void setAssertNoUnrefencedFilesOnClose(boolean v)
public void close() throws IOException
Directory
close
in interface
Closeable
close
in class
Directory
IOException
public void removeIndexOutput( IndexOutput out, String name)
public void removeIndexInput( IndexInput in, String name)
public boolean isOpen()
public void failOn( MockDirectoryWrapper.Failure fail)
public String [] listAll() throws IOException
Directory
listAll
in class
Directory
NoSuchDirectoryException
- if the directory is not prepared for any
write operations (such as
Directory.createOutput(String)
).
IOException
- in case of other IO errors
public boolean fileExists( String name) throws IOException
Directory
fileExists
in class
Directory
IOException
public long fileModified( String name) throws IOException
Directory
fileModified
in class
Directory
IOException
@Deprecated public void touchFile( String name) throws IOException
Directory
touchFile
in class
Directory
IOException
public long fileLength( String name) throws IOException
Directory
FileNotFoundException
if the file does not exist
fileLength
in class
Directory
name
- the name of the file for which to return the length.
FileNotFoundException
- if the file does not exist.
IOException
- if there was an IO error while retrieving the file's
length.
public Lock makeLock( String name)
Directory
Lock
.
public void clearLock( String name) throws IOException
Directory
clearLock
in class
Directory
name
- name of the lock to be cleared.
IOException
public void setLockFactory( LockFactory lockFactory) throws IOException
Directory
setLockFactory
in class
Directory
lockFactory
- instance of
LockFactory
.
IOException
public LockFactory getLockFactory()
Directory
getLockFactory
in class
Directory
public String getLockID()
Directory
public void copy( Directory to, String src, String dest) throws IOException
Directory
Directory
to
under the new
file name
dest
.
If you want to copy the entire source directory to the destination one, you can do so like this:
Directory to; // the directory to copy to for (String file : dir.listAll()) { dir.copy(to, file, newFile); // newFile can be either file, or a new name }
NOTE: this method does not check whether dest exist and will overwrite it if it does.
copy
in class
Directory
IOException


--- layout: default title: Welcome ---
I am a Data Assimilation Research Scientist at the Center for Western Weather and Water Extremes (CW3E) of the Scripps Institution of Oceanography at the University of California San Diego. This is the home for my professional and creative interests. Please see the links in the menu for details about my research and other activities. See news and announcements below.


asSUCCESS 0 asERROR -1 asCONTEXT_ACTIVE -2 asCONTEXT_NOT_FINISHED -3 asCONTEXT_NOT_PREPARED -4 asINVALID_ARG -5 asNO_FUNCTION -6 asNOT_SUPPORTED -7 asINVALID_NAME -8 asNAME_TAKEN -9 asINVALID_DECLARATION -10 asINVALID_OBJECT -11 asINVALID_TYPE -12 asALREADY_REGISTERED -13 asMULTIPLE_FUNCTIONS -14 asNO_MODULE -15 asNO_GLOBAL_VAR -16 asINVALID_CONFIGURATION -17 asINVALID_INTERFACE -18 asCANT_BIND_ALL_FUNCTIONS -19 asLOWER_ARRAY_DIMENSION_NOT_REGISTERED -20 asWRONG_CONFIG_GROUP -21 asCONFIG_GROUP_IS_IN_USE -22 asILLEGAL_BEHAVIOUR_FOR_TYPE -23
Call finished successfully.
An error occured.
A script context is currently active.
A script context hasn't finished the execution.
The context hasn't been prepared yet and cannot be executed.
One or more arguments are invalid.
No function could be found.
The feature you are trying to use is not yet supported.
The name is invalid.
The name is taken.
The declaration is invalid.
The object is invalid.
The type is invalid.
The function, property, or object is already registered.
Multiple functions were found that matches the search.
No module with the specified name could be found.
No global variable with the specified name could be found.
At least one of the registration methods failed.
The function cannot be bound because the interface is not correct.
Not all of the functions could be bound.
A lower dimension array must be registered first.
This error message is received, for example, when trying to register an object property and the object type was registered in a different configuration group than the current one.
This happens when trying to remove a configuration group that is currently being used. A group is in use, if a script module uses the configuration in the group, or if an object with a type from the group is still alive.
This error means that the behaviour isn't allowed for the object type, i.e. it doesn't match the flags set with RegisterObjectType.


PRE_ROUTE
Prepare. Predict. Pre-route
An AI traffic simulator that predicts the best re-routes
so we can
make better decisions.
An AI traffic simulator that predicts the best re-routes
so we can
make better decisions.


The following table lists various keyboard shortcuts that you can use to perform most common tasks.
On Mac
OS X, the
Ctrl
key needs to be substituted with the
Command
key.
| Shortcut Key | Action Performed |
|---|---|
F1 (Command + ? on Mac OS X) |
Help |
Ctrl + N |
New Session |
F3 |
Connect... |
F4 |
Disconnect |
Ctrl + F3 |
Reconnect |
F7 |
Download |
Ctrl + F7 |
Download As |
Ctrl + Shift + F7 |
Download and Unzip |
F9 |
Upload |
Ctrl + F9 |
Upload As |
Ctrl + Shift + F9 |
Zip and Upload |
F12 |
Aborts the current transfer immediately. |
Ctrl + Shift + O |
Open local file or directory |
Ctrl + Shift + E |
Edit local file |
Ctrl + Shift + P |
Print local file |
Ctrl + Shift + M |
E-mail local file |
Ctrl + Shift + F |
New Local File |
Ctrl + Shift + D |
New Local Directory |
Ctrl + Shift + R |
Rename local file or directory |
Ctrl + Shift + Delete |
Delete local files and/or directories |
Ctrl + Shift + F5 |
Refreshes the contents of local pane. |
Ctrl + Shift + I |
Local file properties |
Ctrl + O |
Open remote file or directory |
Ctrl + E |
Edit remote file |
Ctrl + P |
Print remote file |
Ctrl + M |
E-mail remote file |
Ctrl + F |
New remote file |
Ctrl + D |
New remote directory |
Ctrl + R |
Rename remote directory |
Ctrl + Delete |
Delete remote files and/or directories |
Ctrl + F5 |
Refreshes the contents of the remote pane. |
Ctrl + I |
Remote file properties |


cmake(1)¶
Synopsis¶
Generate a Project Buildsystem cmake [<options>] <path-to-source> cmake [<options>] <path-to-existing-build> cmake [<options>] -S <path-to-source> -B <path-to-build> Build a Project cmake --build <dir> [<options>] [-- <build-tool-options>] Install a Project cmake --install <dir> [<options>] Open a Project cmake --open <dir> Run a Script cmake [{-D <var>=<value>}...] -P <cmake-script-file> Run a Command-Line Tool cmake -E <command> [<options>] Run the Find-Package Tool cmake --find-package [<options>] View Help cmake --help[-<topic>]
Description¶
The cmake executable is the command-line interface of the cross-platform buildsystem generator CMake. The above Synopsis lists various actions the tool can perform as described in sections below.
To build a software project with CMake, Generate a Project Buildsystem.
Optionally use cmake to Build a Project, Install a Project or just
run the corresponding build tool (e.g. make
) directly. cmake can also
be used to View Help.
The other actions are meant for use by software developers writing
scripts in the CMake language
to support
their builds.
For graphical user interfaces that may be used in place of cmake,
see ccmake
and cmake-gui
.
For command-line interfaces to the CMake testing and packaging facilities,
see ctest
and cpack
.
For more information on CMake at large, see also the links at the end of this manual.
Introduction to CMake Buildsystems¶
A buildsystem describes how to build a project’s executables and libraries
from its source code using a build tool to automate the process. For
example, a buildsystem may be a Makefile
for use with a command-line
make
tool or a project file for an Integrated Development Environment
(IDE). In order to avoid maintaining multiple such buildsystems, a project
may specify its buildsystem abstractly using files written in the
CMake language
. From these files CMake
generates a preferred buildsystem locally for each user through a backend
called a generator.
To generate a buildsystem with CMake, the following must be selected:
- Source Tree
- The top-level directory containing source files provided by the project.
The project specifies its buildsystem using files as described in the
cmake-language(7)
manual, starting with a top-level file namedCMakeLists.txt
. These files specify build targets and their dependencies as described in thecmake-buildsystem(7)
manual. - Build Tree
The top-level directory in which buildsystem files and build output artifacts (e.g. executables and libraries) are to be stored. CMake will write a
CMakeCache.txt
file to identify the directory as a build tree and store persistent information such as buildsystem configuration options.To maintain a pristine source tree, perform an out-of-source build by using a separate dedicated build tree. An in-source build in which the build tree is placed in the same directory as the source tree is also supported, but discouraged.
- Generator
This chooses the kind of buildsystem to generate. See the
cmake-generators(7)
manual for documentation of all generators. Runcmake --help
to see a list of generators available locally. Optionally use the-G
option below to specify a generator, or simply accept the default CMake chooses for the current platform.When using one of the Command-Line Build Tool Generators CMake expects that the environment needed by the compiler toolchain is already configured in the shell. When using one of the IDE Build Tool Generators, no particular environment is needed.
Generate a Project Buildsystem¶
Run CMake with one of the following command signatures to specify the source and build trees and generate a buildsystem:
cmake [<options>] <path-to-source>
Uses the current working directory as the build tree, and
<path-to-source>
as the source tree. The specified path may be absolute or relative to the current working directory. The source tree must contain aCMakeLists.txt
file and must not contain aCMakeCache.txt
file because the latter identifies an existing build tree. For example:$ mkdir build ; cd build $ cmake ../src
cmake [<options>] <path-to-existing-build>
Uses
<path-to-existing-build>
as the build tree, and loads the path to the source tree from itsCMakeCache.txt
file, which must have already been generated by a previous run of CMake. The specified path may be absolute or relative to the current working directory. For example:$ cd build $ cmake .
cmake [<options>] -S <path-to-source> -B <path-to-build>
Uses
<path-to-build>
as the build tree and<path-to-source>
as the source tree. The specified paths may be absolute or relative to the current working directory. The source tree must contain aCMakeLists.txt
file. The build tree will be created automatically if it does not already exist. For example:$ cmake -S src -B build
In all cases the <options>
may be zero or more of the Options below.
After generating a buildsystem one may use the corresponding native
build tool to build the project. For example, after using the
Unix Makefiles
generator one may run make
directly:
$ make $ make install
Alternatively, one may use cmake to Build a Project by automatically choosing and invoking the appropriate native build tool.
Options¶
-S <path-to-source>
- Path to root directory of the CMake project to build.
-B <path-to-build>
Path to directory which CMake will use as the root of build directory.
If the directory doesn’t already exist CMake will make it.
-C <initial-cache>
Pre-load a script to populate the cache.
When CMake is first run in an empty build tree, it creates a
CMakeCache.txt
file and populates it with customizable settings for the project. This option may be used to specify a file from which to load cache entries before the first pass through the project’s CMake listfiles. The loaded entries take priority over the project’s default values. The given file should be a CMake script containingset()
commands that use theCACHE
option, not a cache-format file.-D <var>:<type>=<value>, -D <var>=<value>
Create or update a CMake
CACHE
entry.When CMake is first run in an empty build tree, it creates a
CMakeCache.txt
file and populates it with customizable settings for the project. This option may be used to specify a setting that takes priority over the project’s default value. The option may be repeated for as manyCACHE
entries as desired.If the
:<type>
portion is given it must be one of the types specified by theset()
command documentation for itsCACHE
signature. If the:<type>
portion is omitted the entry will be created with no type if it does not exist with a type already. If a command in the project sets the type toPATH
orFILEPATH
then the<value>
will be converted to an absolute path.This option may also be given as a single argument:
-D<var>:<type>=<value>
or-D<var>=<value>
.-U <globbing_expr>
Remove matching entries from CMake
CACHE
.This option may be used to remove one or more variables from the
CMakeCache.txt
file, globbing expressions using*
and?
are supported. The option may be repeated for as manyCACHE
entries as desired.Use with care, you can make your
CMakeCache.txt
non-working.-G <generator-name>
Specify a build system generator.
CMake may support multiple native build systems on certain platforms. A generator is responsible for generating a particular build system. Possible generator names are specified in the
cmake-generators(7)
manual.If not specified, CMake checks the
CMAKE_GENERATOR
environment variable and otherwise falls back to a builtin default selection.-T <toolset-spec>
Toolset specification for the generator, if supported.
Some CMake generators support a toolset specification to tell the native build system how to choose a compiler. See the
CMAKE_GENERATOR_TOOLSET
variable for details.-A <platform-name>
Specify platform name if supported by generator.
Some CMake generators support a platform name to be given to the native build system to choose a compiler or SDK. See the
CMAKE_GENERATOR_PLATFORM
variable for details.-Wno-dev
Suppress developer warnings.
Suppress warnings that are meant for the author of the
CMakeLists.txt
files. By default this will also turn off deprecation warnings.-Wdev
Enable developer warnings.
Enable warnings that are meant for the author of the
CMakeLists.txt
files. By default this will also turn on deprecation warnings.-Werror=dev
Make developer warnings errors.
Make warnings that are meant for the author of the
CMakeLists.txt
files errors. By default this will also turn on deprecated warnings as errors.-Wno-error=dev
Make developer warnings not errors.
Make warnings that are meant for the author of the
CMakeLists.txt
files not errors. By default this will also turn off deprecated warnings as errors.-Wdeprecated
Enable deprecated functionality warnings.
Enable warnings for usage of deprecated functionality, that are meant for the author of the
CMakeLists.txt
files.-Wno-deprecated
Suppress deprecated functionality warnings.
Suppress warnings for usage of deprecated functionality, that are meant for the author of the
CMakeLists.txt
files.-Werror=deprecated
Make deprecated macro and function warnings errors.
Make warnings for usage of deprecated macros and functions, that are meant for the author of the
CMakeLists.txt
files, errors.-Wno-error=deprecated
Make deprecated macro and function warnings not errors.
Make warnings for usage of deprecated macros and functions, that are meant for the author of the
CMakeLists.txt
files, not errors.-L[A][H]
List non-advanced cached variables.
List
CACHE
variables will run CMake and list all the variables from the CMakeCACHE
that are not marked asINTERNAL
orADVANCED
. This will effectively display current CMake settings, which can then be changed with-D
option. Changing some of the variables may result in more variables being created. IfA
is specified, then it will display also advanced variables. IfH
is specified, it will also display help for each variable.-N
View mode only.
Only load the cache. Do not actually run configure and generate steps.
--graphviz=[file]
Generate graphviz of dependencies, see
CMakeGraphVizOptions
for more.Generate a graphviz input file that will contain all the library and executable dependencies in the project. See the documentation for
CMakeGraphVizOptions
for more details.--system-information [file]
Dump information about this system.
Dump a wide range of information about the current system. If run from the top of a binary tree for a CMake project it will dump additional information such as the cache, log files etc.
--loglevel=<ERROR|WARNING|NOTICE|STATUS|VERBOSE|DEBUG|TRACE>
Set the log level.
The
message()
command will only output messages of the specified log level or higher. The default log level isSTATUS
.--debug-trycompile
Do not delete the
try_compile()
build tree. Only useful on onetry_compile()
at a time.Do not delete the files and directories created for
try_compile()
calls. This is useful in debugging failed try_compiles. It may however change the results of the try-compiles as old junk from a previous try-compile may cause a different test to either pass or fail incorrectly. This option is best used for one try-compile at a time, and only when debugging.--debug-output
Put cmake in a debug mode.
Print extra information during the cmake run like stack traces with
message(SEND_ERROR)
calls.--trace
Put cmake in trace mode.
Print a trace of all calls made and from where.
--trace-expand
Put cmake in trace mode.
Like
--trace
, but with variables expanded.--trace-source=<file>
Put cmake in trace mode, but output only lines of a specified file.
Multiple options are allowed.
--warn-uninitialized
Warn about uninitialized values.
Print a warning when an uninitialized variable is used.
--warn-unused-vars
Warn about unused variables.
Find variables that are declared or set, but not used.
--no-warn-unused-cli
Don’t warn about command line options.
Don’t find variables that are declared on the command line, but not used.
--check-system-vars
Find problems with variable usage in system files.
Normally, unused and uninitialized variables are searched for only in
CMAKE_SOURCE_DIR
andCMAKE_BINARY_DIR
. This flag tells CMake to warn about other files as well.
Build a Project¶
CMake provides a command-line signature to build an already-generated project binary tree:
cmake --build <dir> [<options>] [-- <build-tool-options>]
This abstracts a native build tool’s command-line interface with the following options:
--build <dir>
- Project binary directory to be built. This is required and must be first.
--parallel [<jobs>], -j [<jobs>]
The maximum number of concurrent processes to use when building. If
<jobs>
is omitted the native build tool’s default number is used.The
CMAKE_BUILD_PARALLEL_LEVEL
environment variable, if set, specifies a default parallel level when this option is not given.Some native build tools always build in parallel. The use of
<jobs>
value of1
can be used to limit to a single job.--target <tgt>..., -t <tgt>...
- Build
<tgt>
instead of the default target. Multiple targets may be given, separated by spaces. --config <cfg>
- For multi-configuration tools, choose configuration
<cfg>
. --clean-first
- Build target
clean
first, then build. (To clean only, use--target clean
.) --use-stderr
- Ignored. Behavior is default in CMake >= 3.0.
--verbose, -v
Enable verbose output - if supported - including the build commands to be executed.
This option can be omitted if
VERBOSE
environment variable orCMAKE_VERBOSE_MAKEFILE
cached variable is set.--
- Pass remaining options to the native tool.
Run cmake --build
with no options for quick help.
Install a Project¶
CMake provides a command-line signature to install an already-generated project binary tree:
cmake --install <dir> [<options>]
This may be used after building a project to run installation without using the generated build system or the native build tool. The options are:
--install <dir>
- Project binary directory to install. This is required and must be first.
--config <cfg>
- For multi-configuration generators, choose configuration
<cfg>
. --component <comp>
- Component-based install. Only install component
<comp>
. --prefix <prefix>
- Override the installation prefix,
CMAKE_INSTALL_PREFIX
. --strip
- Strip before installing.
-v, --verbose
Enable verbose output.
This option can be omitted if
VERBOSE
environment variable is set.
Run cmake --install
with no options for quick help.
Open a Project¶
cmake --open <dir>
Open the generated project in the associated application. This is only supported by some generators.
Run a Script¶
cmake [{-D <var>=<value>}...] -P <cmake-script-file>
Process the given cmake file as a script written in the CMake
language. No configure or generate step is performed and the cache
is not modified. If variables are defined using -D
, this must be
done before the -P
argument.
Run a Command-Line Tool¶
CMake provides builtin command-line tools through the signature
cmake -E <command> [<options>]
Run cmake -E
or cmake -E help
for a summary of commands.
Available commands are:
capabilities
Report cmake capabilities in JSON format. The output is a JSON object with the following keys:
version
A JSON object with version information. Keys are:
string
- The full version string as displayed by cmake
--version
. major
- The major version number in integer form.
minor
- The minor version number in integer form.
patch
- The patch level in integer form.
suffix
- The cmake version suffix string.
isDirty
- A bool that is set if the cmake build is from a dirty tree.
generators
A list available generators. Each generator is a JSON object with the following keys:
name
- A string containing the name of the generator.
toolsetSupport
true
if the generator supports toolsets andfalse
otherwise.platformSupport
true
if the generator supports platforms andfalse
otherwise.extraGenerators
- A list of strings with all the extra generators compatible with the generator.
fileApi
Optional member that is present when the
cmake-file-api(7)
is available. The value is a JSON object with one member:requests
A JSON array containing zero or more supported file-api requests. Each request is a JSON object with members:
kind
- Specifies one of the supported Object Kinds.
version
- A JSON array whose elements are each a JSON object containing
major
andminor
members specifying non-negative integer version components.
serverMode
true
if cmake supports server-mode andfalse
otherwise.
chdir <dir> <cmd> [<arg>...]
- Change the current working directory and run a command.
compare_files [--ignore-eol] <file1> <file2>
- Check if
<file1>
is same as<file2>
. If files are the same, then returns0
, if not it returns1
. The--ignore-eol
option implies line-wise comparison and ignores LF/CRLF differences. copy <file>... <destination>
- Copy files to
<destination>
(either file or directory). If multiple files are specified, the<destination>
must be directory and it must exist. Wildcards are not supported.copy
does follow symlinks. That means it does not copy symlinks, but the files or directories it point to. copy_directory <dir>... <destination>
- Copy directories to
<destination>
directory. If<destination>
directory does not exist it will be created.copy_directory
does follow symlinks. copy_if_different <file>... <destination>
- Copy files to
<destination>
(either file or directory) if they have changed. If multiple files are specified, the<destination>
must be directory and it must exist.copy_if_different
does follow symlinks. echo [<string>...]
- Displays arguments as text.
echo_append [<string>...]
- Displays arguments as text but no new line.
env [--unset=NAME]... [NAME=VALUE]... COMMAND [ARG]...
- Run command in a modified environment.
environment
- Display the current environment variables.
make_directory <dir>...
- Create
<dir>
directories. If necessary, create parent directories too. If a directory already exists it will be silently ignored. md5sum <file>...
Create MD5 checksum of files in
md5sum
compatible format:351abe79cd3800b38cdfb25d45015a15 file1.txt 052f86c15bbde68af55c7f7b340ab639 file2.txt
sha1sum <file>...
Create SHA1 checksum of files in
sha1sum
compatible format:4bb7932a29e6f73c97bb9272f2bdc393122f86e0 file1.txt 1df4c8f318665f9a5f2ed38f55adadb7ef9f559c file2.txt
sha224sum <file>...
Create SHA224 checksum of files in
sha224sum
compatible format:b9b9346bc8437bbda630b0b7ddfc5ea9ca157546dbbf4c613192f930 file1.txt 6dfbe55f4d2edc5fe5c9197bca51ceaaf824e48eba0cc453088aee24 file2.txt
sha256sum <file>...
Create SHA256 checksum of files in
sha256sum
compatible format:76713b23615d31680afeb0e9efe94d47d3d4229191198bb46d7485f9cb191acc file1.txt 15b682ead6c12dedb1baf91231e1e89cfc7974b3787c1e2e01b986bffadae0ea file2.txt
sha384sum <file>...
Create SHA384 checksum of files in
sha384sum
compatible format:acc049fedc091a22f5f2ce39a43b9057fd93c910e9afd76a6411a28a8f2b8a12c73d7129e292f94fc0329c309df49434 file1.txt 668ddeb108710d271ee21c0f3acbd6a7517e2b78f9181c6a2ff3b8943af92b0195dcb7cce48aa3e17893173c0a39e23d file2.txt
sha512sum <file>...
Create SHA512 checksum of files in
sha512sum
compatible format:2a78d7a6c5328cfb1467c63beac8ff21794213901eaadafd48e7800289afbc08e5fb3e86aa31116c945ee3d7bf2a6194489ec6101051083d1108defc8e1dba89 file1.txt 7a0b54896fe5e70cca6dd643ad6f672614b189bf26f8153061c4d219474b05dad08c4e729af9f4b009f1a1a280cb625454bf587c690f4617c27e3aebdf3b7a2d file2.txt
remove [-f] <file>...
- Remove the file(s). If any of the listed files already do not
exist, the command returns a non-zero exit code, but no message
is logged. The
-f
option changes the behavior to return a zero exit code (i.e. success) in such situations instead.remove
does not follow symlinks. That means it remove only symlinks and not files it point to. remove_directory <dir>...
- Remove
<dir>
directories and their contents. If a directory does not exist it will be silently ignored. rename <oldname> <newname>
- Rename a file or directory (on one volume). If file with the
<newname>
name already exists, then it will be silently replaced. server
- Launch
cmake-server(7)
mode. sleep <number>...
- Sleep for given number of seconds.
tar [cxt][vf][zjJ] file.tar [<options>] [--] [<pathname>...]
Create or extract a tar or zip archive. Options are:
c
- Create a new archive containing the specified files.
If used, the
<pathname>...
argument is mandatory. x
- Extract to disk from the archive.
The
<pathname>...
argument could be used to extract only selected files or directories. When extracting selected files or directories, you must provide their exact names including the path, as printed by list (-t
). t
- List archive contents.
The
<pathname>...
argument could be used to list only selected files or directories. v
- Produce verbose output.
z
- Compress the resulting archive with gzip.
j
- Compress the resulting archive with bzip2.
J
- Compress the resulting archive with XZ.
--zstd
- Compress the resulting archive with Zstandard.
--files-from=<file>
- Read file names from the given file, one per line.
Blank lines are ignored. Lines may not start in
-
except for--add-file=<name>
to add files whose names start in-
. --format=<format>
- Specify the format of the archive to be created.
Supported formats are:
7zip
,gnutar
,pax
,paxr
(restricted pax, default), andzip
. --mtime=<date>
- Specify modification time recorded in tarball entries.
--
- Stop interpreting options and treat all remaining arguments
as file names, even if they start with
-
.
time <command> [<args>...]
- Run command and display elapsed time.
touch <file>...
- Creates
<file>
if file do not exist. If<file>
exists, it is changing<file>
access and modification times. touch_nocreate <file>...
- Touch a file if it exists but do not create it. If a file does not exist it will be silently ignored.
create_symlink <old> <new>
- Create a symbolic link
<new>
naming<old>
.
Note
Path to where <new>
symbolic link will be created has to exist beforehand.
Windows-specific Command-Line Tools¶
The following cmake -E
commands are available only on Windows:
delete_regv <key>
- Delete Windows registry value.
env_vs8_wince <sdkname>
- Displays a batch file which sets the environment for the provided Windows CE SDK installed in VS2005.
env_vs9_wince <sdkname>
- Displays a batch file which sets the environment for the provided Windows CE SDK installed in VS2008.
write_regv <key> <value>
- Write Windows registry value.
Run the Find-Package Tool¶
CMake provides a pkg-config like helper for Makefile-based projects:
cmake --find-package [<options>]
It searches a package using find_package()
and prints the
resulting flags to stdout. This can be used instead of pkg-config
to find installed libraries in plain Makefile-based projects or in
autoconf-based projects (via share/aclocal/cmake.m4
).
Note
This mode is not well-supported due to some technical limitations. It is kept for compatibility but should not be used in new projects.
View Help¶
To print selected pages from the CMake documentation, use
cmake --help[-<topic>]
with one of the following options:
--help,-help,-usage,-h,-H,/?
Print usage information and exit.
Usage describes the basic command line interface and its options.
--version,-version,/V [<f>]
Show program name/version banner and exit.
If a file is specified, the version is written into it. The help is printed to a named <f>ile if given.
--help-full [<f>]
Print all help manuals and exit.
All manuals are printed in a human-readable text format. The help is printed to a named <f>ile if given.
--help-manual <man> [<f>]
Print one help manual and exit.
The specified manual is printed in a human-readable text format. The help is printed to a named <f>ile if given.
--help-manual-list [<f>]
List help manuals available and exit.
The list contains all manuals for which help may be obtained by using the
--help-manual
option followed by a manual name. The help is printed to a named <f>ile if given.--help-command <cmd> [<f>]
Print help for one command and exit.
The
cmake-commands(7)
manual entry for<cmd>
is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-command-list [<f>]
List commands with help available and exit.
The list contains all commands for which help may be obtained by using the
--help-command
option followed by a command name. The help is printed to a named <f>ile if given.--help-commands [<f>]
Print cmake-commands manual and exit.
The
cmake-commands(7)
manual is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-module <mod> [<f>]
Print help for one module and exit.
The
cmake-modules(7)
manual entry for<mod>
is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-module-list [<f>]
List modules with help available and exit.
The list contains all modules for which help may be obtained by using the
--help-module
option followed by a module name. The help is printed to a named <f>ile if given.--help-modules [<f>]
Print cmake-modules manual and exit.
The
cmake-modules(7)
manual is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-policy <cmp> [<f>]
Print help for one policy and exit.
The
cmake-policies(7)
manual entry for<cmp>
is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-policy-list [<f>]
List policies with help available and exit.
The list contains all policies for which help may be obtained by using the
--help-policy
option followed by a policy name. The help is printed to a named <f>ile if given.--help-policies [<f>]
Print cmake-policies manual and exit.
The
cmake-policies(7)
manual is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-property <prop> [<f>]
Print help for one property and exit.
The
cmake-properties(7)
manual entries for<prop>
are printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-property-list [<f>]
List properties with help available and exit.
The list contains all properties for which help may be obtained by using the
--help-property
option followed by a property name. The help is printed to a named <f>ile if given.--help-properties [<f>]
Print cmake-properties manual and exit.
The
cmake-properties(7)
manual is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-variable <var> [<f>]
Print help for one variable and exit.
The
cmake-variables(7)
manual entry for<var>
is printed in a human-readable text format. The help is printed to a named <f>ile if given.--help-variable-list [<f>]
List variables with help available and exit.
The list contains all variables for which help may be obtained by using the
--help-variable
option followed by a variable name. The help is printed to a named <f>ile if given.--help-variables [<f>]
Print cmake-variables manual and exit.
The
cmake-variables(7)
manual is printed in a human-readable text format. The help is printed to a named <f>ile if given.
See Also¶
The following resources are available to get help using CMake:
- Home Page
-
The primary starting point for learning about CMake.
- Online Documentation and Community Resources
https://cmake.org/documentation
Links to available documentation and community resources may be found on this web page.
- Mailing List
https://cmake.org/mailing-lists
For help and discussion about using CMake, a mailing list is provided at<EMAIL_ADDRESS>The list is member-post-only but one may sign up on the CMake web page. Please first read the full documentation at https://cmake.org before posting questions to the list.


List of all members.
Public Member Functions |
|
| xajaxResponseManager () |
|
& | getInstance () |
|
| configure ($sName, $mValue) |
|
| clear () |
|
| append ($mResponse) |
|
| debug ($sMessage) |
|
| send () |
|
| getCharacterEncoding () |
|
| getOutputEntities () |
Public Attributes |
|
| $objResponse |
|
| $sCharacterEncoding |
|
| $bOutputEntities |
|
| $aDebugMessages |
Detailed Description
Definition at line 29 of file xajaxResponseManager.inc.php.
The documentation for this class was generated from the following file:


title = "Contact" url = "/contact" layout = "octaskin" is_hidden = 0 [genericForm contactForm] group = "Contact Form" messages_success = "Your contact request was received. Thank you for contacting!" messages_errors = "There were errors with your submission" reset_form = 1 inline_errors = "disabled" js_on_success = "$.oc.flashMsg({ 'text': 'Your contact request was received!', 'class': 'success', });" sanitize_data = "disabled" anonymize_ip = "disabled" recaptcha_theme = "light" recaptcha_type = "image" recaptcha_size = "normal" [genericForm subscribeNewsletter] messages_success = "Your form was successfully submitted" messages_errors = "There were errors with your submission" inline_errors = "disabled" sanitize_data = "disabled" anonymize_ip = "disabled" recaptcha_theme = "light" recaptcha_type = "image" recaptcha_size = "normal" == {% partial "pages-contact/header" %} {% partial "pages-contact/mainpage" %} {% component 'contactForm'%}


The popHealth web application should be configured to use HTTPS rather than HTTP. Using HTTP to access popHealth could allow responses from the popHealth web application to be intercepted and viewed. HTTPS connections should be used to load webpages containing sensitive data such as personal health information (PHI). You should configure your popHealth server to be served via HTTPS. If you are running popHealth on Apache and Phusion Passenger, you can use the following steps to configure HTTPS. See http://httpd.apache.org/docs/2.0/ssl/
If this is a test instance of popHealth with no PHI, you can override this warning by setting the value force_unsecure_communications to true in popHealth/config/pophealth.yml and restart popHealth.


View recent calibrations, re-print your certificates, and manage your fleet with just a couple of clicks.
With 1 click you can add your customers to your account and let them see all their own vehicle data.
We use advanced encryption algorithms to ensure your data is always safe and secure.
That's not just skin deep
Print a plaque in less than 5 seconds
Every calibration just a click away
Can automatically read and display driver card data
Can generate detailed PDF reports of your recent and upcoming calibrations
Webcal is highly flexible and can be pre-populated with vehicles, inspectors, tyre sizes, and lots more
Customer services
Mon - Friday 8.30 - 5pm
Technical support 24/7
Tel: 01925 880081


Explore millions of specimens and objects from the Australian Museum natural science & cultural collections.
Image title
eg. Australian frogs
eg. Date collected, Date donated
eg. New South Wales
eg. E039560-002
eg. Natural Science or Cultural Collection
Restrict to items with images


Module : nats
Module overview
This module provides the capability to connect with NATS and NATS Streaming servers and performs the following functionality.
- Point to point communication (Queues)
- Pub/Sub (Topics)
- Request/Reply
Basic Usage
Setting up the connection
First step is setting up the connection with the NATS Basic/Streaming server. The following ways can be used to connect to a NATS Basic/Streaming server.
- Connect to a server using the URL
nats:Connection connection = new("nats://localhost:4222");
- Connect to one or more servers with a custom configuration
nats:Connection connection = new("nats://serverone:4222, nats://servertwo:4222", config);
Publishing messages
Publishing messages is handled differently in the NATS Basic server and Streaming server. The 'ballerina/nats' module provides different APIs to publish messages to each server.
Publishing messages to the NATS basic server
Once connected, publishing is accomplished via one of the below two methods.
- Publish with the subject and the message content.
nats:Producer producer = new(connection);
nats:Error? result = producer->publish(subject, "hello world");
- Publish as a request that expects a reply.
nats:Producer producer = new(connection);
nats:Message|nats:Error reqReply = producer->request(subject, "hello world", 5000);
- Publish messages with a replyTo subject
nats:Producer producer = new(connection);
nats:Error? result = producer->publish(subject, <@untainted>message,
replyToSubject);
- Publish messages with a replyTo callback service
nats:Producer producer = new(connection);
nats:Error? result = producer->publish(subject, <@untainted>message,
replyToService);
service replyToService =
@nats:SubscriptionConfig {
subject: "replySubject"
}
service {
resource function onMessage(nats:Message msg, string data) {
// Prints the incoming message in the console.
log:printInfo("Received reply message : " + data);
}
resource function onError(nats:Message msg, nats:Error err) {
log:printError("Error occurred in data binding", err);
}
};
Publishing messages to a NATS streaming server
Once connected to a streaming server, publishing messages is accomplished using the following method.
nats:StreamingProducer producer = new(connection);
string|error result = producer->publish(subject, "hello world");
if (result is error) {
io:println("Error occurred while publishing the message.");
} else {
io:println("GUID "+result+" received for the produced message.");
}
Publish api supports the
byte[], boolean, string, int, float, decimal, xml, json, record {}
message types.
Listening to incoming messages
The Ballerina NATS module provides the following mechanisms to listen to messages. Similar to message publishing, listening to messages is also handled differently in NATS basic and streaming servers.
Listening to messages from a NATS server
import ballerina/io;
import ballerina/nats;
// Initializes the NATS listener.
listener nats:Listener subscription = new(connection);
// Binds the consumer to listen to the messages published to the 'demo' subject.
@nats:SubscriptionConfig {
subject: "demo"
}
service demo on subscription {
resource function onMessage(nats:Message msg, string data) {
// Prints the incoming message in the console.
io:println("Subject : " + msg.getSubject());
io:println("Message content : " + data));
}
resource function onError(nats:Message msg, nats:Error err) {
io:println(err);
}
}
Listening to messages from a Streaming server
import ballerina/io;
import ballerina/nats;
// Initializes the NATS Streaming listener.
listener nats:StreamingListener subscription = new(conn, "test-cluster", "c1");
// Binds the consumer to listen to the messages published to the 'demo' subject.
@nats:StreamingSubscriptionConfig {
subject: "demo"
}
service demo on subscription {
resource function onMessage(nats:StreamingMessage msg, string data) {
// Prints the incoming message in the console.
io:println("Subject : " + msg.getSubject());
io:println("Message content : " + data));
}
resource function onError(nats:StreamingMessage msg, nats:Error err) {
io:println(err);
}
}
Advanced Usage
Using the TLS protocol
The Ballerina NATS module allows the use of the tls:// protocol in its URLs. This setting expects a secure socket to be set in the connection configuration as shown below.
nats:ConnectionConfig config = {
secureSocket : {
trustStore : {
path: "nats-basic/keyStore.p12",
password: "xxxxx"
}
}
};
// Initializes a connection.
nats:Connection connection = new("tls://localhost:4222", config = config);
Note: The default thread pool size used in Ballerina is number of processors available * 2. You can configure the thread pool size by using the
BALLERINA_MAX_POOL_SIZE
environment variable.
| ConnectionConfig | The parameters used to create a NATS streaming subscription. |
| Detail | Record type to hold the details of an error. |
| PendingLimits | Parameters to set limits on the maximum number of messages, or maximum size of messages this consumer will hold before it starts to drop new messages waiting for the resource functions to drain the queue. Setting a value to anything less than or equal to 0 will disable this check. |
| SecureSocket | Provides configurations for facilitating secure communication with a remote HTTP endpoint. |
| StreamingConfig | Configuration related to establishing a streaming connection. |
| StreamingSubscriptionConfigData | The parameters used to create a NATS streaming subscription. |
| SubscriptionConfigData | NATS basic subscription parameters. |
| Connection | Represents a single network connection to the NATS server. |
| Message | Represents a message, which will be pushed from the NATS server to the consumer. |
| Producer | NATS |
| StreamingMessage | Represents the message a NATS Streaming Server sends to a subscription service. |
| StreamingProducer | NATS |
| Listener | Represents a connection which will be used for subscription. |
| StreamingListener | Represents the NATS Streaming Server connection, to which a subscription service should be bound to in order to receive messages of the corresponding subscription. |
| NATS_ERROR | |
| NEW_ONLY | |
| LAST_RECEIVED | |
| FIRST | |
| TIME_DELTA_START | |
| SEQUENCE_NUMBER |
| StreamingSubscriptionConfig | Streaming subscription configuration annotation. |
| SubscriptionConfig | Basic Subscription config annotation. |
| Content | |
| StartPosition | The position to start receiving messages. NEW_ONLY - Specifies that message delivery should start with the messages, which are published after the subscription is created. LAST_RECEIVED - Specifies that message delivery should start with the last (most recent) message stored for this subject. TimeDeltaStart - Specifies that message delivery should start with a given historical time delta (from now). SequenceNumber - Specifies that message delivery should start at the given sequence number. FIRST - Specifies that message delivery should begin at the oldest available message for this subject. |
| Error |


-
Sandy
CTO of Lukbuk
-
Srinu Basava
Designer
-
Rahul Dravid
Favourite Cricketer
-
Prem Pillai
Senior Developer
-
Arjun URS
ROR Developer
Mr. Srinu Basava
CTO of Lukbuk
Designer
Favourite Cricketer
Senior Developer
ROR Developer
Animated Chart
Tight pants next level keffiyeh you probably haven't heard of fixie sustainable quinoa 8-bit american apparel have a terry richardson vinyl chambray. Beard stumptown, cardigans banh mi lomo thundercats. whatever keytar , scenester farm-to-table banksy Austin twitter handle freegan cred raw denim single-origin coffee viral.
Top Right Bottom LeftTight pants next level keffiyeh you probably haven't heard of fixie sustainable quinoa 8-bit american apparel have a terry richardson vinyl chambray. Beard stumptown, cardigans banh mi lomo thundercats. whatever keytar , scenester farm-to-table banksy Austin twitter handle freegan cred raw denim single-origin coffee viral.
Methodologies eyeballs incentivize models. Platforms web-enabled cultivate dynamic synergies: technologies content
Methodologies eyeballs incentivize models. Platforms web-enabled cultivate dynamic synergies: technologies content deploy ROI communities
Methodologies eyeballs incentivize models. Platforms web-enabled cultivate dynamic synergies: technologies deploy communities methodologies sticky
Eyeballs incentivize models. Platforms web-enabled cultivate dynamic synergies: technologies content deploy ROI communities methodologies sticky
One fine body…


Terraform with Remote S3 and Locking state
Ok …. so you …. you need to build infrastructure for your team. This is a job for terraform. Whenever you execute your plans in terraform a “state” file gets created called terraform.tfstate, this generally is created in the .terraform directory and contains information about the infrastructure and configuration that terraform is managing. It is generally accepted that when multiple people work on the same project it’s better to store this state file remotely so that more members of the team can access it to make changes to the infrastructure, I would dare to add even if you use multiple computers this is a wise thing to do.
The state file contains information about what real resources exist for each object defined in the terraform config files. For example, if you have a DNS zone resource created in your terraform config, then the state file contains info about the actual resource that was created on AWS.
Here is an example of creating a DNS zone with Terraform:
resource "aws_route53_zone" "example_dns_zone" {
name = "domain.com"
}
And this is how a state file looks like:
"aws_route53_zone.example_dns_zone": {
"type": "aws_route53_zone",
"primary": {
"id": "Z2D2ARTZHH4NUA",
"attributes": {
"name": "domain.com"
}
}
},
Store State Remotely in S3
If you are working on a team, then its best to store the terraform state file remotely so that many people can access it. In order to setup terraform to store state remotely you need two things: an s3 bucket to store the state file in and an terraform s3 backend resource.
You can create an s3 bucket in a terraform config like so:
provider "aws" {
region = "us-west-2"
}
resource "aws_s3_bucket" "terraform-state-storage-s3" {
bucket = "terraform-remote-state-storage-s3"
versioning {
enabled = true
}
lifecycle {
prevent_destroy = true
}
tags {
Name = "S3 Remote Terraform State Store"
}
}
Then create the s3 backend resource like so:
terraform {
backend “s3” {
encrypt = true
bucket = "terraform-remote-state-storage-s3"
region = us-west-2
key = path/to/state/file
}
}
What is locking and why do we need it?
If the state file is stored remotely so that many people can access it, then you risk multiple people attempting to make changes to the same file at the exact same time. So we need to provide a mechanism that will “lock” the state if its currently in-use by another user. We can accomplish this by creating a dynamoDB table for terraform to use.
Create the dynamoDB table like this:
resource "aws_dynamodb_table" "dynamodb-terraform-state-lock" {
name = "terraform-state-lock-dynamo"
hash_key = "LockID"
read_capacity = 20
write_capacity = 20
attribute {
name = "LockID"
type = "S"
}
tags {
Name = "DynamoDB Terraform State Lock Table"
}
}
You will need to modify the Terraform S3 backend resource and add in the dynamoDB table:
terraform {
backend “s3” {
encrypt = true
bucket = "terraform-remote-state-storage-s3"
dynamodb_table = "terraform-state-lock-dynamo"
region = us-west-2
key = path/to/state/file
}
}
Once you’ve created the S3 bucket and dynamoDB table, along with the backend S3 resource referencing those, then you can run your terraform configs like normal with terraform plan and terraform apply commands and the state file will show up in the s3 bucket. After those commands, if you inspect .terraform/terraform.tfstate, you will see that it contains the location of the state file now instead of the actual state file.
cat .terraform/terraform.tfstate
{
"version": 3,
"backend": {
"type": "s3",
"config": {
"bucket": "terraform-remote-state-storage-s3",
"dynamodb_table": "terraform-state-lock-dynamo",
"encrypt": true,
"key": "example/terraform.tfstate",
"region": "us-west-2"
}
}
}


- What can you do with it?
Generate random sequence of numbers and use them as IDs for your React app or any other app
IDs generated are never the same- no duplicates
- How do i use it?
Simply call the randID()
function anywhere in your code where you need to supply IDs
The function takes an optional parameter, randID(x)
- where x
is the length of the output of your ID depending on your need
If a parameter is not supplied, it uses its default output length [10]
, you can however modify this value in the source code
- What else?
The parameter passed must be greater than 1 and must be an integer
, otherwise nothing will be returned and an error will be logged in the console telling you what happened


//Click button to calculate sum, multiply, modulus within one function only. Alert one after the other


Geigenberger, Peter, Ina Thormählen, Danilo M. Daloso, and Alisdair R. Fernie. 2017. “The Unprecedented Versatility of the Plant Thioredoxin System.” Trends in Plant Science 22 (3): 249–62. https://doi.org/https://doi.org/10.1016/j.tplants.2016.12.008.
Hägglund, Per, Christine Finnie, Hiroyuki Yano, Azar Shahpiri, Bob B. Buchanan, Anette Henriksen, and Birte Svensson. 2016. “Seed Thioredoxin H.” Biochimica et Biophysica Acta (BBA) - Proteins and Proteomics 1864 (8): 974–82. https://doi.org/https://doi.org/10.1016/j.bbapap.2016.02.014.
Kobrehel, K, J H Wong, A Balogh, F Kiss, B C Yee, and B B Buchanan. 1992. “Specific Reduction of Wheat Storage Proteins by Thioredoxin H.” Plant Physiology 99 (3). American Society of Plant Biologists: 919–24. https://doi.org/10.1104/pp.99.3.919.
Maeda, Kenji, Christine Finnie, and Birte Svensson. 2005. “Identification of Thioredoxin h-Reducible Disulphides in Proteomes by Differential Labelling of Cysteines: Insight into Recognition and Regulation of Proteins in Barley Seeds by Thioredoxin h.” PROTEOMICS 5 (6): 1634–44. https://doi.org/10.1002/pmic.200401050.
Motohashi, Ken, Aiko Kondoh, Michael T. Stumpp, and Toru Hisabori. 2001. “Comprehensive Survey of Proteins Targeted by Chloroplast Thioredoxin.” Proceedings of the National Academy of Sciences 98 (20). National Academy of Sciences: 11224–9. https://doi.org/10.1073/pnas.191282098.
Verdoucq, L, F Vignols, J P Jacquot, Y Chartier, and Y Meyer. n.d. “In Vivo Characterization of a Thioredoxin H Target Protein Defines a New Peroxiredoxin Family.” J Biol Chem 274 (28). Laboratoire de Physiologie et de Biologie Moléculaire des Plantes, UMR 5545, Université de Perpignan, Avenue de Villeneuve, F 66025, Perpignan, France.: 19714–22. https://doi.org/10.1074/jbc.274.28.19714.
Yamazaki, Daisuke, Ken Motohashi, Takeshi Kasama, Yukichi Hara, and Toru Hisabori. n.d. “Target Proteins of the Cytosolic Thioredoxins in Arabidopsis Thaliana.” Plant Cell Physiol 45 (1). Chemical Resources Laboratory, Tokyo Institute of Technology, Nagatsuta 4259, Midori-ku, Yokohama, 226-8503 Japan.: 18–27. https://doi.org/10.1093/pcp/pch019.


WITNESS LIST Civil Justice (Interim) Committee April 23, 1998-9:30A Unins.Motorists-Tort System Changes On: Campbell, Jerry P. (TX Asc Defense Counsels), Waco O'Connell, Jeffrey (self), Charlottsvile Ryles, Tim (Defense&Plaintiffs Atty), Newborn Slack, Mike (TTLA), Austin Tobias, Andrew (self), Miami Watkins, Robert L. (State Farm Insurance Co), Bloomington Uninsured Motorists On: Anderson, Lyndon (TDI), Austin Birnbaum, Birny (Center for Eco. Justice), Austin Bomer, Elton (TDI, Commissioner), Austin Durden, David (TDI), Austin Gaslin, Guillermo (self), Cedar Park Lambe, Dan (TX Citizen Action), Austin Presley, Philip (self), Austin Purcell, Carolyn (self), Austin Riley, Jack Lee (self), Amarillo Strain, Sputnik (TX MC Rights Assoc.), Algoa Uninsured Motorists - Enforcement On: Dike, Jerry (TX DOT), Austin Elder, Frank (TX DPS), Austin Loewe, Eric (NAII), Des Plaines O'Connell, Jeffrey (self), Charlottsvile Sherman, E.C. (TX DPS), Austin


| Home | Libraries | People | FAQ | More |
The abstract base class encapsulating a platform-specific file handle.
class async_io_handle : public std::enable_shared_from_this< async_io_handle > { // ... };
|
Function |
Description |
Parameters |
|---|---|---|
~async_io_handle() |
|
Function |
Description |
Parameters |
Returns |
|---|---|---|---|
async_file_io_dispatcher_base * parent() |
Returns the parent of this io handle. |
||
std::shared_ptr< async_io_handle > container() |
Returns a handle to the directory containing this handle. Only
works if |
||
void * native_handle() |
Returns the native handle of this io handle. On POSIX, you can
cast this to a fd using |
||
const chrono::system_clock::time_point & opened() |
Returns when this handle was opened. |
||
const std::filesystem::path & path() |
Returns the path of this io handle. |
||
file_flags flags() |
Returns the final flags used when this handle was opened. |
||
bool opened_as_file() |
True if this handle was opened as a file. |
||
bool opened_as_dir() |
True if this handle was opened as a directory. |
||
bool opened_as_symlink() |
True if this handle was opened as a symlink. |
||
off_t read_count() |
Returns how many bytes have been read since this handle was opened. |
||
off_t write_count() |
Returns how many bytes have been written since this handle was opened. |
||
off_t write_count_since_fsync() |
Returns how many bytes have been written since this handle was last fsynced. |
||
directory_entry direntry(metadata_flags wanted = directory_entry::metadata_fastpath()) |
Returns a mostly filled directory_entry for the file or directory
referenced by this handle. Use |
metadata_flags: wanted: |
|
stat_t lstat(metadata_flags wanted = directory_entry::metadata_fastpath()) |
Returns a mostly filled stat_t structure for the file or directory
referenced by this handle. Use |
metadata_flags: wanted: |
|
std::filesystem::path target() |
Returns the target path of this handle if it is a symbolic link. |
||
void * try_mapfile() |
Tries to map the file into memory. Currently only works if handle is read-only. |
#include <boost/afio/afio.hpp>


--- layout: post title: This baseball player is INSANE category: video tags: - Video status: publish type: post published: true meta: ---
Nothing else to say really.


| 1 |
Kookmin University |
Reaction mechanism study on SARS Coronavirus helicase and its applications to develop the inhibitors |
45,736 |
137,209 |
1 November 2013 |
31 October 2016 |
| 2 |
Chonbuk National University |
A genetic characteristic study for zoonotic potential of several pathogens from bats in Korea |
15,152 |
45,455 |
1 June 2018 |
31 May 2021 |
| 3 |
Kookmin University |
Mechanistic study on SARS Coronavirus helicase in the process of viral genome replication |
18,272 |
54,816 |
1 September 2010 |
31 August 2013 |
| 4 |
Chungnam National University |
Identification of mechanism of coronavirus cross-species transmission and pathogenesis mediated by host proteases |
45,455 |
136,364 |
1 March 2020 |
28 February 2023 |
| 5 |
Center for Disease Control |
Immunogenocity of SARS-CoV receptor binding protein expressed on coxsackieviral vector |
30,455 |
60,909 |
1 January 2010 |
31 December 2011 |


secoJenaTextFacet
seco.facetedSearch
A free-text search facet using Jena text search.
This facet can only be used if the SPARQL endpoint supports Jena text query.
The facet does not make any SPARQL queries, just generates SPARQL triple patterns out of the typed text for other facets to use.
The produced constraint looks like the following (where predicate
, and limit
are based on the configuration options, and left out if undefined):
(?id ?score) <http://jena.apache.org/text#query> (predicate "search terms" limit) .
If the graph
option is defined, the constraint is wrapped accordingly:
GRAPH graph { (?id ?score) <http://jena.apache.org/text#query> (predicate "search terms" limit) . }
The score is captured as variable ?score
, and can thus be used to sort results.
The search terms are sanitized in order to avoid syntax errors from the backend.
In case there is an even number of quotes ("
) they are escaped in the search terms.
If there is an odd number of quotes, they are removed.
Backslashes, and parentheses are removed, as well as AND
, OR
, and NOT
,
if they are the first or last tokens in the query.
"~
" is removed if it's the first character in the query.
Consecutive "~
" are removed. I.e. "~~
" is changed to "~
".
Otherwise the search terms are not modified, so e.g. AND
, OR
, *
, and ~
can be used in the query.
The sanitization is not reflected to the user, so if a search triggers while
they are writing, and the last word they wrote is, e.g., "AND
",
the user will see all that they wrote, but the produced SPARQL constraint
will not include the AND
. The user can continue writing, and the next time
the search triggers, if the query is valid, the constraint will include it.
<seco-jena-text-facet options="{Object}"> </seco-jena-text-facet>
| Param | Type | Details |
|---|---|---|
| options | Object | The configuration object with the following structure:
|


{% include 'layouts/home_head.html' %}
Skip to content
{% include 'dashboard-layouts/header.html' %}
Last Updated :
Index Name
Current Value
Change
% Change
{% for index in indices%}
{{index}}
{%endfor%}
{% include 'layouts/home_footer.html' %} {% include 'layouts/home_additonal_body_contents.html' %}


HFV: a Business Inteligence tool with Artificial Intelligence algorithms to Measure “Academic Behavior Analysis in Virtual Courses Using a Data Mining Approach. This tool periodically feeds from the log from CMS (LVE) (for example Moodle) to produce metrics that characterize each student, course, program, calendar and/or academic period to help profesors, teachers and Directors to take decisions. To the students, it tells their behavior and helps forsee their performence based on the interaction againts the virtual learning platform.
HFV Helps to know the Behavior of Virtual Students & Correlates it to their Performance
1. Show (graphically) the interaction of students or tutors in these platforms to define tools or policies that directly impact the retention and permanence of students.
2. The data that these tool collects, after some EDM, can provide multiple dimensions of student behavior to teachers and the institution. so, tutors can take decions on the fly by "observing" individual or group virtual behavior.
1. Helps to foresee how will be his/her performance based on his behavior correlated against analyzed historical/periodical patrons.
2. Gives comparisions and correlations to show competitiveness in behavior not only on grades. Show levels of interaction: Access, Use of resources, interaction with other Students and Teacher.