Data is often stored as plain text file. That’s good because it is a simple format. However, simplicity comes with a cost: Not all questions may have definite answers. The most common hassle when reading/importing text files is that the encoding scheme is unknown, aka wrong. This problem mostly occurs when, say, a Mac user stores a text file, where per default UTF8 text encoding is applied. In contrast, on a Windows machine, Windows-encoding (often dubbed “latin1”,“Windows 1252” or “ISO-8859-1”) is the default. What happens then is similar to what would happen if type a letter any you read thinking that it is in French – confusion guaranted.
With a little more details,
- “Windows 1252” is a widely used 8-bit encoding scheme, including mostly English letters.
- “ISO-8859-1” is also 8-bit, and covers the latin character set, thereby suitably depicting most European Languages. For example, the letter “A” is encoded as “0032” (hex).
- “UTF-8” (“Unicode Transformation Format”) is the predominant encoding in the WWW; it covers more than 100 scripts (languages) from all over the world, including emojis, and special characters. Encoding a letter via UTF8 may produce a byte sequence betweeen 1 and 4 bytes. More frequently used letters are stored in the beginning of the code page, so that only 1 byte is needed for encoding.
According to Wikipedia, UTF8 is the defacto standard in the internet:
A little more in depth, consider that the text binary representation for some text (string). It will be pinned down to some bits and bytes. The question is what “translation code” from text to bits (or vice versa) is used? That’s exactly what’s defined in a text encoding scheme such aus UTF8. By the way, it seems that UTF8 is a reasonable standard, dear Windows user, consider following this standard. Your favorite text editor, such as Notepad++, or Text Mate, will offer you an option to “save with encoding” or similar. By the way, RStudio will do that for you, too (see File > Save with Encoding…).
So much for theory. Now, let’s test it. Assume we have a text file, and we do not know the encoding. So what we do is, we guess it:
Guessing encoding
library(readr)
library(readxl)
Here’s the file (ignore for the moment that the file name suggests an encoding):
fileurl <- "https://data-se.netlify.com/download/text-latin1.csv"
guess_encoding(fileurl)
## # A tibble: 1 x 2
## encoding confidence
## <chr> <dbl>
## 1 ISO-8859-1 0.36
Now that we have an educated guess, let’s try to parse it. The parameter locale
can be used to adapt to local language settings such as used for text encoding.
Read textfile with specified encoding
text <- read_csv(file = fileurl,
locale = locale(encoding = "ISO-8859-1"))
## Parsed with column specification:
## cols(
## col1 = col_character(),
## col2 = col_double(),
## col3 = col_double()
## )
Let’s see whether it worked out:
text
## # A tibble: 3 x 3
## col1 col2 col3
## <chr> <dbl> <dbl>
## 1 Nürnberg 1.1 1.1
## 2 München 2 2
## 3 Düsseldorf 3 3
Save text file with specified encoding
Note that write_csv()
will only write to UTF8.
write_csv(x = text,
path = "path/to/file.csv")
However, write.csv()
and friends can be used to define the encoding:
write.csv(x = text,
file = "test2.csv",
fileEncoding = "utf8")
Hazzle free with Excel?
Maybe easier to use an excel data file where the encoding is defined within the data (xls(x)) file? Well, yes, but some times no.
Let’s try it:
textxlsxurl <- "https://data-se.netlify.com/download/text.xlsx"
destfilename <- "text.xlsx"
textxlsx <- download.file("https://data-se.netlify.com/download/text.xlsx",
destfile = destfilename)
file.exists(destfilename)
## [1] TRUE
text_xlsx <- read_xlsx(path = destfilename)
text_xlsx
## # A tibble: 3 x 3
## col1 col2 col3
## <chr> <dbl> <dbl>
## 1 Nürnberg 1 1
## 2 München 2 2
## 3 Düsseldorf 3 3
if (file.exists(destfilename))
file.remove(destfilename) # remove file
## [1] TRUE
That seems to work easily. Maybe that’s the easiest way at the end of the day (?).
One problem that may arise - besides building on proprietary code that may change without notice - is that Excel may have problems reading a UTF8 csv, as explained here.
Get encoding of string
Assume there is some text (string), already loaded in your R session. How to determine and change the encoding then?
Here’s the string:
text$col1
## [1] "Nürnberg" "München" "Düsseldorf"
What’s the encoding?
Encoding(text$col1)
## [1] "UTF-8" "UTF-8" "UTF-8"
Now let’s change the encoding:
Encoding(text$col1) <- "latin1"
Encoding(text$col1)
## [1] "latin1" "latin1" "latin1"
To get an overview on supported encodings, use iconvlist()
. Be aware, the list is long:
length(iconvlist())
## [1] 419
To get the default encoding of your system, use this function:
Sys.getlocale()
## [1] "en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8"
If R says the encoding is unknown
it often means that it’s the system’s default.
For more details, check out this post.


|
|
|
|
|
|
|
Coming
Soon: Hiking and Sightseeing Other Hobbies Our
Pets |
|
|
|
|
One of my favorite pastimes is fishing. I remember
when I had the time to
fish. Now I am more of a Dad than anything - and that's good
news. Fishing has been replaced by the New Light of
My Life . It's a nice trade to spend time with my little
Ali-Baba instead of fishing. When she gets old enough - maybe next
summer - I'll try to teach her. If she likes it, cool. Update:
|
|
|
|
|
Discover
America's Parks (LLBean)
|
|
|
| Indiana
Rivers
|
|
|
Life is tough on kids these days. They get exposed to
violence at such an early age. She used to love the kind purple
dinosaur named Barney.
Now she is really into RugRats
and Dexter's
Laboratory. |
|
My wife Stephanie is from Hawaii, California,
Maryland, and Pennsylvania; I am from Kentucky, Indiana, Ohio, and
New Jersey. We first met in 1984 at the Psychology Department here
at Purdue. She came to study and I was as a research technician, but
we didn't become romantically involved until many years later. She
has a Bachelor's, a Master's, and a PhD in Psychology with
specialization in neuroscience. |
|
Stephanie is now a Research Scientist at Med
Institute Inc. and is an educational writer for Rue Educational Publishers. |
|


This page is the marking guide to your website that your tutor will use to find your elements. Do not name this page anything other than assignment.html (all lower case) or else we may not be able to find and mark your assignment elements. How to use this page:
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Student Forum Participation
https://piazza.com/class/izbtuxo34jtvk?cid=448
https://piazza.com/class/izbtuxo34jtvk?cid=443
https://piazza.com/class/izbtuxo34jtvk?cid=68
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
Student Forum Participation
https://piazza.com/class/izbtuxo34jtvk?cid=696
https://piazza.com/class/izbtuxo34jtvk?cid=805
Replace this line with your URL link to this element in your website.
Notes: Provide any notes you may have about this element here.
Notes: Provide any notes you may have about this element here.
https://developers.facebook.com/docs/plugins/
Notes: Provide any notes you may have about this element here.
Replace this line with your URL link to this element in your website.
Notes: Provide any notes you may have about this element here.
Replace this line with your URL link to this element in your website.
Notes: Provide any notes you may have about this element here.
Replace this line with your URL link to this element in your website.
Notes: Provide any notes you may have about this element here.
Other
Continuous Improvement Session
Replace this line with the date you attended the continuous improvement session.
Report
Replace this line with the local URL to your report.


Immerge into the futuristic colonized Solar System of EXPANSE, discover the life of detective Josephus Miller by taking on his helmet.
Find Out MoreAREO is the simple solution for everyone to create product display, games, virtual open house, interactive story etc. All brought to you by SpinVR.
Goto AREOAREO is the simple solution for everyone to create product display, games, virtual open house, interactive story etc. All brought to you by SpinVR.
Goto AREOLorem ipsum dolor sit amet, consectetur adipiscing elit. Proin magna magna, rhoncus id tempor dictum, porttitor quis ex. Fusce dignissim, augue eget posuere rhoncus, nibh elit sodales justo.
Get StartedWe update our templates and presets everyday.
Use as is, or create your own.
HTC Vive, Oculus Rift, HoloLens and Gear VR.
Part of the evolving VR community.
Ready to start your next project with us? That's great! Give us a call or send us an email and we will get back to you as soon as possible!


--- layout: post title: no title date: '2015-12-30T18:30:29+01:00' categories: - Sketchbooks - Storyboards picture_url: https://film-Storyboards.tumblr.com/post/136290227243 ---


