API for Techfesia.
curl -X GET -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/users/test_user_001/auth_modes"
GET /users/test_user_001/auth_modes HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_token" -d '{
"password":"Hello World"
}' "http://localhost:8000/users/test_user_001/password/"
POST /users/test_user_001/password/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_token
{
"password":"Hello World"
}
| Status | 201 Created |
|---|---|
|
curl -X PUT -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_token" -d '{
"oldPassword":"old_passord",
"newPassword":"new_password"
}' "http://localhost:8000/users/test_user_001/password/"
PUT /users/test_user_001/password/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_token
{
"oldPassword":"old_passord",
"newPassword":"new_password"
}
curl -X PATCH -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"resetToken":"sampled_reset_token",
"newPassword":"password"
}' "http://localhost:8000/users/test_user_001/password/"
PATCH /users/test_user_001/password/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"resetToken":"sampled_reset_token",
"newPassword":"password"
}
| Status | 200 OK |
|---|---|
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
curl -X GET -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/users?limit=10"
GET /users?limit=10 HTTP/1.1
Host: localhost:8000
Accept: application/json
Content-Type: application/json
Authorization: Bearer sample_staff_token
| Status | 400 Bad Request |
|---|---|
| Content-Type | application/json |
|
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X GET -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/users/test_user_001"
GET /users/test_user_001 HTTP/1.1
Host: localhost:8000
Accept: application/json
Content-Type: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X GET -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/users/test_user_001/privileges"
GET /users/test_user_001/privileges HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
| Status | 200 OK |
|---|---|
|
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"username":"test_user_001",
"firstName":"Test",
"lastName":"User",
<EMAIL_ADDRESS>"password":"Hello World",
"phoneNumber":"+911234567890",
"collegeName":"Test College 123",
"profilePicture":"url_to_profile_pic"
}' "http://localhost:8000/users/"
POST /users/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"username":"test_user_001",
"firstName":"Test",
"lastName":"User",
<EMAIL_ADDRESS>"password":"Hello World",
"phoneNumber":"+911234567890",
"collegeName":"Test College 123",
"profilePicture":"url_to_profile_pic"
}
| Status | 201 Created |
|---|---|
| Content-Type | application/json |
|
| Status | 400 Bad Request |
|---|---|
| Content-Type | application/json |
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
curl -X PUT -H "Content-Type: application/json" -H "accept: application/json" -H "Authorization: Bearer sample_token" -d '{
"username":"test_user_001",
"firstName":"Test",
"lastName":"User",
<EMAIL_ADDRESS>"phoneNumber":"+911234567890",
"collegeName":"Test College 123",
"profilePicture":"url_to_profile_pic"
}' "http://localhost:8000/users/test_user_001?="
PUT /users/test_user_001?= HTTP/1.1
Host: localhost:8000
Content-Type: application/json
accept: application/json
Authorization: Bearer sample_token
{
"username":"test_user_001",
"firstName":"Test",
"lastName":"User",
<EMAIL_ADDRESS>"phoneNumber":"+911234567890",
"collegeName":"Test College 123",
"profilePicture":"url_to_profile_pic"
}
| Status | 200 OK |
|---|---|
|
curl -X PUT -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_token" -d '{
"provider":"google"
}' "http://localhost:8000/users/test_user_001/picture"
PUT /users/test_user_001/picture HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_token
{
"provider":"google"
}
| Status | 200 OK |
|---|---|
|
curl -X PUT -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/users/test_user_001/disable"
PUT /users/test_user_001/disable HTTP/1.1
Host: localhost:8000
Authorization: Bearer sample_staff_token
curl -X DELETE -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/users/test_user_001/"
DELETE /users/test_user_001/ HTTP/1.1
Host: localhost:8000
Authorization: Bearer sample_staff_token
| Status | 200 OK |
|---|
curl -X PUT -H "Accept: application/json" -H "Content-Type: multipart/form-data" -H "Authorization: Bearer sample_token" "http://localhost:8000/users/test_user_001/pictureupload"
PUT /users/test_user_001/pictureupload HTTP/1.1
Host: localhost:8000
Accept: application/json
Content-Type: multipart/form-data
Authorization: Bearer sample_token
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
| Status | 202 Accepted |
|---|---|
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"username":"test_user_001",
"password":"Hello World"
}' "http://localhost:8000/auth/token/"
POST /auth/token/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"username":"test_user_001",
"password":"Hello World"
}
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"refresh":"sample_token"
}' "http://localhost:8000/auth/token/refresh/"
POST /auth/token/refresh/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"refresh":"sample_token"
}
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"username":"test_staff_user_001",
"password":"Hello Staff Password"
}' "http://localhost:8000/auth/token/"
POST /auth/token/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"username":"test_staff_user_001",
"password":"Hello Staff Password"
}
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"refresh":"sample_staff_token"
}' "http://localhost:8000/auth/token/refresh/"
POST /auth/token/refresh/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"refresh":"sample_staff_token"
}
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"username":"sample_superuser_001",
"password":"Hello Superuser Password"
}' "http://localhost:8000/auth/token/"
POST /auth/token/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"username":"sample_superuser_001",
"password":"Hello Superuser Password"
}
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"refresh":"sample_superuser_token"
}' "http://localhost:8000/auth/token/refresh/"
POST /auth/token/refresh/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
{
"refresh":"sample_superuser_token"
}
| Status | 0 |
|---|---|
|
curl -X DELETE -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/auth/token/"
DELETE /auth/token/ HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
curl -X PUT -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_token" -d '{
"token":"sample_token"
}' "http://localhost:8000/auth/token/"
PUT /auth/token/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_token
{
"token":"sample_token"
}
| Status | 200 OK |
|---|---|
| Content-Type | application/json |
|
Category: Every event is associated with a category. For Example: Hackathon, Workshop, Coding, Designing, Exhibition.
curl -X GET -H "Accept: application/json" "http://localhost:8000/events/category"
GET /events/category HTTP/1.1
Host: localhost:8000
Accept: application/json
| Status | 0 |
|---|---|
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"name": "Name of Category",
"description": "Description about the Category (Optional)"
}' "http://localhost:8000/events/category"
POST /events/category HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"name": "Name of Category",
"description": "Description about the Category (Optional)"
}
| Status | 201 Created |
|---|---|
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
curl -X PUT -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"description": "Update the description for this category."
}' "http://localhost:8000/events/tags/sample_category_name"
PUT /events/tags/sample_category_name HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"description": "Update the description for this category."
}
| Status | 202 Accepted |
|---|---|
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
curl -X DELETE -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdHVkZW50SUQiOiJ0aGlzaWQiLCJzdHVkZW50RW1haWwiOiJyYW1kQGdtYWlsLmNvbSIsImlhdCI6MTU1NDM5NzYyMiwiZXhwIjoxNTU0NDA0ODIyfQ.bfmiEvKyoqP_y0R1yxYHXHWZIduYlyAKRJWHgQt-hM0" "http://localhost:8000/events/category/sample_category_name"
DELETE /events/category/sample_category_name HTTP/1.1
Host: localhost:8000
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdHVkZW50SUQiOiJ0aGlzaWQiLCJzdHVkZW50RW1haWwiOiJyYW1kQGdtYWlsLmNvbSIsImlhdCI6MTU1NDM5NzYyMiwiZXhwIjoxNTU0NDA0ODIyfQ.bfmiEvKyoqP_y0R1yxYHXHWZIduYlyAKRJWHgQt-hM0
| Status | 204 No Content |
|---|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
Tags: A small highlight about a event. For Example: Free, Difficult, Special. It is optional.
curl -X GET -H "Accept: application/json" "http://localhost:8000/events/tags"
GET /events/tags HTTP/1.1
Host: localhost:8000
Accept: application/json
| Status | 0 |
|---|---|
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"name": "Name of Tag",
"description": "Description about use of Tag (Optional)"
}' "http://localhost:8000/events/tags"
POST /events/tags HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"name": "Name of Tag",
"description": "Description about use of Tag (Optional)"
}
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
| Status | 201 Created |
|---|---|
|
curl -X PUT -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"description": "Update the description for this tag."
}' "http://localhost:8000/events/tags/sample_tags_name"
PUT /events/tags/sample_tags_name HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"description": "Update the description for this tag."
}
| Status | 202 Accepted |
|---|---|
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
curl -X DELETE -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/events/tags/sample_tags_name"
DELETE /events/tags/sample_tags_name HTTP/1.1
Host: localhost:8000
Authorization: Bearer sample_staff_token
| Status | 204 No Content |
|---|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
Event Endpoints. Allow to create new Events, Delete them and update details.
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/events?limit&page&category&order&tags"
GET /events?limit&page&category&order&tags HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"name": "Name of the Event",
"description": "Event Description",
"date": "YYYY-MM-DD",
"time": "HH:MM",
"venue": "Event Venue",
"fees": "Participation Fee",
"prize": ["First Prize", "Second Prize", "Prize for innovation"],
"teamEvent": true,
"minSize": 3,
"maxSize": 8,
"rules": [
"Everyone should Participate",
"Good Work etc etc"
],
"faq": [
[
"Question with multiple Answers",
"Answer"
],
[
"Put Question 2",
"Put Answer here"
]
],
"category": [
"Defaults to Others",
"Can be an array of valid categories"
],
"tags": [
"Optional",
"Can be an array of valid tags"
]
}' "http://localhost:8000/events"
POST /events HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"name": "Name of the Event",
"description": "Event Description",
"date": "YYYY-MM-DD",
"time": "HH:MM",
"venue": "Event Venue",
"fees": "Participation Fee",
"prize": ["First Prize", "Second Prize", "Prize for innovation"],
"teamEvent": true,
"minSize": 3,
"maxSize": 8,
"rules": [
"Everyone should Participate",
"Good Work etc etc"
],
"faq": [
[
"Question with multiple Answers",
"Answer"
],
[
"Put Question 2",
"Put Answer here"
]
],
"category": [
"Defaults to Others",
"Can be an array of valid categories"
],
"tags": [
"Optional",
"Can be an array of valid tags"
]
}
| Status | 201 Created |
|---|---|
|
curl -X DELETE -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/events/sample_event_id"
DELETE /events/sample_event_id HTTP/1.1
Host: localhost:8000
Authorization: Bearer sample_staff_token
| Status | 200 OK |
|---|
curl -X GET -H "Accept: application/json" "http://localhost:8000/events/sample_event_id"
GET /events/sample_event_id HTTP/1.1
Host: localhost:8000
Accept: application/json
| Status | 200 OK |
|---|---|
|
curl -X PUT -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"name": "Name of the Event",
"description": "Event Description",
"date": "YYYY-MM-DD",
"time": "HH:MM",
"venue": "Event Venue",
"fees": "Participation Fee",
"prize": ["First Prize", "Second Prize", "Prize for innovation"],
"teamEvent": true,
"teamProperties":{
"minSize": 3,
"maxSize": 8
},
"rules": [
"Everyone should Participate",
"Good Work etc etc"
],
"faq": [
[
"Question with multiple Answers",
"Answer1"
],
[
"Put Question 2",
"Put Answer here"
]
],
"category": [
"Defaults to Others",
"Can be an array of valid categories"
],
"tags": [
"Optional",
"Can be an array of valid tags"
]
}' "http://localhost:8000/events/sample_event_id"
PUT /events/sample_event_id HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"name": "Name of the Event",
"description": "Event Description",
"date": "YYYY-MM-DD",
"time": "HH:MM",
"venue": "Event Venue",
"fees": "Participation Fee",
"prize": ["First Prize", "Second Prize", "Prize for innovation"],
"teamEvent": true,
"teamProperties":{
"minSize": 3,
"maxSize": 8
},
"rules": [
"Everyone should Participate",
"Good Work etc etc"
],
"faq": [
[
"Question with multiple Answers",
"Answer1"
],
[
"Put Question 2",
"Put Answer here"
]
],
"category": [
"Defaults to Others",
"Can be an array of valid categories"
],
"tags": [
"Optional",
"Can be an array of valid tags"
]
}
| Status | 202 Accepted |
|---|---|
|
curl -X POST -H "Content-Type: multipart/form-data" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/events/sample_event_id/photo"
POST /events/sample_event_id/photo HTTP/1.1
Host: localhost:8000
Content-Type: multipart/form-data
Accept: application/json
Authorization: Bearer sample_staff_token
| Status | 200 OK |
|---|
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/events/sample_event_id/registrations"
GET /events/sample_event_id/registrations HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_staff_token
| Status | 0 |
|---|---|
|
| Status | 200 OK |
|---|---|
|
curl -X POST -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer sample_token" -d '{
"teamId": "2"
}' "http://localhost:8000/events/sample_event_id/register/"
POST /events/sample_event_id/register/ HTTP/1.1
Host: localhost:8000
Accept: application/json
Content-Type: application/json
Authorization: Bearer sample_token
{
"teamId": "2"
}
| Status | 201 Created |
|---|---|
|
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
curl -X GET -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/events/sample_event_id/registrations/sample_registration_id"
GET /events/sample_event_id/registrations/sample_registration_id HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" "http://{{hostname}}/teams?limit&page&event&user"
failed to parse url
parse http://{{hostname}}/teams?limit&page&event&user: invalid character "{" in host name
| Status | 200 OK |
|---|---|
|
| Status | 200 OK |
|---|---|
|
curl -X POST -H "Accept: application/json" -H "Authorization: Bearer sample_token" -H "Content-Type: application/json" -d '{
"name":"The Gingers"
}' "http://localhost:8000/teams/"
POST /teams/ HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
Content-Type: application/json
{
"name":"The Gingers"
}
| Status | 201 Created |
|---|---|
|
curl -X DELETE -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/teams/sample_team_id"
DELETE /teams/sample_team_id HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 204 No Content |
|---|
curl -X PUT -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer sample_token" -d '{
"name": "The Flockers"
}' "http://localhost:8000/teams/sample_team_id"
PUT /teams/sample_team_id HTTP/1.1
Host: localhost:8000
Accept: application/json
Content-Type: application/json
Authorization: Bearer sample_token
{
"name": "The Flockers"
}
| Status | 200 OK |
|---|---|
|
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/teams/sample_team_id"
GET /teams/sample_team_id HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/users/test_user_001/invitation"
GET /users/test_user_001/invitation HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X PUT -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/users/test_user_001/invitation/sample_team_id/accept/"
PUT /users/test_user_001/invitation/sample_team_id/accept/ HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
| Status | 200 OK |
|---|---|
|
curl -X PUT -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/users/test_user_001/invitation/sample_team_id/reject/"
PUT /users/test_user_001/invitation/sample_team_id/reject/ HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X POST -H "Authorization: Bearer sample_token" -H "Content-Type: application/json" -H "Accept: application/json" -d '{
"username": "test_user_001"
}' "http://{{hostname}}/teams/sample_team_id/invitations"
failed to parse url
parse http://{{hostname}}/teams/sample_team_id/invitations: invalid character "{" in host name
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
| Status | 201 Created |
|---|---|
|
curl -X DELETE -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/teams/sample_team_id/test_user_001"
DELETE /teams/sample_team_id/test_user_001 HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 204 No Content |
|---|
curl -X DELETE -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/teams/sample_team_id/invitations/test_user_001"
DELETE /teams/sample_team_id/invitations/test_user_001 HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 422 Unprocessable Entity (WebDAV) (RFC 4918) |
|---|---|
|
| Status | 204 No Content |
|---|
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/ticket?limit&page&user&topic&status"
GET /ticket?limit&page&user&topic&status HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_staff_token
| Status | 200 OK |
|---|---|
|
curl -X GET -H "Accept: application/json" "http://localhost:8000/ticket/public?limit&page&status=&topic"
GET /ticket/public?limit&page&status=&topic HTTP/1.1
Host: localhost:8000
Accept: application/json
| Status | 200 OK |
|---|---|
| Accept | application/json |
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/ticket/test_user_001"
GET /ticket/test_user_001 HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_token" -d '{
"title": "Another Issue",
"description": "Fix it Faster",
"view": "public or private"
}' "http://localhost:8000/ticket/"
POST /ticket/ HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_token
{
"title": "Another Issue",
"description": "Fix it Faster",
"view": "public or private"
}
| Status | 201 Created |
|---|---|
|
curl -X PUT -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -H "Content-Type: application/json" -d '{
"content": "This is my solution"
}' "http://localhost:8000/ticket/sample_ticket_id/close"
PUT /ticket/sample_ticket_id/close HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_staff_token
Content-Type: application/json
{
"content": "This is my solution"
}
| Status | 200 OK |
|---|---|
|
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/events/sample_event_id/organisers"
GET /events/sample_event_id/organisers HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"username": "user_001",
"role": "role"
}' "http://localhost:8000/events/sample_event_id/organisers"
POST /events/sample_event_id/organisers HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"username": "user_001",
"role": "role"
}
| Status | 0 |
|---|---|
|
curl -X DELETE -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/events/sample_event_id/organisers/test_user_001"
DELETE /events/sample_event_id/organisers/test_user_001 HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_staff_token
| Status | 204 No Content |
|---|
curl -X GET -H "Accept: application/json" -H "Authorization: Bearer sample_token" "http://localhost:8000/events/sample_event_id/volunteers"
GET /events/sample_event_id/volunteers HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_token
| Status | 200 OK |
|---|---|
|
curl -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"username": "user_5",
"task": ["Arrange Rooms", "Take Attendence"]
}' "http://localhost:8000/events/sample_event_id/volunteers"
POST /events/sample_event_id/volunteers HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"username": "user_5",
"task": ["Arrange Rooms", "Take Attendence"]
}
| Status | 0 |
|---|---|
|
curl -X DELETE -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" "http://localhost:8000/events/sample_event_id/volunteers/test_user_001"
DELETE /events/sample_event_id/volunteers/test_user_001 HTTP/1.1
Host: localhost:8000
Accept: application/json
Authorization: Bearer sample_staff_token
| Status | 204 No Content |
|---|
curl -X PUT -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer sample_staff_token" -d '{
"task": ["Task1", "Task2"]
}' "http://localhost:8000/events/sample_event_id/volunteers/test_user_001"
PUT /events/sample_event_id/volunteers/test_user_001 HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Accept: application/json
Authorization: Bearer sample_staff_token
{
"task": ["Task1", "Task2"]
}
| Status | 0 |
|---|---|
|


