--- layout: syllabus title: Medieval World ---
Medieval World
HN202-01S | Spring 2023
01S TTH 9:25-10:40; Humanities Center, 232
01S Enrichment Hour F 2:00pm-2:50pm; Humanities Center, 338
Plenary Seminar 3-3:50pm; Knott Hall, B01
Dr. Jeffrey C. Witt | jcwitt [at] loyola [dot] edu | ext. 2947
Philosophy Department 050M
Office Hours: By Appointment Tues: 1pm-3pm; Wed: 1pm-3pm; Thurs: 1pm-3pm
This seminar course will examine the period of history spanning from 400 to 1500 C.E., often referred to as the Middle Ages. We will examine this period from multiple dimensions, looking at the historical development of social ideas, theology, philosophy, and literature. As we will see, it is an extremely diverse period, and the seminar format will provide us with significant time to reflect and debate the ways in which this period does and does not represent a unified whole. Further, in keeping with our Messina theme, "Self and Other," this course will consider the ways different thinkers, writers, and political actors have thought about the individual and the pursuit of happiness in the context of society and the outsider. Finally, the course aims to provide space to reflect on the ways in which the Middle Ages influence and challenge our own assumptions about ourselves and our place in society.
Students will be able to demonstrate knowledge of principle actors, historical developments, and foundational texts from the period 400-1500 C.E.
Students will be able to examine and articulate connections between developments in medieval history, literature, philosophy, and theology.
Students will be able to converse cogently about the Middle Ages as an idea and as a historical reality.
Rosenwein, A Short History of the Middle Ages (SHMA), 5th ed. (Toronto: University of Toronto Press, 2018)
Augustine, The City of God (COG), trans. Marcus Dods (New York: The Modern Library, 1993)
Rule of St. Benedict (RSB) (Collegeville, MN: Liturgical Press, 1982)
Two Lives of Charlemagne (TLC), trans. David Ganz (New York: Penguin, 2008)
The First Crusade: The Chronicle of Fulcher of Chartres and Other Source Material (TFC), ed. Edward Peeters (Philadelphia: University of Pennsylvania Press, 1998)
Beowulf (B), trans. Seamus Heaney (New York: W. W. Norton, 2002)
Chrétien de Troyes, Arthurian Romances (AR), trans. William Kibler (New York: Penguin, 2004)
The Green Knight, ed. by J.R.R. Tolkien (GK), (William Morrow, 2021)
Dante, Purgatorio (P), trans. Robert Durling (Oxford: Oxford University Press, 2003)
Class involvement means, first of all, coming to class. Secondly, it means coming to class prepared. This primarily means both having read the assigned text and having the day's reading out and ready to be marked. Thirdly, it means being an active participant in the classroom. Finally, participation includes attendance and engagement during Messina EH, Messina events (and post event discussions), and plenary lectures. Lack of participation in these areas will negatively affect your overall participation grade.
Class Notes Discussion (10%): To encourage you in the above three areas, we will collaboratively prepare for class using a common set of class notes, with reading/discussion notes. Student will be expected to read and interact with the class notes using the Hypothesis Annotation Tool.
A participatory grade is meant to motivate the goal of active engagement. Thus genuine and sincere engagement, rather meeting a certain threshold or quota is the goal. Those who engage in a sincere way will generally automatically find themselves fulfilling the requirements of participation. What if follows is a general rubric to help clarify expectations.
Meets expectations (10): student contributes around 2-3 substantial posts (at least 1 of which is a response to a "discussion block" and at least one of which is a reply to another student's post). (As a rule of thumb a "substantial" post is usually between 100-200 words.) In addition to posting, the student is adding links, responding to others, and asking clarifying questions. During our in person class the student will also be prepared and willing to provide summaries of class notes and previous asynchronous discussions.
Approaches expectations (8): student occasionally posts, perhaps just once per class; comments are short, rote, showing a lack of genuine engagement with material and peers.
Because I know everyone has busy weeks, I'll drop your lowest 6 days (out of around 22 possible contributing days).
Weekly Quizzes (5%): To give you just a little push to keep up with the readings, class attendance and plenary lectures, we will have short reading quizzes which are to be completed on Moodle prior to the assigned class. Quizzes may include content from the previous weeks reading, lectures, plenaries, or the upcoming class reading. Because I know everyone has busy weeks, I'll drop your lowest 2 quizzes.
Reading Guide (2.5%): In groups of 3, students will take turns preparing the "reading guide" for 5 strategic readings: Beowulf, Knight of the Cart, the Green Knight, and Purgatory 1-15 and 16-33
Paper 1 (20%) (5-6 pages)
Paper 2 (20%) (5-6 pages)
Mid Term Exam (20%)
Final Exam (22.5%)
93% A, 90% A-, 88% B+, 83% B, 80 B-, 78% C+, 73% C, 70% C-, 68% D+, 60% D
Honor Code and Plagiarism: Students are expected to follow the university's honor code: "The Honor Code states that all students of the Loyola community have been equally entrusted by their peers to conduct themselves honestly on all academic assignments. Our goal is to foster a trusting atmosphere that is ideal for learning. In order to achieve this goal, every student must be actively committed to this pursuit and its responsibilities, and is therefore called to be active in the governing of the community’s standards. Thus, all students have the right, as well as the duty, to expect honest work from their colleagues. From this, we students will benefit and learn from the caring relationships that our community trustfully embodies. The students of this University understand that accepting collective and individual responsibility for the ethical welfare of their peers exemplifies a commitment to the community. Students who submit materials that are the products of their own mind demonstrate respect for themselves and the community in which they study. These students possess a strong sense of honor, reverence for truth, and a commitment to Jesuit education. Accordingly, students found violating the Honor Code will be reprimanded appropriately in the belief that they will, with the support of their peers, learn from the mistake. This Code not only requires students to understand the ideals of truth and personal care as the two strongest educational factors expressed in cura personalis, but also calls them to demonstrate a general concern for the welfare of their colleagues and for the University." See the honor code for further information. https://www.loyola.edu/academics/honor-code.
 Reports of such offenses are taken seriously, and Loyola encourages students experiencing sexual misconduct to report the incident in accordance with the University’s policy on Reporting Misconduct (PDF) (pages 36-37). Loyola is also committed to an environment free of other forms of harassment and discrimination. For information about policies and reporting resources, please visit harassment and discrimination policy (PDF).
Remember that while you have five teachers, I have more than 70 students. Thus, while I'm eager to connect with you, I can do this best by enforcing a few procedures.
For questions about the course, both content and procedure questions, please use our moodle help discussion board. Using this system will help ensure that I see and respond to your email. It will additionally ensure that others who have similar questions can also receive an answer. So, if you send me a direct email about course content and procedure, I will politely ask you to ask it again via our moodle "help" discussion board and I will be eager and glad to respond.
For other issues, I will be glad to discuss these with you. But I would ask that you use our office hours booking service and reserve a time slot to discuss it with me. We can generally always communicate better when we speak in person and this is an opportunity for me to get to know you better. This also helps me manage my time and provide you with the best response I can. So again, if you send me a direct email, I'll will be glad to discuss it with you, but I will often direct you to the booking system so that we can schedule a chance to talk about the issue.
**This is a tentative schedule, subject to revision depending on our progress and extenuating circumstances**
Week 1
Tue Jan 17 (Class 1) -
Thu Jan 19 (Class 2) - Augustine, City of God (COG), Book 2, pp. 40-73; SHMA, Chapter 1 (first half), pp. 1-24
Week 2
Tue Jan 24 (Class 3) - Augustine, City of God (COG), Book 19, pp. 669-709.
Thu Jan 26 (Class 4) - "Introduction to the Rule of St. Benedict" (RSB); Rule of St. Benedict (RSB); SHMA, Chapter 1 (second half), pp. 24-37.
Week 3
Tue Jan 31 (Class 5) - Isabelle Cochelin, "When the Monks were the Book" in The Medieval Bible as a Way of Life ed. Susan Boyton and Diane Reilly, pp. 61-83 (Moodle); Joseph Lynch, "Monastic Life: The Twelfth Century" in The Medieval Church: A Brief History, pp. 197-215 (Moodle).
Thu Feb 2 (Class 6) - "The Siege of Constantinople: Easter Chronicle", pp. 55-59 (Moodle); "The Quinisext Council", pp. 60-62 (Moodle); "The iconoclastic argument: The Synod of 754", pp. 62-66 (Moodle); SHMA, Chapter 2, 41-80.
Week 4
Tue Feb 7 (Class 7) - Malise Ruthven, Islam in the World, "Muhammad the Model," pp. 26-79 (Moodle).
Thu Feb 9 (Class 8) - "Muhammad's words in the Hadith: Al-bukhari, On Fasting," pp. 147-151 (Moodle); SHMA, Chapter 3, pp. 81-111.
Week 5
Tue Feb 14 (Class 9) - The Life of Charlemagne (TLC), "General Introduction," pp. ix-xx and “Introduction,” pp. 3-13; Einhard, The Life of Charlemagne (TLC), pp. 15-44.
Thu Feb 16 (Class 10) - The First Crusade (TFC), "Introduction," pp. 1-24 and Part I, "Pope Urban II at the Council of Clermont," pp. 25-46; SHMA, Chapter 4, pp. 113-151.
Week 6
Tue Feb 21 (Class 11) - The First Crusade (TFC), Part II, "The Chronicle of Fulcher of Chartres, Book I," pp. 47-101; SHMA, Chapter 5 (first half), pp. 161-184.
Thu Feb 23 (Class 12) - The First Crusade (TFC), Part III.1-6, "Peter the Hermit and the 'Crusade of the People'," pp. 102-150.
Week 7
Tue Feb 28 (Class 13) - Review day (Paper 1 Due).
Thu Mar 2 (Class 14) - Midterm Exam
Week 8
Tue Mar 7 - Spring Break
Thu Mar 9 - Spring Break
Week 9
Tue Mar 14 (Class 15) - Humanities Symposium When the Emperor was Divine by Julie Otsuka.
Thu Mar 16 (Class 16) - Humanities Symposium When the Emperor was Divine by Julie Otsuka.
Week 10
Tue Mar 21 (Class 17) - Anglo Saxon History; Beowulf Background; Make progress on Beowulf reading for Thursday
Thu Mar 23 (Class 18) - Beowulf (B), "Introduction" and Text; Beowulf (B), pp. 3-78
Week 11
Tue Mar 28 (Class 19) - Court life in the 12th Century; Chretien de Troyes Background; Make progress on Chretien de Troyes reading for Thursday
Thu Mar 30 (Class 20) - Chretien de Troyes, Arthurian Romances (AR), "The Knight of the Cart" (AR), pp. 207-294.
Week 12
Tue April 4 (Class 21) - Aquinas with Dr. Bauerschmidt;
Thu April 6 - Easter
Week 13
Tue Apr 11 (Class 22) - The Green Knight
Thu Apr 13 (Class 23) - Introduction to Dante's Purgatory; Aristotle's Ethics in the Christian Context; Dante, Inferno, Canto 1-2 (Moodle); SHMA, Chapter 7 (second half), pp. 282-300.
Week 14
Tue Apr 18 (Class 24) - Dante, Purgatorio (P), Cantos 1-15;
Thu Apr 20 (Class 25) - Dante, Purgatorio (P), Cantos 15-33.
Week 15
Tue Apr 25 (Class 26) - John Kelly, The Great Mortality, c. 3, pp. 53-77 (Moodle) SHMA, Chapter 8 (first half), pp. 301-323.
Thu Apr 27 (Class 27) - Julian of Norwich, Showings (S), Revelation XIV, pp. 248-304. SHMA, Chapter 8 (second half), pp. 323-343.
Tue May 4th, 1pm Final Exam


flex-flow: row wrap
writing-mode: horizontal-tb;
flex-flow: column wrap
writing-mode: horizontal-tb;
flex-flow: row wrap-reverse
writing-mode: horizontal-tb;
flex-flow: column wrap
writing-mode: horizontal-tb;
flex-flow: row wrap
writing-mode: vertical-lr;
flex-flow: column wrap
writing-mode: vertical-lr;


Article Title
2019-12-03 11:02:03
#Tag-1
#Tag-2
#Tag-3
Section 1
This is a test. Letter A
is here.
This style is inspired by this website.
Subsection 1.1
This is a test code:
#include
int main()
{
return 0;
}
Subsection 1.2
This is a normal line.
This is a bold line.
This is a italic line.
Section 2
This is a test.
Section 3
This is a test link.
This is a test ordered list:
- item 1
- item 2
- item 3
This is a test unordered list:
- item 1
- item 2
- item 3
This is a test table:
| Column 1 | Column 2 |
|---|---|
| Cell 1 | Cell 2 |
| Cell 3 | Cell 4 |


This workshop is geared towards intermediate-level Python users. Attendees will need cell phone and a laptop with a working python environment.
We’ll assume you have a good basic familiarity with the language, and already have a good working environment setup.
We will be using Python 3.6, but any version after 3.5 will work as well.
We will be using a python cookie cutter to setup a basic template to start our project off with.
We’ll go through what aiohttp is, how to utilize it and start building our asynchronous web service.
We’ll talk about the benefits of setting up an asynchronous server including better metrics and logging.
We’ll be building an app akin to the Dial-A-Joke app built by Steve Wozniak. Our server will make calls to users who have signed up to receive jokes at scheduled times and tell them a joke using TTS, and it will also provide a basic interactive experience over the phone using the touchpad.
We’ll setup native asynchronous scheduling inside the service and let it run.
Workshop that goes through getting started with MicroPython, using the D1 mini as the hardware platform.
There is an initial setup part that covers installing drivers and connecting to boards REPL, usually about 15-20 minutes.
Matrix is an open standard for interoperable, decentralised, real-time communication over the Internet.
It can be used to power Instant Messaging, VoIP/WebRTC signalling, Internet of Things communication - or anywhere you need a standard HTTP API for publishing and subscribing to data whilst tracking the conversation history.
There are Python SDKs available for interfacing with Matrix as a client (that is, doing things a client application or bot would do, such as sending and receiving messages.)
Download the entire RoboFarm and RoboRecycling folders
Save in a folder where you can use Python and a Jupyter Notebook or upload to your Google Drive and run in Colab
To run Notebooks locally:
Comment out Google Colab specific instructions ie mounting a Google Drive
Adjust 'base_dir' to point to your location of the RoboFarm or RoboRecycling folder on your system.
Run notebook the requirements cell should install everything you need if you don't already have it eg Tensorflow
Make a check point so you can return to original version.
To run in Colab:
These notebooks should run on Colab without modifcation you may need to adjust "base_dir" to point to the correct location
Link to folder here:
Robo Farm
https://drive.google.com/drive/folders/1x4hxiDkYLmqQzikF6OZ6oFNLfvZROom2?usp=sharing
RoboRecycling
https://drive.google.com/open?id=13ymFwjEimJYmeqwzsG66yznIrSnhh-ty


Coffey v. Ripple Labs - an early legal analysis
June 8, 2018
I’m taking a break from our regular Solidity programming to take a close look at the securities litigation filed against Ripple Labs on May 3. Let’s look very closely at Plaintiff’s claim that XRP is a security, which exposes it to a broad array of regulatory and private legal actions.
Current Procedural Posture
First, the case was filed recently (ok, back in May, but in judicial time that’s pretty recent) in California State Court as a securities class action against Ripple and its CEO. Plaintiff lives in San Diego.
Less than a week ago, the defendants removed the case from state court to federal court in San Francisco. This is a simple and common defense maneuver. Defendants do it because it’s often thought, whether true or not, that federal court is less “plaintiff friendly.” There will likely be some objections from the plaintiffs to try to send it back to state court.
As I write this, this only pending matter in open court is a routine status conference to be held in September. The parties are probably planning or have already started discovery requests. Discovery is the phase of litigation where the parties get to demand documents and conduct depositions. It’s the phase where Michael Avenatti is making so much progress against Trump in the Stormy Daniels litigation.
Almost surely, the defense is planning a motion to dismiss or some other tactic to stop the litigation before it really starts.
Substantive Claims
It’s a thirty page complaint, so there’s a lot of ground to cover – both on the facts and the law. Some of the issues border on the salacious (allegations of bribes to Coinbase or fraudulently conflating sources of revenue, for example), some issues are legal technicalities (e.g., seeking class action status), and some issues raised are actually fairly interesting discussions of the blockchain technology for the court’s benefit.
I’m going to focus on the three pages where plaintiff’s counsel alleges Ripple’s coin (“XRP”) is a security.
If it’s a security, then Ripple needed to file a registration statement (expensive), provide extensive financial disclosures, and is subject to a whole host of securities laws and private litigation, such as this case.
The Howey Test
Whether a local snow cone business, financial services company, or blockchain startup needs to comply with complex securities laws (both state Blue Sky laws and/or federal securities laws) often turns on whether those companies are selling “securities.”
Lawyers and courts look to the seminal Securities and Exchange Commission v. W. J. Howey Co. case to guide them in the analysis of whether someone is, or is not, dealing in securities. When you’re selling stocks, the analysis is pretty cut and dried. But there are many cases where it isn’t quite so clear, especially with the recent way of initial coin offerings (“ICOs”).
Given all the buzz over blockchains in the past year, it’s understandable that the Internet has recently minted a massive number of new experts on the Howey test.
We spent a lot of time on Howey in my securities regulation class. W.J. Howey Co. was selling real estate based contracts giving buyers a share of a large farm, which the buyers then leased back to Howey to run its farming operations. Buyers hoped for large profits from Howey’s agricultural management skill and experience. The court concluded that Howey was dealing in securities because buyers invested money into an endeavor where Howey promised to generate profits for the buyers through its agricultural management.
While today’s Howey analysts focus on a mechanical four pronged test crafted by Justice Murphy in 1946, they miss that courts often look to the simpler policy behind the mechanical rule to help guide a decision. It’s a pretty simple policy: if you’re hoping someone else will take your money, pool it, and generate profits for you, then it’s very likely you’re buying a security that needs to be regulated to protect investors and create confidence in markets.
Plaintiff’s Application of Howey
But who cares what I say? I’m yet another Howey analyst, right?
Notwithstanding everything I wrote above, here are the four prongs of Howey, summarized: 1. an investment of money, 2. in a common enterprise, 3. with an expectation of profits, and 4. profits depends on defendant’s management capabilities.
And here’s how the Plaintiff argued Howey applies in the Ripple case (keep in mind that, new facts will emerge from discovery to either strengthen or weaken the arguments):
First, XRP buyers invested money. This one is kind of simple. To buy XRP you either have to exchange it for some other cryptocurrency or put real cash into it. Either way, it’s money.
Second, investors are buying into a common enterprise in that XRP is fungible and, importantly, profits are intertwined with Ripple Lab because, as Ripple says, it “sells XRP to fund its operations and promote the network.”
Third, XRP buyers had a reasonable expectation of profits. This seems pretty obvious. Why else would you buy XRP? Plaintiff points out a number of facts to establish this element but the strongest might be that defendants “publicly touted XRP’s price performance on numerous occasions.”
Fourth, the profits were dependent solely on Ripple’s technical, entrepreneurial, and managerial efforts. Plaintiff points out that Ripple itself stated that it was selling XRP for the purpose of funding “its operation and [to] promote the network.”
What Happens Next
In litigation the plaintiff gets to make the opening argument, in the form of the complaint we just analyzed. Without a counter argument, it seems pretty convincing. Ripple and Garlinghouse will need to eventually answer the complaint, in which they may or may not give us a counter argument – we’ll see!
If they file a motion to dismiss, they’ll need to explain why Plaintiff’s analysis of Howey is wrong, which is be very interesting to read.
Stay tuned and I’ll provide updates as the case progresses.


Exercise Calculator
How can you burn off some of those extra calories before they turn into extra pounds? After thinking about a particular dish you savored, try our "Exercise Calculator" to see how many calories you expend doing your favorite exercise or activity.
BMI Calculator
Calculates Your current BMI
Nutrition Calculator
calculates the total calories consumed
Exercise Timer
Calculates the time while exercising
Fitness
This Website supports fitness for every individual


Home
Search
Map
Event
Contact
Which kind of event are you looking for ?
Tell us more about what kind of event you would like to attempt.
Search
Output
Founded events...


We Serve The Best Quality Food
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Fuga debitis deleniti dolores cupiditate quia reiciendis, obcaecati facere. Amet et enim itaque sapiente. Culpa, incidunt,p eveniet.
Collaboratively redefine fully tested processes and extensible partnerships. Professionally exploit team building opportunities rather than client-focused e-markets. Objectively deliver functionalized platforms through client-centric.
Our Services
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Quae veniam quam incidunt eos eaque esse ducimus dolore, velit, laborum dignissimos?
#1 Recipes Story Website
Compellingly supply mission-critical imperatives for functional meta-services. Completely parallel task distributed materials.
All Type Cuisines
Continually iterate resource-leveling applications through next-generation manufactured products. Quickly transform technically sound.
Detailed Description Menu
Synergistically conceptualize e-business services before cross-unit methods of empowerment. Continually target collaborative.
To get the best results, you must talk to your Vegetables.


scrum
There are many issue tracking and “agile” tools in the wild. In many cases these tools are actually wild in one or more of the following ways:
-
complexity
-
cost
-
ignorant simplicity
-
integration
These tools usually sit further away from where the end result is happening in code.
GitHub provides simple and lightweight Issue Tracking and Project Management but lacks useful reporting that helps a Scrum team inspect and adapt.
If you are already using GitHub why introduce cognitive complexity by having another tool for project management. Keep everything in one place - the code, the issues, the wiki, the reporting.


In my short time in Moringa, I have been able to learn
the basics of HTML and CSS .
With this knowledge I have been able
to start on the following projects
My second project just about making a simple website which is locally hosted
language HTML
The branching test project is experimenting on forking, branching and cloning.
language HTML


| < August 2015 > | |||||||
|---|---|---|---|---|---|---|---|
| Su | M | T | W | Th | F | Sa | |
| 1 | |||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 | |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 | |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 | |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 | |
| 30 | 31 |
So what is Rails. I could give you a broken, terrible explanation, or I could just give you an official description:
"Rails is a web application development framework written in the Ruby language. It is designed to make programming web applications easier by making assumptions about what every developer needs to get started. It allows you to write less code while accomplishing more than many other languages and frameworks. Experienced Rails developers also report that it makes web application development more fun."
Oh boy does that sound great or what folks. It's also opensource, which is nice. Rails aims to make life easier when it comes to web development. It will link a ruby file and corresponding table from a database, while providing a basic development environment.
Rails seems to follow two main principles, Don't Repeat Yourself (DRY), and Convention over Configuration (CoC). DRY is pretty straight forward, repetition is frowned upon. This is mostly for the sake of clarity. CoC essentially allows you to think less. Rails likes to do things it's own way, and only asks for specifics when you deviate from these norms. The idea that you need to learn these norms in the first place feels a bit annoying, but I suppose in the long run it would make things easier.


I am an aspiring Linux System Administrator and Developer.
A dynamic, confident, responsible and focused individual with over 10 years of accumulated technical skills. Proficient in programming and system administration and able to adapt to a diverse environment. A quick learner and a well-informed and well-read individual who always exceeds expectations with excellent outcomes. A passionate individual with strong determination and a drive to widen his knowledge in the tech industry.
Currently looking to take on new clients in the field of system administration and DevOps.
Also availiable for a full time System Administration or Junior DevOps position.
Deciding it was time for a change, I took my hobby of software development and Linux to the next level.
I started my career as a technician, working both independently and for companies.
Python
Ruby
Bash
HTML
Javascript
Ansible
Docker
LXC/LXD
Vagrant
YAML
I love animals and own a delightful dog. I enjoy playing video games (a console guy).
I like dining out and trying different types of cuisines.


Whether its a renovation or new build, we approach every project in the same manner. It starts with an inquiry from a phone call or email. From there, we offer a no-obligation meeting which is meant to communicate the general idea of a project. We thoroughly enjoy this part of the process. It gives us a sense of the clients specific needs and interests so we can build to suite their lifestyle.
In our first meeting, we consult with the client about their specific project. We figure out what needs to be done, and how it should be executed. We run through the scope of the project with the client to ensure we are on the same page.
With this information, we move to the design phase. This is where we share ideas with our architects and designers to plan the project. We narrow in on the structural and aesthetic properties to create a realistic render. This is where we decide how tall that wall will be, what kind of flooring in the kitchen, or type of tile in the bathroom. This phase is crucially important for a successful build.
Once we have enough information to properly evaluate the project, we can provide an estimate. This shows the detailed scope of work, the cost, and a discussion about any specific issues that need to be addressed before we move forward. Once these things are in order—and it’s clear that our plan is aligned with building codes and city by-law—we apply for permits.
Upon approval, we are ready to start. By this time, we have contractors scheduled so we can break ground or start demolition. This is when the plan turns into reality and we begin the real work. JB Builders’ role is to manage the building process, coordinate subcontractors, and ensure things are built according to plan. We are accountable for overseeing the logistics of the entire build.
Finally, and most importantly, we are nothing without our clients. We take pride in being transparent and honest at all costs. It’s our moral imperative, and the basis of our philosophy. We are completely open and accessible to the client, and they are totally informed along the way. We are in constant communication, providing budget and schedule updates as we move through the building process. We have a system and we stick to it. This is how we deliver on time and within budget.
These are the first steps in approaching a custom build or renovation with JB Builders.


" type="video/mp4">
TRAVIS NTHIGA
Founder of T-customs,Concept Designer, Sketch Artist, Craftsman/Builder, UI/UX Developer


CGLsim1D.m
Matlab program that simulates the evolution of the one-dimensional CGL equation using
pseudo-spectral code for the derivatives terms and exponential time-stepping
for the time integration.
CGLsim2D.m
Matlab program that simulates the evolution of the two-dimensional CGL equation using
pseudo-spectral code for the derivatives terms and exponential time-stepping
for the time integration. Here, a square container is assumed.
http://www.cmp.caltech.edu/~mcc/STChaos/
Java simulator (with available source code) for the
modified Ginzburg-Landau equation
as well as the Bar-Eiswirth model and coupled quadratic maps.


Firefighters battling 3-alarm fire at residential building in Elizabeth, New Jersey
by WABCFirefighters are battling a 3-alarm fire at a residential building in New Jersey.
The fire has burned through the roof of a two-story building on Wesfield Avenue.
So far there are no reports of injuries.
People have been evacuated from the building and other nearby buildings as a precaution.
Stay with abc7NY for the latest on this developing story.


If you are already using packages and blueprints for your application (Modular Applications with Blueprints) there are a couple of really nice ways to further improve the experience. A common pattern is creating the application object when the blueprint is imported. But if you move the creation of this object, into a function, you can then create multiple instances of this and later.
So why would you want to do this?
So how would you then actually implement that?
The idea is to set up the application in a function. Like this:
def create_app(config_filename):
app = Flask(__name__)
app.config.from_pyfile(config_filename)
from yourapplication.views.admin import admin
from yourapplication.views.frontend import frontend
app.register_blueprint(admin)
app.register_blueprint(frontend)
return app
The downside is that you cannot use the application object in the blueprints at import time. You can however use it from within a request. How do you get access to the application with the config? Use current_app:
from flask import current_app, Blueprint, render_template
admin = Blueprint('admin', __name__, url_prefix='/admin')
@admin.route('/')
def index():
return render_template(current_app.config['INDEX_TEMPLATE'])
Here we look up the name of a template in the config.
So to use such an application you then have to create the application first. Here an example run.py file that runs such an application:
from yourapplication import create_app
app = create_app('/path/to/config.cfg')
app.run()
The factory function from above is not very clever so far, you can improve it. The following changes are straightforward and possible:


This is just a test case for the html compressor. A comment after this Post comment.
Spaces removed between brs above


java.util.Objects.equals()
a != null && a.equals(b)
This inspection only reports if the project or module is configured to use a language level of 7 or higher.
New in 15


The awesome lead of this project!
Part of our front-end team!
Part of the marketing page team!
Our lonewolf on the back-end!


| Name | Description |
| \Tuxxedo\Debug\Debugable | Allows an object to dispatch its current state to be used in things like |
| \Tuxxedo\Design\EventCaller | Implements event calling hooks for a class |
Generated by Tuxxedo Engine 1.3.0 "Intergalactic" Alpha 1 (experimental).


Main figures
- [Figure 1. Skewed distribution of UMIs leads to increased number of UMI collisions.]
- A. Skewness of UMI distribution
- B. Uneven nucleotide frequencies
- C. Estimated number of collisions
- Figure 2. Comparison of UMI collision and sequencing error correction methods.
- Figure 3. Correcting for Cellular Barcode errors.
- A. Origin of background cells
- [B. Number of equidistant adjacent CBs]
- C. Increase in #molecules per cell


@import fr.gospeak.core.domain.CommonCfp @import fr.gospeak.libs.scalautils.domain.Page @import fr.gospeak.web.domain.Breadcrumb @import fr.gospeak.web.pages.published.cfps.routes.CfpCtrl @import fr.gospeak.web.pages.published.partials.html.{cfpItem, container_theme} @import fr.gospeak.web.utils.Formats @import fr.gospeak.web.utils.UserAwareReq @(cfps: Page[CommonCfp])(b: Breadcrumb)(implicit req: UserAwareReq[AnyContent]) @container_theme("CFPs - Gospeak", b)() {
Have something interesting to share? Find a corresponding CFP and propose a talk!
Afraid of speaking? Take a look at theses getting started and helpful articles and testimonials.
A Conference is missing? You can add it here


4 writes to IsReservedMember
System.Management.Automation (4)
engine\MshMemberInfo.cs (4)
209
destiny.
IsReservedMember
= IsReservedMember;
4408
IsReservedMember
= true
4442
IsReservedMember
= true
4472
IsReservedMember
= true
2 references to IsReservedMember
System.Management.Automation (2)
engine\MshMemberInfo.cs (2)
209
destiny.IsReservedMember =
IsReservedMember
;
4583
if (_memberSetOwner != null && _memberSetOwner.
IsReservedMember
)


Space-Filling Designs and Uniformity Criteria.
| Version: | 1.8 |
| Depends: | R (≥ 2.10) |
| Suggests: | rgl, randtoolbox, lattice |
| Published: | 2018-10-29 |
| Author: | Jessica Franco, Delphine Dupuy, Olivier Roustant, Patrice Kiener, Guillaume Damblin and Bertrand Iooss. |
| Maintainer: | Celine Helbert <Celine.Helbert at ec-lyon.fr> |
| License: | GPL-3 |
| URL: | http://dice.emse.fr/ |
| NeedsCompilation: | yes |
| Citation: | DiceDesign citation info |
| Materials: | NEWS |
| In views: | ExperimentalDesign |
| CRAN checks: | DiceDesign results |
| Reference manual: | DiceDesign.pdf |
| Package source: | DiceDesign_1.8.tar.gz |
| Windows binaries: | r-devel: DiceDesign_1.8.zip, r-release: DiceDesign_1.8.zip, r-oldrel: DiceDesign_1.8.zip |
| OS X binaries: | r-release: DiceDesign_1.8.tgz, r-oldrel: DiceDesign_1.8.tgz |
| Old sources: | DiceDesign archive |
| Reverse depends: | ATmet |
| Reverse imports: | CaliCo, DiceOptim, DoE.wrapper, GPareto, GPGame, hetGP, minimaxdesign |
| Reverse suggests: | kergp, lineqGPR, mistat, pGPx, sensitivity |
Please use the canonical form https://CRAN.R-project.org/package=DiceDesign to link to this page.


These examples have moved to storybook
https://solid.github.io/solid-ui/examples/storybook/?path=/docs/notepad--notepad


Introduction |
Documentation |
Downloads |
Forum |
Credits |
|
Copyright (c) 2003 Ronan Collobert (IDIAP, Trebolloc & Co)
Copyright (c) 2003 Samy Bengio (IDIAP) Copyright (c) 2003 Johnny Mariéthoz (IDIAP) All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |


As an Embrace alumni, I have a deep appreciation for design, design thinking, and the power of form in helping realize a product’s value. Upon arriving at Stanford, my buddy Rajan Patel shared with me how transformative Dave Beach, the Product Realization Lab, and specifically the “Introduction to Machining” course (ME203) had been for him. I was hooked and knew I had to take the course the second I got to campus.
ME203 is an intensive 10-week course: in the first two weeks, all students are taught how to mill, lathe, use a foundry (sandcasting), and weld … ! We use that to build a magnifying lens and a plaque of the Stanford crest, and have to finish them professionally. Once that’s been completed, all students undertake a project of their choosing over the next ~6 weeks. I decided to build a pasta holder for my girlfriend, Andrea.
Background
I came up with this product idea before Andrea had moved back to the United States. We met in Bangalore, and I came back to start school 7 months before she got to the Bay Area. Due to terrible timing, I ended up choosing classes that would take 70-80 hours a week just as she arrived. I thought that if I could make something *for* her about her *favorite food*, I might be able to get away with being so absent. :)
A prompt for the product is to determine a “critical part.” This is the design attribute in the product that everything is built around and must be successful. I decided that I would have two - since Andrea was traveling so much, I wanted to index on durability and freshness. I chose polycarbonate and aluminum as materials that would support that.
Machining on a lathe
Every part I built was done on a lathe. I was doing some interesting things - for example, working on both ends of a 12’-long 1/8”-thick piece of polycarbonate - that required developing some savvy and using niche parts like a center pivot and creating extra pieces as reinforcement so that the part wouldn’t deform the plastic.
Prototyping, CAD, and BOMs
Personally, my exploration into prototyping didn’t extend far beyond looking at different threading types. This was a mistake as, had I prototyped, there would have been several things that I did differently in my final product. For example - my cap is solid aluminum, and it gives the product a top-heavy feel. I wanted it to have a “light, California feel.” This is why I used solid, natural materials and gave them a clean finish instead of doing anything extra. With some prototyping, I would have cut some more material out of my lid to give it the balance I was looking for.
An endless series of broken things
My design was a relatively simple concept, and I expected that I would be able to build it quickly and focus on design extensions – such as using a laser cutter or adding steel plating fixtures. Then, my first 4 aluminum ribbons (.050” thick) broke – and I lost 16 hours of lab time. Two of them broke when parting, and in one instance, the parting tool broke!
- The parting tool must be perpendicular to the surface, it should be set off of the
- Each time the part is removed and placed again on the lathe, a new center point is established – never finish working when you are .030” from finishing your cut.
- If you want it done right – for the circles to be perfectly concentric – don’t take the product off the late.
- If you want it to be okay, make sure to use the dial calipers to ensure circularity.
I now can make this part in 2 hours – but it actually took me 18 hours to get there. And if I had made the part perfectly the first time, I probably wouldn’t have learned any of this (because I wouldn’t have realized what worked for me!).
The final product!
Once I had all of my pieces finished, I needed to assemble them. I had designed a .0050” ribbon of aluminum to fit over a polycarbonate ridge. They had a tolerance overlap of .0005” so that friction would hold them together. I pushed them together on an arbor press and breathed a HUGE sigh of relief when it slipped on without breaking. I had spent so much time, and broken so many parts, that I think I might have cried if this didn’t work.
I also added a “reveal” between where the aluminum and the polycarb met on the outside of the product. This was done so that when a user runs their finger along the interface, it’s impossible to tell if there might be some inconsistency in the shapes of the two pieces.
Lessons learned
ME203 was a great experience for me, and a jumping point for being able to move into increasingly more technical projects. Here were a few of my big lessons:
- I love products. Growing up, my family was actually known for its design abilities. My grandfather was a pilot; my dad and his brothers raced sprint cars on open-wheel dirt tracks. They were known for getting more out of cheaper products, because they built their own cars. I grew up on the smell of cut metal and grease. My brother worked in the pit crew for an IndyCar. In a small way, being a part of this class has brought me closer to my family. It’s been fun getting to share with them the experience of the class, and the joys and frustrations of working with the materials to realize a concept.
- Prototyping only works if you know what you’re testing. In building the product, I made many decisions on the fly – I was balancing cost, available products, and anticipated aesthetics. Initially, I thought I didn’t need to prototype because I had one joining function (threading) and I knew what the product would look like aesthetically. At the end, I realized that I could have explored and experimented with all of these factors had I known to look for them in my prototypes.
- “You have to ‘go’ to know.” – Tony Scott. Tony is an older GSB alum who has credited his career to his willingness to use new experiences as a learning process. I am glad to have taken this course as I wouldn’t have had the ability to articulate these learnings any other way.
-
Production & design are both art and science. Before taking this course, I thought of manufacturing as an exact science. One knows what their technical specifications are, and then they press a button and many parts are produced in cookie cutter fashion. I’m being slightly simplistic, but this is a close approximation.
That’s not the case. Parts wear; people get tired. Cuts slip. Press fits change between materials. Many joining parts are guided by “what feels right.” Designs change as one considers cost and “what’s available.” Even though the process involves a machine, it is much less mechanical than one might think from the outside.
It’s a bit funny/silly, but I also got to make a summary video of the project in lieu of being present for the final. It says much of the things covered in this post, and can be found here.


|
Timer
The Timer
function returns the number of elapsed seconds since the function was
last called and first called.
|
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:Timer ID
::
:: By: Ritchie Lawrence, 2002-10-10. Version 1.1
:: Updated 2007-10-31 - thanks to Fabricio and Darren
::
:: Func: Returns number of seconds elapsed since the function was last
:: called
and first called. For NT4/2000/XP/2003.
::
:: Args: %1 (by ref) The first time this function is called, this
variable
:: is
initialised to '<last> <first>
<init>' where <last> and
<first>
:: are zero
and <init> is the number of elapsed seconds since
::
1970-01-01
00:00:00. This value is used by subsequent calls to
::
determine
the elapsed number of seconds since the last call
::
(<last>)
and the first call (<first>).
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
setlocal ENABLEEXTENSIONS&call set ID=%%%1%%
set t=2&if "%date%z" LSS "A" set t=1
for /f "skip=1 tokens=2-4 delims=(-)" %%a in ('echo/^|date') do (
for /f "tokens=%t%-4 delims=.-/ " %%d in ('date/t')
do (
set %%a=%%d&set
%%b=%%e&set %%c=%%f))
for /f "tokens=5-7 delims=:. " %%a in ('echo/^|time') do (
set hh=%%a&set nn=%%b&set ss=%%c)
set /a dd=100%dd%%%100,mm=100%mm%%%100
set /a z=14-mm,z/=12,y=yy+4800-z,m=mm+12*z-3,j=153*m+2
set /a j=j/5+dd+y*365+y/4-y/100+y/400-2472633
set /a hh=100%hh%%%100,nn=100%nn%%%100,ss=100%ss%%%100
set /a j=j*86400+hh*3600+nn*60+ss
for /f "tokens=1-3 delims= " %%a in ('echo/%ID%') do (
set l=%%a&set f=%%b&set c=%%c)
if {%c%}=={} endlocal&set %1=0 0 %j%&goto :EOF
set /a l=j-c-f,f+=l
endlocal&set %1=%l% %f% %c%&goto :EOF
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
|
|
Parameters
%1 (by ref) The first time this
function is called, this variable is initialised to
'<last> <first> <init>' where
<last> and <first> are zero and
<init> is the number of elapsed seconds since 1970-01-01
00:00:00. This value is used by subsequent calls to determine the
elapsed number of seconds since the last call (<last>)
and the first call (<first>).
Return Values
See parameters above.
Example
@echo off & setlocal
set var=
call :Timer var
call :show
::wait about 3 seconds
ping <IP_ADDRESS> -n 4 >nul
call :Timer var
call :show
::wait about 7 seconds
ping <IP_ADDRESS> -n 8 >nul
call :Timer var
call :show
goto :EOF
:show
for /f "tokens=1-2 delims= " %%a in ('echo/%var%') do (
echo/Seconds since last call: %%a, seconds since
first call: %%b
)
goto :EOF
Remarks
The first time the function is called, it should be
passed an undefined variable.
Multiple timers can be used in parallel; just use a
different variable name for each instance. See the function's header
for more information.
Update: Corrected an error in the penultimate statement
(it used to read: set /a l=j-c-l,f+=l) - thank you Fabricio and Darren
for spotting this error.
See Also
Sleep
|


Fake news is one type of “misinformation” or disinformation.” However, much of the “news” can be simply misleading. Some people or news outlets convey misleading quantitative information unconsciously; some do it deliberately. Researchers often present numerical results, and conclusions based on those results, without also putting forth enough effort to calculate and report the uncertainties and inaccuracies in those results. Perhaps more insidious, many professionals construct quantitative information to serve a pre-disposition, a political goal, or a business objective. What is an individual reader or consumer of this information to do?
in-context


Notebooks
Story: Food eaten by the !kun
Food eaten by the !kun
Title
Food eaten by the !kun
Collection
Summary
The names and descriptions of some plants and animals eaten in !nanni and Tamme's country. It includes notes on whether the food is eaten raw or cooked, and what food is found in the Damara's country.
Comments
1) See also What !nanni's father told him (what to eat and avoid) and Elephants (eating their hearts) and Things eaten by the !kun and Animals eaten by the !kun, 2) This story is found in Book XI & XII-4
Contributors
Date
10 – 11 January 1880
Categories
Custom and daily life, Plants and animals
Story Pages
9228-9229