CEP 811 is steaming forward at full speed and we’re now getting close to finishing week four of the course. This week, we’ve been tasked with creating an outline for a MOOC. After many days opening a new blog post and staring at it, I think I’ve finally landed on a format and topic. So, without further ado, I humbly submit for your consideration…
In I’ll Take it to Go, my peers will explore mobile creation skills by working only on mobile phones for the course and through open communication, feedback, and remixing by peers.
Course topic: facilitating active learning on mobile devices.
Students are coming into schools with mobile devices which are not being utilized for a variety of reasons, one of which is not knowing how to effectively engage students in higher order thinking skills. Often, mobile apps and tools are dismissed as only having entertainment value. We are missing a huge opportunity to leverage the computing power in their pockets.
So, the question is, “Why mobile devices?” Consider the amount of time you use your device each day. Directions, research, quick communication…all done on the go. We capture moments through photos and video, we share our lives with one another as we move from place to place. These simple (and often free) tools can be repurposed to support students and the learning process. Nearly all students have experience with mobile devices, so the time spent teaching complicated tools can be eliminated. Remember, Cognitive Load Theory states that learning can only occur when the student can apply sufficient working memory resources (Sweller, Merrienboer, and Paas, 1998). Too often, new tools command the student focus rather than the learning task given. By using familiar tools, accentuating process and encouraging connections, the course will push learners into higher-order application of ideas and skills.
This is meant for all educators and students. Tools that can be used by students can (and should) also be used by teachers and other staff to engage, encourage, and support learning. This won’t be a typical MOOC. The course will be decentralized and focus on skill building and innovative application of mobile learning techniques. Learning targets will have suggested tasks to complete, but participants will be able to network, explore, and create their own products for completion. Peer evaluations will be used as benchmarks for progress through the course, and the course can be taken in any sequence. That being said, the length of the course may vary from one person to another.
Participants in the course will be expected to use their mobile device to create a history of artifacts to demonstrate their learning. Areas of focus will include photography, video, audio, social media, and blogging. While all tasks can be done on a traditional desktop or laptop computer, the main objective of the course is to immerse learners in the world of mobile tech so they can bring their experiences back to the classroom to more successfully engage their students. The time it takes to complete is partly determined by the depth of exploration that occurs within each topic and the resulting peer assessment, revision, and remixing. There is no prescribed “time on task,” and learners will have an opportunity to explore ideas as in depth as they would like.
The majority of MOOCs focus on using the Internet as content delivery…a large pipeline through which information can be delivered from one person to thousands. The problem is that the Internet doesn’t work like a pipe. It works like a network, with information criss-crossing from one person to another. If we want to design effective online classes, we need to build courses to mimic that network. As long as MOOCs focus on technology (the LMS used for delivery) and the content (top-shelf professors), their design and effectiveness will continue to suffer. Pedagogy must has as much importance as the others, if not more, in order to truly innovate in online education.
TPACK self-assessment. [Digital]. Retrieved from http://caryacademy-sti.wikispaces.com/TPACK+Self-Assessment
Sweller, J, Merrienboer, J, Paas, F. (1998). Cognitive architecture and instructional design. Educational Psychology Review. 10-3, 251-296. Retrieved from https://docs.google.com/file/d/0B68p5ayLtLuqZ2wtTTNueElZUHc/edit?usp=drive_web
Written on November 17th, 2013 by Brian Bennett Categorized in: All MAET Technology
Leave a comment


For more details see browser's console.
Open websocket
Close websocket
Start
Stop
or send json
Send json
Clan dialogue


Total Users
{{ user|length }}
Total Males
{{ male|length }}
Total Females
{{ female|length }}
Total Visit
{{total_visit}}
Visits Over Time
Visitors Map geo-presentation
Device Usage
|
Top 5 |
Device |
|
|---|---|---|
|
Device model
| # | Model |
|---|---|
| {{forloop.counter}} | {{device_model.user_agent}} |


Sri Lanka team arrives in Islamabad ahead of Test series
by https://www.dawn.com/authors/202/dawn-com, Dawn.comSri Lanka's cricket team arrived in Islamabad on Monday ahead of their Test series against Pakistan starting on December 11.
Test cricket is returning to Pakistan after over a decade as the Sri Lankan team plays its World Test Championship matches in the country. The first Test will start on Wednesday at Pindi Cricket Stadium in Rawalpindi followed by a second Test at National Stadium in Karachi from December 19-23.
Sri Lankan fast bowler Suranga Lakmal will miss the two-match Test series after contracting dengue fever, Sri Lanka’s cricket board announced on Sunday. He will be replaced by Asitha Fernando, who will join the squad for the second match of the series.
Sri Lanka have also given former skipper Dinesh Chandimal a chance to fight his way back into the national team, now led by Dimuth Karunaratne.
Meanwhile, Fawad Alam was a surprise inclusion in Pakistan's 16-member squad announced on Saturday. The squad will be led by Azhar Ali.
In September, Sri Lanka's national cricket squad had arrived in Pakistan for a tour comprising three One-Day Internationals and three Twenty20 matches. Ten senior players citing security concerns had opted out of the tour.
Squads:
Sri Lanka: Dimuth Karunaratne (captain), Oshada Fernando, Kusal Mendis, Angelo Mathews, Dinesh Chandimal, Kusal Perera, Lahiru Thirimanne, Dhananjaya de Silva, Niroshan Dickwella, Dilruwan Perera, Lasith Embuldeniya, Lahiru Kumara, Vishwa Fernando, Kasun Rajitha, and Lakshan Sandakan. Substitute player from the end Test: Asitha Fernando.
Pakistan: Azhar Ali (captain), Fawad Alam, Mohammad Rizwan (wicket keeper), Babar Azam, Abid Ali, Asad Shafiq, Haris Sohail, Imam-ul-Haq, Imran Khan, Kashif Bhatti, Mohammad Abbas, Naseem Shah, Shaheen Shah Afridi, Shan Masood, Yasir Shah, and Usman Shinwari.


--- layout: post title: ! 'Aron Pilholfer at #doingdataj' date: 2012-04-02 01:10:26.000000000 +05:30 categories: - Blog - Data Visualization - Data Visualization Thoughts tags: [] status: publish type: post published: true meta: quote-url: http://carlvlewis.net/?p=1967 quote-copy: The problem is that we continue to reward crap journalism that’s based on anecdotal evidence alone . . . But truly if it’s not a priority at the top to reward good data-driven journalism, it’s going to be impossible to get people into data because they just don’t think it’s worth it. _edit_last: '1' quote-author: Aron Pilholfer, New York Times image: '' seo_follow: 'false' seo_noindex: 'false' link-url: http:// audio: http:// tmac_last_id: '229660838376652800' pvc_views: '910' _jetpack_related_posts_cache: a:1:{s:32:"8f6677c9d6b0f903e98ad32ec61f8deb";a:2:{s:7:"expires";i:1433130622;s:7:"payload";a:3:{i:0;a:1:{s:2:"id";i:1967;}i:1;a:1:{s:2:"id";i:3952;}i:2;a:1:{s:2:"id";i:2577;}}}} author: login: cvlewis email<EMAIL_ADDRESS>display_name: Carl V. Lewis first_name: Carl V. last_name: Lewis excerpt: !ruby/object:Hpricot::Doc options: {} ---
Totally agree, but harbor the lurking suspicion that many traditional readers still like to read pretty narratives and don't care as much if the facts back them up. In other words, it's an audience problem just as much as it is an editorial one.


In Aurelia, user interface components are composed of _view_ and _view-model_ pairs. The view is written with HTML and is rendered into the DOM. The view-model is written with JavaScript and provides data and behavior to the view. The Templating Engine along with Dependency Injection are responsible for creating these pairs and enforcing a predictable lifecycle for the component. Once instantiated, Aurelia's powerful _databinding_ links the two pieces together allowing changes in your view-model to be reflected in the view and changes in your view to reflected in your view-model. This Separation of Concerns is great for developer/designer collaboration, maintainability, architectural flexibility, and even source control.
To create a UI component, you need only create two files, one for each of the component parts. Let's create a simple "Hello" component. To do that we'll need a _hello.js_ for our view-model and _hello.html_ for our view. Here's the source for each:
export class Hello {
firstName = 'John';
lastName = 'Doe';
sayHello() {
alert(`Hello ${this.firstName} ${this.lastName}. Nice to meet you.`);
}
}
export class Hello {
constructor() {
this.firstName = 'John';
this.lastName = 'Doe';
}
sayHello() {
alert(`Hello ${this.firstName} ${this.lastName}. Nice to meet you.`);
}
}
export class Hello {
firstName: string = 'John';
lastName: string = 'Doe';
sayHello() {
alert(`Hello ${this.firstName} ${this.lastName}. Nice to meet you.`);
}
}
Notice that the view-model is a plain class. There's nothing remarkable about it. One of the strengths of Aurelia is that you can write so much of your application in vanilla JS.
Also, notice how the view is wrapped in a Web Components HTMLTemplateElement. All views use standards-based HTML templates. You can also see the very simple, easy-to remember binding language. Simply append `.bind` to any HTML attribute in the DOM, and Aurelia will bind it to the corresponding property in your view-model.
The `.bind` binding command configures the "default binding behavior" for the attribute. For most attributes, this is a `one-way` binding, where data updates only flow in one direction: from the view-model to the view. However, usually, the behavior you want for form controls is `two-way` binding so that data not only flows from your view-model into your view, but user input in the view flows back into your view-model.
Those are the defaults, but you can always be explicit about the binding direction by using `.one-way`, `two-way` or `.one-time` in place of `.bind`. (`.one-time` renders the initial value of the property but does not perform synchronzation thereafter, making it a nice memory and performance gain for data you know will not change.)
In addition to binding HTML attributes, you can also bind events. Any event, either native or custom, can be bound using `.trigger` this causes the expression to be invoked when the indicated event is fired.
> You can read more about data binding in the various Binding articles.
Now you know how to build basic components. What's great about this knowledge? It's consistent throughout Aurelia. The same pattern as above is used to create your app's root component, screens that the router navigates to, custom elements, dynamically composed UI components, modal dialogs, etc.
## Component Instantiation Through Dependency Injection (DI)
View-models and other interface elements, such as Custom Elements and Custom Attributes, are created as classes which are instantiated by the framework using a dependency injection container. Code written in this style is easy to modularize and test. Rather than creating large classes, you can break things down into small objects that collaborate to achieve a goal. The DI can then put the pieces together for you at runtime.
In order to leverage DI, you simply decorate your class to tell the framework what it should pass to its constructor. Here's an example of a CustomDetail component that depends on Aurelia's fetch client.
import {inject} from 'aurelia-framework';
import {HttpClient} from 'aurelia-fetch-client';
@inject(HttpClient)
export class CustomerDetail {
constructor(http) {
this.http = http;
}
}
import {HttpClient} from 'aurelia-fetch-client';
export class CustomerDetail {
static inject() { return [HttpClient] };
constructor(http) {
this.http = http;
}
}
import {autoinject} from 'aurelia-framework';
import {HttpClient} from 'aurelia-fetch-client';
@autoinject
export class CustomerDetail {
constructor(private http: HttpClient) {}
}
* If you are using ES2016, use the `inject` decorator. It should pass a list of types to provide instances of. There should be one argument for each constructor parameter. In the above example, we needed an HttpClient instance, so we added the `HttpClient` type in the `inject` decorator and then added a corresponding parameter in the constructor.
* If you are sticking with ES2015, or don't want to use decorators, you can also add a static `inject` method to the class that returns an array of types to inject.
* If you are using TypeScript >= 1.5, you can add the `@autoinject` decorator to your class and leave out the Types in the decorator call, but just use them on the constructor's signature.
## The Component Lifecycle
All components have a well-defined lifecycle. Below is a list of methods you can implement on your view-model in order to hook into the component lifecycle:
1. `constructor()` - The view-model's constructor is called first.
2. `created(owningView: View, myView: View)` - If the view-model implements the `created` callback it is invoked next. At this point in time, the view has also been created and both the view-model and the view are connected to their controller. The created callback will recieve the instance of the "owningView". This is the view that the component is declared inside of. If the component itself has a view, this will be passed second.
3. `bind(bindingContext: Object, overrideContext: Object)` - Databinding is then activated on the view and view-model. If the view-model has a `bind` callback, it will be invoked at this time. The "binding context" to which the component is being bound will be passed first. An "override context" will be passed second. The override context contains information used to traverse the parent hierarchy and can also be used to add any contextual properties that the component wants to add.
4. `attached()` - Next, the component is attached to the DOM (in document). If the view-model has an `attached` callback, it will be invoked at this time.
5. `detached()` - At some point in the future, the component may be removed from the DOM. If/When this happens, and if the view-model has a `detached` callback, this is when it will be invoked.
6. `unbind()` - After a component is detached, it's usually unbound. If your view-model has the `unbind` callback, it will be invoked during this process.
Each of these callbacks is optional. Implement whatever makes sense for your component, but don't feel obligated to implement any of them if they aren't needed for your scenario. Usually, if you implement `bind` you will need to implement `unbind`. The same goes for `attached` and `detached`, but again, it isn't mandatory.


