The lion (Panthera leo) is a species in the family Felidae; it is a muscular, deep-chested cat with a short, rounded head, a reduced neck and round ears, and a hairy tuft at the end of its tail. It is sexually dimorphic; adult male lions have a prominent mane, which is the most recognisable feature of the species. With a typical head-to-body length of 184–208 cm (72–82 in) they are larger than females at 160–184 cm (63–72 in). It is a social species, forming groups called prides. A lion pride consists of a few adult males, related females and cubs. The lion is an apex and keystone predator, although some lions scavenge when opportunities occur, and have been known to hunt humans, although the species typically does not.
Typically, the lion inhabits grasslands and savannas, but is absent in dense forests. It is usually more diurnal than other big cats, but when persecuted it adapts to being active at night and at twilight. In the Pleistocene, the lion ranged throughout Eurasia, Africa and North America, but today it has been reduced to fragmented populations in Sub-Saharan Africa and one critically endangered population in western India. It has been listed as Vulnerable on the IUCN Red List since 1996 because populations in African countries have declined by about 43% since the early 1990s. Lion populations are untenable outside designated protected areas. Although the cause of the decline is not fully understood, habitat loss and conflicts with humans are the greatest causes for concern.
One of the most widely recognised animal symbols in human culture, the lion has been extensively depicted in sculptures and paintings, on national flags, and in contemporary films and literature. Lions have been kept in menageries since the time of the Roman Empire and have been a key species sought for exhibition in zoological gardens across the world since the late 18th century. Cultural depictions of lions were prominent in the Upper Paleolithic period; carvings and paintings from the Lascaux and Chauvet Caves in France have been dated to 17,000 years ago, and depictions have occurred in virtually all ancient and medieval cultures that coincided with the lion's former and current ranges.
One of the most widely recognised animal symbols in human culture, the lion has been extensively depicted in sculptures and paintings, on national flags, and in contemporary films and literature. Lions have been kept in menageries since the time of the Roman Empire and have been a key species sought for exhibition in zoological gardens across the world since the late 18th century. Cultural depictions of lions were prominent in the Upper Paleolithic period; carvings and paintings from the Lascaux and Chauvet Caves in France have been dated to 17,000 years ago, and depictions have occurred in virtually all ancient and medieval cultures that coincided with the lion's former and current ranges.


|
MasterScan
Lab_Matlab_control Master Branch
|
Mirrors dotsClientEnsemble objects from another instance of Matlab.
dotsEnsembleServer opens a socket and checks for messages sent from dotsClientEnsemble objects created in another Matlab instance. It creates topsEnsemble objects on the server which mirror the client ensembles. It can call methods on server objects and return results to the client objects.
Client-server interactions must be initiated on the client side. For basic method calls, the client is expected to wait until dotsEnsembleServer reports that it's finished with each action and returns any results.
dotsEnsembleServer also continuously invokes runBriefly() on those ensemble objects that have isRunning set to true. This allows client and server ensembles to run concurrent behaviors across Matlab instances. Invoking run() or start(), and finish(), on a client ensembl controls isRunning for the mirrored server ensemble.
The runBriefly() behavior of each server ensemble depends on which of its calls are active. Invoking setActiveByName() or callByName(), with the isActive flag, from the client side controls the behavior of the mirrored server ensemble.
Properties and Events | |
| Property | timeout = 1.0 |
| seconds to allow for network communications | |
| Property | waitTime = 0.0001 |
| seconds to yield periodically to the operating system | |
| Property | clockFunction |
| function that returns the current time as a number | |
Protected Properties | |
| Property | clientIP |
| IP address of the Snow Dots client. | |
| Property | clientPort |
| network port of the Snow Dots client | |
| Property | serverIP |
| IP address of this dotsEnsembleServer. | |
| Property | serverPort |
| network port of this dotsEnsembleServer | |
| Property | socket |
| socket identifier for communictions | |
| Property | ensembles |
| server side ensemble instances | |
| Property | ensembleCell |
| cache ensembles in a cell array for faster access | |
Methods | |
| self | dotsEnsembleServer (clientIP, clientPort, serverIP, serverPort) |
| Create an ensemble server with optional network addresses. More... | |
| setAddresses (self, clientIP, clientPort, serverIP, serverPort) | |
| Use the given network addresses for messages. More... | |
| run (self, duration) | |
| Run the server with optional duration. More... | |
| reset (self) | |
| Return to a like-new state. More... | |
Protected Methods | |
| openSocket (self) | |
| Get a socket for messages. | |
| status | doNextTransaction (self) |
| Do a transaction on self, or delegate a named ensemble. More... | |
| runEnsemblesBriefly (self) | |
| Let each ensemble that isRunning runBriefly(). | |
Static Methods | |
| static | runNewServer (duration, clientIP, clientPort, serverIP, serverPort) |
| Create an ensemble server and start it running. More... | |
| self dotsEnsembleServer | ( | clientIP | , |
| clientPort | , | ||
| serverIP | , | ||
| serverPort | |||
| ) |
Create an ensemble server with optional network addresses.
| clientIP | string IP address of the Snow Dots client |
| clientPort | network port number of the Snow Dots client |
| serverIP | string IP address of the ensemble server |
| serverPort | netowrk port number of the ensemble server |
If clientIP, clientPort, serverIP, and serverPort are provided, attempts to connect to a client using the given addresses. Otherwise, uses default provided by dotsTheMessenger.
| setAddresses | ( | self | , |
| clientIP | , | ||
| clientPort | , | ||
| serverIP | , | ||
| serverPort | |||
| ) |
Use the given network addresses for messages.
| clientIP | string IP address of the Snow Dots client |
| clientPort | network port number of the Snow Dots client |
| serverIP | string IP address of the ensemble server |
| serverPort | netowrk port number of the ensemble server |
If clientIP, clientPort, serverIP, and serverPort are provided, attempts to connect to a client using the given addresses. Otherwise, uses default provided by dotsTheMessenger.
| run | ( | self | , |
| duration | |||
| ) |
Run the server with optional duration.
| duration | how long to keep running |
Starts the server running, responding to messages from the client side and invoking runBriefly() on server-side ensembles that have isRunning set to true.
If @duration is provided, runs for that long, in units of clockFunction, then returns. By default, runs forever.
| reset | ( | self | ) |
Return to a like-new state.
Removes all ensembles, and with them all server-side objects. Also re-opens network sockets. Reset may be invoked directly on the server side, or remotely from the client side, via the appropriate transaction. Note that the server will reply to the "reset" transaction just before resetting itself. The server may be unresponsive for a short time after it reposnds.
|
protected |
Do a transaction on self, or delegate a named ensemble.
This most important method for dotsEnsembleServer. It checks for a client message, and if there is a message, it carries out the indicated transaction. The transaction may be one of a few types, related to the server itself, or the ensembles it contains.
After carrying out a transaction, the server sends a reply to the client (which the client should be waiting for). The reply contains the original transaction data, plus any data requested in the transaction, plus timing data about the server's behavior.
Returns the message status from dotsTheMessenger, which is positive there was a transaction to carry out.
|
static |
Create an ensemble server and start it running.
| duration | time in seconds to keep running |
| clientIP | string IP address of the Snow Dots client |
| clientPort | network port number of the Snow Dots client |
| serverIP | string IP address of the ensemble server |
| serverPort | netowrk port number of the ensemble server |
Creates an instance of dotsEnsembleServer and lets it run. If duration is provided, runs for that many seconds, otherwise runs forever.
If clientIP, clientPort, serverIP, and serverPort are provided, attempts to connect to a client using the given addresses. Otherwise, uses default addresses provided by dotsTheMessenger. @deatils runNewServer() will block, busying its Matlab instance, until the server is done running, if ever.


Nicholas Wolf
Get this presentation:
https://nmwolf.github.io/rdm-intro-dataservices
Nick's ORCID: 0000-0001-5512-6151
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.
| NYU Google Drive | NYU Box | NYU Research Workspace | |
|---|---|---|---|
| Intended use | General data use requiring password access | General data, including sensitive or secure data | High-capacity data storage |
| Storage size | Unlimited | Unlimited | 2 TB |
| Sharing and user control | Yes | Yes | Yes |
| Versioning and file change tracking | Yes | Some | Snapshots of files |
| Funder requirements | Moderate risk security | High risk security | U.S. based data location |
Put your data into an archival-friendly format, preferably one that is open source, software agnostic, and lossless.
Code Composer
Web Application/Publishing
Homepage: https//guides.nyu.edu/dataservices
Email<EMAIL_ADDRESS>Learn more about RDM: guides.nyu.edu/data_management
Nick's ORCID: 0000-0001-5512-6151
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.


Based on Marathon, Jalian Systems provides a commercial version with extra features and support. You can use MarathonITE and reduce the effort required for creating resilient test suites. Use the included extract method refactoring to reuse your test scripts. Perform exploratory or semi-automatic testing through MarathonITE and share the test scripts with the development team.
Marathon records the name and recognition properties of the components in object map. Object map is stored as YAML files in the project folder. Each Marathon Project stores this information locally.
When more than one test engineer is working on the same project, sharing the object maps requires manual merging of the object map files. MarathonITE provides an option to centralize the object maps. By running a Objectmap Server on a central server, all test engineers can share this central repository.
More info:
Learn more about MarathonITE


front-end dev | graphics designer | programmer
About :
Basically I'm an 'Ambivert' pursuing my B.Tech Degree from a pretty well known instituition, Sree Chitra Thirunal College of Engineering. Like pretty much all kids these days I too like to code , and let me say I'm pretty good at it too. I also do poster designing, and front end development. If I havent made it clear from my website , I'm a weeb too.
Talents :
Projects :


Welcome to PySOT Dashboard’s documentation!
¶
Contents:
Quickstart
PySOT Dashboard
Dependencies
Installation
Usage
FAQ
Client
Client Page Layout
User Input
Image Displaying Result
PySOT Dictionary Layout
Experimental Design
Surrogate Model
Adaptive Sampling
Optimization Problem
Strategy
Controller
Kernel
Tail
Delay
Projection Function
Surrogate Optimization Problem
Tutorial
Source Code
Server
PySOT Dictionary
PySOT Object
Controller Object
Module Scraper
Projection Function
Delay Functions
Client Page
Image Display
Indices and tables
¶
Index
Module Index
Search Page
Related Topics
Documentation overview
Next:
Quickstart
Quick search


like what you see?
support me
Embed Editor
Use variables (will skip field checks and direcly add names without doublequotes)
Basic settings
Color
Thumbnail settings
Author settings
Fields
Footer settings
Embed Preview
Python code