Rare's next Xbox game is pure 'Princess Mononoke'
'Everwild' is a gorgeous new open-world adventure .
by Devindra HardawarIf Sea of Thieves isn't your bag, how about a sumptuous cel-shaded game from Rare that looks like a lost Miyazaki film? The Microsoft studio announced Everwild today during the XO19 Inside Xbox presentation, and while there aren't many details to run with, it certainly looks intriguing. The trailer shows us a gorgeous world filled with fantasy creatures and human-like characters tentatively co-existing, while something nefarious brews in darkness. Rare says it's an open-world title that it'll be developing alongside Sea of Thieves, so don't expect it to arrive anytime soon.


|
the Internet Engineering Task Force (IETF) the goal of the IETF is to make the Internet work better. the mission of the IETF is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet. Newcomers to the IETF should start here.
the Internet Engineering Task Force (IETF) is an organized activity of the Internet Society (ISOC). ISOC is a non-profit organization founded in 1992 to provide leadership in Internet-related standards, education, and policy. It is dedicated to ensuring the open development, evolution and use of the Internet for the benefit of people throughout the world. See: http://www.isoc.org/ | ||||||||||||||||||||||||||||


Girl Develop It is here to provide affordable and accessible programs to learn software through mentorship and hands-on instruction.
Some "rules"
Source: WebAIM Screen Reader Survey, February 2014 opens in a new window
Semantic structure is one of the most important usability features for screen reader users, as it helps them more easily understand and navigate the page structure. Headings also help all your users can and understand content. Read more about headings opens in a new window.
// Headings should not skip levels until h1-h4 have been established