A unique name describing the action that triggered the event.
See the name
property of the IAnalyticsActionCause
interface.
Example: pagerNext
A name describing the category of actions to which the action that triggered the event belongs.
See the type
property of the IAnalyticsActionCause
interface.
Example: getMoreResults
The name of the collection to which the clicked query result item belongs.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: default
Additional metadata to send along with the event.
Note: This field may include custom user context information (see Sending Custom Context Information).
Example: { "currentResultsPerPage": 25, "userRole": "developer" }
The name of the device or browser that triggered the event.
Note: The framework normally sets this field by parsing the current navigator.userAgent
value.
Example: Chrome
The type of query result item that was clicked.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: FAQ
The 1-based position of the clicked item in the query results set.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
The title of the clicked query result item.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: Coveo ML Frequently Asked Questions
The URI of the clicked query result item.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: http://www.example.com/org:organization/articletype:FAQ/article:aB1c2000000A1BcDEF/language:en_US
The hashed URI of the clicked query result item.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: AbCñdeFghiJKLM1n
The URL of the clicked query result item.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: https://example.com/aB1c2000000A1Bc
The language of the search interface from which the event originates.
Must be a valid ISO-639-1 code.
Note: By default, the framework sets this field according to the currently loaded culture file (see Changing the Language of Your Search Interface).
Example: en
Whether the event originates from a mobile device.
Note: The framework normally sets this field by parsing the current navigator.userAgent
value.
The broad application context from which the event originates.
Note: By default, the framework sets this field to Search
. However, you can use the setOriginContext
method of the Analytics
component to modify the default value.
Example: Search
The identifier of the search interface from which the event originates.
Note: This field is normally set through the searchHub
option of the Analytics
component. However, when actually recording the event, the Coveo Cloud usage analytics service may override this value with information extracted from the search token.
Example: PartnerPortalSearch
The identifier of the tab from which the event originates.
Note: The framework normally sets this field to the identifier of the currently selected Tab
in the search interface.
Example: All
The address of the webpage that linked to the search interface from which the event originates.
Note: The framework normally sets this field to the current document.referrer
value.
Example: http://example.com/
The name of the query pipeline to which the Search API query that returned the clicked result item was routed.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: PartnerPortalSearchPipeline
The ranking modifier that was applied to the clicked query result item.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: Reveal ART
The time it took to get a response from the Search API for the query related to the event (in milliseconds).
Note: The framework normally sets this field to 0
, except for search events in which case it sets the field by retrieving the information from the related Search API query response.
The unique identifier of the Search API query that returned the clicked result item.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: 74682726-0e20-46eb-85ac-f37259346f57
The name of the source that contains the clicked query result item.
Note: The framework normally sets this field by retrieving the information from the related Search API query response.
Example: Product Documentation
The name of the A/B test that applied to the related Search API query.
Note: This field is normally set by the splitTestRunName
option of the Analytics
component. However, if this option is left undefined, the framework attempts to set this field by retrieving information from the related Search API query response.
Example: Testing new ART model
The version of the A/B test that applied to the related Search API query (i.e., version A or version B).
Note: This field is normally set by the splitTestRunVersion
option of the Analytics
component. However, if this option is left undefined and the related Search API query response indicates that an A/B test was applied, the framework sets this field to the name of the query pipeline to which the query was routed.
Example: PartnerPortalSearchPipelineWithART
The software acting on behalf of the end-user whose action triggered the event.
Note: By default, the framework sets this field to the current navigator.userAgent
value.
Example: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36
The display name of the end-user whose action triggered the event.
Note: This field is normally set to the userDisplayName
option value of the Analytics
component. However, when actually recording the event, the Coveo Cloud usage analytics service may override this value with information extracted from the search token.
Example: Alice Smith
The groups the end-user whose action triggered the event belongs to.
Note: This field is normally left undefined, and the Coveo Cloud usage analytics service attempts to extract the information from the search token when actually recording the event.
The identifier of the end-user whose action triggered the event.
Note: This field is normally set to the user
option value of the Analytics
component. However, when actually recording the event, the Coveo Cloud usage analytics service may override this value with information extracted from the search token.
Example<EMAIL_ADDRESS>The way the item was clicked.
Note: The framework normally sets this field to the exact same value as actionCause
.
Example: documentOpen
Describes a Coveo Cloud usage analytics click event.


Cabinet agrees to raise grade UD41 medical officers to UD43, says Dzulkefly
KUALA KRAI, Nov 20 — The Cabinet has basically agreed with the Health Ministry’s proposal to raise the grade of contract medical officers from UD41 to UD43, said Minister Datuk Seri Dr Dzulkefly Ahmad.
“I have presented it to the Cabinet and, in principle, the Cabinet has no problem to approve the proposal and I as the minister concerned will hold discussions with the Finance Ministry and the Public Service Department on the matter,” he told reporters after the opening ceremony of the Sultan Ismail Petra Hospital here today.
The RM286 million hospital was opened by the Sultan of Kelantan, Sultan Muhammad V.
Meanwhile, Dr Dzulkefly confirmed that eight Pasir Puteh Malaysian Maritime Enforcement Agency personnel had suffered from respiratory infections believed to be contracted from Vietnamese fishermen who were recently detained.
“The health problem is, however, under control and the Kelantan Health Department has examined 18 personnel and 45 Vietnamese fishermen and only 19 of them showed symptoms,” he said. — Bernama


{{/* Concert || (Festival && StartDate.Equal(EndDate) */}}
{{if or .Concert (and .Festival (not .Duration)) }}
on
{{end}}
{{if (and .Festival .Duration)}}
from
{{with .StartDate}}
{{end}}
to
{{with .EndDate}}
{{end}}
{{end}}
{{if (not .Solo)}}
{{end}}
{{else}}
Looks like there are no upcoming shows on the calendar. Please check again in the future, or sign up for our mailing list to find out when Run Boy Run will be playing near you.


{%extends 'base.html'%} {%block text%} {%if error%} {{error}} {%endif%} Manage your account service info For now you have {{all_services}} out of 3 services entered {%endblock%} {%block content%}


