Privacy Statement
Last revised: {{ site.privacy_statement_last_revision }}Nederlandstalige versie — Version française
Privacy Statement Summary
This privacy statement explains what information we gather about you, what we use that information for and who we give that information to. It also sets out your rights in relation to your information and who you can contact for more information or queries.
Your information will be used in accordance with the consents that you have given, with Act of 30 july 2018 on the protection of natural persons with regards to the processing of personal data and with European Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 (entered into force on 25 May 2018) on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (GDPR).This Privacy Notice is also intended to assist you in making informed decisions when using our website.
What this privacy statement covers?
This privacy statement sets out how we will collect, handle, store and protect information about you when:
- providing services to you or our clients
- you use “our Website” or
- performing any other activities that form part of the operation of our business, as described in further detail below.
When we refer to “our Website” or “this Website” in this policy we mean the specific webpages of itenium.be.
This privacy statement also contains information about when we share your personal data with other members of the itenium Network and other third parties (for example, our service providers).
In this privacy statement, your information is sometimes called “personal data” or “personal information”. We may also sometimes collectively refer to handling, collecting, protecting and storing your personal information as “processing” such personal information.
What information we collect?
In the course of providing services to you or our clients and performing due diligence checks in connection with our services (or discussing possible services we might provide), we will collect or obtain personal data about you. We may also collect personal data from you when you use our Website.
We may collect or obtain such data because you give it to us (for example in a form on our Website), because other people give that data to us (for example your employer or adviser, or third party service providers that we use to help operate our business) or because it is publicly available.
We may also collect or obtain personal data from you because we observe or infer that data about you from the way you interact with us or others. For example, to improve your experience when you use our Website and ensure that it is functioning effectively, we (or our service providers) may use cookies (small text files stored in a user’s browser) and Web beacons which may collect personal data. Additional information on how we use cookies and other tracking technologies and how you can control these can be found on our Cookiepolicy.
The personal data that we collect or obtain may include: your name; age; date of birth; gender; e-mail address; telephone number; home address; country of residence; lifestyle and social circumstances (for example, your pastimes); family circumstances (for example, your marital status and dependents); employment and education details (for example, the organization you work for, your job title and your education details); financial and tax-related information (for example your income and tax residency); your postings on any blogs, forums, wikis and any other social media applications and services that we provide; your IP address; your browser type and language; your access times; complaint details; details of how you use our products and services; details of how you like to interact with us and other similar information.
The personal data we collect may also include so called ‘sensitive’ or ‘special categories’ of personal data, such as details about your: dietary requirements (for example, where itenium would like to provide you with lunch during a meeting), health (for example, so that we can make reasonable accommodations for you in our buildings, products and services).
The types of personal data and special categories of personal data that we collect may vary depending on the nature of the services that we provide to you or our client, or how you use our Website. In some rare circumstances, we might also gather other special categories of personal data about you because you volunteer that data to us or we are required to gather that data as a result of legal requirements imposed on us.
Where we are provided with personal data about you by our client, we use reasonable efforts to include clauses into the contract with the client that will require them to comply with the privacy laws and regulations relevant to that information; this may include, for example, that the client has provided you with notice of the collection (and other matters) and has obtained any necessary consent for us to process that information as described in this privacy statement.
We understand the importance of protecting children's privacy. Our Website and services are not designed for, or intentionally targeted at, children. It is not our policy to intentionally collect or store information about children.
How we use information about you?
Use of personal information to provide services to our clients
We will use your personal data to provide you or our client with the requested services. As part of this, we may also use your personal data in the course of correspondence relating to the services. Such correspondence may be with you, our client, other members of the itenium Network, our service providers or competent authorities. We may also use your personal data to conduct due diligence checks relating to the services. Because we provide a wide range of services to our clients, the way we use personal data in relation to our services also varies. For example, we might use personal data:
- about a client to help him/her complete a tax returnabout a client’s employees to contact him during the performance of our services and keep them informed of the project’s progress or in order to communicate them our projects’ deliverables.
Use of personal information for other activities that form part of the operation of our business We may also use your personal data for the purposes of, or in connection with:
- applicable legal or regulatory requirements
- requests and communications from competent authorities
- administrative purposes
- financial accounting, invoicing and risk analysis purposes
- client relationship purposes, which may involve: (i) sending you thought leadership or details of our products and services that we think might be of interest to you; (ii) contacting you to receive feedback on services; and (iii) contacting you for other market or research purposes. In all above cases, we give you the opportunity to decline our offers and requests at any time. In specific cases if needed, for example in case you are not yet a client, we will make sure to obtain your prior consent before sending you communications’ materials or other marketing requests (see also below, “The legal grounds we use for processing personal information”);
- recruitment and business development purposes (for example testimonials from a client’s employees may be used as part of our recruitment and business development materials with that employee’s permission)
- services we receive from our professional advisors, such as lawyers, accountants and consultants
- protecting our rights and those of our clients.
- to manage and improve our Website
- to tailor the content of our Website to provide you with a more personalised experience and draw your attention to information about our products and services that may be of interest to you
- to manage and respond to any request you submit through our Website.
- education and training to relevant staff to ensure they are aware of our privacy obligations when handling personal data
- administrative and technical controls to restrict access to personal data on a ‘need to know’ basis
- technological security measures, including fire walls, encryption and anti-virus software
- physical security measures, such as staff security passes to access our premises.
- obtain confirmation that we are processing your personal data and request a copy of the personal data we hold about you
- ask that we update the personal data we hold about you, or correct such personal data that you think is incorrect or incomplete
- ask that we delete personal data that we hold about you, or restrict the way in which we use such personal data
- withdraw consent to our processing of your personal data (to the extent such processing is based on consent)
- receive a copy of the personal data concerning you, which you have provided to us, in a structured, commonly used and machine-readable format and to transmit such personal data to another party (to the extent the processing is based on consent or a contract)
- object to our processing of your personal data.
Use of personal information collected via our Website
In addition to the purposes connected to the operation of our business above, we may also use your personal data collected via our Website:
The legal grounds we use for processing personal information
We are required by law to set out in this privacy statement the legal grounds on which we rely in order to process your personal data.
As a result, we use your personal data for the purposes outlined above because : (a) of the legal and regulatory obligations that we are subject to, such as keeping records for regulatory or tax purposes or providing information to a public body or law enforcement agency or (b) the information is required in order to provide our services to you or our client. (c) of our legitimate interests in the effective delivery of our services to you or our client; (d) of our legitimate interests in the effective and lawful operation of our business so long as such interests are not outweighed by your interests;
To the extent that we process any sensitive personal data relating to you for any of the purposes outlined above, we will do so because either: (i) you have given us your explicit consent to process that data; (ii) we are required by law to process that data in order to ensure we meet our ‘know your client’ and ‘anti-money laundering’ obligations (or other legal obligations imposed on us); (iii) the processing is necessary to carry out our obligations under employment, social security or social protection law; (iv) the processing is necessary for the establishment, exercise or defence of legal claims or (v) you have made the data public.
Where we are legally required to obtain your explicit consent to provide you with certain marketing materials, we will only provide you with such marketing materials where we have obtained such consent from you.
Who we disclose your information to?
In connection with one or more of the purposes outlined in the “How we use information about you?” section above, we may disclose details about you to: third parties that provide services to us; competent authorities (including courts and authorities regulating us); your employer and/or their advisers; your advisers; organizations that help us reduce the incidence of fraud and other third parties that reasonably require access to personal data relating to you for one or more of the purposes outlined in the “How we use information about you?” section above.
Our Website hosts various blogs, forums, wikis and other social media applications or services that allow you to share content with other users (collectively “Social Media Applications”). Importantly, any personal information that you contribute to these Social Media Applications can be read, collected and used by other users of the application. We have little or no control over these other users and, therefore, we cannot guarantee that any information that you contribute to any Social Media Applications will be handled in accordance with this privacy statement.
Please note that some of the recipients of your personal data referenced above may be based in countries outside of the European Union whose laws may not provide the same level of data protection. In such cases, we will ensure that there are adequate safeguards in place to protect your personal data that comply with our legal obligations. The adequate safeguard might be a data transfer agreement with the recipient based on standard contractual clauses approved by the European Commission for transfers of personal data to third countries.
We may also need to disclose your personal data if required to do so by law, a regulator or during legal proceedings.
We may share non-personal, de-identified and aggregated information with third parties for several purposes, including data analytics, research, submissions, thought leadership and promotional purposes.
Protection of your personal information
We use a range of physical, electronic and managerial measures to ensure that we keep your personal data secure, accurate and up to date. These measures include:
Although we use appropriate security measures once we have received your personal data, the transmission of data over the internet (including by e-mail) is never completely secure. We endeavor to protect personal data, but we cannot guarantee the security of data transmitted to us or by us.
How long we keep your information for?
We will hold your personal data on our systems for the longest of the following periods: (i) as long as is necessary for the relevant activity or services; (ii) any retention period that is required by law; or (iii) the end of the period in which litigation or investigations might arise in respect of the services.
Your rights
You have various rights in relation to your personal data. In particular, you have a right to:
To exercise any of your rights, or if you have any other questions about our use of your personal data, please email {{ site.email.gdpr }} or write to us at the address below:
{{ site.address.maatschappelijk }}
You may also use these contact details if you wish to make a complaint to us relating to your privacy.
Right to complain
If you are unhappy with the way we have handled your personal data or any privacy query or request that you have raised with us, you have a right to complain to the EU Data Protection Authority (“DPA”) in your jurisdiction:
Data Protection Authority
Rue de la Presse 35
<EMAIL_ADDRESS>www.dataprotectionauthority.be
Changes to this privacy statement
We may modify or amend this privacy statement from time to time.
To let you know when we make changes to this privacy statement, we will amend the revision date at the top of this page. The new modified or amended privacy statement will apply from that revision date. Therefore, we encourage you to periodically review this statement to be informed about how we are protecting your information.


Not connected to webinos
Proximity Reminder
Check reminders
Add Reminder
Reminder Id:
Not connected to webinos


Let's first discusss what they are. IQ, as we all know, stands for Intelligence Quotient.
IQ is a score derived from a set of standardized tests, which is designed to
assess
human intelligence. EQ stands for Emotional Quotient. EQ is the ability of individuals
to understand their own emotions, as well as the emotions of those around them.
EQ is important to me because it doesn't just take smarts to get through a job, or even
life. If I understand my emotions, why I'm feeling happy, relieved, sad or overwhelmed
Then I can figure out a game plan to tackle whatever is making me feel bad, or celebrate
why I'm feeling good. It's also important because if someone around me is feeling
any
of those same emotions I can be happy for them or try help them get through whatever
it is that's making them feel bad.
This is all relevant to me, because being smart won't help me figure out the emotions of people.
If I ever come across an uncomfortable situation at EDA, for example, then
I need to make sure I
have a method of working through those emotions.