Most important

Next most important

Third most important

Other heading

Tip: use the Firefox Web Developer Toolbar to inspect headings. Look under Information > View Document Outline.
The HTML5 Document Outline
opens in a new window
by the Paciello Group
Label
<input type="text" id="name-field" name="name-field">
Label
<input type="text" id="name-field"
name="name-field" placeholder="Type your name" />
Goofy page

Disney.com

opens in a new window

For links that open in new windows, an offscreen span
inside the link is most reliable for screen readers, but title=""
can also be used.
The tabindex attribute explicitly defines the tab order for focusable elements (typically links and form controls) within a page. It can be used to define whether elements should be focusable. (WebAIM opens in a new window)

Focusable Heading

Link focusable only by script

Div tabbable in new order

Note: tabindex
values higher than 0 require managing the entire page's tab order. Use with caution!
/* Hide only visually, but have it available for screenreaders.
Copied from HTML5 Boilerplate*/
.visuallyhidden {
border: 0;
clip: rect(0 0 0 0);
height: 1px;
margin: -1px;
overflow: hidden;
padding: 0;
position: absolute;
width: 1px;
}
.reallyHidden {
display: none;
visibility: hidden;
}
.notHidden {
display: block;
visibility: visible;
}
Explore keyboard navigation with content that is hidden and offscreen
What is WAI-ARIA, what does it do for me, and what not? opens in a new window
What does this thing do?
<form role="search">
The current condition of this particular thing
<input aria-disabled="true">
The nature of the thing
<input aria-required="true">