A place for general developer talk – for everyone! | Documentation https://developers.komodoplatform.com | MoreDev Docs - https://docs.komodoplatform.com | Mastering CryptoConditions - https://github.com/KomodoPlatform/Mastering_CryptoConditions
ok cool, hopefully it will be soon as I need to update our explorer and prepare zelcore in time as well.
SHossain08-Dec-18 11:09 AM
@TheTrunk here is the sapling ready insight explorer sourcce and guide https://github.com/DeckerSU/komodo-explorers-install
We will announce when Komodo source and Agama wallet is ready. Currently we are testing.
Mastering Bitcoin 2nd Edition - Programming the Open Blockchain - bitcoinbook/bitcoinbook
jorian08-Dec-18 05:28 PM
2nd edition is the latest afaik
Anthony08-Dec-18 05:56 PM
Hello developer channel we come in peace
Alright08-Dec-18 06:04 PM
Anthony08-Dec-18 06:04 PM
I and @cYnIx come from the Commercium project, we are looking to swap to Komodo and snapshot the current chain and migrate the pubkey and balance to Komodo. We are also looking to have the chain pow and pos with staking. If anyone can point us in the right direction.
That was generated automatically using getsnapshot rpc on an asset chain. Might be able to port that rpc to your current chain, not sure
@dukeleto is likely a good person to talk to about migrating
Anthony08-Dec-18 06:22 PM
Ok good place to start thanks
aseandude09-Dec-18 01:10 PM
@pbca26 where to find the how to instructions for upgrading my asset chain Koinon for the upcoming Komodo Dec 15 fork? What do I need to do?
Nabob09-Dec-18 01:18 PM
You need to upgrade komodod binaries, so all asset chain has those upgraded code. If you are using Agama for launching your coin. please wait for new release build. Stay tuned to #official📢. @aseandude
Fill out the "Submit New Project" form quickly and securely on Airtable.
we were using it to gather contact info of asset chain devs
aseandude09-Dec-18 01:53 PM
Done. Regards
riddler18k09-Dec-18 07:56 PM
hey guys, if you have multiple assets, how do they talk to each other? anything I can read up on?
Alright09-Dec-18 08:02 PM
@riddler18k there are asset chains which are independent blockchains along with the assets contract which are non-fungible tokens that can be created on the independent blockchains. You're likely referring to the asset chains. They can "talk to each other" via Momom protocol.(merkle root of merkle root of merkle root) Momom data is included with each notarization, so any notarized chain can verify that a transaction happened on any other notarized chain
What's a Merkle Tree? The concept can be a little confusing at first but Komodo Platform's Guide To Understanding Merkle Trees will make it perfectly clear.
riddler18k09-Dec-18 08:06 PM
thanks, is there an equilvant of swarm (eth storage) for KMD?
Komodo is the world's only blockchain platform to offer both security and limitless, on-demand blockchain scalability to every project on the platform.
Not familiar with swarm, not sure what you mean
riddler18k09-Dec-18 08:07 PM
thanks, I read that but didn't click re using it to verify different transactions on different chains!
re swarm.. its file storage... say there is a file i want to store on decentralised storage.... how would I do it on KMD?(edited)
various scripts we have developed on STAKED so far, none of these are perfect and some might not even work. use them as examples of what you can do. - StakedChain/PoS_scripts
it's a rough PoC, but it works
basically, spin up a permissioned chain, "stream" the file to it with that and have notaries notarize it
You can do it on non-permissioned chains, but you'll be limited by block size and time
@riddler18k if you're interested in playing around with that @blackjok3r is the man to talk to. He made it
riddler18k09-Dec-18 08:13 PM
thanks mate
am thinking of who architecture of a project I have in mind
I really like what you guys have done, just trying to understand a few basic things
It's 2mb on every asset chain right now. Changes to 4mb after December 15 hardfork
riddler18k09-Dec-18 08:17 PM
aaah of course sapling
Alright09-Dec-18 08:17 PM
You should be able to create a new parameter to change blocksize then merge that into KMD
or just set it manually and fork
riddler18k09-Dec-18 08:17 PM
and in terms of transaction fee for a chain.... how/where is that set?
Alright09-Dec-18 08:18 PM
do you want to set a minimum?
it's not consensus enforced, miners can choose what they will put into blocks
riddler18k09-Dec-18 08:18 PM
and if it's POS?
Alright09-Dec-18 08:21 PM
It's still set by miner
or staker if that's what you want to call it
Do you want lower or higher fees than default?
riddler18k09-Dec-18 08:25 PM
I was actually thinking of having a flat fee or being able to set that providing i can get all the miners to agree say every year or so(edited)
Alright09-Dec-18 08:36 PM
Is allowing miners decide what they'll put into blocks not going to work with your chain?
that's default behavior, comes from bitcoin
so user can send a tx with no transaction fee, but it won't get confirmed until a miner who is allowing free transactions mines a block
riddler18k09-Dec-18 09:05 PM
oh sorry misunderstood! yep of course standard behaviour, thinking about more on lines of having an asset to manage storage for my platform and how transaction costs would work(edited)
riddler18k09-Dec-18 11:28 PM
Thanks for answering my questions @Alright
Been reading up on interoperability-cross-chain-smart-contracts(edited)
do we have an example of 2 asset chains using MoMoM to verify a transaction?
Alright09-Dec-18 11:30 PM
Stop by #kmdlabs we're launching a fungible cluster of chains. 1 coin many blockchains concept
you can transfer LABS coins between the chains via momom burn protocol
riddler18k09-Dec-18 11:31 PM
ooooh nice thanks
where are you based btw? am from UK
Alright09-Dec-18 11:31 PM
There is gateways contract which uses momom as well
riddler18k09-Dec-18 11:32 PM
anonymous cool beans
seen any example of smart contracts in Java or another lang for KMD?
other than C/C++
Alright09-Dec-18 11:33 PM
Not yet, requires linked libraries to be written
If I knew any C, I'd be working towards a python library
riddler18k09-Dec-18 11:33 PM
lol
Alright09-Dec-18 11:37 PM
There's a lot you can do with existing contracts in any language that can interact with daemon via rpc
Komodo Platform is eliminating the scalability problem for the blockchain industry. Komodo's solution has achieved over 20,000 tx/sec. Learn more here.
D.rabbani10-Dec-18 07:30 AM
hello guys
@blackjok3r i need your help again
fortunately i have got the previous 64 addressess priv keys
i have found that inside the POS splitter
can you please let me know that how do i restore the ballance
as wallet .dat file is corrupted
i mean the priv keys are in List.py
file
the wallet.dat file was corrupted before and it was generating an error i thought about making a new chain
grewalsatinder10-Dec-18 07:32 AM
@radix42 hey mate, can you please resume work on compiling komodod on arm64 ?
best would be to have it buildable like it builds on x64 linux with just ./zcutils/build.sh -j4
D.rabbani10-Dec-18 07:32 AM
camn someone help me out thanks
grewalsatinder10-Dec-18 07:32 AM
CC @Mylo@ca333
@jl777c
just FYI
D.rabbani10-Dec-18 08:16 AM
yes thanks @webworker01 i will do that what do you mean by urprivatekey ?


{% extends 'base.html' %} {% block content %} {% if user %}
Your IP Address is
Accessing from : {{ua}}
a web service by balitechy.com