Appreciating Hubble at Hyper-speed: Download
To run Appreciating Hubble at Hyper-speed, first unzip the downloaded
archive. Windows and Mac users, double-click ahah.jar
.
Linux users, run java -jar ahah.jar
.
The Sun Java Runtime version 1.4.3 or newer is required to run Appreciating Hubble at Hyper-speed - the latest version can be downloaded from Java.com.
A configuration file is included that can be used to change the application's default behavior. To learn about the contents and format of this file, see the Configuration File section of the online manual.


Contact Us
Images
Students
My Blogs
Profilio
Home
Please Provide Information For Keep Updating This Website


Below is the schedule for open student hours (no one is in an office these days, but these are similar to what is sometimes called “office hours”).
These are times when there will be a course staff person available to answer any questions you have.
| Monday 4-5:30pm | Nick |
| Monday 5:30-6pm | Yu |
| Monday 6:30-8pm | Anlan |
| Monday 8-9:30pm | Megan |
| Tuesday 12:30-2pm | Timothy |
| Tuesday 2-3:30pm | Nijat |
| Tuesday 3:30-5pm | Jonah |
| Tuesday 5-6:30pm | Nick |
| Tuesday 6-7:30pm | Kush |
| Wednesday 9:30-10:30am | Dave |
| Wednesday noon-2:00pm | Nathan |
| Wednesday noon-1:30pm | Timothy |
| Wednesday 1:30-3pm | Vi |
| Wednesday 7:30-9pm | Noah |
| Thursday 9:30-11am | John |
| Thursday 12:30-2pm | Joey |
| Thursday 2:30-4pm | Joshua |
| Thursday 4:30-6pm | Brandon |
| Thursday 6:30-8pm | Preston |
| Friday 9-10:30am | Yu |
| Friday 10:30-noon | Megan |
| Friday 12-1pm | Dave |
| Friday 1pm-2:30pm | Nathan |
| Friday 2-3:30pm | William |
| Friday 5:30-7:00pm | Nijat |
| Saturday 10-11:30am | Nicholas |
| Saturday 11:30am-1pm | Rachel |
| Sunday 10:30am-noon | Michelle |
| Sunday 3:30-5pm | Joshua |
| Sunday 5:30-7pm | Nicholas |
During the scheduled times, the listed staff person is available to answer your questions.
You can request help by putting a message in the #help-requests
channel. You will also see open help video rooms (that may have
particular topics that are being covered), and should feel free to
just jump into these rooms.
You may be wondering what the point of faculty open student hours is with how wonderful the TAs are, and all the opportunities you have with the cohort sessions and TA office hours. If you are feeling reluctant to come to faculty office hours, this video might help:
For my (Dave) office hours, I will be in the discord, but will use this zoom link for video discussions (this is mainly to be able to use the waiting room to have private discussions when desirable; if you connect to the zoom room and are not invited in immediately, I will try to send you a message, but you might have to wait for this to finish). (Note: if you want to arrange a private meeting with me at a different time, use https://davidevans.youcanbook.me/.)


Chipmaker Intel says supply remains tight in PC business; shares slip
Intel Corp said on Wednesday it has not been able to keep up with the increasing demand for CPUs and said supply remained "extremely tight" in its personal computer business.
REUTERS: Intel Corp said on Wednesday it has not been able to keep up with the increasing demand for CPUs and said supply remained "extremely tight" in its personal computer business.
"Despite our best efforts, we have not yet resolved this challenge," the chipmaker said https://www.sec.gov/Archives/edgar/data/50863/000119312519296610/d817506dex991.htm in a letter, in which the company also apologised to its customers and partners for the shipment delays.
Shares of the chipmaker were down nearly 1per cent in after-market trading.
(Reporting by Ambhini Aishwarya in Bengaluru; Editing by Arun Koyyur)


Sohan Jain
Devops
Engineer
I'am Full Stack WebDevloper and Cloud Architect
Education
Year
Course
University
2019-2022
Engineering
Visvesvaraya Technological University
2016-2019
Diploma
Shree Bahubali Polytechnic
Licenses and certifications
Java ★★★★☆
Python ★★★★☆
html ★★★★★
CSS ★★★★☆
Contact


This community has been striving for equality, not just in law, but in their everyday lives. All deserve a life that they can live without fear of being true their self and discriminated against due to their sexual or gender orientation. Though rights are steadily improving, there are still locations all over the globe where being LGBTQ+ people are being imprisoned or even put to death. This is not a local issue, but a global one.
More and more people are joining this community and more non-LGBTQ+ are showing their support. There has been significant progress over the past decade alone. The UN's involvement sparked the movement and its support has been growing stronger with the community.
There are plenty of organizations that could use your support. Together, we can fight against discrimination and bigotry.
Find an organization: What can I do to help?


Logged in user:
User
has Roles:
Role
Welcome to Marvel Products
View Products
View Users
Add Product


EIGHTEEN SPRINGS (1997)
"It is as difficult to love someone forever as it is to hate someone forever."
3.5 out of ****
Starring Wu Chien-lien, Leon Lai, Anita Mui, Huang Lei, Ge You Directed by Ann Hui Written by Kin-chung Chan, from the novel by Eileen Chang Cinematography by Ping-bin Lee
EIGHTEEN SPRINGS is a love story in which no one ever says the words "I love you." No one speaks the word "love" in any context, as far as I recall. There is talk of marriage, of money, of couples who are good pairs, of couples who are poor matches--but never of love. Marriage is less a matter of what is right than what is appropriate. Yet the movie is founded on the convincing, touching, deeply felt romance between Shujun (FALLEN ANGELS' Leon Lai) and Manjing (EAT DRINK MAN WOMAN's Wu Chien-lien), two young people who are transparently in love, even if they never say the words.
Shujun is the son of a wealthy family in Nanjing. Manjing's father died when she was young, and her sister (Anita Mui) had to take a shameful job as a "ballroom hostess" to provide for the family. Because the sister's work reflects poorly on Manjing's entire family, she is an unsuitable bride for Shujun--according to his family.
Today, Shujun might ignore his family's wishes, but he and Manjing live in Shanghai in the 1930s, where marriages were decided by decorum as much as by desire, so he does not have that liberty. They live in a world not unlike Jane Austen's, where social codes and manners govern all behaviour, and the way people act within such strict guidelines can be at times humorous, at times heartbreaking.
Heartbreaking, mostly, for the difference in social status is merely the beginning of the lovers' problems. Shujun's choice of family over self has tragic consequences, especially for Manjing. The problems become perhaps too extreme--Chinese movies never seem to err on the side of caution when it comes to providing hardships for their characters. The latter half of the film struck me as being a bit too much, because the first half is so gentle, so graceful and delicate in its exploration of young love. Nevertheless, the idyllic beginning makes the lovers' later separation, their loss and longing, terribly poignant.
EIGHTEEN SPRINGS is refreshing in the way it devotes time to the courtship, unlike most movies, which treat romance in a perfunctory manner. Here, we see love developing, rather than being informed about it after the fact.
Shujun and Manjing are introduced by a mutual friend (Huang Lei) when Shujun comes to work in a factory in Shanghai. The budding romantic tension is subtle but unmistakable. Soon Shujun and Manjing are finding moments alone together, but there is no overt romance, no profession of love. They grow close, and, without even a kiss, are soon discussing marriage. It is typical of their hesitant courtship that marriage is not so much proposed as suggested: "Wouldn't it be nice if we were married?" But we can believe that it would be nice. They are both quiet, mild-mannered, conscientious; they are comfortable together.
Their love manifests itself in small, understated gestures. Shujun learns that Manjing lost one of her gloves, so he takes a flashlight and searches through the woods at night to find it. When he gives it to her the next day, he doesn't tell her about the trouble he went through--clearly, the act of giving, of pleasing her, is all the gratification he needs. He walks her home from work every night, and when they part, they simply say, "See you tomorrow," but the way they glance at each other as they do, awkward, guarded, wanting to say more but afraid to do so, perfectly captures the fragile emotions of young lovers. Credit for this belongs to Lai and Wu, who are both wonderful: they imbue mundane exchanges and brief gestures with complex, profound, restrained feelings.
This is one of the great pleasures of the film, that it pays attention to the nuances of feeling that attend even the smallest gestures. In this sense, it is a domestic movie, a movie about everyday lives, everyday things. Such films can be drab, but in the right hands they can be fascinating--as this one is--because they remind us that there are hidden worlds of emotion that we tend to forget about, that we take for granted as we go about our lives. Unfortunately, Shujun and Manjing never get the chance to take those emotions for granted.
A Review by David Dalgleish (July 2/98<EMAIL_ADDRESS>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


Recipe 19.14. Merging Sorted SequencesCredit: Sébastien Keim, Raymond Hettinger, Danny Yoo ProblemYou have several sorted sequences (iterables) and need to iterate on the overall sorted sequence that results from "merging" these sequences. SolutionA generator is clearly the right tool for the job, in the general case (i.e., when you might not have enough memory to comfortably hold all the sequences). Implementing the generator is made easy by the standard library module heapq, which supplies functions to implement the "heap" approach to priority queues: import heapq def merge(*subsequences): # prepare a priority queue whose items are pairs of the form # (current-value, iterator), one each per (non-empty) subsequence heap = [ ] for subseq in subsequences: iterator = iter(subseq) for current_value in iterator: # subseq is not empty, therefore add this subseq's pair # (current-value, iterator) to the list heap.append((current_value, iterator)) break # make the priority queue into a heap heapq.heapify(heap) while heap: # get and yield lowest current value (and corresponding iterator) current_value, iterator = heap[0] yield current_value for current_value in iterator: # subseq is not finished, therefore add this subseq's pair # (current-value, iterator) back into the priority queue heapq.heapreplace(heap, (current_value, iterator)) break else: # subseq has been exhausted, therefore remove it from the queue heapq.heappop(heap) DiscussionThe need for "merging" sorted subsequences into a larger sorted sequence is reasonably frequent. If the amount of data is small enough to fit entirely in memory without problems, then the best approach is to build a list by concatenating all subsequences, then sort the list: def smallmerge(*subsequences): result = [ ] for subseq in subsequences: result.extend(subseq) result.sort( ) return result The sort method of list objects is based on a sophisticated natural merge algorithm, able to take advantage of existing sorted subsequences in the list you're sorting; therefore, this approach is quite fast, as well as simple (and general, since this approach's correctness does not depend on all subsequences being already sorted). If you can choose this approach, it has many other advantages. For example, smallmerge works fine even if one of the subsequences isn't perfectly sorted to start with; and in Python 2.4, you may add a generic keywords argument **kwds to smallmerge and pass it right along to the result.sort( ) step, to achieve the flexibility afforded in that version by the cmp=, key=, and reverse= arguments to list's sort method. However, you sometimes deal with large sequences, which might not comfortably fit in memory all at the same time (e.g., your sequences might come from files on disk, or be computed on the fly, item by item, by other generators). When this happens, this recipe's generator will enable you to perform your sequence merging while consuming a very moderate amount of extra memory (dependent only on the number of subsequences, not on the number of items in the subsequences). The recipe's implementation uses a classic sequence-merging algorithm based on a priority queue, which, in turn, lets it take advantage of the useful heapq module in the Python Standard Library. heapq offers functions to implement a priority queue through the data structure known as a heap. A heap is any list H such that, for any valid index 0<=i<len(H), H[i]<=H[2*i+1], and H[i]<=H[2*i+2] (if 2*i+1 and 2*i+2 are also valid indices into H). This heap property is fast to establish on an arbitrary list (function heapify does that) and very fast to re-establish after altering or removing the smallest item (and functions heapreplace and heappop do that). The smallest item is always H[0] (it's easy to see that the "heap" property implies this), and being able to find the smallest item instantly makes heaps an excellent implementation of priority queues. In this recipe, we use as items in the "heap" a "pair" (i.e., two-items tuple) for each subsequence that is not yet exhausted (i.e., each subsequence through which we have not yet fully iterated). As its first item, each pair has the "current item" in the corresponding subsequence and, as its second item, an iterator over that subsequence. At each iteration step, we yield the smallest "current item", then we advance the corresponding iterator and re-establish the "heap" property; when an iterator is exhausted, we remove the corresponding pair from the "heap" (so that, clearly, we're finished when the "heap" is emptied). Note the idiom that we use to advance an iterator by one step, dealing with the possibility that the iterator is exhausted: for current_value in iterator: # if we get here the iterator was not empty, current_value was # its first value, and the iterator has been advanced one step ...use pair (current_value, iterator)... # we break at once as we only wanted the first item of iterator break else: # if we get here the break did not execute, so the iterator # was empty (exhausted) # deal with the case of iterator being exhausted... We use this idiom twice in the recipe, although in the first of the two uses we do not need the else clause since we can simply ignore iterators that are immediately exhausted (they correspond to empty subsequences, which can be ignored for merging purposes). If you find this idiom confusing or tricky (because it uses a for statement whose body immediately breaksi.e., a statement that looks like a loop but is not really a loop because it never executes more than once!), you may prefer a different approach: try: current_value = iterator.next( ) except StopIteration: # if we get here the iterator was empty (exhausted) # deal with the case of iterator being exhausted... else: # if we get here the iterator was not empty, current_value was # its first value, and the iterator has been advanced one step # use pair (current_value, iterator)... I slightly prefer the idiom using for; in my view, it gains in clarity by putting the normal case (i.e., an unexhausted iterator) first and the rare case (an exhausted iterator) later. A variant of the try/except idiom that has the same property is: try: current_value = iterator.next( ) # if we get here the iterator was not empty, current_value was # its first value, and the iterator has been advanced one step # use pair (current_value, iterator)... except StopIteration: # if we get here the iterator was empty (exhausted) # deal with the case of iterator being exhausted... However, I somewhat dislike this variant (even though it's quite OK for the two specific uses of this recipe) because it crucially depends on the code indicated as "use pair" never raising a StopIteration exception. As a general principle, it's best to use a TRy clause's body that is as small as possiblejust the smallest fragment that you do expect to possibly raise the exception you're catching in the following handlers (except clauses), not the follow-on code that must execute only if the exception was not raised. The follow-on code goes in the else clause of the try statement, in properly defensive Pythonic coding style. In any case, as long as you are fully aware of the tradeoffs in clarity and defensiveness between these three roughly equivalent idioms, you're welcome to develop your own distinctive Pythonic style and, in particular, to choose freely among them! If you do choose either of the idioms that explicitly call iterator.next( ), a further "refinement" (i.e., a tiny optimization) is to keep as the second item of each pair, rather than the iterator object, the bound-method iterator.next directly, ready for you to call. This optimization is not really tricky at all (it is quite common in Python to stash away bound methods and other such callables), but it may nevertheless result in code of somewhat lower readability. Once again, the choice is up to you! See AlsoChapter 5 for general issues about sorting and Recipe 5.7 and Recipe 5.8 about heapq specifically; Library Reference and Python in a Nutshell documentation on module heapq and lists' sort method; Robert Sedgewick, Algorithms (Addison-Wesley) (heaps are covered starting on p. 178 in the 2d edition); heapq.py in the Python sources contains an interesting discussion of heaps. |


The railway is currently closed for the winter. But here is our timeable for the summer. Standard running times are 14:00 to 17:30. Prices are £1 for our Rasised Track (The Little Railway)and £1.50 for the Ground Level Track (The Big Railway)
| Dates | Size of Railway | Notes |
|---|---|---|
| 7th April | Big Railway | Parties hier available |
| 21st April | Little Railway | |
| 22nd April | Bank Hoilday Special |
|
| 28th April | Little Railway | |
| 29th April | Bank Hoilday Special | |
| 5th May | Big Railway | |
| 6th May | Bank Hoilday Special | |
| 12th May | Big Railway | Parties hier available |
| 19th May | Little Railway | |
| 26th May | Big Railway | Parties hier available |
| 27th May | Bank Hoilday Special | |
| 2nd June | Little Railway | |
| 9th June | Big Railway | Parties hier available |
| 15th June | Charity Day Special | One Railway Running |
| 16th June | Big Railway | Parties hier available |
| 23rd June | Little Railway | |
| 30th June | Big Railway | Parties hier available |
| 7th July | Little Railway | |
| 14th July | Big Railway | Parties hier available |
| 21st July | Big Railway | Parties hier available |
| 28th July | Little Railway | |
| 4th August | Big Railway | Parties hier available |
| 7th August | Summer Hoilday Special | 14:00 to 17:30 |
| 11th August | Little Railway | |
| 14th August | Summer Hoilday Special | 14:00 to 17:30 |
| 18th August | Big Railway | Parties hier available |
| 21st August | Summer Hoilday Special | 14:00 to 17:30 |
| 25th August | Big Railway | Parties hier available |
| 26th August | Bank Hoilday Special | |
| 28th August | Summer Hoilday Special | 14:00 to 17:30 |
| 1st September | Little Railway | |
| 8th September | Big Railway | Parties hier available |
| 15th September | Little Railway | |
| 22nd September | Big Railway | Parties hier available |
| 29th September | Big Railway | Parties hier available |
| 6th October | Charity Day Special | BOTH RAILWAYS RUNNING!!! |


Back to TGM
Documentation
This webapp is for simulating outpost, assault, and/or other objectives for Nerf, Airsoft, Paintball, or Water War games. Supports most screen sizes, and supports touch and keyboard/mouse. Requires an up-to-date HTML5-compliant browser.
Setting up a game is straightforward and simply involves filling out the form. Following is an explanation of each field.
Score Limit
Number of points needed for a team to win. Currently does not support infinite values.
Countdown
A countdown that must run initially before the game begins. Doesn't work yet.
Time Limit
Game ends automatically after the time limit expires. Games can be instantaneous or up to just under 24 hours.
Objective Type
Outpost sets up a control point style objective for capture. Teams must hold down the capture button for a set duration to take the control point, and may earn points for capturing and/or holding the control point.
Bomb sets up an assault style objective for attack. To score, the attacking team must plant the bomb. If successful, the opposing team must try to diffuse the bomb before it activates.
Usable By Teams
Specifies which teams may use the objective to score.
In Outpost, this can be set to allow only one team to take the control point.
In Assault (bomb), this is set to differentiate between the attacking and defending team.
Outpost Settings
Starting Team: Team that owns the outpost when the game starts.
Time to Capture: Number of seconds it takes to capture or neutralize the control point.
Can Only Capture Once: Disables control point after first capture by any team.
Neutralize Before Capture: Requires the control point to be neutralized before being taken.
Points for Capture: Points rewarded to the team that captures the control point.
Ownership Scoring: Points rewarded to the team that owns the control point, given every second or every minute.
Bomb Settings
Time to Plant: Time required to arm the bomb.
Time to Diffuse: Time required to diffuse the bomb.
Ticking Time: Time the bomb runs for before detonation.
Points for Planting: Points awarded to team for successfully arming bomb.
Points for Detonation: Points awarded to team for successful detonation.
Points for Diffusal: Points awarded to team for successful diffusal.
Can Only Use Once: Disables the objective after first disarm/detonation.


Exploring mechanisms to traverse Variant Calling Formatted files remotely (without downloading them). The rationale is the same advanced for digital pathology in imagebox2 by relying on range requests. For parsing full files see old project at IBL.
Although the real action is in the console, this page will be used to test the JavaScript vcf SDK. To do so, select the URL of the remote VCF file (or use default test VCF file borrowed from Tollefson 2019), and then try different methods. For examples of the real-world challange see clinVar, snp or 1000genomes.
-


Watch Transcript
Transcript name:
Watch Transcript
Afrikaans
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Bashkir
Basque
Belarusian
Bengali
Bosnian
Bulgarian
Burmese
Catalan
Cebuano
Chinese
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Finnish
French
Galician
Georgian
German
Greek
Gujarati
Haitian
Hebrew
Hill Mari
Hindi
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Khmer
Korean
Kyrgyz
Lao
Latin
Latvian
Lithuanian
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mari
Mongolian
Nepali
Norwegian
Papiamento
Persian
Polish
Portuguese
Punjabi
Romanian
Russian
Scottish Gaelic
Serbian
Sinhalese
Slovak
Slovenian
Spanish
Sundanese
Swahili
Swedish
Tagalog
Tajik
Tamil
Tatar
Telugu
Thai
Turkish
Udmurt
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Xhosa
Yiddish
Translate
Made by Mark Noonan (
@marktnoonan
), based on David Walsh's
blog post
.


lxConfirm
lx.confirm
Directive which encapsulates a modal confirm window.
For more information look at the guide.


--- layout: doc title: Documentation ---
This file documents version 4.4 of Proof General, a generic Emacs interface for proof assistants.
Proof General 4.4 has been tested with GNU Emacs 24.4 on Linux. It is supplied ready to use for the proof assistants LEGO, Coq, Isabelle, and PhoX. Experimental support is provided for several other provers.
This document was generated by Erik Martin-Dorel on September 18, 2016 using texi2html 1.82.


Well for starters I pet a lot of dogs, and those dogs are good, so by transitive property, I must be so good.
Tuna Melts My Heart (Tuna pictured left), any three legged dog, Toast (a no toothed dog from a puppy mill), Tsuki (a three legged pitt cutie)
Learn moreLorem ipsum dolor sit amet, consectetur adipisicing elit. Reprehenderit maiores nam, aperiam minima assumenda.
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Reprehenderit maiores nam, aperiam minima assumenda.
Learn more


| Interface | Description |
|---|---|
| ConfirmDialog.ConfirmDialogListener |
This is the interface used to talk to the activity.
|
| PlaceBidDialog.PlaceBidDialogListener |
This is the interface used to talk to the activity.
|
| Class | Description |
|---|---|
| Bid |
This is the entity class for a bid object
|
| BidList |
This is the entity class for a bid object
|
| BidListAdapter |
To inflate the row selection for bids
|
| BidListTest |
Created by Hailan on 2018-02-20.
|
| BidTest |
Created by Logan Yue on 2018-02-20.
|
| BuildConfig | |
| ConfirmDialog |
A dialog fragment that will will work with an activity, user must bundle in the
dialog title, message, and cancel/confirm button text.
|
| DatePickerFragment |
A dialog for picking dates.
|
| EditMyProfileActivity |
EditMyProfileActivity starts after user selects the UserMenuButton --> "Edit My Profile"
|
| ElasticSearchController |
This class will handle the connection and async tasks to the es server
|
| ElasticSearchController.AddProfile |
This AsyncTask will add a profile to the db (can also be used to update profile)
|
| ElasticSearchController.AddTask |
This AsyncTask will add a task to the db.
|
| ElasticSearchController.DeleteProfile |
This AsyncTask will update a task from the db based on a taskid
|
| ElasticSearchController.DeleteTask |
This AsyncTask will update a task from the db based on a taskid
|
| ElasticSearchController.GetProfile |
This AsyncTask will retrieve profile from the db matching a username.
|
| ElasticSearchController.GetTask |
This AsyncTask will retrieve a task from the db based on a taskid
|
| ElasticSearchController.GetTasks |
This async task will return a list of task dependent on the preformatted query
|
| ElasticSearchController.UpdateTask |
This AsyncTask will update a task from the db based on a taskid
|
| ElasticSearchControllerTest |
Created by Zhipeng Zhang on 2018/2/22.
|
| ExampleInstrumentedTest |
Instrumented test, which will execute on an Android device.
|
| ExampleUnitTest |
Example local unit test, which will execute on the development machine (host).
|
| LogInActivity |
Allows the user to log in or move to a signup activity
|
| LogInActivityTest |
Created by Logan Yue on 2018-03-12.
|
| MapsActivity |
Based on: Mitch Tabian's Google Maps & Google Places Course - https://codingwithmitch.com/courses/ and https://www.youtube.com/watch?v=Vt6H9TOmsuo
|
| MapsSearchLocationActivity |
An activity which lets the user select a location for their task.
|
| MapsSearchTasksActivity |
An activity which shows all tasks with status Requested and Bidded within 5km.
|
| MockTask |
A mock task object for testing purposes.
|
| MyProfileViewActivity |
MyProfileViewActivity displays information of current user
|
| MyProfileViewActivityTest |
Created by Hailan on 2018-03-14.
|
| OtherProfileViewActivity |
OtherProfileViewActivity displays information of another user
|
| PlaceBidDialog |
A dialog fragment that will will work with an taskprovideractivity
This allows the user to edit their bid or add a bid.
|
| Profile |
This is the entity class for a profile object
|
| ProfileTest |
Created by ag on 2018-02-24.
|
| ProfileViewActivity |
Abstract class ProfileViewActivity generalizes MyProfileViewActivity and OtherProfileViewActivity
|
| ProviderCustomArrayAdapter |
An array adapter for SearchActivity and ProviderTaskListActivity.
|
| ProviderLayout |
An abstract activity which implements the navigation for the Provider options.
|
| ProviderPlaceBidTest |
Created by kaixiangzhang on 2018-03-13.
|
| ProviderTaskController |
Created by kaixiangzhang on 2018-03-11.
|
| ProviderTaskListActivity |
An activity where the provider can see the tasks - with different ui depending
On the task status, and input
|
| ProviderTaskListActivityTest | |
| ProviderViewHolder |
Holds the view objects for the ProviderCustomArrayAdapter.
|
| ProviderViewRequestedTaskTest |
Created by Zhipeng Zhang on 2018/3/16.
|
| ProviderViewTask |
An activity where the provider can see the tasks - with different ui depending
On the task status, and input
|
| R | |
| R.anim | |
| R.animator | |
| R.attr | |
| R.bool | |
| R.color | |
| R.dimen | |
| R.drawable | |
| R.id | |
| R.integer | |
| R.layout | |
| R.menu | |
| R.mipmap | |
| R.string | |
| R.style | |
| R.styleable | |
| RequesterAddTaskActivity |
An activity where a user in Requester mode can add a task with status "Requested".
|
| RequesterAddTaskActivityTest |
Created by Zhipeng Zhang on 2018/3/14.
|
| RequesterAddTaskController |
Created by kaixiangzhang on 2018-03-11.
|
| RequesterCustomArrayAdapter |
An array adapter for RequesterViewListActivity.
|
| RequesterEditTaskActivity |
An activity where a user in Requester mode can edit a task with status "Requested".
|
| RequesterEditTaskActivityTest |
An intent testing class to test RequesterEditTaskActivity.
|
| RequesterLayout |
An abstract activity which implements the navigation for the Requester options.
|
| RequesterUpdateTaskController |
Created by kaixiangzhang on 2018-03-11.
|
| RequesterViewHolder |
Holds the view objects for the ProviderCustomArrayAdapter.
|
| RequesterViewListActivity |
An activity where the requester can view all of their tasks with status requested, bidded or
assigned.
|
| RequesterViewTaskActivity |
The activity that is displayed when a user in the Requester role views one of their own tasks.
|
| Review | |
| ReviewList |
A custom ArrayList class for handling Review objects.
|
| ReviewListTest |
Created by Hailan on 2018-02-20.
|
| ReviewsAdaptor |
ReviewsAdaptor is used when looking at the profiles of both current user and other users.
|
| ReviewTest |
Created by Zhipeng Zhang on 2018-02-21.
|
| SearchActivity |
An activity where the provider can search for tasks in either requested or bidded states ('open to bidding')
On default it will display the most recently requested tasks/
|
| SignUpActivity |
Allows the user to create a new profile
|
| SignUpActivityTest |
Created by Logan Yue on 2018-03-12.
|
| Task |
This is the entity class for a task object
TODO potentially remove some setters/getters that are not being used
REVIEW AFTER Project part 5 full implementation
|
| TaskList | |
| TaskListTest |
Created by Hailan on 2018-02-20.
|
| TaskTest |
Created by ag on 2018-02-24.
|


The Web - World Wide Web
Invented in the 1990’s and currently consists of approximately 30 Billion pages.
HTML is the common language of the web. While many types of files such as Plain Text, HTML, Images, Videos, and Music, HTML is the main type of document found on the web. The web is comprised of documents linked together via Hyper Links.
HTML - Hypertext Markup Language
HTML is made up of:
• Text Content
• Markup – What it looks like
• References to (e.g. images and videos)
• Links to other pages
Markup is achieved with the use of HTML "Tags."
Tags are often comprised of a set of Opening < X > and Closing tags < / X>
NOTE:Void Tags do not have a Closing Tag.
Element - Everything within a set of opening and closing tags.
Attribute - Property of the HTML element.
Inline / Block
Examples of Inline Tags
< b > - Bold - makes the text bold
< em > - Emphasis - presents the text in an italicized form
< span > - Span - ??? I will learn what this does later
< a href > - Anchor Tag - Used for making links
< img > - Image Tag - Used to include images. Consists of a source location (src=) and alternate text (alt=)
< br > - Line Break - Used set contents on the next line
Examples of Block Tags
< p > - Paragraph - This tag is used to set the contents on a new line but also creates an invisible box around the text that can have additional parameters such as Vertical and Horizontal
< div > - Div - ??? I will learn what this does later


--- title: istio.rbac.v1alpha1 layout: protoc-gen-docs generator: protoc-gen-docs schema: istio.rbac.v1alpha1.RbacConfig schema: istio.rbac.v1alpha1.ServiceRole schema: istio.rbac.v1alpha1.ServiceRoleBinding number_of_entries: 0 ---
Note: The v1alpha1 RBAC policy is deprecated by the v1beta1 Authorization policy. This page is kept for migration purpose and will be removed in Istio 1.6.
Istio RBAC (Role Based Access Control) defines ServiceRole and ServiceRoleBinding objects.
A ServiceRole specification includes a list of rules (permissions). Each rule has the following standard fields:
["*"]
to include all HTTP methods.
This field should not be set for TCP services. The policy will be ignored.
For gRPC services, only POST
is allowed; other methods will result in denying services.In addition to the standard fields, operators can also use custom keys in the constraints
field,
the supported keys are listed in the “constraints and properties” page.
Below is an example of ServiceRole object “product-viewer”, which has “read” (“GET” and “HEAD”) access to “products.svc.cluster.local” service at versions “v1” and “v2”. “path” is not specified, so it applies to any path in the service.
apiVersion: "rbac.istio.io/v1alpha1"
kind: ServiceRole
metadata:
name: products-viewer
namespace: default
spec:
rules:
- services: ["products.svc.cluster.local"]
methods: ["GET", "HEAD"]
constraints:
- key: "destination.labels[version]"
values: ["v1", "v2"]
A ServiceRoleBinding specification includes two parts:
roleRef
field that refers to a ServiceRole object in the same namespace.subjects
that are assigned the roles.In addition to a simple user
field, operators can also use custom keys in the properties
field,
the supported keys are listed in the “constraints and properties” page.
Below is an example of ServiceRoleBinding object “test-binding-products”, which binds two subjects to ServiceRole “product-viewer”:
apiVersion: "rbac.istio.io/v1alpha1"
kind: ServiceRoleBinding
metadata:
name: test-binding-products
namespace: default
spec:
subjects:
- user<EMAIL_ADDRESS>- properties:
source.namespace: "abc"
roleRef:
kind: ServiceRole
name: "products-viewer"


Regular nouns are ending with "a", but not all words ending with "a" are nouns. Some are prepositions, pronouns or numerals. Some nouns can end with consonants. These can represent materials, gases, liquids or names of objects, persons, plants or animals.
Plural
Regular nouns can change coda to "e" or "i" to represent the plural form. Though not all nouns have a plural form and some nouns do not have a singular form. Most nouns that do not end with the vowel "a" do not have plural or does have an irregular plural.
- pana/pane = bread / breads
- idea/idei = idea /ideas
- Alum = garlic (no plural)
- Muska/Mucte = fly/flies
- Vaka/Vatc = cow/cows
- Virus/ Viruc = virus/viruses
- lyna = wool (no plural)
- Moise = family name (only plural)
Notes:
- Words ending with "i" do not always represent plural;
- Nouns ending with "ea" change to "ei" for plural;
- Nouns ending with "ska" change to "cte" for plural;
- Nouns ending with "s" can change "s" to "c" for plural;
- Family names should be plural and can not be singular;
- Some nouns do not follow these rules and may have a distinct plural form;
Gender:
You can use an adjective to specify gender of a person or animal, but also Maj have different words to identify different genders. In the next two examples, gender is implicit.
- Tcika = girl (female)
- Gatsa = boy (male)
- Dona = woman
- Jeta = gentleman
Maj has generic words used to specific gender but also neutral things or objects.
- fema = female
- femo = feminine
- masa = table
- beka = object
- koza = thing
Names:
For names there are some rules: Names of persons or animals ending with consonants or vowel "o" are male. Names ending with "a" are female. Family names ending with "e" are neither feminine nor masculine but plural. It may be used for boys and girls as well.
- Moise Elucian = name (male)
- Moise Laura = name (female)
Names that contain W or Q must be translated in Maj by replacing W with U and Q with K. This rule is for English names, but German names must replace W with V. That is, pronunciation takes precedence over the written name. If a name has numbers in it these numbers will be translated into Maj numbers.
- Wolf = Volf
- William the Third = Uiliam al Rio
- Oliver Queen = Oliver Kuin
In names we replace X with Z. Unlike places where we replace X with Ks. This is to preserve the length of the name. For example:
- Xena = Zena
- Axia = Azia
- Alexandru = Alezandro
Germanic names of places will be altered to follow Maj rules of abbreviation. We replace X with Ks and "y" with "i". Letters Z and S are converted to "Ts" and "Z". Group "St" is converted to "Ct" and Qu is converted to Ku or K. We will have a special dictionary of names. Group "sch" is converted to "tc".
- Leipzig = Laiptsig
- Stuttgart = Ctutgar
- Quedlinburg = Kedliburg
- Deutschland = Doitcland
Maj is a phonetic language. We approximate the original names with Maj writing to get the best pronunciation possible. So in English we make Deutschlang = Germany. This is not how Maj will do it. Instead we preserve the original name pronunciation with slice modification as you can see above. In Maj a noun can end with a consonant so the name Doitcland is a perfect valid Maj name and it has almost the same pronunciation as the German word Deutschland.
English names of persons and places are more difficult to convert into Maj because Maj do not have letter W and letter Y. Both frequent letters in English. We replace "W" with "U" and "Y" with "i". For example:
- Wesley = Uesli
- Wilma = Uilma
Some names look like English names but also German names. In this case, W is converted in V, but it depends. If a person has this name but is born English then U can be used. We also apply the "r" modifier for letter "e" and "a", that will convert to "h".
- Walter = Ualthr (Englishman) or Valthr (Germanic)
- Wagner = Uagnhr (Englishman) or Vagnhr (Germanic)
Acuzativ:
Acuzativ is used when we state something about somebody. For acuzativ you use prepositions: "de/la" = "from/to" and "po /pe = for/ on". These can be in front of the noun to highlight the object. The object can be a noun or a pronoun.
- el bera sonu po alde = the beer is for grown ups;
- ni-ora daru bere la gatse or thike = never give bears to boys or girls;
- ke posu moa sevu la tua? = what I can serve you?
- po me una bera rogu-te = for me one bear please.
Dative:
Dative case is used when somebody is giving something to someone else. For dative we do not use particles. Instead we use a special form of pronoun
- Noh ne paju el bera apo freo; = We like the bear only cold;
- Mie ym paju el bera lex freo; = I like the bear less cold;
Genitive:
The genitive case represents a relation between nouns. Sometimes it represents the ownership relation with the object. Sometimes we use the particle: "al"/"ale" to represent genitive cases.
- este sonu al gace = these belong to the boys.
- kela sonu al mia = that is mine.
- kele sonu ale mia = those are mine.
- zhi venu ale eno = they arrive first.
- noi venu ale bio = we arrive second.
Composite words
You can create new words by linking one adjective with one noun or two nouns together. The new word may have a related meaning but the new meaning is not always easy to guess so you must learn these words from Lexicon.
- novo-jora = today
- novo-sera = tonight
- nejo-tepa = winter
- primo-urba = capital city


Before Change
b_p = agg.EdwBenchmarkPerformance(
total_iterations=2, expected_queries=[Q1_NAME, Q2_NAME])
i1_p = agg.EdwIterationPerformance("1", 2)
s1_p = agg.EdwStreamPerformance(S1_NAME, 2)
q11_p = agg.EdwQueryPerformance(Q1_NAME, Q1_PERFORMANCE, METADATA_EMPTY)
q12_p = agg.EdwQueryPerformance(Q2_NAME, Q2_PERFORMANCE, METADATA_EMPTY)
s1_p.add_query_performance(q11_p)
s1_p.add_query_performance(q12_p)
i1_p.add_stream_performance(s1_p)
b_p.add_iteration_performance(i1_p)
i2_p = agg.EdwIterationPerformance("2", 2)
s2_p = agg.EdwStreamPerformance(S1_NAME, 2)
q21_p = agg.EdwQueryPerformance(Q1_NAME, Q1_PERFORMANCE, METADATA_EMPTY)
q22_p = agg.EdwQueryPerformance(Q2_NAME, Q2_PERFORMANCE, METADATA_EMPTY)
s2_p.add_query_performance(q21_p)
s2_p.add_query_performance(q22_p)
i2_p.add_stream_performance(s2_p)
b_p.add_iteration_performance(i2_p)
self.assertTrue(b_p.aggregated_query_status(Q1_NAME))
self.assertFalse(b_p.aggregated_query_status(QFAIL_NAME))
After Change
b_p = agg.EdwBenchmarkPerformance(
total_iterations=2, expected_queries=[Q1_NAME, Q2_NAME])
i1_p = agg.EdwPowerIterationPerformance("1", 2)
i1_p.add_query_performance(Q1_NAME, Q1_PERFORMANCE, METADATA_EMPTY)
i1_p.add_query_performance(Q2_NAME, Q2_PERFORMANCE, METADATA_EMPTY)
b_p.add_power_iteration_performance(i1_p)
i2_p = agg.EdwPowerIterationPerformance("2", 2)
i2_p.add_query_performance(Q1_NAME, Q1_PERFORMANCE, METADATA_EMPTY)
i2_p.add_query_performance(Q2_NAME, Q2_PERFORMANCE, METADATA_EMPTY)
b_p.add_power_iteration_performance(i2_p)
self.assertTrue(b_p.aggregated_query_status(Q1_NAME))
self.assertFalse(b_p.aggregated_query_status(QFAIL_NAME))


|
mpi_cmake_modules
|
We define here a couple of useful macros to ease the management of the Protobuf message code generation.
This CMake module provide 2 macros that both work in collaboration with Catkin. Both macros will provide the generated C++ message source files. In addition to this one can generate the Python files by setting the following CMake variable:
set(PROTOBUF_COMPILE_PYTHON ON)
These files will be installed in the correct Python directory.
The first macro is a generic purpose macro which can be used in any project.
protobuf_catkin_generate_cpp(src_path srcs hdrs)
This macro takes the path to the folder in which you stored you *.proto
files. This path is relative to your project path.
This macro then fills in the SRCS
and HDRS
variables with the generated C++ sources generated from the protobuf generator.
One then need to build this files by hand by creating a library.
This macro expect that you have put the *.proto
files in the protobuf
folder located in your project root PROJECT_PATH/protobuf/
. Then calling:
protobuf_catkin_generate_lib(my_protobuff_messages)
Will create the CMake target my_protobuff_messages
which you can depend on:
target_link_libraries(my_target my_protobuff_messages)


KAIROS SOCIETY PORTUGAL
Kairos Society Portugal started in late 2012 and has been actively linking the most entrepreneurial and outstanding students in Portugal.
Kairos Society Portugal aims to connect the young entrepreneurs and visionary leaders to fellows in other countries and reputable mentors that will help our fellows taking their projects to the next level. We are building the basis for those who dare to think big to bring their visions into reality.
Currently we have members that are part of startups that aim to disrupt the industry they are in, founders of entrepreneurship clubs, CEOs of microfinance organizations and other future leaders.
KAIROS PORTUGAL FELLOWS
Ana Margarida Marcos
Margarida is the Co-CEO of C-MOVE, a microfinance student run organization that operates in Portugal, Mozambique, São Tomé e Príncipe and Timor-Leste, since 2012. Before, Margarida worked for 6 months as a fellow of C-MOVE in Mozambique helping with microfinance and consultancy to local businesses, coaching entrepreneurs and developing new ways of developing the local businesses and the educational system. With a degree in Management at Nova School of Business and Economics (2008-2011), she is currently concluding a Marketing internship at Henkel, to go back to Nova SBE for a Management Masters.
André Albuquerque
André Albuquerque is a Master business student majoring in Technology Entrepreneurship and Innovation Strategy at Católica Lisbon School of Business and Economics.
He worked at Google as Strategic Partnerships Intern both at European HQ in Dublin and Global HQ in California. Previously he won the 2012 Google Europe Ambassador program and was selected to the Associate Summer Internship program at Google in 2011.
André has worked multinational companies, small businesses, start-ups, NGO's, entrepreneurship organizations and education entities.
Catarina Martins
Catarina is a student of Industrial Management Engineering, at IST. She is an active member of a student branch of IEEE, taking part in several social and academic projects. Lately she coordinated an entrepreneurial event and competition in Mobile Apps. She's also a member of: NEEGI, promoting the binding of technological knowledge with management skills, and fostering interchange of students in Europe; ESTIEM, as delegate from Lisbon, and member of the Organizing Committee of the next European Council Meeting. She also likes to collaborate with companies in events like entrepreneurship boot camps and team-building activities.
David Dias
David is a Communication Networks Engineer, taking now a Masters on Cloud Computing, P2P networks and Mobile applications at IST,. He is, as well, an IEEE Volunteer serving as IEEE Computer Society Student Ambassador for Region 8(EMEA) and the Google Student Ambassador for Europe representing Portugal. David lives his days trying to push forward the humanity by being a catalyst of his peers, trying to make the most of the energy he puts in every project he is up too, whether it is related to his field of studies or not.
You can find David motivating everyone around me to make something happen, or trying to develop the next big thing in WebDev.
Davis Gouveia
Passionate about entrepreneurship, education and new technologies, with only 18 years old helped to found one that ended up becoming one of the most popular educational portals in Portugal, www.exames.org. During the next 5 years he continued with this project and, in the meanwhile, became tge president at JUNITEC, one of the most innovative junior enterprises in the country. Since then he is vice president at JADE Portugal, the Portuguese Federation of Junior Enterprises, part of the organizingteam member of Startup Pirates @ Lisboa and founding member of the Daring Project.
João Figueirinhas Costa
João is a naturally born networker and communicator with an entrepreneurial spirit, wanting to turn our world into a more conscious, sustainable and healthy ecosystem, in all ways. He believes innovations in education and public governance are two of the main ways in which his objective, shared by many, can be attained. João is a senior student at the Portuguese Catholic University, where he is studying economics. Over the last 3 years he has worked in Portugal and China, in a variety of sectors, including Talent Management and Recruitment, Hotel Management, B2C Tourism Industry, Banking and Tech Startups such as Groupon and Wimdu.
João Freire de Andrade
João is the founder of BET, Bring Entrepreneurs Together. BET’s mission is to promote entrepreneurship by creating opportunities to gather students from different Universities and areas of knowledge. João is the founder and CEO of t-shirt lovers, a web based startup that have as mission the objective of creating the biggest clothing community. He has also been a MOVE Micro Finance fellow in Mozambique. In this project he helped 7 poor entrepreneurs starting their businesses.
His under degree in economics was in NOVA and is currently finishing the thesis in Católica Lisbon, with a focus on startup valuation.
José Pedro Silva
19-year-old José Pedro studies, simultaneously, Mathematics at the University of Porto and Management at the Catholic University of Portugal (UCP) with a merit scholarship. He currently is the CFO of Católica Students’ Corporation, UCP’s junior enterprise, and an active member in other projects such as the School of Economics and Management’s Debate Club and its academic newspaper, while also preparing students to take the BMAT.
Interested and passionate about everything he does, José Pedro is searching for the best way to leave its mark in this world. He is known as a results-driven and persistent person with remarkable analytical and execution skills. Capable of solving problems efficiently, has a great will to keep doing even more and better.
Mario Nzualo
Originally from Mozambique, has spent half of his life in Portugal and half in Mozambique.Currently living in Lisbon and finishing his Master Degree in Communication Networks Engineering and specializing in Mobile Payments.
Loves to travel and meet new people and cultures. Spends most of his time traveling all over Europe while leading a pan-European organisation of 4200 technical students, BEST (Board of European Students of Technology).
Pedro Balas
Pedro is a student of Mechanical Engineering at IST- In 2008, he invented the internationally patented Electric Spherical Generator (ESG). In 2009, he founded the company EMOVE, becoming CEO, in order to accomplish the goal of taking the ESG to several markets, with a stronger focal point in the wave energy industry. Between 2009 and 2010, along with his company, he won seven distinct prizes. Since June 2011, he established a new office in Silicon Valley, California, through an invitation of the incubator Plug and Play Technology Center. By the Summer of 2012, EMOVE patented its technology internationally, and built and tested the most efficient electromechanical converter in the world. His major objectives in three years are to make wave energy economically viable and capacitate wind turbines with this efficient technology, and to build and test real scale prototypes for both applications.
Pedro Conceição
<EMAIL_ADDRESS>Pedro is the founding presidente of Kairos Portugal. While doing his masters at the Maastricht University, he decided it would make perfect sense to connect the most outstanding Portuguese students to their peers around the world. Pedro has studied and worked in a number of countries such as Brazil, China and India, among others. In the meanwhile he has founded, with friends, a youth nonprofit organization and a startup. Currently he is working with social entrepreneurs in Lisbon.
Raquel Inácio
Master student of Electrical and Computer Engineer at IST. Since the first year of university she has participated in new projects and technological activities. She joined JUNITEC (first junior company in Portugal) in 2009, and since then has evolved and nowadays is the President. Concerned not only with the development of technology and entrepreneurship, but also with the society and human relations, she did volunteer work in a local Hospital with children. Fond of sports, practices tennis, mountain biking and jogging.
Rui Costa
Rui Costa is a Network and Communications Engineering Masters student with deep concerns in making a change in several technological and academic areas, having as main research and thesis topic Vehicular Ad-hoc Networks. Currently he is working on his master thesis that aims to develop an agnostic application development platform for vehicular networks environments that facilitates applications development while creating a low cost alternative to such systems.
Rui is also an experienced presenter and has led several presentations to different targets of several topics. Currently he is leading a global project for IEEE that aims to develop and spread the creation of local education resources based on multimedia resources and technologies in several countries.
Vasco Sousa
Born in São Mamede de Infesta, county of Matosinhos, in March 1989, Vasco Sousa is a student of the Integrated Master of Industrial Engineering and management of the Engineering Faculty of the University of Porto. He is currently the consultant of Research and Development at Hidros, the junior enterprise of engineering of the State University of Rio de Janeiro, the institution where is doing a student exchange program. In October 2009 Vasco Sousa joined the management board of the Entrepreneurship Club of the University of Porto (CEdUP), responsible for the dissemination of the entrepreneurship spirit among the academic community, assuming the position of president of the organization in January 2011.


You show low signs of stess and you are implementing plenty of strategies to cope.
You show average signs of stess and you are implementing a normal amount of strategies to cope.
You show more than average signs of stess and you need to implement more coping strategies.


Project subjectSolution overview
Project management : RedmineContinuous integration : Cloudbees / Jenkins
Clone a Git project on Netbeans
oauth
Grails tricksImportant links


Privacy notice
Effective: 2014-01-01
Applicability
This privacy notice applies only to the IT Communications Office (it.iu.edu) and explains our practices concerning the collection, use, and disclosure of visitor information. Visitor information collected by IT Communications Office will be used only as outlined in this privacy notice.
Other units at the university may collect and use visitor information in different ways. Therefore, visitors to other university websites should review the privacy notices for the particular sites they visit. IT Communications Office is not responsible for the content of other websites or for the privacy practices of websites outside the scope of this notice.
Changes
Because Internet technologies continue to evolve rapidly, IT Communications Office may make appropriate changes to this notice in the future. Any such changes will be consistent with our commitment to respecting visitor privacy, and will be clearly posted in a revised privacy notice.
Collection and Use
Passive/Automatic Collection
When you view pages on our site, the web server automatically collects certain technical information from your computer and about your connection.
This website is hosted on Webserve, a shared web-hosting environment provided by IU's University Information Technology Services. For more information about privacy practices related to Webserve, read the Webserve Privacy Notice Supplement.
In addition to any information collected by Webserve, our server and/or site collects the following:
- your IP address
- the domain name from which you visit our site
- user-specific information on which pages are visited
- aggregate information on pages visited
- the referring website
- the date and time of visit
- the duration of visit
- your browser type
- your screen resolution
Continued use of our website indicates consent to the collection, use, and disclosure of this information as described in this notice.
Some technical information is retained in aggregate; it may not have a current retention/deletion schedule.
Active/Manual/Voluntary Collection
Other than automatically collected technical information about your visit (described above, or cookies, described below), we may ask you to provide information voluntarily, such as through forms or other manual input-in order to make products and services available to you, to maintain and manage our relationship with you, including providing associated services or to better understand and serve your needs. This information is generally retained as long as you continue to maintain a relationship with us. Your providing this information is wholly voluntary. However, not providing the requested information (or subsequently asking that the data be removed) may affect our ability to deliver the products or service for which the information is needed. Providing the requested information indicates your consent to the collection, use, and disclosure of this information as described in this notice. Information we may actively collect could include:
- the email addresses of those who communicate with us via email
- name
- information volunteered by the visitor, such as preferences, survey information and/or site registrations
Information Usage
This information is:
- used to improve the content of our site
Information Used For Contact
If you supply us with your postal/mailing address:
- You will only receive the information for which you provided us your address.
Information Sharing
We may share aggregate, non-personally identifiable information with other entities or organizations.
We do not share any personally identifiable information with other entities or organizations, except when legally required to do so, at the request of governmental authorities conducting an investigation, to verify or enforce compliance with the policies governing our website and applicable laws, or to protect against misuse or unauthorized use of our website.
Except as described above, we will not share any information with any party for any reason.
Except as provided in the Disclosure of Information section below, we do not attempt to use the technical information discussed in this section to identify individual visitors.
Cookies
A cookie is a small data file that is written to your hard drive that contains information about your visit to a web page. If you prefer not to receive cookies, you may configure your browser not to accept them at all, or to notify and require approval before accepting new cookies. Some web pages/sites may not function properly if the cookies are turned off, or you may have to provide the same information each time you visit those pages.
In order to customize the information and services offered to you, our site uses cookies to:
- record user-specific information on what pages users access or visit
- customize web page content on visitors' browser type or other information that the visitor sends
Children
This site is not directed to children under 13 years of age, does not sell products or services intended for purchase by children, and does not knowingly collect or store any personal information, even in aggregate, about children under the age of 13. We encourage parents and teachers to be involved in children's Internet explorations. It is particularly important for parents to guide their children when they are asked to provide personal information online.
Use of Third Party Services
This website uses Google Analytics, a web analytics service provided by Google, Inc. ("Google"). Google Analytics uses cookies (described above) to help the website analyze how users use the site. The information generated by the cookie about your use of the website (including possibly your IP address) will be transmitted to and stored by Google.
For more information, please visit Google's Privacy Policy.
Disclosure of Information
Other than sharing your information with other appropriate university personnel and units to ensure the quality, functionality, and security of our website, or manage your relationship with us, we will not disclose personally identifiable information about your use of the site except under the following circumstances:
- With your prior written (including email) consent
- When we have given you clear notice that we will disclose information that you voluntarily provide
- With appropriate external parties, such as law enforcement agencies, in order to investigate and respond to suspected violations of law or university policy. Any such disclosures shall comply with all applicable laws and university policies.
Security
Due to the rapidly evolving nature of information technologies, no transmission of data over the Internet can be guaranteed to be completely secure. While we are committed to protecting the privacy of our visitors, we cannot guarantee the security of any information that you transmit to university websites, and you do so at your own risk. However, once we receive your information, we will use reasonable safeguards consistent with prevailing industry standards and commensurate with the sensitivity of the data being stored to maintain the security of that information on our systems.
In addition, we will comply with all applicable federal, state and local laws regarding the privacy and security of visitor information.
We have appropriate security measures in place in our physical facilities to protect against the loss, misuse, or alteration of information that we have collected from you at our site.
Privacy Notice Changes
From time to time, we may use visitor information for new, unanticipated uses not previously disclosed in our privacy notice.
We will post the policy changes to our website to notify you of these changes and provide you with the ability to opt out of these new uses. If you are concerned about how your information is used, you should check back at our website periodically.
Visitors may prevent their information from being used for purposes other than those for which it was originally collected by:
- sending us an email at the listed address
Contact Information
If you have questions or concerns about this policy, please contact us.
IT Communications Office
2709 E. 10th St.
Bloomington, IN 47408
<EMAIL_ADDRESS>If you feel that this site is not following its stated policy and communicating with the owner of this site does not resolve the matter, or if you have general questions or concerns about privacy or information technology policy at Indiana University, please contact the chief privacy officer through the University Information Policy Office, 812-855-UIPO, privacy@iu.edu.


As a leader of a product development team you might have a PM that you’re working with, but some of your role will involve deciding how/when product is built, who builds what, etc. So you’ll need to level up your product skills.
After 15 Years as a Product Leader, CEO and Now VC, Here’s the Advice I Always Share with Future Founders - by FirstRound Capital. Takeaway: Todd Jackson (former product manager of Gmail, among other credentials) on how “[b]uilding really high-quality products takes an incredible amount of behind-the-scenes discipline, especially as your team grows.” He also advises to protect quality and the user experience, and to take a site reliability engineering approach.
Aligning Projects with Business Goals - by Anthony Eden. Provides a simple project management spreadsheet of six questions: 1) What is the problem we are trying to solve?; 2) What does success look like, and how does it fit in the big picture?; 3) What are the MUST DO and the MUST NOT DO items?; 4) What is the deadline?; 5) Who should I talk to for help and get feedback?; 6) Have we done this before? Something we already have to get started?
Am I a Product Manager or a Product Owner? Part 1: Confusion Abounds - by Ellen Gottesdiener. Takeaway: a five-part article series on differentiating the roles, with lots of keen insights and explanations. Part 2: Part 2: 5 Ways to Untangle the Mess.
From Apathy to Autonomy (video) - by Darko Zelić.
The Art of Project Management - notes by Joe Golberg about Scott Berkun’s book.
The Art of the Start: The Time-Tested, Battle-Hardened Guide for Anyone Starting Anything - by Joe Goldberg. Notes about the book by Guy Kawasaki.
Blue Ocean Strategy - notes by Joe Goldberg about the book by W. Chan Kim and Renée Mauborgne.
The Bootstrapper’s Bible - Joe Goldberg’s notes about the book by Seth Godin.
Designing Workshops that Work: Getting Better at Brainstorming - by Cindy Chang. Takeaway: Start with an overview, work backwards and think in chunks to start a plan as well as about outcomes, detail, delegate.
Do the Simple Thing First: The Engineering Behind Instagram - by Harry McCracken. Takeaway: Instagram founders made technical decisions using a principle which favored practicality over perfection. “If it solves a problem and gets us closer to launch, let’s do it.”
Everyone Forgets Technical Research - by Product Habits. Takeaway: Offers a step-by-step template for creating a 1-3 page technical research outline that will enable product leads to communicate plans more effectively with developers, who can then better do the research on their side required to build a product successfully. “The outline should be a short summary of what you’re looking to create, including required features and functionality. You should also provide guidance on what matters most to you (and customers). What’s the core problem you’re looking to solve, and how do you plan to solve it? What are the most important parts of what you’re building?”
Growing Your Tech Stack: When to Say No - by Jessica Kerr. Takeaway: An exploration of what tools are Low-Risk (local developer utilities), Moderate Risk 1 (deployment infrastructure), Moderate Risk 2 (programming language), and serious risk (database). “When you do accept a technology into your stack, make sure it has an owner. Spread knowledge through pairing, documentation, and communication. Make responsibility explicit and set aside time for maintenance, upgrades, and reassessment. The right technology today will be the wrong technology at some point.”
Growth Hacking Notebook - notes by Joe Goldberg.
Here’s How to De-Risk Your Product Strategy - by Jeff Gothelf. Takeaway: Strategic planning involves three questions: who’s the target market, what’s the value proposition, and what’s your Key Result.
How Compare and Contrast Decisions Lead to Better Product Outcomes (slides) - by Teresa Torres. Takeaway: A detailed look at how to bring focus to product decisions, including suggested tools like the “opportunity solution tree.”
How to Kickstart and Scale a Marketplace Business – Phase 1: 🐣 Crack the Chicken-and-Egg Problem (Part 1/4) - by Lenny Rachitsky. Takeaway: insights from Airbnb, DoorDash, Thumbtack, Etsy, Uber and other companies on how to scale a marketplace. Crack the chicken-and-egg problem, scale your marketplace, then evolve it.
How to Make Things High-Quality - by Julie Zhuo. Takeaway: “When you get into a TTBQT (‘The Tradeoff Between Quality and Time’) state, the real question to ask is: ‘If we knew X would take this long to get to high-quality, would we have opted to do it in the first place?’”
How New Startups Can Win at PR — Advice from a 20-Year Comms Career - by FirstRound. Takeaway: Terra Carmichael, VP of Global Communications at Eventbrite, offers tips on attracting media coverage.
How to Sell the Problem Before Selling the Solution - by David Bailey. Takeaway: Tactical ways to express customer needs and “lead with the need.”
Hypergrowth and The Law of Startup Physics - by FirstRound Capital. Takeaway: “The law of startup physics: humans grow linearly, companies grow exponentially.”
In Praise of SWARMing - by Dan North. Takeaway: “I am offering a new acronym, SWARMing: Scaling Without A Religious Methodology. My argument isn’t that packaged scaling methods are unhelpful per se, rather that they are neither necessary nor sufficient for successful transformation. They can be anything from a useful starting point to an expensive distraction, but one thing they are not is a solution.”
Informal Doesn’t Scale - by Jim Grey. Takeaway: “People sometimes fetishize startup smallness. It feels so good! But clinging to it will limit your growth trajectory. Like the overgrown fly, lack of process will crush your company. You need to change your ways of working to fit the company’s size. But this doesn’t have to be terrible. It totally can be terrible, if you do it wrong. Even if you do it right, it will change and even get rid of some of your company’s original goodness. But it enables new levels of goodness that you can’t imagine yet.”
Key Learnings in My First Year as a PM at Amazon - by Venkatraman Prabhu. Takeaway: Lessons learned after a year at the global retailer. Choose the right manager, always measure the product’s impact, keep experimenting, have weekly 1:1’s with key stakeholders, and get advice.
Knowns vs Unknowns — Are You Building a Successful Company or Just Typing? - by Aaron Batalion. Takeaway: “You’re probably not the only one in the world with your idea, but if you focus the best people in the room on only the known unknowns, you’ll have a much better shot at winning.”
Lean-Agile Product Management - by Jez Humble. Takeaway: the course website from Humble’s class at UC Berkeley, with syllabus and resources that cover the product lifecycle, team-building, and other key topics. Includes lots of links to talks/articles/etc. that you might also find linked to here.
Lean Startup - notes by Joe Goldberg about the book by Eric Ries.
LeanStartup.com - based on the book. Offers an e-newsletter.
Little Red Book Of Selling: 12.5 Principles of Sales Greatness - notes by Joe Goldberg about the book by Jeffrey Gitomer.
The MVP is dead. Long live the RAT. - by Rik Higham. Takeaway: “There is a flaw at the heart of the term Minimum Viable Product: it’s not a product. It’s a way of testing whether you’ve found a problem worth solving. A way to reduce risk and quickly test your biggest assumption. Instead of building an MVP identify your Riskiest Assumption and Test it. Replacing your MVP with a RAT will save you a lot of pain.”
Notes from “Good Strategy / Bad Strategy” - by Jeff Zych. Takeaway: a focused overview of the book by UCLA Anderson School of Management professor Richard P. Rumelt. “Strategy is designing a way to deal with a challenge. A good strategy, therefore, must identify the challenge to be overcome, and design a way to overcome it. To do that, the kernel of a good strategy contains three elements: a diagnosis, a guiding policy, and coherent action.” Includes some critical thoughts on OKRs.
Observations on Product Management - by Dan Hill. Takeaway: “Most Product Managers (and everyone probably) spend too little time thinking about how to solve a problem. They jump straight into solving it. Problems come in different shapes, and not all need the same process. The process that shipped the last product is unlikely to be the one that you need for the next…Incremental development and vision are not orthogonal; they both require the other. All product must start with a vision — a point of view — but then be built critically step by step. It’s ok to learn something new as you go.”
The Only Metric That Matters — Now With Fancy Slides! - by Josh Elman at Greylock Partners. Takeaway: “[T]he only thing founders need to think about is: Are people using your product? Are they using it how you expect (i.e performing the core action)? And, are they performing the core action at the frequency you expect?”
The Product Dartboard - by Janet Brunckhorst at Carbon Five. Takeaway: offers a deep dive/description of a tool that assesses a team or individual against attributes associated with project success.
Product Discovery Anti-Patterns Leading to Failure - by Stefan Wolpers. Takeaway: “The main contributing variables to various product discovery anti-patterns are: * Existing organizational dysfunctions, for example, the organization is structured in functional silos; * A substantial degree of ego issues among individual players—the what-is-in-for-me-syndrome—resulting in personal agendas being pursued; * A complex, multi-layered reporting structure within organizations that filters as well as delays the flow of information, thus impeding communication and decision-making.”
Product Manager vs. Product Owner - by Melissa Perri. Takeaway: “A good Product Manager is taught how to prioritize work against clear outcome oriented goals, how to discover and validate real customer and business value, and what processes are needed to reduce the uncertainty that the product will succeed in market. Without this background in Product Management, someone can effectively go through the motions of Product Owner role in Scrum, but they can never be successful in making sure they are building the right thing.”
The Product Manager Superpower: User Science - by Brent Tworetzky. Takeaway: “While finding the perfect user-product fit is rarely easy, trained product managers can find great fits consistently with User Science–the field of deeply understanding people interacting with products through rigorous toolings and process. User science involves understanding both user needs (identifying which problem to solve) and user behaviors (understanding how and why users react to products). This distinction is important: winning products need both a meaningful problem to solve and strong execution.”
Product Strategy Means Saying No - by Intercom. Takeaways: Review common reasons for making product decisions and ask whether they are actually good for the product.
Reminder: Your “Product” Company is Just an Implementation Detail - by Jeremy Baker. Takeaway: The progress our customer wants to make is the most important thing. We think about our features and what they can do, and present them that way. When we do this, we’re “forcing our customer to do the hard work. They have to map features to their process and figure out if it helps them make progress … Instead, talk about the progress our customer wants to make, and build tools that enable that progress.”
Risk Assessment and Prioritization for Startups - by Leo Polovets. Takeaway: a slide deck about the value of addressing risks head-on, and early. Includes self-assessment tips.
Scaling Airbnb with Brian Chesky — Class 18 Notes of Stanford University’s CS183C - by Chris McCann. Takeaway: about Airbnb’s “10 star service” thought experiment, in which they transcended the usual five-star review by adding five more measurements for success.
The Scrum Product Owner Theses - by Stefan Wolpers. Not necessarily tied to the Scrum agile framework, this list of 56 “theses” addresses the PO’s role; examines product discovery and stakeholder management; roadmap planning, and more.
The Shortest Path Is the Scariest - by Omri Ben Shitrit. Takeaway: “To be good at execution … Continuously identify the next most important problem we should be solving for our customers. We’ve written about this in the past. Understand (roughly) the cost and benefit of solving the problem, and our confidence level in both side of the equation. Find the optimal set of tradeoffs between product scope and engineering costs in solving the problem.”
To Grow Faster, Hit Pause — and Ask These Questions from Stripe’s COO - by First Round. Takeaway: “There’s a list of questions companies should ask themselves as they head into rapid growth — ideally in that relatively brief moment right after clinching product-market fit.” The post provides these questions, to help you become less reactive and more proactive in managing your growth.
Transforming from Projects to Products - by John Yorke. Takeaway: “Agile Transformation means thinking of Products rather than Projects. Agile is a Mindset not a set of rules to be followed. It requires a cultural change not a process change. Agile changes the way we measure project success and how we measure people’s behaviour. Change is Hard. Project Management and People Management are those that need to change the most.”
The Ultimate Question - notes by Joe Goldberg about the book by Fred Reichheld, which focuses on measurements like the net promoter score (NPS).
Veteran CTO (with Multiple Successful Exits) Answers Your Top Startup-Building Questions - by FirstRound. Takeaway: an interview with/profile of Adil Ajmal, CTO of LendingHome, who has scaled up teams at seven tech organizations. He covers topics ranging from interviewing to hiring a VP Product.
What Happens When Startups Turn from Their Innovation Stage to Operational Excellence? - by Mark Suster. Takeaway: “Startups are fun and exhilarating and filled with challenging problems to solve. To the neophyte it seems like startup challenges are strictly product or technical in nature but to innovate, systematize and scale a billion dollar company it involves way more decisions about strategy, economics, resource allocations and team composition.”
When, Which…Design Thinking, Lean, Design Sprint, Agile? - by Geert Claes. Takeaway: “It probably makes more sense to just look at Design Thinking, Lean, Design Sprint & Agile as a bunch of tools and techniques in one’s toolbox, rather than argue for one over the other, because they can all add value somewhere on the innovation spectrum.”
Why Software Sucks - by Scott Berkun. Good ways to think about why it happens and what you can do to make it happen less.
All About OKRs: How To Set Them, Achieve Them, And Track Them In Trello - by Kevan Lee. Takeaway: A concise and clear description of what OKRs are and how to create them (i.e., for both productivity as well as agile/cultural reasons).
Applying OKRs - by Dan North. Takeaway: Insights from Dan about working with companies applying Objectives and Key Results; do’s and dont’s.
Awesome-OKR - by Domenico Solazzo. Takeaway: an Awesome List of OKR-related decks, articles and videos.
Beyond OKRs: The Formula for High Performing Teams (video) - by Christina Wodtke. Takeaway: the creator of Radical Focus talks about different kinds of teams, team-building, experiential learning, and more.
Learn OKR - by Felipe Castro. Takeaway: A comprehensive resource of information on how to create and plan to OKRs. Includes a link to a free, downloadable book.
OKRs - by Eleganthack. Takeaway: articles on personal OKRs, “one objective to rule them all,” and miscellaneous resources.
OKRs.com - by Ben Lamorte. Takeaway: a resource for anyone using Objectives and Key Results (OKRs) or considering using OKRs to make measurable progress on their most important goals at work.
Set Goals with OKRs - by re:Work. Takeaway: a step-by-step guide to creating, developing and grading OKRs.
Why OKRs Are Not Delivering the Result Executive Managers Expect - by Veronika Goncalves. Takeaway: “In many cases, when organizations apply OKRs, they apply the process the in the same format as Management by Objectives: using a Top-Down Approach. But this format does not create value for the organization because the top managers do not understand what the customer’s real problems are. When defining the objectives, they are usually not in alignment with the company’s current reality.” Also, OKRs might not be the right framework for every company; consider options like agile portfolio management.


