iVariantGuide Report Summary
Title:
{{title}}
Description
{{description}}
Report link
Explore full report


Do you want to save changes to this document before closing?
If you don't save, your changes will be lost.
There is more in heaven and sky than you have or can imagine. Software just lives in the depths of Hell.
If you don't save, your changes will be lost.


<ui5-select>
Basic Select
Phone
Tablet
Desktop
Phone
Tablet
Desktop
Phone
Tablet
Desktop
Phone
Tablet
Desktop
Select with Value State
Apple
Avocado
Mango
Orange
Pumpkin
Carrot
Strawberry
Tomato
Red Chili Pepper
Apple
Avocado
Mango
Orange
Pumpkin
Carrot
Strawberry
Tomato
Red Chili Pepper


Computer Science courses at CAS.
More Info
Courses available at SDM.
College of Engineering courses.
Metropolitan college courses.


Hi, Andrew here! I'm an aspiring data scientist with a desire to turn dull spreadsheets of numbers into beautiful imagery. With a guilty pleasure in tinkering with visualization libraries to create clear pictures, I have an aspiration to utilize my skills in order to solve problems and create an impact. Experienced in most fields of data science, including data wrangling, supervised and unsupervised learning, model evaluation, feature engineering, and data visualization. Open to internships or junior level positions in the Data Science field.
Currently working through a Master's Degree in Data Science at the University of Colorado, Boulder while volunteering at the non-profit organization Omdena. In my spare time I am practicing creating visualizations through Tableau and preparing for the Tableau Data Analyst certification.
Submission for the Pump it Up: Data Mining the Water Table competition that utilizes supervised learning to predict the functional status of water pumps in Tanzania, a country in East Africa.
Utilizes the python packages pandas, scikit-learn, matplotlib, seaborn, and geopandas.
Supervised machine learning model that takes in tweets and utilizes Natural Language Processing python libraries to classify their sentiment as positive, neutral, or negative.
Utilizes the python packages pandas, scikit-learn, seaborn, nltk, regex, and keras.
Recommender System model that utilizes Entrez to pull scholarly data from the National Center for Biotechnology Information servers based off of a keyword, recommends several articles that are relevant to the keyword, and provides extra analyses for future research.
Utilizes the python packages pandas, scikit-learn, seaborn, Bio, and nltk.
Master's Degree in Data Science at University of Colorado, Boulder ( Estimated Graduation Early 2024 )
Flatiron School Data Science Bootcamp
Bachelor's Degree in Computer Science at University of California, Santa Cruz
Volunteer at Omdena
Intern Software Contractor at Seagate
Intern at Anecdata
Intern at Acer Cloud Tech Inc.
Tableau Desktop Specialist


80% of adolescents globally lacking physical activity, PVO finds
by BNNThe World Health Organisation has found in a major study that globally only one in five adolescents moves enough daily to prevent detrimental effects on their health.
French news agency AFP reports on Friday, November 22, that in its first ever report on global trends for adolescent physical activity, the UN health agency stressed that urgent action was needed to get teens off their screens and moving more.
«We absolutely need to do more or we will be looking at a very bleak health picture for these adolescents,» study co-author Leanne Riley commented to journalists ahead of the launch.
The report, which was published in the Lancet Child & Adolescent Health journal, is based on data from surveys conducted between 2001 and 2016 of some 1.6 million students between the ages of 11 and 17 across 146 nations.
It found that 81 percent did not meet the WHO advice of at least an hour a day of physical activity such as walking, playing, riding a bike or taking part in organised sporting activities.
This was deemed worrying, since regular physical activity provides a host of health benefits, from improved heart and respiratory fitness to better cognitive function, making learning easier, according to WTO.


Pending Oders: 20
Reconcilled Orders: 80
Total Orders: 100
Un-reconcilled Payments: 20
Reconcilled Payments: 80
Total Payments: 100


Hello friends of Refcode!
We are asking for your support this Giving Tuesday to help us reach more refugees than ever before!
Donate nowAfter a slowdown during COVID, this year we really ramped back up to speed:
In summary, we are building a community where refugees and immigrants can transform their lives through education, mentorship, and technology.
With your help, we will more than double our reach in 2023, running 4 cohorts instead of 2, simultaneously serving even more refugees through self-paced curriculum, and expanding the number of clients we take through the Software Agency.
Thanks to the community of Refcode grads and professional software engineers volunteering their time, we’re able to accomplish a lot with a small budget, but this year the primary thing holding us back from accomplishing all that we hoped for was money.
Donations to Refcode help us manage the logistics to keep all these events and programs running smoothly, and more importantly, help to increase our operating budget history which increases the chances that we’ll receive large grants in the future. (Most foundations do not like giving money to programs that don’t have a history of spending a lot of money!)
I hope you’ll donate today and also forward this along to a connection who cares about refugees and diversity in the tech sphere.
Donate now


STAR WARS: THE EMPIRE STRIKES BACK (THE SPECIAL EDITION) A film review by Chad Polenz Copyright 1997 Chad Polenz
**** (out of 4 = excellent) 1997, PG, 130 minutes [2 hours, 10 minutes] [fantasy] Starring: Mark Hamill (Luke Skywalker), Harrison Ford (Han Solo), Carrie Fisher (Princess Leia), Billy Dee Williams (Lando Calrissian), James Earl Jones (voice of Darth Vader), written by George Lucas, Leigh Brackett, Lawrence Kasdan, produced by Gary Kurtz, directed by Irvin Kershner.
"The Empire Strikes Back" will always be considered the best or the worst of the "Star Wars" trilogy. Unlike the other two films, there is no major victory here and bad things happen to the heroes. On the other hand, this film contains the greatest amount of detail, continues the definition of The Force and the universe, and establishes a vivid mood, all of which can be just as moving as the swashbuckling adventure.
Truly the most notable improvement for the special edition re-releases of these films is their images on a big screen and digital surround sound. I don't remember seeing this movie in theaters back in 1980, so I have essentially become four years old again as I am able to view this film as it was meant to be seen.
I noticed many things happening around the perimeters and in the background that had either been cut or unfocused before. Also, the sound and sound effects editing are greatly improved with this edition; you can hear pieces of debris hitting the ground; people talking in the background; and every footstep on the metal floors.
Unlike the special edition of "Star Wars," this print does not contain as many additions. The first major enhancement occurs early in the film as Luke Skywalker is held captive by the snow monster. In the original version the monster scene seemed like a bit of a cop-out, but now it actually has some meaning to it. When Luke uses his lightsaber to defeat the monster, it doesn't seem so "implied" anymore because of the detail.
One of the best aspects to this film is its mood and atmosphere, especially that of Yoda's swamp planet Degobah and Lando Calrissian's Cloud City. Cloud City was already a beautiful, blissful place and although only a few enhancements are added here, they are profound on a subconscious level. When the Millennium Falcon arrives, it is shown flying throughout the entire city, and we can see people and buildings in the background; it no longer looks like a studio set at all. When characters walk by windows, we can see activity happening outside, instead of just still pictures. In fact, of the greatest enhancements only lasts a few seconds - as Lando uses a public address system to warn the population to flee the city, we see hundreds of people stop in the streets, in the halls, and in their homes to listen.
Luke's Jedi training is one of the most important elements in all of the films, and the words of Yoda are so simple and yet so profound at the same time. I have heard The Force is a Hollywood disguise for New Age philosophy, but I doubt it. This is a completely different universe and its ability to define such a complex place through relatively simple methods is nothing short of genius.
"The Empire Strikes Back" could be seen as the best of the trilogy for its definition of its reality and great designs. Or it could be seen as the worst of the series because of its sad tone and choppy storytelling (I always wondered how Luke knew where to find Han and Leia out of the entire galaxy and how Darth Vader knew Luke was coming). But it's the fascinating story that makes this a great film. (2/24/97) (6/11/97) [see "The Empire Strikes Back" for critique of original film, see also: "Star Wars: The Special Edition," "Return Of The Jedi: The Special Edition"]
please visit Chad'z Movie Page @ http://members.aol.com/ChadPolenz/index.html
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Object that represents a club.
Located in /library/Ivc/Model/Clubs/Club.php (line 24)
Documentation generated on Tue, 21 Feb 2012 06:45:22 +0800 by phpDocumentor 1.4.1


{{mailid}}
please enter first name
please enter valid first name
first name must be less than 20.
please enter last name
please enter valid last name
first name must be less than 15.
please enter mobile no
enter valid mobile no
please enter group name
group name must be less than 25.


27
1 Do not boast about tomorrow,
for you do not know what a day may bring.
2 Let someone else praise you and not your own mouth;
a stranger and not your own lips.
3 Consider the heaviness of a stone and the weight of sand,
and the provocation of a fool is heavier than both.
4 There is the cruelty of rage and the flood of anger,
but who is able to stand before jealousy?
5 Better is an open rebuke
than hidden love.
6 Faithful are the wounds caused by a friend,
but an enemy may kiss you profusely.
7 A person who has eaten to the full rejects even a honeycomb,
but to the hungry person, every bitter thing is sweet.
8 A bird that wanders from its nest
is like a man who strays from where he lives.
9 Perfume and incense make the heart rejoice,
but the sweetness of a friend is better than his advice.
10 Do not forsake your friend and your friend's father,
and do not go to your brother's house on the day of your calamity.
Better is a neighbor who is nearby than a brother who is far away.
11 Be wise, my son, and make my heart rejoice;
then I will give back an answer to the one who mocks me.
12 A prudent man sees trouble and hides himself,
but inexperienced people push ahead and suffer because of it.
13 Take a garment if its owner
puts up money as security for a stranger's debt;
and take it if he puts up security for an adulteress.
14 Whoever gives his neighbor a blessing with a loud voice early in the morning,
that blessing will be considered to be a curse!
15 A quarreling wife is like
the constant dripping on a rainy day;
16 restraining her is like restraining the wind,
or trying to catch oil in your right hand.
17 Iron sharpens iron;
in the same way, a man sharpens his friend.
18 The one who tends a fig tree will eat its fruit,
and the one who protects his master will be honored.
19 Just as water reflects a person's face,
so a person's heart reflects the person.
20 Just as sheol and Abaddon are never satisfied,
so a man's eyes are never satisfied.
21 A crucible is for silver and a furnace is for gold,
and a person is tested when he is praised.
22 Even if you crush a fool with the pestle—along with the grain—
yet his foolishness will not leave him.
23 Be sure you know the condition of your flocks,
and be concerned about your herds,
24 for wealth is not for ever.
Does a crown endure for all generations?
25 The grass is gone and the new growth appears
and on the mountains food for the cattle is gathered in.
26 The lambs will provide your clothing,
and the goats will provide the price of the field.
27 There will be goats' milk for your food—the food for your household—
and nourishment for your servant girls.