{{ option.description }}
Enter search text:
-- OR --
Select a nutrient:
Returned: {{foodItems.length}} food item(s).
{{food.description}}
Choose amount:
Choose Unit of Measure:


public class Delta extends AbstractPair<java.lang.Integer,java.lang.Integer> implements java.lang.Comparable<Delta>
| Modifier and Type | Field and Description |
|---|---|
private java.lang.Double |
_euclidian |
private java.lang.Integer |
_manhattan |
_first, _hashCode, _second
| Constructor and Description |
|---|
Delta(Delta other)
Copy-Constructor.
|
Delta(Direction direction)
Constructs a Delta from a Direction.
|
Delta(int x,
int y)
Constructs a new Delta given the delta-x and delta-y.
|
| Modifier and Type | Method and Description |
|---|---|
private void |
_invalidate()
Invalidates the cached distances.
|
int |
compareTo(Delta other)
Compares two Deltas by their Manhattan-distance.
|
static Delta |
Down()
Factory-function to create a downward Delta.
|
double |
euclidian() |
Delta |
invert() |
static Delta |
Left()
Factory-function to create a leftward Delta.
|
int |
manhattan() |
static Delta |
Right()
Factory-function to create a rightward Delta.
|
static Delta |
Stay()
Factory-function to create the Delta to stay,
i.e.
|
static Delta |
Up()
Factory-function to create an upward Delta.
|
int |
x() |
void |
x(int x)
Sets the x-component of the Delta.
|
int |
y() |
void |
y(int y)
Sets the y-component of the Delta.
|
compareTo, equals, first, first, hashCode, second, second, toString, toStringPlain
private java.lang.Integer _manhattan
private java.lang.Double _euclidian
public Delta(int x, int y)
x
- The delta for the x-component.y
- The delta for the y-component.public Delta(Delta other)
other
- The other Delta to copy this one from.public Delta(Direction direction)
direction
- The direction to create this Delta with.public static Delta Up()
public static Delta Down()
public static Delta Left()
public static Delta Right()
public static Delta Stay()
public int x()
public void x(int x)
x
- The new x-component for the Delta.public int y()
public void y(int y)
y
- The new y-component for the Delta.public double euclidian()
public int manhattan()
public Delta invert()
public int compareTo(Delta other)
compareTo
in interface java.lang.Comparable<Delta>
other
- The other Delta to compare this one with.private void _invalidate()