API documentation¶
pyLARDA main module¶
-
class
pyLARDA.
LARDA
(data_source='local', uri=None)[source]¶ init a new larda instance
Parameters: - data_source (str, optional) – either
'local'
,'remote'
or'filepath'
- uri – link to backend
Returns: larda object
-
connect_local
(camp_name, build_lists=True, filt=None)[source]¶ built the connector list for the specified campaign (only valid systems are considered) the connectors are instances of the Connector.Connector Class
NEW: one connector per system then the params are parts of this system
Parameters: - camp_name (str) – name of campaign as defined in
campaigns.toml
- build_lists (Bool, optional) – Flag to build the filelists or not (with many files this may take some time)
- filt (list, optional) – Filter for name
['system', 'MIRA']
or insturment identifiert['instr_name', 'hatpro_g2_lacros']
- camp_name (str) – name of campaign as defined in
-
read
(system, parameter, time_interval, *further_slices, **kwargs)[source]¶ Parameters: - system (str) – identifier for the system
- parameter (str) – choosen param
- time_interval –
[dt, dt]
time interval, or [dt] one time - *further_slices – range, vel,..
[0, max]
or [3000]
Returns: the dictionary with data
- data_source (str, optional) – either
pyLARDA.Connector¶
-
pyLARDA.Connector.
convert_regex_date_to_dt
(re_date)[source]¶ convert a re_date dict to datetime
Warning
When using 2 digit years (i.e. RPG) a 20 will be added in front
Parameters: re_date (dict) – result of the regex search with keys Returns: datetime
-
pyLARDA.Connector.
convert_to_datestring
(datepattern, f)[source]¶ convert the date in a (file-)string to dt
Parameters: - datepatttern – a python regex definition with named groups
- f – the string
Returns: datetime
-
pyLARDA.Connector.
setup_valid_date_filter
(valid_dates) → Callable[source]¶ validator function for chunks of valid dates
Parameters: valid_dates – list of [begin, end] in ‘YYYYMMDD’ Returns: a single argument (‘YYYYMMDD-HHMMSS’) validator function
-
pyLARDA.Connector.
path_walk
(top, prefilter='.*', topdown=False, followlinks=False)[source]¶ pendant for os.walk
-
pyLARDA.Connector.
guess_end
(dates)[source]¶ estimate the end of a file
Returns: list of pairs [begin, end]
-
class
pyLARDA.Connector.
Connector_remote
(camp_name, system, plain_dict, uri)[source]¶ connect the data (from the a remote source) to larda
Parameters: - camp_name (str) – campaign name
- system (str) – system identifier
- plain_dict (dict) – connector meta info
- uri (str) – address of the remote source
-
collect
(param, time_interval, *further_intervals, **kwargs) → dict[source]¶ collect the data from a parameter for the given intervals
Parameters: - param (str) –
- time_interval – list of begin and end datetime
- *further_intervals – range, velocity, …
- **interp_rg_join – interpolate range during join
Returns: data_container
-
pyLARDA.Connector.
walk_str
(pathinfo)[source]¶ match the names and subdirs with regex using string
only works for unix systems, but is reasonably fast
Parameters: pathinfo – dict Returns: all_files
-
pyLARDA.Connector.
walk_pathlib
(pathinfo)[source]¶ match the names and subdirs with regex using pathlib
should give cross-platform compatability, but comes with a performance penalty (>3x)
Parameters: pathinfo – dict Returns: all_files
-
class
pyLARDA.Connector.
Connector
(system, system_info, valid_dates, description_dir=None)[source]¶ connect the data (from the ncfiles/local sources) to larda
Parameters: - system (str) – system identifier
- system_info (dict) – dict info loaded from toml
- valid_dates (list of lists) – list of begin and end datetime
- description_dir (optional) – dir with the description rst
-
collect
(param, time_interval, *further_intervals, **kwargs) → dict[source]¶ collect the data from a parameter for the given intervals
Parameters: - param (str) –
- time_interval – list of begin and end datetime
- *further_intervals – range, velocity, …
- **interp_rg_join – interpolate range during join
Returns: data_container
-
collect_path
(param, time_interval, *further_intervals, **kwargs) → dict[source]¶ “
Returns: data_container
pyLARDA.helpers¶
-
pyLARDA.helpers.
get_converter_array
(string, **kwargs)[source]¶ colletion of converters that works on arrays combines time, range and varconverters (i see no conceptual separation here)
the maskconverter becomes relevant, if the order is no time, range, whatever (as in mira spec)
chaining example:
`var_conversion = 'z2lin,extrfromaxis2(0)'`
Returns: (varconverter, maskconverter) which both are functions
-
pyLARDA.helpers.
flatten
(xs)[source]¶ flatten inhomogeneous deep lists e.g.
[[1,2,3],4,5,[6,[7,8],9],10]
-
pyLARDA.helpers.
argnearest
(array, value)[source]¶ find the index of the nearest value in a sorted array for example time or range axis
Parameters: - array (np.array) – sorted array with values, list will be converted to 1D array
- value – value to find
Returns: index
-
pyLARDA.helpers.
nearest
(array, pivot)[source]¶ find the nearest value to a given one
Parameters: - array (np.array) – sorted array with values
- pivot – value to find
Returns: value with smallest distance
-
pyLARDA.helpers.
get_extrfromaxis2
(string)[source]¶ get function that extracts given index from axis2
-
pyLARDA.helpers.
fill_with
(array, mask, fill)[source]¶ fill an array where mask is true with fill value
-
pyLARDA.helpers.
guess_str_to_dict
(string)[source]¶ try to convert a text string into a dict intended to be used in the var_def
Returns: dict with flag as key and description string
-
pyLARDA.helpers.
reshape_spectra
(data)[source]¶ This function reshapes time, range and var variables of a data container and returns numpy arrays.
Parameters: data (dict) – data container Returns: list with - ts (numpy.array): time stamp numpy array, dim = (n_time,)
- rg (numpy.array): range stamp numpy array, dim = (n_range,)
- var (numpy.array): values of the spectra numpy array, dim = (n_time, n_range, n_vel)
-
pyLARDA.helpers.
isKthBitSet
(n, k)[source]¶ Function to check if a certain bit of a number is set (required to analyse quality flags)
-
pyLARDA.helpers.
pprint
(data, verbose=False)[source]¶ print a pretty representation of the data container
-
pyLARDA.helpers.
extract_case_from_excel_sheet
(data_loc, sheet_nr=0, **kwargs)[source]¶ This function extracts information from an excel sheet. It can be used for different scenarios. The first row of the excel sheet contains the headline, defined as follows:
A B C D E F G H 1 date start end h0 hend MDF noise_fac notes ORA B C D E F 1 datestart dateend h0 hend noise_fac notes The following rows contain the cases of interest. Make sure that the ALL the data in the excel sheet is formatted as string! The data has to be provided in the following syntax:
- date (string): format YYYYMMDD
- start (string): format HHMMSS
- datestart (string): format YYYYMMDDHHMMSS
- dateend (string): format YYYYMMDDHHMMSS
- end (string): format HHMMSS
- h0 (string): minimum height
- hend (string): maximum height
- MDF (string): name of the MDF used for this case
- noise_fac (string): noise factor
- notes (string): additional notes for the case (stored but not in use by the program)
Parameters: - data_loc (string) – path to the excel file (make sure the data_loc contains the suffix .xlsx)
- sheet_nr (integer) – number of the desired excel sheet
Returns: case_list contains the information for all cases
- begin_dt (datetime object): start of the time interval
- end_dt (datetime object): end of the time interval
- plot_range (list): height interval
- MDF_name (string): name of MDF used for this case
- noisefac (string): number of standard deviations above mean noise level
- notes (string): additional notes for the user
-
pyLARDA.helpers.
interp_only_3rd_dim
(arr, old, new)[source]¶ function to interpolate only the velocity (3rd) axis
-
pyLARDA.helpers.
put_in_container
(data, data_container, **kwargs)[source]¶ This routine will generate a new larda container, replacing var in the data_container given with data
- Kwargs:
- all keys used in larda containers, that is paraminfo (dict): information from params_[campaign].toml for the specific variable rg_unit: range unit mask: ndarray of same size as var, indicating masked values ts: time stamp in unix time var_lims: variable limits colormap: colormap to be used for plotting
Returns: larda data container Return type: container (dict)
-
pyLARDA.helpers.
change_dir
(folder_path, **kwargs)[source]¶ This routine changes to a folder or creates it (including subfolders) if it does not exist already.
Parameters: folder_path (string) – path of folder to switch into
-
pyLARDA.helpers.
make_dir
(folder_path)[source]¶ This routine changes to a folder or creates it (including subfolders) if it does not exist already.
Parameters: folder_path (string) – path of folder to switch into
-
pyLARDA.helpers.
print_traceback
(txt)[source]¶ Print the traceback to an error to screen. :param - txt: error msg :type - txt: string
-
pyLARDA.helpers.
smooth
(y, box_pts, padding='constant')[source]¶ Smooth a one dimensional array using a rectangular window of box_pts points
Parameters: - y (np.array) – array to be smoothed
- box_pts – number of points of the rectangular smoothing window
Returns: smoothed array
Return type: y_smooth (np.arrax)
pyLARDA.NcReader¶
Try to use netcdf4-python
-
pyLARDA.NcReader.
get_time_slicer
(ts: numpy.array, f: str, time_interval: List[datetime.datetime]) → list[source]¶ get time slicer from the time_interval Following options are available
- time_interval with [ts_begin, ts_end]
- only one timestamp is selected and the found right one would be beyond the ts range -> argnearest instead searchsorted
- only one is timestamp
Parameters: - ts – unix timestamps as array
- f – filename
- time_interval – time interval to slice for
Returns: slicer
-
pyLARDA.NcReader.
get_var_attr_from_nc
(name, paraminfo, variable)[source]¶ get the attribute from the variable
Parameters: - name –
- paraminfo –
- variable –
-
pyLARDA.NcReader.
get_meta_from_nc
(ncD, meta_spec, varname)[source]¶ get some meta data into the data_container
specified within the paraminfo meta.name tags - gattr.name: global attribute with name - vattr.name: variable attribute with name - var.name: additional varable (ideally single value)
Parameters: - ncD – netCDF file object
- meta_spec – dict with all meta. definition
- varname – name of the variable to load (for vattr)
Returns: dict with meta data
-
pyLARDA.NcReader.
timeheightreader_rpgfmcw
(paraminfo)[source]¶ build a function for reading in time height data special function for a special instrument ;)
the issues are:
- range variable in different file
- stacking of single variables
for now works only with 3 chirps and range variable only in level0
-
pyLARDA.NcReader.
specreader_rpgfmcw
(paraminfo)[source]¶ build a function for reading in spectral data special function for a special instrument ;)
the issues are:
- range variable in different file
- stacking of single variables
for now works only with 3 chirps and range variable only in level0
-
pyLARDA.NcReader.
scanreader_mira
(paraminfo)[source]¶ reader for the scan files
- load full file regardless of selected time
- covers spec_timeheight and spec_time
-
pyLARDA.NcReader.
interp_only_3rd_dim
(arr, old, new, **kwargs)[source]¶ function to interpolate only the velocity (3rd) axis
-
pyLARDA.NcReader.
specreader_kazr
(paraminfo)[source]¶ build a function for reading in spectral data another special function for another special instrument ;)
the issues are:
- variables time and range are merged and can be accessed by a locator mask
- noise is not saved and has to be computed from the spectra
- spectra are not in reflectivity but in 10*log10(mW)
- need to be converted using specZ = spec * h.z2lin(float(f.cal_constant[:-3])) * self.range[ir]**2
-
pyLARDA.NcReader.
reader_pollyraw
(paraminfo)[source]¶ build a function for reading in the polly raw data into larda
pyLARDA.NcWrite¶
pyLARDA.ParameterInfo¶
-
pyLARDA.ParameterInfo.
deep_update
(source, overrides)[source]¶ Update a nested dictionary. Only additions, no removal modify
source
in place.
-
pyLARDA.ParameterInfo.
select_matching_template
(syskey, templates, fname)[source]¶ templates either match by exact name or regex in also_match
Example
in a template ``` [CLOUDNET]
also_match = “CLOUDNET_.+” [CLOUDNET.generic] …` also matches ``CLOUDNET_LIMRAD
-
pyLARDA.ParameterInfo.
check_filter
(filter, config)[source]¶ filter for a specific key in the config file, i.e. instr_name, instr_id, …
Parameters: - filter – dict with name (instr_name) and matching value (MIRA_NMRA)
- config – dict loaded from the config file
Returns: True or False
TODO: maybe at one point we will need path level filtering
-
pyLARDA.ParameterInfo.
do_parameter_generic_inheritance
(config, cinfo_hand_down={})[source]¶ inhert the parameter.generic information to the single variables
Parameters: - config (dict) – config dict as read from toml
- cinfo_hand_down (dict, optional) – campaign information to inherit
Returns: config


ABSTRACT
smaller header
smallest header
bla bla intro
Function
An
abstract
is a
summary
.
Click here for Google
Click here for page 2
list item 1
list item 2
first one
second one
2a
2a-i
2a-ii
2b
third one


Dorky Meter
Answer these questions below you humans...
Q1. Do you watch Anime?
Q2. Do you play videogames?
Q3. Have you built your own computer?
Q4. Do you like riddles?
Q5. Do you watch science videos on YouTube?
Q6. Do you know what numbers come after 3.14?
Q7. Do you have more than 1 monitor?
Q8. Do you like comics or Manga?
Q9. Do you talk to yourself time to time?
Q10. Do you know any programming languages?
Click here to see the result


Description:
|
Core Security Technologies Advisory - The Firebird database manager contains an integer overflow in the processing of certain tags on the XDR protocol used for communication with the server. Version vulnerable include Firebird SQL 1.0.3 and before, 1.5.5 and before, 2.0.3 and before, and 2.1.0 Beta 2 and before.
|