<https://github.com/rbsriobr/SBW>
User guide (.pdf)Screencasts
See an interactive
presentation (28MB)
See video (Youtube)
Youtube video
1. Download and install AutoHotkey.
2. Download
this AutoHotkey script.
3. Based on your needs, edit this script. The documentation of AutoHotkey
may help you.
The SendInput function sends a string to the window that has focus.
... FUNC_FORWARD( ) { SendInput, Forward{Enter} } ...
4. Run the script.
5. Run SBW, connect (See screencast)
Download file
(.svg)
Download
an AutoHotkey script for Blender 3D (use a plain text editor to edit it)
Note. This script will remap keys and buttons. When working with another
application, suspend it to avoid unnecessary workload on the cpu. (See tray icon
menu)


Find nice route
We will help you create a nice tour for the day. Choose from options below...
City:
Choose City
San Francisco, CA
Chicago, IL
New York, NY
Los Angeles, CA
Travel mode:
Driving
Walking
Bicycling
Transit


Crime Finder
Created By Edgar and Chris
Twitter
Facebook
Instagram
Find The Crime Today
Chose a district below to find a set of crimes that were reported to that district
Choose a District
District 1 - Central
District 2 - Wentworth
District 3 - Grand Crossing
District 4 - South Chicago
District 5 - Calument
District 6 - Gresham
District 7 - Englewood
District 8 - Chicago Lawn
District 9 - Deering
District 10 - Ogden
District 11 - Harrison
District 12 - Near West
District 14 - Shakespeare
District 15 - Austin
District 16 - Jefferson Park
District 17 - Albany Park
District 18 - Near North
District 19 - Town Hall
District 20 - Lincoln
District 22 - Morgan Park
District 24 - Rogers Park
District 25 - Grand Central
Search!