{% extends "site_template.html" %} {% block header-nav-content %}
Inside N Out Designs is a building/remodeling company that specializes in both interior and exterior home improvement projects. Our goal is to meet your renovation needs through an enjoyable and professional process. Below are some building/remodeling ideas that Inside N Out can bring to life in order for you to enjoy your home at its fullest potential.
Kitchens, Baths, Floors (wood, tile, laminates), Custom finished basements, Bedrooms and Offices
Windows, Doors, Siding, Decks, Patios, Fountains and Retaining Walls, and Landscape design (mulch, bed design and plants)


1.1 This document defines the bylaws under which the Apache CloudStack project operates. It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved and specifies the rules for specific project actions.
1.2. CloudStack is a project of the Apache Software Foundation. The foundation holds the trademark on the name "CloudStack" and copyright on Apache code including the code in the CloudStack codebase. The foundation FAQ explains the operation and background of the foundation.
1.3. CloudStack operates under a set of principles known collectively as the "Apache Way". Those principles are: Transparency, consensus, non-affiliation, respect for fellow developers, and meritocracy, in no specific order.
Apache projects define a set of roles with associated rights and responsibilities. These roles govern what tasks an individual may perform within the project. The roles are defined in the following sections:
A Contributor that makes sustained, welcome contributions to the project may be invited to become a Committer by the PMC. The invitation will be at the discretion of a supporting PMC member.
2.3. Committers The project's Committers are responsible for the project's technical management. Committers have access to all project source control repositories. Committers may cast binding votes on any technical discussion regarding the project (or any sub-project).
2.3.1. Committer access is by invitation only and must be approved by a lazy consensus of the active PMC members.
2.3.2. All Apache Committers are required to have a signed Individual Contributor License Agreement (ICLA) on file with the Apache Software Foundation. There is a Committer FAQ which provides more details on the requirements for Committers at Apache.
2.3.3. A Committer who makes a sustained contribution to the project may be invited by the PMC to become a member of the PMC, after approval of the PMC.
2.4. Project Management Committee
The Project Management Committee (PMC) for Apache CloudStack is responsible to the board and the ASF for the management and oversight of the Apache CloudStack codebase.
2.4.1. The responsibilities of the PMC include:
<IP_ADDRESS>. Fostering, supporting and growing the project's community.
<IP_ADDRESS>. Deciding what is distributed as products of the Apache CloudStack project. In particular all releases must be approved by the PMC.
<IP_ADDRESS>. Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.
<IP_ADDRESS>. Speaking on behalf of the project.
<IP_ADDRESS>. Resolving license disputes regarding products of the project.
<IP_ADDRESS>. Nominating new PMC members and committers.
<IP_ADDRESS>. Maintaining these bylaws and other guidelines of the project.
<IP_ADDRESS>. Managing and protecting the project's trademarks and brand.
2.4.2. Membership of the PMC is by invitation only and must be approved by a lazy consensus of active PMC members.
2.4.3. A PMC member is considered "emeritus" by their own declaration. An emeritus member may request reinstatement to the PMC. Such reinstatement is subject to lazy consensus of the active PMC members.
2.4.4. "Active PMC members" are all non-emeritus PMC members.
2.4.4. The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache Software Foundation (Vice President, Apache CloudStack) and has primary responsibility to the board for the management of the projects within the scope of the CloudStack PMC. The chair reports to the board quarterly on developments within the CloudStack project. The chair must be an active PMC member.
2.4.5. If the current chair of the PMC resigns, or the term of the current chair expires, the PMC will attempt to reach consensus on a new chair through discussion, confirming that consensus via a vote to recommend a new chair using a lazy 2/3 majority voting method. In the case that consensus is not achieved, the PMC will vote for a chair using Single Transferable Vote (STV) voting. Due to the fact that the discussions are about specific individuals, this vote would be held on the cloudstack-private mailing list. The decision must be ratified by the Apache board.
2.4.6. The role of PMC chair will have a one year term. The intention of this term is to allow for a rotation of the role amongst the PMC members. This intention does not prohibit the PMC from selecting the same chair to serve consecutive terms.
This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval.
3.1. Voting
3.1.1. Decisions regarding the project are made by votes on the primary project development mailing list (dev@cloudstack.apache.org). Where necessary, PMC voting may take place on the private CloudStack PMC mailing list. Votes are clearly indicated by subject line starting with [VOTE]. Votes may contain multiple items for approval and these should be clearly separated. Voting is carried out by replying to the vote mail.
3.1.2. Voting may take four flavors:
<IP_ADDRESS>. +1 "Yes," "Agree," or "the action should be performed." In general, this vote also indicates a willingness on the behalf of the voter in "making it happen"
<IP_ADDRESS>. +0 This vote indicates a willingness for the action under consideration to go ahead. The voter, however will not be able to help.
<IP_ADDRESS>. -0 This vote indicates that the voter does not, in general, agree with the proposed action but is not concerned enough to prevent the action going ahead.
<IP_ADDRESS>. -1 This is a negative vote. On issues where consensus is required, this vote counts as a veto if binding. All vetoes must contain an explanation of why the veto is appropriate. Vetoes with no explanation are void. It may also be appropriate for a -1 vote to include an alternative course of action.
3.1.3. All participants in the CloudStack project are encouraged to show their agreement with or against a particular action by voting. For technical decisions, only the votes of active committers are binding. Non-binding votes are still useful for those with binding votes to understand the perception of an action in the wider CloudStack community. For PMC decisions, only the votes of PMC members are binding.
3.1.4. Voting can also be applied to changes made to the CloudStack codebase. These typically take the form of a veto (-1) in reply to the commit message sent when the commit is made.
3.1.5. Non-binding -1 votes are not considered to be vetos for any decision.
3.2. Approvals
There are three types of approvals that can be sought. Section 3.4 describes actions and types of approvals needed for each action.
3.2.1. Lazy Consensus - Lazy consensus requires 3 binding +1 votes and no binding -1 votes.
3.2.2. Lazy Majority - A lazy majority vote requires 3 binding +1 votes and more binding +1 votes than binding -1 votes.
3.2.3. Lazy 2/3 Majority - Lazy 2/3 majority votes requires at least 3 binding votes and twice as many binding +1 votes as binding -1 votes.
3.3. Vetoes
3.3.1. Vetoes are only possible in a lazy consensus vote.
3.3.2. A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the reasons for the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto - merely that the veto is valid.
3.3.3. If you disagree with a valid veto, you must lobby the person casting the veto to withdraw their veto. If a veto is not withdrawn, any action that has been vetoed must be reversed in a timely manner.
3.4. Actions
This section describes the various actions which are undertaken within the project, the roles that have the right to start a vote on the action, the corresponding approval required for that action and those who have binding votes over the action.
3.4.1. Technical Decisions
A technical decision is any decision that involves changes to the source code that we distribute in our official releases.
Technical decisions should normally be made by the entire community using discussion-lead consensus gathering, and not through formal voting.
Technical decisions must be made on the project development mailing list.
During the consensus gathering process, technical decisions may be vetoed by any Committer with a valid reason.
If a formal vote is started for a technical decision, the vote will be held as a lazy consensus of active committers.
Any user, contributor, committer, or PMC member can initiate a technical decision making process.
3.4.2. Non-Technical Decisions
A non-technical decisions is any decision that does not involve changes to the source code that we distribute in our official releases (excluding questions of trademark usage).
Non-technical decisions should normally be made by the entire community using discussion-lead consensus-building, and not through formal voting.
Non-technical decisions can be made on whichever project mailing list is most appropriate.
Non-technical decisions cannot be vetoed, but if there is strong opposition a formal vote can be used to resolve the dispute.
If a formal vote is started for a non-technical decision, the vote will be held as a lazy 2/3 majority of active committers.
Any user, contributor, committer, or PMC member can initiate a non-technical decision making process.
3.4.3. Release Plan
Defines the timetable and work items for a release. The plan also nominates a Release Manager.
A lazy majority of active committers is required for approval.
Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.
3.4.4. Product Release
When a release of one of the project's products is ready, a vote is required to accept the release as an official release of the project.
Lazy Majority of active PMC members is required for approval.
Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.
3.4.5. Adoption of New Codebase
When the codebase for an existing, released product is to be replaced with an alternative codebase. If such a vote fails to gain approval, the existing code base will continue.
This also covers the creation of new sub-projects within the project.
Lazy 2/3 majority of active PMC members.
Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.
3.4.6. New Committer
When a new committer is proposed for the project.
Lazy consensus of active PMC members.
Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.
3.4.7. New PMC Member
When a committer is proposed for the PMC.
Lazy consensus of active PMC members.
Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.
3.4.8. Committer Removal
When removal of commit privileges is sought. Note: Such actions will also be referred to the ASF board by the PMC chair
Lazy 2/3 majority of active PMC members (excluding the committer in question if a member of the PMC).
Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.
3.4.9. PMC Member Removal
When removal of a PMC member is sought. Note: Such actions will also be referred to the ASF board by the PMC chair.
Lazy 2/3 majority of active PMC members (excluding the member in question)
Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.
3.4.10. Modifying Bylaws
Modifying this document.
Lazy majority of active PMC members
Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.
3.4.11. Trademark Usage Approvals
Our project maintains a formal Trademark Usage Guidelines document, which serves as a additive reference to the Apache Software Foundation's trademark policies. The Apache CloudStack PMC has had approval authority delegated to it for requests from third parties to use our trademarks. It is the PMC's responsibility to provide these approvals, and to ensure that any requests are in compliance with both the project and the foundation's trademark usage policies.
The CloudStack Trademark Guidelines specify how a requestor is expected to request permission for usage of the trademarks.
The process of approval will typically be as follows: * A request is made that includes the required information for the PMC to make a decision.
A PMC member reviews the request and provides an initial acknowledgement response to the requester.
If no PMC member raises a concern after 72 hours, the requester can assume approval.
In situations where a concern is raised, the PMC member is expected inform the requster that there is some discussion that needs to be had prior to approval from the PMC. This notice serves to end the assumed approval after 72 hours.
After raising a concern, the PMC member in question is required to forward the concern to<EMAIL_ADDRESS>explaining the issue that they have with the request. The use of<EMAIL_ADDRESS>for discussing the request is to allow the PMC to deliberate without confusing the requester, and to ensure that a formal approval or denial is clear at the end of the discussion.
The PMC will then attempt to achieve consensus on how the request for approval will be answered. The requester may be asked for more information to help the PMC make a decision, may be asked to make a change to the proposal in order to gain approval, or may have their request be denied.
If consensus is not achieved within the PMC by discussion, then a formal VOTE can be called as a Lazy 2/3 majority of voting PMC members.
Votes related to trademark usage approvals may be performed on the<EMAIL_ADDRESS>mailing list.
3.5. Voting Timeframes
Formal votes are open for a period of at least 72 hours to allow all active voters time to consider the vote.