| # | File | Line | Problem |
|---|---|---|---|
| 1 | /home/codal/Laravel/postapi/app/Console/Kernel.php | 25 | Avoid unused parameters such as '$schedule'. |
| 2 | /home/codal/Laravel/postapi/app/Http/Controllers/Auth/RegisterController.php | 50 | Avoid using static access to class '\Illuminate\Support\Facades\Validator' in method 'validator'. |
| 3 | /home/codal/Laravel/postapi/app/Http/Controllers/Auth/RegisterController.php | 65 | Avoid using static access to class '\App\User' in method 'create'. |
| 4 | /home/codal/Laravel/postapi/app/Http/Controllers/PostAPIcontroller.php | 29 | Avoid using static access to class 'App\Http\Controllers\Show' in method 'show'. |
| 5 | /home/codal/Laravel/postapi/app/Http/Controllers/PostAPIcontroller.php | 31 | Avoid using static access to class '\App\Post' in method 'show'. |
| 6 | /home/codal/Laravel/postapi/app/Http/Controllers/PostAPIcontroller.php | 40 | Avoid using static access to class 'App\Http\Controllers\Update' in method 'update'. |
| 7 | /home/codal/Laravel/postapi/app/Http/Controllers/PostAPIcontroller.php | 41 | Avoid using static access to class '\App\Post' in method 'update'. |
| 8 | /home/codal/Laravel/postapi/app/Http/Controllers/PostAPIcontroller.php | 50 | Avoid unused parameters such as '$request'. |
| 9 | /home/codal/Laravel/postapi/app/Http/Controllers/PostAPIcontroller.php | 52 | Avoid using static access to class 'App\Http\Controllers\Delete' in method 'delete'. |
| 10 | /home/codal/Laravel/postapi/app/Http/Controllers/PostAPIcontroller.php | 53 | Avoid using static access to class '\App\Post' in method 'delete'. |
| 11 | /home/codal/Laravel/postapi/app/Http/Resources/api.php | 7 | The class api is not named in CamelCase. |
| 12 | /home/codal/Laravel/postapi/app/Providers/BroadcastServiceProvider.php | 17 | Avoid using static access to class '\Illuminate\Support\Facades\Broadcast' in method 'boot'. |


I am a data scientist and systems engineer based in the Pittsburgh area. I studied physics at Kenyon College, then completed my Ph.D. in physics at Carnegie Mellon University. My professional expertise extends across data science, programming, and automation engineering.
This site contains an assortment of posts related to professional projects, as well as descriptions of a few personal interests (somewhat) related to my professional pursuits. If you'd appreciate a full detailed resume in pdf form, please contact me and I'll be happy to send you one.
Thanks very much for visiting!


---
title: Miami Valley Regional
date: Wednesday, March 6, 2019
end_date: Saturday, March 9, 2019
---
Spartan Robotics will be competing in the Miami Valley Regional in 2019!
The event is free and open to the public. The event schedule is available at the link below if you plan to attend.
More information, including the event schedule, can be found at:
https://www.firstinspires.org/team-event-search/event?id=37604
The event's The Blue Alliance page, for match schedules, webcast links, etc., can be found here:
https://www.thebluealliance.com/event/2019ohmv


Back
AlphaJpg
Choose a demo
Canvas 2D
Canvas 2D (Cross Origin Image)
Canvas 2D (Background Image)
Canvas 2D (WebP, PNG & No JS Fallbacks)
WebGL
WebGL (Cross Origin Image)
WebGL (Background Image)
SVG
SVG (Cross Origin Image)
SVG Filter (No JS Required)
SVG Mask (No JS Required)


#include <stdbool.h>
#include <stdlib.h>
Go to the source code of this file.
Returns the capacity of the array identified by the specified handle.
- Parameters
-
| [in] | handle | - The handle of the dynamic array |
- Returns
- The capacity of the allocated backing array
Returns the logical size of the dynamic array identified by the specified handle.
- Parameters
-
| [in] | handle | - The handle of the dynamic array |
- Returns
- The capacity of the allocated backing array
Delete the element specified by the handle and index.
- Parameters
-
| [in] | handle | - The handle of the dynamic array to be freed |
| [in] | index | - The position of the data element to be removed |
Frees the dynamic array identified by the specified handle.
- Parameters
-
| handle | - The handle of the dynamic array to be freed |
Gets the element at the specified index.
This function returns the element at the specified index from the dynamic array identified by the specified handle.
- Parameters
-
| [in] | handle | - The handle of the dynamic array |
| [in] | index | - position of the array element to be returned |
| [in,out] | p_data | - pointer to data element containing data to be returned |
Initialize the dynamic array with the number of elements and size per element.
- Parameters
-
| num_elements | - The number of elements to store in the array. |
| element_size | - The size of each element in the array. |
| bool insert_element |
( |
DYNARRAY_HANDLE |
handle, |
|
|
size_t |
index, |
|
|
void * |
p_data |
|
) |
| |
Insert an element into the array specified by the handle and index.
If the backing array has reached its capacity, the array will be resized by twice the current capacity.
- Parameters
-
| [in] | handle | - The handle of the dynamic array to be freed |
| [in] | index | - The position to store the data element. |
| [in] | p_data | - The data to be stored. |
Stores the specified data element at the location indicated by the index.
The index needs to be within the capacity. Any previously stored data at the location is replaced by the new content.
- Parameters
-
| [in] | handle | - The handle of the dynamic array |
| [in] | index | - The position to store the data element. |
| [in] | p_data | - The data to be stored. |


What is Docker?
Docker is an open source project that allows users to store items in containers. It allows users to isolate their apps from the environment
they are working on.
Key benefits:
Open Source software
Isolate from the environment so that no bugs occur due to local system error
Huge community of users
Docker Vs Virtilization:
Docker is basically using the OS-level virtualization, Linux namespaces and control groups, for example. Its overhead is very thin compared to a virtualization technique, like Hypervisor used by virtual machines.
VMs & Docker – each comes with benefits and demerits. Under a VM environment, each workload needs a complete OS. But with a container environment, multiple workloads can run with 1 OS. The bigger the OS footprint, the more environment benefits from containers. With this, it brings further benefits like Reduced IT management resources, reduced size of snapshots, quicker spinning up apps, reduced & simplified security updates, less code to transfer, migrate and upload workloads.
How to download Docker:
Install VirtualBox. The only component we have to install. Download the installer from the download page and run it. After the installation, reboot the computer.
Download docker-machine. We need docker-machine for creating Docker hosts in VirtualBox. Check the release page and download the latest release
Install tinycorelinux as Docker host in VirtualBox. Change the memory settings if you want to give Docker more or less memory.
Download docker-client.
Create a batch file start_docker.bat in the c:\docker folder and insert the following commands.
Add c:\docker to the system path.
Lastly, we set up shared folders. You can configure a shared folder via Command Prompt with the vboxmanage tool. In this example, I map the Windows folder c:\docker\data to the Docker host. Ensure that the folder exists before you run the command.
For more information, check https://golb.hplar.ch/2019/01/docker-on-windows10-home-scratch.html
For more information, check https://www.edureka.co/blog/docker-explained/"


Vacation Generator
What is your favorite cuisine?
What is your ideal weather forecast?
Favorite pastime?
Nature or nightlife?
Home body or adventure seeker?
Enter


Contains code
This package is made up of the following modules:
- DroneApp: Defines the configuration of drones in the swarm used for task completion.
- AppController: Creates objects from the below modules from the specification in the DroneApp module.
- DroneControl: Sends commands and listens to packets from a drone via the controlloop module.
- DroneStates: Defines the state of an individual drone based on status messages.
- SwarmControl: Manages multiple drone controllers to complete a task using logic.
- SwarmStates: Defines the state of a group (or swarm) of drones in relation to a set task based on status messages.
- StatusUpdater: Handles raw sensor readings pushed up from the drone and parses them into formats which are useful for different parts of the program. Statuses are then pushed out to DroneControl and SwarmControl objects.
- ImageProcessor: Processes video frames direct from the drone, pushes output to DroneControl and provides a video feed in an external window. Utilises the aruco library to process reference markers.
- Navigator: Handles all logic relating to routing over a known mapped area.
- Controllers: Manages access to a range of controllers which use the DroneControl module to push control inputs to the drone.
Initially sets up system in configuration provided. Routes communication of status messages to status updater.
The base class for overseeing actions of an individual drone.
Acts upon messages from SwarmControl class by changing position (using Controller class) or carrying out standard land, take off, change camera actions (using ControlLoop class).
A class which manages the sending and receiving of packets over the network. It stores the relevant data of received packets and sends packets when requested.
IP address of drone: config.[‘host’] Localhost: <IP_ADDRESS>
ID = 2
The state for when the drones are initially airborne. State entry requirements: drones are airborne. State purpose: to get drones hovering stably at height. State exit: when drones are stable and ready to manoeuvre
ID = 0
The state for when the drones are not verified as being in contact with the network. State entry requirements: - State purpose: to get drones communicating State exit: when drones are on and communicating
ID = 3
The state for when the drones are stable in height. State entry requirements: drones are stable at altitude. State purpose: to get drones hovering stably over target marker, transitioning through marker transition vector to achieve this. State exit: when marker is stable over target marker.
ID = 1
The state for when the drones are not airborne. State entry requirements: drones are on and able to communicate with the controller. State purpose: to get drones airborne State exit: when drones are airborne
A class which determines states of a drone. This is the base class from which all states inherit. As status messages are received, the state machine determines the next state and changes it accordingly.
Upon creation of a new state, the state is initialised and then runs action() which carries out further initialisation.
The base class for overseeing cooperative control of multiple drones.
Uses navigation logic (from Navigator class) and task logic (from Swarm States) to decide on actions. Actions are sent to each drone’s Individual Controller.
ID = 0
The SetupState is for when the drones are not verified as being ready for operations. State entry requirements: none State purpose: to WAIT until drones are hovering stably
State transition conditions:
State 0: -
State 1: height_stable == True for all drones
State 2: -
A class which manages the state of the SwarmController object. This is the base class from which all states inherit. As status messages are received, the state machine determines the next state and changes it accordingly.
ID = 1
The GroundState state for when task is not being achieved. State entry requirements: assets are ready. State purpose: to achieved the task.
TASK - to move continuously around a loop without collision
State transition conditions:
State 0: -
State 1: -
State 2: airprox == False && following_marker == True
ID = 2
The CooperativeController state for when the task is being achieved. State entry requirements: task is being achieved. State purpose: watch over situation to detect danger to both task and assets.
TASK - to move continuously around a loop without collision
State transition conditions:
State 0: -
State 1: airprox == True || following_marker == False
State 2: -
Updates statuses through code, parsing into the required format at each stage.
Expand documentation here - e.g. contents of statuses
A class which works out safe routes for drones to follow. All functions are called with a list of the drones current positions (and possibly other parameters too) All ‘public’ functions return one list of n lists, where n is the number of drones being controlled
A basic deconfliction algorithm which changes the routes of all drones that have unsafe routes Only guarantees deconfliction on maps with no junctions
Checks the routes of each drone with the current position of the other drones. A list containing bools is returned. If a drone’s route risks collision with another then False is returned for that drone.
Returns drone_id of the drone in front of loop. ‘Front’ drone is determined by whichever drone has the most number of clear spaces in front of them.
Returns a route which is the current positions passed
Returns markers next to current marker in order [forward,backward]
A basic algorithm for setting a looping route around a continuous path. Route is never longer than 6 markers ahead.
Class forming the base functionality of a controller
Class to manage all the controllers for one drone. Regulates the packets being sent to the drone so only one command is sent every heartbeat (otherwise we may overload the system).
Implementation of a lead-lag controller which takes a position and returns a correcting velocity Controller also pre-compensates by a value of K
ANALOGUE CONTROLLER: G(s) = (as + 1) / (bs + 1)
Implementation of a lead-lag controller using Tustin Transformation. Takes a position and returns a correcting velocity Controller also pre-compensates by a value of K
ANALOGUE CONTROLLER: G(s) = (as + 1) / (bs + 1)


