The in-memory solution for the Oasis Kernel is called the kernel tools or “ktools”. ktools is an independent “specification” of a set of processes which means that it defines the processing architecture and data structures. The framework is implemented as a set of components called the “reference model” which can then be adapted for particular model or business needs.
The code can be compiled in Linux, POSIX-compliant Windows and native Windows. The installation instructions can be found in README.md.
The Kernel performs the core Oasis calculations of computing effective damageability distributions, Monte-Carlo sampling of ground up loss, the financial module calculations, which apply insurance policy terms and conditions to the sampled losses, and finally some common catastrophe model outputs.
The early releases of Oasis used a SQL-compliant database to perform all calculations. Release 1.3 included the first “in-memory” version of the Oasis Kernel written in C++ and C to provide streamed calculation at high computational performance, as an alternative to the database calculation. The scope of the in-memory calculation was for the most intensive Kernel calculations of ground up loss sampling and the financial module. This in-memory variant was first delivered as a stand-alone toolkit "ktools" with R1.4.
With R1.5, a Linux-based in-memory calculation back-end was released, using the reference model components of ktools. The range of functionality of ktools was still limited to ground up loss sampling, the financial module and single output workflows, with effective damage distributions and output calculations still being performed in a SQL-compliant database.
In 2016 the functionality of ktools was extended to include the full range of Kernel calculations, including effective damageability distribution calculations and a wider range of financial module and output calculations. The data stream structures and input data formats were also substantially revised to handle multi-peril models, user-definable summary levels for outputs, and multiple output workflows.
In 2018 the Financial Module was extended to perform net loss calculations for per occurrence forms of reinsurance, including facultative reinsurance, quota share, surplus share, per risk and catastrophe excess of loss treaties.
The Kernel is provided as a toolkit of components (“ktools”) which can be invoked at the command line. Each component is a separately compiled executable with a binary data stream of inputs and/or outputs.
The principle is to stream data through the calculations in memory, starting with generating the damage distributions and ending with calculating the user's required result, before writing the output to disk. This is done on an event-by-event basis, which means at any one time the compute server only has to hold the model data for a single event in its memory, per process. The user can run the calculation across multiple processes in parallel, specifiying the analysis workfkow and number of processes in a script file appropriate to the operating system.
The components can be written in any language as long as the data structures of the binary streams are adhered to. The current set of components have been written in POSIX-compliant C++. This means that they can be compiled in Linux and Windows using the latest GNU compiler toolchain.
The components in the Reference Model can be summarized as follows;
Standard piping syntax can be used to invoke the components at the command line. It is the same syntax in Windows DOS, Linux terminal or Cygwin (a Linux emulator for Windows). For example the following command invokes eve, getmodel, gulcalc, fmcalc, summarycalc and eltcalc, and exports an event loss table output to a csv file.
$ eve 1 1 | getmodel | gulcalc -r –S100 -a1 –i - | fmcalc | summarycalc -f -1 - | eltcalc > elt.csv
Example python scripts are provided along with a binary data package in the /examples folder to demonstrate usage of the toolkit. For more guidance on how to use the toolkit, see Workflows.


Each of these 162 dots is a
Technology Development and Demonstration research project!
In space, physical processes can be better understood with the control of external influences such as gravity. Technical innovations designed for space systems are tested on the International Space Station (ISS) before use in other spacecraft systems. While investigating how new technologies operate in space, unexpected discoveries are possible. Simplified physical systems can also be directly used to improve models of physical processes leading to new industrial techniques and materials.
The ISS provides the unique capability to perform long-duration experiments in the absence of gravity and in interaction with other spacecraft systems not available in any other laboratory. Additional insight comes from the presence of the ISS crew observing and interacting with these experiments and participating in the discovery process.
The ISS research portfolio includes many engineering and technology investigations designed to take advantage of these opportunities. Experiments investigating thermal processes, nanostructures, fluids and other physical characteristics are taking place to develop these technologies and provide new innovations in those fields. Additionally, advanced engineering activities operating in the space station infrastructure are proving next-generation space systems to increase capabilities and decrease risks to future missions. Emerging materials, technology and engineering research activities on the ISS are developing into benefits for economic development and quality of life.


Library: Net
Package: Messages
Header: Poco/Net/MultipartWriter.h
Description
This class is used to write MIME multipart messages to an output stream.
The format of multipart messages is described in section 5.1 of RFC 2046.
To create a multipart message, first create a MultipartWriter object. Then, for each part, call nextPart() and write the content to the output stream. Repeat for all parts. After the last part has been written, call close() to finish the multipart message.
Member Summary
Member Functions: boundary, close, createBoundary, nextPart, stream
Constructors
MultipartWriter
explicit MultipartWriter(
std::ostream & ostr
);
Creates the MultipartWriter, using the given output stream.
Creates a random boundary string.
MultipartWriter
MultipartWriter(
std::ostream & ostr,
const std::string & boundary
);
Creates the MultipartWriter, using the given output stream and boundary string.
Destructor
~MultipartWriter
~MultipartWriter();
Destroys the MultipartWriter.
Member Functions
boundary
const std::string & boundary() const;
Returns the multipart boundary used by this writer.
close
void close();
Closes the multipart message and writes the terminating boundary string.
Does not close the underlying stream.
createBoundary
static std::string createBoundary();
Creates a random boundary string.
The string always has the form MIME_boundary_XXXXXXXXXXXX, where XXXXXXXXXXXX is a random hexadecimal number.
nextPart
void nextPart(
const MessageHeader & header
);
Opens a new message part and writes the message boundary string, followed by the message header to the stream.
stream
std::ostream & stream();
Returns the writer's stream.


Fish out Kogi PDP woman leader’s murderers –Buhari
by John AmehJohn Ameh, Abuja
President Muhammadu Buhari said on Sunday that he expected security agencies to conduct a thorough investigation into the “heinous murder” of a Kogi State Peoples Democratic Party Woman Leader, Mrs Achejuh Abuh.
Buhari stated that justice would be served upon conclusion of the investigation, describing the killing as “primitive behaviour” that should not be condoned.
“President Muhammadu Buhari expects scrupulous investigation into the heinous murder of Madam Achejuh Abuh, Woman Leader of the Peoples Democratic Party in Wada/Aro campaign council, in the just-concluded gubernatorial election in Kogi State.
“The President decries whatever could spur anyone to take the life of another human being, particularly a woman, who was burnt to death in her home in the most gruesome manner.
“President Buhari charges all security agencies involved in the investigation to do a thorough and expeditious job on the matter, so that justice could be served without fear or favour”, a State House statement by his media aide, Mr Femi Adesina, said on Sunday.
Buhari said he shared in the grief of the family of the deceased, giving them the assurance that the law would take its full course.
“We must learn to behave decently, whether during elections or at other times. No life should be taken wantonly under any guise, and the fact that this reprehensible act occurred two days after voting shows primitive behaviour, which should not be accepted in a decent society”, the President was quoted as saying.
CopyrightPUNCH.
All rights reserved. This material, and other digital content on this website, may not be reproduced, published, broadcast, rewritten or redistributed in whole or in part without prior express written permission from PUNCH.
Contact: editor@punchng.com


{{define "title"}}Evepraisal - Price check Eve Online items from Cargo Scans, Contracts, D-Scan, EFT, Inventory, Asset listing, Loot History, PI, Survey Scanner, Killmails, Wallet Transactions, Inventory, Assets{{end}} {{define "description"}}Price check Eve Online items from Cargo Scans, Contracts, D-Scan, EFT, Inventory, Asset listing, Loot History, PI, Survey Scanner, Killmails, Wallet TransactionsBlocks, Inventory, Assets{{end}} {{define "content"}}
Evepraisal is a tool for quickly getting bulk estimates of items from Eve Online.
Find something in Eve Online that you want to price check like a contract, cargo scan result, etc. Press CTRL + A, CTRL + C, then click on the lovely box to the left or above this and press CTRL + V. Submit and you should see a price breakdown of all the items.
At first, this started as a simple cargo scan estimator but over time more formats have been added to the parser so you can use it as a more general price checker. Currently the following formats are supported:


Overview
Package
FRAMES
NO FRAMES
Package org.jclouds.cloudservers.domain
Class Summary
AbsoluteLimit
Action
Addresses
BackupSchedule
Builder
ConcreteBuilder
DailyBackup
Flavor
Image
ImageStatus
Limits
RateLimit
RateLimitUnit
RebootType
Server
ServerStatus
ShareIp
SharedIpGroup
Version
VersionStatus
WeeklyBackup
Overview
Package
FRAMES
NO FRAMES
Copyright © 2009-2013 The Apache Software Foundation. All Rights Reserved.


Hello {{username.title()}}
View Weather of place to visit
Current Location/Current IP for Loadbalancing
{{ final }}
Trending Now...
All weather now...
Logout


We are Viridian Robotics, Team 9054, one of two teams from Greenhill School (the other is the Motorheads, Team 9045). We are the founding team of the robotics program at Greenhill School, and this is our 5th year competing in First Tech Challenge.
Our History
In the year of our founding, the very beginning of our team started with a big dream. We had a total of eight members by the end of our first month and a small space with scant storage. Now, we have expanded to two teams of around eleven members each with dedicated programmers, 3D-designers, and builders. Our experiences at previous FTC meets, including winning the Think Award at the Qualifying Championship 2014-2015 and competing at the Regional Championship 2014-2015, has overall strengthened our team and progress year after year. Everyone works together cohesively and becomes exposed to each part of the process, and in the years to come, our robotics teams will continue to achieve and set more goals to challenge ourselves to always work our hardest and be the best team we can possibly be.
Recent Tweets
Tweets by viridianroboticSchedule
Location
Greenhill school is in Addison, Texas off Spring Valley Rd.
4141 Spring Valley Rd Addison TX 75001


| Code | Name | Address | Country | Type | Discount Percentage | Credit Limit | Credit Status | Payment Terms | Language | Currency | Active |
|---|---|---|---|---|---|---|---|---|---|---|---|
| A | John Doe | 620 5th Ave, New York, NY 10020 | United States | Retail | 9 | 999999 | Good history | Due by end of the following month | English | US Dollar (USD) | YES |
| B | João da Silva | Av. Magalhães de Castro, 12000 - Jardim Panorama, São Paulo - SP, 05502-001 | Brazil | Retail | 7 | 777777 | Good history | Cash only | Portuguese | Brazilian Real (BRL) | YES |
| C | Taro Tanaka | 327-0822 Tochigi, Sano, Koenacho, 2058 Sano Premium Outlet 640 | Japan | Retail | 8 | 888888 | Good history | Payment due within 7 days | Japanese | Japanese Yen (JPY) | YES |