This time, it’s different.
Since the beginning of the Rolling Jubilee campaign, we’ve wanted to buy and abolish student debt. But most student loans are guaranteed by the federal government, and so they are not available for purchase. As part of our effort to buy private, unsecured student loans, we talked to Doug St. Peters, the Vice President of Portfolio Management at Sallie Mae, who packages that company’s debt into securities and sells your loans on the secondary market. He confirmed that Sallie Mae does sell its private loans to two large debt buying companies. He would not name names, and he refused to sell us any of these portfolios when he learned that we intended to abolish the debt.
According to St. Peters, private Sallie Mae loans are sold for as little as 15 cents on the dollar. We repeat: a Vice President at Sallie Mae confirmed that they sell private loans for 15 cents on the dollar.
One goal of the Rolling Jubilee campaign has been to educate ourselves and others about how little our debts are actually worth to the creditors who control our lives. If you have a private Sallie Mae loan, you should know that it may be sold at pennies on the dollar, even as the lender and debt collectors demand full payment, plus interest, from you.
Though we were not able to purchase Sallie Mae loans, we have had some success with other portfolios, and we think those who have been petitioning us to buy student debt will be pleased with the results. We will share all of the details on September 17.
This will not be our last debt buy announcement. We are committed to spending all the funds donated to Rolling Jubilee to purchase and abolish debt. But we are also joining with others to develop long-term plans. Buying and abolishing debt is a powerful but limited tactic, and collective action is needed to address the systemic economic problems that force people into debt for basic needs like education.
Join The Movement
On September 17 we will launch a campaign to amplify ongoing protests against the privatization of our colleges and universities. Our latest debt buy is also an opportunity to promote the common-sense solutions that are being ignored by elected officials from, such as making all 2- and 4-year public colleges tuition free.
We encourage students around the country to join us on the week of September 17 by holding a rally or a debt assembly on your campus. You can learn more about how to host an assembly here. You can also read about a debt assembly held earlier this year by students at Southern Illinois University here.
As always, to our friends and families, we owe you everything. To the financial establishment of the world, we owe you nothing.


| Methods' Details |
reset
- Description
- resets the image manager to default data.
This means that all user images of the instance will be removed.
|
|
getAllImageNames
| sequence< string > |
| getAllImageNames( |
[in] short |
nImageType ); |
- Description
- retrieves the list of command URLs which have images associated.
- Parameter nImageType
- specifies the image type for this operation.
- Returns
- all command URLs within the images manager that have an image
associated.
|
|
hasImage
- Description
- determines if a command URL has an associated image.
- Parameter nImageType
- specifies the image type for this operation.
- Parameter ResourceURL
- a command URL that should be checked for an associated image.
- Returns
- true if an image is associated, otherwise false.
|
|
getImages
- Description
- retrieves the associated images of command URLs.
- Parameter nImageType
- specifies the image type for this association operation.
- Parameter aCommandURLSequence
- a sequence of command URLs for which the images are requested.
- Returns
- a sequence of graphics object which are associated with the
provided command URLs. If an unknown command URL is provided or
a command URL has no associated image a graphics object with an
empty image is provided. If the sequence
aCommandURLSequence contains an invalid command
URL a ::com::sun::star::lang::IllegalArgumentException
is thrown.
|
|
replaceImages
- Description
- replaces the associated images of command URLs.
- Parameter nImageType
- specifies the image type for this association operation.
- Parameter aCommandURLSequence
- a sequence of command URLs for which images should be replaced.
- Parameter aGraphicsSequence
- a sequence of graphic objects which should replace the old images
of the provided command URLs.
If a command URL cannot be found the replace call will be omitted. If
aCommandURLSequence contains an invalid command URL a
::com::sun::star::lang::IllegalArgumentException
is thrown. If the image manager is associated with a read-only configuration
manager a ::com::sun::star::lang::IllegalAccessException
is thrown.
|
|
removeImages
- Description
- removes associated images to a command URL.
- Parameter nImageType
- specifies the image type for this association operation.
- Parameter aCommandURLSequence
- a sequence of command URLs for which the images should be removed.
If the aCommandURLSequence contains an invalid command URL a
::com::sun::star::lang::IllegalArgumentException is
thrown. If the image manager is associated with a read-only configuration
manager a ::com::sun::star::lang::IllegalAccessException
is thrown.
|
|
insertImages
- Description
- inserts new image/command associations to a image manager.
- Parameter nImageType
- specifies the image type for this association operation.
- Parameter aCommandURLSequence
- a sequence of command URLs which specify which commands get an new image.
- Parameter aGraphicSequence
- a sequence of graphic objects which should be associated with the provided
command URLs.
If an association is already present it is replaced. If
aCommandURLSequence contains an invalid command URL a
::com::sun::star::lang::IllegalArgumentException
is thrown. If the configuration manager is read-only a
::com::sun::star::lang::IllegalAccessException is
thrown.
|
|
Copyright © 2013, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


Forward 3
Web Technology Summit
What is this presentation?
Two primary categories
- Exciting things that can be used in an existing project.
- Exciting things that might not be usable for an existing project.
What is Forward Web Technology Summit?
- A full-day of talks and discussion about
- Web Technologies
- Technology Architecture and Philosophy
- The Technology Community
- A series of full-day hands-on courses to expose current and emerging technologies
- A place to get free t-shirts suitable for sleeping in
Why "Technology Summit?"
Originally "Forward JS" focused almost entirely on Javascript.
Javascript is becoming more of an end product.
There was a severe lack of animated gifs in presentations (not actually true)
Exciting Nowness - ES6
Brian Holt - ES6 Features
- Tail calls (recursive optimization)
- Tail calls (recursive optimization)
- Tail calls (recursive optimization)
Exciting Nowness - ES6
Brian Holt - ES6 Features
- for(let val of iteratableObj){doStuff()}
- spread operator (...)
function greetMany(greeting, ...names) {}
greetMany('what up', 'Saul Goodman', 'Olivia Godfrey');
- destructuring
function greetStillMore(obj={greeting:'hi there', names:[]}) {
const {greeting, names} = obj;
names.map(function(name) {
console.log(`${greeting} ${name}!`);
});
};
Babel?
Babel JS
- Javascript "transpiler"
- Turns new js into "old" js
- Intelligently optimizes code while parsing
- Integrates into tooling
- Ties into most build systems
- Hooks into unit test frameworks
Babel!
Better Practices: new syntax improves debugging
*shudder* Future Proof: allows teams to write accepted, future-facing syntax now
Extensible: extensible apis allow workflows to be customized
States and Nomads
Zach Tellman - States and Nomads
Not every tool applies to every situation
Not every situation calls for a new tool
Holistic systems have more value over solutions developed in a vacuum
Exciting Future
- IOT (Johnny-Five and Arduino)
- IOT (PubNub and Raspberry Pi)
- ReactJS
IOT (arduino + johnny five)
Arduino
- Small, hackable processor and control board.
- Great for lightweight, low power projects.
- Large community and support.
Johnny Five
- Node JS/Javascript interface for hardware.
- Supports most Arduino-based hardware and related attachments.
- Using the nodebots-workshop package is a great hands-on way to learn.
IOT (pi with pubnub and... python?)
Raspberry Pi
- Inexpexnsive, self-contained, hackable computer platform (runs varieties of linux)
- Can handle hardware hooked up directly to cpu board via programmable pins
- Many accessories for extending functionality
PubNub
- SaaS provider of lightweight messaging managment (32k max message size).
- Built-in analytics, debugging tools, API's
- Useful for connecting many independent self-aware robots
React JS
Brian Holt - React with ES6
- Powerful UI component framework
- Focused around components and state rather than MV+ separation of responsibilities
- A way to make communicative, autonomous UI elements without a large amount of scaffolding
- Will bend your brain the first time you try to use it
- My code from the workshop
Elm
elm-lang.org
- Functional language designed for browsers
- Robust type system alleviates common and hard-to-trace errors
- Minimalist syntax, but not Ruby minimal
Rust + Node
Rust Language
Rust + Node code
- Really, really fast language
- Compiler catches most things before code runs
- Thread safe
- Compiled code can be included as a library in other langs to optimize slow parts
Signal Processing
Myles Borins - Signal Processing
- Great intro to digital audio processing
- Interesting theories on music
- Has a neat demo of Famous and WebGL towards the end
-