Make your building Energy Efficient!
Our site will help your buidling to save energy, money and the environment!
Some of the benefits of using our site:
Up to $300,000 annual energy savings
Tennant satisfaction raised from 50% to 95%
Learn More
OR
Complete our Survey!

What is the amount of your latest gas bill?
What is the amount of your latest electricity bill?
What is your building's square footage?
What is your heating type?
Gas
Electric
Email:
Postal Code:
Submit


I am taking this Fullstack course and I am going to do exceptionally well and pass this course with flying color with Creation assistance.


`f040478` feat: add order ids - DCPRevere
`96f815a` feat: add order id hash function - DCPRevere
`706cbe9` feat: add pair helper function - DCPRevere
`dbde137` feat: create the order class - DCPRevere
`a69dbe2` feat: create order builder class - DCPRevere
Example:
!IMG_1568
The positioning of the cursor and the part of the number visible on screen currently make it easy to edit the number but there is no way to see the whole number.
Request: Display the whole number being edited in the field in a smaller font just below it. Update the additional display dynamically as the contents of the field are changed


Home
Archives
Categories
Tags
About
Tags
blogging
2018-12-14
I have a bad day with Amazon US
steempress
2018-10-08
One text editor to rule them all -- Atom
atom
2018-09-24
Make any Screenshot instantly attractive by using this trick
steempres
2018-07-07
Talk to the world, but not Steem only.
steempress
2018-01-05
Ten hours on a train 高铁十小时
travel
2017-12-31
2017 summary 一年总结
cn
2017-11-08
Advertise Steemit to my favorite blogger 继续介绍 Steemit 给喜欢的博主
steemit
2017-10-31
Powerful tool to reduce grammar mistakes 推介一款强大的英文寫作技巧强化利器
cn
2017-10-25
勿忘初心才可以走得更远 Stay true to what you have started
cn
Your browser is out-of-date!
Update your browser to view this website correctly.
Update my browser now
×


Convert PDF/Images to Text
Drag & drop files here
Open the file Browser
Select Language
File List
- No files uploaded.
Status Messages
- Ready plugin....


bb@
{{ user }}
A bio or something might go here.
{% for net in nets %}
{{ net.net }}@
{{ net.url }}
{% endfor %}


I’m a student at the University of California, Davis majoring in Mechanical Engineering with an emphasis on Mechatronics. I have held various positions during my college years in the field of semiconductors, educational services, and finance. My goal is to connect user needs and business objectives through meaningful design. I utilize my time after classes to gain technical experience through personal projects and self-education. In my free time, I enjoy photographing, driving, playing tennis, and traveling.
As a process engineer intern, I assited the R&D team in developing new SOI wafer polishing processes that decrease the TTV (Total Thickness Variations) to 1+/-0.2 (μm). Our team successfully implemented new quality improvement processes and procedures that increase yield and capacity while reducing cost and downtime.
College students spend hours after class trying to understand math. My job was to help those students reinforce and make sense of what they learned in class. I break down complex math concepts into easily understood steps that help the student solve the problems.
As an office assistant, my duty was to record financial transactions of businesses for bookkeeping functions. I also worked with clients to prepare payroll information by collecting, calculating, and entering data on monthly and quarterly basis.
This scholarship was established by the Regents of the University of California in 1962 and represents the highest honor awarded to a student at the UCs. Recipients are selected on the basis of demonstrated academic excellence, leadership, and exceptional promise.
The Chevron Scholarship is a corporate sponsored scholarship awarded to students who possess a demonstrated potential for leadership to positively impact the barriers that prevent full participation of women and underrepresented minorities in Engineering and Computer Science.
Students qualified for this list in recognition of their dedication to academic pursuits, resulting in a GPA placing them among the top 16% in their class level in the College of Engineering. I have been on the Dean’s List for the quarter of Fall 2018 (3.95/4.00), Winter 2019 (4.00/4.00), Fall 2019 (3.85/4.00).