--- permalink: / layout: default ---
Build cross platform desktop apps with JavaScript, HTML, and CSS
If you can build a website, you can build a desktop app. Electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.
Electron uses Chromium and Node.js so you can build your app with HTML, CSS, and JavaScript.
Electron is an open source project maintained by GitHub and an active community of contributors.
Compatible with Mac, Windows, and Linux, Electron apps build and run on three platforms.
To get started with Electron, check out the resources below. Learn how to wrap your web app with Electron, access all the APIs, and generate installers.
The Electron API Demos app interactively demonstrates the most important features of the Electron API. See what's possible with Electron with sample code and helpful tips for building your app.
A minimal Electron app with helpful notations.
Ask questions in the Discuss forum or our Slack channel. Follow @{{ site.twitter_username }} on Twitter for important announcements. Need to privately reach out? Email<EMAIL_ADDRESS>With Electron, creating a desktop application for your company or idea is easy. Initially developed for GitHub's Atom editor, Electron has since been used to create applications by companies like Microsoft, Facebook, Slack, and Docker.


---
layout: archive
title: Lean Prover Zulip Chat Archive
permalink: 113489newmembers/05853Proofsearch.html
---
The archive URL format has changed. Please find this page at:
https://leanprover-community.github.io/archive/stream/113489-new-members/topic/Proof.20search.html


Introduction
Welcome to the Wolves privacy notice.
Wolves respects your privacy and is committed to protecting your personal data. This privacy notice will inform you as to how we look after your personal data when you visit our website (regardless of where you visit it from) and tell you about your privacy rights and how the law protects you.
This privacy notice is provided in a layered format so you can click through to the specific areas set out below. Alternatively, you can download a pdf version of the policy here. Please also use the Glossary to understand the meaning of some of the terms used in this privacy notice.
 Important information and who we are