Open-minded
Every option should be explored and tried no matter how unpredictable, impossible, insane or ridiculous does it looks or sound.
Every option should be explored and tried no matter how unpredictable, impossible, insane or ridiculous does it looks or sound.
Brainstorming, idea generation, playing sessions, note taking. You think you used everything? We will challenge your mind and its abilities to the limits.
Our methods and ideas are are not written or following any books, curriculums or rules. We consider ourselves rebels and we are proud of it.
Every project with innovation as a goal requires smart approach. Identify real problem first and look for the smartest and simplest solution later.
Tire Technology Expo has grown in strength and stature every year since it was started in Europe 15 years ago. Visitors and exhibitors to the conference and exhibition staged in February 2014 universally praised it as the 'world's leading tire design and tire manufacturing event', noting in particular the outstanding quality of the conference papers and speakers, and the comprehensive extent of machinery manufacturers and suppliers who exhibited at the event.
more...Meteorological Technology World Expo is a truly international exhibition of the very latest climate, weather and hydro - meteorological forecasting, measurement and analysis technologies and service providers for a global community of key decision makers within the aviation industry, shipping companies, marine / port installations, airports, military operations, off-shore exploration companies, wind farm operators, met offices, agriculture operations and research institutes.
more...See live demos, listen to case studies, speak with Wearable Tech Experts The first Wearable Tech Expo in Tokyo 2014. Key players from Japan, America and Europe announced their new products and attracted attention from all over the world. The next Wearable Tech Expo in Tokyo will be doubling in size and include Robotics and IoT. The main players in the wearable industry, human factor engineers, brain scientists, media providers and creators will discuss the future of wearable technology!
more...Space Tech Expo is the West Coast's premier B2B space event for spacecraft, satellite, launch vehicle and space-related technologies. Taking place in Long Beach, the Space Tech Expo exhibition and conference brings together global decision-makers involved in the design, build and testing of spacecraft, satellite, launch vehicle and space-related technologies. Leading the West Coast space and satellite industry, Space Tech Expo is where end-users connect with solution providers.
more...People from Google approached us this January with offer to create new neural network for whole Google's ecosystem. This idea was very interesting and looked almost impossible at first glance. However, our engineers proved their expertise and built amazing autonomous platform. more...
For a years, since founding days of a company, Apple always worked with its own operating system. In October, this was about to change. Our company got chance to rewrite the history by creating brand new OS for Apple. It was very difficult and all our employees worked hard every day. more...
Intel has been manufacturing company for many years. They always used the latest technologies to achieve the best results with lowest costs. However, this was not enough. Intel decided to offer us something that could disrupt whole technology sector. more...
Our goal is to give our customers the best solutions in highest aquality. Our employees strive for excellence and work hard to achieve it. Everything must work and be reliable. Great design must be both, aesthetic and functional. Product or service that pass these conditions will be everlasting.
Our mantra is to create new paths. We are not interested in copying others because we know, that if you want to succeed, you have to be different, unique. Our customers know that we create unique products and experience for them. This is the best way to differentiate us and our brand from the noise on market. Unique, different and proud.


Tools
Json reformat
Does some basic reformatting of the json keys on the PA folder.
Unit explorer
Loads unit data, searchable data.
Unit explorer table
Loads unit data, searchable data. Displayed as a vertical table; good for large screens and comparing units.