Ljubljana Marathon
Ljubljana SLO
Website: www.ljubljanskimaraton.si/en/maraton
Race Winners
(21 runnings)
28 Oct
2007
29 Oct
2006
23 Oct
2005
24 Oct
2004
26 Oct
2003
27 Oct
2002
28 Oct
2001
22 Oct
2000
24 Oct
1999
25 Oct
1998
26 Oct
1997
27 Oct
1996
Notes: 1996 was the inaugural year.
29 Oct
2017
2:08:33
Marius Kimutai (KEN)
(nc)
2:27:02
Shuko Genemo Wote (ETH)
(nc)
30 Oct
2016
2:09:16
Laban Wanjiku Mutai
(KEN)
2:29:32
Purity Chebichi Changwony (KEN)
25 Oct
2015
2:08:19
Limenih Getachu Yizengaw
(ETH)
(nc)
2:25:42
Gizaw Melkam Tola (ETH)
(nc)
26 Oct
2014
2:08:25
Ishmael Busendich
Chemtan (KEN)
2:29:16
Janet Rono Chelegat (KEN)
27
Oct
2013
2:10:26
Mulugeta Wami Degife
(ETH) (nc)
2:27:27
Caroline Chepkwony (KEN) (nc)
28
Oct
2012
2:09:40
Berhanu Shiferaw Tolcha
(ETH)
2:30:45
Worknesh Tola Biru (ETH)
23 Oct
2011
2:08:25
Daniel Kiprugut Too (KEN)
(nc)
2:33:01
Lydia Kurgat Chepkorir (KEN)
(nc)
24 Oct
2010
2:10:17
Evans Kipkosgei Rutto (KEN)
2:37:16
Tiruwok Mekonnen Lemma (ETH)
25 Oct
2009
2:10:12
William Biama (KEN)
(nc)
2:25:24
Caroline Cheptonui Kilel (KEN)
(nc)
26 Oct
2008
2:14:41
Abraham Mulu Amara (ETH)
2:37:13
Tatyana Mezentseva (UKR)
2:12:49
Aleksandr Sitkovskiy (UKR)
(nc)
2:34:58
Tatyana Filoniuk (UKR)
(nc)
2:14:14
Joachim Nshimirimana-2
3:01:55
Inga Juodeskiene (LTU)
2:15:47
Samuel Nganga Njoroge (KEN)
(nc)
2:50:42
Daneja Grandovec (SLO)
(nc)
2:13:31
Joachim Nshimirimana (BDI)
2:46:30
Elena Razdrogina (RUS)
2:13:58
Andriy Naumov-2 (nc)
2:38:13
Galina Zhulyeva-2 (nc)
2:14:30
Andriy Naumov (UKR)
2:39:36
Galina Zhulyeva (UKR)
2:22:57
Roman Kejzar-2 (nc)
3:09:47
Nada Rotovnik (SLO)
(nc)
2:13:35
Patrick Chumba Kimeli (KEN)
3:08:38
Maria-Luisa Costetti (ITA)
2:20:53
Wollya Jarra (ETH)
(nc)
2:52:26
Lyudmila Petrova (RUS)
(nc)
2:18:20
Piotr Poblocki (POL)
2:32:33
Helena Javornik-3
2:19:28
Charles Subano (KEN)
2:40:05
Helena Javornik-2
2:20:12
Roman Kejzar (SLO)
2:37:58
Helena Javornik (SLO)
(nc) => national champion
2017 Mitja Krevs was the SLO champion (11th
place, 2:32:25)
2017 Jasmina Pitamic ( was the SLO champion (7th place, 2:53:05)
2015 Mitja Kosovelj was the SLO champion (10th place, 2:20:53)
2015 Neza Mravlje was the SLO champion (5th place, 2:49:33)
2013 Anton Kosmac was the SLO champion (9th place, 2:24:57)
2013
Zana Jereb was the SLO champion (7th place, 2:42:09)
2011 Mario Vracic was the SLO champion (place unknown, 2:31:48)
2011 Neza
Mravlje was the SLO champion (5th place, 2:42:00)
2009 Roman Kejzar was the SLO champion (11th place, 2:19:24)
2009 Daneja Grandovec was the SLO champion (11th place, 2:52:14)
2007 Bostjan Hrovat was the SLO champion (9th place, 2:33:12)
2007 Helena Javornik was the SLO champion (2nd place, 2:35:45)
2005 Roman Kejzar was the SLO champion (6th place, 2:22:08)
2003 Zdravko Volkar was the SLO champion (8th place, 2:29:20)
2003 Ida Surbek was the SLO champion (4th place, 2:49:57)
1999 Benno Piskur was the SLO champion (9th place, 2:35:45)
1999 Mateja Sustarsic was the SLO champion (place unknown, 3:12:27)
Most Wins
(1996-date)
Men
2
Roman Kejzar (SLO)
1996,2001
Andriy Naumov (UKR)
2002-03
Joachim Nshimirimana (BDI)
2004,2006
Women
3
Helena Javornik (SLO)
1996-98
Prize Money
(ADR qualified runners)
Year Men Women Total 2017 $61,100 $61,100 $122,260 2016 61,545 40,115 101,660 2015 64,455 51,785 116,240 2014 63,350 24,705 88,055 2013 16,565 20,705 37,270 2012 47,220 16,170 63,390 2011 68,785 14,940 83,725 2010 43,615 7,745 51,360 2009 58,500 40,500 99,000 2008 22,755 14,890 37,645 .... 2006 4,460 n/a 4,460 2005 3,585 1,790 5,375 2004 11,895 4,595 16,490 Sums $544,820 $302,950 $847,700
Race Time Bias (sec/km) Year Men Women 2012 +0.3 n/c .... 2009 -1.2 n/c .... 2007 +0.4 n/c 2006 +0.1 n/c 2005 +0.2 n/c .... 1998 +4.7 n/c Avgs +0.7 n/c
Competitive Level (1990-date) Year Men Women 2017<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER> 456 n/c 2009<PHONE_NUMBER><PHONE_NUMBER> 239 82 2006 196 n/c 2005 310 n/c 2004 102 n/c .... 1998 73 n/c
Quality Performances
Men <2:09 8 <2:10 19 <2:11 37 <2:12 47 <2:13 58 <2:14 68 <2:15 79 <2:16 90 <2:17 95 <2:18 105 <2:19 116 <2:20 130 Women <2:26 2 <2:28 6 <2:30 10 <2:32 20 <2:34 27 <2:36 37 <2:38 45 <2:40 54 <2:42 59 <2:44 64 <2:46 67 <2:48 73 <2:50 82
Last Updated on 05 Nov 2017
Contributors: Franco Civai (5), Juraj Gasparovic (6), Klaas Loonstra (15), Barbara Železnik, Gabrijel Ambrožič, Borut Podgornik (6)


Mike Wallis
is a sysadmin at the University of Leeds with 16 years of
experience in the HPC field, with many years of working in
biosciences alongside that. He is one of a small team who keep the
tier 2 N8 HPC facilities running, alongside
several t3 machines used for advanced research computing in
multiple academic disciplines. He has far too many different
hobbies.


Change Password
OnlyPass
Sign Out
One password, unlimited possibilities
Welcome to OnlyPass! Please sign in or create an account.
Create an account
Sign in
Email address:
Password:
Confirm password:
I have read the
Terms and Conditions
and agree to them.
Passwords don't match
Password is too short
Password must include a number
Password must include a letter
You must accept the Terms and Conditions
Cancel
Create an account
Email address:
Password:
Incorrect username or password
Cancel
Sign in
Name
Website
Date last changed
Password
Show
Copy
Generate random
Edit
Delete
Are you sure you wish to delete your login details for this website? Once deleted, login details cannot be recovered.
Cancel
Delete
Current password:
New password:
Confirm new password:
Old password is incorrect
New passwords don't match
Password is too short
Password must include a number
Password must include a letter
Cancel
Change


Please refer to How to Run for basic usage
Explain how to download simulation logs
in the browser
http://localhost:3080/run
accessed
(the following images can be magnified)
Press the link for download download
Simulation log data can be downloaded


Reviewboard Integration Release Notes
Version __VERSION__NUMBER__
v5.0.2
- When adding the Bug ID to the review, the Jira server is pre-appended to provide easier access to the bug (Reviewboard is unable to link it though)
v5.0.1
- [Bug Fix]: Atlassian SDK library wasn't always present on an installed machine
v5.0.0
- [Major]: Reviews must now have a valid Jira reference before they are raised otherwise the review will not be started
- [Major]: When generating statistics from reviews it will now show how many commits have no Jira references and if there are any Jira's that have been logged against excessively
- A report name must now be specified when creating a stats report rather than it automatically using the repository name
v4.0.1
- [Bug Fix]: Review groups were not being saved correctly due to the settings files being reset
v4.0.0
- [Major]: Added an option to simply generate a commit from the ReviewBoard option which will skip the entire ReviewBoard step when ran
v3.2.1
- If the user is unable to connect to the Reviewboard server due to an auth error, they are now prompted to reauthenticate
- [Bug Fix]: The Jira link in the SVN comment was malformed but the format is now correct
v3.2.0
- Modified the build process and version tools to pull information from the repository to generate automatic builds
v3.1.0
- [Major]: Settings is now available in the context menu allowing per server authentication options and the ability to enable debug logging
v3.0.4
- [Bug Fix]: Authentication exceptions are now handled correctly when polling multiple API requests
v3.0.3
- Switched over to using the pre-2.0 Reviewboard API to find the number of ship it's on a review
- Stop on Copy/Rename is now enabled by default when the Tortoise SVN log is displayed
v3.0.2
- Limited the number of concurrent calls to the Reviewboard and SVN servers to reduce load
v3.0.1
- Added checks around the Tortoise SVN hooks incase it is not installed
- Removed the /merge option when opening Tortoise SVN logs
- [Bug Fix]: Fixed issue where the number of reviews collected didn't match the expected review list
v3.0.0
- [Major]: You can now generate statistics against a repository which reports the breakdown of reviews and review metrics
- [Major]: Authentication against servers is now done in a separate application and can be individually managed
v2.3.1
- [Bug Fix]: Patch file was not being cleaned up after every run
v2.3.0
- [Major]: Option now available to view both the review patch file and the files that make up the review
- [Bug Fix]: About and Open Browser now run through RBProc rather than as individual processes
v2.2.0
- When the 'Keep Review Artifacts' option is checked the review files are kept in My Documents/Reviewboard Integration Tools/Reviews
- [Bug Fix]: Notification dialog now resizes correctly when error messages are displayed
v2.1.0
- About dialog now present in the right content menu
- [Bug Fix]: Version number included in the commit message now uses the product version rather than the dialog version
v2.0.0
- [Major]: Create Review now generates a single review when multiple files are selected
- Various checks added when files are selected for review that they are in the same working copy, are source controlled etc.
v1.1.0
- [Major]: Create Review option is now available when you right click .diff or .patch files
- When a review is successfully created the Create Review tools will now automatically close
- Jira link now uses a lowercase b so it doesn't confuse the Jira server
- Added additional checks to the installer so we don't prompt to install software already installed
- Reviewboard server automatically opens when the installer is complete if it's the first time it's run
- Automatically display release notes when the installer completes if we've run the installer before
v1.0.0
- [Major]: Initial release
- [Major]: Create Review option available via right-click on SVN folder


Virtual Etch A Sketch
Please enable javascript
customize grid
Select Grid Size:
16x16
32x32
48x48
64x64
Hide Grid:
Pick Color:
or
Go Random:
Reset Grid
created by kumar vaibhav


DOA Festival 2016 will take place on 24 and 25 September on the familiar Festivalterrein the Cold Kitchen in Bruges. The festival will take place this year for the 1st time . DOA Festival is made possible thanks to the willing cooperation of the city of Bruges and its inhabitants. The information provides an additional service to visitors of DOA Festival. During the festival you will be held here at the height of the program, weather forecasts , information on where everything is located , information about the services and information about public transport. If you have lost something if you've found something that someone else lost , then bring it to the information desk. Visitors can during opening hours, with questions at the information desk , problems, complaints and compliments and one can come up tips and suggestions.
There is one ocial festival campground with sucient capacity to oer a place to all cardholders weekend. The festival campsites are open from Friday, September 23 (20:00) untill Monday, September26th (12:00). It is not possible to reserve a spot in advance. Illegal camping is strictly prohibited. Camping on the festival camping is only available for visitors with a weekend ticket. Visitors with a day ticket can not use the festival campsite (a 2 day ticket give access!). For weekend tickets see ticket sales. All campsites have showers and toilets. There are no foodtrucks on the campsite.


Before Change
// Need to compute output shape dynamically.
dynamic_input_shape = tf.shape(tensor)
dynamic_shape = tf.concat(
[dynamic_input_shape[:start],
[-1],
dynamic_input_shape[start + self._size:]],
axis=0)
tensor = tf.reshape(tensor, dynamic_shape)
After Change
// Need to compute output shape dynamically.
dynamic_input_shape = tf.shape(tensor)
dynamic_initial = dynamic_input_shape[:start]
dynamic_middle = tf.reduce_prod(
dynamic_input_shape[start:start + self._size], keep_dims=True)
dynamic_final = dynamic_input_shape[start + self._size:]
dynamic_shape = tf.concat(
[dynamic_initial, dynamic_middle, dynamic_final], axis=0)
tensor = tf.reshape(tensor, dynamic_shape)
tensor.set_shape(static_shape) // give it some static shape information


DailyCode 44
Today is my last day of typographic focus for this month. It's been a week already...I'm 5 weeks into 2017. My output throughout this week has been simple: not too bad but not extraordinary either. However, I have developed some great insights into engineering mobile UIs in general and mobile typography specifically. The key takeaways from this week are: "snapshot" layouts in sections, type as functional blocks (i.e. paragraph, heading, aside) vs type as letterforms, the reality context of type, and the constraints of type due to limited available space within the screen. There is still much to learn regarding typography. I'm great at understanding and using properties, whether they're CSS properties or typographic properties. I can improve my layout skills and delve deeper into typography in general.
Tomorrow I start working with 2D CSS graphics for a week. SVG for sure.


|
|
RESPONSE_400 = ' Input Payload Validation Failed '
|
|
|
RESPONSE_404 = ' Blackboard Not Found '
|
|
|
RESPONSE_500 = ' Internal Server Error '
|
|
|
GET_RESPONSE_200 = ' Blackboard Read '
|
|
|
GET_RESPONSE_409 = ' Blackboard Empty '
|
|
|
PUT_RESPONSE_201 = ' Blackboard Created '
|
|
|
PUT_RESPONSE_409 = ' Blackboard Already Exists '
|
|
|
POST_RESPONSE_201 = ' Blackboard Updated '
|
|
|
PATCH_RESPONSE_200 = ' Blackboard Cleared '
|
|
|
DELETE_RESPONSE_200 = ' Blackboard Deleted '
|
|
|
DELETE_ALL_RESPONSE_200 = ' All Blackboards Deleted '
|
|
|
__package__ = None
|


The Todo list expanded
Create aTodoList
object with
- A
tasks
array property - A method
printTasks
that will, like the previous excercise, loop over theTodoList
's tasks and print similarly. - An
addTask
method that will add a given task to the list of tasks. - Use the object to add a task to the TodoList and then print the tasks
- Bonus: add a
completeTask
method that will take antask_index
as a parameter and will set the appropriate task to be done


{% extends "GeneralApp/base.html" %} {% block title %}GeneralApp | Sign Up{% endblock %} {% load static %} {% block navbar %}
Username
Password
Confirm password
Email
{{ context }}
By clicking on 'Sign Up', you agree to our Terms and Conditions


Examples to demonstrate the packaged transitions.
Useful for: Theming, Presentation, Changing Behavior
This example has only images wrapped in a <ul> with <li>'s
<ul>
<li>


randFromArray([ "SSS", "SAS", "SAA", "ASA", "SSA", "SSA", "AAA" ])
{
"SSS": "Side-Side-Side",
"SAS": "Side-Angle-Side",
"SAA": "Side-Angle-Angle",
"ASA": "Angle-Side-Angle",
"SSA": "Side-Side-Angle",
"AAA": "Angle-Angle-Angle"
}[ TYPE ]
randomTriangleAngles.triangle()
5 + random() * 2
randRange( 0, 1 ) === 1 ? true : false
{ "SSS": "Yes", "SAS": "Yes", "SAA": "Yes", "ASA": "Yes", "SSA": "No", "AAA": "No" }[ TYPE ]
new Triangle( [ 0, 0 ], ANGLES, SCALE, {} )
Is NAME a triangle congruency postulate?
Answer the question by clicking and dragging the points below to see what triangles you can construct.
If you believe NAME is not a triangle congruency postulate, prove it by constructing incongruent triangles. Otherwise, construct congruent triangles.
Your triangle can be anywhere. There is no need to line up the two triangles.
init({
range: [ [ -7, 7 ], [ -7, 7 ] ]
});
addMouseLayer();
initCongruence({ triangle: TRIANGLE, type: TYPE, reflected: REFLECTED });
TRIANGLE.rotate( randRange( 0, 360 ) );
style({ stroke: "#b1c9f5", "stroke-width": 5 });
TRIANGLE.translate([
-5 - Math.min(TRIANGLE.points[0][0], TRIANGLE.points[1][0], TRIANGLE.points[2][0]),
6 - Math.max(TRIANGLE.points[0][1], TRIANGLE.points[1][1], TRIANGLE.points[2][1])
]);
path( [ lineMidpoint( TRIANGLE.sides[ 2 ] ), TRIANGLE.points[2], TRIANGLE.points[1], TRIANGLE.points[0], lineMidpoint( TRIANGLE.sides[ 2 ] ) ] );
addTriangleDecorations( TRIANGLE, TYPE );


--- title: "Hamilton County schools' per-student salaries" date: 2016-03-23 16:00:00 -0400 layout: post related: embed_source: "/charts/hcde-salaries-2008-2016/" description: Changes in average per-student expenditure between 2008 and 2016. ---


NumCosmo Reference Manual |
|---|
for NumCosmo 0.18.1. The latest version of this documentation can be found on-line at https://numcosmo.github.io/manual/, NumCosmo website.
- NumCosmo Overview
- Introduction — A general description of the library functionality
- Bibliography — The set of books and papers used in the library
- NumCosmo building configuration — Macros describing the current building configuration
- Numcosmo Math
- Miscellaneous Objects
- NcmC — Numerical and physical constants.
- NcmCfg — Library configuration and helper functions.
- NcmUtil — Miscellaneous utilities.
- NcmISet — Index set object
- NcmDiff — Numerical differentiation object
- NcmVector — Vector object representing arrays of doubles.
- NcmMatrix — Matrix object representing an array of doubles.
- NcmNNLS — Non-negative linear least-squares
- NcmSerialize — Serialization, deserialization and duplication object.
- NcmObjArray — GObjects array with serialization support.
- NcmIntegral1d — One dimensional integration object.
- NcmIntegral1dPtr — Function pointer one dimensional integration object.
- NcmIntegralND — N-dimensional integration object.
- NcmLapack — Encapsulated LAPACK functions.
- NcmFuncEval — A general purpose multi-threaded function evaluator.
- NcmTimer — A timer with ETA support.
- NcmRNG — Encapsulated GNU Scientific Library (GSL) random number generator with support for multhreading.
- NcmQuaternion — Quaternions algebra, three-vectors and mapping to matrix.
- MPI Objects
- NcmMPIJob — Abstract class to implement MPI jobs
- NcmMPIJobTest — Test implementation of MPI job class
- NcmMPIJobFit — MPI job object for running NcmFit
- NcmMPIJobMCMC — MPI job object for running MCMC steps
- NcmMPIJobFEval — MPI job object for evaluating fit steps
- ODE Solvers objects
- NcmODE — Abstract class for ODE solvers
- NcmODEEval — Abstract class for ODE system evaluation
- FFTLog
- NcmFftlog — Abstract class for implementing logarithm fast fourier transform.
- NcmFftlogSBesselJ — Logarithm fast fourier transform for a kernel given by the spatial correlation function multipoles.
- NcmFftlogSBesselJLJM — Logarithm fast fourier transform for the base kernel for angular projections.
- NcmFftlogTophatwin2 — Logarithm fast fourier transform for a kernel given by the square of the spherical Bessel function of order one.
- NcmFftlogGausswin2 — Logarithm fast fourier transform for a kernel given by the square of a Gaussian window function.
- Splines 1D
- NcmSpline — Abstract class for implementing splines.
- NcmSplineGsl — GSL spline object wrapper.
- NcmSplineCubic — Abstract class for implementing cubic splines.
- NcmSplineCubicNotaknot — Cubic spline implementation with 'not a knot' boundary conditions.
- NcmSplineCubicD2 — Cubic spline implementation given second derivatives.
- NcmSplineRBF — Radial Basis Function implementation of spline class.
- NcmSplineFunc — Automatic generation of the knots for a spline.
- NcmSplineFuncTest — test suite to analyze the NcmSplineFunc's knots distribution.
- NcmOdeSpline — Automatic generation of splines from ODE solvers (NcmODE).
- Splines 2D
- NcmSpline2d — Abstract class for implementing bidimensional splines.
- NcmSpline2dSpline — Implements bidimensional splines from splines method.
- NcmSpline2dBicubic — Bidimensional bicubic spline
- NcmSpline2dGsl — Implements spline from spline method using The GNU Scientific Library (GSL) as base splines.
- Power spectrum functions
- NcmPowspec — Abstrac class for power spectrum implementation.
- NcmPowspecFilter — Class to compute filtered power spectrum
- NcmPowspecSphereProj — Class to compute spherical projection of power spectra
- NcmPowspecCorr3d — Class to compute filtered power spectrum
- Harmonic Oscillator
- Special Functions
- NcmMpsfTrigInt — Multiple precision sin integral implementation.
- NcmMpsf0F1 — Multiple precision implementation of the hypergeometric 0F1.
- NcmMpsfSBessel — Multiple precision spherical bessel implementation.
- NcmSFSBessel — Double precision spherical bessel implementation.
- NcmSFSphericalHarmonics — Spherical Harmonics object
- Models and Parameters
- NcmModel — Abstract class for implementing models.
- NcmSParam — Properties of a scalar parameter.
- NcmVParam — Properties of a vector-like parameter.
- NcmModelCtrl — Control object for testing updates on model status.
- NcmModelBuilder — A NcmModel builder
- NcmMSet — A set of different NcmModel objects.
- NcmMSetFunc — Abstract class for arbitrary MSet functions.
- NcmMSetFunc — Abstract class for arbitrary MSet functions - bindable version
- NcmMSetFuncList — NcmMSet Functions list.
- NcmData — Abstract class for implementing calculator objects.
- Reparametrization
- NcmReparam — Abstract class for model reparametrization.
- NcmReparamLinear — Linear reparametrization object.
- Data Objects
- NcmData — Abstract class for implementing data objects.
- NcmDataset — A set of NcmData objects
- NcmDataGauss — Gaussian data -- inverse covariance provided.
- NcmDataGaussDiag — Gaussian data -- diagonal covariance provided.
- NcmDataGaussCov — Gaussian data -- covariance provided.
- NcmDataPoisson — Abstract class for implementing poisson distributed data.
- NcmDataDist1d — Abstract class for one variable distribution data.
- NcmDataDist2d — Abstract class for two-variables distribution data.
- Statistical Analysis
- NcmStatsVec — An online statistics vector.
- NcmStatsDist1d — Abstract class for implementing one dimensional probability distributions
- NcmStatsDist1dSpline — One dimensional probability distribution based on a spline
- NcmStatsDist1dEPDF — One dimensional probability distribution based on an EPDF
- NcmStatsDist2d — Abstract class for implementing two-dimensional probability distributions
- NcmStatsDist2dSpline — Two-dimensional probability distribution based on a spline
- NcmBootstrap — Generic index bootstrap.
- NcmLikelihood — Likelihood combining a NcmDataset and priors.
- NcmPrior — A prior for NcmLikelihood.
- NcmPriorGauss — A gaussian prior for NcmLikelihood
- NcmPriorGaussParam — a gaussian prior on a parameter
- NcmPriorGaussFunc — a gaussian prior on a parameter
- NcmPriorFlat — A flat prior for NcmLikelihood
- NcmPriorFlatParam — a flat prior on a parameter
- NcmPriorFlatFunc — a flat prior on a parameter
- NcmMSetCatalog — Ordered catalog of different NcmMSet parameter values.
- NcmMSetTransKern — Abstract Class for a transition kernel and prior.
- NcmMSetTransKernFlat — Multivariate flat sampler.
- NcmMSetTransKernGauss — A multivariate gaussian sampler.
- NcmMSetTransKernCat — Catalog sampler.
- NcmFitState — State of a NcmFit object.
- NcmFit — Abstract class for implementing fitting methods.
- NLopt Interface Object — Interface for NLopt optmization library
- NcmFitNLOptEnum — Automaticaly imported enum from NLOpt library.
- NcmFitGSLLS — Best-fit finder -- GSL least squares algorithms.
- NcmFitGSLMM — Best-fit finder -- GSL non-linear minimization algorithms.
- NcmFitGSLMMS — Best-fit finder -- GSL non-linear minimization (simplex) algorithms.
- NcmFitLevmar — Best-fit finder -- Levenberg-Marquardt nonlinear least squares algorithm library.
- NcmFitMC — Monte Carlo analysis.
- NcmFitMCBS — Monte Carlo and bootstrap analysis.
- NcmLHRatio1d — Likelihood ratio for one dimensional parameter analysis.
- NcmLHRatio2d — Likelihood ratio object for bidimensional parameter analysis.
- NcmABC — Abstract class for Approximate Bayesian Computation (ABC).
- Multivariate density estimation
- NcmStatsDist — Abstract class for implementing N-dimensional probability distributions.
- NcmStatsDistKDE — Abstract class for implementing N-dimensional probability distributions with a fixed density estimator kernel.
- NcmStatsDistVKDE — Abstract class for implementing N-dimensional probability distributions with a variable density estimator kernel.
- NcmStatsDistKernel — An N-dimensional kernel used to compute the kernel density estimation function (KDE) in the NcmStatsDist class.
- NcmStatsDistKernelGauss — An N-dimensional Gaussian kernel used to compute the kernel density estimation function (KDE) in the NcmStatsDist class. An N-dimensional Gaussian kernel used to compute the kernel density estimation function (KDE) in the NcmStatsDist class.
- NcmStatsDistKernelST — An N-dimensional Student's t kernel used to compute the kernel density estimation function (KDE) in the NcmStatsDist class.
- MCMC and ESMCMC
- NcmFitMCMC — Markov Chain Monte Carlo analysis.
- NcmFitESMCMC — Ensemble sampler Markov Chain Monte Carlo analysis.
- NcmFitESMCMCWalker — Ensemble sampler Markov Chain Monte Carlo walker class.
- NcmFitESMCMCWalkerStretch — Ensemble sampler Markov Chain Monte Carlo walker - stretch move.
- NcmFitESMCMCWalkerWalk — Ensemble sampler Markov Chain Monte Carlo walker - walk move.
- NcmFitESMCMCWalkerAPES — Ensemble sampler Markov Chain Monte Carlo walker - apes move.
- MCMC Testing
- NcmModelMVND — Multivariate Normal Distribution mean model.
- NcmDataGaussCovMVND — Multivariate Normal Distribution -- covariance provided.
- NcmModelRosenbrock — Multivariate Normal Distribution mean model.
- NcmDataRosenbrock — Rosenbrock distribution.
- NcmDataGaussMix2D — Gaussian Mixture 2d distribution.
- NcmModelFunnel — Multivariate Normal Distribution mean model.
- NcmDataFunnel — Funnel distribution.
- Spherical maps and Healpix
- NcmSphereMap — An re-implementation of Healpix.
- GObject introspection compatibility
- Gir Scanning Compatibility — Gir scanning types stubs.
- Cosmological Models
- NcHICosmo — Abstract class for implementing homogeneous and isotropic cosmological models
- NcHICosmoPrior — Collection of priors for NcHICosmo models
- NcHICosmoLCDM — $\Lambda$CDM model
- NcHICosmoGCG — Generalized Chaplygin Gas
- NcHICosmoIDEM2 — Interacting Dark Energy Model
- NcDECont — Dark energy contraction perturbations model
- Darkenergy
- NcHICosmoDE — Abstract class for implementing dark energy models
- NcHICosmoDEReparamOk — Dark Energy -- reparametrization $\Omega_{x0} \to \Omega_{k0}$
- NcHICosmoDEReparamCMB — Dark Energy -- CMB reparametrization
- NcHICosmoDEXcdm — Dark Energy -- constant equation of state
- NcHICosmoDEWSpline — Dark Energy -- spline equation of state
- NcHICosmoDECpl — Dark Energy -- Chevallier–Polarski–Linder equation of state
- NcHICosmoDEJbp — Dark Energy -- Jassal-Bagla-Padmanabhan equation of state
- Quantum Gravity Bounce
- NcHICosmoQGRW — Radiation plus $w$-fluid model with a quantum generated bounce phase model.
- NcHICosmoVexp — Single scalar field with an exponential potential
- Kinematic Models
- NcHICosmoQConst — Kinetic model -- Constant deceleration function
- NcHICosmoQLinear — Kinetic model -- Linear deceleration function
- NcHICosmoQSpline — Kinetic model -- Spline deceleration function
- NcHICosmoQRBF — Kinetic model -- Spline deceleration function
- Primordial Cosmology Models
- NcHIPrim — Abstract class for implementing homogeneous and isotropic primordial cosmological models.
- Inflationary
- NcHIPrimPowerLaw — Power law implementation for primordial spectra.
- NcHIPrimAtan — Arctangent modification of the power law primordial spectrum
- NcHIPrimExpc — Exponential cutoff modification of the power law primordial spectrum
- NcHIPrimBPL — Broken power law modification of the power law primordial spectrum
- NcHIPrimSBPL — Smooth Broken power law modification of the power law primordial spectrum
- Observational Cosmology Models
- Planck Foreground and Instrument Models
- NcPlanckFI — Abstract class for Planck Foreground and Instrument models.
- NcPlanckFICorTT — Planck Foreground and Instrument model for TT correlation maps
- NcPlanckFICorTTTEEE — Planck Foreground and Instrument model for TT correlation maps
- Supernova Covariance Models
- NcSNIADistCov — Supernovae distance covariance between distance estimates.
- Cosmological Calculators
- NcDistance — Cosmological distance and time related quantities.
- NcScalefactor — Scale factor as a function of the conformal time.
- NcRecomb — Abstract class for cosmic recombination.
- NcRecombSeager — Cosmic recombination implementing Seager (1999).
- NcRecombCBE — Cosmic recombination by Class.
- NcHIReion — Abstract class for implementing homogeneous and isotropic reionization models.
- NcHIReionCamb — CAMB-like reionization object.
- NcHIReionCambReparamTau — CAMB reionization reparametrization $z_\mathrm{reion} \to \tau_\mathrm{reion}$.
- NcHIQG1D — Minisuperspace 1D quantum gravity models
- Perturbations
- NcHIPert — Abstract class for perturbation in homogeneous and isotropic cosmologies.
- NcHIPertComp — Perturbation background variables transport object
- NcHIPertWKB — WKB perturbation object.
- NcHIPertAdiab — Perturbation object for adiabatic mode only.
- NcHIPertGW — Perturbation object for gwatic mode only.
- NcHIPertTwoFluids — Perturbation object for a two fluids system.
- NcHIPertBoltzmann — Abstract class for perturbative Boltzmann hierarchy.
- NcHIPertBoltzmannStd — Perturbations object for standard Boltzmann hierarchy model.
- NcHIPertFirstOrder — Base object for implementing first order perturbation in a Friedmann background.
- Gravitational theories
- NcHIPertGrav — Abstract class describing a general first order gravitation theory.
- NcHIPertGravEinstein — First order Einstein equations on a Friedmann background.
- Perturbation components
- NcHIPertComp — Abstract class describing a general perturbation component.
- NcHIPertCompPB — Photon-Baryon plasma compoment
- CLASS Backend
- NcCBEPrecision — CLASS (Cosmic Linear Anisotropy Solving System) backend for perturbations
- NcCBE — CLASS (Cosmic Linear Anisotropy Solving System) backend
- NcHIPertBoltzmannCBE — CLASS (Cosmic Linear Anisotropy Solving System) backend for perturbations
- Perturbation Interfaces
- NcHIPertITwoFluids — Perturbation interface for two fluids system.
- Large Scale Structure
- Window Function
- NcWindow — Abstract class for window functions.
- NcWindowTophat — A top-hat window function.
- NcWindowGaussian — A gaussian window function.
- Transfer Function
- NcTransferFunc — Abstrac class for perturbation transfer function.
- NcTransferFuncBBKS — Bardeen, Bond, Kaiser and Szalay (BBKS) transfer function.
- NcTransferFuncEH — Eisenstein-Hu fitting function for the transfer function.
- NcTransferFuncCAMB — Transfer function using CAMB as backend.
- NcGrowthFunc — Growth function of linear perturbations.
- Matter Power Spectrum
- NcPowspecML — Abstract class for linear matter power spectrum implementation.
- NcPowspecMLFixSpline — Class for linear matter power spectrum from a fixed spline.
- NcPowspecMLTransfer — Class for linear matter power spectrum from a transfer function.
- NcPowspecMLCBE — linear matter power spectrum from CLASS backend.
- NcPowspecMNL — Abstrac class for non-linear matter power spectrum implementation.
- NcPowspecMNLHaloFit — nonlinear matter power spectrum from Halofit model.
- Density Profile
- NcHaloDensityProfile — Abstract class for density profile functions.
- NcHaloDensityProfileNFW — Density profile of Navarro-Frenk-White type.
- NcHaloDensityProfileEinasto — Density profile of Einasto type.
- NcHaloDensityProfileDK14 — Density profile of Diemer \& Kravtsov type.
- NcHaloDensityProfileHernquist — Density profile of Hernquist type.
- Multiplicity Function
- NcMultiplicityFunc — Dark matter halo multiplicity function.
- NcMultiplicityFuncPS — Dark matter halo -- Press-Schechter multiplicity function.
- NcMultiplicityFuncST — Dark matter halo -- Sheth-Tormen multiplicity function.
- NcMultiplicityFuncJenkins — Dark matter halo -- Jenkins multiplicity function.
- NcMultiplicityFuncWarren — Dark matter halo -- Warren multiplicity function.
- NcMultiplicityFuncTinker — Dark matter halo -- Tinker multiplicity function.
- NcMultiplicityFuncTinkerMeanNormalized — Dark matter halo -- Tinker normalized multiplicity function mean matter density.
- NcMultiplicityFuncCrocce — Dark matter halo -- Crocce multiplicity function.
- NcMultiplicityFuncBocquet — Dark matter halo -- Bocquet multiplicity function.
- NcMultiplicityFuncWatson — Dark matter halo -- Watson multiplicity function.
- NcHaloMassFunction — Clusters mass function.
- Halo Bias Function Type
- NcHaloBias — Abstract class for halo bias function type.
- NcHaloBiasPS — Press-Schechter halo bias function type.
- NcHaloBiasSTSpher — Sheth-Tormen spherical halo bias function type.
- NcHaloBiasSTEllip — Sheth-Tormen elliptical halo bias function type.
- NcHaloBiasTinker — Tinker halo bias function type.
- NcGalaxyAcf — Galaxy angular correlation function.
- Cluster Redshift
- NcClusterRedshift — Abstract class for cluster redshift distributions.
- NcClusterRedshiftNodist — Cluster abundance redshift real redshift distribution.
- NcClusterPhotozGauss — Individual gaussian photometric distribution for clusters.
- NcClusterPhotozGaussGlobal — Global gaussian photometric distribution for clusters.
- Cluster Mass
- NcClusterMass — Abstract class for cluster mass distributions.
- NcClusterMassNodist — Cluster mass real mass distribution.
- NcClusterMassLnnormal — Cluster mass ln-normal distribution.
- NcClusterMassVanderlinde — Sunyaev-Zel'dovich cluster mass distribution.
- NcClusterMassBenson — Sunyaev-Zel'dovich cluster mass distribution.
- NcClusterMassBensonXRay — Sunyaev-Zel'dovich and x-ray cluster abundance mass distribution.
- NcClusterMassPlCL — Planck-CLASH Cluster Mass Distribution
- NcClusterMassAscaso — FIXME
- Cross-correlations
- Cross-correlations — Angular auto- and cross-spectra.
- NcXcorAB — Cross-correlations data storage object.
- NcXcorLimberKernel — Abstract object for the kernels of projected observables used in cross-correlations.
- NcXcorLimberKernelGal — implementation of NcXcorLimberKernel for galaxy density
- NcXcorLimberKernelCMBLensing — implementation of NcXcorLimberKernel for CMB lensing
- NcXcorLimberKernelWeakLensing — implementation of NcXcorLimberKernel for galaxy weak lensing
- NcClusterAbundance — Cluster abundance distribution
- NcClusterPseudoCounts — FIXME
- NcCorClusterCmbLensLimber — Cluster and CMB lensing correlation using halo model and Limber approximation.
- Galaxy Redshift
- NcGalaxyRedshift — Abstract class describing galaxy redshifts.
- NcGalaxyRedshiftSpec — Class describing spectroscopic galaxy redshifts.
- NcGalaxyRedshiftSpline — Class describing spectroscopic galaxy redshifts.
- NcGalaxyRedshiftGauss — Class describing Gaussian photometric galaxy redshifts.
- Weak Lensing
- NcWLSurfaceMassDensity — Weak lensing surface mass density
- NcReducedShearClusterMass — FIXME cluster mass estimation via reduced shear
- NcReducedShearCalib — Reduced Shear Calibration
- NcReducedShearCalibWtg — Reduced Shear Calibration
- NcGalaxyWL — Class describing galaxy weak lensing distributions.
- NcGalaxyWLDist — Abstract class describing galaxy wl_dists.
- NcGalaxyWLEllipticityGauss — Abstract class describing galaxy weak lensing ellipticity Gaussian distribution
- NcGalaxyWLEllipticityKDE — Class describing galaxy weak lensing ellipticity with Kernel Density Estimation
- NcGalaxyWLEllipticityBinned — Class describing galaxy weak lensing ellipticity with binning
- NcGalaxyWLProj — Abstract class describing galaxy weak lensing reduced shear Gaussian distribution
- Galaxy ACF
- NcGalaxySelfunc — Galaxy phenomelogical selection function.
- Cosmological Data
- NcDataCMB — Helper function for instantiating CMB data
- NcDataCMBShiftParam — Cosmic microwave background data -- shift parameter.
- NcDataCMBDistPriors — Cosmic microwave background data -- distance priors.
- NcDataHubble — Hubble function data.
- NcDataHubbleBao — Hubble function data from BAO.
- NcDataBao — Helper functions for instantiating BAO data
- NcDataBaoA — Baryon oscillation data -- acoustic scale $A$.
- NcDataBaoDV — Baryon oscillation data -- volume mean $D_V$.
- NcDataBaoRDV — Baryon Oscillation Data -- $r_s / D_V$ ratio.
- NcDataBaoDVDV — Baryon oscillation data -- $D_V / D_V$ ratio.
- NcDataBaoEmpiricalFit — Baryon oscillation data -- $D_V / r_s$ empirical likelihood.
- NcDataBaoEmpiricalFit2d — Baryon oscillation data -- $D_H / r_d$ and $D_t / r_d$ empirical likelihood.
- NcDataBaoDHrDAr — Baryon Oscillation Data -- $(D_H/r,\; D_A/r)$ data.
- NcDataBaoDtrDHr — Baryon Oscillation Data -- $(D_H/r,\; D_t/r)$ data.
- NcDataBaoDMrHr — Baryon Oscillation Data -- $(D_M/r,\; H/r)$ data.
- NcDataSNIAId — Helper function for instantiating type Ia supernova data
- NcDataDistMu — Distance modulus data.
- NcDataSNIACov — Type Ia supernovae data with covariance error matrix
- NcDataClusterNCount — Cluster number count data.
- NcDataClusterPseudoCounts — Galaxy clusters data -- pseudo number counts likelihood.
- NcDataClusterWL — Cluster weak lensing likelihood.
- NcDataReducedShearClusterMass — Galaxy clusters data -- pseudo number counts likelihood.
- NcDataPlanckLKL — Planck Likelihood interface.
- NcDataXcor — cross-correlation data object.
- ABC analysis
- NcABCClusterNCount — Object implementing Approximate Bayesian Computation (ABC) for cluster number counts.
- Mathematical Utilities
- NcmBinSplit — Binnary splitting algorithms used to evaluate sums fast and with arbitrary precision.
- NcmFunctionCache — A generic cache for functions values
- NcmMemoryPool — Generic memory pool.
- NcmIntegral — Numerical integration helpers.
- Enumeration Types
- NcmEnumTypes — Automaticaly generated enum types from NumCosmoMath library.
- NcEnumTypes — Automaticaly generated enum types from NumCosmo library.
- Objects Hierarchy
- API Index
- API Index Deprecated
- Annotation Glossary


AMQPWorker
Extends:
AMQPWorker represents a Event dispatch Worker implementing rabbitmq producer to send messages
Static Member Summary
| Static Public Members | ||
| public static get |
Static property containing all the queues created by the worker as the deployment topology |
Method Summary
| Public Methods | ||
| public |
async bindQueues() Perform the binding of all the topology queues to the configured exchange |
|
| public |
async checkQueues() Check all the queues to be configured, by checking it will explicity create the queues if they do not exists |
|
| public |
async getChannel(): amqp.Channel Returns the channel to the configured rabbitmq broker |
|
| public |
Published events to the configured exchange |
Static Public Members
Public Methods
public async bindQueues() source
Perform the binding of all the topology queues to the configured exchange
public async checkQueues() source
Check all the queues to be configured, by checking it will explicity create the queues if they do not exists
public async getChannel(): amqp.Channel source
Returns the channel to the configured rabbitmq broker
Return:
| amqp.Channel |


Apache Airflow's documentation is maintained elsewhere. You will be redirected to the new documentation within 2 seconds. If the browser does not automatically redirect you, you may want to go to
the destination
manually.


This package contains all the Struts action classes (referenced in struts-config.xml)
which process user inputs and interact with the Grouper API. The Javadoc for
individual action classes indicates which parameters (from HttpServletRequest),
attributes (from HttpServletRequest or HttpSession) and cookies,
are read or written* by an action class.
Action classes which interact with the Grouper API should extend GrouperCapableAction,
which gives access to an appropriate GrouperSession and various utility methods.
When customising the Grouper UI it may be necessary to change the behaviour
of an existing action. This may be achieved in one of 3 ways:
- If there is no alternative, write a new class and override the action configuration
in struts-config.xml to use the new action class. This should only be necessary
if an action carries out an irreversible operation, however, consider the
remaining options first.
- Write a new action class which is called before or after the existing
action. This may be achieved by:
- reconfiguring forwards from other actions, however, this approach will
not work if an action is usually referenced directly in HTML
- reconfigure forwards from the action class you are modifying such that
the new action class is called after the original has finished its work
- reconfigure the existing action to have a new path. Write a new action
class and configure it to have the pat hof th eoriginal action, but forward
to the new path for that action.
- extend the existing action class and call super.grouperExecute.
This allows you to execute code before and after the original action. You
must override the existing Struts configuration to associate the action with
your new class.
*Request parameters are usually read-only, however, where ActionForm fields
are set these are considered to have been written.


Home
About
Worship Experience
Messages
Calendar
Give
Prayer Request
Contact Us
Pastor Jameson Eichelburger, Sr.
Lady Tomecka Eichelburger


Wireless - Interface
SSID:
Channel:
Auto
1
2
3
4
5
6
7
8
9
10
11
Wireless Mode:
Auto
54G Only
802.11B Only
54g Protection
Authentication Method:
Open System
Shared Key
WPA-Personal
WPA2-Personal
WPA-Auto-Personal
WPA-Enterprise
WPA2-Enterprise
Radius with 802.1x
WPA Encryption:
TKIP
AES
TKIP+AES
WPA Pre-Shared Key:
WEP Encryption:
None
WEP-64bits
WEP-128bits
WEP Key Type:
HEX
ASCII
Passphrase:
WEP Key 1 :
WEP Key 2 :
WEP Key 3 :
WEP Key 4 :
Key Index:
Key1
Key2
Key3
Key4
Network Key Rotation Interval:
Restore:
Clear the above settings and restore the settings in effect.
Finish:
Confirm all settings and restart WL-330gE now.
Apply:
Confirm above settings and continue.


Establishing your storage configuration¶
Use the Rackspace cloud storage services–Cloud Block Storage, Cloud Files, and Rackspace CDN–to make your cloud recoverable and manageable.
When you create a cloud server, storage of several kinds is alloted to that server based on the choices that you make. Cloud Servers handles initial storage allocations; you can use Cloud Block Storage and Cloud Files to add more storage to your core infrastructure, and Rackspace CDN to accelerate the delivery of your stored content.
- To learn key concepts about Cloud Block Storage, begin at Understanding Cloud Block Storage.
- To see a list of actions that Cloud Block Storage can perform, visit Actions for Cloud Block Storage.
- To learn how to perform Cloud Block Storage actions by using your choice of interface, begin at one of the following topics:
- To learn key concepts about Cloud Files, begin at Understanding Cloud Files.
- To see a list of actions that Cloud Files can perform, visit Actions for Cloud Files.
- To learn how to perform Cloud Files actions by using your choice of interface, begin at one of the following topics:
- To learn key concepts about Rackspace CDN, begin at Understanding Rackspace CDN.
- To see a list of actions that Rackspace CDN can perform, visit Actions for Rackspace CDN.
- To learn how to perform Rackspace CDN actions by using your choice of interface, begin at one of the following topics:


--- layout: things-page title: Australia breadcrumb: no ---
We apologise for any silly sentences that don't make any sense, jokes that aren't funny, inconsistencies, contradictions, embellishments and/or outright falsehoods that may be contained within this document.
However, we ask you to please keep in mind that even in the most outrageous story told by an Australian, there is always a seed of truth that is unwise to ignore.
Melbourne • Yarra Valley • Mornington Peninsula • Geelong • Ballarat • Bendigo • Gippsland • Western Districts & Shipwreck Coast • Northern & Northeastern Victoria • The Mallee
Hobart
The Top End • The Red Centre


--- layout: page ---
Created with Jekyll using a modified version of the Daktilo theme.
The modified version is also licensed under the MIT License.


Filter
public enum Filter
Darwin only. Filter to apply to a kqueue event.
-
Undocumented
Declaration
Swift
public enum Filter
-
Undocumented
Declaration
Swift
public enum Filter
-
Undocumented
Declaration
Swift
public enum Filter
-
Undocumented
Declaration
Swift
public enum Filter
-
Undocumented
Declaration
Swift
public enum Filter
-
Undocumented
Declaration
Swift
public enum Filter
-
Undocumented
Declaration
Swift
public enum Filter
-
Undocumented
Declaration
Swift
public enum Filter


--- layout: post title: hurricane on the outside, sun dress weather inside date: 2011-08-28 04:00:22.000000000 -04:00 type: post published: true status: publish categories: - style tags: - everyday outfit - style meta: _edit_last: '1' _oembed_3c43f84e1da5a19e3ec6a6861f9a096b: author: login: sophie email<EMAIL_ADDRESS>display_name: Pika first_name: '' last_name: '' ---
Sundress Weather.
It is a beautiful thing.
Someone should do research on the psychological effects of good weather on the floral prints lobe of the brain. Seriously.
Why am I writing about Sundress Weather amidst a torrential downpour as hurricane Irene slowly but menacingly makes its way up the East coast?
Because Sundress Weather is brief. Sundress Weather is fleeting. Sundress Weather is that small gap between when all the Frisbees start flying out on campus and when your ice cream liquefies before you even get to take a bite. The rest of the year is t-shirt and leggings weather. Spend 10 minutes getting ready in the morning (7 of them on trying to find that damn problem set I most definitely finished, I think…) weather. Trying not to hit people with my unwieldy bag of books weather.
Unfortunately, the rest of the year also happens to coincide with my entire time at school, where I get to live with some of my greatest friends in what is no doubt the greatest city in the world. And, yes, try to survive midterms and projects and finals, all while constantly trying to remind convince myself that it’s doing me good.
Which is why, inspired by my talented and tech-savvy friend Amrita, I’m going to embark on a little fashion project. Because even if it is a-hurricaine-ing outside, it never hurts to bring a little Sundress Weather inside.
Here’s the plan:
And for reference, here are a few of my thoughts on fashion…
P.S.: In other exciting news, Mon Petit Chou just needs 2 more likes to reach the 100-fan mark on Facebook! Maybe you will be lucky user 100? Check it out-- it’s a great way to keep tabs on what’s cooking if you’re a Facebook user.
P.P.S. Hope everyone stays indoors and safe in the stormy weather. Keep your fingers crossed for New York and the Tri-State area.


A beginner’s guide to realizing proper navigation in a React Native application using ClojureScript and shadow-cljs
That’s a big bunch of words. Let me briefly introduce them to you, so that I can then dive deeper into some of them. “Beginner” in this case means that, a week before I started doing this, I had practically zero experience with Clojure(Script) and React Native. I do have quite a bit of experience using React, and also writing native iOS applications (Swift/Objective-C).
“Guide” means that I’m going to explain to you how I accomplished my goal. You’ll have to interpret it and follow along if you want to do the same. Future versions of any of the tools may break this guide.
React Native Navigation is a framework for React Native. Which is a framework for building cross-platform apps for iOS and Android using JavaScript, but you probably already knew that part. ClojureScript is a functional programming language. It’s a variant of Clojure that compiles to JavaScript. “Proper navigation” is, admittedly, a bit subjective; I’ll explain this part in more detail below. Finally, shadow-cljs is the toolchain I used as an easy way to integrate a bunch of ClojureScript code into an originally Javascript-based project.
A summary of this guide is:
react-native
cli).react-native-navigation
dependency.So let’s get started. I executed all these steps exactly as I’m describing here, the result of which you can find in my GitHub repo. Commit messages include all details about the commands I used. If you want to read my rant about wanting to use native navigation, keep reading till the very end of this post :)
Please note that this post does not include all the code that you need to make it work, that would be too much for a web page. Please refer to the final solution in my GitHub repo if you want to reproduce all of it.
This step is very easy. First, if you haven’t got it yet, install
react-native-cli
:
npm install -g react-native-cli
Then create a new project:
react-native init CLJSReactNativeNavigation
So far so good, nothing new here, let’s move on.
We’re going to use the standalone version of shadow-cljs, as recommended. So we add the npm dependency for shadow-cljs:
yarn add --dev shadow-cljs
Now we need to configure shadow-cljs a bit. We create a file called
shadow-cljs.edn
and give it the following content:
{:source-paths
["src/main" ;; production code
"src/test"] ;; yes we're going to add tests as well!
:dependencies
[[reagent "0.8.1"]]
:builds
{:myapp ;; the target definition
{:target :react-native ;; the target type
:init-fn myapp/init ;; react native's entry point
:output-dir "build"}}} ;; where to put the built JS
This is telling shadow-cljs that there is a target called “myapp”, that
it’s a React Native target, that the entry point of our app is the function
init
in the myapp
namespace, and that the output should be written to the
folder build
.
Now let’s create that myapp
namespace. In src/main
create a file called
myapp.cljs
with the following contents:
(ns myapp
(:require [reagent.core :as r :refer [atom]]
["react-native" :as rn :refer [AppRegistry]]))
(defn app-root []
[:> rn/View {:style {:flex-direction "column"
:margin 40
:align-items "center"
:background-color "white"}}
[:> rn/Text {:style {:font-size 30
:font-weight "100"
:margin-bottom 20
:text-align "center"}}
"Hi Shadow!"]])
(defn init []
(.registerComponent AppRegistry
"CLJSReactNativeNavigation"
#(r/reactify-component app-root)))
Time to check this out! Run the following commands in your terminal:
yarn shadow-cljs compile myapp
yarn react-native run-ios
Tada!
When using shadow-cljs, you also get its variant of hot reloading. You don’t need to use the developer menu to enable it, but you do need to add a bit of code to make it work: (a) you need to had a function that performs the reload, and (b) you need to enable hot reloading in the config.
Let me just give you the code of myapp.cljs
and then explain what’s going on.
(ns myapp
(:require [reagent.core :as r :refer [atom]]
["react-native" :as rn :refer [AppRegistry]]))
(defonce component-to-update (atom nil))
(defn content []
[:> rn/Text {:style {:font-size 30
:font-weight "100"
:margin-bottom 20
:text-align "center"}}
"Hi Shadow!"])
(defn app-root []
[:> rn/View {:style {:flex-direction "column"
:margin 40
:align-items "center"
:background-color "white"}}
[content]])
(def updatable-app-root
(with-meta app-root
{:component-did-mount
(fn [] (this-as ^js this
(reset! component-to-update this)))}))
(defn reload {:dev/after-load true} []
(.forceUpdate ^js @component-to-update))
(defn init []
(.registerComponent AppRegistry
"CLJSReactNativeNavigation"
#(r/reactify-component updatable-app-root)))
This is what it does:
content
), because the call forceUpdate
that we’ll use
updates everything below the application root component, not the root
component itself.component-did-mount
handler
(updatable-app-root
). This handler stores the actual JavaScript object
that represents the root component into the atom component-to-update
.reload
is added, which takes the value of that atom and calls
the method forceUpdate
on it.One final step remains: enabling hot reloading in shadow-cljs.edn
. It’s new
content is:
{:source-paths
["src/main" ;; production code
"src/test"] ;; yes we're going to add tests as well!
:dependencies
[[reagent "0.8.1"]]
:builds
{:myapp ;; the target definition
{:target :react-native ;; the target type
:init-fn myapp/init ;; react native's entry point
:output-dir "build" ;; where to put the built JS
:devtools {:autoload true}}}} ;; enables hot-reloading
If you reload the app, changing the text in the content
component should
cause the app to automatically update!
This bit is a somewhat tedious I’m afraid. You’ll have to go through the instructions to setup React Native Navigation. Add the npm dependency, update your Xcode project, update iOS source code, update Android build files, and update Android source code. Tip for Android part: Please don’t blindly copy-paste. Some of the instructions refer are not up to date, some parts are not really needed, etc. If you want you can have a look at how I did it.
Obviously you’ll skip the last step of the instructions, namely the part where the JavaScript code is updated to use React Native Navigation. We’ll address that in ClojureScript next.
Ok, roll up your sleeves, because here comes the interesting part.
In JavaScript we would need to do something like this:
import { Navigation } from 'react-native-navigation'
Navigation.registerComponent('navigation.playground.WelcomeScreen', () => App)
Navigation.events().registerAppLaunchedListener(() => {
Navigation.setRoot({
root: {
component: {
name: 'navigation.playground.WelcomeScreen'
}
}
})
})
Obviously in ClojureScript we need to do something similar. There’s a problem
though: we need a handle to the actual JavaScript component in order to call
forceUpdate
on it (for hot reloading). React Native Navigation has made the
design choice that it creates new root components for screens that you push
on the navigation stack. So also for those components we need a handle and
call forceUpdate
. We accomplish this by not registering the component itself
with Navigation
, but a wrapper of that component.
This causes another problem though. React Native Navigation gives components
that you register a componentId
. It uses this for its internal registration
so that it can make navigation work. For example, when you push a new screen
onto the navigation stack, it uses the componentId
to find the screen from
which you are pushing. The problem is that we registered the wrapper, but
we’re navigating from the wrapped component. Which does not have a
componentId
, because we never registered it with Navigation
. Solution:
make the wrapper in such a way that it passes its componentId
on to the
wrapped component.
But there is more! React Native Navigation defines some additional life cycle
methods, such as navigationButtonPressed
. And for that to work, you need
to call Navigation.bindComponent
. So our wrapper also calls
bindComponent
and forwards navigationButtonPressed
. Forwarding other
life cycle methods is left as an exercise for the reader.
Here’s the main code for the wrapper (full version):
;; current namespace is `env`
(defonce id-seq-ref (atom 0))
(defonce mounted-ref (atom {}))
(defonce screens-ref (atom {}))
(defn register [key]
(let [get-props
(fn [this]
{::key key
::id (-> this .-state .-id)
:component-id (-> this .-props .-componentId)})
wrapper
(crc #js ;; crc is create-react-class
{:displayName
(str key "Wrapper")
:getInitialState
(let [id (swap! id-seq-ref inc)]
(fn [] #js {:key key
:id id}))
:componentDidMount
(fn []
(this-as
^js this
(bind-component this)
(swap! mounted-ref
assoc-in [key (-> this .-state .-id)] this)))
:componentWillUnmount
(fn []
(this-as
^js this
(swap! mounted-ref update key dissoc (-> this .-state .-id))))
;; FIXME: forward other lifecycles the same way
:navigationButtonPressed
(fn []
(this-as
^js this
(let [{:keys [navigation-button-pressed]}
(get @screens-ref key)
props
(get-props this)]
(js/console.log "navigationButtonPressed"
key
(boolean navigation-button-pressed)
(pr-str props))
(when navigation-button-pressed
(navigation-button-pressed props)))))
:componentDidAppear
(fn []
(this-as
^js this
(js/console.log "componentDidAppear" key)))
:componentDidDisappear
(fn []
(this-as
^js this
(js/console.log "componentDidDisappear" key)))
:render
(fn []
(this-as
^js this
(let [{:keys [render]}
(get @screens-ref key)
props
(get-props this)]
(js/console.log "render" key (pr-str props))
(-> (render props)
(r/as-element)))))})]
(register-component key (fn [] wrapper))))
This stores the mounted components in mounted-ref
, which we can then use
for the hot reloading:
(defn reload {:dev/after-load true} []
(doseq [[key instances] @mounted-ref
[id inst] instances]
(js/console.log "forceUpdate" key id)
(.forceUpdate ^js inst)))
The register
method uses an atom screens-ref
to forward life cycle methods,
so we need to provide a function for screens to add themselves:
(defn add-screen [key screen-def]
(swap! screens-ref assoc key screen-def))
Initially, in myapp/init
we called React Native’s registerComponent
. Now
we call our env/register
instead. We could just call (env/register "App")
,
but we want to pass some options for the navigation bar.
Furthermore we need to call the Navigation.events().registerAppLaunchedListener
JavaScript function to set the navigation root for our app.
The init
function is now:
(defn init []
(env/register "App"
{:topBar {:visible "true"
:title {:text "My App"}
:rightButtons [{:id "add" :systemItem "add"}]}})
(-> (rnn/Navigation.events)
(.registerAppLaunchedListener
(fn []
(->> {:root
{:stack
{:children [{:component {:name "App"}}]}}}
(clj->js)
(rnn/Navigation.setRoot))))))
That’s it! Done! Just four simple, easy, almost trivial steps! Well maybe not so trivial. I guess a ClojureScript beginner couldn’t have come up with this. Well, in fact I am a ClojureScript beginner and I did not come up with this solution myself. All the credits go to Thomas Heller, the author of shadow-cljs. He has been amazing in his support by answering all of my beginner-level questions, and then he ended up conjuring this solution and committing it to my repository. He actually spent hours on this I believe, and that level of support from a community is truly awesome (and rare). He doesn’t seem to be advertising it very much, but you can become his patreon.
What’s special about React Native Navigation is that it is implemented using the
real platform native components, specifically
UINavigationController
on
iOS. I seem to be at odds with most of the rest of the world on this, but I
happen to think that it is very important to present the user with an
experience that is (as much as possible) identical to that of native apps. You
shouldn’t be able to tell from the user experience whether the app was written
using native technology or cross platform technology. Not even when you update
your OS to a new major version. So if my app uses a navigation stack, it has to
be the native one. Maybe I’m more sensitive to this then others, but I get
really upset by apps that don’t support the normal gesture for going back up the
navigation stack. I also get annoyed when the animation that is used while going
back is slightly non-standard. Using the native components is the only way to
accomplish that. Other components can come close, but not close enough for me.
Like I said in the beginning, future versions of any of the tools may break this guide. So it is only fair to mention which versions I was using for this:
| Tool | Version |
|---|---|
| node | 11.10.1 |
| npm | 6.5.0-next.0 |
| react | 16.8.3 |
| react-native | 0.59.3 |
| react-native-cli | 2.0.1 |
| react-native-navigation | 2.16.0 |
| shadow-cljs | 2.8.26 |
| Xcode | 10.2 |
| iOS SDK | 12.2 |
| Android SDK | API levels 26, 27, 28 |
| Build tools 27.0.3, 28.0.3 | |
| System images: android-28 |


We are an organization of 225 hockey referees serving London and area. If you are currently looking for an organization to referee your hockey league, our team would like the opportunity to assist
MoreServices Section
Services
Official Development Program
Official Development Program
Take a look at our certifications and choose best for yourself
Morereferee-role-section
The Role Of Referee
A referee is responsible for the general supervision of the game and can be identified by the red or orange armbands.
Under most officiating systems, the referee is the only official with the authority to assess penalties for violations of the rules. However, the linesmen can report a variety of penalties, such as Too many men on the ice and major penalties, to the referee, who may then assess the penalty. The referee also conducts the opening face-off in each period and face-offs that follow after a goal is scored, which are done at the centre ice face-off dot.
Download to know more about responsibilities and duties of a referee on the ice-field.
membership-letter-section
Get Updates About Membership
Sign up to keep yourself updated
regarding our new membership plans.
Click Here to know more about membership.
gallery-Latest-updates-section
Gallery
To take a trivial example, which of us ever undertakes laborious physical exercise, except to obtain some advantage But who has any right