TMR-24 Virtual Assistant Manager
“Delegate the routine to a Virtual Assistant Manager.
We do not offer a "remind calendar", but a trained virtual assistant manager who, upon request or schedule, can submit reports, monitor running processes to achieve specific goals of the organization and, in case of deviation from the specified parameters, notify of a failure.
Supervision of "control points" of business processes
Monitor the accuracy of business processes, calculate the values of performance indicators and correlate them with planned values, then identify problems and promptly report to the manager.
Operational reporting in Telegram for the accuracy of decision-making
The application sends a report at a configured interval, on request, according to the trained criteria and allows the owner to promptly monitor the business processes of the enterprise.
Personnel management via Telegram chatbot (operational Manager)
To make life easier for the manager, we developed a special Telegram bot, which took over some of the routine tasks:
Supervision of "control points" of business processes
What to control: the result or the process?
Each manager has his own view, one is convinced that it is only necessary to ask for the result, the other prefers to track all the stages of completing tasks, and for the third control means spying on employees and catching violators of discipline.
Automated control in this case is used not so much as a tool to measure the effectiveness of individual employees, but in order to quickly notice emerging problems at the macro level and solve them; so that the top manager has the opportunity at any time to assess the situation by objective parameters, and not rely only on reports of subordinates.
We will implement a chatbot and support stable work, in the shortest possible time with a personal manager, your virtual assistant will start working.
-
The mission of the company.
-
The companys strategy.
-
The companys system of indicators.
-
Control points.
The mechanism of business processes perfectly fits into the structure of the bots dialogue, individual tasks in blocks are bot phrases, branching points are the branching points of a conversation with answer options - buttons, etc.
Visualization of the map simplifies the work of the team, but is not a guarantee of its success. It is important to check the map regularly to track failures and make adjustments if necessary.
Time. Money. Result.
Operational reporting in Telegram for the accuracy of decision-making
A virtual digital assistant based on natural language processing (NLP) technologies instantly prepares business reports in the Telegram messenger chat, connecting to your company's data sources.
The parameters for the report are changed according to your request based on the learning platform, and the data is displayed in a simple format.
Bots work 24/7 and will allow you to be as informed as possible in decision-making issues.
Our specialists are always ready to implement your tasks, offer an individual solution in the shortest possible time or set up a standard report:
-
Implementation of the sales plan.
-
The girth of the customer base.
-
The workload of the staff.
-
The workload of the equipment.
-
Overdue customer orders.
-
Plan-fact analysis.
-
Aging of inventory.
The efficiency of the enterprise when using KPI and BSC systems depends entirely on how these indicators are selected and set, because the range of possible indicators is extremely wide.
The means and principles (policies) of achieving the goals are set, otherwise the principles of "the goal justifies the means" and "all means are good to achieve the goal" begin to operate, and very serious negative consequences are possible in the near future.
Time. Money. Result.
Personnel management via Telegram chatbot (Operational Manager)
The chatbot can manage assigned projects, send messages, post tasks according to the plan, and also, can make mailing to subordinates in automatic mode, thereby saving the time and effort of the manager.
It is not enough to hire qualified specialists: the market is constantly in development, new technologies are being introduced, new trends are emerging that require employees to regularly update their knowledge.
The chat bot is based on And allows you to undergo training at any convenient time, without interrupting the employee from the main activity, without loss of productivity, and most importantly controls and engages the learning process.
Chatbots are the main hit of this year, they suddenly turned from a curiosity into a popular, effective technology where artificial intelligence harmoniously complements the functionality of bots penetrating into different areas of activity.
-
Organization of personnel work (issuance of production tasks, control of execution, simplification of the companys workflow).
-
Training and testing of personnel.
-
In groups of messengers and social networks.
-
The site widget.
-
Voice assistant.
-
Call center.
-
Surveys and questionnaires.
The bot surpasses any person in the possibility of storing and operating large amounts of data, can select the right words to communicate with each user from a multimillion-dollar list. Such a subtle personalization of communication will definitely benefit any business.
The instant reaction of the bot to the users actions helps the business a lot, shows interest in both the client and the companys staff, making the business more efficient.
Time. Money. Result.


You are viewing an historical archive of past issues. Please
report new issues to the appropriate project issue tracker on
GitHub.
Comments
-
Greg Hurrell
Bah, forgot about the
g:CommandTScanDotDirectories
setting.In the example above, you can't open
.git/config
due to the'wildignore'
setting, but you can open stuff inside.vim
, provided thatg:CommandTScanInsideDotDirectories
is set. -
Greg Hurrell
Status changed:
- From: new
- To: closed
Add a comment
Comments are now closed for this issue.


Class: ActiveRecord::Relation::Merger
Do not use. This class is for internal use only.
| Relationships & Source Files | |
| Inherits: | Object |
| Defined in: | activerecord/lib/active_record/relation/merger.rb |
Constant Summary
-
NORMAL_VALUES =
# File 'activerecord/lib/active_record/relation/merger.rb', line 54Relation::VALUE_METHODS - Relation::CLAUSE_METHODS - [ :select, :includes, :preload, :joins, :left_outer_joins, :order, :reverse_order, :lock, :create_with, :reordering ]
Class Method Summary
- .new(relation, other, rewhere = nil) ⇒ Merger constructor
Instance Attribute Summary
- #other readonly
- #relation readonly
- #values readonly
- #replace_from_clause? ⇒ Boolean readonly private
Instance Method Summary
- #merge
- #merge_clauses private
- #merge_joins private
- #merge_multi_values private
- #merge_outer_joins private
- #merge_preloads private
- #merge_select_values private
- #merge_single_values private
Constructor Details
.new(relation, other, rewhere = nil) ⇒ Merger
Instance Attribute Details
#other (readonly)
[ GitHub ]#relation (readonly)
[ GitHub ]
#replace_from_clause? ⇒ Boolean
(readonly, private)
[ GitHub ]
#values (readonly)
[ GitHub ]Instance Method Details
#merge
[ GitHub ]# File 'activerecord/lib/active_record/relation/merger.rb', line 60
def merge NORMAL_VALUES.each do |name| value = values[name] # The unless clause is here mostly for performance reasons (since the `send` call might be moderately # expensive), most of the time the value is going to be `nil` or `.blank?`, the only catch is that # `false.blank?` returns `true`, so there needs to be an extra check so that explicit `false` values # don't fall through the cracks. unless value.nil? || (value.blank? && false != value) relation.public_send(:"#{name}!", *value) end end merge_select_values merge_multi_values merge_single_values merge_clauses merge_preloads merge_joins merge_outer_joins relation end
#merge_clauses (private)
[ GitHub ]# File 'activerecord/lib/active_record/relation/merger.rb', line 176
def merge_clauses relation.from_clause = other.from_clause if replace_from_clause? where_clause = relation.where_clause.merge(other.where_clause, @rewhere) relation.where_clause = where_clause unless where_clause.empty? having_clause = relation.having_clause.merge(other.having_clause) relation.having_clause = having_clause unless having_clause.empty? end
#merge_joins (private)
[ GitHub ]# File 'activerecord/lib/active_record/relation/merger.rb', line 117
def merge_joins return if other.joins_values.empty? if other.klass == relation.klass relation.joins_values |= other.joins_values else associations, others = other.joins_values.partition do |join| case join when Hash, Symbol, Array; true end end join_dependency = other.construct_join_dependency( associations, Arel::Nodes::InnerJoin ) relation.joins!(join_dependency, *others) end end
#merge_multi_values (private)
[ GitHub ]# File 'activerecord/lib/active_record/relation/merger.rb', line 155
def merge_multi_values if other.reordering_value # override any order specified in the original relation relation.reorder!(*other.order_values) elsif other.order_values.any? # merge in order_values from relation relation.order!(*other.order_values) end extensions = other.extensions - relation.extensions relation.extending!(*extensions) if extensions.any? end
#merge_outer_joins (private)
[ GitHub ]# File 'activerecord/lib/active_record/relation/merger.rb', line 136
def merge_outer_joins return if other.left_outer_joins_values.empty? if other.klass == relation.klass relation.left_outer_joins_values |= other.left_outer_joins_values else associations, others = other.left_outer_joins_values.partition do |join| case join when Hash, Symbol, Array; true end end join_dependency = other.construct_join_dependency( associations, Arel::Nodes::OuterJoin ) relation.left_outer_joins!(join_dependency, *others) end end
#merge_preloads (private)
[ GitHub ]# File 'activerecord/lib/active_record/relation/merger.rb', line 96
def merge_preloads return if other.preload_values.empty? && other.includes_values.empty? if other.klass == relation.klass relation.preload_values |= other.preload_values unless other.preload_values.empty? relation.includes_values |= other.includes_values unless other.includes_values.empty? else reflection = relation.klass.reflect_on_all_associations.find do |r| r.class_name == other.klass.name end || return unless other.preload_values.empty? relation.preload! reflection.name => other.preload_values end unless other.includes_values.empty? relation.includes! reflection.name => other.includes_values end end end
#merge_select_values (private)
[ GitHub ]# File 'activerecord/lib/active_record/relation/merger.rb', line 84
def merge_select_values return if other.select_values.empty? if other.klass == relation.klass relation.select_values |= other.select_values else relation.select_values |= other.instance_eval do arel_columns(select_values) end end end


{{/* Copyright (c) 2017, OCAD University, [BSD-3-Clause](https://github.com/fluid-lab/iad-guide-theme/blob/master/LICENSE) */}} {{ partial "head/head.html" . }}