When programming in R there are two fundamental operations we perform on our data. We view
some piece of the data, or we set
some piece of the data to a particular value. These two operations are so fundamental that R comes with many pairs of view
and set
functions. A classic example would be names
. Names can be viewed names(x)
and set names(x) <- new_names
. Lenses are an extension of the idea of view
/set
pairs, offering the following advantages:
set
anything you can view
)set
/view
nested data)In this document, we’ll see a few common data manipulation operations and how they can be improved with lenses.
Let’s take the iris data set for example, we want to perform some manipulations on it.
head(iris)
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species
#> 1 5.1 3.5 1.4 0.2 setosa
#> 2 4.9 3.0 1.4 0.2 setosa
#> 3 4.7 3.2 1.3 0.2 setosa
#> 4 4.6 3.1 1.5 0.2 setosa
#> 5 5.0 3.6 1.4 0.2 setosa
#> 6 5.4 3.9 1.7 0.4 setosa
We’re curious about the value of the 3rd element of the Sepal.Length
column. Using base R we can view
it with:
iris$Sepal.Length[3]
#> [1] 4.7
we can update (set) the value by assigning into it:
iris$Sepal.Length[3] <- 100
head(iris, 3)
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species
#> 1 5.1 3.5 1.4 0.2 setosa
#> 2 4.9 3.0 1.4 0.2 setosa
#> 3 100.0 3.2 1.3 0.2 setosa
and we can perform some operation to update it:
iris$Sepal.Length[3] <- log(iris$Sepal.Length[3])
This works well, however, there are some problems.
The first problem comes with having our view
and set
functions separate.  Here we see Sepal.Length
with the third element replaced, but where did the rest of iris
go! So we lose information when we pipe from a view
to a set
.
 It has the same problem above.
This is a failure of “bidirectionality”, once you’ve chosen to use a view
function, or a set
function, you are locked into that direction.
Lack of composability and bidirectionality means that you frequently have to duplicate your code. For example, if you want to apply an operation to the third element of “Sepal.Length”, you need to specify the chain of accessors twice, once in view
mode, and once in set
mode, making your code messy and cumbersome:
iris$Sepal.Length[3] <- iris$Sepal.Length[3] * 2
head(iris, 3)
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species
#> 1 5.10000 3.5 1.4 0.2 setosa
#> 2 4.90000 3.0 1.4 0.2 setosa
#> 3 9.21034 3.2 1.3 0.2 setosa
We can fix both of these problems by using lenses.
Lenses give you all the power of R’s view
and set
functions plus the advantages noted above. Especially important are the composition and bidirectionality features. Each lens can be used with the view
, and set
functions.
Let’s revisit the operations we performed above using lenses.
The first thing we will do is construct a lens into the third element of the Sepal.Length
component of a structure:
In the above code we’re creating two lenses, one into Sepal.Length
and another into element 3, using the index
function. We’re then composing these two lenses with %.%
producing a new lens into our element of interest.
Note that this lens has no idea we’re going to apply it to iris
. Lenses are constructed without knowing what data they will be applied to.
Now that we have a lens into the third element of Sepal.Length
, we can examine the appropriate element of the iris
dataset with the view
function:
iris %>% view(sepal_length3)
#> [1] 9.21034
We can update this element with the set
function:
iris %>% set(sepal_length3, 50) %>% head(3)
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species
#> 1 5.1 3.5 1.4 0.2 setosa
#> 2 4.9 3.0 1.4 0.2 setosa
#> 3 50.0 3.2 1.3 0.2 setosa
And we can apply a function to change the data. To do this we can apply a function over
the lens:
iris %>% over(sepal_length3, log) %>% head(3)
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species
#> 1 5.100000 3.5 1.4 0.2 setosa
#> 2 4.900000 3.0 1.4 0.2 setosa
#> 3 2.220327 3.2 1.3 0.2 setosa
Note that we never had to respecify what subpart we wanted, the lens kept track for us. We saw that the same lens can be used to both view
and set
, and that they can be composed easily with %.%
.
Now you have seen the main lens verbs and operations
view
: see the subpart of an object a lens is focussed on.set
: set the subpart to a particular value, then return the whole object with the subpart updated.over
: apply a function to the subpart, then return the whole object with the subpart updated.%.%
: compose two lenses to focus on a subpart of a subpart.Now if all lenses had to offer was more composable indexing of vectors, you might not be interested in integrating them into your workflows. But lenses can do a lot more than just pick and set elements in vectors.
For example, this package provides lens-ified version of dplyr::select
. Unlike select
, select_l
is bidirectional. This means you can set
the results of your selection.
let’s select columns between Sepal.Width
and Petal.Width
and increment them by 10:
iris %>%
over(select_l(Sepal.Width:Petal.Width)
, ~ . + 10
) %>%
head(3)
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species
#> 1 5.10000 13.5 11.4 10.2 setosa
#> 2 4.90000 13.0 11.4 10.2 setosa
#> 3 9.21034 13.2 11.3 10.2 setosa
Not only does select_l
create the appropriate lens for you with dplyr::select
style column references, but over
allows us to declare anonymous functions like in purrr
.
At this point I can imagine you saying, all this is very clear, but what good is it, I have mutate
. Well that is a good point. It is hard to beat the convenience of mutate
. However, select_l
has an advantage, it can be used on any named object:
You can use it with vectors, lists, data.frames, etc.
If select_l
isn’t enticing enough, have you ever wanted to set
or modify the results of a filter
? This is not super easy to do in the dplyr
universe. But our lens
ified filter
, filter_l
does this with ease.
Let’s set all “Sepal” columns where the row number is less than three to zero. And for fun let’s also change the column names to all upper case:
library(dplyr)
iris %>%
mutate(row_num = seq_len(n())) %>%
set(filter_l(row_num < 3) %.%
select_l(matches("Sepal"))
, 0) %>%
over(names_l, toupper) %>%
head(3)
#> SEPAL.LENGTH SEPAL.WIDTH PETAL.LENGTH PETAL.WIDTH SPECIES ROW_NUM
#> 1 0.00000 0.0 1.4 0.2 setosa 1
#> 2 0.00000 0.0 1.4 0.2 setosa 2
#> 3 9.21034 3.2 1.3 0.2 setosa 3
You can even use mutate over
your filter_l
iris %>%
mutate(row_num = seq_len(n())) %>%
over(filter_l(row_num < 3)
, ~ mutate(., Sepal.Length = 0)) %>%
head(3)
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species row_num
#> 1 0.00000 3.5 1.4 0.2 setosa 1
#> 2 0.00000 3.0 1.4 0.2 setosa 2
#> 3 9.21034 3.2 1.3 0.2 setosa 3
As you can see, lenses can be smoothly integrated into your tidyverse
workflows, as well as your base R workflows. Giving you the powers of compositionality and bidirectionality to improve your code.
Frequently we end up in situations where we want to modify each element of a nested object. This is especially cumbersome without lenses. Let’s imagine our data lives inside a larger structure. And additionally that it isn’t a nice data frame, but a list.
packed_iris <- list(as.list(iris))
packed_iris %>% str(2)
#> List of 1
#> $ :List of 5
#> ..$ Sepal.Length: num [1:150] 5.1 4.9 9.21 4.6 5 ...
#> ..$ Sepal.Width : num [1:150] 3.5 3 3.2 3.1 3.6 3.9 3.4 3.4 2.9 3.1 ...
#> ..$ Petal.Length: num [1:150] 1.4 1.4 1.3 1.5 1.4 1.7 1.4 1.5 1.4 1.5 ...
#> ..$ Petal.Width : num [1:150] 0.2 0.2 0.2 0.2 0.2 0.4 0.3 0.2 0.2 0.1 ...
#> ..$ Species : Factor w/ 3 levels "setosa","versicolor",..: 1 1 1 1 1 1 1 1 1 1 ...
say I want to add 10 to the first element of each column between Sepal.Length
and Petal.Width
.
To do this with lenses we can use the map_l
function to promote a lens
to apply to each element of a list.
els_l <-
index(1) %.%
select_l(Sepal.Length:Petal.Width) %.%
map_l(index(1))
over_map(packed_iris, els_l, ~ . + 10) %>%
str(2)
#> List of 1
#> $ :List of 5
#> ..$ Sepal.Length: num [1:150] 25.1 4.9 9.21 4.6 5 ...
#> ..$ Sepal.Width : num [1:150] 23.5 3 3.2 3.1 3.6 3.9 3.4 3.4 2.9 3.1 ...
#> ..$ Petal.Length: num [1:150] 21.4 1.4 1.3 1.5 1.4 1.7 1.4 1.5 1.4 1.5 ...
#> ..$ Petal.Width : num [1:150] 20.2 0.2 0.2 0.2 0.2 0.4 0.3 0.2 0.2 0.1 ...
#> ..$ Species : Factor w/ 3 levels "setosa","versicolor",..: 1 1 1 1 1 1 1 1 1 1 ...
Here we use the over_map
function to apply a function to each element, you could equivalently use over
with lapply
as well. As you can see setting and applying functions to multiple elements of nested data is dramatically improved by using lenses.
You can make a lens from scratch (!) by passing view
and set
functions to the lens
constructor:
first_l <- lens(view = function(d) d[[1]],
set = function(d, x) { d[[1]] <- x; d })
As you can see, the view
function must accept an element of data, while the set
function must accept such an element as well as the new value of the subpart, and return the new data in its entirety - thus achieving composability - without modifying the original.
In order to avoid unpleasant surprises or inconsistencies for users, an author of a lens
(via lens
) should ensure it obeys the following rules (the “Lenz laws”, here paraphrased from a Haskell lens tutorial):
view
some data with a lens, and then set
the data with that value, you get the input data back.set
a value with a lens, then view
that value with the same lens, you get back what you put in.set
a value into some data with a lens, and then set
another value with the same lens, it’s the same as only doing the second set
.“Lenses” which do not satisfy these properties should be documented accordingly. By convention, the few such specimens in this library are suffixed by “_il" (“illegal lens”). See the package reference for more.
As you can see from the lens
constructor, knowing how to implement view
and set
for a lens turns out to be sufficient to implement the other verbs such as over
and - most importantly - lens composition (%.%
).
In our implementation, lenses are trivial. They simply store the provided functions. A lens
under the hood is a two element list with an element view
and an element set
.
There is nothing particularly new about the lenses appearing here. For a fairly comprehensive (and highly technical) history of lenses, see links here and this blog post .
Thanks to Leigh Spencer Noakes, Zsu Lindenmaier, and Lily Qiu for reading drafts of this document and providing very helpful feedback.