About Estimated Support
In february 2020, we rolled out a new functionality called Estimated support. This will give you a clue of how widely supported every HTML and CSS features tested on the site is. In july 2021, this feature was updated to no longer reflect an estimation of email clients market share but instead to be a share of all the clients tested on Can I email.
If a feature is tested across 10 email clients, and that this feature is supported in six clients, partially supported in three clients and not supported in one client, its estimated support will be: 60% supported, 30% partially supported and 10% not supported.
The support value taken into account is the one of the latest version of an email client.
For historical purpose, the archive of this page is readable below.
Archive
Up until july 2021, the market share data was provided by EmailClientMarketShare.com, a service ran by Litmus.
While we think this is a valuable functionality to help make technical choices, it is important to keep in mind how email tracking works and how accurate (or how inaccurate) this data can be. So here are a few things worth noting.
Email tracking is inherently flawed.
In order to keep track of email clients, there are two methods used conjointly:
- Use an invisible image (aka tracking pixel). When this image gets downloaded, we can know which email client triggered the download.
- Use a custom link tracking. When you click on a link, we can know where you came from before.
This means that if somebody consults your email with images turned off and doesn't click any link, this person (and its email client) will be totally ignored from your analytics. In 2013, Campaign Monitor published a benchmark of opens by environment based on 1.8 billion opens… from nearly 22 billions email recipients. This means that we have no clue what happens for 20.2 billions of those recipients.
This also means that any email client that displays images by default will be advantaged. This was particularily visible in EmailClientMarketShare.com in late 2013. In december 2013, Gmail accounted for 3.02% of market share according to the site. At that time, Gmail still blocked images by default. In december 2013, Gmail finally turned images on for everyone by default. In January 2014, Gmail accounted for 9.05% of market share according to the same site. That 300% jump is not related to any specific push or new market from Gmail. It's only because images were now visible for everyone, and thus emails could be tracked by analytics.
Different email clients may be reported as the same.
Due to the nature of how certain email applications or webmails work, it is not always possible to have precise measures of which email client version is used precisely. According to Litmus:
In some cases, opens made in third-party email applications will appear in your stats as mobile webmail opens (for example, the AOL Mail iOS app appears as "AOL Mail using iPhone"). Custom applications, like Mailbox, that use WebKit as their rendering engine will appear as native iPhone mail app opens (for example, Mailbox appears as "Apple iPhone"). When this happens, Email Analytics is unable to differentiate between the native iPhone application and the Mailbox application because they both use WebKit to render, and provide the same type of identifying information back to us.
Some email clients also use proxies to serve images. This makes it harder to distinguish the platform under which the email client is used. For example, it is not possible to distinguish Gmail between its desktop webmail, mobile webmail, iOS app or Android app.
Another example is Outlook. In Litmus' data, Outlook accounts for both the Windows and macOS desktop applications. Those two applications are vastly different (the former using Word's rendering engine while the latter uses WebKit, resulting in much better support regarding HTML and CSS in general).
To display an estimated support for those categories, we will determinate an average of the support across all matching clients. For example, if Outlook on macOS supports a certain feature but Outlook on Windows does not, then this feature will be shown as being Partially Supported on Outlook.
If you want to see exactly how we match Litmus' data to Can I email's data, you can take a look at the file _data/emailclientmarketshare.yml
available in our source code on GitHub.
Other things worth mentioning.
- Litmus tracks email clients we don't. (Currently: Apple iPad, Google Android and Windows Live Mail).
- We match market share only to the latest tested version of an email client. So if something is supported in Outlook 2019 but not in Outlook 2016, we won't be able to account for this difference and Outlook's market share will be associated with the feature as supported.
- Some email clients we track are not tracked by Litmus. For example, we keep track of french email clients from Orange that are not accounted in Litmus top 10.
- Litmus top ten doesn't add up to 100%.


Lim Jae Hyun to also take legal action against Park Kyung
by jennywillLim Jae Hyun will be taking legal action against Park Kyung.
Yesterday, Park Kyung had called out artists who were accused of chart manipulation, specifically calling out Vibe, Song Ha Ye, Lim Jae Hyun, Jeon Sang Keun, Jang Deok Cheol, and Hwan In Wook. Vibe had already responded that they would be taking legal action against Park Kyung without any settlement, and now Lim Jae Hyun has also joined them.
HNS HQ, his label, said, "We are letting you know that the accusations that Park Kyung made on November 24th against our label artist are completely false. Chart manipulation is a crime, and we clearly state that our label and our artist has not participated in such criminal activity. We are severely disappointed that Park Kyung named us as criminals and publicly defamed us. We will be asking him to take responsibility for his actions and take legal measures."


/* This file is part of Ext JS 4 Copyright (c) 2011 Sencha Inc Contact: http://www.sencha.com/contact Commercial Usage Licensees holding valid commercial licenses may use this file in accordance with the Commercial Software License Agreement provided with the Software or, alternatively, in accordance with the terms contained in a written agreement between you and Sencha. If you are unsure which license is appropriate for your use, please contact the sales department at http://www.sencha.com/contact. */ /** * @author Ed Spencer * * Simple class that represents a Request that will be made by any {@link Ext.data.proxy.Server} subclass. * All this class does is standardize the representation of a Request as used by any ServerProxy subclass, * it does not contain any actual logic or perform the request itself. */ Ext.define('Ext.data.Request', { /** * @cfg {String} action * The name of the action this Request represents. Usually one of 'create', 'read', 'update' or 'destroy'. */ action: undefined, /** * @cfg {Object} params * HTTP request params. The Proxy and its Writer have access to and can modify this object. */ params: undefined, /** * @cfg {String} method * The HTTP method to use on this Request. Should be one of 'GET', 'POST', 'PUT' or 'DELETE'. */ method: 'GET', /** * @cfg {String} url * The url to access on this Request */ url: undefined, /** * Creates the Request object. * @param {Object} [config] Config object. */ constructor: function(config) { Ext.apply(this, config); } });


--- layout: post title: Top Tips and Handy Hacks for Git tags: - Git - LinkedIn - Work Practices status: publish type: post published: true meta: _edit_last: '451289' _wpas_skip_linkedin: '1' --- Last updated 7/June/2012 I don't think any of these ideas are originally mine and I apologise that I do no longer have the correct information to credit the appropriate people. This is my place to put some of the tips and tricks I come across when using Git. There are of course lots of other places on the inter tubes that provide better tips. These are just mine and I'll update this over time
git config --get user.email
) and if needed set the email address to different value on the repo by omitting the --global
option to the command git config user.email<EMAIL_ADDRESS>)git config --global core.excludesfile ~/.gitignore
git config --global core.autocrlf input
(see GitHub help), but beware of lots of apparent line ending changes after setting this , these are benign.git config --global help.format web
. N.B. Needs the html version of the Git documents installed. Don't like the default browser? Run git config --global web.browser chromium
https
instead of git
as your transport protocol? You can now use various helper programs to cache your https credentials. The GitHub setup help page has details for each platformgit config --global alias.bfg '!java -jar ~/bin/bfg.jar'
with the
correct path and name for your jar PS1='[\u@\h \W$(__git_ps1 " (%s)")]\$ '
. If you cannot locate the bash completions file on your system then you can get a copy from the Git source treegit config --global core.editor=....
) export GIT_EDITOR="/usr/bin/gvim --nofork"
. See below for more Vim tips