{% extends "base/base.html" %} {% load crispy_forms_tags %} {% block content %}
Enter your email address and click the "Send Link” button. A link to reset your password will be sent to your email address


Universally Accessible Cross Origin Request
With CORS, Ajax requests can be made across domains
Loaded content goes here.


private lateinit var coordinatorLayout: CoordinatorLayout
The CoordinatorLayout used as the root of the layout being displayed.


|
|
|
| SANDWICH SHIP SUPPLY |
| Current Conditions as of 8:05 Wednesday, September 9, 2015 |
|
|
| Outside Temp |
74.3 F |
74.3 F |
08:04 |
72.5 F |
05:53 |
| Outside Humidity |
93% |
96% |
06:30 |
91% |
00:00 |
|
| Inside Temp |
72.7 F |
77.4 F |
00:00 |
72.1 F |
07:21 |
| Inside Humidity |
68% |
68% |
07:11 |
52% |
00:00 |
|
| Heat Index |
78.0 F |
77.0 F |
07:23 |
|
|
| Wind Chill |
72.0 F |
|
|
71.0 F |
00:43 |
| Dew Point |
72.0 F |
72.0 F |
04:39 |
71.0 F |
00:00 |
|
| Barometer |
29.917" |
29.923" |
00:19 |
29.890" |
05:17 |
| Bar Trend |
Rising Slowly |
|
|
|
|
|
| Wind Speed |
10 KT |
22 KT |
06:27 |
|
|
| Wind Direction |
WSW 254° |
|
|
|
|
|
| 12 Hour Forecast |
Increasing clouds with little temperature change. |
|
|
|
| Average Wind Speed |
10.1 KT |
7.8 KT |
|
|
|
| Wind Gust Speed |
|
14.8 KT |
|
|
|
|
|
|
| Rain |
0.00"/Hour |
0.00" |
0.00" |
0.00" |
19.55" |
| Last Hour Rain |
0.00" |
|
|
|
|
|
|
|