Systems Design Engineering is an interdisciplinary program, with a focus on solving big problems. Students tackle complex technical systems, while considering the human factors involved.
Students, alumni, and their employers love Systems Design Engineering. But to an outsider, the program is misunderstood and poorly explained. Even our own Dean of Engineering was reportedly quoted saying, "I don't know what systems design engineering is". This website exists to mend these issues.
The content found here generally applies to the entire Systems Design Engineering Department, including both the Systems Design (SYDE) and Biomedical (BME) Engineering programs. Listed courses and program specifics are for SYDE, and may be different for BME.
We learn how to technically analyze systems and use the engineering design process from first idea to production.
SYDE is its own unique discipline, and has great opportunities for specialization
Learn about the history of our program, stretching back to 1960.


You can say, "I love you," in Helvetica. And you can say it with Helvetica Extra Light if you want to be really fancy. Or you can say it with the Extra Bold if it's really intensive and passionate, you know, and it might work.
- Robert Bringhurst
Typographic style is founded not on any one technology of typesetting or printing, but on the primitive yet subtle craft of writing.
- Robert Bringhurst


Kyle I S Harrington /<EMAIL_ADDRESS>Generate a random solution, s (may be a model, parameters, etc.)
Loop until s is correct:
Create an alternative solution, m, by mutating s
Compare the fitness/quality/accuracy of s and m
If m is better, then replace s with m
Otherwise, do nothing
Repeat
Because this is easy:
(def program '(+ 1 1))
(eval program) => 2
(def new-program (cons '- (rest program))) => (- 1 1)
(eval new-program) => 0
Note: the single quote tells the interpreter not to evaluate the code that follows


|
| | sensor_osus_manager_class () |
| | Constructor. More...
|
| |
| | ~sensor_osus_manager_class () |
| | Destructor. More...
|
| |
| int | read_tagged (const char *filename) |
| | Read file in tagged ascii format. More...
|
| |
| int | write_parms (FILE *out_fd) override |
| | Write parameters to the currently opened ASCII file – for saving all relevent parameters to an output Parameter file. More...
|
| |
| | atrlab_manager_class (int n_data_max_in) |
| | Constructor. More...
|
| |
| virtual | ~atrlab_manager_class () |
| | Destructor. More...
|
| |
| int | report_status () |
| | Print status of objects in this class. More...
|
| |
| int | set_cg_x (float x) |
| | Set x-value of cg of object. More...
|
| |
| int | set_cg_y (float y) |
| | Set y-value of cg of object. More...
|
| |
| int | set_cg_z (float z) |
| | Set z-value of cg of object. More...
|
| |
| int | set_cg_az (float az) |
| | Set azimuth angle in deg of object. More...
|
| |
| int | set_cg_el (float el) |
| | Set elevation angle in deg of object. More...
|
| |
| int | set_cg_roll (float roll) |
| | Set roll angle in deg of object. More...
|
| |
| float | get_cg_x () |
| | Return x-value of cg of object. More...
|
| |
| float | get_cg_y () |
| | Return y-value of cg of object. More...
|
| |
| float | get_cg_z () |
| | Return z-value of cg of object. More...
|
| |
| float | get_cg_az () |
| | Return azimuth angle in deg of object. More...
|
| |
| float | get_cg_el () |
| | Return elevation angle in deg of object. More...
|
| |
| float | get_cg_roll () |
| | Return azimuth angle in deg of object. More...
|
| |
| int | set_mode (int mode_current_in) |
| | Set mode – used for cases where the camera tracks a moving object. More...
|
| |
| int | set_if_visible (int view_mode_in) |
| | Set visibility – 0 is off, 1 is on. More...
|
| |
| int | get_if_visible () |
| | Return visibility flag. More...
|
| |
| int | get_n_data () |
| | Return the number of objects currently in the class. More...
|
| |
| int | set_refresh_pending () |
| | Set refresh pending flag. More...
|
| |
| int | set_reread_pending () |
| | Set reread pending flag. More...
|
| |
| int | set_recalc_pending () |
| | Set recalc pending flag. More...
|
| |
| int | monitor_for_onoff (int *mon) |
| | Monitor the input location for object visibility. More...
|
| |
| image_3d_class * | get_image_3d () |
| | Return pointer to 3-d image. More...
|
| |
| int | register_dir (dir_class *dirin) |
| | Register dir_class that stores file names and info for DEM filesets and Point clouds. More...
|
| |
| int | register_clock (clock_input_class *clock) |
| | Register a clock. More...
|
| |
| int | register_map3d_index (map3d_index_class *index) |
| | Register a map index. More...
|
| |
| int | register_vector_index (vector_index_class *vector_index) |
| | Register all vector overlays. More...
|
| |
| int | register_camera_manager (atrlab_manager_class *camera_manager_in) |
| | Register camera manager. More...
|
| |
| int | register_viewer (fusion3d_viewer_class *myViewer) |
| | Register viewer to class. More...
|
| |
| int | register_map3d_lowres (map3d_lowres_class *map3d_lowres_in) |
| | Register map3d_lowres_class to class. More...
|
| |
| int | wire_count (int *count, int index_count) |
| | Monitor input location and transfer its content into int buffer[index_count]. More...
|
| |
| int | check_count (int index_count) |
| | Check for count change for index index_count. More...
|
| |
| int | wire_slider (float *count, int index_slider) |
| | Monitor input location and transfer its content into float buffer[index_slider]. More...
|
| |
| int | check_slider (int index) |
| | Check for slider change for index. More...
|
| |
| int | reset_wiring () |
| | Reset (reinitialize) the wiring for connecting managers with input devices. More...
|
| |
| virtual int | refresh () |
| | Refresh display – Virtual, so just ignore. More...
|
| |
| virtual int | register_icon (icon_class *icon_in) |
| | Register icon – Virtual. More...
|
| |
| virtual int | get_closest_icon (float east, float north, icon_class *icon_out, float &dist_to_icon) |
| | Find the closest icon – Virtual, so if not superceded, just return 0 (no icons). More...
|
| |
| virtual int | get_zoom_factor (float &camera_height) |
| | Get the zoom factor – Virtual, so if not superceded, just return 0. More...
|
| |
| virtual int | set_zoom_factor (float camera_height) |
| | Set the zoom factor – Virtual, so if not superceded, just return 0. More...
|
| |
| virtual int | get_focal_length (float &focal_length) |
| | Get the focal length – Virtual, so if not superceded, just return 0. More...
|
| |
| virtual int | set_focal_length (float focal_length) |
| | Set the focal length – Virtual, so if not superceded, just return 0. More...
|
| |
| virtual int | get_displayed_range_span (int &first_range_out, int &last_range_out) |
| | Get the span of ranges currently displayed – Virtual, so if not superceded, just return 0. More...
|
| |
| virtual int | set_displayed_range_min (int first_range_in) |
| |
| virtual int | set_displayed_range_max (int last_range_in) |
| |
| virtual int | make_scene_3d () |
| |
| | base_jfd_class () |
| | Constructor. More...
|
| |
| virtual | ~base_jfd_class () |
| | Destructor. More...
|
| |
| int | set_diag_flag (int flag) |
| | Set level of diagnostics. More...
|
| |
| int | register_coord_system (gps_calc_class *gps_calc_in) |
| | Register the common gps_calc_class for defining the current coordinate systems and transformations between them. More...
|
| |
| const char * | get_type () |
| | Get the name of the class. More...
|
| |
| int | warning (int oiv_window_flag, const char *message) |
| | Open dialog window with warning. More...
|
| |
| int | warning_s (string cmessage, string smessage) |
| | Open dialog window with 2-part warning message. More...
|
| |
| int | exit_safe (int oiv_window_flag, const char *message) |
| | Open dialog window with fatal error message. More...
|
| |
| int | exit_safe_s (string message, string smessage) |
| | Open dialog window with fatal error message. More...
|
| |
| virtual int | clear_all () |
| |
| virtual int | read_file (string sfilename) |
| | Read file: all functions including open, read header and data and close – Virtual. More...
|
| |
| virtual int | read_file_open (string sfilename) |
| | Read file: only the open part of the entire read-file – Virtual. More...
|
| |
| virtual int | read_file_header () |
| | Read file: only the read-header part of the entire read-file – Virtual. More...
|
| |
| virtual int | read_file_data () |
| | Read file: only the read-data part of the entire read-file – Virtual. More...
|
| |
| virtual int | read_file_close () |
| | Read file: only the close part of the entire read-file – Virtual. More...
|
| |
| virtual int | write_file (string sfilename) |
| | Write file: entire process of open, write header and data and close – Virtual. More...
|
| |
|
| std::vector< int > | om_image_index |
| | Per OM – Index of stored image (-99 for no image) More...
|
| |
| std::vector< int > | om_sorted_index |
| | Per OM – sort – sorted om-index – ordered by time, points to preordered index so you can read files in time order. More...
|
| |
| std::vector< time_t > | om_create_time |
| | Per OM – sort – Time of OML file creation used to sort oml files by time. More...
|
| |
| std::vector< float > | user_bearing_val |
| | Per user-entered bearing – Angle in deg cw from North. More...
|
| |
| std::vector< string > | user_bearing_id |
| | Per user-entered bearing – Corresponding id. More...
|
| |
| std::vector< int > | iom_recent_camera |
| | Working – list of valid camera image indices. More...
|
| |
| std::vector< string > | valid_asset_type |
| | Per Valid sensor type – Sensor type (assetType) More...
|
| |
| std::vector< string > | valid_asset_name |
| | Per Valid sensor type – Sensor name (assetName) More...
|
| |
| std::vector< int > | valid_asset_filter_flags |
| | Per Valid sensor type – Filter flag (1 iff filter out sensor) More...
|
| |
| std::vector< int > | valid_asset_stat_flags |
| | Per Valid sensor type – is sensor stationary. More...
|
| |
| std::vector< int > | valid_asset_local_flags |
| | Per Valid sensor type – is sensor local. More...
|
| |
| std::vector< int > | valid_asset_camera_flags |
| | Per Valid sensor type – does sensor include camera. More...
|
| |
| std::vector< int > | valid_asset_prox_flags |
| | Per Valid sensor type – does sensor include prox. More...
|
| |
| std::vector< int > | valid_asset_red |
| | Per Valid sensor type – Red value [0-255]. More...
|
| |
| std::vector< int > | valid_asset_grn |
| | Per Valid sensor type – Green value [0-255]. More...
|
| |
| std::vector< int > | valid_asset_blu |
| | Per Valid sensor type – Blue value [0-255]. More...
|
| |
| int | n_images |
| | Camera images – No of camera images currently defined. More...
|
| |
| int | n_images_max |
| | Camera images – Max no of target vectors. More...
|
| |
| int | display_name_flag |
| | Flags – 0 for no text display for SensorML, 1 to display short name, 2 to display unique id. More...
|
| |
| int | images_active_flag |
| | Flags – Index of sensor for which images are currently being displayed (-99 for no display) More...
|
| |
| int | use_modify_time_flag |
| | Flags – 0=use file create time (default), 1=use file modify time (for checking for new files and to sort O&M) More...
|
| |
| float | time_interval_show_stat |
| | Display interval – Interval in s over which sensor hits are highlighted. More...
|
| |
| float | time_interval_show_mov |
| | Display interval – Interval in s over which sensor hits are highlighted. More...
|
| |
| int | earliest_in_window_stat |
| | Display interval – Index of earliest OM within display time window. More...
|
| |
| int | latest_in_window_stat |
| | Display interval – Index of latest OM within display time window. More...
|
| |
| int | earliest_in_window_mov |
| | Display interval – Index of earliest OM within display time window. More...
|
| |
| int | latest_in_window_mov |
| | Display interval – Index of latest OM within display time window. More...
|
| |
| int | n_in_window_stat |
| | Display interval – No. of O&M within display time window. More...
|
| |
| int | n_in_window_mov |
| | Display interval – No. of O&M within display time window. More...
|
| |
| float | imagScaleFactorWorld |
| | Scale factor for images – world coordinates. More...
|
| |
| float | offset_lat |
| |
| float | offset_lon |
| |
| float | offset_elev |
| | Offsets added to icon positions to translate to different map. More...
|
| |
| float | d_above_ground |
| | Draw object and track this dist above ground. More...
|
| |
| string | request_osus_addr |
| | OSUS Request UGS – IP address of OSUS server. More...
|
| |
| std::vector< string > | request_sensor_types |
| | OSUS Request UGS – list of assetTypes of sensors that you can request from. More...
|
| |
| int | request_osus_port |
| | OSUS Request UGS – Port of OSUS server. More...
|
| |
| int | dir_flag_osus |
| | Monitor dir – 1 if monitor a dir for OSUS files. More...
|
| |
| float | dir_time_osus |
| | Monitor dir – timer inteval between checks of OSUS dir. More...
|
| |
| string | dirname_osus |
| | Monitor dir – OSUS dir name. More...
|
| |
| string | dir_monitor_pattern_osus |
| | Monitor dir – Filenames must match this pattern to be pulled from dir. More...
|
| |
| time_t | min_create_time_osus |
| | Monitor dir – Only accept files written after this time – updated after each access. More...
|
| |
| int | n_warn |
| |
| sensor_read_osus_class * | sensor_read_osus |
| | Helper class – OSUS parser. More...
|
| |
| time_conversion_class * | time_conversion |
| | Helper class – convert time formats. More...
|
| |
| osus_image_store_class * | osus_image_store |
| | Helper class – store images from OSUS files. More...
|
| |
| osus_command_class * | osus_command |
| | Helper class – command OSUS to task sensors to produce imagery. More...
|
| |
| int | n_data_max |
| | Max no of data objects that can input. More...
|
| |
| int | n_data |
| | No of data objects input
More...
|
| |
| int | refresh_pending |
| | Change pending – any kind (0/1 default) More...
|
| |
| int | reread_pending |
| | Change pending – new image (from file/Epix/etc) (0/1 default) More...
|
| |
| int | recalc_pending |
| | Change pending – new parms requiring recalc (0/1 default) More...
|
| |
| float | cg_world_x |
| | cg location – easting(m) More...
|
| |
| float | cg_world_y |
| | cg location – northing(m) More...
|
| |
| float | cg_world_z |
| | cg location – elevation(m) More...
|
| |
| float | cg_world_az |
| | cg location – Angle in deg from East ccw More...
|
| |
| float | cg_world_el |
| | cg location – Angle in deg from horizontal More...
|
| |
| float | cg_world_roll |
| | cg location – Angle in deg from horizontal More...
|
| |
| int | if_translated |
| | 1 iff object has been translated since last draw More...
|
| |
| int | if_rotated |
| | 1 iff object has been rotated since last draw More...
|
| |
| float | camera_height_old |
| | Previous camera height. More...
|
| |
| int | if_visible |
| | 1 if object visible, 0 if invisible More...
|
| |
| int ** | mon_onoff_a |
| | Multiple vis inputs – Location to monitor. More...
|
| |
| int * | state_onoff_a |
| | Multiple vis inputs – Last state of onoff. More...
|
| |
| int | n_onoff |
| | No of locations presently monitored. More...
|
| |
| int | vis_changed_by_method |
| | 1 iff vis changed by method rather than by monitoring More...
|
| |
| float ** | slider_a |
| | Array of slider values. More...
|
| |
| float * | old_slider_a |
| | Previous vals for sliders. More...
|
| |
| int ** | count_a |
| | Array of counters. More...
|
| |
| int * | old_count_a |
| | Previous vals for counters. More...
|
| |
| int | count_a_default |
| | Array of counters – Default value. More...
|
| |
| int | mode_current |
| | Camera tracking – 0=search. 1=track, 2=model. More...
|
| |
| int | mode_previous |
| | Camera tracking – 0=search. 1=track, 2=model. More...
|
| |
| int | if_new_icon |
| | 1 iff new icon registered More...
|
| |
| int | first_range |
| |
| int | last_range |
| | Span of ranges currently displayed. More...
|
| |
| dir_class * | dir |
| | Helper class –. More...
|
| |
| clock_input_class * | clock_input |
| | Helper class –. More...
|
| |
| map3d_index_class * | map3d_index |
| | Helper class –. More...
|
| |
| image_3d_class * | image_3d |
| | Helper class – For any 3-d images used by manager. More...
|
| |
| atrlab_manager_class * | camera_manager |
| | Helper class –. More...
|
| |
| vector_index_class * | vector_index |
| | Helper class –. More...
|
| |
| fusion3d_viewer_class * | myViewer |
| | Helper class –. More...
|
| |
| map3d_lowres_class * | map3d_lowres |
| | Helper class – to do low-res DEM. More...
|
| |
| icon_class * | icon |
| | Helper class – Pointer to icon. More...
|
| |
| int | diag_flag |
| | Diagnostic level – 0=none, 1=little, 2=moderate, 3=heavy. More...
|
| |
| int | opsys_flag |
| | Operating system – 0=unix, 1=windows, 2=linux. More...
|
| |
| char * | class_type |
| | Unique name for each child class. More...
|
| |
| int | localCoordFlag |
| | Coord systems – -1=unknown local coord system, 0=local same as global, Positive=EPSG where known local coord different from global. More...
|
| |
| gps_calc_class * | gps_calc |
| | Coord systems – Worker class to define global coordinate systems and transformations. More...
|
| |
Manages icons generally, but specifically implemented for UGS sensors.
Icons are marked on the map and when the user clicks near an icon, the information in that icon can be retrieved.


G# Framework
The G# Framework is an add-on toolkit for LabVIEW that adds reference based object-oriented support. It takes advantage of the new data value reference structure in LabVIEW 2009 together with the native classes and will add a full object-oriented support with excellent performance. This is the new generation of object-oriented support that makes LabVIEW as powerful as any object-oriented language. There also exists a StarUML plug-in to the G# Framework.
The G# Framework is a
National Instrument Compatible with LabVIEW Gold product.
G# is a registered trademark of AddQ Consulting.
What is Unique About G#?
An object-oriented language must fulfill the fundamental requirements: abstraction, encapsulation, inheritance and polymorphism. The G# framework has taken a lot of inspiration from C# and Java and therefore has the following additional requirements:
Toolkit Contents
Including:
- G#Object the root object that all classes inherits from.
- G#Interface the root interface that all interfaces inherit from.
- G#Templates class templates that are copied to create new classes.
For more information, please visit the G# Online Manual.
Download
The G# Framework is free and requires no license. You may install the G# IDE
with as many users and computers as you like.
Supported
LabVIEW Versions
LabVIEW 2009 Full Development or higher
Supported
Operating Systems
Windows XP/Vista/7
Red Hat Enterprise Linux WS 4 or later
openSUSE 10.3 or later
Note: Mac OS X may work, but is not tested
Current version: 1.2.0 (view G# Framework ReadMe.txt)
As a good UML design tool we recommend the free, open source tool StarUML together with the free G# StarUML Plug-in extension.
Support
For support issues, please contact<EMAIL_ADDRESS>Our
policy is to respond within one working day. We will not support issues
regarding object-oriented design, but we can of course offer this as consultant
services. Please contact<EMAIL_ADDRESS>Please join the G#
community group for more information, discussions and ideas at:
http://decibel.ni.com/content/groups/gsharp
The Compatible with LabVIEW logo is a trademark of National Instruments Corporation and is used under a license from National Instruments Corporation.


{% extends "main/base_template.html" %}
{% block title %}iWear - Landing Page{% endblock title %}
{% block sidebar %}{% endblock sidebar %}
{% block content %}
Welcome to iWear!
iWear goal is to bring people’s closet to the digital world and make its usage advanced and smarter.
iWear is using RFID technology in order to monitor and analyze the use of clothing items and to provide statistics and data.
Based on the statistics and data, the user can manage his closet and get recommendations of clothing items based on different parameters.
Log in
Register
{% endblock content %}


{% extends "layout.html" %} {% block content %}
Welcome to TastyStats!
Uh-oh, this page is still baking. Please check back in few days for more crispy content...


Update
Follow these steps to update a bid:
- On the Strategies > Subscriptions & Bids page, click Increase Bid next to the alpha you want to update your bid for.
- Place a new bid with the updated allocation and price.
Cancel
Follow these steps to cancel a bid:
- On the Strategies > Subscriptions & Bids page, click Cancel Bid next to the alpha you want to cancel your bid for.
- Click OK.


- 1. Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
- 2. Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
- 3. Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
Prev
Next