Safety
Is climbing safe? Well, any sport that involves leaving the ground is going to involve a certain amount of risk. Climbing is certainly more dangerous than, say, using an elliptical trainer or walking in the park. Most climbers do end up with some scrapes and bruises from harder routes.
That said, climbing is nowhere near as risky as extreme sports like snowboarding. Climbers use a lot of safety equipment, and that equipment is designed and tested to survive intense forces. In fact, I feel far more comfortable 50 feet above the ground on a climbing rope than 5 feet up on a ladder. Serious climbing accidents are rare, especially in indoor climbing.
 This one is self-explanatory. Indoor rock climbing gyms are usually very safe environments, with staff that watch for dangerous practices.  Follow the rules--they are there for a reason. Outdoors climbing takes place in an uncontrolled environment. There are all the usual dangers of being outside, like inclement weather, combined with some other possible dangers, like poorly anchored bolts. If you are climbing outside, go with an experienced climber and use your common sense.
- Inattention. Safety gear only works if you use it properly. Inattention means not checking your gear, leaving your knots untied, or forgetting to double back your harness buckles. A belayer who is not paying attention to their climber can also fail to stop a fall or lower a climber too quickly. Always do your double-checks and never climb with a belayer you do not trust.
- Inadequate or poorly maintained gear. Climbing gear is expensive, and it can be tempting to cut corners. Don't do it. A broken ankle is far more expensive than spending $20 extra dollars for a new harness. In the equipment section I talk more about what gear you can buy used, and what you should get new. Also check your gear regularly for signs of wear, and replace it if it looks like it is starting to wear out. The same goes for rented or borrowed equipment. Inspect it, and don't be afraid to ask for other gear if what you got looks sketchy.
Pay attention and trust your instincts, and you should be just fine.


Simple input field validation using keyup events
Simple input field validation using the 'input' event
Just type a name in the input field and see what happens!
TRY TO TYPE A "!" too
Name (required):


Ariel-1 (A1) is a 2000 lbf Liquid Oxygen, Liquid Natural Gas or Methane engine currently being designed and developed by the Rocket Propulsion Laboratory. A1’s first static fire is planned for August of 2017.
As with all RPL projects, Ariel-1 is an opensource project. Click the link to source on under Technical Specifications to the right to view all of our technical document.
Ariel-1 is the first iteration of the Ariel engine. The engine is designed to use LOX/Methane, a cheap propellant combination which can be synthesized on Mars using the Sebatier reaction.
Thrust: 2000 lbf
Propellants: LOX/LNG
Material: Inconel 718
Link to Source: https://github.com/rocketproplab/Ariel-1


A female pygmy goat is called a doe or nanny. A male pygmy goat is called a buck.
A lot of people like to get a dog or a cat for a pet. One can’t blame them because they do make great companions at home. They are affectionate, and some are even therapeutic. But if you’re not the conventional type, and you want something a little more unique, a pygmy goat is a very good option.


Id
Name
1
first user name
2
second user name
Id
Description
1
first order description
2
second order description


Kyle I S Harrington /<EMAIL_ADDRESS>Some slides adapted from Roni Khardon
The range of values for a given feature can impact an algorithm's performance
Remember using the value of the year directly on assignment 1?
Scale the values into the range $[0,1]$
$x \leftarrow \frac{ x - x_{min} }{ x_{max} - x_{min} }$
Scale based on training set only
Scale the distribution to have mean=0 and std=1
$x \leftarrow \frac{ x - \mu_X }{ \sigma_X }$
Scale based on training set only
Some algorithms only work on discrete features
We may need to discretize real-valued features
Calculate the histogram
This divides the values into bins
Alternatively, use a heuristic/ad-hoc method to discretize in a useful way
E.G. Build a decision tree, let the DT algorithm discretize, and use the split values of the optimized tree
Some features are unordered (i.e. Browsers = [ Firefox, Chrome, Safari ])
Most common approach is to use unit vectors:
| Firefox | Chrome | Safari |
| 1 | 0 | 0 |
| 0 | 1 | 0 |
| 0 | 0 | 1 |
Proposal due: 03/07
Write a 300-500 word abstract describing your proposed project. This should include 2-3 references of papers you expect to include in your final paper.
Project due: 04/25
Turn in a 8-12 page paper. A rough outline is:
B-cell receptors bind specific molecular structures to recruit immune system activity.
B-cell antibody release for recruitment. Image from Arizona Science Center/WikipediaThe epitope prediction problem:
Given that a protein is a sequence of amino acids that fold into a 3D shape, only a subset of these amino acids are bound by B-cell receptors. Which ones?
Protein folding. Image from L. El Ghaoui, BerkeleyComplex Features in Prediction of Discontinuous B-cell Epitopes
This is a project with James Chin.
There are existing methods for B-cell epitope prediction. They vary in terms of specific feature sets, machine learning algorithms, and training/test sets.
Much of the advancement in B-cell epitope prediction has been driven by improvement in features.
We propose a method for synthesizing complex features from a set of basis features that allows provides high-degrees of nonlinearity not possible with simple ML representations.
Linear Threshold Units


EPUB3 Reader Feature Test
Document with a different external CSS for each spine item. Each page tests a different CSS-fontface


new Browser(options)
API for browsers (internal object).
Parameters:
| Name | Type | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
options |
Object |
Properties
|
- Source:
Fires:
Methods
-
addEventListener(event, callback)
-
Registers a listener for an event on the browser instance.
Parameters:
Name Type Description event
String callback
errorCallback - Source:
-
addOwner(emailID, callback)
-
Adds a user as an owner of the current browser
Parameters:
Name Type Description emailID
String callback
errorCallback - Source:
-
addReader(emailID, callback)
-
Adds a user as a reader of the current browser
Parameters:
Name Type Description emailID
String callback
errorCallback - Source:
-
addReaderWriter(emailID, callback)
-
Adds a user as a readerwriter of the current browser
Parameters:
Name Type Description emailID
String callback
errorCallback - Source:
-
close(callback)
-
Closes the browser.
Parameters:
Name Type Description callback
errorCallback - Source:
-
createComponent(name, target, options) → {DOMNode}
-
Creates a new component
Parameters:
Name Type Description name
String The registered name of the component.
target
DOMNode The DOM node in which the component will be embedded.
options
Object Extra options to customize the component.
- Source:
Returns:
- Type
- DOMNode
-
getAppConfig() → {AppConfig}
-
Gets the Application API object.
- Source:
Returns:
- Type
- AppConfig
-
getAppInstanceConfig() → {AppInstance}
-
Gets the application instance associated with the current browser
- Source:
Returns:
- Type
- AppInstance
-
getConnectedClients() → {Array.<{{address: String, email: String}}>}
-
Gets information about the users connected to the current browser
- Source:
Returns:
- Type
- Array.<{{address: String, email: String}}>
-
getCreator() → {String}
-
Gets the user that created the instance.
- Source:
Returns:
- Type
- String
-
getDateCreated() → {Date}
-
Gets the date of creation of the instance.
- Source:
Returns:
- Type
- Date
-
getID() → {Number}
-
Gets the ID of the instance.
- Source:
Returns:
- Type
- Number
-
getLocalState() → {Object}
-
Gets the local state with the current browser
- Source:
Returns:
Custom object provided by the application in the application state file
- Type
- Object
-
getName() → {String}
-
Gets the name of the instance.
- Source:
Returns:
- Type
- String
-
getOwners() → {Array.<User>}
-
Gets all users that are the owners of the instance There is a separate method for this as it is faster to get only the number of owners than to construct a list of them using getOwners and then get that number.
- Source:
Returns:
- Type
- Array.<User>
-
getReaders() → {Array.<User>}
-
Gets all users that have the permission only to read
- Source:
Returns:
- Type
- Array.<User>
-
getReaderWriters() → {Array.<User>}
-
Gets all users that have the permission only to read and write to the instance.
- Source:
Returns:
- Type
- Array.<User>
-
getResetEmail(callback)
-
Gets the email ID that is stored in the session
Parameters:
Name Type Description callback
emailCallback - Source:
-
getURL() → {String}
-
Gets the url of the instance.
- Source:
Returns:
- Type
- String
-
grantPermissions(permission, user, callback)
-
Grants the user a role/permission on the browser.
Parameters:
Name Type Description permission
String user
User callback
errorCallback - Source:
-
isAssocWithCurrentUser() → {Bool}
-
Checks if the current user has some permission associated with this browser
- Source:
Returns:
- Type
- Bool
-
isOwner(user) → {Bool}
-
Checks if the user is an owner of the instance
Parameters:
Name Type Description user
String - Source:
Returns:
- Type
- Bool
-
isReader(emailID) → {Bool}
-
Checks if the user is a reader of the instance.
Parameters:
Name Type Description emailID
String - Source:
Returns:
- Type
- Bool
-
isReaderWriter(user) → {Bool}
-
Checks if the user is a reader-writer of the instance.
Parameters:
Name Type Description user
String - Source:
Returns:
- Type
- Bool
-
redirect(url)
-
Redirects all clients that are connected to the current instance to the given URL.
Parameters:
Name Type Description url
String - Source:
-
rename(newName)
-
Renames the instance.
Parameters:
Name Type Description newName
String - Source:
Fires:
Events
-
rename
-
Event to indicate that the current browser has been renamed
Type:
- String
- Source:
-
share
-
Event to indicate that the current browser has been shared with another user
- Source:


Mail from: From Address Search
Mail To: To Address Search
Subject: Subject Search
Sent Date: Sent Date Search
Message Content: Message Content Search


Home
Log In
Sign Up
Districts
Search
Trivandrum
Kollam
Pathanamthitta
Alappuzha
Kottayam
Idukki
Ernakulam
Thrissur
Palakkad
Malappuram
Kozhikode
Kannur
Kasargod
Wayanad


I've been building websites since '01. Professional experience includes project management at a leading Drupal consultancy for the nonprofit sector, community technology training and conference organizing as a VISTA fellow, and heading the development, hosting, and support of 2,000+ nonprofit website projects at a national organization. I also advise several startups on technology strategy.
I've been a digital nomad since '09, working primarily from Chicago, IL, and Calcutta, India. In my spare time, I travel by motorcycle, teach self defense workshops, and am working on a startup that combines personal safety training with legal support for attack survivors.