A mapathon is an event where participants contribute to an open source map. Mapathons are generally done for relief purposes. The public is invited to make improvements in a pre-selected geographical area to improve coverage and to help disaster relief workers asses risk and plan accordingly. Several online tools facilitate mapathons, like the HOT Tasking Manager used as an example in this guide.
When a hurricane or an earthquake strikes, mapathons become a valuable tool to help ground responders from afar. Libraries, universities, colleges, digital labs, and similar groups are perfect organizations to help translate the good will of many volunteers into data that can save lives. The event in turn becomes a way to open the door to the work that your digital team does outside urgencies. The same techniques used to map disaster zones—drawing and verifying geometries on a raster image—are used to do other types of cultural and scientific work, for example.
Learn more at Missing Maps.
A mapathon can bring substantial positive attention to your office, and help you build many connections around your campus. A mapathon, in turn, can benefit from full institutional support and your help. If you are a top-administrator, you can use this framework to help you create your own preparedness plan for mapathons suited to your local environment. The most important job you can do is to make sure that the top-level communication channels of the university are available to the organizers to help fill the rooms with volunteers.
Something else you should consider is giving the option to a large number of your staff to participate in the event. Not only will this increase the amount of relief data, this is bound to increase morale in your institution.
You don’t have to wait until disaster hits to begin preparations for your institution and your team. Here are some of the things you can do to react more efficiently the day that disaster does strike, and you want to help out:
Rooms: Do a survey of the rooms available to you that are amenable for mapathons. Depending on your public, you might want to identify rooms that have a combination of PCs and tables for laptops; others might be better served by a large room with tables or desks for laptops alone. Keep the list of those rooms easily accessible. Make sure the rooms have a good amount of outlets and good Internet. You can supplement with extension chords.
Communications: Talk to your communications team to see what kinds of rapid-response capacity they have. Make sure the university’s top communication team is also ready to help you fill the room(s). Identify what networks are available to you or your team directly on social media or email, and keep a list. Prepare a template for a mapathon poster and have that ready. We recommend you design for respect for the gravity of the situation without sacrificing attention-grabbing.
Skills: Many academic institutions and labs have one or several GIS specialists on staff. Identify who they are and make sure to talk to them to gage their own readiness to teach beginners how to use the tool. If a GIS specialist is not on hand, identify technologists who are willing to research and learn how to use the tool.
If everything is in place the following steps can be deployed in 6-7 days.
A project is only partially complete once a preliminary open source map has been made. Any mapping project on Open Street Maps, for example, goes through two phases before it is considered complete and made public:
The former requires only basic skills and is easily suitable for a mapathon. The OSM documentation suggests that you need to be experienced for the latter, but beginners can still usefully participate in the validation process by pinpointing particular parts of the review process and marking your work for the review of other experienced users. Even if your event happens once the mapping phase is mostly complete, your team can help carry the project to completion by working on this quality control portion of the process.
See the resources below for tutorials on how to incorporate validation into your mapathon.
We welcome your feedback. If you have ideas on how to improve this model, don’t hesitate to contribute.


guide_chromatic.Rd
This 'guide' is not really a guide, but a decision function for chromatic scales. It chooses the guide based on the number of channels a chromatic scale has seen data from. It is the default guide for the chromatic scales.
guide_chromatic( title = waiver(), ..., available_aes = c("colour", "color", "fill") )
| title | A character string or expression indicating a title of guide.
If |
|---|---|
| ... | Captures arguments to pass down to the constructor of the chosen guide. |
| available_aes | A vector of character strings listing the aesthetics for which a colourbar can be drawn. |
A chromatic_guide
S3 object.
This 'guide' chooses in the following ways based on the number of channels for which data is available.
chooses guide_none()
chooses guide_colourbar2()
chooses guide_colourrect()
chooses guide_colourcube()
chooses guide_colourcube()
with 3 channels
The scale_chromatic page for chromatic scales.
Other guides for chromatic scales:
guide_colourbar2()
,
guide_colourcube()
,
guide_colourrect()