booz-allen-hamilton
Businessmodel of Booz Allen Hamilton
Customer Segments
Booz Allen Hamilton provides a broad range of management and technology, consulting, and engineering services to institutional and corporate clients. The Company’s clients can be organized into three principal categories:
- Government Bodies, including local, state, and federal government agencies in the US, as well as various international government bodies;
- Corporations, primarily companies operating in the financial services, healthcare and life sciences, energy, high-tech manufacturing, retail, and automotive industries; and
- Non-Profits, including various non-profit and charitable organisations across the world. Over the past year, the majority of Booz Allen Hamilton’s revenue was derived from contracts where the end client was an agency or department of the US Government. The Company supports critical missions for a diverse base of federal government clients, including nearly all of the US Government’s cabinet-level departments, and federal contract vehicles. In the fiscal year 2016, the Company’s largest client was the US Army, which accounted for approximately 15% of the Company’s revenue. The Company also counts the US Navy, US Air Force, Federal Bureau of Investigations, National Security Agency, and the Department of Energy among its longstanding clients.
The US continues to be Booz Allen Hamilton’s principal market. The Company’s international clients are primarily based in the Middle East, with the Company also serving a growing presence in Southeast Asia.
Value Propositions
Booz Allen Hamilton provides value to its clients in the following ways:
- Its reputation and industry standing, with the Company established as one of the largest and most well-regarded providers of management and technology, consulting, and engineering services, as is demonstrated by its ability to attract significant business from numerous US Government agencies, including several branches of the US military;
- Its broad portfolio of products and services, with the Company providing a broad portfolio of management and technology, consulting, and engineering services to institutional, commercial, and non-profit clients, including cyber security, IT strategy, and systems delivery solutions;
- Its personalised service delivery, with the Company working closely with its clients over an extended period of time, providing services and solutions that are tailored to the individual needs of each client;
- Its international reach, with the Company serving an international client base across the Middle East and Southeast Asia, in addition to its extensive domestic client base in the US. ### Channels
Booz Allen Hamilton operates a website at www.boozallen.com, through which it provides information on its various services, solutions, locations, and target industries. The nature of the Company’s tailored consulting services does not lend itself to the operation of an online sales, self-service sales channel. The Company also does not operate an online customer portal.
Booz Allen Hamilton makes sales and provides its various services through its dedicated consulting and service personnel, who are organised principally by service line, with separate units covering the Company’s management consulting, technology, engineering, strategic innovation, and product-related services. These employees operate primarily out of the Company’s international network of offices, including numerous locations across 32 US states – and Washington DC – as well as in the United Arab Emirates, Saudi Arabia, Egypt, South Korea, Russia, Indonesia, and Singapore.
Booz Allen Hamilton also operates a number of so-called Sensitive Compartmented Information Facilities, which are enclosed areas within buildings that are used to perform classified work for the US Intelligence Community. A number of the Company’s employees also operate out of facilities provided by the US Government.
Customer Relationships
Booz Allen Hamilton does not provide services to its customers on a self-service basis, nor does it provide an online customer portal through which customers can independently manage their services.
Booz Allen Hamilton provides tailored services to its institutional, commercial, and non-profit clients. The Company’s consultants work closely with clients on an ongoing basis, seeking to deliver personalised services and solutions, and establish longstanding business relationships. Booz Allen Hamilton has already established long-running relationships with a number of government agencies, including relationships spanning more than 65 years with the US Army and the US Navy.
Booz Allen Hamilton provides ongoing support to its clients, operating dedicated client management units. Clients can also contact members of the Company’s consulting and support personnel at the relevant office, or can make more general enquiries over the phone or via an online contact form.
Additionally, Booz Allen Hamilton provides a range of online resources to its clients, notably its various industry and market insights, white papers, videos, podcasts, and studies. Clients are also able to interact with the Company, and follow its corporate developments and activities, through its social media accounts including with Facebook, Twitter, and LinkedIn.
Key Activities
Booz Allen Hamilton is an international provider of management and technology, consulting and engineering services. It operates through a single business segment, providing tailored solutions and consulting services – including systems delivery, engineering and science, cyber, analytics, and consulting – to the US and international governments, commercial entities, and non-profit organisations. Much of the Company’s business relates to its range of services provided to US Government agencies, including the Federal Bureau of Investigations, the US Army, the US Navy, the National Security Agency, and the Department of Homeland Security.
The Company’s commercial clients in the US operate primarily in the financial services, healthcare and life sciences, energy, high-technology manufacturing, retail, and automotive industries. While the bulk of the Company’s business is conducted in the US, Booz Allen Hamilton also serves clients across the Middle East and Southeast Asia.
Key Partners
Booz Allen Hamilton works closely with a range of companies and organisations that assist the Company in providing high-quality services and solutions. These partners can be categorised broadly as:
- Supplier and Vendor Partners, comprising suppliers of services, tools, technologies, and equipment that are utilised across the enterprise or within certain of its departments, as well as companies to which no-technical functions can be outsourced;
- Strategic and Alliance Partners, comprising various market-leading companies across multiple sectors, with which the Company shares resources and collaborates on joint projects;
- Technology Partners, comprising technology, IT services, and systems integration companies that provide technology and It maintenance and security services to the Company;
- Educational and Academic Partners, comprising various education and academic institutions, with which the Company collaborates on management and business programs, and offers opportunities to top graduates; and
- Community and Social Partners, comprising a number of non-profits and charitable organisations with which the Company collaborates on social and community projects around the world. Booz Allen Hamilton has partnerships in place with a number of high-profile names. This includes a technology partnership with Amazon Web Services concerning opportunities related to the internet-of-things, a tie-up with Microsoft to provide surface tablets to hospitals, and an education partnership with Excelsior College.
Key Resources
Booz Allen Hamilton’s key resources are its intellectual properties, its relationships with the US Government, its IT and communications infrastructure – including its cyber security systems, its sales and service network, its partnerships, and its personnel.
Booz Allen Hamilton owns a range of intellectual properties and proprietary information, which are protected by trademark and trade secret laws. The Company also owns a number of patents, although it does not consider its business to be materially dependent on the protection of these patents. Searches of records published by the US Patent and Trademark Office identified several patent applications filed in Booz Allen Hamilton’s name, including applications entitled ‘Mobile pothole detection system and method’, ‘Vehicle identification system and method’ and ‘Systems and method for identifying and mitigating information security risks’.
Booz Allen Hamilton also leases a number of physical properties across the US and abroad, principally relating to its various corporate and administrative offices.
Cost Structure
Booz Allen Hamilton incurs cost in relation to the development of its solutions, the maintenance of its IT and communications infrastructure, the operation of its sales and service network, the management of its partnerships, the procurement of professional services, and the retention of its personnel.
In fiscal year 2016 Booz Allen Hamilton recorded total operating costs and expenses in the amount of $4.96 billion. This included cost of revenue totalling $2.58 billion, and general and administrative expenses – including expenses related to corporate administrative functions, marketing and bid and proposal costs – totalling $806.51 million.
Revenue Streams
Booz Allen Hamilton generates revenue derived from the provision of various management and technology, consulting, and engineering services under contract to institutional and corporate clients, including cyber security, IT strategy, systems delivery, and strategic communications solutions.
In 2016 Booz Allen Hamilton generated annual revenue of $5.41 billion, up marginally on the $5.27 billion recorded by the Company in 2015. The Company attributed this small increase to a general increase in client demand.


gh label
Work with GitHub labels on the command-line.
More information: home page
- List labels for the repository in the current directory:
gh label list
- View labels for the repository in the current directory in the default web browser:
gh label list --web
- Create a label with a specific name, description and color in hexadecimal format for the repository in the current directory:
gh label create name --description "description" --color color_hex
- Delete a label for the repository in the current directory, prompting for confirmation:
gh label delete name
- Update the name and description for a specific label for the repository in the current directory:
gh label edit name --name new_name --description "description"
- Clone labels from a specific repository into the repository in the current directory:
gh label clone owner/repository
- Display help for a subcommand:
gh label subcommand --help


Catherine's older sister. She famously moonwalked across the stage to receive her college diploma and will no doubt break out her moves at the reception. She lives in Brooklyn, works as a software tester, and made this website!
Catherine's oldest sister and constant cooking/baking inspiration. The adorable flower girls and ring bearers all belong to her. Maggie lives in South Bend, Indiana, with her husband, Kirk, and homeschools her children.
Catherine's oldest friend and swimming teammate growing up. Tori recently moved back to the New York area with her husband Matt. She continues to impress everyone with her woodworking and home improvement skills, making up for Catherine's extreme lack of artistic ability.
Catherine's other friend named Tory. Catherine and Tory met in middle school, a time of their life which Tory remembers clearly and Catherine thankfully does not. These days Tory is always picking up new endurance sports and competing in (read: winning) races.
A friend from Ridgewood who spent most of high school in classes with Catherine. After college, Emily and Catherine were roommates in Boston for a few years (pre-Brent). Emily works at an education non-profit in Boston and can often be found curled up with a good book.
A friend from Ridgewood who now lives in New Hampshire with her wife Anna. Jessica is always up to try local breweries and cideries (which quickly won over Brent). She helps people recover from injury as a Recreation Therapist at a rehabilitation hospital.
Catherine's Harvard teammate and college roommate who shares Catherine's love of long meals and naps. She recently wrapped up her PhD in Chemical Engineering at the University of Michigan. This fall, she got married and started as a scientist at AbbVie in Chicago.
Catherine's college roommate and life cheerleader. She is pint-sized, and as a coxswain for the men's crew team, is often hilariously surrounded by large men. She works at a social impact consulting firm in DC and always has fun facts at the ready.
Catherine's Harvard teammate. Faith lives in Boston and works at a marketing firm. Not much has changed since college (other than much less swimming). Catherine and Faith can still be found regularly taking selfies, reliving hilarious events, and frequenting Border Cafe, a Harvard square favorite.
Sheree is Brent's younger sister, and she inherited all the artistic talent: she's a self-taught guitar player, singer, and painter. Sheree is soon to graduate from Cal Poly, where she has studied the impact of climate change on the ocean - bringing her one step closer to fulfilling her dream of living on her surfboard.
Andrew and Brent have been friends since elementary school. Over the past 20 years, they've explored California on many backpacking trips, hunted with their dads, and even spent a summer in Hawai'i "studying for the SAT. " Andrew works as a database developer in California.
Rich and Brent were roommates during their first year at Yale. During that year, Rich introduced Brent to Guitar Hero, Seinfeld, and Family Guy, which was bad for their studies but great for their friendship. Rich works for Disney in New York as a project manager.
Bryce was one of Brent's college roommates and his ping pong nemesis. He recently hiked the entire Appalachian Trail and grew a beard that even Brent envied. Bryce is currently writing and directing his first movie. In his spare time, he works as a software consultant in Texas.
Gabe was another of Brent's college roommates and a frequent Mario Kart competitor. He now lives in Boston and works as at Harvard Business School, where he writes cases for MBA students like Brent and Catherine. As at Yale, Gabe can still be found around campus wearing a bow tie and humming classical music.
Sarah and Brent became fast friends in college over a love of science and terrible Chinese food. After college, they were roommates, where they introduced Catherine and Sarah's wife Jess to Brookline's version of terrible Chinese food: Chef Chow's. Sarah is in her third year of medical school at Tufts.
Cassie and Brent became friends at Yale over long meals in the Silliman dining hall. Cassie moved to Boston for grad school and now works at a non-profit. Cassie, Catherine, and Brent have shared many scoops of ice cream (or in Cassie's case, sorbet) at JP Licks, one of the couple's favorite Boston establishments.
Kyle grew up swimming with Catherine and then met Brent at Yale, where they lived in the same dorm. He received his PhD in Biology at Harvard (much to Catherine's delight) and is now a postdoctoral researcher at Tufts. He has an uncanny ability to pick up new board games and frequently joins Catherine and Brent to play.


4. General pattern of information interactions beyond theoretical limits
When an agent interacts with someone other he receives and keeps an information image of current partner's state.
Interaction between the observer and a certain given agent is possible in principle when the information image of this agent corresponds to his real state with sufficient accuracy. Two-way interaction between observer and given agent is possible when both information images can be maintaining correctly. If information image reproduces the state of the corresponding agent inaccurately, the possibility that this pair of agents will find a mutually acceptable variant of their joint activity based on some incorrect models is rather low.
Remember a picture from above of general limitations on the agent interactions within the information space. Following this the observer has realistic images of the agents when and only when the given agent group can adjust the frequency of changes in its information images on appropriate level. If the frequency of changes fits well to the possibilities of data transfer without losing information actuality to the distance from the observer to the agents then the observer will be able to interact with the agents.
Due to objective reasons an economic system has non-ideal level of current ICT development and some level of stochastic changes in the system. So it is always possible to find groups of agents within the space of a large-scale economic system that do not have technical means to organize information exchange at the level required for their interaction. Persistent stochastic changes in all the parts and objects of economic system devalue the content of information flows disseminated. With the given velocity of the changes in the state of agents requiring appropriate coordination with the partners, and limitations on the information dissemination velocity, it is always possible to determine the maximum distances within the system space exceeding which means technical impossibility of agent interaction. In previous sections this fact was a reason for selecting zones A, B, and C (see Fig. 3). However, by decreasing the necessity to coordinate the changes in their state the agents are able to organize interactions at the distances that exceed theoretically possible values. So if agents simultaneously slow down the level of their information image's changes, they will get conditions to interact each other in wider boundaries then before.
If information exchange level required for agent interactions cannot be attained by technical means (by changing information permeability of the environment), conditions necessary for the interaction can be created by institutional means. Agent can adopt behavior rules common for all of them; in accordance with the above their information images estranged to the outside environment, their information images should match certain standards. If the standards regulate the permissible upper limit of the degree of information image variability, then the set of agents that adhere to this standard, will form their own information images that will be uniform in their mutability extent. The totality of the latter uniform images can be considered as an independent sub-space for agent interaction; its content has certain relationship with the processes of change in the real space of economic system.
In fact, agents here should create a certain projection of real space. This projection has to differ from the reality in, at least, deceleration of the change processes. By designing institutional structures, agents can form projections of real space that reflect real processes with various decelerations. Each of these institutional limitations outlines the sub-spaces and makes for the establishment of new agent interaction conditions and channels. As a result, interactions become possible within broader spatial boundaries that would be unattainable without the use of appropriate institutional structures.
| From the point of view of individual agent-observer (see a man at the left side on Fig. 4), his interaction with variously remote groups of potential partners (one or many men at the right side on Fig. 4) requires him to design and maintain a whole set of his information images made to the standards of the corresponding sub-spaces. So the observer has several parallel channels and sub-space to interact with other agents (four parallel sub-spaces on Fig. 4). To make a set of his potential partners wider he has to simplify his information image according rules and standards of appropriate institutional structures. |
Fig. 4. (see bigger image) |
Thus, certain set of institutional structures operating in an economy, segments the entire space of the system into a certain number of sub-spaces with their own rules and parameters of agent interactions. The more remote interactions are to be organized, the higher deceleration of real processes is to be implemented when designing the corresponding sub-space.
In similar vein, the more remote interactions those sub-spaces are mediating, the stronger are the discrepancies between real processes in an economic system and their reflection in sub-spaces. It would be logical to assume that long-term functioning of these sub-spaces should be completed by a procedure of bringing the state of subspaces into accord with the real state of the economic system.
Now we have a general picture of context where information interactions take place. The next step is to describe a scheme of interactions in details.
Next section - 5. Scheme of Information Interactions: Causes and Motives of Interactions
Previous section - 3. Spatial boundaries of information interactions between agents


{% trans 'Sorry, your browser does not support current web applications.' %}
{% trans 'Please use a newer Browser like firefox or Chrome and NOT IE. Microsoft is ending their support for this browser.' %}
{% trans 'Download Chrome' %} {% trans 'Download Firefox' %} {% trans 'Download Safari' %}


module BitSet: BatBitSet
type t
let empty : unit => t
Example: BitSet.empty ()
let create : int => t
Example: BitSet.create 0 = BitSet.empty ()
Raises Invalid_argument
on negative capacity
let create_full : int => t
Example: BitSet.count (BitSet.create_full n) = n
Raises Invalid_argument
on negative capacity
let copy : t => t
Example:
let a = Bitset.create 8 in
let b = BitSet.copy a in
BitSet.set a 6;
BitSet.mem a 6 && not (BitSet.mem b 6)
let mem : t => int => bool
mem s n
returns true if nth-bit in the bitset s
is set,
or false otherwise.
Example: let a = BitSet.create_full 256 in not (BitSet.mem a 300)
Raises Invalid_argument
on negative index (n < 0
)
let count : t => int
count s
returns the number of bits set in the bitset s
. Also
known as Population Count, or cardinal
for sets.
Example: BitSet.count (BitSet.of_list [6;4;2;2;1]) = 4
let next_set_bit : t => int => option int
next_set_bit s n
returns Some m
when m
is the next set
element with index greater than or equal n
, or None if no such
element exists (i.e. n
is greater than the largest element)
More efficient than scanning with repeated BitSet.mem
.
Raises Invalid_argument
on negative index (n < 0
)
let set : t => int => unit
set s n
sets the n
th-bit in the bitset s
to true.Invalid_argument
on negative index (n < 0
)let unset : t => int => unit
unset s n
sets the n
th-bit in the bitset s
to false.Invalid_argument
on negative index (n < 0
)let put : t => bool => int => unit
put s v n
sets the nth-bit in the bitset s
to v
.Invalid_argument
on negative index (n < 0
)let toggle : t => int => unit
toggle s n
changes the nth-bit value in the bitset s
.Invalid_argument
on negative index (n < 0
)let intersect : t => t => unit
intersect s t
sets s
to the intersection of the sets s
and t
.let unite : t => t => unit
unite s t
sets s
to the union of the sets s
and t
.let differentiate : t => t => unit
differentiate s t
removes the elements of t
from s
.let differentiate_sym : t => t => unit
differentiate_sym s t
sets s
to the symmetrical difference of the
sets s
and t
.let add : int => t => t
add n s
returns a copy of s
with bit n
true.Invalid_argument
on negative index (n < 0
)let remove : int => t => t
remove n s
returns a copy of s
with bit n
false.Invalid_argument
on negative index (n < 0
)let inter : t => t => t
inter s t
returns the intersection of sets s
and t
.let union : t => t => t
union s t
return the union of sets s
and t
.let diff : t => t => t
diff s t
returns s
-t
.let sym_diff : t => t => t
sym_diff s t
returns the symmetrical difference of s
and t
.let print : BatInnerIO.output 'a => t => unit
let enum : t => BatEnum.t int
enum s
returns an enumeration of bits which are set
in the bitset s
.let of_enum : cap::int? => BatEnum.t int => t
of_enum ~cap e
builds a bitset of capacity cap
an enumeration
of ints e
.
Note: Performance of this function may be poor if enumeration is
in increasing order and the max.
let of_list : cap::int? => list int => t
of_enum
, but from a listlet compare : t => t => int
compare s1 s2
compares two bitsets using a lexicographic
ordering. Highest bit indexes are compared first. The capacity of
the bitsets is not important for this comparison, only the bits
starting with the highest set bit and going down.let equal : t => t => bool
equal s1 s2
returns true if, and only if, all bits values in s1 are
the same as in s2.let ord : t => t => BatOrd.order
ord s1 s2
returns BatOrd.Lt
, BatOrd.Eq
or BatOrd.Gt
if compare s1 s2
is, respectively, < 0
, 0
or > 0
.let capacity : t => int
capacity s
returns the number of bits, both set and unset, stored
in s
. This is guaranteed to be larger than the largest element
(set bit index) in s
.


STAPL
Git : STAPL Repository
Duration
2020.05 ~ 2020.09
Introduction
“Can’t I study English in a fun and effective way?” We started to develop an application with this reason. The goal is active,effective studying, breaking away from the traditional hard, boring, document-based study methods. Object recognition technology using deep learning makes it easy and fast to search for words anytime, anywhere. You can study not only words but also example sentence and record your learning with the Notepad function. The Stapl app is available all age groups. You can learn simple usage and use the application efficiently. It will be applied in real life a new way of studying, not a routine study.
Tech
Java php MySQL TensorFlow VisualStudioCode AndroidStudio
Role
- Frontend UX/UI 파트 담당
- 디자인 컨셉과 일관되고, 효율적 학습을 위한 UX/UI 개선
- 비동기 처리와 Splash page 애니메이션 기능 구현


Class Profile
A single Profile Property information of a User.
So a user will have many of these to fully describe his Profile.
Inheritance
Implements
Namespace: Oqtane.Models
Assembly: Oqtane.Shared.dll
Syntax
public class Profile : IAuditable
Properties
| Improve this Doc View SourceCategory
Category of this Profile-Property for grouping etc.
Declaration
public string Category { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
CreatedBy
Username of the creator of this Object.
Declaration
public string CreatedBy { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
CreatedOn
Created Timestamp for this Object.
Declaration
public DateTime CreatedOn { get; set; }
Property Value
| Type | Description |
|---|---|
| System.DateTime |
DefaultValue
Initial/default value of this Property.
Declaration
public string DefaultValue { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Description
Description of the Property for the UI.
Declaration
public string Description { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
IsPrivate
Some Profile Properties are private, meaning other users won't see them.
Declaration
public bool IsPrivate { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Boolean |
IsRequired
Some Profile Properties are required - marked with this field.
Declaration
public bool IsRequired { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Boolean |
MaxLength
Limits the input length of the property.
Declaration
public int MaxLength { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int32 |
ModifiedBy
Username of the last user who modified this Object.
Declaration
public string ModifiedBy { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
ModifiedOn
Modified Timestamp for this Object.
Declaration
public DateTime ModifiedOn { get; set; }
Property Value
| Type | Description |
|---|---|
| System.DateTime |
Name
Name of the Profile-Property. NOT the User-Name.
Declaration
public string Name { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Options
This gives possible values for dropdown input fields.
Declaration
public string Options { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
ProfileId
Internal ID
Declaration
public int ProfileId { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int32 |
SiteId
Reference to the Site. It's nullable, probably because certain users like Super-Users don't specifically belong to any site.
Declaration
public int? SiteId { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Nullable<System.Int32> |
Title
Title (label) of the Profile Property.
Declaration
public string Title { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
ViewOrder
Order of the Property in the list of Profile-Properties.
Declaration
public int ViewOrder { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int32 |


Chuters
High Concept
The goal of the game is to safely land as many parachuters (or "chuters") as you can on the target below before running out of reinforcements.  Obstacles such as enemy tank fire and dynamic wind elements will make this challenge increasingly difficult until the player fails. To add more depth to the game, a chain reaction element will be incorporated--if a player can successfully land a specified number of chuters in a row, they will trigger a bombing run and blow up the enemies on the ground. This is an unwinnable, never-ending game that challenges players to attain higher scores.
Genre
Chuters is a blend of the chain reaction and avoidance game genres.
Platform
We are initially targeting the desktop platform.
Story
There is no specific story in Chuters as the players are only trying to land as many "chuters" as they can and the game continues.
Players must avoid incoming enemy fire to succeed, and successfully landing "chuters" consecutively will generate rewards for the player.
Esthetics
We will be using 8-bit pixel art graphics for the game.
There will be ambient background music that is not too slow.
Some of the types of sound will include:
- score on landing
- battle sounds
Gameplay
Mechanics
The player will have to decide on the fly which direction to fall and possibly how fast. The player will be avoiding bullets while trying to safely land on a specific point.
Control
- Keyboard arrows for movement
- Possible other keys for rewards or power-ups (will update when decided)
Onboarding and Teaching the game
The basic controls will be initially displayed to the user.
Player learning
The player will need to learn what to avoid to make a safe landing.
Screenshots
Other
Nothing to add here. Chuters will be coded from scratch without using external libraries.
About the developers
Derrick Hunt is a game design and development major, journalism minor. He is skilled with game programming and graphic asset creation. This will be the second game he has created using HTML canvas and JavaScript.
Chad Karon is a Game Design and Development major. He is a proficient programmer and this will be the third game he has helped create using HTML canvas and JavaScript.


SharpDevelop (#Develop) is one of the Open Source alternatives to the Microsoft Visual Studio. Currently CS-Script can be integrated with version 2.0 of #Develop.
It is a reasonably stable and flexible IDE. The drawback is the absence of the integrated debugger. Thus, it must be used with an external debugger like MS CLR Debugger. But the integrated debugger is expected in the future releases (see SharpDevelop home page for details).
Open the script in #Develop by using shell extension:
After being activating by the user the 'shell extension' creates a temporary #Develop project, which includes all necessary source files and libraries. The project is automatically loaded into the new instance of #Develop. You can work now with this project as with any other #Develop project. After closing the project all temporary files are cleared.
This is the screenshot of the opening "Hello World!" sample (hello.cs file).
Debugging tutorial | Script Library | MS CLR Debugger


MulensModel.fitdata module¶
-
class
MulensModel.fitdata.
FitData
(model=None, dataset=None, fix_blend_flux=False, fix_source_flux=False, fix_source_flux_ratio=False)¶ Bases:
object
Performs a least squares linear fit for given dataset and model to determine the source flux(es) and (optionally) blend flux. After creating the object, you must run
update()
to perform the linear fit for the fluxes and calculate the chi2. To perform the linear fit without calculating chi2, you can runfit_fluxes()
. If you change anything in the object, e.g. the model parameters, you must re-runupdate()
orfit_fluxes()
.- Arguments :
- model:
Model
object The model to fit to the data.
- dataset:
MulensData
object A single photometric dataset to be fitted.
- fix_blend_flux: False or float, optional
Default is False, i.e. allow the blend flux to be a free parameter. If set to a float, it will fix the blend value to that value.
- fix_source_flux: False, float, or list, optional
Default is False, i.e. allow the source flux to be a free parameter. If set to a float, it will fix the source value to that value. For binary source models, a list should be used to set the fluxes of the individual sources or fix one and not the other, e.g. [2.3, False] would fix source_flux_0 to 2.3 but allow a free fit to source_flux_1.
- fix_source_flux_ratio: False or float, optional
For binary source models, source_flux_ratio is the flux ratio between two components, i.e., source_flux_ratio = source_flux_1 / source_flux_0 Default is False, i.e. allow the source flux to be a free parameter. If set to a float, it will fix the source value to that value.
- model:
-
update
(bad=False)¶ Calculate the best-fit source and blend fluxes as well as the chi2.
- Keywords :
- bad: bool
Default is False. If True recalculates the data magnification for each point to ensure that there are values even for bad datapoints.
-
fit_fluxes
()¶ Execute the linear least squares fit to determine the fitted fluxes. Sets the values of
source_fluxes
,blend_flux
, and (if applicable)source_flux
.Does not calculate chi2. To fit for the fluxes and calculate chi2, run
update()
.
-
get_data_magnification
(bad=False)¶ Calculates the model magnification for each data point.
- Arguments :
- bad: boolean
If True, calculates the magnification for all points. If False, only calculates the magnification for good data points. Values for bad data points are set to 0. Default is False.
- Returns :
- data_magnification: np.ndarray
The model magnification evaluated for each datapoint. If there is more than one source, the magnification of each source is reported separately.
-
get_model_fluxes
(bad=False)¶ Calculate model in flux space.
- Keywords :
- bad: bool
Default is False. If True recalculates the data magnification for each point to ensure that the values for bad datapoints are calculated (otherwise, they are set to the magnitude of the blend).
- Returns :
- model_flux: np.ndarray
The model flux evaluated for each datapoint.
-
get_model_magnitudes
(**kwargs)¶ Calculate model in magnitude space
- Arguments :
**kwargs
:
- Returns :
- model_mag: np.ndarray
The model magnitude evaluated for each datapoint.
-
scale_fluxes
(source_flux, blend_flux)¶ - Rescale the data fluxes to an arbitrary flux scale:
flux = source_flux_0 * (data.flux - blend_flux) / source_flux flux += blend_flux_0 err_flux = source_flux_0 * data.err_flux / source_flux
- Arguments :
- source_flux: float, list, np.array
Flux of the source in the desired system. If n_sources > 1 and source_flux has more than one element, the elements are summed to produce the overall scaling flux.
- blend_flux: float
Flux of the blend in the desired system
- Returns :
(flux, err): the fluxes and flux errors of the dataset rescaled to the desired system
-
get_residuals
(phot_fmt=None, source_flux=None, blend_flux=None, bad=False, type=None)¶ Calculate the residuals for each datapoint relative to the model.
- Keywords :
- phot_fmt: str, optional
specify whether the residuals should be returned in magnitudes (‘mag’) or in flux (‘flux’). Default is ‘mag’. If ‘scaled’, will return the residuals in magnitudes scaled to source_flux, blend_flux.
- source_flux, blend_flux: float
reference source and blend fluxes for scaling the residuals
- bad: bool
Default is False. If True recalculates the data magnification for each point to ensure that there are values even for bad datapoints.
type: deprecated, see “phot_fmt”.
- Returns :
- residuals: np.ndarray
the residuals for the corresponding dataset.
- errorbars: np.ndarray
the scaled errorbars for each point. For plotting errorbars for the residuals.
-
get_chi2_gradient
(parameters)¶ Fits fluxes and calculates chi^2 gradient (also called Jacobian), i.e., \(d chi^2/d parameter\).
- Parameters :
- parameters: str or list, required
Parameters with respect to which gradient is calculated. Currently accepted parameters are:
t_0
,u_0
,t_eff
,t_E
,pi_E_N
, andpi_E_E
. The parameters for which you request gradient must be defined in py:attr:~model.
- Returns :
- gradient: float or np.ndarray
chi^2 gradient
-
calculate_chi2_gradient
(parameters)¶ Calculates chi^2 gradient (also called Jacobian), i.e., \(d chi^2/d parameter\) WITHOUT refitting for the fluxes. Saves computations if, e.g., you want to retrieve both py:attr:~chi2 and py:attr:~chi2_gradient.
- Parameters :
- parameters: str or list, required
Parameters with respect to which gradient is calculated. Currently accepted parameters are:
t_0
,u_0
,t_eff
,t_E
,pi_E_N
, andpi_E_E
. The parameters for which you request gradient must be defined in py:attr:~model.- Returns :
gradient: float or np.ndarray chi^2 gradient
-
property
chi2_gradient
¶ Return previously calculated chi^2 gradient (also called Jacobian), i.e., \(d chi^2/d parameter\). See
get_chi2_gradient()
andcalculate_chi2_gradient()
.- Returns :
- gradient: float or np.ndarray
chi^2 gradient. Will return None if the chi2 gradient was not previously calculated using one of the functions mentioned above.
-
property
chi2
¶ - Returns :
- chi2: float
the total chi2 for the fitted dataset. Good points only. See
good
.
If None, you need to run
update()
to execute the linear fit and calculate the chi2.
-
property
chi2_per_point
¶ - Returns :
- chi2_per_point: np.ndarray
Chi^2 contribution from each data point, e.g.
chi2_per_point[k]
returns the chi2 contribution from the k-th point ofdataset
. Includes bad datapoints.
If None, you need to run
update()
to execute the linear fit and calculate the chi2.
-
property
source_flux
¶ - Returns :
source_flux: float the fitted source flux. Only defined for models with a single source. See also
source_fluxes
If None, you need to run
fit_fluxes()
orupdate()
to execute the linear fit.
-
property
source_fluxes
¶ - Returns :
- source_fluxes: np.array
the fitted source flux(es).
If None, you need to run
fit_fluxes()
orupdate()
to execute the linear fit.
-
property
blend_flux
¶ - Returns :
- blend_flux: float
the fitted blend flux or the value set by fix_blend_flux (see Keywords).
If None, you need to run
fit_fluxes()
orupdate()
to execute the linear fit.
-
property
source_flux_ratio
¶ source_flux_ratio = source_flux_1 / source_flux_0
- Returns :
- source_flux_ratio: float
the ratio of the fitted source fluxes or the value set by fix_source_flux_ratio (see Keywords).
If None, you need to run
fit_fluxes()
orupdate()
to execute the linear fit.
-
property
dataset
¶ MulensData
objectA single photometric dataset to be fitted.
-
property
gamma
¶ float
Limb-darkening coefficient for this fit. Set by
bandpass
andget_limb_coeff_gamma()
.* CHECK LINKS IN SPHINX. PROBABLY WON’T WORK. *


| Total net profit | 16.54 | Gross profit | 77.75 | Gross loss | -61.21 |
| Profit factor | 1.27 | Expected payoff | 0.1 | ||
| Absolute drawdown | -0.15 | Maximal drawdown (%) | 17.54 (52.25%) | ||
| Total trades | 171 | Profit trades (% of total) | 97 (56.73%) | Loss trades (% of total) | 74 (43.27%) |
| Long positions (won %) | 84 (55.95%) | Short positions (won %) | 87 (57.47%) | ||
| Largest | profit trade | 8.36 | loss trade | -5.52 | |
| Average | profit trade | 0.8 | loss trade | -0.83 | |
| Minimum | profit trade | 0.0 | loss trade | -0.02 | |
| Maximum | take profit in pips | 226.0 | stop loss in pips | -152.2 | |
| Average | take profit in pips | 189.1 | stop loss in pips | -141.4 | |
| Minimum | take profit in pips | 178.3 | stop loss in pips | -104.5 | |
| Maximum | Reward-Risk | 2.2 | Duration in minutes | 4668 | |
| Average | Reward-Risk | 1.3 | Duration in minutes | 491.9 | |
| Minimum | Reward-Risk | 1.2 | Duration in minutes | 3 | |
| Maximum | consecutive wins (profit in money) | 6.0 (6.4) | consecutive losses (loss in money) | 5.0 (-4.44) | |
| Average | consecutive wins | 2.0 | consecutive losses | 1.0 |
| Total net profit | 7.21 | Gross profit | 42.55 | Gross loss | -35.34 |
| Profit factor | 1.2 | Expected payoff | 0.09 | ||
| Absolute drawdown | -1.42 | Maximal drawdown (%) | 12.22 (64.59%) | ||
| Total trades | 84 | Profit trades (% of total) | 47 (55.95%) | Loss trades (% of total) | 37 (44.05%) |
| Largest | profit trade | 8.36 | loss trade | -5.52 | |
| Average | profit trade | 0.91 | loss trade | -0.96 | |
| Minimum | profit trade | 0.01 | loss trade | -0.03 | |
| Maximum | take profit in pips | 226.0 | stop loss in pips | -152.2 | |
| Average | take profit in pips | 188.8 | stop loss in pips | -141.7 | |
| Minimum | take profit in pips | 178.3 | stop loss in pips | -104.5 | |
| Maximum | Reward-Risk | 2.2 | Duration in minutes | 4499.0 | |
| Average | Reward-Risk | 1.3 | Duration in minutes | 493.2 | |
| Minimum | Reward-Risk | 1.2 | Duration in minutes | 3.0 | |
| Maximum | consecutive wins (profit in money) | 8.0 (5.48) | consecutive losses (loss in money) | 4.0 (-7.68) | |
| Average | consecutive wins | 2.0 | consecutive losses | 1.0 |
| Total net profit | 9.33 | Gross profit | 35.2 | Gross loss | -25.87 |
| Profit factor | 1.36 | Expected payoff | 0.11 | ||
| Absolute drawdown | -0.15 | Maximal drawdown (%) | 8.79 (51.58%) | ||
| Total trades | 87 | Profit trades (% of total) | 50 (57.47%) | Loss trades (% of total) | 37 (42.53%) |
| Largest | profit trade | 3.01 | loss trade | -4.22 | |
| Average | profit trade | 0.7 | loss trade | -0.7 | |
| Minimum | profit trade | 0.0 | loss trade | -0.02 | |
| Maximum | take profit in pips | 205.7 | stop loss in pips | -147.9 | |
| Average | take profit in pips | 189.3 | stop loss in pips | -141.2 | |
| Minimum | take profit in pips | 182.6 | stop loss in pips | -124.8 | |
| Maximum | Reward-Risk | 1.6 | Duration in minutes | 4668.0 | |
| Average | Reward-Risk | 1.3 | Duration in minutes | 490.7 | |
| Minimum | Reward-Risk | Duration in minutes | 8.0 | ||
| Maximum | consecutive wins (profit in money) | 7.0 (8.35) | consecutive losses (loss in money) | 5.0 (-2.01) | |
| Average | consecutive wins | 2.0 | consecutive losses | 1.0 |


--- layout: default title: Home ---
This website hosts the whimsical ramblings of a software engineer who spends too much time thinking about the important things in life like the meaning behind the biofluoresence of platypuses.


José Carlos Soto Monterrubio
I am a Ph. D. candidate in Computer Science by the Instituto Tecnológico de Ciudad Madero and Ph. D. candidate in Engineering Informatics by Universidad de Cádiz. My research interest are intelligent optimization, parallel computing and data analyst.
Parallel programming, intelligent optimization, multi-objective optimization, artifial intelligence, data analyst


flag-icon-css
A collection of all country flags in SVG — plus the CSS for easier integration. See the demo.
Install
You can either download the whole project as is or install it via Bower or NPM:
$ bower install flag-icon-css
$ npm install flag-icon-css
Usage
For using the flags inline with text add the classes .flag-icon
and
.flag-icon-xx
(where xx
is the
ISO 3166-1-alpha-2 code
of a country) to an empty
. If you want to have a squared version flag
then add the class flag-icon-squared
as well. Example:

You could also apply this to any element, but in that case you’ll have to use the
flag-icon-background
instead of flag-icon
and you’re set. This will add the
correct background with the following CSS properties:
background-size: contain;
background-position: 50%;
background-repeat: no-repeat;
Which means that the flag is just going to appear in the middle of an element, so
you will have to set manually the correct size of 4 by 3 ratio or if it’s squared
add also the flag-icon-squared
class.
Development
Run the npm install
to install the dependencies after cloning the project and
you’ll be able to:
To watch for changes and live reload if served
$ grunt
To build *.less
files
$ grunt build
To serve it on localhost:8000
$ grunt connect
To have only specific countries in the css file, remove the ones that you don’t
need from the
flag-icon-list.less
file and build it again.
Credits
This project wouldn’t exist without the awesome and now deleted collection of SVG flags by koppi.


Nature
Hills.
A Good angle.
Sunset and nature.
Late evening.
Shores of an ocean.
Boats ready to sail.
drop.
White Mountains.
Animals
cat-1
cat-2
cat-3
cat-4
animal 5
animal 6
animal 7
animal 8
People
person 1
person 2
person 3
person 4
person 5
person 6
person 7
person 8


Hey there. I'm Gabriel.
For now, I'm a student on the Faculty of Organization and Informatics in Varaždin
(a small city in northern Croatia).Right now I'm on my 4th year of studies, and my major is Organization of Business Systems.
This page was primarily imagined as my portfolio page, to show some of my works, and projects that I was involved during college
and some of my personal ones. Secondarily I'll be using this page as a platform for learning Web development and design.
Currently I'm learning Web development from a great course hosted on Udemy


public static final class Protos.ExecutorInfo.Builder extendsimplements Protos.ExecutorInfoOrBuilder
mesos.ExecutorInfo
Describes information about an executor.
| Modifier and Type | Method and Description |
|---|---|
Protos.ExecutorInfo.Builder |
addAllResources(java.lang.Iterable<? extends Protos.Resource> values)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
addResources(int index,
Protos.Resource.Builder builderForValue)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
addResources(int index,
Protos.Resource value)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
addResources(Protos.Resource.Builder builderForValue)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
addResources(Protos.Resource value)
repeated .mesos.Resource resources = 5; |
Protos.Resource.Builder |
addResourcesBuilder()
repeated .mesos.Resource resources = 5; |
Protos.Resource.Builder |
addResourcesBuilder(int index)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo |
build() |
Protos.ExecutorInfo |
buildPartial() |
Protos.ExecutorInfo.Builder |
clear() |
Protos.ExecutorInfo.Builder |
clearCommand()
optional .mesos.CommandInfo command = 7; |
Protos.ExecutorInfo.Builder |
clearContainer()
optional .mesos.ContainerInfo container = 11; |
Protos.ExecutorInfo.Builder |
clearData()
optional bytes data = 4; |
Protos.ExecutorInfo.Builder |
clearDiscovery()
optional .mesos.DiscoveryInfo discovery = 12; |
Protos.ExecutorInfo.Builder |
clearExecutorId()
required .mesos.ExecutorID executor_id = 1; |
Protos.ExecutorInfo.Builder |
clearFrameworkId()
optional .mesos.FrameworkID framework_id = 8; |
Protos.ExecutorInfo.Builder |
clearLabels()
optional .mesos.Labels labels = 14; |
Protos.ExecutorInfo.Builder |
clearName()
optional string name = 9; |
Protos.ExecutorInfo.Builder |
clearResources()
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
clearShutdownGracePeriod()
optional .mesos.DurationInfo shutdown_grace_period = 13; |
Protos.ExecutorInfo.Builder |
clearSource()
Deprecated.
|
Protos.ExecutorInfo.Builder |
clearType()
optional .mesos.ExecutorInfo.Type type = 15; |
Protos.ExecutorInfo.Builder |
clone() |
Protos.CommandInfo |
getCommand()
optional .mesos.CommandInfo command = 7; |
Protos.CommandInfo.Builder |
getCommandBuilder()
optional .mesos.CommandInfo command = 7; |
Protos.CommandInfoOrBuilder |
getCommandOrBuilder()
optional .mesos.CommandInfo command = 7; |
Protos.ContainerInfo |
getContainer()
optional .mesos.ContainerInfo container = 11; |
Protos.ContainerInfo.Builder |
getContainerBuilder()
optional .mesos.ContainerInfo container = 11; |
Protos.ContainerInfoOrBuilder |
getContainerOrBuilder()
optional .mesos.ContainerInfo container = 11; |
com.google.protobuf.ByteString |
getData()
optional bytes data = 4; |
Protos.ExecutorInfo |
getDefaultInstanceForType() |
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
com.google.protobuf.Descriptors.Descriptor |
getDescriptorForType() |
Protos.DiscoveryInfo |
getDiscovery()
optional .mesos.DiscoveryInfo discovery = 12; |
Protos.DiscoveryInfo.Builder |
getDiscoveryBuilder()
optional .mesos.DiscoveryInfo discovery = 12; |
Protos.DiscoveryInfoOrBuilder |
getDiscoveryOrBuilder()
optional .mesos.DiscoveryInfo discovery = 12; |
Protos.ExecutorID |
getExecutorId()
required .mesos.ExecutorID executor_id = 1; |
Protos.ExecutorID.Builder |
getExecutorIdBuilder()
required .mesos.ExecutorID executor_id = 1; |
Protos.ExecutorIDOrBuilder |
getExecutorIdOrBuilder()
required .mesos.ExecutorID executor_id = 1; |
Protos.FrameworkID |
getFrameworkId()
optional .mesos.FrameworkID framework_id = 8; |
Protos.FrameworkID.Builder |
getFrameworkIdBuilder()
optional .mesos.FrameworkID framework_id = 8; |
Protos.FrameworkIDOrBuilder |
getFrameworkIdOrBuilder()
optional .mesos.FrameworkID framework_id = 8; |
Protos.Labels |
getLabels()
optional .mesos.Labels labels = 14; |
Protos.Labels.Builder |
getLabelsBuilder()
optional .mesos.Labels labels = 14; |
Protos.LabelsOrBuilder |
getLabelsOrBuilder()
optional .mesos.Labels labels = 14; |
java.lang.String |
getName()
optional string name = 9; |
com.google.protobuf.ByteString |
getNameBytes()
optional string name = 9; |
Protos.Resource |
getResources(int index)
repeated .mesos.Resource resources = 5; |
Protos.Resource.Builder |
getResourcesBuilder(int index)
repeated .mesos.Resource resources = 5; |
java.util.List<Protos.Resource.Builder> |
getResourcesBuilderList()
repeated .mesos.Resource resources = 5; |
int |
getResourcesCount()
repeated .mesos.Resource resources = 5; |
java.util.List<Protos.Resource> |
getResourcesList()
repeated .mesos.Resource resources = 5; |
Protos.ResourceOrBuilder |
getResourcesOrBuilder(int index)
repeated .mesos.Resource resources = 5; |
java.util.List<? extends Protos.ResourceOrBuilder> |
getResourcesOrBuilderList()
repeated .mesos.Resource resources = 5; |
Protos.DurationInfo |
getShutdownGracePeriod()
optional .mesos.DurationInfo shutdown_grace_period = 13; |
Protos.DurationInfo.Builder |
getShutdownGracePeriodBuilder()
optional .mesos.DurationInfo shutdown_grace_period = 13; |
Protos.DurationInfoOrBuilder |
getShutdownGracePeriodOrBuilder()
optional .mesos.DurationInfo shutdown_grace_period = 13; |
java.lang.String |
getSource()
Deprecated.
|
com.google.protobuf.ByteString |
getSourceBytes()
Deprecated.
|
Protos.ExecutorInfo.Type |
getType()
optional .mesos.ExecutorInfo.Type type = 15; |
boolean |
hasCommand()
optional .mesos.CommandInfo command = 7; |
boolean |
hasContainer()
optional .mesos.ContainerInfo container = 11; |
boolean |
hasData()
optional bytes data = 4; |
boolean |
hasDiscovery()
optional .mesos.DiscoveryInfo discovery = 12; |
boolean |
hasExecutorId()
required .mesos.ExecutorID executor_id = 1; |
boolean |
hasFrameworkId()
optional .mesos.FrameworkID framework_id = 8; |
boolean |
hasLabels()
optional .mesos.Labels labels = 14; |
boolean |
hasName()
optional string name = 9; |
boolean |
hasShutdownGracePeriod()
optional .mesos.DurationInfo shutdown_grace_period = 13; |
boolean |
hasSource()
Deprecated.
|
boolean |
hasType()
optional .mesos.ExecutorInfo.Type type = 15; |
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable |
internalGetFieldAccessorTable() |
boolean |
isInitialized() |
Protos.ExecutorInfo.Builder |
mergeCommand(Protos.CommandInfo value)
optional .mesos.CommandInfo command = 7; |
Protos.ExecutorInfo.Builder |
mergeContainer(Protos.ContainerInfo value)
optional .mesos.ContainerInfo container = 11; |
Protos.ExecutorInfo.Builder |
mergeDiscovery(Protos.DiscoveryInfo value)
optional .mesos.DiscoveryInfo discovery = 12; |
Protos.ExecutorInfo.Builder |
mergeExecutorId(Protos.ExecutorID value)
required .mesos.ExecutorID executor_id = 1; |
Protos.ExecutorInfo.Builder |
mergeFrameworkId(Protos.FrameworkID value)
optional .mesos.FrameworkID framework_id = 8; |
Protos.ExecutorInfo.Builder |
mergeFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
Protos.ExecutorInfo.Builder |
mergeFrom(com.google.protobuf.Message other) |
Protos.ExecutorInfo.Builder |
mergeLabels(Protos.Labels value)
optional .mesos.Labels labels = 14; |
Protos.ExecutorInfo.Builder |
mergeShutdownGracePeriod(Protos.DurationInfo value)
optional .mesos.DurationInfo shutdown_grace_period = 13; |
Protos.ExecutorInfo.Builder |
removeResources(int index)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
setCommand(Protos.CommandInfo.Builder builderForValue)
optional .mesos.CommandInfo command = 7; |
Protos.ExecutorInfo.Builder |
setCommand(Protos.CommandInfo value)
optional .mesos.CommandInfo command = 7; |
Protos.ExecutorInfo.Builder |
setContainer(Protos.ContainerInfo.Builder builderForValue)
optional .mesos.ContainerInfo container = 11; |
Protos.ExecutorInfo.Builder |
setContainer(Protos.ContainerInfo value)
optional .mesos.ContainerInfo container = 11; |
Protos.ExecutorInfo.Builder |
setData(com.google.protobuf.ByteString value)
optional bytes data = 4; |
Protos.ExecutorInfo.Builder |
setDiscovery(Protos.DiscoveryInfo.Builder builderForValue)
optional .mesos.DiscoveryInfo discovery = 12; |
Protos.ExecutorInfo.Builder |
setDiscovery(Protos.DiscoveryInfo value)
optional .mesos.DiscoveryInfo discovery = 12; |
Protos.ExecutorInfo.Builder |
setExecutorId(Protos.ExecutorID.Builder builderForValue)
required .mesos.ExecutorID executor_id = 1; |
Protos.ExecutorInfo.Builder |
setExecutorId(Protos.ExecutorID value)
required .mesos.ExecutorID executor_id = 1; |
Protos.ExecutorInfo.Builder |
setFrameworkId(Protos.FrameworkID.Builder builderForValue)
optional .mesos.FrameworkID framework_id = 8; |
Protos.ExecutorInfo.Builder |
setFrameworkId(Protos.FrameworkID value)
optional .mesos.FrameworkID framework_id = 8; |
Protos.ExecutorInfo.Builder |
setLabels(Protos.Labels.Builder builderForValue)
optional .mesos.Labels labels = 14; |
Protos.ExecutorInfo.Builder |
setLabels(Protos.Labels value)
optional .mesos.Labels labels = 14; |
Protos.ExecutorInfo.Builder |
setName(java.lang.String value)
optional string name = 9; |
Protos.ExecutorInfo.Builder |
setNameBytes(com.google.protobuf.ByteString value)
optional string name = 9; |
Protos.ExecutorInfo.Builder |
setResources(int index,
Protos.Resource.Builder builderForValue)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
setResources(int index,
Protos.Resource value)
repeated .mesos.Resource resources = 5; |
Protos.ExecutorInfo.Builder |
setShutdownGracePeriod(Protos.DurationInfo.Builder builderForValue)
optional .mesos.DurationInfo shutdown_grace_period = 13; |
Protos.ExecutorInfo.Builder |
setShutdownGracePeriod(Protos.DurationInfo value)
optional .mesos.DurationInfo shutdown_grace_period = 13; |
Protos.ExecutorInfo.Builder |
setSource(java.lang.String value)
Deprecated.
|
Protos.ExecutorInfo.Builder |
setSourceBytes(com.google.protobuf.ByteString value)
Deprecated.
|
Protos.ExecutorInfo.Builder |
setType(Protos.ExecutorInfo.Type value)
optional .mesos.ExecutorInfo.Type type = 15; |
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
public Protos.ExecutorInfo.Builder clear()
public Protos.ExecutorInfo.Builder clone()
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
public Protos.ExecutorInfo getDefaultInstanceForType()
public Protos.ExecutorInfo build()
public Protos.ExecutorInfo buildPartial()
public Protos.ExecutorInfo.Builder mergeFrom(com.google.protobuf.Message other)
public final boolean isInitialized()
public Protos.ExecutorInfo.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
java.io.IOException
public boolean hasType()
optional .mesos.ExecutorInfo.Type type = 15;
For backwards compatibility, if this field is not set when using `LAUNCH` offer operation, Mesos will infer the type by checking if `command` is set (`CUSTOM`) or unset (`DEFAULT`). `type` must be set when using `LAUNCH_GROUP` offer operation. TODO(vinod): Add support for explicitly setting `type` to `DEFAULT ` in `LAUNCH` offer operation.
hasType
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Type getType()
optional .mesos.ExecutorInfo.Type type = 15;
For backwards compatibility, if this field is not set when using `LAUNCH` offer operation, Mesos will infer the type by checking if `command` is set (`CUSTOM`) or unset (`DEFAULT`). `type` must be set when using `LAUNCH_GROUP` offer operation. TODO(vinod): Add support for explicitly setting `type` to `DEFAULT ` in `LAUNCH` offer operation.
getType
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setType(Protos.ExecutorInfo.Type value)
optional .mesos.ExecutorInfo.Type type = 15;
For backwards compatibility, if this field is not set when using `LAUNCH` offer operation, Mesos will infer the type by checking if `command` is set (`CUSTOM`) or unset (`DEFAULT`). `type` must be set when using `LAUNCH_GROUP` offer operation. TODO(vinod): Add support for explicitly setting `type` to `DEFAULT ` in `LAUNCH` offer operation.
public Protos.ExecutorInfo.Builder clearType()
optional .mesos.ExecutorInfo.Type type = 15;
For backwards compatibility, if this field is not set when using `LAUNCH` offer operation, Mesos will infer the type by checking if `command` is set (`CUSTOM`) or unset (`DEFAULT`). `type` must be set when using `LAUNCH_GROUP` offer operation. TODO(vinod): Add support for explicitly setting `type` to `DEFAULT ` in `LAUNCH` offer operation.
public boolean hasExecutorId()
required .mesos.ExecutorID executor_id = 1;
hasExecutorId
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorID getExecutorId()
required .mesos.ExecutorID executor_id = 1;
getExecutorId
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setExecutorId(Protos.ExecutorID value)
required .mesos.ExecutorID executor_id = 1;
public Protos.ExecutorInfo.Builder setExecutorId(Protos.ExecutorID.Builder builderForValue)
required .mesos.ExecutorID executor_id = 1;
public Protos.ExecutorInfo.Builder mergeExecutorId(Protos.ExecutorID value)
required .mesos.ExecutorID executor_id = 1;
public Protos.ExecutorInfo.Builder clearExecutorId()
required .mesos.ExecutorID executor_id = 1;
public Protos.ExecutorID.Builder getExecutorIdBuilder()
required .mesos.ExecutorID executor_id = 1;
public Protos.ExecutorIDOrBuilder getExecutorIdOrBuilder()
required .mesos.ExecutorID executor_id = 1;
getExecutorIdOrBuilder
in interface Protos.ExecutorInfoOrBuilder
public boolean hasFrameworkId()
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
hasFrameworkId
in interface Protos.ExecutorInfoOrBuilder
public Protos.FrameworkID getFrameworkId()
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
getFrameworkId
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setFrameworkId(Protos.FrameworkID value)
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
public Protos.ExecutorInfo.Builder setFrameworkId(Protos.FrameworkID.Builder builderForValue)
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
public Protos.ExecutorInfo.Builder mergeFrameworkId(Protos.FrameworkID value)
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
public Protos.ExecutorInfo.Builder clearFrameworkId()
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
public Protos.FrameworkID.Builder getFrameworkIdBuilder()
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
public Protos.FrameworkIDOrBuilder getFrameworkIdOrBuilder()
optional .mesos.FrameworkID framework_id = 8;
TODO(benh): Make this required.
getFrameworkIdOrBuilder
in interface Protos.ExecutorInfoOrBuilder
public boolean hasCommand()
optional .mesos.CommandInfo command = 7;
hasCommand
in interface Protos.ExecutorInfoOrBuilder
public Protos.CommandInfo getCommand()
optional .mesos.CommandInfo command = 7;
getCommand
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setCommand(Protos.CommandInfo value)
optional .mesos.CommandInfo command = 7;
public Protos.ExecutorInfo.Builder setCommand(Protos.CommandInfo.Builder builderForValue)
optional .mesos.CommandInfo command = 7;
public Protos.ExecutorInfo.Builder mergeCommand(Protos.CommandInfo value)
optional .mesos.CommandInfo command = 7;
public Protos.ExecutorInfo.Builder clearCommand()
optional .mesos.CommandInfo command = 7;
public Protos.CommandInfo.Builder getCommandBuilder()
optional .mesos.CommandInfo command = 7;
public Protos.CommandInfoOrBuilder getCommandOrBuilder()
optional .mesos.CommandInfo command = 7;
getCommandOrBuilder
in interface Protos.ExecutorInfoOrBuilder
public boolean hasContainer()
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
hasContainer
in interface Protos.ExecutorInfoOrBuilder
public Protos.ContainerInfo getContainer()
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
getContainer
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setContainer(Protos.ContainerInfo value)
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
public Protos.ExecutorInfo.Builder setContainer(Protos.ContainerInfo.Builder builderForValue)
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
public Protos.ExecutorInfo.Builder mergeContainer(Protos.ContainerInfo value)
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
public Protos.ExecutorInfo.Builder clearContainer()
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
public Protos.ContainerInfo.Builder getContainerBuilder()
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
public Protos.ContainerInfoOrBuilder getContainerOrBuilder()
optional .mesos.ContainerInfo container = 11;
Executor provided with a container will launch the container with the executor's CommandInfo and we expect the container to act as a Mesos executor.
getContainerOrBuilder
in interface Protos.ExecutorInfoOrBuilder
public java.util.List<Protos.Resource> getResourcesList()
repeated .mesos.Resource resources = 5;
getResourcesList
in interface Protos.ExecutorInfoOrBuilder
public int getResourcesCount()
repeated .mesos.Resource resources = 5;
getResourcesCount
in interface Protos.ExecutorInfoOrBuilder
public Protos.Resource getResources(int index)
repeated .mesos.Resource resources = 5;
getResources
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setResources(int index, Protos.Resource value)
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder setResources(int index, Protos.Resource.Builder builderForValue)
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder addResources(Protos.Resource value)
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder addResources(int index, Protos.Resource value)
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder addResources(Protos.Resource.Builder builderForValue)
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder addResources(int index, Protos.Resource.Builder builderForValue)
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder addAllResources(java.lang.Iterable<? extends Protos.Resource> values)
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder clearResources()
repeated .mesos.Resource resources = 5;
public Protos.ExecutorInfo.Builder removeResources(int index)
repeated .mesos.Resource resources = 5;
public Protos.Resource.Builder getResourcesBuilder(int index)
repeated .mesos.Resource resources = 5;
public Protos.ResourceOrBuilder getResourcesOrBuilder(int index)
repeated .mesos.Resource resources = 5;
getResourcesOrBuilder
in interface Protos.ExecutorInfoOrBuilder
public java.util.List<? extends Protos.ResourceOrBuilder> getResourcesOrBuilderList()
repeated .mesos.Resource resources = 5;
getResourcesOrBuilderList
in interface Protos.ExecutorInfoOrBuilder
public Protos.Resource.Builder addResourcesBuilder()
repeated .mesos.Resource resources = 5;
public Protos.Resource.Builder addResourcesBuilder(int index)
repeated .mesos.Resource resources = 5;
public java.util.List<Protos.Resource.Builder> getResourcesBuilderList()
repeated .mesos.Resource resources = 5;
public boolean hasName()
optional string name = 9;
hasName
in interface Protos.ExecutorInfoOrBuilder
public java.lang.String getName()
optional string name = 9;
getName
in interface Protos.ExecutorInfoOrBuilder
public com.google.protobuf.ByteString getNameBytes()
optional string name = 9;
getNameBytes
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setName(java.lang.String value)
optional string name = 9;
public Protos.ExecutorInfo.Builder clearName()
optional string name = 9;
public Protos.ExecutorInfo.Builder setNameBytes(com.google.protobuf.ByteString value)
optional string name = 9;
@Deprecated public boolean hasSource()
optional string source = 10 [deprecated = true];
'source' is an identifier style string used by frameworks to track the source of an executor. This is useful when it's possible for different executor ids to be related semantically. NOTE: 'source' is exposed alongside the resource usage of the executor via JSON on the slave. This allows users to import usage information into a time series database for monitoring. This field is deprecated since 1.0. Please use labels for free-form metadata instead.
hasSource
in interface Protos.ExecutorInfoOrBuilder
@Deprecated public java.lang.String getSource()
optional string source = 10 [deprecated = true];
'source' is an identifier style string used by frameworks to track the source of an executor. This is useful when it's possible for different executor ids to be related semantically. NOTE: 'source' is exposed alongside the resource usage of the executor via JSON on the slave. This allows users to import usage information into a time series database for monitoring. This field is deprecated since 1.0. Please use labels for free-form metadata instead.
getSource
in interface Protos.ExecutorInfoOrBuilder
@Deprecated public com.google.protobuf.ByteString getSourceBytes()
optional string source = 10 [deprecated = true];
'source' is an identifier style string used by frameworks to track the source of an executor. This is useful when it's possible for different executor ids to be related semantically. NOTE: 'source' is exposed alongside the resource usage of the executor via JSON on the slave. This allows users to import usage information into a time series database for monitoring. This field is deprecated since 1.0. Please use labels for free-form metadata instead.
getSourceBytes
in interface Protos.ExecutorInfoOrBuilder
@Deprecated public Protos.ExecutorInfo.Builder setSource(java.lang.String value)
optional string source = 10 [deprecated = true];
'source' is an identifier style string used by frameworks to track the source of an executor. This is useful when it's possible for different executor ids to be related semantically. NOTE: 'source' is exposed alongside the resource usage of the executor via JSON on the slave. This allows users to import usage information into a time series database for monitoring. This field is deprecated since 1.0. Please use labels for free-form metadata instead.
@Deprecated public Protos.ExecutorInfo.Builder clearSource()
optional string source = 10 [deprecated = true];
'source' is an identifier style string used by frameworks to track the source of an executor. This is useful when it's possible for different executor ids to be related semantically. NOTE: 'source' is exposed alongside the resource usage of the executor via JSON on the slave. This allows users to import usage information into a time series database for monitoring. This field is deprecated since 1.0. Please use labels for free-form metadata instead.
@Deprecated public Protos.ExecutorInfo.Builder setSourceBytes(com.google.protobuf.ByteString value)
optional string source = 10 [deprecated = true];
'source' is an identifier style string used by frameworks to track the source of an executor. This is useful when it's possible for different executor ids to be related semantically. NOTE: 'source' is exposed alongside the resource usage of the executor via JSON on the slave. This allows users to import usage information into a time series database for monitoring. This field is deprecated since 1.0. Please use labels for free-form metadata instead.
public boolean hasData()
optional bytes data = 4;
This field can be used to pass arbitrary bytes to an executor.
hasData
in interface Protos.ExecutorInfoOrBuilder
public com.google.protobuf.ByteString getData()
optional bytes data = 4;
This field can be used to pass arbitrary bytes to an executor.
getData
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setData(com.google.protobuf.ByteString value)
optional bytes data = 4;
This field can be used to pass arbitrary bytes to an executor.
public Protos.ExecutorInfo.Builder clearData()
optional bytes data = 4;
This field can be used to pass arbitrary bytes to an executor.
public boolean hasDiscovery()
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
hasDiscovery
in interface Protos.ExecutorInfoOrBuilder
public Protos.DiscoveryInfo getDiscovery()
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
getDiscovery
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setDiscovery(Protos.DiscoveryInfo value)
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
public Protos.ExecutorInfo.Builder setDiscovery(Protos.DiscoveryInfo.Builder builderForValue)
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
public Protos.ExecutorInfo.Builder mergeDiscovery(Protos.DiscoveryInfo value)
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
public Protos.ExecutorInfo.Builder clearDiscovery()
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
public Protos.DiscoveryInfo.Builder getDiscoveryBuilder()
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
public Protos.DiscoveryInfoOrBuilder getDiscoveryOrBuilder()
optional .mesos.DiscoveryInfo discovery = 12;
Service discovery information for the executor. It is not interpreted or acted upon by Mesos. It is up to a service discovery system to use this information as needed and to handle executors without service discovery information.
getDiscoveryOrBuilder
in interface Protos.ExecutorInfoOrBuilder
public boolean hasShutdownGracePeriod()
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
hasShutdownGracePeriod
in interface Protos.ExecutorInfoOrBuilder
public Protos.DurationInfo getShutdownGracePeriod()
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
getShutdownGracePeriod
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setShutdownGracePeriod(Protos.DurationInfo value)
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
public Protos.ExecutorInfo.Builder setShutdownGracePeriod(Protos.DurationInfo.Builder builderForValue)
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
public Protos.ExecutorInfo.Builder mergeShutdownGracePeriod(Protos.DurationInfo value)
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
public Protos.ExecutorInfo.Builder clearShutdownGracePeriod()
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
public Protos.DurationInfo.Builder getShutdownGracePeriodBuilder()
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
public Protos.DurationInfoOrBuilder getShutdownGracePeriodOrBuilder()
optional .mesos.DurationInfo shutdown_grace_period = 13;
When shutting down an executor the agent will wait in a best-effort manner for the grace period specified here before forcibly destroying the container. The executor must not assume that it will always be allotted the full grace period, as the agent may decide to allot a shorter period and failures / forcible terminations may occur.
getShutdownGracePeriodOrBuilder
in interface Protos.ExecutorInfoOrBuilder
public boolean hasLabels()
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
hasLabels
in interface Protos.ExecutorInfoOrBuilder
public Protos.Labels getLabels()
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
getLabels
in interface Protos.ExecutorInfoOrBuilder
public Protos.ExecutorInfo.Builder setLabels(Protos.Labels value)
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
public Protos.ExecutorInfo.Builder setLabels(Protos.Labels.Builder builderForValue)
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
public Protos.ExecutorInfo.Builder mergeLabels(Protos.Labels value)
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
public Protos.ExecutorInfo.Builder clearLabels()
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
public Protos.Labels.Builder getLabelsBuilder()
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
public Protos.LabelsOrBuilder getLabelsOrBuilder()
optional .mesos.Labels labels = 14;
Labels are free-form key value pairs which are exposed through master and slave endpoints. Labels will not be interpreted or acted upon by Mesos itself. As opposed to the data field, labels will be kept in memory on master and slave processes. Therefore, labels should be used to tag executors with lightweight metadata. Labels should not contain duplicate key-value pairs.
getLabelsOrBuilder
in interface Protos.ExecutorInfoOrBuilder


Connect with more prospects, book more meetings, and generate more sales.
Dear Friend:
What I am about to say will probably shock you. You may not like hearing it.
But you'll have to admit that it's absolutely true.
Recognize, also, that it significantly impacts all of your future prospects for business growth and long-term prosperity. Here goes...
There are three types of entrepreneurs in the business world.
No matter which of the three groups you may currently fall into, one thing is certain: You want your business to do more, have more, reach farther and achieve a lot more financial and business success.
The problem is—at all three places on the entrepreneurial "continuum"— most people don't know how to move up to the higher (let alone the HIGHEST) levels. That's where I can help.
Back when I was reaching out to companies I did something horribly wrong.
How wrong you ask?
So wrong that for 6 months of sending emails I closed 0 deals.
Yes 0 deals.
And looking back... fixing this one thing would skyrocket my chances of sealing the deal.
What am I talking about?
I'm, of course, talking about my offer.
Show two completely different offers to the same number of targets and one will make you $2k and the other one will make you $15k.
This is the power of a good offer.
And back then...
(I'm not proud of saying this out loud)
My offer was...
"Give me $1000 and I'll take care of your LinkedIn networking problems for you"
This stinks!
No wonder I was not closing anybody.
But...
You don't have to go through this...
In fact, you can learn how to craft a really good offer rather easily and fast.
Your offer will determine your success.
All you have to do is follow the step-by-step system we developed.
When I started sticking to the system, I was suddenly able to close bigger deals with less effort.
We've spent years doing lead generation and have compared and tested almost every course available on the subject. I'm confident you'll find this useful!
If you want to build a powerhouse business but you're slammed. You can give your seat to a colleague...
Yours,
Robert Cooke
P.S. The Complete Guide on Business Emails is sponsored by our partner Leadspod.


Toggle navigation
★ Akos
Level: 2
Ranking: 47
Exp: 500/1200
MY PLANS
Today
FCT
Tomorrow
A's Birthday
Dinner with A
25 Dez
It's Christmas!
New Plan
Back


Draw a sketch below.
The sketch is stored as JSON in an input field.
Click to display the JSON data in the viewer.


An Axis-Aligned Bounding Box for a Node. Note that the values of the bounding box are not final, but might be changed.
More...
|
| double | lx |
| | Lower X-Coordinate. Do not set manually after constructing! Use the property instead! More...
|
| |
| double | ly |
| | Lower Y-Coordinate. Do not set manually after constructing! Use the property instead! More...
|
| |
| double | lz |
| | Lower Z-Coordinate. Do not set manually after constructing! Use the property instead! More...
|
| |
| double | ux |
| | Upper X-Coordinate. Do not set manually after constructing! Use the property instead! More...
|
| |
| double | uy |
| | Upper Y-Coordinate. Do not set manually after constructing! Use the property instead! More...
|
| |
| double | uz |
| | Upper Z-Coordinate. Do not set manually after constructing! Use the property instead! More...
|
| |
An Axis-Aligned Bounding Box for a Node. Note that the values of the bounding box are not final, but might be changed.
◆ BoundingBox() [1/2]
| CloudData.BoundingBox.BoundingBox |
( |
double |
lx, |
|
|
double |
ly, |
|
|
double |
lz, |
|
|
double |
ux, |
|
|
double |
uy, |
|
|
double |
uz |
|
) |
| |
|
inline |
Creates a new Bounding Box with the given parameters
◆ BoundingBox() [2/2]
Creates a new Bounding Box with the given Parameters
- Parameters
-
| min | Vector containing lx, ly and lz |
| max | Vector containing ux, uy and uz |
◆ Center()
| Vector3d CloudData.BoundingBox.Center |
( |
| ) |
|
|
inline |
Returns the center of the box
◆ GetBoundsObject()
| Bounds CloudData.BoundingBox.GetBoundsObject |
( |
| ) |
|
|
inline |
Returns the Bounds-Object (Unity-Class for BoundingBoxes)
◆ Max()
Returns the highest corner of the bounding box
◆ Min()
Returns the lowest corner of the bounding box
◆ MoveAlong()
| void CloudData.BoundingBox.MoveAlong |
( |
Vector3d |
vector | ) |
|
|
inline |
Moves the box along the given vector
◆ MoveToOrigin()
| void CloudData.BoundingBox.MoveToOrigin |
( |
| ) |
|
|
inline |
Moves the boxes, so its center is in the origin
◆ Radius()
| double CloudData.BoundingBox.Radius |
( |
| ) |
|
|
inline |
Returns the radius of the circumscribed sphere (half the length of the diagonal)
◆ Size()
Returns the width (x-length), length(y-length) and height (z-length) of the box
◆ SwitchYZ()
| void CloudData.BoundingBox.SwitchYZ |
( |
| ) |
|
|
inline |
Switches the Y and Z coordinates of the bounding box. This might be neccessary because of different coordinate systems
◆ lx
| double CloudData.BoundingBox.lx |
Lower X-Coordinate. Do not set manually after constructing! Use the property instead!
◆ ly
| double CloudData.BoundingBox.ly |
Lower Y-Coordinate. Do not set manually after constructing! Use the property instead!
◆ lz
| double CloudData.BoundingBox.lz |
Lower Z-Coordinate. Do not set manually after constructing! Use the property instead!
◆ ux
| double CloudData.BoundingBox.ux |
Upper X-Coordinate. Do not set manually after constructing! Use the property instead!
◆ uy
| double CloudData.BoundingBox.uy |
Upper Y-Coordinate. Do not set manually after constructing! Use the property instead!
◆ uz
| double CloudData.BoundingBox.uz |
Upper Z-Coordinate. Do not set manually after constructing! Use the property instead!
◆ Lx
| double CloudData.BoundingBox.Lx |
|
getset |
◆ Ly
| double CloudData.BoundingBox.Ly |
|
getset |
◆ Lz
| double CloudData.BoundingBox.Lz |
|
getset |
◆ Ux
| double CloudData.BoundingBox.Ux |
|
getset |
◆ Uy
| double CloudData.BoundingBox.Uy |
|
getset |
◆ Uz
| double CloudData.BoundingBox.Uz |
|
getset |
The documentation for this class was generated from the following file:


|
Troy Hunt
is one of the top cybersecurity experts in the world
right now, and he is everywhere.
Troy's website
haveibeenpwned.com
helps people (and governments!) world-wide check if
their data's been leaked. He even has his own
Wikipedia page.
Troy was an SSW client for many years, and even did his
first public presentation here.
For one night only, Troy will be presenting at the
SSW-run Sydney .NET User Group.
Join us on the evening of Wednesday, July 25 to see Troy
Hunt in person as he gives his latest presentation.
|


"KERCHIEF "mentioned only Ezekiel 13:18, 21, as an article of apparel or ornament applied to the head of the idolatrous women of Israel. The precise meaning of the word is uncertain. It appears to have been a long loose shawl, such as Oriental women wrap themselves in (Ruth 3:15; Isaiah 3:22). Some think that it was a long veil or head-dress, denoting by its form the position of those who wore it.
"KERCHIEF "mentioned only Ezekiel 13:18, 21, as an article of apparel or ornament applied to the head of the idolatrous women of Israel. The precise meaning of the word is uncertain. It appears to have been a long loose shawl, such as Oriental women wrap themselves in (Ruth 3:15; Isaiah 3:22). Some think that it was a long veil or head-dress, denoting by its form the position of those who wore it.


PRETTY PIZZA
Pizza Delivery is Painful
We bring you pizza when it counts.
Log In
Browse Pizza
ADD MORE CONTENT HERE


M3 x 5 mm Machine Screw Cross Head - M35
Summary
Name: M3 x 5 mm Machine Screw Cross Head
ID: SCRE-M3-X-05-70
Hex ID: M35
WebPage: https://github.com/oomlout/oomlout-OOMP/wiki/SCRE-M3-X-05-70
Short URL: http://oom.lt/M35
Revision History: https://github.com/oomlout/oomlout-OOMP/blob/master/parts/SCRE-M3-X-05-70/
| Type |
Size |
Color |
Description |
Index |
SCRE Machine Screw |
M3 M3 |
X
|
05 x 5 mm |
70 Cross Head |
Images
About
This part is awaiting a description.
Specifications
| Info |
Value |
| Type |
Machine Screw |
| Size |
M3 |
| Description |
x 5 mm |
| Index |
Cross Head |
Extra Details
Spotted a mistake, want to add more? Let us know<EMAIL_ADDRESS>All images and resources are licensed [CC BY-SA] unless otherwise stated (ie. the datasheets)


India will not join RCEP trade deal in blow to sprawling Asian pact
BANGKOK: India said Monday (Nov 4) it would not join a sprawling Asian trade pact, raising fears over how domestic producers would be hit, in a major blow for what could be the world's largest trade deal.
The Regional Comprehensive Economic Partnership (RCEP) was meant to account for 30 per cent of global GDP and loop in half of the world's people.
But India dug in over concerns about market access, fearing its domestic industries would be hard hit if the country was flooded by cheap Made-in-China goods.
"We have conveyed to the participating countries that we will not be joining the RCEP," Vijay Thakur Singh, a senior diplomat in charge of East Asia for India's Ministry of External Affairs.
"Our decision was guided by the impact this agreement will have on the ordinary human beings of India and livelihood of people, including the poorest of the poor," she said.
READ: What is the RCEP trade deal and what happens now?
READ: Asia-wide trade pact on course despite India, Thailand says
“Present form of the RCEP Agreement does not fully reflect the basic spirit and agreed guiding principles of RCEP,” prime minister Narendra Modi was quoted saying by Indian public broadcaster Prasar Bharati News Services in a tweet. “It does not address satisfactorily India’s outstanding issues and concerns.”
“It is not possible for India to join the #RCEP Agreement,” the broadcaster further quoted Modi as saying in the tweet.
The dramatic pullout comes after frenzied negotiations at the Association of Southeast Asian Nations (ASEAN) summit in Bangkok, which closed Monday evening.
The meeting was dominated by trade issues - with RCEP front and centre - backlit by the crippling US-China tariff war threatening to drag global growth.
The decision is a major blow to the deal, which intended to loop in all 10 ASEAN states plus China, Japan, South Korea, Australia and New Zealand - notably excluding the US.
Remaining members said they were aiming to sign the deal next year, after legal review of the draft terms of the text agreed Monday.
The news came after a full day of meetings at the ASEAN summit in Bangkok, attended by the leaders of Japan, South Korea, and India, along with China's premier.
Notably absent was a top US official after Washington sent commerce secretary Wilbur Ross and national security advisor Robert O'Brien in lieu of President Donald Trump.
OPEN DOOR
India's decision dashed hopes of closing the RCEP deal at the summit after seven years of gruelling negotiations.
A senior trade diplomat with knowledge of the negotiations said Modi did not budge because he was under domestic pressure.
But the diplomat held out the option that India could join at a "later date" even after it is signed, if outstanding issues are resolved.
China's deputy foreign minister Le Yucheng echoed that view.
"Whenever India is ready, it is welcome to get on board," he said before New Delhi confirmed its pullout.
As negotiations were being finalised Monday, the ASEAN bloc and its allies espoused open trade in the region.
"We are once again faced with the high winds of trade protectionism," said South Korean leader Moon Jae-in.
"We need to protect the free-trade order ... and bring the global economy back on track."


| Interface | Description |
|---|---|
| LocalModel |
The local model interface is used to build the model storage on top of it
|
| Message |
The interface message
|
| NetMsg |
Net msg class, this is different from the net message this one travels over the net directly
|
| Observer<T> |
This is a key part, the observer waits for an update by the observable
|
| RmiClientInterface |
The RmiClientInterface interface is the client interface that extends the Remote interface for RMI communitation.
|
| RmiServerInterface |
The RmiServerInterface is the server interface that extends the Remote interface and exposes two methods.
|
| Class | Description |
|---|---|
| CommandConstants |
Those constants are used to set some conventional values for the params of the Conditions.
|
| DeserializerConstants |
Those constants are used to set some conventional values for the deserializer, all the fields of the json files
have an entry here.
|
| ErrorResponse |
This class is basically a wrapper of the String class, this class was designed to have more functionality
but due to lack of time they were never implemented.
|
| InternalMessage |
This class represents a set of commands.
|
| MessageParser |
Transform a Message in a List of PlayerActions using reflection so that the Controller can check/setUp them.
|
| NetMessage |
Net message class
|
| Observable<T> |
This is a key part, the observable is the baseline for the majority of our classes, provides the method used to communicate internally
|
| Request |
Request objects are used by the View to send data to the Controller.
|
| RequestParser |
The RequestParser class is used to parse a request message from the server, by parsing the internal message
of a request.
|
| Response |
The Response class is the network object that is sent from server to client for any kind of notification and
communitation.
|
| RuntimeTypeAdapterFactory<T> |
Adapts values whose runtime type may differ from their declaration type.
|
| Exception | Description |
|---|---|
| Observer.CommunicationError |
The exception that notify if something is wrong
|


for i : 0 .. 7
%Set data bit i on parallel port LPT2
PC.ParallelPut (2, 2 ** i)
put "Data bit ", i, " or Pin ", i + 2, "has just been set"
end for
| 1 | Data bit 0 | 16 | Data bit 4 | ||||
| 2 | Data bit 1 | 32 | Data bit 5 | ||||
| 4 | Data bit 2 | 64 | Data bit 6 | ||||
| 8 | Data bit 3 | 128 | Data bit 7 |
For example, the command PC.ParallelPut (97) sets data bits 0, 5 and 6 high (97 = 1 + 32 + 64) and sets the other data pins low. Because there are only 8 data pins in the parallel port, the value passed to PC.ParallelPut must be from 0 to 255.
The PC.ParallelPut procedure is not meant for sending a stream of characters to the parallel port (for example, if you want to send the string "Hello" to the printer). If you want to do this, open the file "LPT1" using the open statement and put to the file.
This means that you can only call the function by calling PC.ParallelPut, not by calling ParallelPut.


In this post, I am looking into something that I have been wanting to look into for a while. This short notebook shows a mini investigation into work I did during my PhD.
Attaching package: 'data.table'
The following objects are masked from 'package:dplyr':
between, first, last
The following object is masked from 'package:purrr':
transpose
theme_set(theme_bw())
kidsides::download_sqlite_db()
Attempt failed to check sqlite exists or to download from the URL: https://tlab-kidsides.s3.amazonaws.com/data/effect_peds_19q2_v0.3_20211119.sqlite.gz
con <- kidsides::connect_sqlite_db()
In this notebook, I want to investigate more into a claim I made in my paper on pediatric drug safety:
We investigate the relationship between development stage and known pediatric drug effects, such as montelukast-induced psychiatric disorders, where we found a significant signal (odds ratio 8.77 [2.51, 46.94]) within the second year of life.
Now I’m not disputing this claim, I actually have this enrichment in the database I created:
# A tibble: 1 × 15
category atc_con…¹ meddr…² nichd atc_c…³ meddr…⁴ a b c d lwr
<chr> <chr> <chr> <chr> <chr> <chr> <int> <int> <int> <int> <dbl>
1 soc_atc5 monteluk… Psychi… todd… ATC5 SOC 16 6777 3 11145 2.51
# … with 4 more variables: odds_ratio <dbl>, upr <dbl>, pvalue <dbl>,
# fdr <dbl>, and abbreviated variable names ¹atc_concept_name,
# ²meddra_concept_name, ³atc_concept_class_id, ⁴meddra_concept_class_id
The odds of 8.7708426 indicates a large association of statistically significant reporting of montelukast-induced Psychiatric disorders for toddlers.
But, these statistics were generated using a null threshold declaring significance. I’m interested to evaluate montelukast and Psychiatric disorders having larger signal at a particular stage. Here’s my visualizations to attempt to evaluate this:
From these, we can see how there are large, outlier scores for montelukast induced Psychiatric disorders at the toddler stage. The score distributions are similar across toddler and childhood stages, though. Nevertheless, the last graph shows that the signals in the toddler stage are above the null 99% scores in a larger proportion of the signal distribution. So empirically, we do see that montelukast-induced Psychiatric disorders are more likely (i.e. have larger, nonrandom signal) at the toddler stage of child development.
Since the last graph is the most definitive graph showing localization of non-random signal for this systematic disorder, we can create the graph for all montelukast-induced systematic disorders in order to evaluate non-random signal at stages:
You can see that few systematic disorders had higher-than-the-null signal at stages. Psychiatric disorders do seem to be uniquely induced in toddlers by montelukast.