I'm a 2022 BNMIT graduate. With a degree in Electronics and Communications Engineering.
I'm a 2022 BNMIT graduate. With a degree in Electronics and Communications Engineering.
View ResumeSoftware toolkit for remotely eavesdropping video monitors using a Software Defined Radio (SDR) receiver. It exploits compromising emanations from cables carrying video signals.
With an RTL-SDR dongle, Raspberry Pi, piece of wire and literally no other hardware it is possible to perform replay attacks on simple digital signals like those used in 433 MHz ISM band devices. This can be used for example to control wireless home automation devices like alarms, garage doors and switches.
The RTL-SDR can be used as a super cheap real time air radar. Modern planes use something called an ADS-B (Automatic Dependent Surveillance-Broadcast) Mode-S transponder, which periodically broadcasts location and altitude information to air traffic controllers.
ACARS is an acronym for Aircraft Communications Addressing and Reporting System which is a digital communications system that aircraft use to send and receive short messages to and from ground stations.
The RTL-SDR software defined radio can be used to analyze cellular phone GSM signals, using Linux based tools GR-GSM (or Airprobe) and Wireshark.
The RTL-SDR software defined radio can be used to analyze cellular phone GSM signals, using Linux based tools GR-GSM (or Airprobe) and Wireshark.
Using face recognition to open a door or control other home automation devices
A suite of WiFi/Bluetooth offensive and defensive tools for the ESP32. The tool itself serves as a portable device used to test and analyze WiFi and Bluetooth devices.
Pwnagotchi is an A2C-based AI, powered by bettercap and running on a Raspberry Pi Zero W, that learns from its surrounding Wi-Fi environment to maximize crackable WPA key material it captures, either through passive sniffing or by performing de-authentication and association attacks. This material is collected on disk as PCAP files containing any form of handshake supported by hashcat, including full and half WPA handshakes as well as PMKIDs.
TelloPOV is a rather simplistic approach to be able to launch your Tello drone & have it track your face. This approach has been tested & proven to work with the DJI Tello Drone(Non - Educational Version).
A steam bashed dishwasher that can be powered from the excess heat produced while cooking. This device is designed to be portable enough for use by street vendors in Bangalore. We were given a stipend to research and build this product at IISc Bangalore's Center for Product Design and Manufacturing.
BCP56 is a a full feature public safety platform which connects all of the information of the Police department to the dispatchers and first responders with the help of a Records management system (RMS) and then helps them to take the best course of action with the help of a Computer aided dispatch system (CAD).
Micro Aerial Attack Vehicle (MAAV) is a low cost loitering munition based on a lightweight and compact multi-rotor platform designed for DRDO:Dare to Dream Hack.
Asian Regional Space Settlement Design Competition: Wrote a comprehensive proposal for sustaining life in space, in cooperation with NASA.


ates the file cannot be modified, 'ma' off + indicates the file was modified = indicates the file is read-only =+ indicates the file is read-only and modified (path) is the path of the file being edited - VIM the server name |v:servername| or "VIM" Only works if the terminal supports setting window titles (currently Amiga console, Win32 console, all GUI versions and terminals with a non- empty 't_ts' option - these are Unix xterm and iris-ansi by default, where 't_ts' is taken from the builtin termcap). *X11* When Vim was compiled with HAVE_X11 defined, the original title will be restored if possible. The output of ":version" will include "+X11" when HAVE_X11 was defined, otherwise it will be "-X11". This also works for the icon name |'icon'|. But: When Vim was started with the |-X| argument, restoring the title will not work (except in the GUI). If the title cannot be restored, it is set to the value of 'titleold'. You might want to restore the title outside of Vim then. When using an xterm from a remote machine you can use this command: rsh machine_name xterm -display $DISPLAY & then the WINDOWID environment variable should be inherited and the title of the window should change back to what it should be after exiting Vim. *'titlelen'* 'titlelen' number (default 85) global {not in Vi} {not available when compiled without the |+title| feature} Gives the percentage of 'columns' to use for the length of the window title. When the title is longer, only the end of the path name is shown. A '<' character before the path name is used to indicate this. Using a percentage makes this adapt to the width of the window. But it won't work perfectly, because the actual number of characters available also depends on the font used and other things in the title bar. When 'titlelen' is zero the full path is used. Otherwise, values from 1 to 30000 percent can be used. 'titlelen' is also used for the 'titlestring' option. *'titleold'* 'titleold' string (default "Thanks for flying Vim") global {not in Vi} {only available when compiled with the |+title| feature} This option will be used for the window title when exiting Vim if the original title cannot be restored. Only happens if 'title' is on or 'titlestring' is not empty. This option cannot be set from a |modeline| or in the |sandbox|, for security reasons. *'titlestring'* 'titlestring' string (default "") global {not in Vi} {not available when compiled without the |+title| feature} When this option is not empty, it will be used for the title of the window. This happens only when the 'title' option is on. Only works if the terminal supports setting window titles (currently Amiga console, Win32 console, all GUI versions and terminals with a non-empty 't_ts' option). When Vim was compiled with HAVE_X11 defined, the original title will be restored if possible |X11|. When this option contains printf-style '%' items, they will be expanded according to the rules used for 'statusline'. Example: :auto BufEnter * let &titlestring = hostname() . "/" . expand("%:p") :set title titlestring=%<%F%=%l/%L-%P titlelen=70 The value of 'titlelen' is used to align items in the middle or right of the available space. Some people prefer to have the file name first: :set titlestring=%t%(\ %M%)%(\ (%{expand(\"%:~:.:h\")})%)%(\ %a%) Note the use of "%{ }" and an expression to get the path of the file, without the file name. The "%( %)" constructs are used to add a separating space only when needed. NOTE: Use of special characters in 'titlestring' may cause the display to be garbled (e.g., when it contains a CR or NL character). {not available when compiled without the |+statusline| feature} *'toolbar'* *'tb'* 'toolbar' 'tb' string (default "icons,tooltips") global {only for |+GUI_GTK|, |+GUI_Athena|, |+GUI_Motif| and YXXY+GUI_Photon|} The contents of this option controls various toolbar settings. The possible values are: icons Toolbar buttons are shown with icons. text Toolbar buttons shown with text. horiz Icon and text of a toolbar button are horizontally arranged. {only in GTK+ 2 GUI} tooltips Tooltips are active for toolbar buttons. Tooltips refer to the popup help text which appears after the mouse cursor is placed over a toolbar button for a brief moment. If you want the toolbar to be shown with icons as well as text, do the following: :set tb=icons,text Motif and Athena cannot display icons and text at the same time. They will show icons if both are requested. If none of the strings specified in 'toolbar' are valid or if 'toolbar' is empty, this option is ignored. If you want to disable the toolbar, you need to set the 'guioptions' option. For example: :set guioptions-=T Also see |gui-toolbar|. *'toolbariconsize'* *'tbis'* 'toolbariconsize' 'tbis' string (default "small") global {not in Vi} {only in the GTK+ 2 GUI} Controls the size of toolbar icons.  The exact dimensions in pixels of the various icon sizes depend on the current theme. Common dimensions are large=32x32, medium=24x24, small=20x20 and tiny=16x16. If 'toolbariconsize' is empty, the global default size as determined by user preferences or the current theme is used. *'ttybuiltin'* *'tbi'* *'nottybuiltin'* *'notbi'* 'ttybuiltin' 'tbi' boolean (default on) global {not in Vi} When on, the builtin termcaps are searched before the external ones. When off the builtin termcaps are searched after the external ones. When this option is changed, you should set the 'term' option next for the change to take effect, for example: :set notbi term=$TERM See also |termcap|. Rationale: The default for this option is "on", because the builtin termcap entries are generally better (many systems contain faulty xterm entries...). *'ttyfast'* *'tf'* *'nottyfast'* *'notf'* 'ttyfast' 'tf' boolean (default off, on when 'term' is xterm, hpterm, sun-cmd, screen, rxvt, dtterm or iris-ansi; also on when running Vim in a DOS console) global {not in Vi} Indicates a fast terminal connection. More characters will be sent to the screen for redrawing, instead of using insert/delete line commands. Improves smoothness of redrawing when there are multiple windows and the terminal does not support a scrolling region. Also enables the extra writing of characters at the end of each screen line for lines that wrap. This helps when using copy/paste with the mouse in an xterm and other terminals. *'ttymouse'* *'ttym'* 'ttymouse' 'ttym' string (default depends on 'term') global {not in Vi} {only in Unix and VMS, doesn't work in the GUI; not available when compiled without YXXY+mouse|} Name of the terminal type for which mouse codes are to be recognized. Currently these strings are valid: *xterm-mouse* xterm xterm-like mouse handling. The mouse generates "<Esc>[Mscr", where "scr" is three bytes: "s" = button state "c" = column plus 33 "r" = row plus 33 This only works up to 223 columns! See "dec" for a solution. xterm2 Works like "xterm", but with the xterm reporting the mouse position while the mouse is dragged. This works much faster and more precise. Your xterm must at least at patchlevel 88 / XFree 3.3.3 for this to work. See below for how Vim detects this automatically. *netterm-mouse* netterm NetTerm mouse handling. The mouse generates "<Esc>}r,c<CR>", where "r,c" are two decimal numbers for the row and column. *dec-mouse* dec DEC terminal mouse handling. The mouse generates a rather complex sequence, starting with "<Esc>[". This is also available for an Xterm, if it was configured with "--enable-dec-locator". *jsbterm-mouse* jsbterm JSB term mouse handling. *pterm-mouse* pterm QNX pterm mouse handling. The mouse handling must be enabled at compile time |+mouse_xterm| |+mouse_dec| |+mouse_netterm|. Only "xterm"(2) is really recognized. NetTerm mouse codes are always recognized, if enabled at compile time. DEC terminal mouse codes are recognized if enabled at compile time, and 'ttymouse' is not "xterm" (because the xterm and dec mouse codes conflict). This option is automatically set to "xterm", when the 'term' option is set to a name that starts with "xterm", and 'ttymouse' is not "xterm" or "xterm2" already. The main use of this option is to set it to "xterm", when the terminal name doesn't start with "xterm", but it can handle xterm mouse codes. The "xterm2" value will be set if the xterm version is reported to be 95 or higher. This only works when compiled with the |+termresponse| feature and if |t_RV| is set to the escape sequence to request the xterm version number. Otherwise "xterm2" must be set explicitly. If you do not want 'ttymouse' to be set to "xterm2" automatically, set t_RV to an empty string: :set t_RV= *'ttyscroll'* *'tsl'* 'ttyscroll' 'tsl' number (default 999) global Maximum number of lines to scroll the screen. If there are more lines to scroll the window is redrawn. For terminals where scrolling is very slow and redrawing is not slow this can be set to a small number, e.g., 3, to speed up displaying. *'ttytype'* *'tty'* 'ttytype' 'tty' string (default from $TERM) global Alias for 'term', see above. *'undolevels'* *'ul'* 'undolevels' 'ul' number (default 100, 1000 for Unix, VMS, Win32 and OS/2) global {not in Vi} Maximum number of changes that can be undone. Since undo information is kept in memory, higher numbers will cause more memory to be used (nevertheless, a single change can use an unlimited amount of memory). Set to 0 for Vi compatibility: One level of undo and "u" undoes itself: set ul=0 But you can also get Vi compatibility by including the 'u' flag in 'cpoptions', and still be able to use CTRL-R to repeat undo. Set to a negative number for no undo at all: set ul=-1 This helps when you run out of memory for a single change. Also see |undo-two-ways|. *'updatecount'* *'uc'* 'updatecount' 'uc' number (default: 200) global {not in Vi} After typing this many characters the swap file will be written to disk. When zero, no swap file will be created at all (see chapter on recovery |crash-recovery|). 'updatecount' is set to zero by starting Vim with the "-n" option, see |startup|. When editing in readonly mode this option will be initialized to 10000. The swapfile can be disabled per buffer with |'swapfile'|. When 'updatecount' is set from zero to non-zero, swap files are created for all buffers that have 'swapfile' set. When 'updatecount' is set to zero, existing swap files are not deleted. Also see |'swapsync'|. This option has no meaning in buffers where |'buftype'| is "nofile" or "nowrite". *'updatetime'* *'ut'* 'updatetime' 'ut' number (default 4000) global {not in Vi} If this many milliseconds nothing is typed the swap file will be written to disk (see |crash-recovery|). Also used for the |CursorHold| autocommand event. *'verbose'* *'vbs'* 'verbose' 'vbs' number (default 0) global {not in Vi, although some versions have a boolean verbose option} When bigger than zero, Vim will give messages about what it is doing. Currently, these messages are given: >= 1 When the viminfo file is read or written. >= 2 When a file is ":source"'ed. >= 5 Every searched tags file and include file. >= 8 Files for which a group of autocommands is executed. >= 9 Every executed autocommand. >= 12 Every executed function. >= 13 When an exception is thrown, caught, finished, or discarded. >= 14 Anything pending in a ":finally" clause. >= 15 Every executed Ex command (truncated at 200 characters). This option can also be set with the "-V" argument. See |-V|. This option is also set by the |:verbose| command. When the 'verbosefile' option is set then the verbose messages are not displayed. *'verbosefile'* *'vfile'* 'verbosefile' 'vfile' string (default empty) global {not in Vi} When not empty all messages are written in a file with this name. When the file exists messages are appended. Writing to the file ends when Vim exits or when 'verbosefile' is made empty. Setting 'verbosefile' to a new value is like making it empty first. The difference with |:redir| is that verbose messages are not displayed when 'verbosefile' is set. *'viewdir'* *'vdir'* 'viewdir' 'vdir' string (default for Amiga, MS-DOS, OS/2 and Win32: "$VIM/vimfiles/view", for Unix: "~/.vim/view", for Macintosh: "$VIM:vimfiles:view" for VMS: "sys$login:vimfiles/view" for RiscOS: "Choices:vimfiles/view") global {not in Vi} {not available when compiled without the +mksession feature} Name of the directory where to store files for |:mkview|. This option cannot be set from a |modeline| or in the |sandbox|, for security reasons. *'viewoptions'* *'vop'* 'viewoptions' 'vop' string (default: "folds,options,cursor") global {not in Vi} {not available when compiled without the +mksession feature} Changes the effect of the |:mkview| command. It is a comma separated list of words. Each word enables saving and restoring something: word save and restore cursor cursor position in file and in window folds manually created folds, opened/closed folds and local fold options options options and mappings local to a window or buffer (not global values for local options) slash backslashes in file names replaced with forward slashes unix with Unix end-of-line format (single <NL>), even when on Windows or DOS "slash" and "unix" are useful on Windows when sharing view files with Unix. The Unix version of Vim cannot source dos format scripts, but the Windows version of Vim can source unix format scripts. *'viminfo'* *'vi'* *E526* *E527* *E528* 'viminfo' 'vi' string (Vi default: "", Vim default for MS-DOS, Windows and OS/2: '20,<50,s10,h,rA:,rB:, for Amiga: '20,<50,s10,h,rdf0:,rdf1:,rdf2: for others: '20,<50,s10,h) global {not in Vi} {not available when compiled without the |+viminfo| feature} When non-empty, the viminfo file is read upon startup and written when exiting Vim (see |viminfo-file|). The string should be a comma separated list of parameters, each consisting of a single character identifying the particular parameter, followed by a number or string which specifies the value of that parameter. If a particular character is left out, then the default value is used for that parameter. The following is a list of the identifying characters and the effect of their value. CHAR VALUE ! When included, save and restore global variables that start with an uppercase letter, and don't contain a lowercase letter. Thus "KEEPTHIS and "K_L_M" are stored, but "KeepThis" and "_K_L_M" are not. Only String and Number types are stored. " Maximum number of lines saved for each register. Old name of the '<' item, with the disadvantage that you need to put a backslash before the ", otherwise it will be recognized as the start of a comment! % When included, save and restore the buffer list. If Vim is started with a file name argument, the buffer list is not restored. If Vim is started without a file name argument, the buffer list is restored from the viminfo file. Buffers without a file name and buffers for help files are not written to the viminfo file. When followed by a number, the number specifies the maximum number of buffers that are stored. Without a number all buffers are stored. '' Maximum number of previously edited files for which the marks are remembered. This parameter must always be included when 'viminfo' is non-empty. Including this item also means that the |jumplist| and the |changelist| are stored in the viminfo file. / Maximum number of items in the search pattern history to be saved. If non-zero, then the previous search and substitute patterns are also saved. When not included, the value of 'history' is used. : Maximum number of items in the command-line history to be saved. When not included, the value of 'history' is used. < Maximum number of lines saved for each register. If zero then registers are not saved. When not included, all lines are saved. '"'' is the old name for this item. Also see the 's' item below: limit specified in Kbyte. @ Maximum number of items in the input-line history to be saved. When not included, the value of 'history' is used. c When included, convert the text in the viminfo file from the 'encoding' used when writing the file to the current 'encoding'. See |viminfo-encoding|. f Whether file marks need to be stored. If zero, file marks ('0 to '9, 'A to 'Z) are not stored. When not present or when non-zero, they are all stored. '0 is used for the current cursor position (when exiting or when doing ":wviminfo"). h Disable the effect of 'hlsearch' when loading the viminfo file. When not included, it depends on whether ":nohlsearch" has been used since the last search command. n Name of the viminfo file. The name must immediately follow the 'n'. Must be the last one! If the "-i" argument was given when starting Vim, that file name overrides the one given here with 'viminfo'. Environment variables are expanded when opening the file, not when setting the option. r Removable media. The argument is a string (up to the next ','). This parameter can be given several times. Each specifies the start of a path for which no marks will be stored. This is to avoid removable media. For MS-DOS you could use "ra:,rb:", for Amiga "rdf0:,rdf1:,rdf2:". You can also use it for temp files, e.g., for Unix: "r/tmp". Case is ignored. Maximum length of each 'r' argument is 50 characters. s Maximum size of an item in Kbyte. If zero then registers are not saved. Currently only applies to registers. The default "s10" will exclude registers with more than 10 Kbyte of text. Also see the '<' item above: line count limit. Example: :set viminfo='50,<1000,s100,:0,n~/vim/viminfo '50 Marks will be remembered for the last 50 files you edited. <1000 Contents of registers (up to 1000 lines each) will be remembered. s100 Registers with more than 100 Kbyte text are skipped. :0 Command-line history will not be saved. n~/vim/viminfo The name of the file to use is "~/vim/viminfo". no / Since '/' is not specified, the default will be used, that is, save all of the search history, and also the previous search and substitute patterns. no % The buffer list will not be saved nor read back. no h 'hlsearch' highlighting will be restored. When setting 'viminfo' from an empty value you can use |:rviminfo| to load the contents of the file, this is not done automatically. This option cannot be set from a |modeline| or in the |sandbox|, for security reasons. *'virtualedit'* *'ve'* 'virtualedit' 've' string (default "") global {not in Vi} {not available when compiled without the |+virtualedit| feature} A comma separated list of these words: block Allow virtual editing in Visual block mode. insert Allow virtual editing in Insert mode. all Allow virtual editing in all modes. onemore Allow the cursor to move just past the end of the line Virtual editing means that the cursor can be positioned where there is no actual character. This can be halfway into a tab or beyond the end of the line. Useful for selecting a rectangle in Visual mode and editing a table. "onemore" is not the same, it will only allow moving the cursor just after the last character of the line. This makes some commands more consistent. Previously the cursor was always past the end of the line if the line was empty. But it is far from Vi compatible. It may also break some plugins or Vim scripts. For example because |l| can move the cursor after the last character. Use with care! Using the |$| command will move to the last character in the line, not past it. This may actually move the cursor to the left! It doesn't make sense to combine "all" with "onemore", but you will not get a warning for it. *'visualbell'* *'vb'* *'novisualbell'* *'novb'* *beep* 'visualbell' 'vb' boolean (default off) global {not in Vi} Use visual bell instead of beeping. The terminal code to display the visual bell is given with 't_vb'. When no beep or flash is wanted, use ":set vb t_vb=". Note: When the GUI starts, 't_vb' is reset to its default value. You might want to set it again in your |gvimrc|. In the GUI, 't_vb' defaults to "<Esc>|f", which inverts the display for 20 msec. If you want to use a different time, use "<Esc>|40f", where 40 is the time in msec. Does not work on the Amiga, you always get a screen flash. Also see 'errorbells'. *'warn'* *'nowarn'* 'warn' boolean (default on) global Give a warning message when a shell command is used while the buffer has been changed. *'weirdinvert'* *'wiv'* *'noweirdinvert'* *'nowiv'* 'weirdinvert' 'wiv' boolean (default off) global {not in Vi} This option has the same effect as the 't_xs' terminal option. It is provided for backwards compatibility with version 4.x. Setting 'weirdinvert' has the effect of making 't_xs' non-empty, and vice versa. Has no effect when the GUI is running. *'whichwrap'* *'ww'* 'whichwrap' 'ww' string (Vim default: "b,s", Vi default: "") global {not in Vi} Allow specified keys that move the cursor left/right to move to the previous/next line when the cursor is on the first/last character in the line. Concatenate characters to allow this for these keys: char key mode b <BS> Normal and Visual s <Space> Normal and Visual h "h" Normal and Visual (not recommended) l "l" Normal and Visual (not recommended) < <Left> Normal and Visual > <Right> Normal and Visual ~ "~" Normal [ <Left> Insert and Replace ] <Right> Insert and Replace For example: :set ww=<,>,[,] allows wrap only when cursor keys are used. When the movement keys are used in combination with a delete or change operator, the <EOL> also counts for a character. This makes "3h" different from "3dh" when the cursor crosses the end of a line. This is also true for "x" and "X", because they do the same as "dl" and "dh". If you use this, you may also want to use the mapping ":map <BS> X" to make backspace delete the character in front of the cursor. When 'l' is included and it is used after an operator at the end of a line then it will not move to the next line. This makes "dl", "cl", "yl" etc. work normally. NOTE: This option is set to the Vi default value when 'compatible' is set and to the Vim default value when 'compatible' is reset. *'wildchar'* *'wc'* 'wildchar' 'wc' number (Vim default: <Tab>, Vi default: CTRL-E) global {not in Vi} Character you have to type to start wildcard expansion in the command-line, as specified with 'wildmode'. More info here: |cmdline-completion|. The character is not recognized when used inside a macro. See 'wildcharm' for that. Although 'wc' is a number option, you can set it to a special key: :set wc=<Esc> NOTE: This option is set to the Vi default value when 'compatible' is set and to the Vim default value when 'compatible' is reset. *'wildcharm'* *'wcm'* 'wildcharm' 'wcm' number (default: none (0)) global {not in Vi} 'wildcharm' works exactly like 'wildchar', except that it is recognized when used inside a macro. You can find "spare" command-line keys suitable for this option by looking at |ex-edit-index|. Normally you'll never actually type 'wildcharm', just use it in mappings that automatically invoke completion mode, e.g.: :set wcm=<C-Z> :cnoremap ss so $vim/sessions/*.vim<C-Z> Then after typing :ss you can use CTRL-P & CTRL-N. *'wildignore'* *'wig'* 'wildignore' 'wig' string (default "") global {not in Vi} {not available when compiled without the |+wildignore| feature} A list of file patterns. A file that matches with one of these patterns is ignored when completing file or directory names, and influences the result of |expand()|, |glob()| and |globpath()| unless a flag is passed to disable this. The pattern is used like with |:autocmd|, see |autocmd-patterns|. Also see 'suffixes'. Example: :set wildignore=*.o,*.obj The use of |:set+=| and |:set-=| is preferred when adding or removing a pattern from the list. This avoids problems when a future version uses another default. *'wildmenu'* *'wmnu'* *'nowildmenu'* *'nowmnu'* 'wildmenu' 'wmnu' boolean (default off) global {not in Vi} {not available if compiled without the |+wildmenu| feature} When 'wildmenu' is on, command-line completion operates in an enhanced mode. On pressing 'wildchar' (usually <Tab>) to invoke completion, the possible matches are shown just above the command line, with the first match highlighted (overwriting the status line, if there is one). Keys that show the previous/next match, such as <Tab> or CTRL-P/CTRL-N, cause the highlight to move to the appropriate match. When 'wildmode' is used, "wildmenu" mode is used where "full" is specified. "longest" and "list" do not start "wildmenu" mode. If there are more matches than can fit in the line, a ">" is shown on the right and/or a "<" is shown on the left. The status line scrolls as needed. The "wildmenu" mode is abandoned when a key is hit that is not used for selecting a completion. While the "wildmenu" is active the following keys have special meanings: <Left> <Right> - select previous/next match (like CTRL-P/CTRL-N) <Down> - in filename/menu name completion: move into a subdirectory or submenu. <CR> - in menu completion, when the cursor is just after a dot: move into a submenu. <Up> - in filename/menu name completion: move up into parent directory or parent menu. This makes the menus accessible from the console |console-menus|. If you prefer the <Left> and <Right> keys to move the cursor instead of selecting a different match, use this: :cnoremap <Left> <Space><BS><Left> :cnoremap <Right> <Space><BS><Right> The "WildMenu" highlighting is used for displaying the current match |hl-WildMenu|. *'wildmode'* *'wim'* 'wildmode' 'wim' string (Vim default: "full") global {not in Vi} Completion mode that is used for the character specified with 'wildchar'. It is a comma separated list of up to four parts. Each part specifies what to do for each consecutive use of 'wildchar'. The first part specifies the behavior for the first use of 'wildchar', The second part for the second use, etc. These are the possible values for each part: "" Complete only the first match. "full" Complete the next full match. After the last match, the original string is used and then the first match again. "longest" Complete till longest common string. If this doesn't result in a longer string, use the next part. "longest:full" Like "longest", but also start 'wildmenu' if it is enabled. "list" When more than one match, list all matches. "list:full" When more than one match, list all matches and complete first match. "list:longest" When more than one match, list all matches and complete till longest common string. When there is only a single match, it is fully completed in all cases. Examples: :set wildmode=full Complete first full match, next match, etc. (the default) :set wildmode=longest,full Complete longest common string, then each full match :set wildmode=list:full List all matches and complete each full match :set wildmode=list,full List all matches without completing, then each full match :set wildmode=longest,list Complete longest common string, then list alternatives. More info here: |cmdline-completion|. *'wildoptions'* *'wop'* 'wildoptions' 'wop' string (default "") global {not in Vi} {not available when compiled without the |+wildignore| feature} A list of words that change how command line completion is done. Currently only one word is allowed: tagfile When using CTRL-D to list matching tags, the kind of tag and the file of the tag is listed. Only one match is displayed per line. Often used tag kinds are: d #define f function Also see |cmdline-completion|. *'winaltkeys'* *'wak'* 'winaltkeys' 'wak' string (default "menu") global {not in Vi} {only used in Win32, Motif, GTK and Photon GUI} Some GUI versions allow the access to menu entries by using the ALT key in combination with a character that appears underlined in the menu. This conflicts with the use of the ALT key for mappings and entering special characters. This option tells what to do: no Don't use ALT keys for menus. ALT key combinations can be mapped, but there is no automatic handling. This can then be done with the |:simalt| command. yes ALT key handling is done by the windowing system. ALT key combinations cannot be mapped. menu Using ALT in combination with a character that is a menu shortcut key, will be handled by the windowing system. Other keys can be mapped. If the menu is disabled by excluding 'm' from 'guioptions', the ALT key is never used for the menu. This option is not used for <F10>; on Win32 and with GTK <F10> will select the menu, unless it has been mapped. *'window'* *'wi'* 'window' 'wi' number (default screen height - 1) global Window height. Do not confuse this with the height of the Vim window, use 'lines' for that. Used for |CTRL-F| and |CTRL-B| when there is only one window and the value is smaller than 'lines' minus one. The screen will scroll 'window' minus two lines, with a minimum of one. When 'window' is equal to 'lines' minus one CTRL-F and CTRL-B scroll in a much smarter way, taking care of wrapping lines. When resizing the Vim window, the value is smaller than 1 or more than or equal to 'lines' it will be set to 'lines' minus 1. {Vi also uses the option to specify the number of displayed lines} *'winheight'* *'wh'* *E591* 'winheight' 'wh' number (default 1) global {not in Vi} {not available when compiled without the +windows feature} Minimal number of lines for the current window. This is not a hard minimum, Vim will use fewer lines if there is not enough room. If the focus goes to a window that is smaller, its size is increased, at the cost of the height of other windows. Set 'winheight' to a small number for normal editing. Set it to 999 to make the current window fill most of the screen. Other windows will be only 'winminheight' high. This has the drawback that ":all" will create only two windows. To avoid "vim -o 1 2 3 4" to create only two windows, set the option after startup is done, using the |VimEnter| event: au VimEnter * set winheight=999 Minimum value is 1. The height is not adjusted after one of the commands that change the height of the current window. 'winheight' applies to the current window. Use 'winminheight' to set the minimal height for other windows. *'winfixheight'* *'wfh'* *'nowinfixheight'* *'nowfh'* 'winfixheight' 'wfh' boolean (default off) local to window {not in Vi} {not available when compiled without the +windows feature} Keep the window height when windows are opened or closed and 'equalalways' is set. Also for |CTRL-W_=|. Set by default for the |preview-window| and |quickfix-window|. The height may be changed anyway when running out of room. *'winfixwidth'* *'wfw'* *'nowinfixwidth'* *'nowfw'* 'winfixwidth' 'wfw' boolean (default off) local to window {not in Vi} {not available when compiled without the +windows feature} Keep the window width when windows are opened or closed and 'equalalways' is set. Also for |CTRL-W_=|. The width may be changed anyway when running out of room. *'winminheight'* *'wmh'* 'winminheight' 'wmh' number (default 1) global {not in Vi} {not available when compiled without the +windows feature} The minimal height of a window, when it's not the current window. This is a hard minimum, windows will never become smaller. When set to zero, windows may be "squashed" to zero lines (i.e. just a status bar) if necessary. They will return to at least one line when they become active (since the cursor has to have somewhere to go.) Use 'winheight' to set the minimal height of the current window. This option is only checked when making a window smaller. Don't use a large number, it will cause errors when opening more than a few windows. A value of 0 to 3 is reasonable. *'winminwidth'* *'wmw'* 'winminwidth' 'wmw' number (default 1) global {not in Vi} {not available when compiled without the +vertsplit feature} The minimal width of a window, when it's not the current window. This is a hard minimum, windows will never become smaller. When set to zero, windows may be "squashed" to zero columns (i.e. just a vertical separator) if necessary. They will return to at least one line when they become active (since the cursor has to have somewhere to go.) Use 'winwidth' to set the minimal width of the current window. This option is only checked when making a window smaller. Don't use a large number, it will cause errors when opening more than a few windows. A value of 0 to 12 is reasonable. *'winwidth'* *'wiw'* *E592* 'winwidth' 'wiw' number (default 20) global {not in Vi} {not available when compiled without the +vertsplit feature} Minimal number of columns for the current window. This is not a hard minimum, Vim will use fewer columns if there is not enough room. If the current window is smaller, its size is increased, at the cost of the width of other windows. Set it to 999 to make the current window always fill the screen. Set it to a small number for normal editing. The width is not adjusted after one of the commands to change the width of the current window. 'winwidth' applies to the current window. Use 'winminwidth' to set the minimal width for other windows. *'wrap'* *'nowrap'* 'wrap' boolean (default on) local to window {not in Vi} This option changes how text is displayed. It doesn't change the text in the buffer, see 'textwidth' for that. When on, lines longer than the width of the window will wrap and displaying continues on the next line. When off lines will not wrap and only part of long lines will be displayed. When the cursor is moved to a part that is not shown, the screen will scroll horizontally. The line will be broken in the middle of a word if necessary. See 'linebreak' to get the break at a word boundary. To make scrolling horizontally a bit more useful, try this: :set sidescroll=5 :set listchars+=precedes:<,extends:> See 'sidescroll', 'listchars' and |wrap-off|. *'wrapmargin'* *'wm'* 'wrapmargin' 'wm' number (default 0) local to buffer Number of characters from the right window border where wrapping starts. When typing text beyond this limit, an <EOL> will be inserted and inserting continues on the next line. Options that add a margin, such as 'number' and 'foldcolumn', cause the text width to be further reduced. This is Vi compatible. When 'textwidth' is non-zero, this option is not used. See also 'formatoptions' and |ins-textwidth|. {Vi: works differently and less usefully} *'wrapscan'* *'ws'* *'nowrapscan'* *'nows'* 'wrapscan' 'ws' boolean (default on) *E384* *E385* global Searches wrap around the end of the file. Also applies to |]s| and |[s|, searching for spelling mistakes. *'write'* *'nowrite'* 'write' boolean (default on) global {not in Vi} Allows writing files. When not set, writing a file is not allowed. Can be used for a view-only mode, where modifications to the text are still allowed. Can be reset with the |-m| or |-M| command line argument. Filtering text is still possible, even though this requires writing a temporary file. *'writeany'* *'wa'* *'nowriteany'* *'nowa'* 'writeany' 'wa' boolean (default off) global Allows writing to any file with no need for "!" override. *'writebackup'* *'wb'* *'nowritebackup'* *'nowb'* 'writebackup' 'wb' boolean (default on with |+writebackup| feature, off otherwise) global {not in Vi} Make a backup before overwriting a file. The backup is removed after the file was successfully written, unless the 'backup' option is also on. Reset this option if your file system is almost full. See |backup-table| for another explanation. When the 'backupskip' pattern matches, a backup is not made anyway. NOTE: This option is set to the default value when 'compatible' is set. *'writedelay'* *'wd'* 'writedelay' 'wd' number (default 0) global {not in Vi} The number of microseconds to wait for each character sent to the screen. When non-zero, characters are sent to the terminal one by one. For MS-DOS pcterm this does not work. For debugging purposes. top - main help file


PostgreSQL authentication¶
Client authentication determines which users are allowed to view published databases. By default, the GEE Server does not require authentication for user access. However, you can configure authentication for your server.
If you use a load-balanced grid of GEE servers, a single common authentication source (such as PostgreSQL or LDAP) makes user administration easier. When you add users, you can add them to a single database instead of to each virtual server.
Authentication encrypts passwords before transmitting and storing them. Besides the security benefits, there are performance benefits to encrypting passwords instead of storing them in plaintext. As a plaintext password file grows to more than 200 users, there will likely be a noticeable slowdown. This is because the entire password file is read into memory each time the virtual server is accessed to search for a password.
If you have a PostgreSQL database, you can use standard Apache authentication methods such as Digest authentication to control user access. This is useful if you already store user passwords in a PostgreSQL table, or if you want to use a unified authentication mechanism other than LDAP for your GEE Server and other systems.
Before you begin
- Do not use the PostgreSQL database that ships with GEE. Instead, install PostgreSQL on a separate port or a different host.
- You must set up client authentication for each virtual server you want to use authentication with.
Apache modules
The Apache configuration below uses these modules:
- The
mod_authn_dbd
module provides the authentication back-end with a PostgreSQL server. For more information about the module, see the mod_authn_dbd section in the Apache documentation. - The
mod_auth_digest
module is used for Digest authentication. For more information aboutmod_auth_digest
, see the mod_auth_digest section in the Apache documentation.
Terms
In the steps below, you can replace these names with the names you want to use. For example, you can replace geeauthdb with the name of your database.
geeauthdb
. The database to connect to.geepasswd
. The table that stores user information.geeuser
. The user login to connect to the database.postgres
. The default PostgreSQL adminstrator user on Ubuntu.
To configure client authentication for PostgreSQL:
Connect to the PostgreSQL server:
sudo su - postgres psql --port=5433
Create the database and user:
CREATE USER geeuser WITH PASSWORD 'geeuserpasswd'; CREATE DATABASE geeauthdb; GRANT ALL PRIVILEGES ON DATABASE geeauthdb to mypguser; \q
Create a table to store the passwords:
psql --port=5433 --username=geeuser geauthdb CREATE TABLE geepasswd (username varchar(32) NOT NULL, realm varchar(255) NOT NULL, passwd varchar(255) NOT NULL, realname varchar(255), PRIMARY KEY (username, realm)); \q
The table includes these fields:
username
.realm
.password
.realname
. Optional. The realname field does not require a value, but is included in case you want to use it. You can also add other optional fields if needed.
Create the encrypted password by inserting encyption functions into the database with the
pgcrypto
contributed module:psql --port=5433 --username=geeuser geauthdb < /usr/share/postgresql/8.4/contrib/pgcrypto.sql
Note: You can substitute a different method for this step. The Password Formats section in the Apache documentation gives examples in multiple programming languages for encrypting the password so that it is readable by Apache.
Make sure the database works by inserting a test user:
psql --port=5433 --username=geeuser geauthdb INSERT INTO geepasswd VALUES ('jsmith', 'realm', encode(digest( 'jsmith' || ':' || 'realm' || ':' ||'password', 'md5'), 'hex'), 'Jane Smith'); \q
Replace “jsmith”, “realm”, “password” and “Jane Smith” with the values you want to use.
Note: The password is hashed with MD5 because the Apache
mod_authn_dbd
module requires it. This also prevents the password from appearing in plaintext.Create a file named
pgsql-auth.conf
at/opt/google/gehttpd/conf/extra/pgsql-auth.conf
.Add these lines to the
pgsql-auth.conf
file:``DBDriver pgsql`` ``DBDParams "hostaddr=yourpgserver port=yourport user=geuser password=yourpassword dbname=gee_auth"`` ``DBDMin 4`` ``DBDKeep 8`` ``DBDMax 20`` ``DBDExptime 300``
Replace
yourpgserver
andyourport
with the address or hostname of your PostgreSQL database. Replacegeuser
andyourpassword
with the username and password of your test user.Open the
/opt/google/gehttpd/conf/gehttpd.conf
file and insert the line:Include /opt/google/gehttpd/conf/extra/pgsql-auth.conf
above the line:
Include conf.d/*.conf
The result is:
# Include Google Earth Server-specific files Include /opt/google/gehttpd/conf/extra/pgsql-auth.conf Include conf.d/*.conf
Add the following lines at the beginning of the
<Location>
directive of your virtual server:AuthType Digest AuthName "realm" AuthDigestDomain '/default_map/' AuthDigestProvider dbd AuthDBDUserRealmQuery "SELECT passwd FROM geeauth WHERE username = %s and realm = %s" BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
If this is a
_ge_ virtual
server, add:BrowserMatch "GoogleEarth" AuthDigestEnableQueryStringHack=On
If this is a
_map_ virtual
server, add:BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
For more information about
AuthDigestEnableQueryStringHack
, see the mod_auth_digest section in the Apache documentation.The final
<Location>
directive looks like:<Location "/default_map/*"> AuthType Digest AuthName "realm" AuthDigestDomain '/default_map/' AuthDigestProvider dbd AuthDBDUserRealmQuery "SELECT passwd FROM geeauth WHERE username = %s and realm = %s" BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On Require valid-user SetHandler gedb-handler Include conf.d/virtual_servers/runtime/default_map_runtime </Location>
Save and close the virtual server configuration file.
Restart the server:
/etc/init.d/geserver restart
After you verify the configuration with your test user, you can add your users to the database.


15 August 2001
Disease Outbreak Reported
Since the third week of May, 77 cases and 17 deaths (case-fatality rate of 22%) have been reported to WHO in the Balombo district of Angola. Neisseria meningitidis serogroup A has been laboratory confirmed. The epidemic threshold of 15 cases per 100 000 population per week has been exceeded in the affected district and the cumulative attack rate is 212 per 100 000 population since the beginning of the year. Data from other districts is unavailable at the present time.
On 13 August, a mass vaccination campaign was launched targeting the population of Balombo district over 2 years of age. Médecins sans Frontières is supporting the mass vaccination campaign and has provided vaccines, autodestruct syringes and oily chloramphenical for case management.


Portfolio page coming soon. In the meantime, please feel free to contact me if you would like to see a specific part of my portfolio, which I can send to you by email.
You can also find a full list of my publications here and a full list of my work in the news here.


Home
A GAE/J project template for JSF based applications.
This is a simple starter template to help you get started with deploying a JSF based application on top of
Google's AppEngine.
You can find the source for this template on GitHub.
Key points about this bare bones starter template:
- Configured with JSF 2.2 & JPA 2 & CDI & PrimeFaces.
- Basic code for supporting serialization, session cleanup and stuff that I keep blogging about.
- Uses Gradle as its build system (including downloading & running the GAE/J server itself).
- Uses bootstrap for page templating.


B.Tech. III (CO) Semester – 5 |
L |
T |
P |
C |
CO305 : PRINCIPLE OF PROGRAMMING LANGUAGES (CS-III) |
3 |
1 |
2 |
5 |
(14 Hours) |
||||
Introduction to Prolog, Prolog Programs Models, Types Of Logic, WFF, Symbolic Logic, Facts, Clauses, Predicates, Unification, Backtracking, Cut, Fail & Built-In Predicates, Recursion in Prolog, Arithmetic Operators & Relational Operators ,LIST Processing, String manipulation & Built-In Predicates, Compound objects, Dynamic Database. |
||||
(15 Hours) |
||||
Introduction to Object Oriented Programming, Token, Expression & control Structure, Classes & Objects, Constructors & Destructors, Operator Overloading & Type Conversion, Inheritance, Pointers, Virtual Functions and Polymorphism, I/O Operations, Working With Files. |
||||
(13 Hours) |
||||
Why Study Programming Language?, A History Of Programming Language, Role Of programming Language, Programming Environments ; Implicit and Explicit Sequence Control, Sequencing with Arithmetic Expressions, Sequence Control between Statements ; Subprogram Sequence Control Attributes of Control, Parameter Transmission ; Storage Management. |
||||
(14 Hours) |
||||
(Total Contact Time: 42 Hours + 14 Hours = 56 Hours) |
||||
PRACTICALS |
||||
1). Implement Prolog Programs for Recursion, Arithmetic Operators & Relational Operator. |
||||
BOOKS RECOMMENDED |
||||
1). Bjarne Stroustrup, ”The C++ Programming Language”, Addison-Wesley Professional, 3/E 2000 |


I'm trying to figure out the costumes for Hamlet. I ask Bill to mark up the script with style suggestions.
When I get the script back, it's a hundred times longer. The content isn't any different — every time a character speaks a line, Bill writes what they're wearing. For example:
BERNARDO (Wearing armor and carrying a spear) Who's there? FRANCISCO (Wearing armor and carrying a spear) Nay, answer me: stand, and unfold yourself. BERNARDO (Wearing armor and carrying a spear) Long live the king!
I write back, Hey, Bill, think you could just write on a different piece of paper what the costumes should be for each type of person?
The next version of the script is back to normal length, with all the costume suggestions listed on a separate page: Each guard wears armor and carries a spear.
Styling is figuring out how you want elements to look. For example, you'd probably want a header to stand out from whatever it introduces, so you might just underline it, or you might make its font huge and orange and bold or something.


{# --- Inherit non-display elements from the common directory to avoid duplication --- #} {% partial "layout/common/head/default" %} {% partial "layout/clean/head/styles" %}


Cartoons Lou used to watch...
More clues
Movies Lou used to watch...
More clues
Now here are some shots of Lou so you can make a guess:
Click the right one for a video of Lou
17-20
21-24
25-29
30-34
35-39


Class: Aws::OpsWorks::Types::UpdateLayerRequest
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | (unknown) |
Overview
When passing UpdateLayerRequest as input to an Aws::Client method, you can use a vanilla Hash:
{
layer_id: "String", # required
name: "String",
shortname: "String",
attributes: {
"EcsClusterArn" => "String",
},
custom_instance_profile_arn: "String",
custom_json: "String",
custom_security_group_ids: ["String"],
packages: ["String"],
volume_configurations: [
{
mount_point: "String", # required
raid_level: 1,
number_of_disks: 1, # required
size: 1, # required
volume_type: "String",
iops: 1,
},
],
enable_auto_healing: false,
auto_assign_elastic_ips: false,
auto_assign_public_ips: false,
custom_recipes: {
setup: ["String"],
configure: ["String"],
deploy: ["String"],
undeploy: ["String"],
shutdown: ["String"],
},
install_updates_on_boot: false,
use_ebs_optimized_instances: false,
lifecycle_event_configuration: {
shutdown: {
execution_timeout: 1,
delay_until_elb_connections_drained: false,
},
},
}
Instance Attribute Summary
-
#attributes ⇒ Hash<String,String>
rw
One or more user-defined key/value pairs to be added to the stack attributes.
. -
#auto_assign_elastic_ips ⇒ Boolean
rw
Whether to automatically assign an Elastic IP address to the layer's instances.
-
#auto_assign_public_ips ⇒ Boolean
rw
For stacks that are running in a VPC, whether to automatically assign a public IP address to the layer's instances.
-
#custom_instance_profile_arn ⇒ String
rw
The ARN of an IAM profile to be used for all of the layer's EC2 instances.
-
#custom_json ⇒ String
rw
A JSON-formatted string containing custom stack configuration and deployment attributes to be installed on the layer's instances.
-
#custom_recipes ⇒ Types::Recipes
rw
A
.LayerCustomRecipes
object that specifies the layer's custom recipes. -
#custom_security_group_ids ⇒ Array<String>
rw
An array containing the layer's custom security group IDs.
. -
#enable_auto_healing ⇒ Boolean
rw
Whether to disable auto healing for the layer.
. -
#install_updates_on_boot ⇒ Boolean
rw
Whether to install operating system and package updates when the instance boots.
-
#layer_id ⇒ String
rw
The layer ID.
. -
#lifecycle_event_configuration ⇒ Types::LifecycleEventConfiguration
rw
.
-
#name ⇒ String
rw
The layer name, which is used by the console.
. -
#packages ⇒ Array<String>
rw
An array of
.Package
objects that describe the layer's packages. -
#shortname ⇒ String
rw
For custom layers only, use this parameter to specify the layer's short name, which is used internally by AWS OpsWorksand by Chef.
-
#use_ebs_optimized_instances ⇒ Boolean
rw
Whether to use Amazon EBS-optimized instances.
. -
#volume_configurations ⇒ Array<Types::VolumeConfiguration>
rw
A
.VolumeConfigurations
object that describes the layer's Amazon EBS volumes.
Instance Attribute Details
#attributes ⇒ Hash
<String
,String
> (rw)
One or more user-defined key/value pairs to be added to the stack attributes.
#auto_assign_elastic_ips ⇒ Boolean
(rw)
Whether to automatically assign an Elastic IP address to the layer's instances. For more information, see How to Edit a Layer.
#auto_assign_public_ips ⇒ Boolean
(rw)
For stacks that are running in a VPC, whether to automatically assign a public IP address to the layer's instances. For more information, see How to Edit a Layer.
#custom_instance_profile_arn ⇒ String
(rw)
The ARN of an IAM profile to be used for all of the layer's EC2 instances. For more information about IAM ARNs, see Using Identifiers.
#custom_json ⇒ String
(rw)
A JSON-formatted string containing custom stack configuration and deployment attributes to be installed on the layer's instances. For more information, see Using Custom JSON.
#custom_recipes ⇒ Types::Recipes (rw)
A LayerCustomRecipes
object that specifies the layer's custom recipes.
#custom_security_group_ids ⇒ Array
<String
> (rw)
An array containing the layer's custom security group IDs.
#enable_auto_healing ⇒ Boolean
(rw)
Whether to disable auto healing for the layer.
#install_updates_on_boot ⇒ Boolean
(rw)
Whether to install operating system and package updates when the instance boots. The default value is true
. To control when updates are installed, set this value to false
. You must then update your instances manually by using CreateDeployment to run the update_dependencies
stack command or manually running yum
(Amazon Linux) or apt-get
(Ubuntu) on the instances.
We strongly recommend using the default value of true
, to ensure that your instances have the latest security updates.
#layer_id ⇒ String
(rw)
The layer ID.
#lifecycle_event_configuration ⇒ Types::LifecycleEventConfiguration (rw)
#name ⇒ String
(rw)
The layer name, which is used by the console.
#packages ⇒ Array
<String
> (rw)
An array of Package
objects that describe the layer's packages.
#shortname ⇒ String
(rw)
For custom layers only, use this parameter to specify the layer's short name, which is used internally by AWS OpsWorksand by Chef. The short name is also used as the name for the directory where your app files are installed. It can have a maximum of 200 characters and must be in the following format: /\A[a-z0-9\-\_\.]+\Z/.
The built-in layers' short names are defined by AWS OpsWorks. For more information, see the Layer Reference
#use_ebs_optimized_instances ⇒ Boolean
(rw)
Whether to use Amazon EBS-optimized instances.
#volume_configurations ⇒ Array
<Types::VolumeConfiguration> (rw)
A VolumeConfigurations
object that describes the layer's Amazon EBS volumes.


mvinfluence: Influence Measures and Diagnostic Plots for Multivariate Linear
Models
Computes regression deletion diagnostics for multivariate linear models and provides some associated
diagnostic plots. The diagnostic measures include hat-values (leverages), generalized Cook's distance, and
generalized squared 'studentized' residuals. Several types of plots to detect influential observations are
provided.
Downloads:
Reverse dependencies:
Linking:
Please use the canonical form
https://CRAN.R-project.org/package=mvinfluence
to link to this page.


|
TFKaldi
|
a class for the monophone GMM More...
Public Member Functions | |
| def | name (self) |
| def | trainscript (self) |
| def | conf_file (self) |
| def | parent_gmm_alignments (self) |
| def | trainops (self) |
| def | graphopts (self) |
| Public Member Functions inherited from kaldi.gmm.GMM | |
| def | __init__ (self, conf) |
| KaldiGMM constructor. More... | |
| def | train (self) |
| train the GMM | |
| def | align (self) |
| use the GMM to align the training utterances | |
| def | test (self) |
| test the GMM on the testing set | |
| def | name (self) |
| the name of the GMM | |
| def | trainscript (self) |
| the script used for training the GMM | |
| def | conf_file (self) |
| the configuration file for this GMM | |
| def | parent_gmm_alignments (self) |
| the path to the parent GMM model (empty for monophone GMM) | |
| def | trainops (self) |
| the extra options for GMM training | |
| def | graphopts (self) |
| the extra options for the decoding graph creation | |
Additional Inherited Members | |
| Public Attributes inherited from kaldi.gmm.GMM | |
| conf | |
a class for the monophone GMM


Arrival Time Demo App
Edit Parameters
Tap any Cell to Edit
Location
A
Location
B
Location
C
Start Time
Cycle Length
Arrival Open
Arrival Close


Default bar sparkline and another version of the same with the step set to 5.
Bar sparkline with an offwhite background color and another version of the same with the step set to 5 and the minMarker turned off.


{% extends "site_base.html" %} {% load i18n %} {% block title %}Welcome{% endblock %} {% block tab_id %}id="home_tab"{% endblock %} {% block base_content %}
Welcome to Django-schedule's example site. Congratulations, if you're reading this then you've taken the necessary steps to successfully setup an example site! Now poke around and kick the tires!
{% endblocktrans %}