#include <Message.h>
Public Member Functions | |
| QPID_MESSAGING_EXTERN | Message (qpid::types::Variant &) |
| QPID_MESSAGING_EXTERN | Message (const std::string &bytes=std::string()) |
| QPID_MESSAGING_EXTERN | Message (const char *, size_t) |
| QPID_MESSAGING_EXTERN | Message (const Message &) |
| QPID_MESSAGING_EXTERN Message & | operator= (const Message &) |
| QPID_MESSAGING_EXTERN void | setReplyTo (const Address &) |
| QPID_MESSAGING_EXTERN const Address & | getReplyTo () const |
| QPID_MESSAGING_EXTERN void | setSubject (const std::string &) |
| QPID_MESSAGING_EXTERN const std::string & | getSubject () const |
| QPID_MESSAGING_EXTERN void | setContentType (const std::string &) |
| QPID_MESSAGING_EXTERN const std::string & | getContentType () const |
| QPID_MESSAGING_EXTERN void | setMessageId (const std::string &) |
| QPID_MESSAGING_EXTERN const std::string & | getMessageId () const |
| QPID_MESSAGING_EXTERN void | setUserId (const std::string &) |
| QPID_MESSAGING_EXTERN const std::string & | getUserId () const |
| QPID_MESSAGING_EXTERN void | setCorrelationId (const std::string &) |
| QPID_MESSAGING_EXTERN const std::string & | getCorrelationId () const |
| QPID_MESSAGING_EXTERN void | setPriority (uint8_t) |
| QPID_MESSAGING_EXTERN uint8_t | getPriority () const |
| QPID_MESSAGING_EXTERN void | setTtl (Duration ttl) |
| QPID_MESSAGING_EXTERN Duration | getTtl () const |
| QPID_MESSAGING_EXTERN void | setDurable (bool durable) |
| QPID_MESSAGING_EXTERN bool | getDurable () const |
| QPID_MESSAGING_EXTERN bool | getRedelivered () const |
| QPID_MESSAGING_EXTERN void | setRedelivered (bool) |
| QPID_MESSAGING_EXTERN const qpid::types::Variant::Map & | getProperties () const |
| QPID_MESSAGING_EXTERN qpid::types::Variant::Map & | getProperties () |
| QPID_MESSAGING_EXTERN void | setProperties (const qpid::types::Variant::Map &) |
| QPID_MESSAGING_EXTERN void | setContent (const std::string &) |
| QPID_MESSAGING_EXTERN void | setContent (const char *chars, size_t count) |
| QPID_MESSAGING_EXTERN std::string | getContent () const |
| QPID_MESSAGING_EXTERN std::string | getContentBytes () const |
| QPID_MESSAGING_EXTERN void | setContentBytes (const std::string &) |
| QPID_MESSAGING_EXTERN qpid::types::Variant & | getContentObject () |
| QPID_MESSAGING_EXTERN const qpid::types::Variant & | getContentObject () const |
| QPID_MESSAGING_EXTERN void | setContentObject (const qpid::types::Variant &) |
| QPID_MESSAGING_EXTERN const char * | getContentPtr () const |
| QPID_MESSAGING_EXTERN size_t | getContentSize () const |
| QPID_MESSAGING_EXTERN void | setProperty (const std::string &, const qpid::types::Variant &) |
Friends | |
| struct | MessageImplAccess |
Representation of a message.
| QPID_MESSAGING_EXTERN std::string qpid::messaging::Message::getContent | ( | ) | const |
Get the content as a std::string
| QPID_MESSAGING_EXTERN std::string qpid::messaging::Message::getContentBytes | ( | ) | const |
Get the content as raw bytes (an alias for getContent()
| QPID_MESSAGING_EXTERN qpid::types::Variant& qpid::messaging::Message::getContentObject | ( | ) |
Get the content as a Variant, which can represent an object of different types. This can be used for content representing a map or a list for example.
| QPID_MESSAGING_EXTERN const qpid::types::Variant& qpid::messaging::Message::getContentObject | ( | ) | const |
Get the content as a Variant, which can represent an object of different types. This can be used for content representing a map or a list for example.
| QPID_MESSAGING_EXTERN const char* qpid::messaging::Message::getContentPtr | ( | ) | const |
Get a const pointer to the start of the content data. The memory pointed to is owned by the message. The getContentSize() method indicates how much data there is (i.e. the extent of the memory region pointed to by the return value of this method).
| QPID_MESSAGING_EXTERN size_t qpid::messaging::Message::getContentSize | ( | ) | const |
Get the size of content in bytes.
| QPID_MESSAGING_EXTERN const std::string& qpid::messaging::Message::getContentType | ( | ) | const |
Returns the content type (i.e. the MIME type) for the message. This can be used to determine how to decode the message content.
| QPID_MESSAGING_EXTERN const qpid::types::Variant::Map& qpid::messaging::Message::getProperties | ( | ) | const |
In addition to a payload (i.e. the content), messages can include annotations describing aspectf of the message. In addition to the standard annotations such as TTL and content type, application- or context- specific properties can also be defined. Each message has a map of name values for such custom properties. The value is specified as a Variant.
| QPID_MESSAGING_EXTERN bool qpid::messaging::Message::getRedelivered | ( | ) | const |
The redelivered flag if set implies that the message may have been previously delivered and thus is a hint to the application or messaging infrastructure that if de-duplication is required this message should be examined to determine if it is a duplicate.
| QPID_MESSAGING_EXTERN Duration qpid::messaging::Message::getTtl | ( | ) | const |
Get the time to live for this message in milliseconds.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setContent | ( | const std::string & | ) |
Set the content to the data held in the string parameter. Note: this is treated as raw bytes and need not be text. Consider setting the content-type to indicate how the data should be interpreted by recipients.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setContent | ( | const char * | chars, |
| size_t | count | ||
| ) |
Copy count bytes from the region pointed to by chars as the message content.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setContentBytes | ( | const std::string & | ) |
Set the content as raw bytes (an alias for setContent()
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setContentObject | ( | const qpid::types::Variant & | ) |
Set the content using a Variant, which can represent an object of different types.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setContentType | ( | const std::string & | ) |
Set the content type (i.e. the MIME type) for the message. This should be set by the sending application and indicates to recipients of message how to interpret or decode the content.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setCorrelationId | ( | const std::string & | ) |
Can be used to set application specific correlation identifiers as part of a protocol for message exchange patterns. E.g. a request-reponse pattern might require the correlation-id of the request and response to match, or might use the message-id of the request as the correlation-id on the response etc.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setDurable | ( | bool | durable | ) |
Mark the message as durable. This is a hint to the messaging infrastructure that the message should be persisted or otherwise stored such that failoures or shutdown do not cause it to be lost.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setMessageId | ( | const std::string & | ) |
Set an application defined identifier for the message. At present this must be a stringfied UUID (support for less restrictive IDs is anticipated however).
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setPriority | ( | uint8_t | ) |
Sets a priority level on the message. This may be used by the messaging infrastructure to prioritise delivery of higher priority messages.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setRedelivered | ( | bool | ) |
Can be used to provide a hint to the application or messaging infrastructure that if de-duplication is required this message should be examined to determine if it is a duplicate.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setTtl | ( | Duration | ttl | ) |
Set the time to live for this message in milliseconds. This can be used by the messaging infrastructure to discard messages that are no longer of relevance.
| QPID_MESSAGING_EXTERN void qpid::messaging::Message::setUserId | ( | const std::string & | ) |
Sets the user id of the message. This should in general be the user-id as which the sending connection authenticated itself as the messaging infrastructure will verify this. See Connection::getAuthenticatedUsername()


Classes
The following classes are available globally.
-
Measurement class.
See moreDeclaration
Swift
@objc(Measurement) public final class _ObjCMeasurement : NSObject
-
Payment item model.
See moreDeclaration
Swift
@objcMembers public final class PaymentItem : NSObject
-
Acquirer information class.
See moreDeclaration
Swift
@objcMembers public final class Acquirer : NSObject, Decodable
-
Address model.
See moreDeclaration
Swift
@objcMembers public final class Address : Decodable
-
Amount modificator class, used for taxes and doscount models.
See moreDeclaration
Swift
@objcMembers public class AmountModificator : NSObject, Codable
-
Authentication class.
See moreDeclaration
Swift
@objcMembers public final class Authentication : NSObject, IdentifiableWithString
-
Authorize object.
See moreDeclaration
Swift
@objcMembers public final class Authorize : NSObject, AuthorizeProtocol, IdentifiableWithString
-
Authorize action model.
See moreDeclaration
Swift
@objcMembers public class AuthorizeAction : NSObject, Codable
-
Authorize action response class.
See moreDeclaration
Swift
@objcMembers public final class AuthorizeActionResponse : AuthorizeAction
-
Card Verification class.
See moreDeclaration
Swift
@objcMembers public class CardVerification : NSObject, Decodable, IdentifiableWithString
-
Charge model. To charge a credit or a debit card, you create a charge object. You can retrieve and refund individual charges as well as list all charges. Charges are identified by a unique random ID.
See moreDeclaration
Swift
@objcMembers public final class Charge : NSObject, ChargeProtocol, IdentifiableWithString
-
Currency structure.
See moreDeclaration
Swift
@objcMembers public final class Currency : NSObject
-
Customer model.
See moreDeclaration
Swift
@objcMembers public final class Customer : NSObject, Decodable, OptionallyIdentifiableWithString
-
Destination model.
See moreDeclaration
Swift
@objcMembers public final class Destination : NSObject, Codable, IdentifiableWithString
-
Group of destinations.
See moreDeclaration
Swift
@objcMembers public final class DestinationGroup : NSObject, Decodable
-
Email address model.
See moreDeclaration
Swift
@objcMembers public final class EmailAddress : NSObject
-
Structure representing API error.
See moreDeclaration
Swift
@objcMembers public final class APIError : NSObject, Codable
-
Error detail model.
See moreDeclaration
Swift
@objcMembers public final class ErrorDetail : NSObject
-
API error.
See moreDeclaration
Swift
@objcMembers public final class TapSDKAPIError : TapSDKError
-
Base abstract class for errors.
See moreDeclaration
Swift
@objcMembers public class TapSDKError : NSObject, Encodable
-
Known error. Either network or serialization error.
See moreDeclaration
Swift
@objcMembers public final class TapSDKKnownError : TapSDKError
-
Unknown or unhandled error.
See moreDeclaration
Swift
@objcMembers public final class TapSDKUnknownError : TapSDKError
-
Phone number model.
See moreDeclaration
Swift
@objcMembers public final class PhoneNumber : NSObject
-
Quantity model.
See moreDeclaration
Swift
@objcMembers public final class Quantity : NSObject, Encodable
-
Receipt dispatch settings.
See moreDeclaration
Swift
@objcMembers public final class Receipt : NSObject, OptionallyIdentifiableWithString, Codable
-
Reference object.
See moreDeclaration
Swift
@objcMembers public final class Reference : NSObject, Codable
-
Response structure.
See moreDeclaration
Swift
@objcMembers public final class Response : NSObject
-
Saved Card model.
See moreDeclaration
Swift
@objcMembers public final class SavedCard : NSObject, OptionallyIdentifiableWithString
-
Secret key class.
See moreDeclaration
Swift
@objcMembers public final class SecretKey : NSObject
-
Shipping data model class.
See moreDeclaration
Swift
@objcMembers public final class Shipping : NSObject, Codable
-
Source model.
See moreDeclaration
Swift
@objcMembers public final class Source : SourceRequest
-
Source request model for the charge.
See moreDeclaration
Swift
@objcMembers public class SourceRequest : NSObject, IdentifiableWithString, Encodable
-
Tax data model.
See moreDeclaration
Swift
@objcMembers public final class Tax : NSObject, Codable
-
Token model.
See moreDeclaration
Swift
@objcMembers public final class Token : NSObject, IdentifiableWithString
-
Tokenized card model.
See moreDeclaration
Swift
@objcMembers public final class TokenizedCard : IdentifiableWithString
-
Redirect model.
See moreDeclaration
Swift
@objcMembers public final class TrackingURL : NSObject
-
Transaction details model.
See moreDeclaration
Swift
@objcMembers public final class TransactionDetails : NSObject
-
Transfer model.
See moreDeclaration
Swift
@objcMembers public final class Transfer : NSObject, OptionallyIdentifiableWithString, Decodable
-
Pay button.
See moreDeclaration
Swift
@objcMembers public final class PayButton : TapNibView, SessionProtocol
-
Base settings class for goSell SDK.
See moreDeclaration
Swift
@objcMembers public final class GoSellSDK : NSObject
-
SDK session class. Use this class if you don’t want to place Pay Button and make it do everything for you.
See moreDeclaration
Swift
@objcMembers public final class Session : NSObject, SessionProtocol
-
Blur style.
- none: No blur.
- light: Light blur
- extraLight: Extra light blur
- dark: Dark blur
- regular: Regular blur
- prominent: Prominent blur.
Declaration
Swift
@objc public final class TapBlurStyle : NSObject


1.27.x Stable Releases
This document describes releases leading up to the 1.27.x stable series.
The 1.27.x series deprecates several unused backends and plugins. Please see https://groups.google.com/forum/#!topic/pants-devel/ngMZRIJvwHM for more information.
1.27.1rc0 (6/16/2020)
N.B.: No further releases are expected in the 1.27.x stable series. This .1rc0 release is for those upgrading through stable versions who wish to retain pytest console coverage support in Pants "v1".
Bugfixes
- Restore pytest coverage console report. (#10016) PR #10016
1.27.0 (5/20/2020)
The first stable release in the 1.27.x series, with no changes since the previous release candidate!
1.27.0rc2 (5/15/2020)
API Changes
- Deprecate, instead of error, when Python targets have non-Python sources (#9752) PR #9752
Bugfixes
- Fix Target API bindings not loading for plugins (#9789) PR #9789
1.27.0rc1 (5/7/2020)
Bugfixes
- Fix crash when V2 goals like repl have no specified targets (#9673) PR #9673
- Temporarily disable ./pants backends goal due to bug (#9629) PR #9629
- Fix zip_safe field not being used with V2 binary (#9598) PR #9598
- Fix typo in V1 Python interpreter selection error message (#9589) PR #9589
- Revert allowing Python targets to include .c files in their sources (#9583) PR #9583
1.27.0rc0 (4/17/2020)
API Changes
New Features
- More flexible binary and run rules. (#9529) PR #9529
Bugfixes
- Don't report diagnostics for cached targets (#9492) PR #9492
- Add link back to source control dir from physical workdir (#9531) PR #9531
- Fix V2 binary still using the current platform when platforms is specified (#9563) Issue #957 PR #9563
- Propagate the owners_not_found_behavior to FilesystemSpec expansion. (#9551) PR #9551
- [junit-runner] simplify fail fast (#9403) PR #9403
- Fix workdir symlink's destination/physical dir not always created (#9504) PR #9504
Refactoring, Improvements, and Tooling
- Add rules to determine if configurations or targets have non-empty sources (#9521) PR #9521
- Allow target_types2 register.py entry point to register new symbols (#9558) PR #9558
- Remove several unused TargetAdaptor utility rules (#9569) PR #9569
- Remove the fork_context method and support code. (#9554) PR #9554
- Convert repl goal to the new Targets API (#9565) PR #9565
- Port V2 Pytest Coverage to use the Target API (#9556) PR #9556
- Remove unused HydratedTargetWithOrigin (#9553) PR #9553
- Port setup-py2 to use the Target API (#9547) PR #9547
- Some refactoring in EngineDisplay (#9546) PR #9546
- Remove unused TargetAdaptorWithOrigin (#9544) PR #9544
- Drop normpath comparison, the vast majority of which is covered by the other checks. (#9538) PR #9538
- Port V2 fmt and lint to use Target API (#9537) PR #9537
- Rename ExecuteProcessRequest to Process and ExecuteProcessResult to ProcessResult (#9535) PR #9535
- Factor out a util function to parse a requirement constraint. (#9533) PR #9533
- Utilities to create subsystem instances. (#9528) PR #9528
- Convert RankedValue int ranks to Enum. (#9526) PR #9526
- Add PantsdRunContext context to pantsd tests (#9518) PR #9518
- Refactor V2 Pytest Coverage implementation (#9549) PR #9549
Testing
Documentation
- Prepare 1.26.0rc2. (#9550) PR #9550
1.27.0.dev3 (4/13/2020)
API Changes
- Deprecate source in favor of sources (#9471) PR #9471
- Deprecate unused backends (#9512) PR #9512
- Deprecate unused plugins (#9508) PR #9508
- Remove broken indices and repos fields from python_binary (#9497) PR #9497
- Delay deprecation of lint.pythonstyle and V1 isort to 1.28.0.dev0 (#9503) PR #9503
- Upgrade to pex 2.1.9. (#9489) PR #9489
- Update node.js dependencies. (#9474) PR #9474
New Features
- Add ./pants backends to list all available backend packages (#9468) PR #9468
- Add --pants-use-gitignore option (#9310) PR #9310
- Wire up python-repos options to V2 Pex usage (#9495) PR #9495
- Port dependencies2 to use the Target API and to work with JARs (#9494) PR #9494
- Add a flag to prevent the FsEventService and watchman from starting (#9487) PR #9487
- Add respect strict dep option for export-dep-as-jar (#9482) PR #9482
Bugfixes
Refactoring, Improvements, and Tooling
- Add a mypy plugin to support @total_ordering. (#9525) PR #9525
- Allow intrinsics to have multiple input arguments (#9527) PR #9527
- Port the fs crate(s) to async-await (#9473) PR #9473
- Bump to grpcio 0.5.1. (#9470) PR #9470
- Bump to tokio 0.2.16. (#9467) PR #9467
- Revert "Bump to tokio 0.2.16. (#9467)" (#9477) PR #9477
- Rename CreatePex to PexRequest and add Target API support (#9480) PR #9480
- Rename ChrootedPythonSources to ImportablePythonSources and add Target API support (#9479) PR #9479
- Attach a description to PexRequests. (#9523) PR #9523
- Add ScalarField and SequenceField templates (#9465) PR #9465
- Allow Sources subclasses to specify the # of expected files (#9466) PR #9466
- Fix targets that do not have a dependencies field with the Target API (#9481) PR #9481
- Don't show V1 bindings when exclusively using V2 (#9511) PR #9511
- Port AWS Lambda (V1 and V2) to use the Target API (#9491) PR #9491
- Port ./v2 test to use the Target API (#9484) PR #9484
- Add Target API bindings for python_dist, python_requirement_library, and unpacked_whls (#9475) PR #9475
- Add Target API bindings for backend/codegen and backend/docgen (#9486) PR #9486
- Add Target API bindings for python_app and jvm_app (#9490) PR #9490
- Add Target API bindings for pants-plugins (#9488) PR #9488
- Avoid needless instantiation of LocalPantsRunner (#9501) PR #9501
- Revert "Avoid needless instantiation of LocalPantsRunner (#9450)" (#9499) PR #9499
- Avoid needless instantiation of LocalPantsRunner (#9450) PR #9450
- Add some type annotations to pantsd test helpers (#9517) PR #9517
- Move the WorkUnitStore to a thread/task local (#9522) PR #9522
- Avoid recomputing a BuildFileAddress when subclassing will do. (#9472) PR #9472
- Do not mix platforms and interpreter constraints while building release pexes (#9515) PR #9515
- Distinguish pex sources from additional input files. (#9514) PR #9514
- Build PEX files in two steps. (#9516) PR #9516
- Leverage PEX_ROOT for Pex CLI. (#9513) PR #9513
- Create @named_rule`s and add additional annotations to rules (#9453) `PR #9453
- [IDE] Precompute flattened dependencies for modulizable targets (#9311) PR #9311
- Reorder commit hooks by stack depth. (#9524) PR #9524
- Improve CI skips in git commit hooks (#9496) PR #9496
- Add convert_source_to_sources.py script to help users migrate away from deprecated source field (#9309) PR #9309
Testing
- Fix test that depends on a Python stdlib line number (#9493) PR #9493
1.27.0.dev2 (4/3/2020)
API Changes
New Features
- Make the list of JS lintable extensions configurable (#9423) PR #9423
- Improve formatting of ./pants help (#9411) PR #9411
- Improve formatting of ./pants goals and ./pants target-types2 (#9414) PR #9414
- Improve formatting of target-types2 --details (#9410) PR #9410
- Implement Cobertura output option for #9275 (#9325) PR #9325
- Add notify fs watcher to engine. (#9318) PR #9318
- Pass all python_binary fields to V2 binary and run (#9449) PR #9449
- Add list-v2 to work with the Target API (#9433) PR #9433
- Port filedeps2 to use the Target API and add the missing --transitive option (#9459) PR #9459
Bugfixes
- Fix equality and hashing of engine.Collection (#9437) PR #9437
- fix accidentally double-registering setuptools for ipex (#9341) PR #9341
- fix --tag filtering when a TargetAdaptor has None for the 'tags' kwarg (#9443) PR #9443
- Eliminate PEX_ROOT warning for CreatePex. (#9418) PR #9418
- Don't rerun uncachable nodes if they are dirtied while running. (#9452) PR #9452
- Ignore notify events for pants_ignore patterns. (#9406) PR #9406
Refactoring, Improvements, and Tooling
- Provide better TypeError in extern_identify hash failure (#9430) PR #9430
- Allow a StringField to require one of several choices (enum) (#9461) PR #9461
- Formalize marking fields as required (must be defined in the BUILD file) (#9392) PR #9392
- Add DictStringToStringField and DictStringToStringSequenceField field templates (#9455) PR #9455
- Add support for getting the direct and transitive dependencies of a Target (#9440) PR #9440
- Fallback in target-types2 to the docstring from parent Fields when not available (#9404) PR #9404
- Add Target API bindings for contrib/cpp and backend/native (#9445) PR #9445
- Add Target API bindings for backend/jvm (#9460) PR #9460
- Add Target API bindings for contrib/node and contrib/scalajs (#9447) PR #9447
- Add Target API bindings for contrib/go (#9444) PR #9444
- Add Target API bindings for build_graph target types (#9425) PR #9425
- Store the Filespec on the Sources field (#9458) PR #9458
- Remove unused JarDependency parameter. (#9457) PR #9457
- Remove unused variables from _register_rules (#9432) PR #9432
- Fix misleading comment. (#9424) PR #9424
Testing
- Use GlobMatchErrorBehavior.error in TestBase (#9456) PR #9456
- Cache native_engine.so in AWS in CI to avoid unnecessary Rust compilation (#9413) PR #9413
- Store CI objects in S3 based on lifetime. (#9438) PR #9438
- Refactor CI bootstrap shards setup to prepare for caching native_engine.so (#9409) PR #9409
- Fix uploading native_engine.so to AWS too many times in CI (#9451) PR #9451
- Move Build Wheels shards lower in CI order (#9383) PR #9383
- Skip 2 flaky tests and bump 2 test timeouts (#9422) PR #9422
- Skip flaky artifact cache and RSC compile tests (#9439) PR #9439
- Skip flaky TestArtifactCache test. (#9427) PR #9427
- Skip flaky TestPantsDaemonIntegration test. (#9421) PR #9421
- Skip flaky PytestRunTimeoutIntegrationTest test. (#9442) PR #9442
- break up flaky python integration tests that keep timing out (#9408) PR #9408
- Fix incorrect guidance for running fmt. (#9419) PR #9419
1.27.0.dev1 (3/26/2020)
API Changes
New Features
- Visualize the rule graph for @goal_rules. (#9377) PR #9377
- Add ./pants targets-types2 goal (#9376) PR #9376
- Plumb Pants log level to PEX_VERBOSE in v2. (#9328) PR #9328
- Report warnings and errors to reporting server for JVM targets (#9293) PR #9293
- Support opening coverage reports. (#9323) PR #9323
- Add Cobertura output option for Scoverage (#9275) PR #9275
- Add support for pytest-cov console reports. (#9302) PR #9302
Bugfixes
- Fix use of pid (#9400) PR #9400
- Use pants_workdir global option in run goal (#9381) PR #9381
- Make roots goal work with the buildroot. (#9378) PR #9378
- Change google maven mirror url (#9352) PR #9352
- Fix PathGlobs to be deterministic for more cache hits (#9347) PR #9347
- don't match the interpreter patch version for .ipex files! (#9285) PR #9285
- A newtype for the requirements.txt file dep. (#9307) PR #9307
- [jvm] use LUB when reusing cached dists; add breadcrumbs to Location (#9274) PR #9274
- Revision: ensure that 1 < 1.0.1; reformat test cases to use bare asserts (#9290) PR #9290
Refactoring, Improvements, and Tooling
- Filter sources when creating a pex. (#9405) PR #9405
- Make DaemonPantsRunner a dataclass (#9382) PR #9382
- Improve output of target-types2 goal (#9390) PR #9390
- Remove custom properties from nailgun (#9389) PR #9389
- Revert internally enforcing Flake8's E231 trailing comma lint (#9387) PR #9387
- Improve console output of binary and awslambda goals. (#9375) PR #9375
- Formalize default values for Fields (#9384) PR #9384
- Hotfix lint failure due to PR merge order conflict (#9385) PR #9385
- Internally enable Flake8 lints for is None, is False/True, and not in (#9379) PR #9379
- Add FrozenDict as an immutable wrapper around native dictionaries (#9366) PR #9366
- Move verification of configs out of OptionsBootstrapper (#9369) PR #9369
- Additional refactoring around pants initialization (#9368) PR #9368
- Enable E231 lint internally to check for bad trailing commas (#9364) PR #9364
- Refactor code pertaining to pants initialization (#9348) PR #9348
- Change the workunit description for requirement pex creation. (#9370) PR #9370
- Port to tokio 0.2, and to stdlib futures for fs and task_executor (#9071) PR #9071
- Add light-weight logic to Compatibility, Timeout, and Coverage Python fields (#9355) PR #9355
- Use V2 Flake8 internally instead of pants.contrib.python.checks (#9308) PR #9308
- Add runtime type checking to Fields (#9353) PR #9353
- Allow @goal_rule`s to request `Targets and demo with ./v2 binary run (#9345) PR #9345
- Move the global level option to an Enum. (#9327) PR #9327
- Update to latest num_enum (#9344) PR #9344
- Allow using Target API Field`s with `determine_source_files.py (#9342) PR #9342
- Make LocalPantsRunner a dataclass (#9339) PR #9339
- Change Target to have a similar interface to dict[t] and dict.get(t) (#9340) PR #9340
- Allow registering new target types with the Target API (#9334) PR #9334
- Allow stripping source roots from a Sources field (#9335) PR #9335
- Add some type-checking around PantsDaemon (#9336) PR #9336
- Minor follow up for 9259 (#9333) PR #9333
- Add Target.class_has_field (#9329) PR #9329
- Demonstrate use of the Target API with python_create_binary.py (#9316) PR #9316
- Add Target.has_field() as sugar for Target.has_fields() (#9314) PR #9314
- Add support for hydrating sources with the Target API (#9306) PR #9306
Testing
- Skip flaky RscCompileIntegrationYoutline test. (#9398) PR #9398
- Skip all flaky tests with GitHub issues. (#9391) PR #9391
- Skip Rust tests and JVM tests in CI when no respective changes were made (#9367) PR #9367
- Fix flaky pantsd test. (#9363) PR #9363
- Fix CI running for Jar publish commits (#9322) PR #9322
1.27.0.dev0 (3/14/2020)
API Changes
- Upgrade to pex 2.1.6. (#9255) PR #9255
- Remove deprecated pants.backend.python files moved to pants.python (#9238) PR #9238
- Remove deprecated --target-spec-file and --positional-arg-file in favor of --spec-file (#9237) PR #9237
- Remove deprecated --owner-of in favor of file arguments (#9235) PR #9235
- Remove deprecated --dependencies-internal-only and --dependencies-external-only (#9258) PR #9258
- Remove deprecated --fmt-skip and --lint-skip (#9254) PR #9254
- Revert removing --test-fast and delay the removal from 1.27.0.dev0 to 1.28.0.dev0 (#9251) PR #9251
- Revert "Load the bootstrapped zinc compiler from the zinc server's classpath. (#8753)" (#9226) PR #9226
- Stop defaulting to --transitive and remove the option when it no-ops (#9236) PR #9236
- Remove --glob-expansion-failure and deprecate --files-not-found-behavior=ignore (#9242) PR #9242
- Remove --test-fast to always have better test caching (#9241) PR #9241
- Remove deprecated dict_option, list_option, and target_list_option (#9243) PR #9243
- Deprecate --build-file-imports and remove its deprecated value allow (#9234) PR #9234
- Remove deprecated fmt and lint task options moved to subsystem options (#9246) PR #9246
- Deprecate V1 isort implementation in favor of improved V2 implementation (#9267) PR #9267
- Remove support for globs(), rglobs(), and zglobs() (#9247) PR #9247
New Features
- Add support for --dependencies-type=3rdparty to dependencies2 (#9225) PR #9225
- introduce --generate-ipex to (v1) python binary creation to lazy-load requirements (#8793) PR #8793
- [jvm] Add jvm_options to platform; use from junit and run (#9150) PR #9150
- Enable zinc to log diagnostics for jvm languages (#9228) PR #9228
- Rename fmt2 to fmt and lint2 to lint (#9257) PR #9257
Bugfixes
- Switch to a dict-backed OrderedSet impl. (#9305) PR #9305
- Prevent excessive uncached readlink's when using a symlinked workdir (#9270) PR #9270
- Fix interpreter constraints with V2 to AND multiple targets (#9265) PR #9265
- Fix relative path in Zinc compiler (#9261) PR #9261
- Fix V2 AWSLambda not being included in the pantsbuild.pants wheel (#9256) PR #9256
- fixing scoverage sourcePath to be relative in OSS PR #9245
Refactoring, Improvements, and Tooling
- Make Target API safe to use with the engine (#9303) PR #9303
- Filter sources passed to the pytest invocation. (#9299) PR #9299
- Make the platform a remote execution happened on available to @rule`s. (#9198) `PR #9198
- Support build file aliases in v2. (#9279) PR #9279
- Store Address on V2 Target and pass it to Field`s during validation (#9300) `PR #9300
- Add PythonBinary, PythonLibrary, and PythonTests to the Target API (#9301) PR #9301
- Move pants.source's tests into src/python. (#9298) PR #9298
- Improve setup_pytest_for_target concurrency. (#9283) PR #9283
- Bump rust to 1.42 (#9297) PR #9297
- Simplify PrimitiveField to eagerly hydrate values (#9296) PR #9296
- Tweak how to add plugin fields to V2 targets to be more explicit (#9291) PR #9291
- Zinc: Use an Array[PublishDiagnosticsParam] for LSP compliance (#9292) PR #9292
- Change UnionMembership to use dict instead of OrderedDict (#9288) PR #9288
- Allow subclassing Field`s for custom `Field behavior with the Target API (#9286) PR #9286
- Redesign test.py to work with custom target types (#9276) PR #9276
- Add core abstractions for the V2 Target API (#9284) PR #9284
- create RequestsSession.Factory global subsystem, and use it to configure urllib3.util.Retry for http artifact cache downloads (#8568) PR #8568
- Lmdb versioning (#9269) PR #9269
- Remove stale service-shutdown comment, and log the error stacktrace. (#9272) PR #9272
- Simplify sources code now that globs() is removed (#9263) PR #9263
- Mute the path scrub warning when running from sources. (#9264) PR #9264
- Remove leftover globs() code for bundles (#9262) PR #9262
- Format zinc compiler with scalafmt (#9227) PR #9227
- Revert "Update version of cargo-ensure-prefix to fix error while installing (#9240)" (#9248) PR #9248
- Update version of cargo-ensure-prefix to fix error while installing (#9240) PR #9240
Testing
Generated by publish_docs
from dist/markdown/html/src/python/pants/notes/1.27.x.html 2022-12-03T01:08:59.857475


--- title: Fill Missing Data in Orientation Maps sidebar: documentation_sidebar permalink: EBSDFilling.html folder: documentation toc: false ---
Orientation maps determined by EBSD or any other technique are, as all experimental data, effected by measurement errors. Those measurement errors can be divided into systematic errors and random errors. Systematic errors mostly occur due to a bad calibration of the EBSD system and require additional knowledge to be corrected. Deviations from the true orientation due to noisy Kikuchi pattern or tolerances of the indecing algorithm can be modeled as random errors. In this section we demonstrate how random errors can be significantly reduced using denoising techniques.
We shall demonstrate the denoising capabilities of MTEX at the hand of an orientation map of deformed Magnesium
{% highlight matlab %} % import the data mtexdata ferrite % consider only indexed data ebsd = ebsd('indexed'); % reconstruct the grain structure [grains,ebsd.grainId,ebsd.mis2mean] = calcGrains(ebsd,'angle',10*degree); % remove some very small grains ebsd(grains(grains.grainSize<5)) = []; % redo grain segementation [grains,ebsd.grainId] = calcGrains(ebsd,'angle',10*degree); % smooth grain boundaries grains = smooth(grains,5); % plot the orientation map plot(ebsd,ebsd.orientations) % and on top the grain boundaries hold on plot(grains.boundary,'linewidth',1.5) hold off {% endhighlight %} {% highlight plaintext %} saving data to /home/hielscher/mtex/master/data/ferrite.mat ebsd = EBSD Phase Orientations Mineral Color Symmetry Crystal reference frame -1 136 (0.22%) notIndexed 0 63044 (100%) Ferrite LightSkyBlue 432 Properties: ci, fit, iq, sem_signal, x, y, oldId Scan unit : um {% endhighlight %}Although the data set has already some not indexed pixels we artificially make the situation more worse by throwing away 75 percent of all data.
{% highlight matlab %} ebsdSub = ebsd(discretesample(length(ebsd),round(length(ebsd)*25/100))); % plot the reduced data plot(ebsdSub,ebsdSub.orientations) {% endhighlight %}Our aim is now to recover the orginal orientation map. In a first step we reconstruct the grain structure from the remaining 25 percent of pixels.
{% highlight matlab %} % reconstruct the grain structure [grainsSub,ebsdSub.grainId] = calcGrains(ebsdSub,'angle',10*degree); grainsSub = smooth(grainsSub,5); hold on plot(grainsSub.boundary,'linewidth',1.5) hold off {% endhighlight %}The easiest way to reconstruct missing data is to use the command fill which interpolates missing data using the method of nearest neighbor. It is very recommended to pass the grain structure grainsSub
as an additional argument to the fill
function. In this case the nearest neighbors are choosen within the grains.
A much more powerful method is to use any denoising method and set the option fill
.
Data sets with many missing pixels most often appear when measuring geological samples. The following data set of forsterite contains about 25 percent missing pixels. Lets start by importing the data and reconstructing the grain structure.
{% highlight matlab %} close all; plotx2east mtexdata forsterite ebsd = ebsd(inpolygon(ebsd,[10 4 5 3]*10^3)); plot(ebsd('Fo'),ebsd('Fo').orientations) hold on plot(ebsd('En'),ebsd('En').orientations) plot(ebsd('Di'),ebsd('Di').orientations) % compute grains [grains,ebsd.grainId] = calcGrains(ebsd('indexed'),'angle',10*degree); % remove small grains ebsd(grains(grains.grainSize < 3)) = []; % and repeat the grain computation [grains,ebsd.grainId] = calcGrains(ebsd('indexed'),'angle',10*degree); % grains = smooth(grains,5); % plot the boundary of all grains plot(grains.boundary,'linewidth',2) hold off {% endhighlight %} {% highlight plaintext %} ebsd = EBSD Phase Orientations Mineral Color Symmetry Crystal reference frame 0 58485 (24%) notIndexed 1 152345 (62%) Forsterite LightSkyBlue mmm 2 26058 (11%) Enstatite DarkSeaGreen mmm 3 9064 (3.7%) Diopside Goldenrod 12/m1 X||a*, Y||b*, Z||c Properties: bands, bc, bs, error, mad, x, y Scan unit : um {% endhighlight %}Using the option fill
the command smooth
fills the holes inside the grains. Note that the nonindexed pixels at the grain boundaries are kept untouched. In order to allow MTEX to decide whether a pixel is inside a grain or not, the grain
variable has to be passed as an additional argument.
In order to visualize the orientation gradient within the grains, we plot the misorientation to the meanorientation. We observe that the mis2mean varies smoothly also within the regions of not indexed orientations.
{% highlight matlab %} % plot mis2mean for all phases ipfKey = axisAngleColorKey(ebsdS('Fo')); ipfKey.oriRef = grains(ebsdS('fo').grainId).meanOrientation; ipfKey.maxAngle = 2.5*degree; color = ipfKey.orientation2color(ebsdS('Fo').orientations); plot(ebsdS('Fo'),color,'micronbar','off') hold on ipfKey.oriRef = grains(ebsdS('En').grainId).meanOrientation; plot(ebsdS('En'),ipfKey.orientation2color(ebsdS('En').orientations)) % plot boundary plot(grains.boundary,'linewidth',4) plot(grains('En').boundary,'lineWidth',4,'lineColor','r') hold off {% endhighlight %}For comparison
{% highlight matlab %} ipfKey.oriRef = grains(ebsd('fo').grainId).meanOrientation; ipfKey.maxAngle = 2.5*degree; color = ipfKey.orientation2color(ebsd('Fo').orientations); plot(ebsd('Fo'),color,'micronbar','off') hold on ipfKey.oriRef = grains(ebsd('En').grainId).meanOrientation; plot(ebsd('En'),ipfKey.orientation2color(ebsd('En').orientations)) % plot boundary plot(grains.boundary,'linewidth',4) plot(grains('En').boundary,'lineWidth',4,'lineColor','r') hold off {% endhighlight %}


CriC is a web platform which manages emergency situations (e.g. earthquakes, fires, floods etc.) by the authorities or organizations. The application will integrate Google Crisis Map and Fusion Tables or creating additional layers. These layers would provide information of interest aiming at the occurring events and the affected areas.
We will use CAP (Common Alerting Protocol) for transmitting the notifications and alerts to the population (directly affected or nearby); eventually using social platforms.
Using Geolocaion API and servicies like Google Person Finder, the system can automatically provide information about finding a missing person (e.g. when the respective person is unconscious or injured) and/or about possible shelters and rescue routes.
The application admits multiple types of users, each of them being provided with various functionalities.
This kind of user has minimal access to the application. He can either register in order to become an authenticated user, or just use the functionalities provided for him: view the lists of shelters, alerts and missing persons. They will also receive an notification when there is a new alert added.
This user has already created an account and has logged in. In addition to the functionalities of a guest, this user can also request adding or removing a missing person in the database. If the request to add a missing person succeeds, the user will receive a notification when the person is found. The removal of a missing person means that the person has been found.
This is the most powerful kind of user in this application. They belong to profile organisations or authorities. They can use any of the functionalities mentioned before. They are also responsable of adding or removing shelters, missing people or alerts and checking if the request to do so is justified.
If the user has an account, then he has to use the username and password he set to login. Otherwise, in order to create an account, a user has to complete a registration form.
Each available shelter has to be added by an organization account. When a shelter is no longer in use, the organization accounts have to get rid of them. A regular user, wheter logged in or not, is able to view a list of the available shelters.
When a new alert occurs, it is added to the app by an organization account and then removed when it is no longer happening. All users get a notification with information about an alert when it is added and then are able to see a list of all the active alerts.
Any authenticated user can request adding or removing a missing person. The organization accounts have to check if the request is justify and proceed act accordingly. When a user requests adding a missing person, their infomration becoms the contact information for the missing person in case they are found. The user who made the requests will also recieve a notification when the person is declared found and removed from the database. Any user can see the list of missing people.
After creating an account, the information provided by the user in order to create the account will be saved here.
Contains all the shelters available.
Contains the emergencies that take place at that certain moment.
Relation between users, emergencies and shelters. Has the role to connect a user which is in the vecinity of an emergency to a shelter nearby.
Contains the people that have been declared missing and information that could be helpful in order to find them.
Relation between users and missing_people. Provides a contact to reach when a person is found.
Google Crisis Map is a collection of national and regional-scale emergency layers related to weather, hazards and emergency preparedness and response. It is provided by the Google Crisis Response Team as a tool that allows creation of mashups for crisis, humanitarian and non-profit purposes.
The goal is to take crisis-related geographical data and centralize it. The geo-data is stored in a format that can be used with a Geographic Information System; therefore it requires a special software, unavailable for everyone.
It takes data that lives scattered across various governmental websites or organizations’ websites (e.g. NOAA, FEMA, Unitar) in many different formats and it makes them available to all users without any kind of special software. The Crisis Map API points at third-party layers, it doesn’t host the data and it makes the critical disaster geo-data more accessible.
The Map has various layers: weather-related (precipitation, clouds, storm information, air quality), fires, floods, evacuation routes, traffic & transit.
It can be embedded into our web application by creating a mashup inside our code.
The geographic data is accepted in several forms:
We will use Google Fusion Tables to generate the geo-data on the map.
Google Fusion Tables is a web service for data management. Fusion tables are used for gathering, sharing and visualizing data tables. It can display various imagery, such as: charts, maps, network graphs or custom layouts.
We will use location tables to display the corresponded mapped data. Fusion tables can accept uploaded data in text-delimited formats, such as CSV (comma-separated text) or TSV (other delimiter), spreadsheet formats: XLS, XSLX, ODS or Google Spreadsheets. The locations can be specified in latitude and longitude numbers or descriptive text (e.g. “France”) or an address.
After the Table is created (or updated) and public, we can use a generated ID to add the layer in Google Crisis Map.
The Common Alerting Protocol is an open, non-proprietary message format for all types of alerts and notifications. It is basically a special XML file. It does not address any particular application or telecommunications method; it is compatible with emerging techniques.
It provides flexible geographic targeting using latitude and longitude shapes, multilingual messaging, phased or delayed times and expirations, message updates, cancellations; facility for digital images and audio.
The structure of it consists of an "alert" segment, which may contain one or more "info" segments, each of them eventually including one or more "area" and/or "resource" segments. Mostly, the CAP messages should include at least one "info" element.
Any time Google launches Google Person Finder in response to a crisis, government and non profit organizations can help people locate each other by spreading the word, using the data, and adding information. We will use this API to implement out missing persons section of the site.
The Person Finder application stores and exports records using the People Finder Interchange Format (PFIF), which is based on XML.
When displaying any content accessed via the API to a user, we must display a link to the original source of information to refer any enquiries in connection with that specific record back to the original source, and may not intermix content accessed via the API with other content in any way that makes it unclear which content came from which source.
The Geolocation API returns a location and accuracy radius based on information about cell towers and WiFi nodes that the mobile client can detect. We will use this API to warn users about emergencies near their location.
Communication is done over HTTPS using POST.
A successful geolocation request will return a JSON-formatted response defining a location and radius.
The Directions API is a service that calculates directions between locations. We can search for directions for several modes of transportation. We will use this api to guide users to nearby shelters in case of emergencies.
We will access the Directions API through an HTTP interface, with requests constructed as a URL string, using text strings or latitude/longitude coordinates to identify the locations, along with our API key.