Dilly
Questions
Add Moments
Friends
Activity
x
First Notification
x
Second Notification
x
Third Notification
Account
Friends
Account Settings
Help&Support
Logout
Please answer the questions to complete your profile
Which country you dream a lot to visit?
Which was the first country you visited?
When you visited it?
Which was you best concerted you've seen and heard?
When was that concert?
Which is your favourite band or singer?
When you start to like the band or the singer?
Have you ever met a celebrity?
When you met him/her?
When you felt love for the first time?
When you felt this?
Which was your happiest moment from your life?
When this happened?
When did you start primary school?
Which was it?
When did you start secondary school?
Which was it?
When did you start high school?
Which was it?
When did you start faculty?
Which was it?

In what moment of time this happened?
Have you ever been in a holiday? If yes, which was the most beautiful you ever had?
When you've been in this holiday?
Do you have/had any pet? If yes, which was it?
When was the starting moment you had one?
Do you have a hobby/passion? If yes, which is it?
When you discovered this hobby/passion?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15


{% extends "_layouts/base.html" %} {% block metaTitle %}{{ ['Page Not Found', super()]|join(' | ') }}{% endblock %} {% block bodyClasses %}not-found{% endblock %} {% block content %}
Sorry, we couldn't find the page you were looking for. The page may have moved or been deleted.