Purpose of this privacy notice
This privacy notice aims to give you information on how Wolves collects and processes your personal data through your use of this website, including any data you may provide through this website when you sign up to our newsletter or purchase a product or service or take part in a competition or play a game or engage in a chat forum or watch our video services.
It is important that you read this privacy notice together with any other privacy notice or fair processing notice we may provide on specific occasions when we are collecting or processing personal data about you so that you are fully aware of how and why we are using your data. This privacy notice supplements the other notices and is not intended to override them.
Controller
Wolverhampton Wanderers Football Club Limited is the controller and responsible for your personal data (collectively referred to as "Wolves", "we", "us" or "our" in this privacy notice).
We have appointed a data protection officer (DPO) who is responsible for overseeing questions in relation to this privacy notice. If you have any questions about this privacy notice, including any requests to exercise your legal rights, please contact the DPO using the details set out below.
Contact details
Our full details are:
Full name of legal entity: Wolverhampton Wanderers Football Club Limited
Name or title of DPO: Matt Wild, Club Secretary
Email address<EMAIL_ADDRESS>Postal address: DPO, Wolverhampton Wanderers Football Club, 67 Waterloo Rd, Wolverhampton WV1 4QR
Telephone number: 0871 222 2220
Changes to the privacy notice and your duty to inform us of changes
This version was last updated on 21st May, 2018 and historic versions can be obtained by contacting us.
The data protection law in the UK will change on 25 May 2018. Although this privacy notice sets out most of your rights under the new laws, we may not yet be able to respond to some of your requests (for example, a request for the transfer of your personal data) until May 2018 as we are still working towards getting our systems ready for some of these changes.
It is important that the personal data we hold about you is accurate and current. Please keep us informed if your personal data changes during your relationship with us.
Third-party links and social media
This website may include links to third-party websites, plug-ins and applications. Clicking on those links or enabling those connections may allow third parties to collect or share data about you.
We have a social media presence for the purpose of engaging with our fans.
If you enable such connections or choose to communicate your personal data to us via third-party websites or social media, please remember that we do not control these third-party websites and are not responsible for their privacy statements. When you leave our website or interact with us on social media, we encourage you to read the privacy notice of every website of forum that you visit or use.
2. The data we collect about you
Personal data, or personal information, means any information about an individual from which that person can be identified. It does not include data where the identity has been removed (anonymous data).
We may collect, use, store and transfer different kinds of personal data about you which we have grouped together follows:
- Identity Data includes first name, maiden name, last name, username or similar identifier, marital status, title, age, date of birth and gender.
- Contact Data includes billing address, delivery address, email address and telephone numbers.
- Financial Data includes bank account and payment card details.
- Transaction Data includes details about payments to and from you and other details of products and services you have purchased from us.
- Technical Data includes internet protocol (IP) address, your login data, browser type and version, time zone setting and location, browser plug-in types and versions, operating system and platform and other technology on the devices you use to access this website.
- Profile Data includes your username and password, purchases or orders made by you, your interests, occupation, preferences, feedback and survey responses.
- Usage Data includes information about how you use our website, products and services.
- Marketing and Communications Data includes your preferences in receiving marketing from us and our third parties and your communication preferences.
We also collect, use and share Aggregated Data such as statistical or demographic data for any purpose. Aggregated Data may be derived from your personal data but is not considered personal data in law as this data does not directly or indirectly reveal your identity. For example, we may aggregate your Usage Data to calculate the percentage of users accessing a specific website feature. However, if we combine or connect Aggregated Data with your personal data so that it can directly or indirectly identify you, we treat the combined data as personal data which will be used in accordance with this privacy notice.
We do not collect any Special Categories of Personal Data about you (this includes details about your race or ethnicity, religious or philosophical beliefs, sex life, sexual orientation, political opinions, trade union membership, information about your health and genetic and biometric data) nor do we collect any information about criminal convictions and offences without your explicit opt in consent.
If you fail to provide personal data
Where we need to collect personal data by law, or under the terms of a contract we have with you and you fail to provide that data when requested, we may not be able to perform the contract we have or are trying to enter into with you (for example, to provide you with goods or services). In this case, we may have to cancel a product or service you have with us but we will notify you if this is the case at the time.
3. How is your personal data collected?
We use different methods to collect data from and about you including through:
- Direct interactions. You may give us your Identity, Contact and Financial Data by filling in forms or by corresponding with us by post, phone, email or otherwise. This includes personal data you provide when you:
- apply for our products or services;
- create an account on our website;
- subscribe to our service or publications;
- request marketing to be sent to you;
- enter a competition, promotion or survey;
- engage in a chat forum;
- or watch our video services; or
- give us some feedback.
- Automated technologies or interactions. As you interact with our website, we may automatically collect Technical Data about your equipment, browsing actions and patterns. We collect this personal data by using cookies, server logs and other similar technologies. We may also receive Technical Data about you if you visit other websites employing our cookies. Please see our cookies policy for further details.
- Third parties or publicly available sources. We may receive personal data about you from various third parties and public sources as set out below.
- Technical Data from the following parties:
(a) analytics providers such as Google based outside the EU;
(b) advertising networks such as affiliate window based inside OR outside the EU; and
(c) search information providers such as Yahoo based inside OR outside the EU - Contact, Financial and Transaction Data from providers of technical, payment and delivery services based inside OR outside the EU.
- Identity and Contact Data from data brokers or aggregators such as Experian based inside OR outside the EU.
- Identity and Contact Data from publicly availably sources such as Companies House and the Electoral Register based inside the EU
4. How we use your personal data
We will only use your personal data when the law allows us to. Most commonly, we will use your personal data in the following circumstances:
- Where we need to perform the contract we are about to enter into or have entered into with you.
- Where it is necessary for our legitimate interests (or those of a third party) and your interests and fundamental rights do not override those interests.
- Where we need to comply with a legal or regulatory obligation.
Click here to find out more about the types of lawful basis that we will rely on to process your personal data.
Generally, we do not rely on consent as a legal basis for processing your personal data other than in relation to sending third party direct marketing communications to you via email or text message. You have the right to withdraw consent to marketing at any time by contacting the DPO.
Purposes for which we will use your personal data
We have set out below, in a table format, a description of all the ways we plan to use your personal data, and which of the legal bases we rely on to do so. We have also identified what our legitimate interests are where appropriate.
Note that we may process your personal data for more than one lawful ground depending on the specific purpose for which we are using your data. Please contact the DPO if you need details about the specific legal ground we are relying on to process your personal data where more than one ground has been set out in the table below.
|
Purpose/Activity |
Type of data |
Lawful basis for processing including basis of legitimate interest |
|
To register you as a new customer |
(a) Identity (b) Contact |
Performance of a contract with you |
|
To process and deliver your order including: (a) Manage payments, fees and charges (b) Collect and recover money owed to us |
(a) Identity (b) Contact (c) Financial (d) Transaction (e) Marketing and Communications |
(a) Performance of a contract with you (b) Necessary for our legitimate interests (to recover debts due to us) |
|
To manage our relationship with you which will include: (a) Notifying you about changes to our terms or privacy policy (b) Asking you to leave a review or take a survey |
(a) Identity (b) Contact (c) Profile (d) Marketing and Communications |
(a) Performance of a contract with you (b) Necessary to comply with a legal obligation (c) Necessary for our legitimate interests (to keep our records updated and to study how customers use our products/services) |
|
To enable you to partake in a prize draw, competition or complete a survey |
(a) Identity (b) Contact (c) Profile (d) Usage (e) Marketing and Communications |
(a) Performance of a contract with you (b) Necessary for our legitimate interests (to study how customers use our products/services, to develop them and grow our business) |
|
To administer and protect our business and this website (including troubleshooting, data analysis, testing, system maintenance, support, reporting and hosting of data) |
(a) Identity (b) Contact (c) Technical |
(a) Necessary for our legitimate interests (for running our business, provision of administration and IT services, network security, to prevent fraud and in the context of a business reorganisation or group restructuring exercise) (b) Necessary to comply with a legal obligation |
|
To deliver relevant website content and advertisements to you and measure or understand the effectiveness of the advertising we serve to you |
(a) Identity (b) Contact (c) Profile (d) Usage (e) Marketing and Communications (f) Technical |
Necessary for our legitimate interests (to study how customers use our products/services, to develop them, to grow our business and to inform our marketing strategy) |
|
To use data analytics to improve our website, products/services, marketing, customer relationships and experiences |
(a) Technical (b) Usage |
Necessary for our legitimate interests (to define types of customers for our products and services, to keep our website updated and relevant, to develop our business and to inform our marketing strategy) |
|
To make suggestions and recommendations to you about goods or services that may be of interest to you |
(a) Identity (b) Contact (c) Technical (d) Usage (e) Profile |
Necessary for our legitimate interests (to develop our products/services and grow our business) |
Marketing
We strive to provide you with choices regarding certain personal data uses, particularly around marketing and advertising. We have established a privacy centre where you can view and make certain decisions about your personal data. You can access the centre via a link on every email that we send you or by logging in to www.wolves.co.uk
Promotional offers from us
We may use your Identity, Contact, Technical, Usage and Profile Data to form a view on what we think you may want or need, or what may be of interest to you. This is how we decide which products, services and offers may be relevant for you (we call this marketing).
You will receive marketing communications from us if you have requested information from us or purchased goods or services from us or if you provided us with your details when you entered a competition or registered for a promotion and, in each case, you have not opted out of receiving that marketing.
Third-party marketing
We will get your express opt-in consent before we share your personal data with any company outside the Wolves group of companies for marketing purposes.
Opting out
You can ask us or third parties to stop sending you marketing messages at any time by logging into the website and checking or unchecking relevant boxes to adjust your marketing preferences or by following the opt-out links on any marketing message sent to you or by contacting the DPO at any time.
Where you opt out of receiving these marketing messages, this will not apply to personal data provided to us as a result of a product/service purchase, warranty registration, product/service experience or other transactions.
Cookies
You can set your browser to refuse all or some browser cookies, or to alert you when websites set or access cookies. If you disable or refuse cookies, please note that some parts of this website may become inaccessible or not function properly. For more information about the cookies we use, please see here
Change of purpose
We will only use your personal data for the purposes for which we collected it, unless we reasonably consider that we need to use it for another reason and that reason is compatible with the original purpose. If you wish to get an explanation as to how the processing for the new purpose is compatible with the original purpose, please contact the DPO.
If we need to use your personal data for an unrelated purpose, we will notify you and we will explain the legal basis which allows us to do so.
Please note that we may process your personal data without your knowledge or consent, in compliance with the above rules, where this is required or permitted by law.
5. Disclosures of your personal data
We may have to share your personal data with the parties set out below for the purposes set out in the table in paragraph 4 above.
- Internal Third Parties as set out in the glossary.
- External Third Parties as set out in the glossary.
- Specific third parties as listed here.
- Third parties to whom we may choose to sell, transfer, or merge parts of our business or our assets. Alternatively, we may seek to acquire other businesses or merge with them. If a change happens to our business, then the new owners may use your personal data in the same way as set out in this privacy notice.
We require all third parties to respect the security of your personal data and to treat it in accordance with the law. We do not allow our third-party service providers to use your personal data for their own purposes and only permit them to process your personal data for specified purposes and in accordance with our instructions.
6. International transfers
We do not transfer your personal data outside the European Economic Area (EEA).
7. Data security
We have put in place appropriate security measures to prevent your personal data from being accidentally lost, used or accessed in an unauthorised way, altered or disclosed. In addition, we limit access to your personal data to those employees, agents, contractors and other third parties who have a business need to know. They will only process your personal data on our instructions and they are subject to a duty of confidentiality.
We have put in place procedures to deal with any suspected personal data breach and will notify you and any applicable regulator of a breach where we are legally required to do so.
All integrations via SFTP file transfer or API direct from partner systems are fully encrypted and secure. If we need to do ad-hoc data transfers, we use a secure cloud folder for storing and transferring files and data
8. Data retention
How long will you use my personal data for?
We will only retain your personal data for as long as necessary to fulfil the purposes we collected it for, including for the purposes of satisfying any legal, accounting, or reporting requirements.
To determine the appropriate retention period for personal data, we consider the amount, nature, and sensitivity of the personal data, the potential risk of harm from unauthorised use or disclosure of your personal data, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal requirements.
Details of retention periods for different aspects of your personal data are available in our retention policy which you can request from us by contacting the DPO.
By law we have to keep basic information about our customers (including Contact, Identity, Financial and Transaction Data) for six years after they cease being customers for tax purposes.
In some circumstances you can ask us to delete your data: see below for further information.
In some circumstances we may anonymise your personal data (so that it can no longer be associated with you) for research or statistical purposes in which case we may use this information indefinitely without further notice to you.
9. Your legal rights
Under certain circumstances, you have rights under data protection laws in relation to your personal data. Please click on the links below to find out more about these rights:
- Request access to your personal data
- Request correction of your personal data
- Request erasure of your personal data
- Object to processing of your personal data
- Request restriction of processing your personal data
- Request transfer of your personal data
Right to withdraw consent
You have the right to make a complaint at any time to the Information Commissioner's Office (ICO), the UK supervisory authority for data protection issues (www.ico.org.uk). We would, however, appreciate the chance to deal with your concerns before you approach the ICO so please contact us in the first instance. If you wish to exercise any of the rights set out above, please contact the DPO on email at<EMAIL_ADDRESS>by telephone on 0871 222 2220 or by post at DPO, Wolverhampton Wanderers Football Club, 67 Waterloo Rd, Wolverhampton WV1 4QR
No fee usually required
You will not have to pay a fee to access your personal data (or to exercise any of the other rights). However, we may charge a reasonable fee if your request is clearly unfounded, repetitive or excessive. Alternatively, we may refuse to comply with your request in these circumstances.
What we may need from you
We may need to request specific information from you to help us confirm your identity and ensure your right to access your personal data (or to exercise any of your other rights). This is a security measure to ensure that personal data is not disclosed to any person who has no right to receive it. We may also contact you to ask you for further information in relation to your request to speed up our response.
Time limit to respond
We try to respond to all legitimate requests within one month. Occasionally it may take us longer than a month if your request is particularly complex or you have made a number of requests. In this case, we will notify you and keep you updated.
10. Glossary
LAWFUL BASIS
Legitimate Interest means the interest of our business in conducting and managing our business to enable us to give you the best service/product and the best and most secure experience. We make sure we consider and balance any potential impact on you (both positive and negative) and your rights before we process your personal data for our legitimate interests. We do not use your personal data for activities where our interests are overridden by the impact on you (unless we have your consent or are otherwise required or permitted to by law). You can obtain further information about how we assess our legitimate interests against any potential impact on you in respect of specific activities by contacting the DPO.
Performance of Contract means processing your data where it is necessary for the performance of a contract to which you are a party or to take steps at your request before entering into such a contract.
Comply with a legal or regulatory obligation means processing your personal data where it is necessary for compliance with a legal or regulatory obligation that we are subject to.
THIRD PARTIES
External Third Parties
- Service providers acting as processors who provide IT and system administration services.
- Professional advisers acting as processors or joint controllers including lawyers, bankers, auditors and insurers who provide consultancy, banking, legal, insurance and accounting services.
- HM Revenue & Customs, regulators and other authorities acting as processors or joint controllers who require reporting of processing activities in certain circumstances.
YOUR LEGAL RIGHTS
You have the right to:
Request access to your personal data (commonly known as a "data subject access request"). This enables you to receive a copy of the personal data we hold about you and to check that we are lawfully processing it.
Request correction of the personal data that we hold about you. This enables you to have any incomplete or inaccurate data we hold about you corrected, though we may need to verify the accuracy of the new data you provide to us.
Request erasure of your personal data. This enables you to ask us to delete or remove personal data where there is no good reason for us continuing to process it. You also have the right to ask us to delete or remove your personal data where you have successfully exercised your right to object to processing (see below), where we may have processed your information unlawfully or where we are required to erase your personal data to comply with local law. Note, however, that we may not always be able to comply with your request of erasure for specific legal reasons which will be notified to you, if applicable, at the time of your request.
Object to processing of your personal data where we are relying on a legitimate interest (or those of a third party) and there is something about your particular situation which makes you want to object to processing on this ground as you feel it impacts on your fundamental rights and freedoms. You also have the right to object where we are processing your personal data for direct marketing purposes. In some cases, we may demonstrate that we have compelling legitimate grounds to process your information which override your rights and freedoms.
Request restriction of processing of your personal data. This enables you to ask us to suspend the processing of your personal data in the following scenarios: (a) if you want us to establish the data's accuracy; (b) where our use of the data is unlawful but you do not want us to erase it; (c) where you need us to hold the data even if we no longer require it as you need it to establish, exercise or defend legal claims; or (d) you have objected to our use of your data but we need to verify whether we have overriding legitimate grounds to use it.
Request the transfer of your personal data to you or to a third party. We will provide to you, or a third party you have chosen, your personal data in a structured, commonly used, machine-readable format. Note that this right only applies to automated information which you initially provided consent for us to use or where we used the information to perform a contract with you.
Withdraw consent at any time where we are relying on consent to process your personal data. However, this will not affect the lawfulness of any processing carried out before you withdraw your consent. If you withdraw your consent, we may not be able to provide certain products or services to you. We will advise you if this is the case at the time you withdraw your consent.
11. Cookies Policy
Site tracking & cookies
When visiting our website, we would like to use "cookies" and other tracking technologies which record information and data automatically.
What are cookies?
"Cookies" are small text files stored on your "browser" on your computer's hard drive, which collect basic information, but not personally identifying information, that a website can use to recognize repeat site visits. Cookies send information stored on them back to our webserver when you access our website.
Cookies enable Wolves to provide features such as remembering your address, so that you do not have to re-enter it each time you use the website. Cookies do not attach to your system or damage your files.
Removing cookies
Cookies can be deleted from your hard drive if you wish. Most web browsers automatically accept cookies. You can usually change your browser so that it will not accept cookies. If you do this, you will still be able to browse around the site and use most of the features on the website but the functions that allow you to add items to your trolley, set up a new account or access an existing account will not be available. Alternatively, you can adjust your browser to tell you when a website tries to put a cookie on your computer. How you adjust your browser to stop it accepting cookies or to notify you of them will depend on the type of internet browser programme, which your computer uses.
If your computer uses Microsoft Internet Explorer or Netscape Navigator, you will need to follow these instructions at this link www.allaboutcookies.org (Wolves is not responsible for the content of external websites.)
Go to the heading "Manage Cookies". Click onto the option you prefer, either stopping cookies being installed or notifying you of them. From the list provided, click onto the programme, which your computer uses. If this is not shown on the list, click on the "help" heading on the bar at the top of this page, search for information on "cookies" - an explanation of how to delete cookies will appear, then follow those instructions.
If we cannot use such technology it is possible that certain functionality or 'personalised' services of this site might be affected and you might not be able to access certain Webpages. This information does not identify you personally.
What information do we collect?
We automatically collect and store only the following information about your visit:-
- the internet domain and IP address from where you access our Website;
- the type of browser software and operating system used to access our Website;
- the date and time you access our Website;
- the pages you enter, visit and exit our Website from; and
- if you linked to our Website from another Website, the address of that Website.
Why do we collect this information?
We use this information to help us identify click stream patterns, to compile aggregate data in order to observe behaviour and to improve our Website, to learn about the number of visitors to our Website, the types of technology our visitors use, to target the advertising and to assess the general effectiveness of such advertising.
We only use this information to ensure that our Webpages stay compatible with a selection of browsers and systems and thereby ensure that the pages appeal to a wide audience.
Currently our Webpages are optimised for the following Internet browsers: Internet Explorer 8.0+, Firefox, Safari, Chrome and native browsers on mobile devices and tablets.
We do not use cookies to collect or store personal information such as your name or email address.
Third party advertising cookies
Some of the advertisements you see on this site are generated by third parties. Some of these third parties generate their own "anonymous cookies", for the same reasons we do: to track how many unique users have seen a particular ad, and how many times they have seen it.
These third party cookies cannot be used to identify an individual user, but only for statistical purposes, for example, in providing you with advertisements that are more relevant to your interests. Additionally, the companies that generate these cookies have their own, very strict, privacy policies but we don't have access to these cookies; other than allowing them to be served, we have no role to play in these cookies at all (although we may use statistical information arising from these third party cookies and provided to us by third parties, to improve the targeting of advertisements to users).
List of cookies on www.wolves.co.uk
|
Cookie Name |
Purpose |
|
_ga _gat_UA-100320797-1 _gid |
Cookies related to Google Analytics which facilitate tracking information about how the website is being used, e.g. number of users. |
|
cookie-accept _sa_sso_upid wwfc_name wwfc_token _RequestVerificationToken |
Cookies associated with login and sign on for the website. |
Cookies set by third-party on login.wolves.co.uk
|
_ga _gat_UA-100320797-1 _gid |
Cookies set by 3rd Party provider on login.wolves.co.uk for Google Analytics which facilitate tracking information about how the website login is being used, e.g. number of users. |
|
_RequestVerificationToken _sa_sso_referringtenantid _sa_sso_returnvisitorurl _sa_sso_successredirecturl _sa_sso_upid _sa_sso_session |
Cookies set by 3rd Party provider on login.wolves.co.uk to enable the handshake for a personalised experience for fans when they login to the site. Ability to reveal Hi ‘Name’ and link to the fan’s account details once logged in. |
Consent to cookies
In using this website, and by submitting your information, you consent to the collection, storage and use of your personal information by us as set out in this Cookies Policy.
If you do not agree, please leave this website now.


|
Auto-update: Enables or disables auto updating of this intersection when changing options.
Gizmo: Enables or disables most gizmo drawing on all objects related to this intersection.
Intersection turn lane options:
No turn lanes: Creates an intersection with no turn lanes.
Left turn lane only: Creates an intersection with a left turn lane.
Both turn lanes: Creates an intersection with left turn and right turn lanes.
Left yield on green: If checked, replaces the standard 3-light left turn light with a five-light yield on green left turn signal structure and sign.
Street lights: If checked, attaches street lights to each intersection pole. Point lights optional and can be manipulated in the next option segment.
Gray color: If checked, sets the traffic light pole base materials to gray galvanized steel. If unchecked the material used is black metal paint.
Normal pole alignment: Recommended to keep this option on unless abnormal twisting of light objects is occurring. Turn this option off if the roads immediately surrounding your intersection are curved at extreme angles and cause irregular twisting of the traffic light objects. Turning this option off will attempt to align the poles perpendicular to the adjacent relevant road without any part existing over the main intersection bounds.
Point lights: Enabled means that point lights for the traffic lights (and street lights, if enabled) will be turned on. This is accessible via script \"bLightsEnabled\"
If street pole lights enabled: Street light range, intensity and color: These settings directly correlate to the standard point light settings.
Traffic light scale sensitivity: Increasing this value will increase the scaling sensitivity relative to the size of the intersection. Higher scaling value = bigger traffic lights at further distances. Default value is 170.
Grade correction: If using extreme road grades immediately surrounding the intersection, terrain height matching errors may occur at the point of road expansion leading to the intersection.
Raise this value if you see terrain poking through the road at the road expansion areas.
Lower this value if you are not using road mesh colliders and notice dips at the expansion points.
Default value is 0.375 meters, which is the maximum value for a linear range of 0% to 20% grade.
Recommended to keep grades and angles small leading up to intersections.
= Reset to default value.
|


zfs
Manage ZFS filesystems.
More information: home page
- List all available zfs filesystems:
zfs list
- Create a new ZFS filesystem:
zfs create pool_name/filesystem_name
- Delete a ZFS filesystem:
zfs destroy pool_name/filesystem_name
- Create a Snapshot of a ZFS filesystem:
zfs snapshot pool_name/filesystem_name@snapshot_name
- Enable compression on a filesystem:
zfs set compression=on pool_name/filesystem_name
- Change mountpoint for a filesystem:
zfs set mountpoint=/my/mount/path pool_name/filesystem_name


Click the button below to begin tracking!
An equilateral triangle is a triangle whose three sides all have exactly the same length.
An isosceles triangle is a triangle that has (at least) two equal side lengths.
A scalene triangle is a triangle tha meets minimum triangle's criteria that is; No side can be equal or greater than the sum of the other two sides in which case, the shape is not a triangle.


SmackDaddy Pizza is the place to go for delicious pizza
Please Choose the following toppings:
You've ordered a pizza, please click here for order details.
Toppings:
Price: $


Dear participant,
you receive this e-mail to confirm your participation. Below you will find a confirmation token. Please keep this token save as this token can be used to register yourself again on a different mobile device.
Best regards,
Research Team


Inbox
-
Lucas Kriebel (via Twitter)
Lucas Kriebel (@LucasKriebel) has sent you a direct message on Twitter! –11:49 am -
Conceptboard
Please complete your Conceptboard signup –11:45 am -
Randy, me (5)
Last pic over my village –5:01 am -
Andrew Zimmer
Mochila Beta: Subscription Confirmed –Mar 8 -
Infinity HR
Sveriges Hetaste sommarjobb –Mar 8 -
Web Support Dennis
Re: New mail settings –Mar 7 -
me, Peter (2)
Off on Thursday –Mar 4 -
Medium
This Week's Top Stories –Feb 28 -
Death to Stock
Montly High-Res Photos –Feb 28 -
Revibe
Weekend on Revibe –Feb 27 -
Erik, me (5)
Regarding our meeting –Feb 24 -
KanbanFlow
Task assigned: Clone ARP's website –Feb 24 -
Tobias Berggren
Let's go fishing! –Feb 23 -
Charukaw, me (7)
Hey man –Feb 23 -
me, Peter (5)
Home again! –Feb 21 -
Stack Exchange
1 new items in your Stackexchange inbox –Feb 21 -
Google Drive Team
You can now use your storage in Google Drive –Feb 20 -
me, Susanna (11)
Train/Bus –Feb 19 -
Peter, me (3)
Hello –Mar. 6 -
me, Susanna (7)
Since you asked... and i'm inconceivably bored at the train station –Mar. 6


{% extends "base.html"%} {%block title%}PCap Files{%endblock%} {%block location%}
Home -> PCap Files
Select your PCap file.


---
layout: post
title: ! 'RailsConf: 65% 80% of the seats sold!'
categories:
- sightings
author: David
published: true
date: 2006-02-06 16:52:00.000000000 +00:00
---
RailsConf was announced less than a week ago and the seats are going faster than snappy quick. Of the 400 tickets for sale, 265 were gone as of this morning. That’s 65% sold or just 135 left.
I’d be very surprised if we still had any tickets left by the end of the week. This is shaping up to be the exclusive event of the year, so if you don’t want to regret participating in that, you’d better secure yourself a ticket before it’s too late.
The conference panel is currently judging the more than 80(!) talk proposals and the final schedule will hopefully be announced some times next week.
UPDATE: 80% of the tickets are now gone.


My Diary
Home
Welcome to the place of peace and tranquility
Pin down your thoughts
Date
Entry
Edit
Modify
27/02/2018
Entry 1
The day was sad and gloomy....
Modify/Edit