Interaction with the Little Ones
blueimp Gallery is a touch-enabled, responsive and customizable image and video gallery, carousel and lightbox, optimized for both mobile and desktop web browsers. It features swipe, mouse and keyboard navigation, transition effects, slideshow functionality, fullscreen support and on-demand content loading and can be extended to display additional content types.


This demo use greensock's
GSAP
TweenMax. On the comparison of
GSAP
and
Agile.Tween
,please see
http://www.greensock.com/transitions
The canvas is only used to draw picture


If the data sample contains structured fields then it may take up to 30 seconds to load.
If the browser warns about a 'busy' script then respond to allow more time.
{{col.name}}


Security Requirements needed to access Operations in this API (clients must choose one combination):
Security Requirements needed to access this Operation (clients must choose one combination):
{{ requirement.getSecurityRequirementNames().join(", ") }}
No Security


[gecode-users] If then type constraints
Malcolm Ryan
malcolmr at cse.unsw.edu.au
Mon Mar 10 05:05:37 CET 2008
If I use reification like this, do I have to write my search code so
that it instantiates all the booleans as well as all the 'normal'
variables? Or can I rely on the fact that once all the 'normal'
variables are instantiated all the booleans should also be instantiated.
Malcolm
On 06/03/2008, at 4:15 PM, Christian Schulte wrote:
> Use reification, that's clumsy but works. So, with minimodeling
> support it
> should be something like (~ reifies a linear relation, && is
> conjunction,
> imp is implication, and tt means that the statement must be true):
> post(home, tt(imp(~(v1 == 2),~(v2 != 1) && ~(v3 != 3)));
> or directly:
> BoolVar b1(home,0,1), b2(home,0,1), b3(home,0,1), b23(home,0,1);
> rel(home, v1, IRT_EQ, 2, b1);
> rel(home, v2, IRT_NQ, 1, b2);
> rel(home, v3, IRT_NQ, 3, b3);
> rel(home, b2, BOT_AND, b3, b23);
> rel(home, b1, BOT_IMP, b23, 1);
>
> Or check whether extensional constraints work for you.
>
> Christian
>
> --
> Christian Schulte, www.ict.kth.se/~cschulte/
>
>
> -----Original Message-----
> From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On
> Behalf
> Of Debdeep Banerjee
> Sent: Thursday, March 06, 2008 3:03 PM
> To: users at gecode.org
> Cc: users at gecode.org
> Subject: [gecode-users] If then type constraints
>
> Hi,
> How do I model if-then style constraints ? What I want to do is post
> constraints if a variable is assigned a particular value. For example
> say I have variable set V { v1, v2, v3} and each of them has the
> domain
> {1,2,3}. what I want to achieve is
> if v1== 2 then
> v2 !=1 /\ v3 !=3
>
> I know I can do this using a custom propagator, but is there any
> other way ?
>
> With regards
> Debdeep
>
> --
> Debdeep Banerjee
> PhD Candidate
> CSL/RSISE/NICTA
> Australian National University
> Email: debdeep.banerjee at rsise.anu.edu.au
> Web:http://rsise.anu.edu.au/~banerjed
>
>
>
> _______________________________________________
> Gecode users mailing list
> users at gecode.org
> https://www.gecode.org/mailman/listinfo/gecode-users
>
>
> _______________________________________________
> Gecode users mailing list
> users at gecode.org
> https://www.gecode.org/mailman/listinfo/gecode-users
More information about the gecode-users
mailing list


Before Change
with mock.patch.object(AbstractStoreTestImpl, "search_runs", return_value=runs):
store = AbstractStoreTestImpl()
assert store.list_run_infos(experiment_id, view_type) == run_infos
store.search_runs.assert_called_once_with([experiment_id], None, view_type)
def test_search_runs():
After Change
run_infos = [mock.Mock()]
runs = [mock.Mock(info=info) for info in run_infos]
with mock.patch.object(AbstractStoreTestImpl, "search_runs",
return_value=PagedList(runs, None)):
store = AbstractStoreTestImpl()
result = store.list_run_infos(experiment_id, view_type, page_token=token)
for i in range(len(result)):
assert result[i] == run_infos[i]
assert result.token is None
store.search_runs.assert_called_once_with([experiment_id], None, view_type,
SEARCH_MAX_RESULTS_DEFAULT, None, token)
def test_search_runs():
experiment_id = mock.Mock()
view_type = mock.Mock()
runs = [mock.Mock(), mock.Mock()]


Industry Consortium Point of Contacts for PAWR RFP
{% if incorrect_password %}
Incorrect Password, please try again
{% endif %}
Please enter the password to enter the page
{% csrf_token %} Password:


The instructions are very very simple, when you click on a hole, the color of the hole you clicked and 2 of
its neighbours will be toggled. The toggling sequence of the lamps:
Lamp lighting -> Yellow lamp -> Red lamp -> Lamp turned off
When all the lamps are turned off, the game is completed.
Additionally, you can use the keyboard.
Ctrl+Z -> Undo
R -> Restart
Up Key or W -> Rotate L
(Rotation button is on the left side of the timer)
H -> Help


Home
Results
About Us
Enter a favorite movie below and we'll let you know which one you should watch next!


Git tagging your builds automatically
I need to write a much longer post to explain my thoughts on 'versioning' and what constitutes a release with today's trends of continuous integration, but for now, a simple tip.
I wanted a way to distinguish each build, not each release but each build. There is one excellent source of truth for that which is your git repository.
Wouldn't it be great if each build contained a full git log of what went into it?.
The magic
We use circleci (but it would be trivial to do with any decent continuous integration server) and before building we simply execute git log –oneline –decorate –graph > resources/public/glog.txt
:
machine:
java:
version: oraclejdk8
## Customize dependencies
dependencies:
cache_directories:
- "~/.m2"
pre:
- git fetch --tags
test:
override:
- git log --oneline --decorate --graph > resources/public/glog.txt
- lein full-build-no-tests!
- mkdir -p $CIRCLE_TEST_REPORTS/junit/
- find . -type f -regex ".*/target/test-reports/.*xml" -exec cp {} $CIRCLE_TEST_REPORTS/junit/ \;
- cp target/*.war $CIRCLE_ARTIFACTS
# this doesn't work so commented out
# in favour of an explicit `cp` in the test: post: stage
#general:
# artifacts:
# - "target/*.war"
(resources\public
is exposed from the root of the lein war
WAR
file)
This is of course only one way of doing it, but it was the 'Simplest Thing That Can Possibly Work'. And sure, it corrupts the working directory because resources\public
is under git version control, but it doesn't matter because circleci
containers are disregarded after every build.
That's all for now - why not enjoy some light entertainment :-).


lib/models/addon.js:137
Addon
Extends:
Root class for an Addon. If your addon module exports an Object this will be extended from this base class. If you export a constructor (function), it will not extend from this class.
Hooks:
Constructor Summary
| Public Constructors | |
|---|---|
| public |
Addon(parent, project)
Root class for an Addon. If your addon module exports an Object this will be extended from this base class. If you export a constructor (function), it will not extend from this class. |
Property Summary
| Public Properties | |
|---|---|
| public final |
: Symbol
A Symbol constant for sharing between index.js and addon-proxy.js rather than putting the symbol into the Symbol global cache. The symbol is used in per-bundle cache entries to refer to the field that points at the real instance that a Proxy refers to. |
| public final |
The set of addons that this addon itself depends on. |
| public final |
The host app instance. |
| public final |
The name of this addon. |
| public final |
This addon's parent. |
| public final |
The contents of the addon's |
| public final |
The root project to which this addon belongs. |
| public final |
The absolute path of the root directory where this addon is located. |
| public final |
ui: UI
A |
Method Summary
| Public Methods | |
|---|---|
| public |
blueprintsPath( ): String
Returns the path for addon blueprints. |
| public |
buildError(error)
This hook is called when an error occurs during the preBuild, postBuild or outputReady hooks for addons, or when the build fails |
| public |
cacheKeyForTree(treeType): String
Calculates a cacheKey for the given treeType. It is expected to return a cache key allowing multiple builds of the same tree to simply return the original tree (preventing duplicate work). If it returns null / undefined the tree in question will opt out of this caching system. |
| public |
Augments the application's configuration settings. |
| public |
contentFor(type, config, content)
Allow addons to implement contentFor method to add string output into the associated |
| public |
dependencies( ): Object
|
| public |
Find an addon of the current addon. |
| public |
Check if the current addon intends to be hinted. Typically this is for hinting/linting libraries such as eslint or jshint |
| public |
import(asset, [options])
Imports an asset into this addon. |
| public |
Allows addons to define a custom transform function that other addons and app can use when using |
| public |
included(parent)
This method is called when the addon is included in a build. You would typically use this hook to perform additional imports |
| public |
Allows the specification of custom addon commands. Expects you to return an object whose key is the name of the command and value is the command instance.. |
| public |
init(parent, project)
Initializes the addon. If you override this method make sure and call |
| public |
Allows to mark the addon as developing, triggering live-reload in the project the addon is linked to. |
| public |
|
| public |
lintTree(treeType, tree)
Return value is merged into the tests tree. This lets you inject linter output as test results. |
| public |
moduleName( ): String
Returns the module name for this addon. |
| public |
outputReady(result)
This hook is called after the build has been processed and the build files have been copied to the output directory |
| public |
postBuild(result)
This hook is called after a build is complete. |
| public |
postprocessTree(type, tree): Tree
Post-process a tree |
| public |
preBuild(result)
This hook is called before a build takes place. |
| public |
preprocessTree(type, tree): Tree
Pre-process a tree |
| public |
serverMiddleware(startOptions)
This hook allows you to make changes to the express server run by ember-cli. |
| public |
setupPreprocessorRegistry(type, registry)
Used to add preprocessors to the preprocessor registry. This is often used by addons like ember-cli-htmlbars and ember-cli-coffeescript to add a |
| public |
shouldIncludeChildAddon(childAddon): Boolean
Can be used to exclude addons from being added as a child addon. |
| public |
testemMiddleware(app)
This hook allows you to make changes to the express server run by testem. |
| public |
treeFor(name): Tree
Returns a given type of tree (if present), merged with the application tree. For each of the trees available using this method, you can also use a direct method called |
| public |
treeForAddon(tree): Tree
Returns a tree for this addon |
| public |
treeForAddonTemplates(tree): Tree
Returns the tree for this addon's templates |
| public |
treeForAddonTestSupport(tree): Tree
Returns the tree for all test files namespaced to a given addon. |
| public |
treeForApp(tree): Tree
Returns the tree for all app files |
| public |
treeForPublic(tree): Tree
Returns the tree for all public files |
| public |
treeForStyles(tree): Tree
Returns the tree for all style files |
| public |
treeForTemplates(tree): Tree
Returns the tree for all template files |
| public |
treeForTestSupport(tree): Tree
Returns the tree for all test support files |
| public |
treeForVendor(tree): Tree
Returns the tree for all vendor files |
| Private Methods | |
|---|---|
| private |
_eachProjectAddonInvoke(methodName, args)
Invoke the specified method for each of the project's addons. |
| private |
_findHost( )
This method climbs up the hierarchy of addons up to the host application. |
| private |
Looks in the addon/ and addon/templates trees to determine if template files exist in the pods format that need to be precompiled. |
| private |
_treeFor(name): Tree
|
| private |
_warn( )
|
| private |
addonJsFiles( ): Tree
Returns a tree containing the addon's js files |
| private |
compileAddon(tree): Tree
Runs the addon tree through preprocessors. |
| private |
compileStyles(addonStylesTree): Tree
Runs the styles tree through preprocessors. |
| private |
compileTemplates(tree): Tree
Runs the templates tree through preprocessors. |
| private |
concatFiles(tree, options): Tree
Shorthand method for broccoli-concat |
| private |
Discovers all child addons of this addon and an AddonInfo about each addon in this.addonPackages (keyed on addon name). |
| private |
eachAddonInvoke(methodName, args)
Invoke the specified method for each enabled addon. |
| private |
jshintAddonTree( ): Tree
Returns a tree with JSHint output for all addon JS. |
| private |
preprocessJs( ): Tree
Preprocesses a javascript tree. |
| private |
processedAddonJsFiles(the): Tree
Returns a tree with all javascript for this addon. |
| private |
Looks in the addon/ and addon/templates trees to determine if template files exist that need to be precompiled. |
| private |
treeGenerator( ): Tree
Generates a tree for the specified path |
Public Constructors
lib/models/addon.js:137
public Addon(parent, project)
Public Properties
lib/models/per-bundle-addon-cache/target-instance.js:3
public final : Symbol
A Symbol constant for sharing between index.js and addon-proxy.js rather than putting the symbol into the Symbol global cache. The symbol is used in per-bundle cache entries to refer to the field that points at the real instance that a Proxy refers to.
lib/models/addon.js:223
public final addons: Addon[]
The set of addons that this addon itself depends on.
This array is populated from the addon's listed dependencies
and any items in
ember-addon.paths
in its package.json
.
lib/models/addon.js:188
public final app: EmberApp
The host app instance.
Note: this property will only be present on addons that are a direct dependency
of the application itself, not of other addons. It is also not available in init()
,
but will be set before setupPreprocessorRegistry()
and included()
are invoked.
lib/models/addon.js:170
public final name: String
The name of this addon.
lib/models/addon.js:210
public final parent: Project | Addon
This addon's parent.
If the addon is a direct dependency of an application, then parent
will be the
corresponding project instance. If it's a
dependency of another addon, then parent
will be a reference to that addon.
lib/models/addon.js:245
public final pkg: Object
The contents of the addon's package.json
.
lib/models/addon.js:201
public final project: Project
The root project to which this addon belongs.
lib/models/addon.js:179
public final root: String
The absolute path of the root directory where this addon is located.
lib/models/addon.js:235
public final ui: UI
A console-ui
object that can be used
to log messages for the user and indicate progress on long-running operations.
Public Methods
lib/models/addon.js:1351
public blueprintsPath( ): String
Returns the path for addon blueprints.
Return:
The path for blueprints
Example:
lib/models/addon.js:1650
public buildError(error)
This hook is called when an error occurs during the preBuild, postBuild or outputReady hooks for addons, or when the build fails
Uses:
- Custom error handling during build process
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| error | Error |
|
The error that was caught during the processes listed above |
Example:
lib/models/addon.js:674
public cacheKeyForTree(treeType): String
Calculates a cacheKey for the given treeType. It is expected to return a cache key allowing multiple builds of the same tree to simply return the original tree (preventing duplicate work). If it returns null / undefined the tree in question will opt out of this caching system.
This method is invoked prior to calling treeFor with the same tree name.
You should override this method if you implement custom treeFor or treeFor* methods, which cause addons to opt-out of this caching.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| treeType | String |
|
Return:
cacheKey
lib/models/addon.js:1369
public config(env, baseConfig): Object
Augments the application's configuration settings.
Object returned from this hook is merged with the application's configuration object.
Application's configuration always take precedence.
Uses:
- Modifying configuration options (see list of defaults here)
- For example
minifyJS
storeConfigInMeta
- et, al
- For example
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| env | String |
|
Name of current environment (ie "development") |
| baseConfig | Object |
|
Initial application configuration |
Return:
Configuration object to be merged with application configuration.
Example:
config(environment, appConfig) {
return {
someAddonDefault: "foo"
};
}
lib/models/addon.js:1727
public contentFor(type, config, content)
Allow addons to implement contentFor method to add string output into the associated {{content-for 'foo'}}
section in index.html
Uses:
- For instance, to inject analytics code into
index.html
Example:
lib/models/addon.js:1409
public dependencies( ): Object
Return:
The addon's dependencies based on the addon's package.json
lib/models/addon.js:340
public findOwnAddonByName( )
Find an addon of the current addon.
Example: ember-data depends on ember-cli-babel and wishes to have additional control over transpilation this method helps.
// ember-data/index.js
treeForAddon(tree) {
let babel = this.findOwnAddonByName('ember-cli-babel');
return babel.transpileTree(tree, {
// customize the babel step (see: ember-cli-addons readme for more details);
});
}
lib/models/addon.js:364
public hintingEnabled( )
Check if the current addon intends to be hinted. Typically this is for hinting/linting libraries such as eslint or jshint
lib/models/addon.js:772
public import(asset, [options])
Imports an asset into this addon.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| asset | Object | String |
|
Either a path to the asset or an object with environment names and paths as key-value pairs. |
| options | Object |
|
Options object |
| options.type | String |
|
Either 'vendor' or 'test', defaults to 'vendor' |
| options.prepend | Boolean |
|
Whether or not this asset should be prepended, defaults to false |
| options.destDir | String |
|
Destination directory, defaults to the name of the directory the asset is in |
lib/models/addon.js:1484
public importTransforms( ): Object
Allows addons to define a custom transform function that other addons and app can use when using app.import
.
This function is not implemented by default
Uses:
- An app or addons want to transform a dependency that is being imported using
app.import
.
Return:
An object with custom transforms
Example:
importTransforms() {
return {
'my-custom-transform': function(tree, options) {
// transform the incoming tree and return the updated tree
}
};
}
Alternatively, if you want to process options
before being passed into the custom transform function, use:
importTransforms() {
return {
'my-custom-transform': {
transform: function(tree, options) {
// transform the incoming tree and return the updated tree
},
processOptions: function(assetPath, entry, options) {
// process your options
return options
}
};
}
lib/models/addon.js:739
public included(parent)
This method is called when the addon is included in a build. You would typically use this hook to perform additional imports
Uses:
- including vendor files
- setting configuration options
Note: Any options set in the consuming application will override the addon.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| parent | EmberApp | EmberAddon |
|
The parent object which included this addon |
Example:
included(parent) {
this._super.included.apply(this, arguments);
this.import(somePath);
}
lib/models/addon.js:1460
public includedCommands( ): Object
Allows the specification of custom addon commands. Expects you to return an object whose key is the name of the command and value is the command instance..
This function is not implemented by default
Uses:
- Include custom commands into consuming application
Return:
An object with included commands
Example:
includedCommands() {
return {
'do-foo': require('./lib/commands/foo')
};
}
lib/models/addon.js:254
public init(parent, project)
Initializes the addon. If you override this method make sure and call this._super.init && this._super.init.apply(this, arguments);
or your addon will not work.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| parent | Project | Addon |
|
The project or addon that directly depends on this addon |
| project | Project |
|
The current project (deprecated) |
Example:
init(parent, project) {
this._super.init && this._super.init.apply(this, arguments);
this._someCustomSetup();
}
lib/models/addon.js:393
public isDevelopingAddon( ): Boolean
Allows to mark the addon as developing, triggering live-reload in the project the addon is linked to.
Uses:
- Working on projects with internal addons
Return:
lib/models/addon.js:1419
public isEnabled( ): Boolean
Return:
Whether or not this addon is enabled
lib/models/addon.js:1708
public lintTree(treeType, tree)
Return value is merged into the tests tree. This lets you inject linter output as test results.
Uses:
- JSHint
- any other form of automated test generation that turns code into tests
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| treeType | String |
|
|
| tree | Tree |
|
tree of files (JavaScript files for |
Example:
lib/models/addon.js:1336
public moduleName( ): String
Returns the module name for this addon.
Return:
module name
lib/models/addon.js:1633
public outputReady(result)
This hook is called after the build has been processed and the build files have been copied to the output directory
It's passed a result
object which contains:
directory
Path to build output
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| result | Object |
|
Build result object |
Example:
- Opportunity to symlink or copy files elsewhere.
- ember-cli-rails-addon
- In this case we are using this in tandem with a rails middleware to remove a lock file. This allows our ruby gem to block incoming requests until after the build happens reliably.
lib/models/addon.js:1617
public postBuild(result)
This hook is called after a build is complete.
It's passed a result
object which contains:
directory
Path to build output
Uses:
- Slow tree listing
- May be used to manipulate your project after build has happened
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| result | Object |
|
Build result object |
lib/models/addon.js:1542
public postprocessTree(type, tree): Tree
Post-process a tree
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| type | String |
|
What kind of tree (eg. 'js', 'css', 'template') |
| tree | Tree |
|
Tree to process |
Return:
Processed tree
Example:
lib/models/addon.js:1609
public preBuild(result)
This hook is called before a build takes place.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| result | Object |
|
Build object |
lib/models/addon.js:1528
public preprocessTree(type, tree): Tree
Pre-process a tree
Uses:
- removing / adding files from the build.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| type | String |
|
What kind of tree (eg. 'js', 'css', 'template') |
| tree | Tree |
|
Tree to process |
Return:
Processed tree
lib/models/addon.js:1555
public serverMiddleware(startOptions)
This hook allows you to make changes to the express server run by ember-cli.
It's passed a startOptions
object which contains:
app
Express server instanceoptions
A hash with:project
Current projectwatcher
environment
This function is not implemented by default
Uses:
- Tacking on headers to each request
- Modifying the request object
Note: that this should only be used in development, and if you need the same behavior in production you'll need to configure your server.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| startOptions | Object |
|
Express server start options |
Example:
serverMiddleware(startOptions) {
var app = startOptions.app;
app.use(function(req, res, next) {
// Some middleware
});
}
lib/models/addon.js:1666
public setupPreprocessorRegistry(type, registry)
Used to add preprocessors to the preprocessor registry. This is often used by addons like ember-cli-htmlbars
and ember-cli-coffeescript to add a template
or js
preprocessor to the registry.
Uses:
- Adding preprocessors to the registry.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| type | String |
|
either |
| registry | Object |
|
the registry to be set up |
Example:
setupPreprocessorRegistry(type, registry) {
// ensure that broccoli-ember-hbs-template-compiler is not processing hbs files
registry.remove('template', 'broccoli-ember-hbs-template-compiler');
registry.add('template', {
name: 'ember-cli-htmlbars',
ext: 'hbs',
_addon: this,
toTree(tree) {
var htmlbarsOptions = this._addon.htmlbarsOptions();
return htmlbarsCompile(tree, htmlbarsOptions);
},
precompile(string) {
var htmlbarsOptions = this._addon.htmlbarsOptions();
var templateCompiler = htmlbarsOptions.templateCompiler;
return utils.template(templateCompiler, string);
}
});
if (type === 'parent') {
this.parentRegistry = registry;
}
}
lib/models/addon.js:1428
public shouldIncludeChildAddon(childAddon): Boolean
Can be used to exclude addons from being added as a child addon.
Uses:
- Abstract away multiple addons while only including one into the built assets
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| childAddon | Addon |
|
Return:
Whether or not a child addon is supposed to be included
Example:
shouldIncludeChildAddon(childAddon) {
if(childAddon.name === 'ember-cli-some-legacy-select-component') {
return this.options.legacyMode;
} else if(childAddon.name === 'ember-cli-awesome-new-select-component') {
return !this.options.legacyMode;
} else {
return this._super.shouldIncludeChildAddon.apply(this, arguments);
}
}
lib/models/addon.js:1594
public testemMiddleware(app)
This hook allows you to make changes to the express server run by testem.
This function is not implemented by default
Uses:
- Adding custom test-specific endpoints
- Manipulating HTTP requests in tests
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| app | Object |
|
the express app instance |
lib/models/addon.js:586
public treeFor(name): Tree
Returns a given type of tree (if present), merged with the
application tree. For each of the trees available using this
method, you can also use a direct method called treeFor[Type]
(eg. treeForApp
).
Available tree names:
Uses:
- manipulating trees at build time
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| name | String |
|
Return:
lib/models/addon.js:828
public treeForAddon(tree): Tree
Returns a tree for this addon
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
Addon file tree
Example:
treeForAddon() {
var tree = this._super.treeForAddon.apply(this, arguments);
var checker = new VersionChecker(this);
var isOldEmber = checker.for('ember', 'bower').lt('1.13.0');
if (isOldEmber) {
tree = new Funnel(tree, { exclude: [ /instance-initializers/ ] });
}
return tree;
}
lib/models/addon.js:816
public treeForAddonTemplates(tree): Tree
Returns the tree for this addon's templates
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
Addon Template file tree
lib/models/addon.js:925
public treeForAddonTestSupport(tree): Tree
Returns the tree for all test files namespaced to a given addon.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
lib/models/addon.js:792
public treeForApp(tree): Tree
Returns the tree for all app files
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
App file tree
lib/models/addon.js:905
public treeForPublic(tree): Tree
Returns the tree for all public files
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
Public file tree
lib/models/addon.js:862
public treeForStyles(tree): Tree
Returns the tree for all style files
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
The tree to process, usually |
Return:
The return tree has the same contents as the input tree, but is moved so that the app/styles/
path is preserved.
lib/models/addon.js:804
public treeForTemplates(tree): Tree
Returns the tree for all template files
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
Template file tree
lib/models/addon.js:893
public treeForTestSupport(tree): Tree
Returns the tree for all test support files
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
Test Support file tree
lib/models/addon.js:881
public treeForVendor(tree): Tree
Returns the tree for all vendor files
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Return:
Vendor file tree
Private Methods
lib/models/addon.js:506
private _eachProjectAddonInvoke(methodName, args)
Invoke the specified method for each of the project's addons.
lib/models/addon.js:716
private _findHost( )
This method climbs up the hierarchy of addons up to the host application.
This prevents previous addons (prior to this.import
, ca 2.7.0)
to break at importing assets when they are used nested in other addons.
lib/models/addon.js:1000
private _shouldCompilePodTemplates( ): Boolean
Looks in the addon/ and addon/templates trees to determine if template files exist in the pods format that need to be precompiled.
This is executed once when building, but not on rebuilds.
Return:
indicates if pod based templates need to be compiled for this addon
lib/models/addon.js:652
private _treeFor(name): Tree
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| name | String |
|
Return:
lib/models/addon.js:574
private _warn( )
lib/models/addon.js:1272
private addonJsFiles( ): Tree
Returns a tree containing the addon's js files
Return:
The filtered addon js files
lib/models/addon.js:1152
private compileAddon(tree): Tree
Runs the addon tree through preprocessors.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Addon file tree |
Return:
Compiled addon tree
lib/models/addon.js:961
private compileStyles(addonStylesTree): Tree
Runs the styles tree through preprocessors.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| addonStylesTree | Tree |
|
Styles file tree |
Return:
Compiled styles tree
lib/models/addon.js:1118
private compileTemplates(tree): Tree
Runs the templates tree through preprocessors.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Templates file tree |
Return:
Compiled templates tree
lib/models/addon.js:379
private concatFiles(tree, options): Tree
Shorthand method for broccoli-concat
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| tree | Tree |
|
Tree of files |
| options | Object |
|
Options for broccoli-concat |
Return:
Modified tree
lib/models/addon.js:431
private discoverAddons( )
Discovers all child addons of this addon and an AddonInfo about each addon in this.addonPackages (keyed on addon name).
Child addons include those from 'dependencies' (not devDependencies) and in-repo addons
Any packageInfos that we find that are marked as not valid are excluded.
lib/models/addon.js:481
private eachAddonInvoke(methodName, args)
Invoke the specified method for each enabled addon.
lib/models/addon.js:1206
private jshintAddonTree( ): Tree
Returns a tree with JSHint output for all addon JS.
Return:
Tree with JShint output (tests)
lib/models/addon.js:1289
private preprocessJs( ): Tree
Preprocesses a javascript tree.
Return:
Preprocessed javascript
lib/models/addon.js:1300
private processedAddonJsFiles(the): Tree
Returns a tree with all javascript for this addon.
Parameters:
| Name | Type | Attribute | Description |
|---|---|---|---|
| the | Tree |
|
tree to preprocess |
Return:
Processed javascript file tree
lib/models/addon.js:986
private shouldCompileTemplates( ): Boolean
Looks in the addon/ and addon/templates trees to determine if template files exist that need to be precompiled.
This is executed once when building, but not on rebuilds.
Return:
indicates if templates need to be compiled for this addon
lib/models/addon.js:539
private treeGenerator( ): Tree
Generates a tree for the specified path


{% extends 'layout.html' %} {% block pageTitle %} What is your name? {% endblock %} {% block content %}
We use your reference number to find your application.


repository.repository_mongo package¶
Subpackages¶
Submodules¶
repository.repository_mongo.db_atlas module¶
-
repository.repository_mongo.db_atlas.
close_db
(e=None)[source]¶ Check if a connection has been created. If the connection exists this one will be closed. This function will be called after each request to close the connection in case is set up
-
repository.repository_mongo.db_atlas.
get_db
()[source]¶ Create a connection to the db to be able to perform any queries and operations. It creates the special object ‘g’ that is unique for each request
Returns: g, global object storing the data that have to be accesse during the request. This connection will be stored and reused for the next request
-
repository.repository_mongo.db_atlas.
init_app
(app)[source]¶ Register the functions ‘close_db’ and ‘init_db_command’ with the application instance, otherwise they won’t be used by the application. ‘close_db’ is called after each request, this means that the db will close the connection after each request. ‘init-db’ command has been registered with the app, and now it can be called using in this order the below flask commands:
1.-set FLASK_APP=<app.py> 2.-set FLASK_ENV=development 3.-flask init-db
- Parameters
'app.teardown_appcontext()' –
flask to call the function when cleaning up after returning the response (tells) –
'app.cli.add_command()' –
a new command that can be called with the flask command (adds) –
repository.repository_mongo.db_model module¶
-
class
repository.repository_mongo.db_model.
Stock
(*args, **values)[source]¶ Bases:
mongoengine.document.Document
-
exception
DoesNotExist
¶ Bases:
mongoengine.errors.DoesNotExist
-
exception
MultipleObjectsReturned
¶ Bases:
mongoengine.errors.MultipleObjectsReturned
-
id
¶ A unicode string field.
-
name
¶ A unicode string field.
-
objects
¶ The default QuerySet Manager.
Custom QuerySet Manager functions can extend this class and users can add extra queryset functionality. Any custom manager methods must accept a
Document
class as its first argument, and aQuerySet
as its second argument.The method function should return a
QuerySet
, probably the same one that was passed in, but modified in some way.
-
quality
¶ 32-bit integer field.
-
sell_in
¶ 32-bit integer field.
-
exception
repository.repository_mongo.repo module¶
-
class
repository.repository_mongo.repo.
Factory
[source]¶ Bases:
object
-
static
create_object_item
(item)[source]¶ Create an object from each item included inside the data base. Depending which one are the names of the items, they will have one class or other assigned to them and it will create and object from the selected class. This method was created by @dfleta from github
- Parameters
item (list) – Is a list that contains all the required info of each item, it has three different aspects: name, sell_in and quality.
- Returns
Returns an object that have assigned a class and the class has been assigned to the object by the name of this one
- Return type
[Object]
-
static


Statistical Models
We will be combining our analysis of the standard deviation model and the z-score model since they use very similar implementations -- only the ‘loss’ value calculations are different. This section provides a brief overview of why and how we used these models to map the variability of users’ keystrokes patterns.
Getting an approximate range for variability is important for the two models. We want to do this in the training step, which we will talk more about when we discuss implementations. This approximate range will be our keystroke patterns identifiers, assuming users have different patterns.
Standard Deviation and Z-Score
Figure 1: Stouffer's z-score
The standard deviation model is the most straightforward approach out of all three models. Standard deviations measure how ‘far’ values in the data set are from the mean. In our project, we used them to measure how far a user’s input is from their previously ‘saved’ keystroke pattern.
For the z-score model, out of different approaches using z-scores, we decided to follow Stouffer’s approach. First, a z-score is the number of standard deviations, some values in the data set are away from the mean. A standard z-score approach would use individual z-scores to analyze variability within a dataset. Stouffer’s approach is a bit different from standard z-score calculations since we define Z using a standard normal cumulative distribution function. In other words, Stouffer’s z-score is the averaged sum of all z-scores.
Bounds
Another important concept we should define before discussing the actual implementations is ‘bounds’. After we collected values that measure variability of user’s keystroke patterns, we needed a way to test whether these approximations of typing patterns are suitable in assessing new input keystrokes. When are our measurements most successful in accepting true users while rejecting false users? We used ‘bounds’ to define possible moments in which this could happen.
We used the name ‘bounds’ in both the standard deviation model and the z-score model. A ‘bound’ points to a number that marks the end of a range we will be looking at to see if our loss lies within that certain range. In a sense, it represents test values for variability.
In the stdev model, the bounds represent the ‘count’ of standard deviations. Using bounds, we attempted to figure out whether a sample data is within the range defined by 'mean +/- stdev*bound'. In the z-score model, the bounds represent the averaged sum of z-scores. With the z-score model, we checked whether the averaged total sum of z-scores is less than a certain number (bound).
We expected adding up z-scores to improve our statistical models. The ranges which we would test the user's input data in would become more flexible since individual variability measurements would even out. The z-score model, especially using Stouffer's calculations, is a more holistic approach to mapping variability.
Implementations
We first used the online data to get a rough ‘outline’ of the models. The online data step consists of a training step and a testing step. After testing, we got the optimal bound, which marks the moment in which the model is the most successful in accepting true users while rejecting false users.
Next, we used the survey data, which we have collected with our self-constructed survey. We proceeded with going through the same training and testing steps. There were slight changes to how we train and test our data, though the general idea of what’s going on in these steps remained the same.
Again, the approaches used for the two models are much similar, but there is a distinct difference in ‘what’ we calculated that ultimately makes the approximations we make using the z-score model better in representing keystroke patterns.
1. The first step of the two model finds the optimal bound using only the online data set. We trained the model on 10 random samples of a certain user, and tested it on the rest of the data. The training step involves taking the standard deviation and mean of the 10 random samples.
2. With the results we got from the training step, we performed different comparative calculations in the two models.
There’s not much ‘extra’ calculations we needed to do for the standard deviation model since the values we would be comparing to didn't need to be preprocessed for our final comparison step.
In the z-score model, however, with the standard deviation and mean, we were able to figure out the z-scores corresponding to each keystroke of a new input (dwell time and flight time of a key press/ key presses). By summing up all z-scores, we got our total input loss (a.k.a. the distance from the average of the 10 random samples to the new input).
Figure 2: ROC curves with optimal bounds marked
3. We then compared these losses against our 11 bounds (0 - 10) to construct ROC curves (Figure 2). If the loss is below a bound, we accepted (TA or FA). Otherwise, we rejected (TR or FR). The most important information we got from this first step is the optimal bound, which is when TAR (true acceptance rate) + FAR (false acceptance rate) = 1, EER. In our tests, the optimal bound was 6 for the standard deviation model and 8 for the z-score model.
4. After we figured out the optimal bounds, we moved on to stage two: we applied the same training and testing methods to the survey data.
Some minor details we still needed to change were the number of iterations we make in the testing step. First of all, we didn’t need to compare our losses to 11 bounds! Just one, our optimal bound, was okay. Additionally, we no longer were required to look through ALL keystroke data of a certain user. We conducted 2 testing rounds. In one, we used the first 10 inputs at training and in the other we used the second 10 inputs to train. In both, we used the last 10 inputs in testing.
Results
Figure 3: Results from two different training rounds
Recall that the numbers in Figure 3 are percentages, and that higher TAR and lower FAR are desired.
The bests results from the standard deviation model were from the second set of survey tests (2nd 10 tests, or tests 11-20).
The best results from the z-score model were also from the second set of survey tests.
Though the first testing round gave us a higher true acceptance rate, it also resulted in a higher false acceptance rate for the z-score model. This is probably because the test takers used the first set of tests to get familiarized with the never before seen password ‘.tie5Roanl’, thereby resulting in higher typing variability. The same reason applies to the results we observed from the standard deviation model.
We also noticed that our results match our speculation about the z-score model and how Stouffer’s approach would improve model results. Since we accepted users based on all z-scores, and this balanced out some of the approximated ranges for our identifier, we could say that the standard deviation model is a bit stricter in terms of accepting ‘true’ users compared to the z-score model. As a result, the z-score model shows a better TAR but sometimes shows a larger FAR, a maximum of 0.9 even.


No listings accepting Bitcoin Cash found in {{section_title}}.
Try clearing the Bitcoin Cash only filter to see all listings, then reach out to them over social media or e-mail
{%- assign section_id = include.id-param -%} {%- assign section_title = include.title-param -%} {%- assign section_file = site.data[section_id] -%} {%- assign count_bch = 0 -%} {%- assign count_listings = 0 -%} {%- for call in section_file.rpc -%} {%- assign count_listings = count_listings | plus: '1' -%} {%- if call.abc or call.bu or call.xt or call.bitprim -%} {%- assign count_bch = count_bch | plus: '1' -%} {%- endif -%} {%- endfor -%}


--- layout: post title: ! 'Book Review: Danielle Steel - Betrayal' tags: - Book Review status: publish type: post published: true meta: _yoast_wpseo_linkdex: '88' _edit_last: '2' _yoast_wpseo_focuskw: Danielle Steel - Betrayal _yoast_wpseo_title: Danielle Steel - Betrayal - Miss Enchanted _yoast_wpseo_metadesc: ! 'Book Review: Danielle Steel - Betrayal' _yoast_wpseo_meta-robots-noindex: '0' _yoast_wpseo_meta-robots-nofollow: '0' _yoast_wpseo_meta-robots-adv: none _yoast_wpseo_sitemap-include: ! '-' _yoast_wpseo_sitemap-prio: ! '-' _yoast_wpseo_canonical: '' _yoast_wpseo_redirect: '' _wp_old_slug: ds _thumbnail_id: '6103' _yoast_wpseo_metakeywords: '' ---
I have always had a good read from Daniel Steel. She has this very unique way of introducing her characters. If you have read her books, I am pretty sure you will understand what that means. This is my third pick from her after Lone Eagle and Sisters. Danielle Steel - Betrayal is a story of a talented Hollywood Director and the betrayal she faces from the people she loved the most.
Price: Rs.299.. you can check out some good deals and comparison on books here at MySmartPrice Story summary & plotFirst 1-4 chapters dedicatedly emphasize on explaining the various characters again and again. I found some part of text repeated so many times in the book, that was really unnecessary and really boring. The plot is introduced a little later... but I must warn you, if you want to grab a copy of Betrayal then please do no read the summery of the book at the back else everything is very predictable. But then that's the case with every DS book that I have ever read. You will expect some changes or excitement during the read, but the story is very plain and simple.
Why you should pick this book, because


Learn more about me
Marketing Program Manager at Verathon, a global medical device company.
I am a curious individual who loves to learn and explore. I started my career in international health, where I lived in Kazakhstan and Moldova. I eventually expanded my expertise towards marketing and business.


This service allows to get information about current status of projects:
main information, bugs' statistic.
Just select interest project.
{% extends "layout.html" %} {% block body %}
| Project | Total Critical Unresolved Bugs | Total Unresolved Bugs | Total Number of Bugs |
|---|---|---|---|
| {{ statistic[p]["critical"] }} | {{ statistic[p]["unresolved"] }} | {{ statistic[p]["total"] }} |


Combines literate programming ('knitr' and 'rmarkdown') and version control ('Git', via 'git2r') to generate a website containing time-stamped, versioned, and documented results.
| Version: | 1.1.1 |
| Depends: | R (≥ 3.2.5) |
| Imports: | callr, getPass, git2r, glue, knitr (≥ 1.18), methods, rmarkdown (≥ 1.7), rprojroot, rstudioapi, R.utils, stringr (≥ 1.1.0), tools, utils, whisker, yaml |
| Suggests: | covr, devtools, testthat, withr |
| Published: | 2018-07-06 |
| Author: | John Blischak [aut, cre], Peter Carbonetto [aut], Matthew Stephens [aut] |
| Maintainer: | John Blischak <jdblischak at uchicago.edu> |
| BugReports: | https://github.com/jdblischak/workflowr/issues |
| License: | MIT + file LICENSE |
| URL: | https://github.com/jdblischak/workflowr |
| NeedsCompilation: | no |
| SystemRequirements: | pandoc (>= 1.12.3) - http://pandoc.org |
| Materials: | NEWS |
| CRAN checks: | workflowr results |
| Reference manual: | workflowr.pdf |
| Vignettes: |
Getting started with workflowr Customize your research website Migrating an existing project to use workflowr How the workflowr package works Frequently asked questions |
| Package source: | workflowr_1.1.1.tar.gz |
| Windows binaries: | r-devel: workflowr_1.1.1.zip, r-release: workflowr_1.1.1.zip, r-oldrel: workflowr_1.1.1.zip |
| OS X binaries: | r-release: workflowr_1.1.1.tgz, r-oldrel: workflowr_1.1.1.tgz |
| Old sources: | workflowr archive |
Please use the canonical form https://CRAN.R-project.org/package=workflowr to link to this page.


What if Australian property prices are still falling?
by Unconventional EconomistMartin North and John Adams have challenged the notion that Australian dwelling values are rising strongly, claiming that dwelling values across three quarters of suburbs fell in value over July to October, according to Realestate.com.au data:
This, they claim, challenges the narrative of a strong property rebound and represents a “pattern of unusual and fishy behaviour” whereby “the establishment has sought to kill the counter narrative that the market is falling”.
There are 968 words left in this subscriber-only article.


Ortholog info
menu bar is under developing
Links
Action
Another action
Something else here
ID:1009; Arginine Receptor
Alignment Viewer
Function 1
Function 2
Function 3
Phylogenetic tree
Download
Function 2
Function 3


emonTH: pulse AND one-wire temperature measurement; AC with battery backup?
Submitted by markocosic on Wed, 24/09/2014 - 15:18
Hello,
I'd like to monitor hot water usage. Flow rate via pulse output flow meter and incoming/outgoing temperatures using the one-wiresensors clamped to the copper pipes to and from a heat exchanger.
Q1) Can I do this using the emonTH rather than an emonTx V2?
It's the same hardware base and has the two inputs I need; right? (forgive the silly question: I usually work on the water side)
A slight complication is that the heat exchangers are on thermal stores are located in social housing with prepayment electricity meters: AC power availability is not guaranteed and I'd like to leave them there for 6 months unattended.
Q2a) Would it be practical to fire up the emonTH (or emonTx V2) in response to an interrupt from the pulse output flow meter, read the temperatures, keep logging pulses and temperatures every second or so whilst they are arriving/hot water is being used then go back to sleep when it's been 10 seconds and no data has been received? Is this likely to give acceptable battery life if I were to use D-cells?
Q2b) Do you know of any "USB UPSes" that are inexpensive and suitable for running an emonTH or emonTx V2 in a permanently on manner for a day or two without AC power?
emonTH: pulse AND one-wire temperature measurement; AC with battery backup?
Submitted by markocosic on Wed, 24/09/2014 - 15:18Hello,
I'd like to monitor hot water usage. Flow rate via pulse output flow meter and incoming/outgoing temperatures using the one-wiresensors clamped to the copper pipes to and from a heat exchanger.
Q1) Can I do this using the emonTH rather than an emonTx V2?
It's the same hardware base and has the two inputs I need; right? (forgive the silly question: I usually work on the water side)
A slight complication is that the heat exchangers are on thermal stores are located in social housing with prepayment electricity meters: AC power availability is not guaranteed and I'd like to leave them there for 6 months unattended.
Q2a) Would it be practical to fire up the emonTH (or emonTx V2) in response to an interrupt from the pulse output flow meter, read the temperatures, keep logging pulses and temperatures every second or so whilst they are arriving/hot water is being used then go back to sleep when it's been 10 seconds and no data has been received? Is this likely to give acceptable battery life if I were to use D-cells?
Q2b) Do you know of any "USB UPSes" that are inexpensive and suitable for running an emonTH or emonTx V2 in a permanently on manner for a day or two without AC power?
Thanks,
--
Marko


Datasets
Throughout the years I've had to create different datasets for different things. A lot of them are pretty boring, but here's a few that are cool!:
U.S.D.A. Pomological Watercolors
Description: Watercolor collection documenting fruit and nut
varieties developed by growers or introduced by USDA plant explorers
around the turn of the 20th century.
National Geographic Magazine Covers
Description: Covers of all National Geographic Magazines (1960-2018). Includes script to scrape recent years' data.
Bob Ross Paintings
Description: All Bob Ross paintings (and a few from his son) featured in the TV Show 'The Joy of Painting'.
Skate Video Music
Description: Dataset covering the music used in skateboarding videos from 1989 to 2018. Data scraped from skatevideosite.com.


Plots of the vacancy versus time for the nanocrystalline NiAl models with different grain sizes of ( a) 6.5 nm at 1200 K; ( b) 4.5 nm at1200 K; ( c) 3.8 nm at 1200 K; ( d) 6.5 nm at 1400 K; ( e) 4.5 nm at 1400 K; ( f) 3.8 nm at 1400 K under the stress levels of 1.5, 2.0 and 2.5 GPa.


Black Friday 2019 iPhone deals
Shacknews has collected all the best Black Friday deals on new iPhones from your favorite retailers.
by Chris JarrardBlack Friday is now upon us. It is that special time of year when retailers begin blood feuds with each other in an attempt to sell discount electronics to the masses. The winner of this war can be you if you know which deals to look for. Our crack team of deal-hunting specialists has combed the depths of the internet to find the best deals on iPhones. You’ll be able to get the right phone for your needs at a price that won’t leave you destitute.
Black Friday 2019 iPhone deals
-
Walmart
• $450 Walmart eGift Card with new iPhone XS with new Verizon or AT&T activation (in-store only)
• $400 Walmart eGift Card with new iPhone XS Max, iPhone XR with new Verizon or AT&T activation (in-store only)
• $300 Walmart eGift Card with new iPhone 11, iPhone 11 Pro, iPhone 11 Pro Max with new Verizon or AT&T activation (in-store only)
• iPhone 6s 32GB for Straight Talk - $149 ($50 off)
-
Amazon
• Apple iPad Pro (12.9-inch, Wi-Fi, 256GB) - Space Gray - $1049 ($100 off)
• Apple iPad Pro (11-inch, Wi-Fi, 256GB) - Silver - $879 ($70 off)
• Apple AirPods Pro - $235 ($14 off)
-
Best Buy
• 11-Inch iPad Pro with Wi-Fi 64GB Space Gray - $649 ($150 off)
• Apple Watch Series 3 (GPS) - $189 ($10 off)
• Apple Watch Series 4 (GPS) - $249 ($50 off)
-
AT&T
• iPhone XR 64GB $5 a month with new activation and approved credit
-
Verizon
• Get $700 bill credit with the purchase of 2 new iPhones (11 Pro Max, 11 Pro, 11) with new line activation
Be sure to check back with us as we continue to update these iPhone deals over the course of Black Friday. While you’re here, take a look at our Black Friday 2019 Hub for even more promotions, including Nintendo Switch, Xbox One, and PS4!
*Shacknews may receive a small compensation for any purchases made using the links provided in this article.


#include <objtools.h>
|
| | Material (QString _name, QVector3D _Ka, QVector3D _Kd, QVector3D _Ks, int _Ns, int _illum, QString KaImage, QString KdImage) |
| |
| QString | serialize () |
| | Serialize the material object into a string return a QString that can be directly write into .mtl. More...
|
| |
◆ Material()
| Material::Material |
( |
QString |
_name, |
|
|
QVector3D |
_Ka, |
|
|
QVector3D |
_Kd, |
|
|
QVector3D |
_Ks, |
|
|
int |
_Ns, |
|
|
int |
_illum, |
|
|
QString |
KaImage, |
|
|
QString |
KdImage |
|
) |
| |
|
inline |
◆ serialize()
| QString Material::serialize |
( |
| ) |
|
Serialize the material object into a string return a QString that can be directly write into .mtl.
◆ illum
◆ Ka
◆ Kd
◆ Ks
◆ Map_Ka
◆ Map_Kd
◆ name
◆ Ns
The documentation for this class was generated from the following files: